Bug#990412: pam: Regression - it won't search /lib/security

2021-07-06 Thread Hideki Yamane
control: tags -1 +patch +pending Hi, I've found the root cause of this bug, and fixed it. On my local sid machine, I've tested it with edit /etc/pam.d/su as search pam_yubico.so, exec su and it searchs /lib/security/pam_yubico.so :) See below debdiff. If it seems to be okay, I'll put it into

Bug#990412: pam: Regression - it won't search /lib/security

2021-07-06 Thread Sam Hartman
> "Hideki" == Hideki Yamane writes: control: tags -1 -patch -pending I NACK this proposed NMU. This many years after multiarch, I think it is entirely reasonable for PAM to drop support for non-multiarch paths at the transition between buster and bullseye. As I said earlier in the bug, I'm h

Bug#990412: pam: Regression - it won't search /lib/security

2021-07-06 Thread Hideki Yamane
Hi Sam, On Tue, 06 Jul 2021 08:46:30 -0600 Sam Hartman wrote: > This many years after multiarch, I think it is entirely reasonable for > PAM to drop support for non-multiarch paths at the transition between > buster and bullseye. It was NOT raised as a goal of bullseye for libpam-* packages tho

Bug#990412: pam: Regression - it won't search /lib/security

2021-07-06 Thread Sam Hartman
> "Hideki" == Hideki Yamane writes: >> I think Steve is quite familiar with multiarch and while he >> hasn't commented yet I'm assuming he dropped those patch lines as >> part of removing unnecessary upstream deltas. Hideki> I want his comment, too. Okay, let's hold off unti

Bug#990412: pam: Regression - it won't search /lib/security

2021-07-06 Thread Steve Langasek
On Tue, Jul 06, 2021 at 08:46:30AM -0600, Sam Hartman wrote: > > "Hideki" == Hideki Yamane writes: > control: tags -1 -patch -pending > I NACK this proposed NMU. > This many years after multiarch, I think it is entirely reasonable for > PAM to drop support for non-multiarch paths at the tran

Bug#990412: pam: Regression - it won't search /lib/security

2021-07-07 Thread Sam Hartman
> "Steve" == Steve Langasek writes: Steve> For the record, I did not intentionally drop those lines, Steve> this was a matter of a mis-merge. Okay, if it was a miss-merge, let's see if we can fix. I'm reasonably busy this morning but will try to prepare something later today based on