Control: severity -1 normal Control: tags -1 + unreproducible moreinfo
Hi Michael, I've adopted mod-dnssd; 0.6-6 is now in unstable, and I'm going through its open bugs. This upgrade failure isn't reproducible in a clean environment. Vagrant Cascadian couldn't trigger it on a 0.6-3.2 to 0.6-3.3 upgrade, and piuparts passes both testing-to-sid and stable-to-sid. Your report showed /etc/apache2/mods-available/dnssd.conf and dnssd.load missing on your system; with the module's .load file absent, the postinst's "apache2_invoke enmod dnssd" has nothing to enable and exits non-zero, which aborts configure. That enable-or-exit snippet is generated by dh_apache2 and is identical across apache2 modules, so it points at an inconsistent local apache2 module state rather than a defect in the package. Since it doesn't affect clean upgrades, I've downgraded the severity to normal and tagged it unreproducible/moreinfo. Could you check whether it still reproduces on a current bookworm or trixie system? If you can still hit it, please run the failing upgrade with "sh -x" on the postinst and attach that, along with the contents of /etc/apache2/mods-available/ and /etc/apache2/mods-enabled/. If I don't hear back I'll close this in a few weeks. Thanks, Jayen Ashar <[email protected]>
