what repro list should i use?

Forum Forums New users New Users and General Questions what repro list should i use?

Tagged: 

  • This topic has 6 replies, 5 voices, and was last updated Sep 14-10:08 pm by anticapitalista.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #67028
    Member
    bertil

    Just fire up antiX after a couple of years in a drawer.

    Where can I find a list with the new repro to configure?

    Thanks

    #67030
    Moderator
    christophe
    Helpful
    Up
    0

    Hi, bertil.
    Didn’t sudo apt update work as-is?

    confirmed antiX frugaler, since 2018

    #67041
    Forum Admin
    rokytnji
    Helpful
    Up
    0

    inxi -Fxz -r

    or

    inxi -V8 -z

    also needs to be posted before anyone can answer you.

    Sometimes I drive a crooked road to get my mind straight.
    Not all who Wander are Lost.
    I'm not outa place. I'm from outer space.

    Linux Registered User # 475019
    How to Search for AntiX solutions to your problems

    #67144
    Member
    sybok
    Helpful
    Up
    0

    Hi, please provide the inxi output.
    This will identify the repos used so far, antiX version etc.

    If you have used stable/testing repository, I would suggest to update via
    sudo apt update && sudo apt dist-upgrade && sudo apt autoclean
    Then, having identified the antiX/Debian version from repositories, you may check the EOL (end-of-life) for your release and decide what to do.

    If ‘buster’ (Debian 10) was used, I would keep it as is till antiX 21 (based on ‘bullseye’ = Debian 11) is officially out.
    If you are adventures, you may want to experiment with changing ‘buster’ to ‘bullseye’ and upgrade.
    Be warned that you may/will run into several minor issues!
    If ‘stretch’ (Debian 9) was used, I would decide according to the EOL.

    Note that antiX 17 (I am not sure if it is ‘buster’/’stretch’ based) is supported until 2022, see this link.

    Also, I have recently updated all my ‘buster’ (Debian 10) based antiX-stable installations to ‘bullseye’ (upcoming antiX 21).
    I have manually replaced all occurences of ‘buster’ by ‘bullseye’; setting up the repositories was a 3-step process:
    1) buster to bullseye (including occurrences of ‘Buster’)
    for f in /etc/apt/sources.list.d/*.list; do sudo cp "$f" "${f}.old"; sudo sed -i 's/\([Bb]\)uster/\1ullseye/g' "$f"; done
    2) Rename all filenames ‘*.list’ with ‘buster’ in name to ‘bullseye’.
    3) Security; there was a change in security and the new correct line is:
    http://security.debian.org/ bullseye-security

    Be warned that I did run into several minor issues/errors during the upgrade!

    #67249
    Member
    bertil
    Helpful
    Up
    0

    Sorry, here is some more info:

    I get theese errors:

    Err:3 http://iso.mxrepo.com/antix/buster buster InRelease                                                                      
      The following signatures were invalid: EXPKEYSIG DB36CDF3452F0C20 antiX (antix repo) <repo@antixlinux.com>
    

    and

    E: Repository 'http://ftp.gr.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
    
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    282 packages can be upgraded. Run 'apt list --upgradable' to see them.
    W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://iso.mxrepo.com/antix/buster buster InRelease: The following signatures were invalid: EXPKEYSIG DB36CDF3452F0C20 antiX (antix repo) <repo@antixlinux.com>
    W: Failed to fetch http://iso.mxrepo.com/antix/buster/dists/buster/InRelease  The following signatures were invalid: EXPKEYSIG DB36CDF3452F0C20 antiX (antix repo) <repo@antixlinux.com>
    W: Some index files failed to download. They have been ignored, or old ones used instead.
    

    and more like that.

    inxi -Fxz -r gives me

    System:    Host: antix1 Kernel: 4.9.193-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 
               Desktop: IceWM 1.5.5+git20190610 Distro: antiX-17.1_x64-full Heather Heyer 17 March 2018 
               base: Debian GNU/Linux 10 (buster) 
    Machine:   Type: Laptop System: LENOVO product: 20175 v: Lenovo IdeaPad Yoga 13 serial: <filter> 
               Mobo: LENOVO model: INVALID v: 31900003WIN8 STD MLT serial: <filter> UEFI [Legacy]: LENOVO v: 66CN55WW 
               date: 02/28/2013 
    Battery:   ID-1: BAT1 charge: 23.5 Wh condition: 23.8/49.3 Wh (48%) model: Lenovo IdeaPad Mocca2 status: Charging 
    CPU:       Topology: Dual Core model: Intel Core i3-3227U bits: 64 type: MT MCP arch: Ivy Bridge rev: 9 L2 cache: 3072 KiB 
               flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 15164 
               Speed: 1537 MHz min/max: 800/1900 MHz Core speeds (MHz): 1: 1537 2: 968 3: 1882 4: 1631 
    Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 
               Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1600x900~60Hz 
               OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 18.3.6 direct render: Yes 
    Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
               bus ID: 00:1b.0 
               Sound Server: ALSA v: k4.9.193-antix.1-amd64-smp 
    Network:   Message: No Device data found. 
               IF-ID-1: wlan1 state: up mac: <filter> 
    Drives:    Local Storage: total: 133.70 GiB used: 6.33 GiB (4.7%) 
               ID-1: /dev/sda vendor: Samsung model: MZMPC128HBFU-000L1 size: 119.24 GiB 
               ID-2: /dev/sdb type: USB vendor: Toshiba model: TransMemory size: 14.45 GiB 
    Partition: ID-1: / size: 7.87 GiB used: 6.33 GiB (80.4%) fs: ext4 dev: /dev/sdb1 
               ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb2 
    Sensors:   System Temperatures: cpu: 48.0 C mobo: N/A 
               Fan Speeds (RPM): N/A 
    Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
               1: deb http://iso.mxrepo.com/antix/buster buster main nonfree
               Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
               1: deb http://ftp.gr.debian.org/debian/ buster-updates main contrib non-free
               Active apt repos in: /etc/apt/sources.list.d/debian.list 
               1: deb http://ftp.gr.debian.org/debian/ buster main contrib non-free
               2: deb http://security.debian.org/ buster/updates main contrib non-free
               Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
               1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
               No active apt repos in: /etc/apt/sources.list.d/onion.list 
               No active apt repos in: /etc/apt/sources.list.d/various.list 
    Info:      Processes: 176 Uptime: 22m Memory: 7.68 GiB used: 602.9 MiB (7.7%) Init: SysVinit runlevel: 5 Compilers: 
               gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36 
    
    #67250
    Member
    bertil
    Helpful
    Up
    0

    I followed the steps in the previous post but i am still stuck on:

    Err:2 http://iso.mxrepo.com/antix/bullseye bullseye InRelease                          
      The following signatures were invalid: EXPKEYSIG DB36CDF3452F0C20 antiX (antix repo) <repo@antixlinux.com>
    

    and

    N: Ignoring file 'debian-stable-updates.list.old' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
    W: GPG error: http://iso.mxrepo.com/antix/bullseye bullseye InRelease: The following signatures were invalid: EXPKEYSIG DB36CDF3452F0C20 antiX (antix repo) <repo@antixlinux.com>
    E: The repository 'http://iso.mxrepo.com/antix/bullseye bullseye InRelease' is not signed.
    N: Updating from such a repository can't be done securely, and is therefore disabled by default.
    N: See apt-secure(8) manpage for repository creation and user configuration details.'
    
    • This reply was modified 1 week, 4 days ago by bertil.
    • This reply was modified 1 week, 4 days ago by bertil.
    #67253
    Forum Admin
    anticapitalista
    Helpful
    Up
    0

    antiX-17 by default did not use buster repos, but stretch.
    You must have changed it.
    Read what the front page of this forum says about expired keys.

    Philosophers have interpreted the world in many ways; the point is to change it.

    antiX with runit - leaner and meaner.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.