apt upgrade/autoremove broke antix21 & apt-get

[Member PenguinGuy]

So apt-get wanted to..

Upgrade:
gconf-gsettings-backend libgtk-3-0 libgtk-3-common libgtk-3-bin

& then it autoremoved this (or partially tried).

Remove:
add-desktop-antix add-key-antix antix-goodies app-select-antix arandr at-spi2-core
audacious audacity automount-antix avahi-daemon bamfdaemon blueman bluetooth bluez
brave-browser celluloid cherrytree chromium chromium-l10n claws-mail
claws-mail-i18n claws-mail-pdf-viewer claws-mail-pgpinline claws-mail-pgpmime
claws-mail-smime-plugin claws-mail-tools clearlooks-phenix-theme clipit cmst code
connman control-centre-antix darktable dbus dbus-daemon dbus-x11
dconf-gsettings-backend dconf-service desktop-defaults-antix desktop-menu-antix
desktop-session-antix ds-mouse-antix elogind file-roller firefox-esr flatpak
galculator galternatives gconf2 geany gexec gir1.2-gtk-3.0 gir1.2-handy-1 gksu
glib-networking gnome-bluetooth gnome-disk-utility gnome-mahjongg gparted grsync
grubcc-antix gsettings-desktop-schemas gstreamer1.0-plugins-good guvcview ibus
ibus-data inkscape inxi-gui-antix ipp-usb kinit kio libappstream-glib8
libayatana-appindicator3-1 libayatana-ido3-0.4-0 libayatana-indicator3-7
libcanberra-gtk3-0 libcolord-gtk1 libexo-2-0 libgksu2-0 libgnome-bluetooth13
libgspell-1-2 libgtk-3-0 libgtk-3-0:i386 libgtk-3-bin libgtk-3-common libgtk-4-1
libgtk-4-common libgtkmm-3.0-1v5 libgtksourceview-3.0-1 libgtksourceviewmm-3.0-0v5
libhandy-1-0 libkf5authcore5 libkf5bookmarks5 libkf5configwidgets5
libkf5declarative5 libkf5iconthemes5 libkf5kiocore5 libkf5kiogui5
libkf5kiowidgets5 libkf5parts5 libkf5purpose-bin libkf5purpose5 libkf5quickaddons5
libkf5textwidgets5 libkf5wallet-bin libkf5xmlgui5 libnautilus-extension1a
libokular5core10 libosmgpsmap-1.0-1 libostree-1-1 libpam-elogind libplank-common
libplank1 libpolkit-qt5-1-1 libreoffice-gtk3 libsoup-3.0-0 libsoup2.4-1
libvte-2.91-0 libwebkit2gtk-4.1-0 libwnck-3-0 libwxgtk3.0-gtk3-0v5 libxfce4ui-2-0
libxfconf-0-3 locale-antix mirage notify-osd okular palemoon pdfarranger pkexec
plank policykit-1 polkitd qml-module-org-kde-kquickcontrolsaddons
qt5-gtk-platformtheme screenlight-antix screenshot-antix set-dpi-antix
set-screen-blank-antix simple-scan streamlight-antix synaptic
system-config-printer system-config-printer-common transmission-gtk udisks2
vivaldi-stable wallpaper-antix waterfox-current-kpe xfburn xfconf yad zenity zoom

Anyways, apt-get can no longer install things because all DNS now fail to resolve.

Is there a way to fix this without reinstalling everything?

I saw about maybe using wget to manually reinstall apt, but then it crashed & now I can’t even login.

Guess I just need to manually look over every single autoremove in the future instead of just scripting -y on it.

• This topic was modified 9 months, 3 weeks ago by PenguinGuy.
• This topic was modified 9 months, 3 weeks ago by PenguinGuy.
• This topic was modified 9 months, 3 weeks ago by PenguinGuy.

[Moderator christophe]

Helpful

Up

0

::

What is your
inxi -r ?

confirmed antiX frugaler, since 2019

[Member PenguinGuy]

Helpful

Up

0

::

This is going to be forever unsolved because I gave up & just did a clean install.

However now I’m back to installing Nvidia driver, but now this the 3rd time the instructions/solutions I figured out don’t work & it just hangs on a black screen. So now I reinstalled Antix 21 2x times so far today.

[Member sybok]

Helpful

Up

2

::

I had a bad experience with blindly accepting removal of what apt suggested for removal too; it was something completely different and less unfortunate.
I became more careful since then.

[Forum Admin anticapitalista]

Helpful

Up

3

::

You were warned

https://www.antixforum.com/forums/topic/dbus-upgrade-breaks-antix/

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

antiX with runit - leaner and meaner.

[Member PenguinGuy]

Helpful

Up

0

::

anticapitalista wrote:

You were warned

https://www.antixforum.com/forums/topic/dbus-upgrade-breaks-antix/

Is there a way to integrate future warnings into apt?

Like we call an update.sh & it will query for serious warnings before running apt-get?

I don’t really come on the forums & search the news every time I need to update something.

• This reply was modified 9 months, 3 weeks ago by PenguinGuy.

[Member sybok]

Helpful

Up

0

::

