Your message dated Fri, 01 Mar 2024 21:35:22 +0000
with message-id <[email protected]>
and subject line Bug#1064788: fixed in haproxy 2.9.6-1
has caused the Debian Bug report #1064788,
regarding haproxy: installs same filename to both bin and sbin
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.)


-- 
1064788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064788
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: haproxy
Severity: normal

Dear Maintainer,

your package installs the filename halog to both bin and sbin as opposed to 
just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

--- End Message ---
--- Begin Message ---
Source: haproxy
Source-Version: 2.9.6-1
Done: Vincent Bernat <bernat@neo>

We believe that the bug you reported is fixed in the latest version of
haproxy, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vincent Bernat <bernat@neo> (supplier of updated haproxy 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 [email protected])


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

Format: 1.8
Date: Fri, 01 Mar 2024 22:01:08 +0100
Source: haproxy
Architecture: source
Version: 2.9.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HAProxy Maintainers <[email protected]>
Changed-By: Vincent Bernat <bernat@neo>
Closes: 1064788
Changes:
 haproxy (2.9.6-1) unstable; urgency=medium
 .
   * New upstream release.
   * d/install: don't ship halog both in usr/bin and usr/sbin.
     Closes: #1064788.
Checksums-Sha1:
 f89e8d5b2f4d05934cf3ad78875ef3477d363a35 2402 haproxy_2.9.6-1.dsc
 3a168509ab85fb698366d83471f71ed8a0fa4e74 4507680 haproxy_2.9.6.orig.tar.gz
 a6ee3b3ba9407d602363c83f0607f9bb198cb13f 74044 haproxy_2.9.6-1.debian.tar.xz
 9581d41efe39ea9f2b394eab4f559ffb0e88511d 10273 haproxy_2.9.6-1_amd64.buildinfo
Checksums-Sha256:
 94d0112392299e302927e9260d762ec72b99b8bcf0d5fb7a1ac4f1f6843833fa 2402 
haproxy_2.9.6-1.dsc
 208adf47c8fa83c54978034ba5c0110b7463c47078f119bd052342171a3b9a0b 4507680 
haproxy_2.9.6.orig.tar.gz
 a6d13e09976c25822868623396a2148d7e6f42e50dca43c38c893703aaf8da95 74044 
haproxy_2.9.6-1.debian.tar.xz
 479a4bb09fdbfbdd2340b66ff108035aac0dcfebe39c1acfe8b24c99321e6ce2 10273 
haproxy_2.9.6-1_amd64.buildinfo
Files:
 6aaaf3dfcc4dcf0955d8c9f3e80d1a75 2402 net optional haproxy_2.9.6-1.dsc
 a9485924b56d275ab8a0098b4c97dd81 4507680 net optional haproxy_2.9.6.orig.tar.gz
 1712bac31052d9f40054628bf2adf688 74044 net optional 
haproxy_2.9.6-1.debian.tar.xz
 d9a28ebf8b9a88aa3eabacee8132a11d 10273 net optional 
haproxy_2.9.6-1_amd64.buildinfo

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

iQJEBAEBCAAuFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAmXiQ6EQHGJlcm5hdEBs
dWZmeS5jeAAKCRCVpC/oNTUl+TMYEACB5Ze+Mcv/OE+S8N1ML/p5eDTGh11t9J9X
j/To7jBQfxsZaf041sU5aXlSmF9XHd4muZGScx8x5LeTMDFNaPJPSqZryJVdV06m
no9vW/9dzX14pCfl27pukjE+SlYSbQQoVq+UYNEaFGaLurEkrCdtfuKwFdGLIbW+
m4/SV3IYOV3N2DxU0bJ5u7jlTvCoqnriVC9Xuk+zYsUdiSrhnoeK93DccXNolcPT
Bb0FUgl+7wpTn0c2w7aff64So0w8NZfe19vjdGCsNqiCbTurXbDEGziMD7Pxnk3D
scfg2z+xX7x2YvnsjjAMmOjr8KvZQVQYFZvILs2cuJVh+GuiDVSfvZ1lcoPF0G8G
oRdpreZbPtsj0OH2p+M7PxS/4E7bVowPVmz8kGlYzKjyCu7RkpXiDXlcGGHfOKhO
6ejGhrqzHBZEEtjTc1A4J9bGcncliyznmjQ/8Aq2X+U0rVoVBjs0DYKgMZKmJFrG
jOzaltRinMg4a0PAtd6LBk9QHBAP1a5isdtief6qP4mSBrfmfvX32HD/dhZNN1ZF
8NqDhJnk02Hisz8lpa7mRoXrw7FuIrLJn3cvVRYf8CQXXj4RMBK8ZdqdYsZfcy2l
So6ePLQa/0HaIBkks1IzgbN6xIUTEwP4RsFrmUh2MYk+vBeCrPBP7LQE72Lt2YyX
2qw3Gteorw==
=Xzbc
-----END PGP SIGNATURE-----

Attachment: pgp6VUk9Cy0iA.pgp
Description: PGP signature


--- End Message ---

Reply via email to