--- Begin Message ---
Source: lighttpd
Version: 1.4.52-1
It has come up that lighttpd's binary packages are organized
suboptimally. I'm creating this bug report to discuss a better
organization and have X-Debbugs-Cced some interested parties. Please
forward the bug to other interested parties that you may know of.
Problem #1:
Some upload since stretch added the mod_vhostdb_* modules including
mod_vhostdb_ldap.so and mod_vhostdb_mysql.so. Therefore lighttpd now
depends on libldap and libmariadbclient. That produces an unreasonable
installation size for embedded uses. Multiple people (including Stefan
Bühler, Glenn Strauss and myself) have requested to shrink this.
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.
Are there more problems?
Fixing the first problem likely involves making the second problem
worse. We should seek to avoid that.
With regard to fixing this my first proposal builds on the existing
practise to put mod_foo.so into lighttpd-mod-foo: Let every binary
package build from src:lighttpd have Provides for the modules that it
ships. For the present lighttpd-mod-* packages, no Provides are needed.
Only the main lighttpd package needs a pile of provides. A README.Debian
should explain that you should use these virtual packages in Depends
rather than e.g. "Depends: lighttpd (>=
$version_that_introduced_mod_foo)".
Given that lighttpd modules are comparatively small (some tens of KB), I
suggest that grouping them by their main dependency would make sense.
The fairly obvious consequences would be:
* lighttpd-modules-mysql: mod_authn_mysql, mod_mysql_vhost,
mod_vhostdb_mysql
* lighttpd-modules-ldap: mod_authn_ldap, mod_vhostdb_ldap
* lighttpd (base package): mod_access, mod_accesslog, mod_alias,
mod_auth, mod_authn_file, mod_cgi, mod_dirlisting, mod_evasive,
mod_evhost, mod_expire, mod_extforward, mod_fastcgi,
mod_flv_streaming, mod_indexfile, mod_proxy, mod_redirect,
mod_rewrite, mod_rrdtool, mod_scgi, mod_secdownload, mod_setenv,
mod_simple_vhost, mod_sockproxy, mod_ssi, mod_staticfile, mod_status,
mod_uploadprogress, mod_userdir, mod_usertrack, mod_vhostdb,
mod_wstunnel
* The modules mod_authn_gssapi, mod_cml, mod_geoip, mod_magnet,
mod_trigger_b4_dl and mod_webdav presently have their own binary
packages and they each have significant library piles. Maybe it is
best to leave these as is.
* The remaining modules are mod_compress, mod_deflate and mod_openssl.
These pull zlib1g, libbz2-1.0 and libssl1.1. At least the first two
are transitively essential already and mod_openssl seems to be very
popular, so it likely is best to leave them with the main binary
package.
Resulting changes:
* Merge lighttpd-mod-authn-mysql and lighttpd-mod-mysql-vhost together
into lighttpd-modules-mysql.
* Rename lighttpd-mod-auth-ldap to lighttpd-modules-ldap.
* Add 3 transitional dummy packages for the removed/renamed packages.
* Move mod_vhostdb_mysql and mod_vhostdb_ldap to the new packages.
-> mysql and ldap depends removed from lighttpd
-> +2 binary packages for buster
-> -3 binary packages for bullseye
-> Due to Provides (see above), rdeps don't have to change.
Then Stefan and Glenn proposed adding new modules:
* mod_vhostdb_dbi
* mod_vhostdb_pgsql
* mod_authn_pam
* mod_authn_sasl
Here it is less clear how to organize them. mod_cml and
mod_trigger_b4_dl each use libsasl2 (via libmemcached).
mod_vhostdb_pgsql is likely the only module that links postgres, so
likely it'll deserve a binary package.
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?
Please reply in a timely manner to allow implementing as much of the
changes as possible before the buster release.
Helmut
--- 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 ---