The script could be written along these lines:
0) Alias the script e.g. in your ‘~/.bashrc’.
1) Dry run:
sudo apt update && sudo apt dist-upgrade --dry-run | tee /tmp/apt_dry-run.tmp
2) Check/parse/manipulate the output file:
– get the ‘remove’ line (where the suggestions to remove start), remove all lines before
– inspect suggestions to be removed
– they should NOT contain (checked via grep -i 2>/dev/null) any of the strings in a BASH array defined at the top of the script
– if any detected, append to a new array
3)
If check passed:
run the ordinary ‘sudo apt dist-upgrade’
else:
print warning which of the not allowed strings detected
exit 0;

[Forum Admin anticapitalista]

Helpful

Up

1

::

When running sid/testing it is essential that user reads the output of apt dist-upgrade before pressing Enter.
Any automated alternatives will end in tears somewhere down the line.

Please note that antiX with sid/testing should only be used by experienced users.

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

antiX with runit - leaner and meaner.

[Member PenguinGuy]

Helpful

Up

0

::

sybok wrote:

The script could be written along these lines:
0) Alias the script e.g. in your ‘~/.bashrc’.
1) Dry run:
sudo apt update && sudo apt dist-upgrade --dry-run | tee /tmp/apt_dry-run.tmp
2) Check/parse/manipulate the output file:
– get the ‘remove’ line (where the suggestions to remove start), remove all lines before
– inspect suggestions to be removed
– they should NOT contain (checked via grep -i 2>/dev/null) any of the strings in a BASH array defined at the top of the script
– if any detected, append to a new array
3)
If check passed:
run the ordinary ‘sudo apt dist-upgrade’
else:
print warning which of the not allowed strings detected
exit 0;

I don’t know if it has to be this complex.

I’m thinking if a person is posting online in the forums, it would be easier for them to post somewhere a status to cURL & then a regex can be run against for a match (like ‘!upgrade’ or something like that).

So literally whoever is updating the warning could just write ‘!upgrade’ or delete it & not any other text so its easy & fast to update & maintain.

As for just general use, maybe having a list of critical antix components that can be blocked from autoremove might help. That way if you uninstall most of your apps, you can still use antix & reinstall them & fix your system.

Another simple idea is to have apt autoremove check for a certain # (like 15+) entries & then fail with a warning of suspicion (so if you wanted to continue you would have to manually autoremove.

[Member sybok]

Helpful

Up

1

::

can be blocked from autoremove might help

See https://www.tecmint.com/disable-lock-blacklist-package-updates-ubuntu-debian-apt/
Editing file ‘/etc/apt/apt.conf.d/01autoremove’, section ‘NeverAutoRemove’.

Beware that any custom edits may be over-ridden when ‘apt’ itself is upgraded (user is prompted to approve in such cases and it is possible to perform a merge).

[Member andyprough]

Helpful

Up

0

::

I did not get any of these upgrade options. In fact, I didn’t get any upgrade options at all yesterday or today for antiX 21.

[Forum Admin anticapitalista]

Helpful

Up

0

::

@andyprough – the upgrades are only for sid repo users.

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

antiX with runit - leaner and meaner.

[Member PenguinGuy]

Helpful

Up

0

::

sybok wrote:

can be blocked from autoremove might help

See https://www.tecmint.com/disable-lock-blacklist-package-updates-ubuntu-debian-apt/
Editing file ‘/etc/apt/apt.conf.d/01autoremove’, section ‘NeverAutoRemove’.

Beware that any custom edits may be over-ridden when ‘apt’ itself is upgraded (user is prompted to approve in such cases and it is possible to perform a merge).

Unsure if I want to actually change the apt, just use a script that checks entries before calling apt.

[Member iznit]

Helpful

Up

1

::

them to post somewhere a status to cURL

impossible to guarantee a “posted status” will be accurate for all users, worldwide, across 100?+ mirrors which may not be up to date

‘NeverAutoRemove’

This can breed a false sense of security. Breakage [[[or undesirable outcomes]]] caused by “unattended” or ” -y ” scripted apt update operations is probably inevitable, even without auto removals. Anyone wishing to “automate” better ought to include a system backup as a step in the automated process.

[Member PenguinGuy]

Helpful

Up

0

::

So here is the script that lets you limit the max packs of autoremove (just set maxPacks at the top). It doesn’t require sudo & is safe to test (just comment out the autoremove – y line).

This should solve the majority of autoremove issues.

Now I can create the upgrade curl script if someone has a server & format to update.

That would cover 90+% of issues without much work.

#!/bin/bash

maxPacks_i=10

delimiter_S=" installed, "

check_S="$(apt-get autoremove -s)"

check_S=$check_S$delimiter_S

check_A_S=()
while [[ $check_S ]]; do
 check_A_S+=( "${check_S%%"$delimiter_S"*}" )
 check_S=${check_S#*"$delimiter_S"}
done

check_S=${check_A_S[1]}

delimiter_S=" to remove"

check_S=$check_S$delimiter_S

check_A_S=()
while [[ $check_S ]]; do
 check_A_S+=( "${check_S%%"$delimiter_S"*}" )
 check_S=${check_S#*"$delimiter_S"}
done

check_S=${check_A_S[0]}

if (( check_S > 0)) && (( check_S < maxPacks_i )); then
  echo "AUTOREMOVING -- packs: $check_S / $maxPacks_i max."
  sudo apt-get autoremove -y
else
  echo "NO AUTOREMOVE -- packs: $check_S / $maxPacks_i max."
fi

• This reply was modified 9 months, 3 weeks ago by PenguinGuy.
• This reply was modified 9 months, 3 weeks ago by PenguinGuy.
• This reply was modified 9 months, 3 weeks ago by PenguinGuy.

[Author]

Posts