Hi Sam, Quoting Sam Hartman (2021-11-03 15:36:30) > I did initial investigation of the source, and there's nothing odd going > on there with the configure script. > So, this one is going to be strange and probably isn't pam's fault. > > I think the bug is appropriate, but it wouldn't surprise me if the fix > is somewhere other than pam, because the configure script looks quite > normal. > > I just wanted to write and confirm that source inspection doesn't show > anything obvious. > I don't have sbuild set up locally (I moved to debspawn a few months > ago), but I'll go do that and try to reproduce.
we now know more about this problem. Yesterday, a new dash version got uploaded which enabled LINENO support. This results in autoconf choosing dash instead of bash for configure and this means that all bashisms used in configure.ac are suddenly errors. Since this change in dash affects a lot of source packages and since some of the problems will not be build failures but behaviour changes instead, the change is now reverted in unstable and a dash version with LINENO support was uploaded to experimental. So if you want to see this problem, you have to install dash from experimental instead. I can think of several ways to solve this bug: a) apply the patch provided by Helmut which essentially replaces double equal signs (a bashisms) with a single equal sign b) convince autoconf to continue using bash instead of dash even if dash with LINENO support is used c) convince the dash maintainer to never enable LINENO support so that pam will continue to use bash Thanks! cheers, josch
signature.asc
Description: signature
