Dependency Loop on packages

SliTaz Forum » English Support » Packages

Dependency Loop on packages

(8 posts) (2 voices)

Started 1 year ago by Ravenslock
Latest reply from Ravenslock
This topic is resolved

Tags:

No tags yet.

Ravenslock

offline
Member
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?
Attachments
slitaz_packages.png (31.7 KB, 174 downloads) 1 year old
Posted 1 year ago #
Ceel

offline
Administrator

Hi Ravenslock,

Maybe an answer at your question: read the "Users become unusable" topic from here

Posted 1 year ago #
Ravenslock

offline
Member

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.

Posted 1 year ago #
Ceel

offline
Administrator
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 --root= 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).

pam was probably installed as a depend; at the first update that followed Tazpkg installed the -pam.
In this case you can remove these packages and even do it from the full install:
1. First, check if pam is still installed with tazpkg info pam; if not, go to step 3
2. Check if pam is a depend of another package: tazpkg rdepends pam.
3. Remove the -pam packages
If pam was'nt installed or required by another package, that all.

If pam is required by another package, as root, add in the /var/lib/tazpkg/blocked-packages.list all the -pam packages:
```
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
```
This will avoid at Tazpkg to re-install them.
Re-install pam. At next update, maybe Tazpkg will warn you that some -pam packages are blocked but it should update busybox, dropbear, fuse, libcap, ppp and slim.
Posted 1 year ago #
Ceel

offline
Administrator

Not sure it is a good idea, wait before to remove packages.

Posted 1 year ago #
Ravenslock

offline
Member

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.

Posted 1 year ago #
Ceel

offline
Administrator
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) fuse2 then fuse and reinstall fuse2.

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 -pam packages as long as pam is installed).

This is not true. Remove pam only if you want to remove the "non -pam" packages after you removed the -pam.
You didn't reinstall pam?
Posted 1 year ago #
Ravenslock

offline
Member

Hi Ceel, System is up-to-date. pam is installed and fuse issue is gone :)
Dependency loop on packages resolved. Thanks.

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.

Dependency Loop on packages

Attachments

Reply