Hi, Helmut, I am not sure if this bug really exists?
FYI: If this bug exists, it is around the current usage of dpkg-maint-helper(1). Helmut, please respond to the following for me to proceed with this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100677 I assumed Helmut (this bug report) rigorously tested for the current packages. I also looked into the solution in rush before sending my initial response. But I felt a bit awkward, to be honest now. So I left the solution in VCS commit only at this moment. Some facts: * 2.100 BOOKWORM version * 2.109 BUG causing version * 2.115 BUG fix version using dpkg-maint-helper(1) * 2.125 CURRENT testing version These point me to think this bug shouldn't exist, now. Please note I am not asserting the bug reporter didn't encounter problem. Bug fix like this can't ensure broken system upgraded from 2.100 to 2.114. The packaging scripts are not be required to address such broken system. Fixing such broken system are usually left to the system admin using 2.109-2.144. As I re-read this bug report, Helmut only presented possible "undeclared file conflict" but had no actual incident log proof to back it up on the current version. I know this is a complicated packaging task situation and want to be absolutely sure. So, please help me with the followings by providing reproducible bug example log on the testing package. If bug exists, I will test updated fix with it. As for the possible "undeclared file conflict" mentioned, it's a complicated situation for which Debian dpkg developers recommend us to use their elegant dpkg-maint-helper(1) to address it without ugly pre-depends. I fixed this bug in 2.115 using this dpkg-maint-helper(1) trick. You can see this dpkg-maint-helper(1) used in debian/debian-reference- common.maintscript: (original commit) https://salsa.debian.org/debian/debian-reference/-/blob/4e6768c41543ff427568b999c3ffcf0afb76cfb7/debian/debian-reference-common.maintscript As for "Pre-Depends: dpkg (>= 1.17.14)" mentioned in the dpkg-maint-helper(1) manpage, I skipped it since all current usable dpkg are: * oldstable: 1.20.13 * old-sec: 1.20.10 * stable: 1.21.22 * testing: 1.22.18 * unstable: 1.22.18 Best regards, Osamu PS: This reminds me to add some easy-to-find reminder in debmake-doc to make it easy to find the usage of dpkg-maint-helper(1) PPS: If the existing fix is good enough, I shouldn't make un-needed and redundant changes in 2.126.
