Your message dated Fri, 02 Dec 2022 17:20:24 +0000
with message-id <e1p19i4-009bfi...@fasolo.debian.org>
and subject line Bug#1020527: fixed in pam-p11 0.3.1-1.2
has caused the Debian Bug report #1020527,
regarding pam-p11: upcoming FTBFS
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1020527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 applied to the Ubuntu package.

I tried to propose a salsa PR, but it seems to be having problems at the
moment, so I'm filing this bug instead.

1. https://bugs.launchpad.net/ubuntu/+source/pam-p11/+bug/1990194
2. https://github.com/OpenSC/pam_p11/issues/24
3.
https://github.com/OpenSC/pam_p11/commit/f6ad88eac351db351940a08715dd3914cc601137

--- End Message ---
--- Begin Message ---
Source: pam-p11
Source-Version: 0.3.1-1.2
Done: Adrian Bunk <b...@debian.org>

We believe that the bug you reported is fixed in the latest version of
pam-p11, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk <b...@debian.org> (supplier of updated pam-p11 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 18 Nov 2022 18:02:03 +0200
Source: pam-p11
Architecture: source
Version: 0.3.1-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSC Maintainers <pkg-opensc-ma...@lists.alioth.debian.org>
Changed-By: Adrian Bunk <b...@debian.org>
Closes: 1020527
Changes:
 pam-p11 (0.3.1-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build with --disable-strict. (Closes: #1020527)
Checksums-Sha1:
 60d1804af55e409251959332c2caacf168008d4c 1961 pam-p11_0.3.1-1.2.dsc
 7aedc26a8748961de03eccc63b60d73b81b93eba 3464 pam-p11_0.3.1-1.2.debian.tar.xz
Checksums-Sha256:
 1ff7e9e9df320cba5e287a9a9425b415e968178667c7d26708b8a9d14a54e100 1961 
pam-p11_0.3.1-1.2.dsc
 728635e891aae9be9f035b375e7ff992319f1ec01c744fe35e28253ceecf2ee0 3464 
pam-p11_0.3.1-1.2.debian.tar.xz
Files:
 e74aa3dd6ae4cdb644066b4dd2e1472d 1961 admin optional pam-p11_0.3.1-1.2.dsc
 b7a5899a7bb6675bb7db127108b60bcd 3464 admin optional 
pam-p11_0.3.1-1.2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmN3rXIACgkQiNJCh6LY
mLEhhA//SCEbK4FPuyTLk2TP3iolxhWRg+V2JIGEVqqUPP8wHkrlPXz1J+/Xl4tE
Wr3XfBPII/65ByME5pPDt4MXpFZ8h7IE6+GMkal7M6FCOGRIpCVLXBIHPYEM3Z/W
hA0KRdVkX/Jk+dLPuG3hxcdBVfM1LligeGQxmPFkSTdyo3dyZAj47I5xth13VmvW
8jYApLRkPs6ljmibT6NEfHuvHY48ABltzUeYxQpQgqvrEmu6MTuNDZ+03pDu2XB+
vyanUntdknMK98whhsV/jGgIuwQCuTTWllmuqd0BuM0wNaQjGbZ685lSY4HeRYjm
JxqnWh6+12eEQQHA8Od0wxqAV17JS3YRMi6Ey9AkYSU0nTG29k0h8nDJeM4Kr7Rb
lXIv8QZnMA4GbEWKQmGxYiOe4iN56KIss2Kmm3fvSC7VCDbxMUU76CLuIBWk4tMA
5VRD+CoyA9wBTwoxXhIhPAV1P30qvT5foTOubY9TmmA7s21SiXLIXb4wgjpB6fzh
BD6wgCn/gnCIw+vl0gmwdzn0vIjv1mHCl7o+4+XL1dC9S0spRt3rP0l0MDRp4ab0
boOERUHJzVBjAsStR6vSB1QIwiP5fBF9mQEdvX3Lny1uCoBvwlzWWnHoEhnDrFqn
67Ou+Gr8ngJdr0CWqK/gZaDH8kNf2U0hBNlplcAcjzZNZA51a0Q=
=1CKz
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to