Hi,
any particular reason for not adopting the upstream patch, which fixes
the problem properly? Disabling the compiler/build flags that tripped
the error could have other consequences.
Control: tags 1020527 + patch
Control: tags 1020527 + pending
Dear maintainer,
I've prepared an NMU for pam-p11 (versioned as 0.3.1-1.2) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru pam-p11-0.3.1/debian/changelog
Control: severity -1 serious
This is now happening.
Package: pam-p11
Version: 0.3.1-1.1
Severity: normal
Dear Maintainer,
it's likely that the current pam-p11 source package will FTBFS in some
architectures if a rebuild is attempted at this time, with gcc-12. We
encountered this problem[1][2] in Ubuntu, and upstream committed a fix[3]
which we
4 matches
Mail list logo