SliTaz Forum

llev

Member

Registered: 2011-12-09

Posts: 568

Replacement packages (e.g. busybox-pam) put tazpkg in a deadlock

Hi,

Some packages come with variants (busybox/busybox-pam, libcomerr/libcomerr3, etc.). I did a massive update recently (I hadn't updated for months, shame on me), and now [c]tazpkg up[/c] shows:

[c]

busybox                  Main        1.23.2     → 1.27.2

cups                     Main        2.0.2      Reconstruit

...

[/c]

Indeed, [c]tazpkg -s busybox[/c] gives:

[c]

Paquets installés

--------------------------------------------------------------------------------

busybox                 1.23.2            système de base

busybox-pam             1.27.2            système de base

================================================================================

2 paquets installés trouvés pour « busybox »

Paquets disponibles

--------------------------------------------------------------------------------

busybox                 1.27.2            système de base

...

busybox-pam             1.27.2            système de base

...

[/c]

But [c]tazpkg -gi busybox --forced[/c] reinstalls [c]busybox-pam[/c] (of course), so, after this, tazpkg still wants to upgrade [c]busybox[/c] which remained at version 1.23.2!

[c]clean-cache[/c] didn't help. Is this due to me not updating for a long time (if so, what can I do to cure the problem?), or is it a bug in tazpkg?

R8

Member

Registered: 2015-08-20

Posts: 143

Re: Replacement packages (e.g. busybox-pam) put tazpkg in a deadlock

Hello,

I had a similar problem with other packages.

See the subject here:

http://forum.slitaz.org/topic/3-updates-remain-visible

I had to uninstall the packages concerned and a lot of dependencies and then reinstall everything. And it finally worked.

lexeii

Administrator

Registered: 2012-03-21

Posts: 1,853

Re: Replacement packages (e.g. busybox-pam) put tazpkg in a deadlock

Hi there,

My apologies.

It is long standing bug/feature of TazPkg embedded in its architecture.

Currently (and just like in few last years) no solution exists.

Only manual removing package from the TazPkg database of installing files will help.