Your message dated Sun, 22 Dec 2024 17:19:31 +0000
with message-id <[email protected]>
and subject line Bug#1088019: fixed in git 1:2.45.2-1.3
has caused the Debian Bug report #1088019,
regarding git-daemon-run: Missing dependency on runit
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.)
--
1088019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088019
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git
Version: 1:2.45.2-1.1
Severity: serious
X-Debbugs-Cc: Chris Hofstaedtler <[email protected]>
git (1:2.45.2-1.1) unstable; urgency=medium
* Non-maintainer upload.
* Demote "runit" dependency to Recommends.
Demoting Depends: runit to Recommends: should have no effect on default
installs (apt will install Recommends by default), and people wanting to
use runit should have it installed already. (Closes: #1078778)
-- Chris Hofstaedtler <[email protected]> Sun, 13 Oct 2024 14:16:01 +0200
The "should have no effect on default installs" claim
is only true when runit is part of the distribution.
What ensures that runit is in trixie without the dependency?
Without runit, this package is RC-buggy broken.
Additionally, the change from 1:2.45.2-1.2 does not properly
handle the case when runit gets installed after git-daemon-run.
For historical reasons the git-daemon packages support being started
by either runit or sysvinit.
The runit support was added before systemd even existed.
Does it make sense to use runit for supervising a daemon
when systemd is the init system?
A systemd unit might be more useful than using runit.
--- End Message ---
--- Begin Message ---
Source: git
Source-Version: 1:2.45.2-1.3
Done: Chris Hofstaedtler <[email protected]>
We believe that the bug you reported is fixed in the latest version of
git, 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.
Chris Hofstaedtler <[email protected]> (supplier of updated git 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: Sun, 22 Dec 2024 16:52:50 +0100
Source: git
Architecture: source
Version: 1:2.45.2-1.3
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Nieder <[email protected]>
Changed-By: Chris Hofstaedtler <[email protected]>
Closes: 1088019
Changes:
git (1:2.45.2-1.3) unstable; urgency=medium
.
* Non-maintainer upload.
* Revert my two previous NMUs as I don't have the time to fully clean
up the situation. Reopens: #1020284 #1078778
Closes: #1088019
Checksums-Sha1:
2499620d2547061b47fbd33df60ee8917d37f374 2804 git_2.45.2-1.3.dsc
7da6d08ebbeb083565ba11bf0f218f0e0648b005 778152 git_2.45.2-1.3.debian.tar.xz
770663073444ac75244548ea87adf8624b5995e1 13364 git_2.45.2-1.3_arm64.buildinfo
Checksums-Sha256:
a2e4645c7ceac7b7fc2435fb20c62a99de5d89d50e162ad150b8861d276a073a 2804
git_2.45.2-1.3.dsc
e35f5d511567629260d2b33255de0e5108f5f6c1362b100dfa08ca8f13736489 778152
git_2.45.2-1.3.debian.tar.xz
a60330cfb2b04798daf9769e3b90ab62135d70cd657e16e7c7175f749f34127f 13364
git_2.45.2-1.3_arm64.buildinfo
Files:
d7b3be80c050a1c2ad7cbe260a9d615b 2804 vcs optional git_2.45.2-1.3.dsc
cd9f8851e850651026837eed805e9bfd 778152 vcs optional
git_2.45.2-1.3.debian.tar.xz
74fff7368802f84c7bbeb4e62f837ab4 13364 vcs optional
git_2.45.2-1.3_arm64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmdoRwEACgkQXBPW25MF
LgOM6A/+PndwD1vEuRVIMJQKqqV9luNyppWKE1HbkX/9bMt1c8FT5sCPZ/YW+egX
0lQ3wfaeA478q6qDd5NxqCYb4H+hCcg4q0CdaFIMHgcVd8MA4/ChWdc1FPI0E5MI
TTk8XfvKWXrlzghzul9tfRfehFADWfVUWRLJbhXGUhypFCDip/vZg1t1ZVLVoRC3
4fOZmpfOBA9pbRaIOxCAoqPpCbs7x9jsCLSsGdeCs7XtcJ5WCuqpCUFIycV38Flv
XADNf55f0qkgtvqrb5Xn4oGJRx1E7c9Bbeahs0uTpLy/3AFpfZ4/kzUNiXRDF7Nc
135Kkv8G1loUg9Lw9kFVLm+Vk+8l6nZF4WjQEfqnFf4JrR3BiEmhnLsBnT2kd6XY
wddtPERWIXyrOKyx8+lyi5SzDfVSKiesP3Sy8SmT6D/NevAHMh57EwA8xtgafCX8
yeGKbye6GLCEknjFtg6YX59sarsjPng089lJ9bV1KlCo8PuL6YozOl7Xljb6zJRL
i6cnZNFJnCuPjRVj6raqQWYIFMyr5TG8vY221pmGYxP/VsyZdWXsnL0rS8qM+M7V
5ikE+/8IcGK0sMP//BLkpCqsNEGUs1LLdk7WxUOZOkE9DtWsLh1CkYMx8h1psOCi
DGXmdzRe2k9RJJiF0ge4P2ZKUZ9hbCWvNq4WWnHzGgOajnKUMwM=
=hVIN
-----END PGP SIGNATURE-----
pgpCweRBJz9WY.pgp
Description: PGP signature
--- End Message ---
