SliTaz Forum
You are not logged in.
Pages: 1
These 6 packages available for upgrade keep reappearing when I install them due to a dependency loop?
dropbear version 2020.81 does not get upgraded to 2022.82
slim version 1.3.5 does not get upgraded to 1.3.6
new build for busybox, fuse, libcap, ppp remains as available upgrade?
Messages when I select install in TazPanel:
WARNING! Dependency loop between "busybox-pam" and "busybox-pam".
WARNING! Dependency loop between "dropbear-pam" and "dropbear-pam".
WARNING! Dependency loop between "libcap-pam" and "libcap-pam".
How do i fix it?
[attachment=50950,3265]
Offline
Hi Ceel
I tried the slitaz live boot and removed the packages but it still didn't work?
tazpkg -r dropbear-pam --root=/media/3da9a31a-ba47-42b9-ac2b-c0ffc078c098/
tazpkg -r libcap-pam --root=/media/3da9a31a-ba47-42b9-ac2b-c0ffc078c098/
tazpkg -r ppp-pam --root=/media/3da9a31a-ba47-42b9-ac2b-c0ffc078c098/
tazpkg -r slim-pam --root=/media/3da9a31a-ba47-42b9-ac2b-c0ffc078c098/
/media/3da9a31a-ba47-42b9-ac2b-c0ffc078c098/bin/busybox: error while loading shared libraries: libpam.so.0: cannot open shared object file: No such file or directory
tazpkg -r busybox-pam --forced --root=/media/3da9a31a-ba47-42b9-ac2b-c0ffc078
c098/
sed: /var/lib/tazpkg/installed/busybox-pam/files.list: No such file or directory
[ Failed ]
Removing all files installed... [ Done ]
Busybox is not installed in the /media/3da9a31a-ba47-42b9-ac2b-c0ffc078c098. Exit.
tazpkg up --root=/media/3da9a31a-ba47-42b9-ac2b-c0ffc078c098/
Recharging repository "Main"
===============================================================
Checking... [ Done ]
Database timestamp: 01/21/2023 19:45
===============================================================
Repository "Main" is up to date.
Package Repository Version Status
===============================================================
busybox Main 1.31.1 New build
dropbear Main 2020.81 → 2022.83
fuse Main 3.10.5 New build
libcap Main 2.63 New build
ppp Main 2.4.7 New build
slim Main 1.3.5 → 1.3.6
===============================================================
You have 6 available upgrades (0 blocked)
401 installed packages scanned in 2s
Do you wish to install them now? (y/N) N
Leaving without any upgrades installed.
Offline
Hi Ravenslock,
To remove packages of an installation from a live session you must mount the partition of the full install in a directory; you cannot use the UUID with the [c]--root=[/c] option (this point is confusing in the Tazpkg manuel and I think --root=/mnt/sda6 should be replaced with --root=/mnt, the target (sda6 in the example) is a directory).
[c]pam[/c] was probably installed as a depend; at the first update that followed Tazpkg installed the [c]-pam[/c].
In this case you can remove these packages and even do it from the full install:
[*]First, check if [c]pam[/c] is still installed with [c]tazpkg info pam[/c]; if not, go to step 3
[*]Check if [c]pam[/c] is a depend of another package: [c]tazpkg rdepends pam[/c].
[*]Remove the [c]-pam[/c] packages
If [c]pam[/c] was'nt installed or required by another package, that all.
If [c]pam[/c] is required by another package, as root, add in the [c]/var/lib/tazpkg/blocked-packages.list[/c] all the [c]-pam[/c] packages:
[c]busybox-pam
cups-pam
cyrus-sasl-pam
dropbear-pam
enlightenment-pam
freeradius-pam
libcap-pam
netatalk-pam
openssh-pam
openvpn-pam
partimage-pam
perdition-pam
php-auth-pam
polkit-pam
ppp-pam
pure-ftpd-pam
samba-pam
screen-pam
slim-pam
sudo-pam[/c]
This will avoid at Tazpkg to re-install them.
Re-install [c]pam[/c]. At next update, maybe Tazpkg will warn you that some [c]-pam[/c] packages are blocked but it should update [c]busybox[/c], [c]dropbear[/c], [c]fuse[/c], [c]libcap[/c], [c]ppp[/c] and [c]slim[/c].
Offline
Not sure it is a good idea, wait before to remove packages.
Offline
tux@slitaz:~$ su root
root@slitaz:/home/tux# mount -vt ext4 /dev/sda1 /mnt/
mount: /dev/sda1 mounted on /mnt.
root@slitaz:/home/tux# tazpkg info pam --root=/mnt/
State : installed package
root@slitaz:/home/tux# tazpkg -r pam --root=/mnt/
The following packages depend on package "pam":
busybox-pam
dropbear-pam
libcap-pam
openssh-pam
ppp-pam
slim-pam
Remove package "pam" (1.2.0)? (y/N) y
root@slitaz:/home/tux# cat /var/lib/tazpkg/blocked-packages.list
busybox-pam
dropbear-pam
libcap-pam
openssh-pam
ppp-pam
slim-pam
root@slitaz:/home/tux# tazpkg up --root=/mnt/
Recharging repository "Main"
================================
Checking... [ Done ]
Database timestamp: 01/21/2023 19:45
================================
Repository "Main" is up to date.
Package Repository Version Status
================================
fuse Main 3.10.5 New build
libcap Main 2.63 New build
ppp Main 2.4.7 New build
slim Main 1.3.5 → 1.3.6
================================
You have 4 available upgrades (0 blocked)
400 installed packages scanned in 2s
Do you wish to install them now? (y/N) y
Package "fuse2-2.9.9" already in the cache
Thanks Ceel. All the packages reappearing is solved except for fuse.
Offline
Hello Ravenslock,
Good to know. And thank you for the feedback!
fuse Main 3.10.5 New build
.../...
Package "fuse2-2.9.9" already in the cache
Right, I forgot a step; same disease, same medicine:
tazpkg info fuse2
TazPkg information
.../...
Provide : fuse
.../...
→ remove (from Tazpanel) [c]fuse2[/c] then [c]fuse[/c] and reinstall [c]fuse2[/c].
Really strange that v.2 can provide v.3, doesn't it ???
but that's a while I removed it on my computer and I don't have any problems.
I edited my previous post because I wrote something wrong:
3. Remove pam: tazpkg -r pam (you cannot remove the [c]-pam[/c] packages as long as pam is installed).
This is not true. Remove [c]pam[/c] only if you want to remove the "non [c]-pam[/c]" packages after you removed the [c]-pam[/c].
You didn't reinstall [c]pam[/c]?
Offline
Hi Ceel, System is up-to-date. pam is installed and fuse issue is gone 
Dependency loop on packages resolved. Thanks.
Offline
Pages: 1
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.56 MiB (Peak: 1.77 MiB) ]