Your message dated Sun, 12 Jul 2026 10:05:49 +1000
with message-id 
<CABDzzBWNRncQqjQFd-yJTX2RinGmmxpJXu=7fgvf88tcy30...@mail.gmail.com>
and subject line Re: Bug#1021915: libapache2-mod-dnssd: Cannot update package
has caused the Debian Bug report #1021915,
regarding libapache2-mod-dnssd: Cannot update packaga
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1021915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021915
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libapache2-mod-dnssd
Version: 0.6-3.3
Severity: important

Dear Maintainer,

During the upgrade I got the following error:

Setting up libapache2-mod-dnssd (0.6-3.3) ...
dpkg: error processing package libapache2-mod-dnssd (--configure):
 installed libapache2-mod-dnssd package post-installation script subprocess retu
rned error exit status 1
Errors were encountered while processing:
 libapache2-mod-dnssd
E: Sub-process /usr/bin/dpkg returned an error code (1)


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (710, 'unstable'), (670, 'testing'), (660, 'experimental'), (600, 
'stable'), (500, 'stable-security'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 6.0.0-trunk-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libapache2-mod-dnssd depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.54-3
ii  avahi-daemon                        0.8-6+b1
ii  libapr1                             1.7.0-8
ii  libavahi-client3                    0.8-6+b1
ii  libavahi-common3                    0.8-6+b1
ii  libc6                               2.36-1

libapache2-mod-dnssd recommends no packages.

libapache2-mod-dnssd suggests no packages.

-- Configuration Files:
/etc/apache2/mods-available/dnssd.conf [Errno 2] No such file or directory: 
'/etc/apache2/mods-available/dnssd.conf'
/etc/apache2/mods-available/dnssd.load [Errno 2] No such file or directory: 
'/etc/apache2/mods-available/dnssd.load'

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi Michael,

A month ago I asked whether this upgrade failure still reproduces on a
current bookworm or trixie system. I haven't heard back, so I'm closing the
bug as announced.

To recap: the failure was never 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 stable-to-sid and testing-to-sid. The evidence pointed
at inconsistent local apache2 module state on the reporting system: the
module's .load file was missing from /etc/apache2/mods-available/, so the
dh_apache2-generated "apache2_invoke enmod dnssd" in the postinst had
nothing to enable and aborted configure.

If you can still reproduce it with a current version (0.6-7 is now in
trixie and sid), please reopen this bug or file a new one, attaching an "sh
-x" trace of the failing postinst and the contents of
/etc/apache2/mods-available/ and /etc/apache2/mods-enabled/.

Thanks,
Jayen Ashar <[email protected]>

--- End Message ---

Reply via email to