Your message dated Fri, 29 Nov 2019 00:54:23 +0100 with message-id <20191128235423.wurg5wd5lfdgpnpm@function> and subject line Re: Bug#945800: libhwloc-plugins needs to be updated/transitioned to work with libhwloc15 as libhwloc5 is being removed/purged has caused the Debian Bug report #945800, regarding libhwloc-plugins needs to be updated/transitioned to work with libhwloc15 as libhwloc5 is being removed/purged to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 945800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945800 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libhwloc-plugins Version: 2.1.0+dfsg-2 Severity: normal Dear Maintainer, While updating today got hit by this bug - dpkg: libhwloc5:amd64: dependency problems, but removing anyway as you requested: libhwloc-plugins:amd64 depends on libhwloc5 (>= 1.11.13~). libhwloc-plugins:amd64 depends on libhwloc5 (<< 1.11.13A). libhwloc-plugins:amd64 depends on libhwloc5 (>= 1.11.13~). libhwloc-plugins:amd64 depends on libhwloc5 (<< 1.11.13A). So it would be nice if it works with libhwloc15 which AFAIK is supposed to take over the functions of libhwloc5. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (500, 'testing-debug'), (100, 'unstable-debug'), (100, 'experimental'), (100, 'unstable'), (50, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libhwloc-plugins depends on: ii libc6 2.29-3 ii libhwloc15 2.1.0+dfsg-2 ii libltdl7 2.4.6-11 ii libpciaccess0 0.14-1 ii libxml2 2.9.4+dfsg1-8 ii ocl-icd-libopencl1 [libopencl1] 2.2.12-2 libhwloc-plugins recommends no packages. libhwloc-plugins suggests no packages. -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C
--- End Message ---
--- Begin Message ---shirish शिरीष, le jeu. 28 nov. 2019 23:52:32 +0000, a ecrit: > At my end, I do have both the new packages. What I was talking about > is dpkg complaining . Ah, it's only a warning on your system, not actually making the upgrade failing? Then yes, dpkg does this, and it is harmless. It does happen when such condition happens, that's completely expected. > Perhaps the postinstall script or something still has the old > dependancy somewhere ? No, dpkg is just warning that some package will temporarily be unusable. Samuel
--- End Message ---
