Summary
mtp-server in the next snapshot still hard-depends on libboost-filesystem1.83.0 and libboost-thread1.83.0, but next has since moved boost to 1.90 and dropped the 1.83 runtime packages. mtp-server is therefore uninstallable, and because droidian-base depends on mtp-server, every device rootfs build against next now fails during the apt/debootstrap stage.
Impact
debos rootfs builds break for any device pulling droidian-base from next. First observed 2026-07-30; builds fail at the "Build rootfs" step with:
E: Unable to satisfy dependencies. Reached two conflicting assignments:
1. mtp-server:arm64 is selected for install because:
1. droidian-base:arm64 is selected for install
2. droidian-base:arm64 Depends mtp-server
2. mtp-server:arm64 Depends libboost-filesystem1.83.0 (>= 1.83.0)
but none of the choices are installable:
[no choices]
Root cause
Boost 1.83 → 1.90 ABI transition in the next archive. mtp-server was last built on 2024-08-02 and was not rebuilt against the new boost, so it still carries the (now-removed) 1.83 shlib dependencies.
Current next snapshot (rolling/main/binary-arm64):
mtp-server 8+git20240802124857.2b0f798.next.production
Depends: ... libboost-filesystem1.83.0 (>= 1.83.0), libboost-thread1.83.0 (>= 1.83.0), ...- The archive now ships only
libboost-*1.90.0; libboost-filesystem1.83.0 and libboost-thread1.83.0 are gone.
next dists/rolling/InRelease Date: Thu, 30 Jul 2026 — matches exactly when builds started failing.
Evidence that it is purely the archive and not any device repo: an unchanged device commit built successfully on 2026-07-29 and failed on 2026-07-30 with no repository change on our side — only the next pointer moved.
Suggested fix
A no-change rebuild of mtp-server against boost 1.90 should resolve it — d-shlibs will pick up libboost-filesystem1.90.0 / libboost-thread1.90.0 automatically.
Note
A handful of unrelated archive packages also still reference boost 1.83 (e.g. litecoin*, libpwiz*, spectrum2*, swiften), but they are not in the device rootfs dependency path. mtp-server is the one that blocks droidian-base, and therefore all device builds.
Summary
mtp-serverin thenextsnapshot still hard-depends onlibboost-filesystem1.83.0andlibboost-thread1.83.0, butnexthas since moved boost to 1.90 and dropped the 1.83 runtime packages.mtp-serveris therefore uninstallable, and becausedroidian-basedepends onmtp-server, every device rootfs build againstnextnow fails during the apt/debootstrap stage.Impact
debosrootfs builds break for any device pullingdroidian-basefromnext. First observed 2026-07-30; builds fail at the "Build rootfs" step with:Root cause
Boost 1.83 → 1.90 ABI transition in the
nextarchive.mtp-serverwas last built on 2024-08-02 and was not rebuilt against the new boost, so it still carries the (now-removed) 1.83 shlib dependencies.Current
nextsnapshot (rolling/main/binary-arm64):mtp-server8+git20240802124857.2b0f798.next.productionDepends: ... libboost-filesystem1.83.0 (>= 1.83.0), libboost-thread1.83.0 (>= 1.83.0), ...libboost-*1.90.0;libboost-filesystem1.83.0andlibboost-thread1.83.0are gone.nextdists/rolling/InReleaseDate: Thu, 30 Jul 2026— matches exactly when builds started failing.Evidence that it is purely the archive and not any device repo: an unchanged device commit built successfully on 2026-07-29 and failed on 2026-07-30 with no repository change on our side — only the
nextpointer moved.Suggested fix
A no-change rebuild of
mtp-serveragainst boost 1.90 should resolve it — d-shlibs will pick uplibboost-filesystem1.90.0/libboost-thread1.90.0automatically.Note
A handful of unrelated archive packages also still reference boost 1.83 (e.g.
litecoin*,libpwiz*,spectrum2*,swiften), but they are not in the device rootfs dependency path.mtp-serveris the one that blocksdroidian-base, and therefore all device builds.