Your message dated Fri, 12 Jun 2020 10:51:03 +0000
with message-id <e1jjhh5-0007re...@fasolo.debian.org>
and subject line Bug#952171: fixed in yubico-pam 2.26-1.1
has caused the Debian Bug report #952171,
regarding yubico-pam: FTBFS: dh_auto_test: error: cd build && make -j4 check
VERBOSE=1 returned exit code 2
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.)
--
952171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yubico-pam
Version: 2.26-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<<PKGBUILDDIR>>/build/tests'
> PASS: util_test
> FAIL: pam_test
> ===========================================
> pam_yubico 2.26: tests/test-suite.log
> ===========================================
>
> # TOTAL: 2
> # PASS: 1
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: pam_test
> ==============
>
> YKVAL mockup started on 30559 at ../../tests/aux/ykval.pl line 52.
> YKVAL mockup started on 17502 at ../../tests/aux/ykval.pl line 52.
> LDAP mockup started at ../../tests/aux/ldap.pl line 101, <DATA> line 755.
> in pam_get_user()
> in pam_get_item() 5 for 0
> in conv_func()
> validation for vvincredibletrerdegkkrkkneieultcjdghrejjbckh (on port 17502)
> at ../../tests/aux/ykval.pl line 62, <GEN1> line 1.
> in pam_strerror()
> in pam_set_data() yubico_setcred_return
> test 1 failed!
> debug: ../pam_yubico.c:838 (parse_cfg): called.
> debug: ../pam_yubico.c:839 (parse_cfg): flags 0 argc 4
> debug: ../pam_yubico.c:841 (parse_cfg): argv[0]=id=1
> debug: ../pam_yubico.c:841 (parse_cfg):
> argv[1]=url=http://localhost:17502/wsapi/2/verify?id=%d&otp=%s
> debug: ../pam_yubico.c:841 (parse_cfg):
> argv[2]=authfile=../../tests/aux/authfile
> debug: ../pam_yubico.c:841 (parse_cfg): argv[3]=debug
> debug: ../pam_yubico.c:842 (parse_cfg): id=1
> debug: ../pam_yubico.c:843 (parse_cfg): key=(null)
> debug: ../pam_yubico.c:844 (parse_cfg): debug=1
> debug: ../pam_yubico.c:845 (parse_cfg): debug_file=1
> debug: ../pam_yubico.c:846 (parse_cfg): alwaysok=0
> debug: ../pam_yubico.c:847 (parse_cfg): verbose_otp=0
> debug: ../pam_yubico.c:848 (parse_cfg): try_first_pass=0
> debug: ../pam_yubico.c:849 (parse_cfg): use_first_pass=0
> debug: ../pam_yubico.c:850 (parse_cfg): nullok=0
> debug: ../pam_yubico.c:851 (parse_cfg): authfile=../../tests/aux/authfile
> debug: ../pam_yubico.c:852 (parse_cfg): ldapserver=(null)
> debug: ../pam_yubico.c:853 (parse_cfg): ldap_uri=(null)
> debug: ../pam_yubico.c:854 (parse_cfg): ldap_bind_user=(null)
> debug: ../pam_yubico.c:855 (parse_cfg): ldap_bind_password=(null)
> debug: ../pam_yubico.c:856 (parse_cfg): ldap_filter=(null)
> debug: ../pam_yubico.c:857 (parse_cfg): ldap_cacertfile=(null)
> debug: ../pam_yubico.c:858 (parse_cfg): ldapdn=(null)
> debug: ../pam_yubico.c:859 (parse_cfg): user_attr=(null)
> debug: ../pam_yubico.c:860 (parse_cfg): yubi_attr=(null)
> debug: ../pam_yubico.c:861 (parse_cfg): yubi_attr_prefix=(null)
> debug: ../pam_yubico.c:862 (parse_cfg):
> url=http://localhost:17502/wsapi/2/verify?id=%d&otp=%s
> debug: ../pam_yubico.c:863 (parse_cfg): urllist=(null)
> debug: ../pam_yubico.c:864 (parse_cfg): capath=(null)
> debug: ../pam_yubico.c:865 (parse_cfg): cainfo=(null)
> debug: ../pam_yubico.c:866 (parse_cfg): proxy=(null)
> debug: ../pam_yubico.c:867 (parse_cfg): token_id_length=12
> debug: ../pam_yubico.c:868 (parse_cfg): mode=client
> debug: ../pam_yubico.c:869 (parse_cfg): chalresp_path=(null)
> debug: ../pam_yubico.c:899 (pam_sm_authenticate): pam_yubico version: 2.26
> debug: ../pam_yubico.c:914 (pam_sm_authenticate): get user returned: foo
> debug: ../pam_yubico.c:157 (authorize_user_token): Using system-wide
> auth_file ../../tests/aux/authfile
> debug: ../util.c:154 (check_user_token): Authorization line: foo:vvincredible
> debug: ../util.c:159 (check_user_token): Matched user: foo
> debug: ../util.c:165 (check_user_token): Authorization token: vvincredible
> debug: ../util.c:165 (check_user_token): Authorization token: (null)
> debug: ../util.c:154 (check_user_token): Authorization line:
> test:cccccccfhcbe:ccccccbchvth:
> debug: ../pam_yubico.c:1034 (pam_sm_authenticate): Tokens found for user
> debug: ../pam_yubico.c:1096 (pam_sm_authenticate): conv returned 44 bytes
> debug: ../pam_yubico.c:1110 (pam_sm_authenticate): Skipping first 0 bytes.
> Length is 44, token_id set to 12 and token OTP always 32.
> debug: ../pam_yubico.c:1118 (pam_sm_authenticate): OTP:
> vvincredibletrerdegkkrkkneieultcjdghrejjbckh ID: vvincredible
> debug: ../pam_yubico.c:157 (authorize_user_token): Using system-wide
> auth_file ../../tests/aux/authfile
> debug: ../util.c:154 (check_user_token): Authorization line: foo:vvincredible
> debug: ../util.c:159 (check_user_token): Matched user: foo
> debug: ../util.c:165 (check_user_token): Authorization token: vvincredible
> debug: ../util.c:169 (check_user_token): Match user/token as foo/vvincredible
> debug: ../pam_yubico.c:1154 (pam_sm_authenticate): Token is associated to the
> user. Validating the OTP...
> debug: ../pam_yubico.c:1156 (pam_sm_authenticate): ykclient return value
> (109): Error performing curl
> debug: ../pam_yubico.c:1157 (pam_sm_authenticate): ykclient url used:
> debug: ../pam_yubico.c:1220 (pam_sm_authenticate): done. [error]
> killed 11463, 11464 and 11465
> FAIL pam_test (exit status: 1)
>
> ============================================================================
> Testsuite summary for pam_yubico 2.26
> ============================================================================
> # TOTAL: 2
> # PASS: 1
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
> ============================================================================
> See tests/test-suite.log
> ============================================================================
> make[4]: *** [Makefile:735: test-suite.log] Error 1
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/build/tests'
> make[3]: *** [Makefile:843: check-TESTS] Error 2
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/build/tests'
> make[2]: *** [Makefile:924: check-am] Error 2
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/build/tests'
> make[1]: *** [Makefile:785: check-recursive] Error 1
> make[1]: Leaving directory '/<<PKGBUILDDIR>>/build'
> dh_auto_test: error: cd build && make -j4 check VERBOSE=1 returned exit code 2
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/yubico-pam_2.26-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: yubico-pam
Source-Version: 2.26-1.1
Done: Adrian Bunk <b...@debian.org>
We believe that the bug you reported is fixed in the latest version of
yubico-pam, 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 952...@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 yubico-pam 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, 29 May 2020 17:37:57 +0300
Source: yubico-pam
Architecture: source
Version: 2.26-1.1
Distribution: unstable
Urgency: low
Maintainer: Debian Authentication Maintainers
<pkg-auth-maintain...@lists.alioth.debian.org>
Changed-By: Adrian Bunk <b...@debian.org>
Closes: 952171
Changes:
yubico-pam (2.26-1.1) unstable; urgency=low
.
* Non-maintainer upload.
* Add upstream fix for test failure. (Closes: #952171)
* Remove unnecessary manual library dependencies.
Checksums-Sha1:
4fc60b530fc204a5affb81d13fcbde193062edd2 2189 yubico-pam_2.26-1.1.dsc
35dc9cea5f02a3348e789c16badf1d1a71ff72c8 70204
yubico-pam_2.26-1.1.debian.tar.xz
Checksums-Sha256:
cb6421fda88706c5522732227765dc3aefa35f4c6068fc857e0b441e4d6ef32f 2189
yubico-pam_2.26-1.1.dsc
31cc622924f88d647a3166a3386a567ba643b5ba17447e0947c14af03f9f2fec 70204
yubico-pam_2.26-1.1.debian.tar.xz
Files:
8fde3768451294853652419c3856791b 2189 admin optional yubico-pam_2.26-1.1.dsc
48959ff960889b2dd405f12bc4c86006 70204 admin optional
yubico-pam_2.26-1.1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl7RH1EACgkQiNJCh6LY
mLG/0hAAqK431pJTZhZ0rIOFQUc3LAbU4DuiCxXKny7Kxrjd394T6IFBo2XopjSQ
YwQAc2iL2SvGnNlVTvM51n5Vq1dJ65t8dbtzfy7NYsTw9Ey643Kz8vXb7BWcOhbJ
oPR2Zo6KR7AiVzwBmGC6PSa0v3kB6ePtipG0DllF0o1PQ0PEl+xIgVGBH/65lm3D
I56AIr/3q6Ru5e0Ld+MH47UvsPrJ/Hn88OmJJZRnOC7ArO4D5nc56AH8uskF3Pqd
T3cT2hj5DZH3A/hqPVzlboHmBowdY/DFhfAuieuD8ZfJ1W1K4SEzyKqfDQnyafCt
vbvnwFuq1q8geExCSUTZXPAsfhFEh+Vd7MmD//zV672zPDzKA1OVXHdTQ/fZPtRS
aqQnrM61nml2yhKS3cOvh9PdxHgWfHKWD+dKtXkGbayo5TydJZndJLN3yiYb9Q1Z
DVjM2EB3VmAFmRC/YxwYz8NzCjIiLdFs8cSlCbEEoA+uCTGXB4cdc5nYwVPYOoZ/
xdB2YuSrI9hLlZuQ5CzCy1Ph6ExA4dEbThuE9Thc8b0Fiw8pjF/we5KkBVs7KYGy
OJne7VlVYQsV3VvphYDzfS+T03R9bK0clTFDT1C0BQG9NRJtECpLXmxmQdTEdXtm
vdSpl03o8MWQrNPtbO/y/FgBgEmjGMBX2w1xm5nYqw2E/8PcZBA=
=Sohm
-----END PGP SIGNATURE-----
--- End Message ---
