Oops?! – cron upgrade to v3.0pl1-169.0ANTIX1 brings in systemd!

Forum Forums News Sid Upgraders Oops?! – cron upgrade to v3.0pl1-169.0ANTIX1 brings in systemd!

  • This topic has 13 replies, 4 voices, and was last updated Aug 22-10:25 pm by wildstar84.
Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • #114506
    Member
    wildstar84

      Just what the title says, upgrading from 165.0antix1 to 169.0antix1 will bring in systemd & libsystemd0.
      (so holding for now)

      Regards,

      Jim

      • This topic was modified 8 months ago by caprea. Reason: moved from "New Users" to "Sid Upgraders"
      • This topic was modified 8 months ago by caprea.
      #114522
      Member
      olsztyn

        Just what the title says, upgrading from 165.0antix1 to 169.0antix1 will bring in systemd & libsystemd0.

        I do not see this happening in my installations of antiX. Perhaps you might have a different composition of system that is causing this though…

        Live antiX Boot Options (Previously posted by Xecure):
        http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

        #114525
        Member
        Xunzi_23

          Unless below has been removed or is not present in /etc/apt/preferences.d/00systemd

          Package: *systemd*:any
          Pin: origin *
          Pin-Priority: -1

          systemd will not be pulled in.

          I have not experienced the reported problem. libsystemd0 is not to be found on any of my
          antiX setups.

          #114533
          Forum Admin
          anticapitalista

            I have upgraded 2 installed sid, one frugal sid and one frugal testing and systemd (or elogind) did not get brought in

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

            antiX with runit - leaner and meaner.

            #114563
            Member
            wildstar84

              Sorry, WRONG GROUP! – I’m running antiX Testing(Trixie), not sid (which is where the pbm happened)!

              
              $>inxi -r
              Repos:
                No active apt repos in: /etc/apt/sources.list
                Active apt repos in: /etc/apt/sources.list.d/antix.list
                  1: deb http://la.mxrepo.com/antix/testing/ testing nosystemd main nonfree
                No active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list
                No active apt repos in: /etc/apt/sources.list.d/buster-backports.list
                No active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
                Active apt repos in: /etc/apt/sources.list.d/debian.list
                  1: deb http://ftp.us.debian.org/debian/ testing non-free-firmware contrib main
                  2: deb http://security.debian.org/ testing-security main contrib non-free
                No active apt repos in: /etc/apt/sources.list.d/mx.list
                No active apt repos in: /etc/apt/sources.list.d/onion.list
                Active apt repos in: /etc/apt/sources.list.d/various.list
                  1: deb http://liquorix.net/debian/ testing main
              

              Also seem to be having trouble adding a screenshot to this, so if not here, then I failed.

              • This reply was modified 8 months ago by wildstar84. Reason: Add inxi & screenshot
              Attachments:
              #114567
              Forum Admin
              anticapitalista

                My frugal testing upgraded without issues.
                Can you try this from the terminal and post the output before you agree to the upgrade

                sudo apt update && sudo apt dist-upgrade

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

                antiX with runit - leaner and meaner.

                #114579
                Member
                wildstar84

                  Ok, the only interesting thing out of apt update is:

                  N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://liquorix.net/debian testing InRelease' doesn't support architecture 'i386'

                  and apt dist-upgrade would do:

                  Reading package lists... Done
                  Building dependency tree... Done
                  Reading state information... Done
                  Calculating upgrade... Done
                  The following packages were automatically installed and are no longer required:
                    libavfilter7 libavformat58 libicu57 libpoppler102 libpoppler118
                    libpostproc55 libpostproc56 libswscale5 libswscale6 libxcb-util0
                  Use 'apt autoremove' to remove them.
                  The following packages will be REMOVED:
                    coinor-libcbc3 linux-headers-5.12.0-19.4-liquorix-amd64
                    linux-headers-5.17.0-15.1-liquorix-amd64
                    linux-headers-5.18.0-16.2-liquorix-amd64
                    linux-headers-5.19.0-12.1-liquorix-amd64
                    linux-headers-5.19.0-17.2-liquorix-amd64
                    linux-headers-6.0.0-10.1-liquorix-amd64
                    linux-headers-6.1.16-1-liquorix-amd64 linux-headers-6.2.13-1-liquorix-amd64
                    linux-image-5.12.0-19.4-liquorix-amd64
                    linux-image-5.17.0-15.1-liquorix-amd64
                    linux-image-5.18.0-16.2-liquorix-amd64
                    linux-image-5.19.0-12.1-liquorix-amd64
                    linux-image-5.19.0-17.2-liquorix-amd64 linux-image-6.0.0-10.1-liquorix-amd64
                    linux-image-6.1.16-1-liquorix-amd64 linux-image-6.2.13-1-liquorix-amd64
                  The following NEW packages will be installed:
                    coinor-libcbc3.1 lib2geom1.2.0 libjim0.81 libsystemd-shared libsystemd0
                    linux-headers-6.4.11-2-liquorix-amd64 linux-image-6.4.11-2-liquorix-amd64
                    python3-attr python3-exceptiongroup python3-h11 python3-outcome
                    python3-sniffio python3-sortedcontainers python3-trio python3-trio-websocket
                    python3-typing-extensions python3-wsproto systemd systemd-dev
                  The following packages have been kept back:
                    dh-python droopy-antix
                  The following packages will be upgraded:
                    aaphoto acpid afterstep afterstep-data alsamixergui alsaplayer-alsa
                    audacious-plugins bash bc bison br2684ctl bs2b-ladspa coinor-libcoinmp1v5
                    cron cron-daemon-common dcraw dctrl-tools dillo dnscrypt-proxy dosbox dzen2
                    fim flent geany ghostscript ghostscript-x gimp-plugin-registry
                    gir1.2-gdkpixbuf-2.0 gir1.2-gtksource-3.0 gir1.2-ibus-1.0 graphviz grsync
                    gtk2-engines gtk2-engines-murrine gtkam gtklp guvcview gv hardinfo
                    herbstluftwm inkscape intel-microcode kbd kid3-cli kid3-core ldnsutils
                    libafterimage0 libafterstep1 libann0 libasyncns0 libatm1 libaudiofile1
                    libbabeltrace1 libbison-dev libbrotli-dev libbrotli1 libcap-ng0 libcbor0.8
                    libcdt5 libcgraph6 libclutter-gtk-1.0-0 libdatrie-dev libdatrie1 libde265-0
                    libdjvulibre21 libdockapp-dev libdockapp3 libe-book-0.1-1 libexif-gtk5
                    libexif12 libffmpegthumbnailer4v5 libflickcurl0 libfuse2 libgdk-pixbuf-2.0-0
                    libgdk-pixbuf-2.0-dev libgdk-pixbuf2.0-bin libgdl-3-5 libgpgme11 libgpgmepp6
                    libgs-common libgs10 libgs10-common libgtkmm-2.4-1v5 libgtksourceview-3.0-1
                    libgts-0.7-5 libguvcview-2.1-2 libgvc6 libgvpr2 libibus-1.0-5
                    libibus-1.0-dev libiec61883-0 liblab-gamut1 libldns3 liblockfile-bin
                    liblockfile1 libmad0 libmanette-0.2-0 libmspub-0.1-1 libnetfilter-conntrack3
                    libnewt0.52 libnl-3-200 libnl-genl-3-200 libnl-route-3-200 libntfs-3g89
                    libpam-gnome-keyring libpathplan4 libpcap0.8 libplist3 libprotobuf-c1
                    libpython3-stdlib libqxp-0.0-0 librabbitmq4 librcd0 libresid-builder0c2a
                    libsdl-image1.2 libsdl-net1.2 libsdl-sound1.2 libsdl1.2debian libseccomp2
                    libshout3 libsidplay2 libsidutils0 libsndifsdl2-dev libsndio-dev libsndio7.0
                    libspatialaudio0 libstartup-notification0 libstfl0 libtag-extras1 libtheora0
                    libtotem-plparser18 libuniconf4.6 libvidstab1.1 libvisio-0.1-1 libvte9
                    libwpd-0.10-10 libwvstreams4.6-base libwvstreams4.6-extras libx264-164
                    libx265-199 libxaw3dxft6 libxcb-keysyms1 libxcb-render-util0 libxcb-util0
                    libxext-dev libxext6 libxi-dev libxi6 libxrandr-dev libxrandr2 libzip4
                    libzmf-0.0-0 linux-headers-liquorix-amd64 linux-image-liquorix-amd64 login
                    lp-solve lshw lua-socket lxappearance mbr most mp3blaster mp3wrap mplayer
                    nmap nmap-common ntfs-3g ntpdate ntpsec-ntpdate ntpsec-ntpdig passwd
                    patchelf python3 python3-cffi-backend python3-minimal python3-ntp
                    python3-pkg-resources python3-setuptools python3-sip python3-streamlink
                    reiser4progs spacefm startpar streamlink usb-modeswitch vorbis-tools wget
                    whiptail wmcalc wmctrl wmmoonclock x11-xserver-utils x265 xbacklight xfburn
                    xgalaga++ xloadimage xpaint xpdf xplanet xserver-xorg-input-evdev
                    xserver-xorg-input-mouse xserver-xorg-input-synaptics yad
                  204 upgraded, 19 newly installed, 17 to remove and 2 not upgraded.
                  Need to get 215 MB/216 MB of archives.
                  After this operation, 2,396 MB disk space will be freed.
                  Do you want to continue? [Y/n] n
                  Abort.

                  Note the systemd additions in lines 24 and 28!

                  #114611
                  Forum Admin
                  anticapitalista

                    Unhold any held packages and try again

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

                    antiX with runit - leaner and meaner.

                    #114710
                    Member
                    wildstar84

                      apt-mark showhold, dpkg -l | grep “^hi”, and dpkg –get-selections | grep “\<hold$” show no held packages. The 2 mentioned (dh-python & droopy-antix) are due to still having python2 (along with python3) installed in order to keep the non-java version of ptktk (et. al.) installed.

                      I do not believe this has anything to do with upgrading cron as it is only updating these two (cron and cron-daemon-common) that cause an issue (no other recent updates present with this issue), and pbly. only the latter, as the latest vsn SPECIFICALLY depends on systemd (see attached), whereas my current vsn (also only recently updated – one week ago: v3.0pl1-163.0antix1) does not!

                      Please diff this (good) vsn. of cron-daemon-common with your latest (v169.0) to determine what precisely has changed. I believe there is likely a mistake/typo/oops there.

                      Thanks,

                      Jim

                      #114713
                      Forum Admin
                      anticapitalista

                        You are the only one to have this upgrade issue so you must have something else that is dragging in systemd.
                        What do you get if you try to upgrade cron only?

                        • This reply was modified 7 months, 4 weeks ago by anticapitalista.

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

                        antiX with runit - leaner and meaner.

                        #114715
                        Member
                        wildstar84

                          I get same following (see image) if I try to upgrade either one individually (or together – cron depends on cron-daemon-common, which IS the problem-child here). This is also true if trying with apt-get as well.

                          Attachments:
                          #114717
                          Forum Admin
                          anticapitalista

                            Wonder why you’re getting this and others aren’t.

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

                            antiX with runit - leaner and meaner.

                            #114718
                            Forum Admin
                            anticapitalista

                              Try installing opensysusers

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

                              antiX with runit - leaner and meaner.

                              #114720
                              Member
                              wildstar84

                                That seems to have made the 2 cron packages willing to update without systemd foo, but I ended up having to run the script manually, which did not do what the newly-installed /etc/init.d/opensysusers was supposed to do (run /usr/bin/opensysusers-sysusers, which is supposed to create (touch) /run/opensysusers/ok, as there was no subdirectory /run/opensysusers/ on this system and the job did not include a mkdir, so I did that manually and touched the ok file (as root), then reran synaptic, which now does not complain. Perhaps “everyone else” already had this package installed, but nothing has ever brought this one in for me (yet), perhaps it’s one of the beta packages that I haven’t updated yet, pending a production release.

                                Either way, it looks like this now needs to be made a dependency of cron-daemon-common (instead of systemd*).

                                Please note that I’ve had this system installed since around 2015 or so and been keeping up-to-date through Buster, Bookworm & now Trixie (as a rolling “testing” system) selectively updating all packages as production versions are released (nearly daily), and betas too (as needed), which has worked very well for me over the years with only the occasional “glitch” such as this (and almost always caught by me before upgrading something that later forced a trip to snapshot.debian.org to roll back). I know “everyone else” generally uses dist-upgrade, but I’ve seen too many broken systems & reinstalls reported by others (not just sid, but not lately either) over the years that cause me to stick with this method, as I’ve invested way too much time customizing and tuning my system to now have to do a full reinstall (and I guess I’m a bit of a control-freak when it comes to my computer). If I were running stable, perhaps I’d be more confident running dist-upgrade and if sid, I’d have too, but I feel I need to be a bit more micromanaging over testing. Heck, I even sometimes read the changelogs when updating (when available) if it’s a major package I depend on or has a known (to me) history of regressions before updating. I Could do a reinstall if I had too, but it’d take me pbly. a week to get everything back working correctly! 😉

                                Cheers & thanks again for working with me to get this resolved,

                                Jim

                                • This reply was modified 7 months, 4 weeks ago by wildstar84.
                              Viewing 14 posts - 1 through 14 (of 14 total)
                              • You must be logged in to reply to this topic.