Your message dated Thu, 27 Feb 2020 07:07:49 +0100
with message-id <[email protected]>
and subject line Closing
has caused the Debian Bug report #952622,
regarding procps does not provide /bin/kill - violates FHS specification
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 [email protected]
immediately.)
--
952622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952622
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: myproxy
Version: 6.2.6-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200225 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules).
Relevant part (hopefully):
> make[5]: Entering directory '/<<PKGBUILDDIR>>'
> FAIL: myproxy-test-wrapper
> =====================================
> myproxy 6.2.6: ./test-suite.log
> =====================================
>
> # TOTAL: 1
> # PASS: 0
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: myproxy-test-wrapper
> ==========================
>
> MyProxy Test 1 (store credential with default name): SUCCEEDED
> MyProxy Test 2 (get info for stored credential): SUCCEEDED
> MyProxy Test 3 (retrieve stored credential): SUCCEEDED
> MyProxy Test 3- (retrieve stored credential to stdout): SUCCEEDED
> MyProxy Test 3N (authenticate w/o retrieving credential): SUCCEEDED
> MyProxy Test 3T (retrieve stored credential w/ trustroots): SUCCEEDED
> MyProxy Test 3R1 (retrieve stored credential after server reconfig): SUCCEEDED
> MyProxy Test 3R2 (retrieve stored credential after server reconfig): SUCCEEDED
> MyProxy Test 3R3 (retrieve stored credential after server reconfig): SUCCEEDED
> MyProxy Test 4 (verify passphrase checking on retrieve): SUCCEEDED
> MyProxy Test 4N (verify passphrase checking on authenticate): SUCCEEDED
> MyProxy Test 5 (change passphrase for credential): SUCCEEDED
> MyProxy Test 6 (verify new passphrase): SUCCEEDED
> MyProxy Test 7 (verify old passphrase fails): SUCCEEDED
> MyProxy Test 8 (verify default renewal policy): SUCCEEDED
> MyProxy Test 9 (remove credential from repository): SUCCEEDED
> MyProxy Test 10 (verify credentials are removed): SUCCEEDED
> sh: 1: exec: /bin/kill: not found
> MyProxy Test 10.a (kill -HUP 17810): FAILED with 32512
> MyProxy Test 11 (store credentials with retrieval policies): SUCCEEDED
> MyProxy Test 12 (verify retrieval policies): SUCCEEDED
> MyProxy Test 13 (store credentials with renewal policies): SUCCEEDED
> MyProxy Test 14 (get info for stored renewal credentials): SUCCEEDED
> MyProxy Test 15 (verify renewal policies): SUCCEEDED
> MyProxy Test 16 (verify lifetime of retrieved credentials): SUCCEEDED
> MyProxy Test 17 (store credential with default name): SUCCEEDED
> MyProxy Test 18 (get info for stored credential): SUCCEEDED
> MyProxy Test 19 (create proxy from stored credential): SUCCEEDED
> MyProxy Test 20 (retrieve stored credential): SUCCEEDED
> MyProxy Test 20T (retrieve stored credential w/ trustroots): SUCCEEDED
> sh: 1: exec: /bin/kill: not found
> MyProxy Test 20.a (kill -HUP 17810): FAILED with 32512
> MyProxy Test 21 (verify passphrase checking on myproxy-logon): SUCCEEDED
> MyProxy Test 22 (verify passphrase checking on myproxy-retrieve): SUCCEEDED
> MyProxy Test 23 (verify myproxy-logon default renewal policy): SUCCEEDED
> MyProxy Test 24 (verify myproxy-retrieve default renewal policy): SUCCEEDED
> MyProxy Test 25 (remove credential from repository): SUCCEEDED
> MyProxy Test 26 (verify credentials are removed): SUCCEEDED
> MyProxy Test 27 (store credentials with retrieval policies): SUCCEEDED
> MyProxy Test 28 (verify myproxy-logon retrieval policies): SUCCEEDED
> MyProxy Test 29 (verify myproxy-retrieve retrieval policies): SUCCEEDED
> MyProxy Test 30 (store credentials with renewal policies): SUCCEEDED
> sh: 1: exec: /bin/kill: not found
> MyProxy Test 30.a (kill -HUP 17810): FAILED with 32512
> MyProxy Test 31 (get info for stored renewal credentials): SUCCEEDED
> MyProxy Test 32 (verify renewal policies): SUCCEEDED
> MyProxy Test 33 (verify lifetime of retrieved credentials): SUCCEEDED
> MyProxy Test 34 (store credentials with retrieve key policies): SUCCEEDED
> MyProxy Test 35 (get info for stored retrieve key credentials): SUCCEEDED
> MyProxy Test 36 (verify myproxy-retrieve key retrieval policies): SUCCEEDED
> MyProxy Test 37 (store credentials w/ retrievable_by_cert policies): SUCCEEDED
> MyProxy Test 38 (verify retrievable_by_cert policies): SUCCEEDED
> MyProxy Test 39 (verify limited proxy retrieves a limited proxy): SUCCEEDED
> MyProxy Test 40 (verify renewed limited proxy is still limited): SUCCEEDED
> sh: 1: exec: /bin/kill: not found
> MyProxy Test 40.a (kill -HUP 17810): FAILED with 32512
> MyProxy Test 41 (retrieve trustroots w/o authentication): SUCCEEDED
> MyProxy Test 42 (check_multiple_credentials): SUCCEEDED
> MyProxy Test 43 (myproxy-admin-query): SUCCEEDED
> MyProxy Test 44 (myproxy.h): SKIPPED
> MyProxy Test 45 (verify long username handling): SUCCEEDED
> $COG_INSTALL_PATH undefined. Skipping Java CoG tests.
> MyProxy Tests Complete: 52 tests passed, 4 tests failed
> FAIL myproxy-test-wrapper (exit status: 4)
>
> ============================================================================
> Testsuite summary for myproxy 6.2.6
> ============================================================================
> # TOTAL: 1
> # PASS: 0
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
> ============================================================================
> See ./test-suite.log
> ============================================================================
> make[5]: *** [Makefile:1447: test-suite.log] Error 1
> make[5]: Leaving directory '/<<PKGBUILDDIR>>'
> make[4]: *** [Makefile:1555: check-TESTS] Error 2
> make[4]: Leaving directory '/<<PKGBUILDDIR>>'
> make[3]: *** [Makefile:1787: check-am] Error 2
> make[3]: Leaving directory '/<<PKGBUILDDIR>>'
> make[2]: *** [Makefile:1332: check-recursive] Error 1
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_test: error: make -j4 check VERBOSE=1 VERBOSE=1 returned exit code 2
The full build log is available from:
http://qa-logs.debian.net/2020/02/25/myproxy_6.2.6-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 ---
signature.asc
Description: This is a digitally signed message part
--- End Message ---
