Package: libboost1.83-dev Version: 1.83.0-2 Severity: normal Dear Maintainer,
after installing libboost-all-dev I can't perform an upgrade anymore. On 2023-12-27 I installed libboost-all-dev and removed everything from previous boost versions without getting an error or even a warning: >From /var/log/apt/history: """ Start-Date: 2023-12-27 14:20:04 Commandline: apt-get install libboost-all-dev ... Start-Date: 2023-12-27 14:23:48 Commandline: apt-get autoremove ... Start-Date: 2023-12-27 14:34:28 Commandline: apt-get remove libboost-filesystem1.74.0 libboost-iostreams1.74.0 libboost-thread1.74.0 ... Start-Date: 2023-12-27 14:23:48 Commandline: apt-get autoremove ... Start-Date: 2023-12-27 14:34:28 Commandline: apt-get remove libboost-filesystem1.74.0 libboost-iostreams1.74.0 libboost-thread1.74.0 ... Start-Date: 2023-12-27 14:41:09 Commandline: apt-get autoremove """ ~# apt-get update && apt-get upgrade Get:1 http://download.opensuse.org/repositories/home:/hawkeye116477:/waterfox/Debian_Unstable InRelease [1,594 B] Hit:2 http://security.debian.org testing-security InRelease Get:3 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_10 InRelease [1,547 B] Hit:4 https://noone.org/conkeror-nightly-debs sid InRelease Hit:5 https://deb.opera.com/opera-stable stable InRelease Hit:6 http://packages.microsoft.com/repos/code stable InRelease Hit:8 https://dl.winehq.org/wine-builds/debian trixie InRelease Hit:9 https://updates.signal.org/desktop/apt xenial InRelease Hit:10 http://ftp.de.debian.org/debian sid InRelease Hit:7 https://debian.qgis.org/debian-nightly sid InRelease Fetched 3,141 B in 1s (3,176 B/s) Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libboost1.83-dev : Conflicts: libboost1.81-dev but 1.81.0-7+b1 is to be installed E: Broken packages ------------------------- additional information: ~# apt-cache policy libboost1.83-dev libboost1.83-dev: Installed: 1.83.0-2 Candidate: 1.83.0-2 Version table: *** 1.83.0-2 500 500 http://ftp.de.debian.org/debian sid/main amd64 Packages 100 /var/lib/dpkg/status ~# apt-cache policy libboost1.81-dev libboost1.81-dev: Installed: (none) Candidate: 1.81.0-7+b1 Version table: 1.81.0-7+b1 500 500 http://ftp.de.debian.org/debian sid/main amd64 Packages Actually I don't have a single package from boost1.81 or earlier installed. All installed boost-packages contain 83: ~# dpkg -l *boost* |grep "^ii" |grep -v 83 ~# ------------------------- Trying a dist-upgrade would seemingly fix the libboost issue. At least the "E: Broken packages" doesn't appear there. However, dry-running it (apt-get -s dist-upgrade), reveals the process would remove the package initscripts. It seems too risky to me to do so. Can I even be sure the systemwould come up? (Both /usr/sbin/init and /sbin/init are symlinks to /lib/systemd/systemd, so I assume I'm on systemd.) Since I'm not a weathered sysadmin I'm not sure whether I'd be able to handle a fully dysfunctional system. Can you please advise me on how to proceed? Thanks and cheers Harald PS: reportbug created this message but tried to send it with sendmail (not configured for remote sending)- So I reassembled the email from /var/spool/exim4 I hope I didn't miss anything important. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.8-amd64 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libboost1.83-dev depends on: ii libstdc++-13-dev 13.2.0-9 libboost1.83-dev recommends no packages. Versions of packages libboost1.83-dev suggests: ii libboost-atomic1.83-dev 1.83.0-2 ii libboost-chrono1.83-dev 1.83.0-2 ii libboost-container1.83-dev 1.83.0-2 ii libboost-context1.83-dev 1.83.0-2 pn libboost-contract1.83-dev <none> ii libboost-coroutine1.83-dev 1.83.0-2 ii libboost-date-time1.83-dev 1.83.0-2 ii libboost-exception1.83-dev 1.83.0-2 ii libboost-fiber1.83-dev 1.83.0-2 ii libboost-filesystem1.83-dev 1.83.0-2 ii libboost-graph-parallel1.83-dev 1.83.0-2 ii libboost-graph1.83-dev 1.83.0-2 ii libboost-iostreams1.83-dev 1.83.0-2 ii libboost-json1.83-dev 1.83.0-2 ii libboost-locale1.83-dev 1.83.0-2 ii libboost-log1.83-dev 1.83.0-2 ii libboost-math1.83-dev 1.83.0-2 ii libboost-mpi-python1.83-dev 1.83.0-2 ii libboost-mpi1.83-dev 1.83.0-2 ii libboost-nowide1.83-dev 1.83.0-2 ii libboost-numpy1.83-dev 1.83.0-2 ii libboost-program-options1.83-dev 1.83.0-2 ii libboost-python1.83-dev 1.83.0-2 ii libboost-random1.83-dev 1.83.0-2 ii libboost-regex1.83-dev 1.83.0-2 ii libboost-serialization1.83-dev 1.83.0-2 ii libboost-stacktrace1.83-dev 1.83.0-2 ii libboost-system1.83-dev 1.83.0-2 ii libboost-test1.83-dev 1.83.0-2 ii libboost-thread1.83-dev 1.83.0-2 ii libboost-timer1.83-dev 1.83.0-2 ii libboost-type-erasure1.83-dev 1.83.0-2 ii libboost-url1.83-dev 1.83.0-2 ii libboost-wave1.83-dev 1.83.0-2 pn libboost1.83-doc <none> ii libboost1.83-tools-dev 1.83.0-2 pn libmpfrc++-dev <none> pn libntl-dev <none> -- no debconf information
