Open wojiushixiaobai opened 4 months ago
Hmm, we don't officially support building FROM debian:sid-slim
, and diverted files at this point in the Dockerfile
is definitely strange (we haven't done any intentional dpkg-divert
calls, so they'd have to be something in the packages themselves, which is weird).
Is this something specific to a build against loong64
, or can you reproduce on a stock amd64
build as well?
@tianon
Yes, as long as the debian:sid-slim
image is used, any architecture can reproduce this problem.
debian:sid
build successfully. debian:trixie
build successfully. debian:sid-slim
build failed.debian:trixie-slim
build failed. Interesting :thinking: (thanks for the detailed testing!)
I'm not sure why we're seeing diversions that are clearly related to usrmerge, but the resulting output format from dpkg-query
that we're choking on is not unexpected/is documented so I guess we ought to put more thought into this:
The output format consists of one line per matching pattern, with a list of packages owning the pathname separated by a comma (U+002C ‘,’) and a space (U+0020 ‘ ’), followed by a colon (U+003A ‘:’) and a space, followed by the pathname. As in:
pkgname1, pkgname2: pathname1 pkgname3: pathname2
File diversions are printed with the following localized strings:
diversion by pkgname from: diverted-from diversion by pkgname to: diverted-to
or for local diversions:
local diversion from: diverted-from local diversion to: diverted-to
https://manpages.debian.org/bookworm/dpkg/dpkg-query.1.en.html