Hi Sam,
On Mon, Nov 13, 2023 at 09:16:33AM -0700, Sam Hartman wrote:
> Bastian> Your suggestion splitting out and removing after one
> Bastian> release would be fine for me.
>
>
> Helmut, I was hoping for a sanity check.
thanks for reaching out.
> Bastian wants to split out some code f
Bastian> Your suggestion splitting out and removing after one
Bastian> release would be fine for me.
Helmut, I was hoping for a sanity check.
Bastian wants to split out some code from pam.
He wants to move pam_userdb.so into its own package to remove db5.3 from
the pseudo-essential set.
Am 13.11.23 um 03:18 schrieb Sam Hartman:
Is this a nice to have for you, or are you heavily involved in something
with broad consensus where this is important.
I have listed this bug in https://wiki.debian.org/Proposals/EssentialOnDiet
Your suggestion splitting out and removing after one rele
> "Bastian" == Bastian Germann writes:
Bastian> X-Debbugs-Cc: vor...@debian.org Hi Sam and Steve,
Bastian> On Wed, 1 Mar 2023 18:34:50 +0100 Bastian Germann wrote:
Bastian> I would volunteer to provide a patch for this but only if
Bastian> it will be considered.
The patch is
X-Debbugs-Cc: vor...@debian.org
Hi Sam and Steve,
On Wed, 1 Mar 2023 18:34:50 +0100 Bastian Germann wrote:
libpam-modules is the only pseudo-essential module that depends on libdb5.3 via
its pam_userdb module.
I have never seen a system actually using this so I suggest to remove during
the tr
Package: libpam-modules
Severity: wishlist
Version: 1.5.2-6
libpam-modules is the only pseudo-essential module that depends on libdb5.3 via
its pam_userdb module.
I have never seen a system actually using this so I suggest to remove during
the trixie release cylce,
i.e. dropping the Build-Depen
6 matches
Mail list logo
