Your message dated Fri, 21 Sep 2018 07:19:42 +0000 with message-id <e1g3fj4-000a4s...@fasolo.debian.org> and subject line Bug#907819: fixed in jellyfish 2.2.10-1 has caused the Debian Bug report #907819, regarding jellyfish: Does not build on paths containing "-L" resulting in random FTBFS when built by sbuild 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.) -- 907819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: src:jellyfish Version: 2.2.8-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid and it failed with this error: -------------------------------------------------------------------------------- /usr/bin/ld: cannot find -ljellyfish-2.0 collect2: error: ld returned 1 exit status error: command 'x86_64-linux-gnu-g++' failed with exit status 1 -------------------------------------------------------------------------------- I'm building on amd64 and this error happens randomly for me (sometimes it fails, sometimes it does not), but it happened at least once in the official autobuilders in another architecture: https://buildd.debian.org/status/fetch.php?pkg=jellyfish&arch=powerpc&ver=2.2.8-3&stamp=1531093335&raw=0 so it seems that the error is not architecture-specific and we can assume it will also fail randomly on the official buildds too. I've put all my failed build logs (buster and sid) here: https://people.debian.org/~sanvila/build-logs/jellyfish/ (but some of those failures are not linking failures). If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
--- End Message ---
--- Begin Message ---Source: jellyfish Source-Version: 2.2.10-1 We believe that the bug you reported is fixed in the latest version of jellyfish, 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 907...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille <ti...@debian.org> (supplier of updated jellyfish 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: SHA256 Format: 1.8 Date: Fri, 21 Sep 2018 08:45:53 +0200 Source: jellyfish Binary: jellyfish libjellyfish-2.0-2 libjellyfish-2.0-dev libjellyfish-perl jellyfish-examples Architecture: source Version: 2.2.10-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team <debian-med-packag...@lists.alioth.debian.org> Changed-By: Andreas Tille <ti...@debian.org> Description: jellyfish - count k-mers in DNA sequences jellyfish-examples - count k-mers in DNA sequences (examples for testing) libjellyfish-2.0-2 - count k-mers in DNA sequences (dynamic library of jellyfish) libjellyfish-2.0-dev - count k-mers in DNA sequences (development files of jellyfish) libjellyfish-perl - count k-mers in DNA sequences (Perl bindings of jellyfish) Closes: 907819 Changes: jellyfish (2.2.10-1) unstable; urgency=medium . * New upstream version * Point Vcs fields to salsa.debian.org * Standards-Version: 4.1.4 * Adapt watch file to also catch v$VERSION tarball names * Clean up quilt patches * Catch exceptions by reference * Do not replace random '-L' strings in command line Closes: #907819 * Drop python3-dna-jellyfish package since the Python module had issues in build process and nobody seemed to be interested to help solving theses Checksums-Sha1: 0e5bdedd201409d6dccd4b9b3e8a50630e00c596 2466 jellyfish_2.2.10-1.dsc ff6da36047de84a94925623bd7355d467e58f4e9 677009 jellyfish_2.2.10.orig.tar.gz bc6a020795b7287796b9ad5d24c4cb5559eb8778 11856 jellyfish_2.2.10-1.debian.tar.xz Checksums-Sha256: ce72c4977a972d97810a3e1813cd2cf758691e6a2a0ca52ff8098716de074a0a 2466 jellyfish_2.2.10-1.dsc 49137356b1cdd014cb70e866f0739fc3fafea6421fa22cc64bcfeba55fc1dc27 677009 jellyfish_2.2.10.orig.tar.gz 9dc571e8a0666d4e4755169f35f88e25b2f9d5100fa60257055ce55ff5375e08 11856 jellyfish_2.2.10-1.debian.tar.xz Files: 521f5071f06a1ef8a782cc376c8386cd 2466 science optional jellyfish_2.2.10-1.dsc f500fe1a92299b41524e508580cd1192 677009 science optional jellyfish_2.2.10.orig.tar.gz f092157cd0590d11adb1f8e5c5f7557d 11856 science optional jellyfish_2.2.10-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlukl8URHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHxrA/9En29WH6tK3Ebl6RGx6Bc4YCsrVYrCW36 peBaTWrrdoHYTRm+pzn2IbRGXOF3uAITWJUttBX+h1C6+KPKpyZS3BZWPFDpS1jY Ld76ILMAkHFdgqY2g70COC139MBDvBznYO8LX0O2HB498YitwMQBh4OOicRq8Ddh DzCBETyAABTjetm1VNORcWTLJpuJR+FehK8HhkBRit2FhOGNjV74wRweJ5OSLczk PU9F68nGe6wX0EwP+VMU5+6oDS8hTL8C+1QLHrauT2ekHJQcK9jDkzgF6xZf7Zlq 03zn30YuBBlCoc/YaVFYz86r5B+6dta914+vCpm87nORFD00xcPraeOU//6q1ic+ MI5aTqZX3IQ3JEm8e2N8UIeW9Reldh6BKtg+VH588Fu8wpH026CuQhjyUhMvOdUi ZRUCtX8S0PCQD9WQvUrQZ4PdMv+u3UeihJsP157JL9rV0H0707mAyYF5BOd3M6VU YaICv9JPS27drsdW86sDIBORT0Jwd84dYrebxb+N12CQh5y5s+kB9CT9dL0DiWhd MrL07e4Eb0esd26CSCElP7TXdL8W6kg/+oMhsb9QiyxDHEaDFOGZZ4f7E6Sm9Mhy 4Ee4yR2kI7dhw5Wz5L5psBp0hjDvMAL57ReNn03go8KN2Qj4ehiuzIwZ6pVDpWKu 6OsZcTthoi0= =sMBR -----END PGP SIGNATURE-----
--- End Message ---
