Bug#916786: marked as done (916750)
Your message dated Wed, 19 Dec 2018 14:44:06 +0000
with message-id <E1gZd4w-00038u-V4@fasolo.debian.org>
and subject line Bug#916786: fixed in elogind 239.3-4+debian1
has caused the Debian Bug report #916786,
regarding 916750
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 owner@bugs.debian.org
immediately.)
--
916786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916786
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: lighttpd
Version: 1.4.52-1
> Problem #2:
>
> lighttpd presently produces 11 binary packages. That's quite many for an
> otherwise small package. Adding binary packages has a metadata cost to
> the Debian archive that affects everyone (not just lighttpd users). We
> should seek to reduce the package count.
IMHO, it appears that the origin of these issues is the metadata cost,
and not that lighttpd is modular. It appears the metadata costs are
the tail wagging the dog for package design decisions. That is most
unfortunate.
> How bad would it be to simply not ship these four packages in buster (as
> is presently the case) and add them for bullseye? Which ones do we
> really need for buster? Did I miss anything?
The previous Debian lighttpd maintainers did a pretty poor job following
upstream. Just about everything that you're doing is an improvement, so
thank you.
Perhaps for Buster, all the new packages should be removed, except
those split from existing lighttpd core (mod_openssl) and from mod_auth
(mod_authn_file, mod_authn_ldap). Hopefully, Debian will address the
metadata cost scaling issue in a future Debian release.
I still think it reflects poorly on Debian that lighttpd in Debian
will be crippled due to Debian packaging scaling limitations.
While I would like to see mod_openssl as its own package for the
future, no such requirement exists at the moment, and other parts of
lighttpd link against libcrypto (not libssl). The lighttpd build
would have to be modified if lighttpd were to provide some algorithms
with the core (e.g. SHA1), rather than obtaining them from libcrypto,
and then mod_openssl built separately. So for now, let's not do
mod_openssl as a separate package.
As you proposed, we might proceed with creating lighttpd-modules-mysql
and lighttpd-modules-ldap to start the transition, as that makes sense
to group the modules depending on the database so that a future Debian
release can remove those dependencies from the core.
.
tl;dr:
I agree with your proposal for lighttpd-modules-mysql and
lighttpd-modules-ldap, though I might suggest lighttpd-modules-mariadb
instead of lighttpd-modules-mysql.
I agree with your proposal to avoid adding new modules to the lighttpd
base package which would increase the dependency footprint of the
lighttpd base package.
I propose leaving the -dev build dependencies in debian/rules so that
others could more easily build dpkgs of the additional modules, and
install those modules themselves.
--- End Message ---
--- Begin Message ---
Source: elogind
Source-Version: 239.3-4+debian1
We believe that the bug you reported is fixed in the latest version of
elogind, 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 916786@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mark Hindley <mark@hindley.org.uk> (supplier of updated elogind 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 ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 19 Dec 2018 09:15:05 +0000
Source: elogind
Binary: elogind libelogind0 libelogind-dev libelogind-dev-doc libpam-elogind
Architecture: source
Version: 239.3-4+debian1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ecosystem Init Diversity Team <debian-init-diversity@chiark.greenend.org.uk>
Changed-By: Mark Hindley <mark@hindley.org.uk>
Description:
elogind - user, seat and session management daemon
libelogind-dev - user, seat and session management library (development files)
libelogind-dev-doc - user, seat and session management library (development documentat
libelogind0 - user, seat and session management library
libpam-elogind - elogind PAM module
Closes: 916786
Changes:
elogind (239.3-4+debian1) unstable; urgency=medium
.
* Set AppStream component id to begin with a reverse domain name.
* Add Breaks and Replaces libelogind-dev (<< 239.1+20181115-1) to
libelogind-dev-doc (Closes: #916786).
Checksums-Sha1:
0459b540c75bd8a4719b41ead0b8a95c409dc70b 2595 elogind_239.3-4+debian1.dsc
ebd0fe1c9bfbc8ae475123a79bea4b58115b46bf 7252 elogind_239.3-4+debian1.debian.tar.xz
0ba761d9c22adde9b9a24134d55020764cb4d550 6455 elogind_239.3-4+debian1_source.buildinfo
Checksums-Sha256:
a972d09e79860c950816d76e952eff62ce327fda757adc023b0b03364c1a3734 2595 elogind_239.3-4+debian1.dsc
294169fd03b867b1614e2f9b769fe3eaf74cbc54f716e5051e0c23c0e332c9f7 7252 elogind_239.3-4+debian1.debian.tar.xz
cc58552573a15ce727306def7a716d64270fccb530e482ca299e6b75173adf55 6455 elogind_239.3-4+debian1_source.buildinfo
Files:
57228d36ffa2aa48dd3675066d18ed7e 2595 admin optional elogind_239.3-4+debian1.dsc
344be12cc6645c7511a6b61ca639b871 7252 admin optional elogind_239.3-4+debian1.debian.tar.xz
83e079cae38a7155891f699293c1de6f 6455 admin optional elogind_239.3-4+debian1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlwaTMUACgkQweDZLphv
fH6CDQ/+JGPbr6uxcs/Pn77E1LjonW52EI544Xns8Va97B9M/d27XSzwOH/rz60F
oVBBm2Ipzu3KTZNC5VdBdzZZerYu3QpyftiVKAL2R6T536MomoxIyl/5IzXtWL1z
2/uWRFbFm/DnvcCauMQizdc3EvwGmvKRYTlfiTiqNv9ePKyMeI0JAqArVWEZb9dR
ITVPOTt0J3huYfBj7+ISqTZ98H2P5FgQ2l02OlgDA5UR/SmhXoLZF4MkQNbfYkWw
hdiE/OkVmgkj1lP8uqx+OZh+QjqQz5a1989jWzVnRt2qVhPzWhBg5Lwq/85SbY7W
cAys7iQ4+nyKXq62eDj3SsVZS9+Jo5EOMLiRarFIX67NRS8gSQL3DnjNAbBjOLb3
VR9U/LwnFhU/IcXM0RCC+ra62R+YU2Y2IUNliEboeALoGhn4QnS9dcaP1tVQKuEh
7wT4a5HyC41L0tb70lpshjYdHtQmBWtNbt9qRK6tkInFYNqZGIAeLEGOL3JfZ94U
TMcmtVLJBiobRZ7v3tZyHbAI3w6xaYCqpq32qoUq2ZhoaQxT9REom7YusKx7JnM+
foP6N9WXIomUzs5mluRVqCncXPhOStNDipx5FYNXciZ7xIc26ZPshOICnBm5hGA8
uzrMxJacVFeaJbwglqS3nwV+v5Ee2L4LbDcDvrDPeB4YD3bY3RQ=
=y6G7
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: