Dev1 Galaxy Forum / [beowulf] Packages being held back.

Re: [beowulf] Packages being held back.

dummy@example.com (bgstack15) — Fri, 30 Aug 2019 14:12:24 +0000

Perusing http://deb.devuan.org/devuan-cd/, it appears that the answer is no. I'm a little surprised, frankly. I can't really keep straight all these silly debian/devuan version numbers. I wish they would just use actual numbers...

Re: [beowulf] Packages being held back.

dummy@example.com (sgage) — Thu, 29 Aug 2019 12:30:11 +0000

bgstack15 wrote:

I have the same problem, where elogind and related packages in my multiarch setup are being held back. This problem affects wine32 which depends on one of these. I also like using elogind versus consolekit which I think might also be related/affected.

I removed wine32 and its hangers-on, and the upgrade completed successfully. I only use wine32 for one program that isn't essential in daily use, so I'll just wait until this gets sorted.

This is a beowulf system updated from ascii. Is there a proper beowulf installer so I could try a clean install?

Re: [beowulf] Packages being held back.

dummy@example.com (bgstack15) — Tue, 20 Aug 2019 11:47:27 +0000

I have the same problem, where elogind and related packages in my multiarch setup are being held back. This problem affects wine32 which depends on one of these. I also like using elogind versus consolekit which I think might also be related/affected.

Re: [beowulf] Packages being held back.

dummy@example.com (sgage) — Mon, 19 Aug 2019 22:33:30 +0000

ralph.ronnquist wrote:

Perhaps it's due to the version disagreement of libuuid1:amd64 and libuuid1:i386 (in beowulf) (and in unstable).

Ah, perhaps. :amd64 is 2.32.1-0.12.32.1, while the upgrade candidate for :i386 is 2.32.1-0.12.33.1, and cascading dependencies takes care of the rest. Best to just wait for :amd64 to 'catch up'?

Re: [beowulf] Packages being held back.

dummy@example.com (ralph.ronnquist) — Mon, 19 Aug 2019 22:20:59 +0000

Perhaps it's due to the version disagreement of libuuid1:amd64 and libuuid1:i386 (in beowulf) (and in unstable).

[beowulf] Packages being held back.

dummy@example.com (sgage) — Mon, 19 Aug 2019 21:38:55 +0000

For the past week or two, I've been getting this:

# apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  elogind libblkid1:i386 libelogind0 libmount1:i386 libpam-elogind
  libuuid1:i386
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.

Is there a problem somewhere, or do I just have to wait for some dependency issue to be resolved?