Bug#983427: libpam-runtime: please add support for DPKG_ROOT

2021-08-26 Thread Johannes Schauer Marin Rodrigues
Hi sam, Quoting Sam Hartman (2021-08-26 22:23:18) > > "Johannes" == Johannes 'josch' Schauer writes: > > Johannes> diff --git a/debian/libpam-runtime.postinst > > I think that your patch ends up with things like $confdir set to > "//etc/pam.d" when $DPKG_ROOT is empty. You get one

Bug#983427: libpam-runtime: please add support for DPKG_ROOT

2021-08-26 Thread Sam Hartman
> "Johannes" == Johannes 'josch' Schauer writes: Johannes> diff --git a/debian/libpam-runtime.postinst I think that your patch ends up with things like $confdir set to "//etc/pam.d" when $DPKG_ROOT is empty. You get one slash from the initialization of the variable and one slash from

Bug#983427: libpam-runtime: please add support for DPKG_ROOT

2021-08-20 Thread Johannes Schauer Marin Rodrigues
Hi, Quoting Sam Hartman (2021-06-22 20:48:43) > So, the feature seems achievable for a significant important use case > and so I think we should take the patch. for your convenience, I created a MR on salsa with the proposed changes: https://salsa.debian.org/vorlon/pam/-/merge_requests/6

Bug#983427: libpam-runtime: please add support for DPKG_ROOT

2021-06-22 Thread Sam Hartman
control: tags -1 confirmed > "Johannes" == Johannes 'josch' Schauer writes: Johannes> Hi, Johannes> since dpkg 1.18.5, dpkg sets the variable DPKG_ROOT when Johannes> invoking maintainer scripts. Usually that variable is Johannes> empty but when calling dpkg with --root and

Bug#983427: libpam-runtime: please add support for DPKG_ROOT

2021-06-21 Thread Sam Hartman
> "Johannes" == Johannes 'josch' Schauer writes: I took a look at the references in the bug. In particular, https://wiki.debian.org/Teams/Dpkg/Spec/InstallBootstrap My goal was to try and do homework prior to a call. Here's where I got: That page actually seems to talk about a different

Bug#983427: libpam-runtime: please add support for DPKG_ROOT

2021-06-21 Thread Johannes Schauer Marin Rodrigues
Hi Sam, Quoting Sam Hartman (2021-02-25 17:56:07) > I'm setting a calendar note to come back tho this in May. > Apologies for not having time sooner; I'm in the middle of planning for > a move and trying to deal with bullseye issues. I hope that everything went okay with your move and we can

Bug#983427: libpam-runtime: please add support for DPKG_ROOT

2021-02-25 Thread Sam Hartman
I'm setting a calendar note to come back tho this in May. Apologies for not having time sooner; I'm in the middle of planning for a move and trying to deal with bullseye issues.

Bug#983427: libpam-runtime: please add support for DPKG_ROOT

2021-02-25 Thread Johannes Schauer Marin Rodrigues
Hi, I don't want to start a discussion. So no need to reply. I just wanted to clarify some things. Quoting Sam Hartman (2021-02-24 23:12:11) > I'm not at all convinced this is a good idea. We're replacing a great, > well-tested facility--namely running maintainer scripts in root directories >

Bug#983427: libpam-runtime: please add support for DPKG_ROOT

2021-02-24 Thread Sam Hartman
control: tags -1 wontfix I'm not at all convinced this is a good idea. We're replacing a great, well-tested facility--namely running maintainer scripts in root directories with a mechanism that requires support to be spread through each package. I appreciate that this approach has the support

Bug#983427: libpam-runtime: please add support for DPKG_ROOT

2021-02-23 Thread Johannes 'josch' Schauer
Package: libpam-runtime Version: 1.4.0-4.1 Severity: wishlist Tags: patch User: debian-d...@lists.debian.org Usertags: dpkg-root-support Hi, since dpkg 1.18.5, dpkg sets the variable DPKG_ROOT when invoking maintainer scripts. Usually that variable is empty but when calling dpkg with --root and