Hi Sam, On Tue, 06 Jul 2021 08:46:30 -0600 Sam Hartman <hartm...@debian.org> 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 those are not multiarch-ed, IMO. And at this time, last minutes for release, we should ensure "it works" as previously to deliver values for users. Breaking several libpam-* packages is not. Is there any *strong* reason to not deffer make libpam-* packages multiarch-ed to bookworm release? > 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. I want his comment, too. git log in his repo just says "refresh patches" for this change, and debian/patches-applied/lib_security_multiarch_compat is the patch for non-multiarch pam modules and still remains. If it was intended, it should be removed, I suppose. > I think you failed to read my comments in the 990412 bug log before > Merging and reassigning. Okay, will read again. Thanks! -- Hideki Yamane <henr...@iijmio-mail.jp>
