Your message dated Tue, 03 Jan 2023 01:36:34 +0000 with message-id <e1pcwee-00cs1b...@fasolo.debian.org> and subject line Bug#1027490: fixed in repopush 0.1.0-3 has caused the Debian Bug report #1027490, regarding repopush: FTBFS: dh_auto_test: error: make -j8 test 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.) -- 1027490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: repopush Version: 0.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<<PKGBUILDDIR>>' > [ -n "$SKIP_SHELLCHECK" ] || shellcheck -- 'repopush.sh' > > In repopush.sh line 103: > rsync $noop $v -az $delete -- "$locpath$path/" "$remote$path/" > ^---^ SC2248 (style): Prefer double quoting even when variables > don't contain special characters. > ^-- SC2248 (style): Prefer double quoting even when > variables don't contain special characters. > > Did you mean: > rsync "$noop" "$v" -az $delete -- "$locpath$path/" "$remote$path/" > > For more information: > https://www.shellcheck.net/wiki/SC2248 -- Prefer double quoting even when > v... > make[3]: *** [Makefile:79: test-shellcheck] Error 1 > make[3]: Leaving directory '/<<PKGBUILDDIR>>' > make[2]: *** [Makefile:75: test] Error 2 > make[2]: Leaving directory '/<<PKGBUILDDIR>>' > dh_auto_test: error: make -j8 test returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2023/01/01/repopush_0.1.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results 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! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---Source: repopush Source-Version: 0.1.0-3 Done: Peter Pentchev <r...@debian.org> We believe that the bug you reported is fixed in the latest version of repopush, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev <r...@debian.org> (supplier of updated repopush 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: Tue, 03 Jan 2023 02:52:54 +0200 Source: repopush Architecture: source Version: 0.1.0-3 Distribution: unstable Urgency: medium Maintainer: Peter Pentchev <r...@debian.org> Changed-By: Peter Pentchev <r...@debian.org> Closes: 1027490 Changes: repopush (0.1.0-3) unstable; urgency=medium . * Declare compliance with Policy 4.6.2 with no changes. * Add the years 2022 and 2023 to my debian/* copyright notice. * Explicitly specify dh-sequence-single-binary. * Add the rsync-unquoted patch to fix a FTBFS because of a new diagnostic message from shellcheck 0.9. Closes: #1027490 Checksums-Sha1: 7564da866943740888944f180bcc9b56b6da97fd 2415 repopush_0.1.0-3.dsc 02a82bba5851917333028dfc5b37d7e3531e5eb8 5536 repopush_0.1.0-3.debian.tar.xz Checksums-Sha256: 10ee475c03854b366960db98e4e34ade090337f32659ecc0bd171551d4279135 2415 repopush_0.1.0-3.dsc b8dce34528396ff9b4017d525fff08b5e6617d77f759c8d42f723b06c3a7c2fc 5536 repopush_0.1.0-3.debian.tar.xz Files: 3fab1d04c2744ae7f134c218371ab73a 2415 admin optional repopush_0.1.0-3.dsc 88eece44421f005d750ed297359ef528 5536 admin optional repopush_0.1.0-3.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmOzf5gQHHJvYW1AZGVi aWFuLm9yZwAKCRBlHu+wJSffE+wYEACnX3QUt7t384qFUwmG2gkyn0rRkQL0pNth Bv8BNXjFugLKUWz8MFj/ATxwb1Q0THb/LGtzpbgm0RElqVokrjZhnojjVp13HvW4 QZxxbLJXBy6MnSHvaENg5GZKqAXngbxQE1FPDFTBInS+48R89zcOmM/xdpUXSEeJ KA/4L2+nGDPlMwc4jg5cvCg38AbrHVVnl8+QfRfWkVjMHdKj47MHXWoR3PVGLYNB 3bDQeGInPVJ5jle4NbsekcVhX2NaykfgL4bUSsRvukokvCVG/27hV2ykO61IOnAp LYqR6fgOkRXceI71OvNacTtROTH0T0NfIO3uzIVXf8H/X13+2HqIUV76F2wTIdLN GH1TtXg7ckkDQZzJYCkVbfSVAHHkaue0iG76v7poSdZcy1BXSXp1ZVLYEUXTtC3B Fc8Md6vcMga39Y5h6zIz+RcBxS1KAsTdpFD1azD8bf5rFBBoOjeRKKWvuEyF1AcX cU+0NYJbBC0CAM67JkA44P9scGoAyymU0bPzBjS2p4yVzJtY1qEDbtSJYzEoiQYb ctc6QVFLV3tU5mWO54u9MtzpxdowBlhCRkezr5lKmraLEZOzzE1R4YLLr9d/KKWL 0XpykRxBZE6WGniDFTlZDtg/XoaRU9em8QMOH+ixBp0ixeJ0/h4/2mAEJgHtzmpI 8fSA6rEAQA== =7MwS -----END PGP SIGNATURE-----
--- End Message ---
