Upgrading antiX – don’ts

Forum Forums General Tips and Tricks Upgrading antiX – don’ts

  • This topic has 39 replies, 22 voices, and was last updated May 14-5:11 pm by Brian Masinick.
Viewing 10 posts - 31 through 40 (of 40 total)
  • Author
    Posts
  • #105328
    Member
    sybok

      @scruffyeagle:
      Not sure if this is the correct thread/topic where to place your post.
      Discussed many times on antiX forum, the antiX’ description displayed in ‘inxi’ does not change because upgrading from older versions may keep “stuff” (e.g. configuration and packages) not (necessarily) included in the newer ones.
      Now, you have have some clues in the ‘base’ part giving the codename of Debian used, i.e. ‘bullseye’.
      Both antiX 21 and antiX 22 are Debian 11, a.k.a. bullseye, based; that’s why there is a shared link to their packages http://antixlinux.com/antix-21-22-packages/ .
      By keeping your system up-to-date with the updates/upgrades (without modifying the files in ‘/etc/apt/sources.list.d/’), you got antiX 22 — more or less (see above remark about the “stuff”) — from antiX 21.

      BTW, antiX 23 will be Debian 12, a.k.a. bookworm, based.

      #109599
      Member
      millerebonds

        Hello,

        I tried to upgrade, I have this error message…

        I prefer to ask before too make brutal choices ,o)

        $ sudo apt-get upgrade --fix-missing
        Lecture des listes de paquets... Fait
        Construction de l'arbre des dépendances... Fait
        Lecture des informations d'état... Fait      
        Calcul de la mise à jour... Fait
        Les paquets suivants seront mis à jour :
          cli-shell-utils ppp python3-cupshelpers system-config-printer
          system-config-printer-common system-config-printer-udev wallpaper-antix
          xserver-common xserver-xorg-core yt-dlp zzzfm zzzfm-common
        12 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
        5 partiellement installés ou enlevés.
        Il est nécessaire de prendre 5 939 ko/6 093 ko dans les archives.
        Après cette opération, 2 350 ko d'espace disque seront libérés.
        Souhaitez-vous continuer ? [O/n] O
        Err :1 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 ppp amd64 2.4.9-1+1.0nosystemd2
          403  Forbidden [IP : 132.227.74.17 80]
        Ign :2 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 system-config-printer all 1.5.18-1.0nosystemd1
        Ign :3 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 system-config-printer-common all 1.5.18-1.0nosystemd1
        Ign :4 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 python3-cupshelpers all 1.5.18-1.0nosystemd1
        Err :5 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 system-config-printer-udev amd64 1.5.18-1.0nosystemd1
          403  Forbidden [IP : 132.227.74.17 80]
        Ign :6 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/main amd64 wallpaper-antix all 0.6.15
        Ign :7 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 xserver-common all 2:1.20.11-1.0nosystemd3
        Err :8 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 xserver-xorg-core amd64 2:1.20.11-1.0nosystemd3
          403  Forbidden [IP : 132.227.74.17 80]
        Ign :9 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/main amd64 yt-dlp all 2023.03.04-1mx21+1
        Err :10 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/main amd64 zzzfm amd64 1.0.7-11
          403  Forbidden [IP : 132.227.74.17 80]
        Ign :11 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/main amd64 zzzfm-common all 1.0.7-11
        Err :2 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 system-config-printer all 1.5.18-1.0nosystemd1
          403  Forbidden [IP : 132.227.74.17 80]
        Err :3 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 system-config-printer-common all 1.5.18-1.0nosystemd1
          403  Forbidden [IP : 132.227.74.17 80]
        Err :4 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 python3-cupshelpers all 1.5.18-1.0nosystemd1
          403  Forbidden [IP : 132.227.74.17 80]
        Err :6 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/main amd64 wallpaper-antix all 0.6.15
          403  Forbidden [IP : 132.227.74.17 80]
        Err :7 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 xserver-common all 2:1.20.11-1.0nosystemd3
          403  Forbidden [IP : 132.227.74.17 80]
        Err :9 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/main amd64 yt-dlp all 2023.03.04-1mx21+1
          403  Forbidden [IP : 132.227.74.17 80]
        Err :11 http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye bullseye/main amd64 zzzfm-common all 1.0.7-11
          403  Forbidden [IP : 132.227.74.17 80]
        (Lecture de la base de données... 177983 fichiers et répertoires déjà installés.)
        Préparation du dépaquetage de .../cli-shell-utils_0.4.9_all.deb ...
        Dépaquetage de cli-shell-utils (0.4.9) sur (0.4.3) ...
        dpkg-deb (sous-processus) : decompressing archive '/var/cache/apt/archives/cli-shell-utils_0.4.9_all.deb' (size=153652) member 'data.tar' : erreur LZMA : les données compressées sont corrompues
        dpkg-deb: erreur: <decompress> subprocess returned error exit status 2
        dpkg: erreur de traitement de l'archive /var/cache/apt/archives/cli-shell-utils_0.4.9_all.deb (--unpack) :
         impossible de copier les données extraites pour « ./usr/share/locale/es_ES/LC_MESSAGES/cli-shell-utils.mo » vers « /usr/share/locale/es_ES/LC_MESSAGES/cli-shell-utils.mo.dpkg-new » : fin de fichier ou de flux inattendue
        Des erreurs ont été rencontrées pendant l'exécution :
         /var/cache/apt/archives/cli-shell-utils_0.4.9_all.deb
        E: Impossible de récupérer http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye/pool/nosystemd/p/ppp/ppp_2.4.9-1%2b1.0nosystemd2_amd64.deb  403  Forbidden [IP : 132.227.74.17 80]
        E: Impossible de récupérer http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye/pool/nosystemd/s/system-config-printer/system-config-printer_1.5.18-1.0nosystemd1_all.deb  403  Forbidden [IP : 132.227.74.17 80]
        E: Impossible de récupérer http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye/pool/nosystemd/s/system-config-printer/system-config-printer-common_1.5.18-1.0nosystemd1_all.deb  403  Forbidden [IP : 132.227.74.17 80]
        E: Impossible de récupérer http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye/pool/nosystemd/s/system-config-printer/python3-cupshelpers_1.5.18-1.0nosystemd1_all.deb  403  Forbidden [IP : 132.227.74.17 80]
        E: Impossible de récupérer http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye/pool/nosystemd/s/system-config-printer/system-config-printer-udev_1.5.18-1.0nosystemd1_amd64.deb  403  Forbidden [IP : 132.227.74.17 80]
        E: Impossible de récupérer http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye/pool/main/w/wallpaper-antix/wallpaper-antix_0.6.15_all.deb  403  Forbidden [IP : 132.227.74.17 80]
        E: Impossible de récupérer http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye/pool/nosystemd/x/xorg-server/xserver-common_1.20.11-1.0nosystemd3_all.deb  403  Forbidden [IP : 132.227.74.17 80]
        E: Impossible de récupérer http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye/pool/nosystemd/x/xorg-server/xserver-xorg-core_1.20.11-1.0nosystemd3_amd64.deb  403  Forbidden [IP : 132.227.74.17 80]
        E: Impossible de récupérer http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye/pool/main/y/yt-dlp/yt-dlp_2023.03.04-1mx21%2b1_all.deb  403  Forbidden [IP : 132.227.74.17 80]
        E: Impossible de récupérer http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye/pool/main/z/zzzfm/zzzfm_1.0.7-11_amd64.deb  403  Forbidden [IP : 132.227.74.17 80]
        E: Impossible de récupérer http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/antix/bullseye/pool/main/z/zzzfm/zzzfm-common_1.0.7-11_all.deb  403  Forbidden [IP : 132.227.74.17 80]
        E: Sub-process /usr/bin/dpkg returned an error code (1)
        #115339
        Member
        tosim

          Re: Upgrading Version
          Will this work to upgrade antix22,32b to antix23(sudo apt update && sudo apt dist-upgrade)?
          Thank you.

          #115340
          Forum Admin
          anticapitalista

            Re: Upgrading Version
            Will this work to upgrade antix22,32b to antix23(sudo apt update && sudo apt dist-upgrade)?
            Thank you.

            Read this post –

            https://www.antixforum.com/forums/topic/antix-21-22-to-antix-23/

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

            antiX with runit - leaner and meaner.

            #132028
            Member
            spaceman

              I hate to do anything I really don’t need to do, so I thought I’d share with my fellow antiXers that use Wine Staging.

              I have the Wine staging repo enabled in my sources. I’ve done many, many dist-upgrades with this repo enabled without issues. anticapilista is probably right though, you should disable all third party repos before upgrading, but I have never had an issue (lucky me). Your mileage may vary. If you decide to do as I do I can’t support you if does all go shape of pear. The antiX guys can’t be expected to either if you do decide to go maverick.

              So it’s your choice and be warmed.

              ~ ASUS ROG Crosshair VIII Hero ~ AMD Ryzen 7 3700X 8-Core ~ Corsair Dominator Platinum 32 GB RAM ~ M.2 SSD Samsung NVMe Evo 970 Plus 500GB ~ SSD Samsung Evo 860 500GB ~ NVIDIA Geforce GTX 1650 Super ~

              Between social reforms and revolution there exists for the social democracy an indissoluble tie. The struggle for reforms is its means; the social revolution, its aim.

              #142096
              Member
              GandalfTheWhite

                1. Do not dist-upgrade any version of antiX using any Debian backports repos since it may cause some apps to fail to install correctly.
                If you do, you get to pick up the pieces and waive any support.
                This is also Debian’s recommendation.

                2. Do not ‘google’ and blindly implement any random ‘advice’ on antiX. Ask for help in the forums.

                3. Do not add third party repos such as Ubuntu ppa.

                4. Use the Package Installer app first to install popular applications such as google-chrome, wine etc. This app is there for a reason.

                5. Do not enable the multimedia repo per default, and of course do not perform a dist-upgrade while it is enabled.
                This is also Debian’s recommendation.

                So … what should I do if I did all those steps? am I going to a corner to cry? Do not tell me that I must format D:

                #142097
                Member
                GandalfTheWhite

                  1. Do not dist-upgrade any version of antiX using any Debian backports repos since it may cause some apps to fail to install correctly.
                  If you do, you get to pick up the pieces and waive any support.
                  This is also Debian’s recommendation.

                  2. Do not ‘google’ and blindly implement any random ‘advice’ on antiX. Ask for help in the forums.

                  3. Do not add third party repos such as Ubuntu ppa.

                  4. Use the Package Installer app first to install popular applications such as google-chrome, wine etc. This app is there for a reason.

                  5. Do not enable the multimedia repo per default, and of course do not perform a dist-upgrade while it is enabled.
                  This is also Debian’s recommendation.

                  #142286
                  Moderator
                  caprea

                    So … what should I do if I did all those steps?

                    you get to pick up the pieces

                    #142287
                    Member
                    PPC

                      So … what should I do if I did all those steps? am I going to a corner to cry? Do not tell me that I must format D:

                      anticapitalista wrote:

                      you get to pick up the pieces

                      It’s the same thing that happens when you do something you should not do, no matter what OS you are using- if the OS gets broken, you have to fix it. Don’t think that only happens in Linux. If you hack your way through the Windows Registry or install software that breaks that OS, you end up holding it’s pieces. It’s your computer, you messed up the OS, you do what you want with the pieces that you got when it broke.
                      If it breaks, usually no “format” is required. There are multiple things you can try to fix what you broke. But usually the faster solution is just reinstalling. Reinstalling antiX is not a painful, long process, like in other OSes. Even on the slowest hardware available, you’ll be up and running in less than 30 minutes. On modern hardware? Probably in 10 minutes or so.
                      If you want to mess around changing your system, probably the best advice would be having a different partition (ideally a different drive, even) to store all your documents and important files, so you lose nothing if you have to reinstall. The “usual” solution is, when you install antiX for the first time, have the “home” folder on it’s own partition. This is sometimes ideal (if you reinstall antiX, since reinstalling does not mess with your home folder), you end up with a pristine OS that includes all the documents and files that you had before reinstalling… and also the same configuration files. That is a blessing, most of the time, but can be a curse, if when you messed up the OS, you also messed up, for example, the Window Manager configuration files. So I suppose the safest best would be always having a “Documents” partition with all your important data (there are ways of linking the Downloads, Documents, ext folders in your home to point to another partition). Also ALWAYS back up important stuff to an external drive, so even if you mess up during the install process and wipe out your “Documents” or “Home” partition, you can restore all your data…

                      Linux gives you freedom- not just from paying for your OS, but also from being spied on, tracked, and not being able to do what you want in your system. You want to change Window Managers? You are free to do it. You want to place the toolbar on the top of the screen? You are free to do that. You want to mess up your repositories, you are free to do that too. You want to wipe out all your data? That would be dumb, but you are free to do that too… Linux does not treat users as dumb people that don’t know what they are doing. Some people complain about that- they have too much freedom and can damage their OS.

                      P.

                      #142339
                      Moderator
                      Brian Masinick

                        To ANYONE who will read and consider a very reasonable approach:

                        With antiX we have multiple ways that you can quickly and efficiently make copies of files OR
                        the complete system.

                        First we have things like Disk-Recovery; that can be found in the “Package Installer” in the “Disks” category.
                        Standard UNIX and Linux tools, also available in antiX include dd, tar, cpio and other mechanisms, which can be used by industrious individuals to build their own backup and recovery strategy.

                        Under “Utility” in the “Package Installer” there is also Clonezilla, which can be used to “clone and restore disks and partitions”.

                        Finally, (and I’ve made you WAIT for this one); it’s my personal favorite, something unique to antiX and distributions that share with antiX – ISO Snapshot and Live USB Maker. HERE is what I do with these: first, after I install my new system, I tend to save prior configurations in multiple places – IF I’m on a system with multiple existing partitions, I can copy my home directory structure, which includes the shell scripts and personal tools that I’ve put together, including my own personal alias definitions, bash script functions, and more; many of these I use for fast, day to day maintenance.

                        Once I copy the stuff I want, including wallpaper appearance and my collection of scripts, I use the ISO Snapshot. This effectively BACKS up the system! Once I do this, in order to SAVE the backup, I put it on a USB Flash Drive. I keep a plain Flash Drive containing each release in case I ever want or need to reinstall; then I create EXTRA Flash Drives that contain the personal snapshots; these make an effective backup. Because I use plenty of cloud-based storage, that is yet another mechanism, so my three-pronged strategy for getting back to my favorite configurations are:

                        1) use multiple partitions and liberally copy between them; I also have multiple systems in the event of any single system failure.

                        2) External, password protected storage – I currently use cloud-based storage for this.

                        3) Various combinations of ISO Snapshot and Live USB Maker (and dd read-only copies if necessary).

                        To summarize, no one single point of failure; even catastrophic hardware failure will not completely eliminate access; only complete destruction of all of my systems would do that; in that case the cloud based storage and/or the Flash Drive (or OLDER CDs and DVDs) would give me many more ways to get something quickly operational.

                        --
                        Brian Masinick

                      Viewing 10 posts - 31 through 40 (of 40 total)
                      • You must be logged in to reply to this topic.