Your message dated Tue, 14 Jan 2025 12:54:44 +0000
with message-id <e1txgrq-003d6w...@fasolo.debian.org>
and subject line Bug#1087324: fixed in haveged 1.9.19-7
has caused the Debian Bug report #1087324,
regarding haveged-udeb: fails to start: haveged_sem error: ENOENT
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 ow...@bugs.debian.org
immediately.)


-- 
1087324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: haveged-udeb
Version: 1.9.19-2
Severity: serious
Tags: d-i
Justification: makes the package useless, arguably critical
X-Debbugs-Cc: debian-b...@lists.debian.org

Hi,

haveged doesn't start at all in d-i, and that's not an apparmor issue
(#1087318):

    haveged: command socket is listening at fd 3
    haveged: Couldn't create named semaphore haveged_sem error: No such file or 
directory

While haveged is supposed to be less critical than it used to be at the
time it was added to the installer, I don't remember seeing a study
making it clear it can be removed. At this point of the release cycle,
I'd rather see haveged fixed anyway.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

--- End Message ---
--- Begin Message ---
Source: haveged
Source-Version: 1.9.19-7
Done: Daniel Baumann <dan...@debian.org>

We believe that the bug you reported is fixed in the latest version of
haveged, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1087...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Baumann <dan...@debian.org> (supplier of updated haveged package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 14 Jan 2025 11:39:21 +0100
Source: haveged
Architecture: source
Version: 1.9.19-7
Distribution: unstable
Urgency: medium
Maintainer: Daniel Baumann <dan...@debian.org>
Changed-By: Daniel Baumann <dan...@debian.org>
Closes: 1087324
Changes:
 haveged (1.9.19-7) unstable; urgency=medium
 .
   * Using postinst in haveged-udeb to create /dev/shm at runtime (Closes:
     #1087324).
Checksums-Sha1:
 6ba7a832f70936e9934cc966c0da793902a248bf 1439 haveged_1.9.19-7.dsc
 980448c172afd26898a2a25dc2b8e7930f42e4eb 11064 haveged_1.9.19-7.debian.tar.xz
 1067bee0f71af21d68e3ca568179909cf5fe3528 6438 haveged_1.9.19-7_amd64.buildinfo
Checksums-Sha256:
 8059f9ffad88c2c4896d72c2dc8c424c9e7831333a583cd7e687eaf355d7a01e 1439 
haveged_1.9.19-7.dsc
 403bb8d36f5e8f78f393d8af409b361e1cb9ed25867a0dc34b8c7bcc941d1843 11064 
haveged_1.9.19-7.debian.tar.xz
 d3d44e73abf4704ccecf13c610153395295d3620050a4936ad7828f7d66ff59e 6438 
haveged_1.9.19-7_amd64.buildinfo
Files:
 d32d8a938b37e04314595f73b9fc6fba 1439 misc optional haveged_1.9.19-7.dsc
 48b9d66e8ba50cea5e89d6909c7c08a0 11064 misc optional 
haveged_1.9.19-7.debian.tar.xz
 17318e08fc1f670827317736f676eda7 6438 misc optional 
haveged_1.9.19-7_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQQmmGg4gLaoSj0ERgL7tPDoCoAiLwUCZ4ZWeQAKCRD7tPDoCoAi
L9P/AP47v877Uwx4jI67CfwNg4/q/drS5XZYpdbDzRJ52bN4awD+LDEsWLAkoiHL
dHIRD1RfwKAoa2uyF86qyi4UJ0eOfgg=
=Fx34
-----END PGP SIGNATURE-----

Attachment: pgpBZLMhjrc1Y.pgp
Description: PGP signature


--- End Message ---

Reply via email to