Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 787234 + pending Bug #787234 [src:cython] cython: FTBFS on arm64, armel, armhf, mipsel Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 787234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#794993: libsnappy1: library transition may be needed when GCC 5 is the default
Processing commands for cont...@bugs.debian.org: forcemerge 791289 794993 Bug #791289 [release.debian.org] snappy: library transition may be needed when GCC 5 is the default Unable to merge bugs because: package of #794993 is 'src:snappy' not 'release.debian.org' Failed to forcibly merge 791289: Did not alter merged bugs. thanks Stopping processing here. Please contact me if you need assistance. -- 791289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791289 794993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794993: libsnappy1: library transition may be needed when GCC 5 is the default
forcemerge 791289 794993 thanks On Sun, Aug 09, 2015 at 07:52:37AM +0200, László Böszörményi wrote: It seems Matthias missed this C++ library transition. He did not; see #791289. I can upload the patch given there now if you want. --- debian/libsnappy1.symbols 2015-08-08 23:54:52.415075073 + +++ debian/libsnappy1/DEBIAN/symbols 2015-08-08 23:59:25.046660564 + @@ -1,5 +1,5 @@ libsnappy.so.1 libsnappy1 #MINVER# - _ZN6snappy10UncompressEPKcmPSs@Base 1.1.3 + _ZN6snappy10UncompressEPKcmPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.1.3 _ZN6snappy10UncompressEPNS_6SourceEPNS_4SinkE@Base 1.1.3 _ZN6snappy11RawCompressEPKcmPcPm@Base 1.1.3 _ZN6snappy13RawUncompressEPKcmPc@Base 1.1.3 Surely you cannot patch things in DEBIAN/. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791121: marked as done (libgenome: library transition may be needed when GCC 5 is the default)
Your message dated Sun, 09 Aug 2015 10:00:16 + with message-id e1zonoq-0008qh...@franck.debian.org and subject line Bug#791121: fixed in libgenome 1.3.1-8 has caused the Debian Bug report #791121, regarding libgenome: library transition may be needed when GCC 5 is the default 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.) -- 791121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libgenome Version: 1.3.1-7 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for BEGIN GCC CXX11 in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition ---End Message--- ---BeginMessage--- Source: libgenome Source-Version: 1.3.1-8 We believe that the bug you reported is fixed in the latest version of libgenome, 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 791...@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 libgenome 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: Sat, 08 Aug 2015 18:56:32 +0200 Source: libgenome Binary: libgenome-1.3-dev libgenome-1.3-0v5 Architecture: source amd64 Version: 1.3.1-8 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Andreas Tille ti...@debian.org Description: libgenome-1.3-0v5 - toolkit for developing bioinformatic related software libgenome-1.3-dev - toolkit for developing bioinformatic related software (devel) Closes: 791121 Changes: libgenome (1.3.1-8) unstable; urgency=medium . * d/rules: drop unneeded override libgomp1-dev * Rename library packages for g++5 ABI
Bug#794993: libsnappy1: library transition may be needed when GCC 5 is the default
On Sun, Aug 9, 2015 at 11:41 AM, Steinar H. Gunderson sgunder...@bigfoot.com wrote: On Sun, Aug 09, 2015 at 07:52:37AM +0200, László Böszörményi wrote: I can upload the patch given there now if you want. Please do. It would be nice if you switch to the 3.0 (quilt) source format as well. --- debian/libsnappy1.symbols 2015-08-08 23:54:52.415075073 + +++ debian/libsnappy1/DEBIAN/symbols 2015-08-08 23:59:25.046660564 + @@ -1,5 +1,5 @@ libsnappy.so.1 libsnappy1 #MINVER# - _ZN6snappy10UncompressEPKcmPSs@Base 1.1.3 + _ZN6snappy10UncompressEPKcmPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.1.3 _ZN6snappy10UncompressEPNS_6SourceEPNS_4SinkE@Base 1.1.3 _ZN6snappy11RawCompressEPKcmPcPm@Base 1.1.3 _ZN6snappy13RawUncompressEPKcmPc@Base 1.1.3 Surely you cannot patch things in DEBIAN/. Please read my mail again: see the attached symbols change, it's not a thing you need to apply - it's the evidence it needs the transition. The proposed NMU is in the other file, in snappy_1.1.3-1_to_1.1.3-1.1.patch (debdiff). Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791126: marked as done (libgtextutils: library transition may be needed when GCC 5 is the default)
Your message dated Sun, 09 Aug 2015 10:00:17 + with message-id e1zonor-0008rl...@franck.debian.org and subject line Bug#791126: fixed in libgtextutils 0.7-3 has caused the Debian Bug report #791126, regarding libgtextutils: library transition may be needed when GCC 5 is the default 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.) -- 791126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libgtextutils Version: 0.7-2 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for BEGIN GCC CXX11 in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition ---End Message--- ---BeginMessage--- Source: libgtextutils Source-Version: 0.7-3 We believe that the bug you reported is fixed in the latest version of libgtextutils, 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 791...@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 libgtextutils 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: Sat, 08 Aug 2015 18:26:26 +0200 Source: libgtextutils Binary: libgtextutils-dev libgtextutils0v5 Architecture: source amd64 Version: 0.7-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Andreas Tille ti...@debian.org Description: libgtextutils-dev - Gordon Text_utils library (development files) libgtextutils0v5 - Gordon Text_utils library Closes: 791126 Changes: libgtextutils (0.7-3) unstable; urgency=medium . * Rename library packages for g++5 ABI transition. (thanks for the patch to Steve Langasek
Processed: Re: Bug#794987: mercurial-git: failed to import extension hgext.git: No module named ignore
Processing control commands: forwarded -1 https://bitbucket.org/durin42/hg-git/issues/157/hg-git-081-doesnt-work-under-mercurial-35 Bug #794987 [mercurial-git] mercurial-git: failed to import extension hgext.git: No module named ignore Set Bug forwarded-to-address to 'https://bitbucket.org/durin42/hg-git/issues/157/hg-git-081-doesnt-work-under-mercurial-35'. -- 794987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794987: mercurial-git: failed to import extension hgext.git: No module named ignore
Control: forwarded -1 https://bitbucket.org/durin42/hg-git/issues/157/hg-git-081-doesnt-work-under-mercurial-35 On Sat, Aug 08, 2015 at 10:04:18PM -0400, James McCoy wrote: Package: mercurial-git Version: 0.8.1-2 Severity: important In a repository using hg-git: $ hg status *** failed to import extension hgext.git: No module named ignore ** unknown exception encountered, please report by visiting ** http://mercurial.selenic.com/wiki/BugTracker ** Python 2.7.10 (default, Jul 1 2015, 10:54:53) [GCC 4.9.2] ** Mercurial Distributed SCM (version 3.5) ** Extensions loaded: color, graphlog, hgk, strip, mq, pager, purge, record, rebase, histedit, gpg Traceback (most recent call last): File /usr/bin/hg, line 43, in module mercurial.dispatch.run() File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 30, in run sys.exit((dispatch(request(sys.argv[1:])) or 0) 255) File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 92, in dispatch ret = _runcatch(req) File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 163, in _runcatch return _dispatch(req) File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 862, in _dispatch repo = hg.repository(ui, path=path) File /usr/lib/python2.7/dist-packages/mercurial/hg.py, line 136, in repository peer = _peerorrepo(ui, path, create) File /usr/lib/python2.7/dist-packages/mercurial/hg.py, line 123, in _peerorrepo obj = _peerlookup(path).instance(ui, path, create) File /usr/lib/python2.7/dist-packages/mercurial/hg.py, line 93, in _peerlookup return thing(path) File /usr/lib/python2.7/dist-packages/hgext/git/__init__.py, line 84, in _local p = urlcls(path).localpath() TypeError: 'NoneType' object is not callable Argh, yes, mercurial-git 0.8.1 doesn't work with hg 3.5. When I uploaded mercurial-git 0.8.1-2, I thought the breaks in mercurial would still be valid (but I didn't check it, and I should have). Sorry for that. I was waiting for a new version of mercurial-git to be released, but given that I've already broken it, I may backport the fix and release a 0.8.1-3 that is compatible with mercurial 3.5. Cheers, Javi signature.asc Description: Digital signature
Bug#787234: marked as done (cython: FTBFS on arm64, armel, armhf, mipsel)
Your message dated Sun, 09 Aug 2015 10:19:39 + with message-id e1zonhb-0007mb...@franck.debian.org and subject line Bug#787234: fixed in cython 0.22.1-2 has caused the Debian Bug report #787234, regarding cython: FTBFS on arm64, armel, armhf, mipsel 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.) -- 787234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: cython Version: 0.22+git62-g9aaa667-1 It failed to build on some architectures: https://buildd.debian.org/status/package.php?p=cythonsuite=sid I think one of the tests is taking too long on some machines: Build killed with signal TERM after 150 minutes of inactivity You could disable the test that takes so long, modify it to take less time, get the test to print something as it runs, to avoid inactivity, or the parallelisation (bug #750841) might help if other shorter tests then run at the same time, generating output. It built for me on arm64 when I left it running overnight with no time-out. ---End Message--- ---BeginMessage--- Source: cython Source-Version: 0.22.1-2 We believe that the bug you reported is fixed in the latest version of cython, 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 787...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher sramac...@debian.org (supplier of updated cython 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: Sun, 09 Aug 2015 11:02:35 +0200 Source: cython Binary: cython cython-dbg cython3 cython3-dbg cython-doc Architecture: source all Version: 0.22.1-2 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team python-apps-t...@lists.alioth.debian.org Changed-By: Sebastian Ramacher sramac...@debian.org Description: cython - C-Extensions for Python cython-dbg - C-Extensions for Python - debug build cython-doc - C-Extensions for Python - documentation cython3- C-Extensions for Python 3 cython3-dbg - C-Extensions for Python 3 - debug build Closes: 787234 Changes: cython (0.22.1-2) unstable; urgency=medium . * Team upload. * debian/rules: Redirect output of testsuite from stderr to stdout. sbuild currently does not check for output on stderr when deciding if a build timed out (see #731940 for details). This caused the build of cython to be killed on slower architectures. (Closes: #787234) * debian/control: Bump Standards-Version. No changes required. Checksums-Sha1: 96bd31133c9745015344c6e7a95e23c8b514f706 2337 cython_0.22.1-2.dsc aff6c3a0f009cbef999f9c852931b467e3f3e74f 22352 cython_0.22.1-2.debian.tar.xz 4b404cc5033dcb04d2bb1db22923b24c3f644b29 438444 cython-doc_0.22.1-2_all.deb Checksums-Sha256: 33531c23c257b53014e6ad4cd5cbd4bd45bf1a2326ed2a0f2cac242d4b2a8a11 2337 cython_0.22.1-2.dsc 457e14a2dd26d7f6940b8bdbc585d03e1434c295fb139e98808481addf9277c1 22352 cython_0.22.1-2.debian.tar.xz c9b8bc94843e764e8b68178c112908c3a6c96b3359de9cb129d9556995be6eda 438444 cython-doc_0.22.1-2_all.deb Files: 2f24461c2526204dd7c1301d349a0a26 2337 python optional cython_0.22.1-2.dsc 39623f353b045f51f959b916ad29a2ce 22352 python optional cython_0.22.1-2.debian.tar.xz e43cf90db31c504d28c0596c76c9 438444 doc optional cython-doc_0.22.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVxyTNAAoJEGny/FFupxmTa6MQAK5MUTsxQaZS0VX+kIxTOv5R Em9anhEs1+nmaxv1aRAjsO23y9tUeMv+9DeSSuXWbnsQxJPg4SazIHOJ3+IJDrPE 6CNpsVY6p+3TivbrZl8JTXbktvpLdNpMwst2YuRIpwWhQ7Ifg0tL9JEdn8CJyFmK +lmbBaSEfuyJ7OmcN9V7V8Q0mHqpNpvlo5spwsjT/BwcVhlAfq3rxgNFTV5xJOXy +rqrAYcWhd8m535O8GnPzrbIE+k+mu5I3uox/oubWZntgrmBF0fSC42wNunH1hOZ IQ+Pp1laKnZWe//tdY9kuwbj1GAGOEhS37Ldw6dirN3l7PnLZF7qirlshC9kJtCf khjae1vENEboUCcO1ITYkWdY2QRbB65Uoq2EOWSCtXhPJ7kCsmLmB4yNQ5pdd0z0 gqq/Tiowzxc6mP/lxzLbrC8WefT1OaXvjT1aHDqE+rM+0F5JUWY2Z73YzErHtwKP 5VVEMpvMH2LltffAU3/ukbF6rSWRlTenoaSC5I15tU3YuNqd/ZITACkkqg/w0xwF Eff93MbmtMeCHD+TFClo9uksWAWIUDOJ3dyNdt3O7jLOS2SIG74L8AXKl4rudGRs 8jfSCGMvPBo+BdLdMjHMS3oXTzqR9Rf4d2t7k2U2d/Qaj2YIXQTHnt4knuGC3mTV 4Uo0MtdDqGU3rkorj222 =ja1p -END PGP SIGNATUREEnd Message---
Bug#795002: nmu: motion
Hi Sebastian, 2015-08-09 11:59 GMT+02:00 Sebastian Ramacher sramac...@debian.org: On 2015-08-09 10:57:23, Balint Reczey wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Dear Release Team, Motion seems to be built in an outdated chroot for the upload. Please rebuild it to use the latest version of libav.*-dev packages which are now built from ffmpeg. nmu motion_3.2.12+git20140228-6 . amd64 . unstable . -m Rebuild against ffmpeg This will produce a build without any ffmpeg support at all. All the binaries from the buildds lack dependencies on the libraries from ffmpeg. motion needs a source upload fixing the ffmpeg detection. Thanks for pointing that out. I have added this bug to the ffmpeg transition wiki [1]. Are there similar issues? I'm preparing a delayed NMU for taoframework to help the transition finish. Ximin, thanks for fixing the motion issue. Cheers, Balint [1] https://wiki.debian.org/Debate/libav-provider/ffmpeg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794686: nslcd start script does not report starting failure
Control: tags -1 + pending On Wed, 2015-08-05 at 20:02 +0300, Nikolay Shaplov wrote: Package: nslcd Version: 0.9.4-3 Severity: serious Justification: fails to build from source Justification is not right but the init script return code is not according to policy so I'll leave it at serious. # /etc/init.d/nslcd stop [ ok ] Stopping nslcd (via systemctl): nslcd.service. # /etc/init.d/nslcd start [ ok ] Starting nslcd (via systemctl): nslcd.service. It does not report any problem, not to the console, not to the syslog It does report a problem to stderr but systemd seems to hide it when the return code is 0 (that was incorrect). The fix is to remove the last exit 0 from /etc/init.d/nslcd. Thanks for reporting this. -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Bug#778039: Patch for GCC 5 build issue
Hello The following commit should fix the build warnings https://github.com/OoliteProject/oolite/commit/80835961e0d0fad8c9dd1bfbd26706808360c66f The commit is to 1.82's version of the files but other than which lines are being patched there shouldn't be any difference to what's needed for 1.77.1 I don't believe this to actually be a security issue - in all five lines the format string is an NSString literal which should be just as safe as a C-string literal. Thanks -- Chris -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#794686: nslcd start script does not report starting failure
Processing control commands: tags -1 + pending Bug #794686 [nslcd] nslcd start script does not report starting failure Added tag(s) pending. -- 794686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#795002: nmu: motion
Processing control commands: reassign -1 motion Bug #795002 [release.debian.org] nmu: motion Bug reassigned from package 'release.debian.org' to 'motion'. Ignoring request to alter found versions of bug #795002 to the same values previously set Ignoring request to alter fixed versions of bug #795002 to the same values previously set retitle -1 motion fails to detects newer ffmpeg and silently disables all ffmpeg features Bug #795002 [motion] nmu: motion Changed Bug title to 'motion fails to detects newer ffmpeg and silently disables all ffmpeg features' from 'nmu: motion' severity -1 serious Bug #795002 [motion] motion fails to detects newer ffmpeg and silently disables all ffmpeg features Severity set to 'serious' from 'normal' -- 795002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791168: libsidplay: diff for NMU version 1.36.59-7.1
Hi Jonathan, On Sat, Aug 8, 2015 at 4:54 PM, Jonathan Wiltshire j...@debian.org wrote: I've prepared an NMU for libsidplay (versioned as 1.36.59-7.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Thanks! But I had other things to apply and -8 is uploaded and just accepted. Cheers, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795004: FTBFS: rspec3: undefined method `color_enabled=' for #RSpec::Core::Config.. (NoMethodError)
Source: ruby-bogus Version: 0.1.5-3 Severity: serious Tags: sid stretch Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build, probably due to incompataility with rspec3: /tmp/buildd/ruby-bogus-0.1.5/spec/spec_helper.rb:12:in `block in top (required)': undefined method `color_enabled=' for #RSpec::Core::Configuration:0x0001637698 (NoMethodError) from /usr/lib/ruby/vendor_ruby/rspec/core.rb:97:in `configure' from /tmp/buildd/ruby-bogus-0.1.5/spec/spec_helper.rb:11:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /tmp/buildd/ruby-bogus-0.1.5/spec/bogus/clean_ruby_spec.rb:1:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke' from /usr/bin/rspec:4:in `main' Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-bogus.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 794975, tagging 794990, tagging 791741, tagging 791736, tagging 791730, tagging 790252 ...
Processing commands for cont...@bugs.debian.org:
tags 794975 + sid
Bug #794975 {Done: Sebastian Ramacher sramac...@debian.org} [mixxx] mixxx:
will FTBFS with unsatisfiable dependencies due to libstdc++ transition
Added tag(s) sid.
tags 794990 + sid
Bug #794990 [src:mrpt] mrpt: ftbfs with new libstdc++ ABI
Added tag(s) sid.
tags 791741 + sid
Bug #791741 [kdegraphics-mobipocket] FTBFS with GCC 5: changes to symbols file
Added tag(s) sid.
tags 791736 + sid
Bug #791736 [qdbm] FTBFS with GCC 5: changes to symbols file
Added tag(s) sid.
tags 791730 + sid
Bug #791730 [libopenraw] FTBFS with GCC 5: new symbols appeared in the symbols
file
Added tag(s) sid.
tags 790252 + sid
Bug #790252 [src:libpgf] libpgf: FTBFS with gcc-5 (symbols)
Added tag(s) sid.
tags 790284 + sid
Bug #790284 [src:ssm] ssm: FTBFS with and gcc-5 (symbols)
Added tag(s) sid.
tags 672390 + sid stretch
Bug #672390 [src:freqtweak] Please consider chaging dependency of libsigc++1.2
to 2.0
Added tag(s) sid and stretch.
tags 672391 + sid stretch
Bug #672391 [src:asc] Please consider chaging dependency of libsigc++1.2 to 2.0
Added tag(s) stretch and sid.
tags 770240 + sid stretch
Bug #770240 [src:libsigc++-1.2] libsigc++-1.2: Keep out of testing
Added tag(s) sid and stretch.
tags 789298 + sid stretch
Bug #789298 [src:htmlcxx] FTBFS with GCC 5
Added tag(s) stretch and sid.
reassign 794973 src:linux
Bug #794973 [linux-image-3.16] Upgrade to Jessie kernel 3.16 breaks Xserver
early in boot process with old nVidia card[Quadro NVS 440]
Warning: Unknown package 'linux-image-3.16'
Bug reassigned from package 'linux-image-3.16' to 'src:linux'.
No longer marked as found in versions 3.16.7.
Ignoring request to alter fixed versions of bug #794973 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
672390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672390
672391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672391
770240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770240
789298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789298
790252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790252
790284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790284
791730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791730
791736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791736
791741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791741
794973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794973
794975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794975
794990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793599: Bug 792599: dbconfig-common must be more robust during removal against packages not depending on command-line client
Control: tags -1 moreinfo Hi Andreas (and other interested parties) On Sat, 25 Jul 2015 13:08:32 +0200 Andreas Beckmann a...@debian.org wrote: Severity: serious User: debian...@lists.debian.org Usertags: piuparts during a test with piuparts I noticed your package fails to remove. Can you please elaborate on your test (and what you think is reasonable to expect)? I may be wrong, but it seems you are preseeding answers to the debconf questions of pdns/dbconfig-common which may be a little weird in this case. You are removing the mysql-server and still request the package in question to purge the database first. Also I believe you are using the non-interactive frontend (is that correct?) Anyways, we may have a difficult choice to make (please help). First the background ideas. 1) The idea of having the possibility of having the clients as a recommend instead of a depends is that the system admin may opt-out of dbconfig-common assistance and configure the package manually that depends on dbconfig-common to do the db configuration. Most packages don't need the client to operate, only dbconfig-common needs it for configuration (which may be skipped). But dbconfig-common shouldn't depend on all the different db clients that it supports, while that also pollutes the system. Unfortunately, once dbconfig-common is running, there is no way to install the required client on demand until bug 421055 [1] is fixed. 2) The idea of failing during removal/purge stems from the idea that you want the package that is removed to clean up e.g. any credentials still laying around and possibly also the database. If I would opt-in for this, I would want to be notified rather noisily when this fails; in dbconfig-common you currently get an error with accompanying question if you want to abort/retry/retry with questions/ignore. Also, if the package is configured with dbconfig-common, I would expect it to be possible to clean up with dbconfig-common. Remember that the database may not be on the same system as where the client should be running. Now, what you are requesting here is that we either break the first idea or the second and I am not sure which one to choose. An idea however, for installations (as in, during install) with the non-interactive frontend, dbconfig-common already defaults to ignore. I am not sure if it is a good work around for this case, but would it actually be acceptable for you and do you believe it solves your reported problem? Paul [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421055 signature.asc Description: OpenPGP digital signature
Processed: Re: Bug 792599: dbconfig-common must be more robust during removal against packages not depending on command-line client
Processing control commands: tags -1 moreinfo Bug #793599 [dbconfig-common] must be more robust during removal against packages not depending on command-line client Added tag(s) moreinfo. -- 793599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: forwarded 727245 http://sourceforge.net/p/abook/mailman/message/34358619/ Bug #727245 [abook] abook: Add an address to Abook with Mutt delete all phone numbers Set Bug forwarded-to-address to 'http://sourceforge.net/p/abook/mailman/message/34358619/'. thanks Stopping processing here. Please contact me if you need assistance. -- 727245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790975: fixed in afflib 3.7.6-4
The whole point of this transition is that the rebuilt library is not compatible. So it can't provide the old name and there can't be a transitional package. Cheers Julien On August 9, 2015 8:25:46 AM CEST, Eriberto Mota eribe...@debian.org wrote: Hi Julien, I applied your patch and I updated some symbols. However, I added a binary libafflib0 as transitional package to avoid break some packages. Is there any problem in doing that? I attached a debdiff between afflib-3.7.6-4 and 3.7.6-5. Thanks a lot in advance. Regards, Eriberto 2015-08-06 19:14 GMT-03:00 Eriberto eribe...@eriberto.pro.br: Hi Julien, Thanks a lot for your quick reply. I will wait 2 days to fix some symbols for ports. Regards, Eriberto 2015-08-06 18:08 GMT-03:00 Julien Cristau jcris...@debian.org: On Thu, Aug 6, 2015 at 22:55:32 +0200, Julien Cristau wrote: On Thu, Aug 6, 2015 at 17:44:32 -0300, Eriberto wrote: Hum... Sorry, can you detail for me how to proceed? Need I use v5? Yes, something like the patch below. ... except with the .symbols files fixed to refer to libafflib0v5 instead of libafflib0; sorry about that. Cheers, Julien -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#794466: Virtualbox might not be suitable for Stretch
On Sat, 2015-08-08 at 20:11 +0200, Markus Frosch wrote: Hi Gianfranco, thanks for your summary. Although I'm not involved in maintaining virtualbox, still a few thoughts: * What would that mean for Jessie updates? * Isn't that basically the same problem we have with MySQL, or even Iceweasel? So I think the question is either drop, or work with upstream releases, from which I'd personally prefer. Not sure about MySQL, but for Iceweasel, is it really like that ? From what I've known, there were trademark issues which led to the rebranding. I'm not sure how they handle vulnerabilities. But their release strategy is: ESR and Regular releases. Every security fix goes into the next Regular release, and also the ESR release. ESR is supported until the next ESR (31 = 38). So usually the Debian Mozilla team prefers the ESR branch for Debian stable. With VBox, they don't have an ESR model. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
Bug#794955: gperf: Embedded code copy with missing copyright
Hi, On 08/08/2015 08:52 PM, Hilko Bengen wrote: Can you tell me a reliable source for that copyright information? I found that information on the debian/copyright of the Debian texi2html which I expect should be a reliable source. Thanks for the quick reply! akira signature.asc Description: OpenPGP digital signature
Bug#794975: marked as done (mixxx: will FTBFS with unsatisfiable dependencies due to libstdc++ transition)
Your message dated Sun, 09 Aug 2015 09:39:14 + with message-id e1zon4u-hc...@franck.debian.org and subject line Bug#794975: fixed in mixxx 1.11.0~dfsg-5 has caused the Debian Bug report #794975, regarding mixxx: will FTBFS with unsatisfiable dependencies due to libstdc++ transition 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.) -- 794975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mixxx Version: 1.11.0~dfsg-4 Severity: serious Justification: fails to build from source (but built successfully in the past) User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Tags: patch A binNMU of mixxx failed to build from source prior to the transition from libvamp-hostsdk3 to libvamp-hostsdk3v5. It has not yet been retried, but when it is, it will likely stop at BD-Uninstallable or continue to fail, because it specifically build-depends on the old libvamp-hostsdk3. It is unusual to build-depend on library packages, because the corresponding -dev usually pulls them in, but I assume there is some special reason in this case. The attached patch appears to resolve this. I'm happy to NMU this (with the addition of this bug number) if necessary. Regards, S From a0156952b92336f21642a9cd31c317f933510919 Mon Sep 17 00:00:00 2001 From: Simon McVittie s...@debian.org Date: Sat, 8 Aug 2015 16:51:35 +0100 Subject: [PATCH] debian/control: change build-dependency on libvamp-hostsdk3 to libvamp-hostsdk3v5 for stdc++ transition --- debian/changelog | 8 debian/control | 2 +- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index f923767..d108522 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +mixxx (1.11.0~dfsg-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/control: change build-dependency on libvamp-hostsdk3 to +libvamp-hostsdk3v5 for stdc++ transition + + -- Simon McVittie s...@debian.org Sat, 08 Aug 2015 16:51:14 +0100 + mixxx (1.11.0~dfsg-4) unstable; urgency=medium * Team upload. diff --git a/debian/control b/debian/control index 6b63635..ae0e57f 100644 --- a/debian/control +++ b/debian/control @@ -30,7 +30,7 @@ Build-Depends: libsoundtouch-dev (= 1.5.0), libtag1-dev, libusb-1.0-0-dev, - libvamp-hostsdk3, + libvamp-hostsdk3v5, libvorbis-dev, pkg-config, portaudio19-dev, -- 2.5.0 ---End Message--- ---BeginMessage--- Source: mixxx Source-Version: 1.11.0~dfsg-5 We believe that the bug you reported is fixed in the latest version of mixxx, 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 794...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher sramac...@debian.org (supplier of updated mixxx 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: Sun, 09 Aug 2015 10:33:54 +0200 Source: mixxx Binary: mixxx mixxx-data Architecture: source all Version: 1.11.0~dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Sebastian Ramacher sramac...@debian.org Description: mixxx - Digital Disc Jockey Interface mixxx-data - Digital Disc Jockey Interface -- data files Closes: 794975 Changes: mixxx (1.11.0~dfsg-5) unstable; urgency=medium . * Team upload. * debian/control: - Remove libvamp-hostsdk3 from B-D. It is pulled in by vamp-pluin-sdk anyway. (Closes: #794975) - Bump Standards-Version (no changes needed). Checksums-Sha1: 8310d2ca07651b1830bbb983bf7df61ea2f724ba 2574 mixxx_1.11.0~dfsg-5.dsc 6dab4c1e052415d582584844277a950db6d942ef 15312 mixxx_1.11.0~dfsg-5.debian.tar.xz 96dd900d25bb498be728e177925e0f9d236476bf 4666500 mixxx-data_1.11.0~dfsg-5_all.deb Checksums-Sha256: ba49b062a52320a0a6720fc4b5a2724d93ffab0a71495f43eb44245e9e509005 2574 mixxx_1.11.0~dfsg-5.dsc 4cf2c326867b030e4d5531d57c28221d22b20097dfc04539e5fd48e612b32b64 15312 mixxx_1.11.0~dfsg-5.debian.tar.xz 95c3ce1b2809b76436eb4de0b2fd15b0e7e474e87a1a8eee39838ad67c239f4d 4666500
Bug#732723: cegui-mk2: Please upgrade OGRE dependency to 1.9 when upstream ready
Hi, On Sun, Aug 9, 2015 at 1:55 AM, Corey Hickey bugfoo...@fatooh.org wrote: Hi, This package is apparently not installable on sid now. 1. libcegui-mk2-0.7.6 requires libogre-1.8.0 2. libstdc++6 Breaks libogre-1.8.0 = 1.8.0+dfsg1-7+b1 Updating libogre-1.8.0 is apparently a wontfix: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791222 Can you please prepare a new upload as mentioned? I have prepared an upload¹, I am waiting it passes the NEW process. Hopefully in a couple of weeks it should be done. If it does not pass, I will upload a revision of 0.7.6. Regards, 1. https://ftp-master.debian.org/new/cegui-mk2_0.8.4-2.html -- Muammar El Khatib. Linux user: 403107. GPG Key = 71246E4A. http://muammar.me | http://proyectociencia.org ,''`. : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787178: RM: w3c-dtd-xhtml -- RoQA; superseded by w3c-sgml-lib
On 2015-07-26 20:41, Mathieu Malaterre wrote: Indeed something went wrong in #787178. Andreas, I am starring at the debdiff for wdg-html-validator in between 1.6.2-7 1.6.2-8. Here is what I see here: I very much appreciate your time for this QA upload but I believe something went wrong. Thanks again for your time. d/changelog being the only file changed ... that looks weird. I don't really remember what happened here, that changelog message does not really fit the bug, most probably I uploaded a (completely different and unrelated) source package from the wrong directory while I tried to fix some FTBFS or similar bug. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778059: marked as done (performous: ftbfs with GCC-5)
Your message dated Sun, 09 Aug 2015 13:20:48 + with message-id e1zoqwu-0003ep...@franck.debian.org and subject line Bug#778059: fixed in performous 1.0+git150721-1 has caused the Debian Bug report #778059, regarding performous: ftbfs with GCC-5 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.) -- 778059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:performous Version: 0.7.0+git20140715-2 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/performous_0.7.0+git20140715-2_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] ^ In file included from /usr/include/libxml++-2.6/libxml++/libxml++.h:53:0, from /«BUILDDIR»/performous-0.7.0+git20140715/game/songs.cc:15: /usr/include/libxml++-2.6/libxml++/parsers/saxparser.h:215:8: warning: 'templateclass class std::auto_ptr' is deprecated [-Wdeprecated-declarations] std::auto_ptr_xmlSAXHandler sax_handler_; ^ In file included from /usr/include/c++/5/memory:81:0, from /usr/include/boost/config/no_tr1/memory.hpp:21, from /usr/include/boost/smart_ptr/shared_ptr.hpp:27, from /usr/include/boost/shared_ptr.hpp:17, from /usr/include/boost/date_time/time_clock.hpp:17, from /usr/include/boost/thread/thread_time.hpp:9, from /usr/include/boost/thread/xtime.hpp:15, from /«BUILDDIR»/performous-0.7.0+git20140715/game/xtime.hh:4, from /«BUILDDIR»/performous-0.7.0+git20140715/game/animvalue.hh:4, from /«BUILDDIR»/performous-0.7.0+git20140715/game/songs.hh:3, from /«BUILDDIR»/performous-0.7.0+git20140715/game/songs.cc:1: /usr/include/c++/5/bits/unique_ptr.h:49:28: note: declared here templatetypename class auto_ptr; ^ In file included from /usr/include/libxml++-2.6/libxml++/libxml++.h:54:0, from /«BUILDDIR»/performous-0.7.0+git20140715/game/songs.cc:15: /usr/include/libxml++-2.6/libxml++/parsers/textreader.h:260:10: warning: 'templateclass class std::auto_ptr' is deprecated [-Wdeprecated-declarations] std::auto_ptrPropertyReader propertyreader; ^ In file included from /usr/include/c++/5/memory:81:0, from /usr/include/boost/config/no_tr1/memory.hpp:21, from /usr/include/boost/smart_ptr/shared_ptr.hpp:27, from /usr/include/boost/shared_ptr.hpp:17, from /usr/include/boost/date_time/time_clock.hpp:17, from /usr/include/boost/thread/thread_time.hpp:9, from /usr/include/boost/thread/xtime.hpp:15, from /«BUILDDIR»/performous-0.7.0+git20140715/game/xtime.hh:4, from /«BUILDDIR»/performous-0.7.0+git20140715/game/animvalue.hh:4, from /«BUILDDIR»/performous-0.7.0+git20140715/game/songs.hh:3, from /«BUILDDIR»/performous-0.7.0+git20140715/game/songs.cc:1: /usr/include/c++/5/bits/unique_ptr.h:49:28: note: declared here templatetypename class auto_ptr; ^ make[3]: Leaving directory '/«BUILDDIR»/performous-0.7.0+git20140715/obj-x86_64-linux-gnu' make[2]: *** [game/CMakeFiles/performous.dir/all] Error 2 CMakeFiles/Makefile2:661: recipe for target 'game/CMakeFiles/performous.dir/all' failed make[2]: Leaving directory
Processed: Re: Bug#794913: libphonenumber6: please use libboost-date-time 1.57 or 1.58 ASAP
Processing control commands: severity -1 normal Bug #794913 [libphonenumber6] libphonenumber6: please use libboost-date-time 1.57 or 1.58 ASAP Severity set to 'normal' from 'critical' retitle -1 libphonenumber6: please use libboost-date-time 1.57 or 1.58 Bug #794913 [libphonenumber6] libphonenumber6: please use libboost-date-time 1.57 or 1.58 ASAP Changed Bug title to 'libphonenumber6: please use libboost-date-time 1.57 or 1.58' from 'libphonenumber6: please use libboost-date-time 1.57 or 1.58 ASAP' -- 794913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794913: libphonenumber6: please use libboost-date-time 1.57 or 1.58 ASAP
Control: severity -1 normal Control: retitle -1 libphonenumber6: please use libboost-date-time 1.57 or 1.58 Simon McVittie was so kind to disable libphonenumber6 in evolution for now and rebuild the package with that. So I guess the severity of this can be lowered again, as this doesn't block updating anymore :) Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Processed: tagging 795010, reassign 795010 to w3c-dtd-xhtml ..., severity of 795010 is serious
Processing commands for cont...@bugs.debian.org: tags 795010 - moreinfo Bug #795010 [ftp.debian.org] RM: w3c-dtd-xhtml -- RoQA; superseded by w3c-sgml-lib Removed tag(s) moreinfo. reassign 795010 w3c-dtd-xhtml 1.2-4 Bug #795010 [ftp.debian.org] RM: w3c-dtd-xhtml -- RoQA; superseded by w3c-sgml-lib Bug reassigned from package 'ftp.debian.org' to 'w3c-dtd-xhtml'. Ignoring request to alter found versions of bug #795010 to the same values previously set Ignoring request to alter fixed versions of bug #795010 to the same values previously set Bug #795010 [w3c-dtd-xhtml] RM: w3c-dtd-xhtml -- RoQA; superseded by w3c-sgml-lib Marked as found in versions w3c-dtd-xhtml/1.2-4. retitle 795010 w3c-dtd-xhtml: should not be released with stretch - superseded by w3c-sgml-lib Bug #795010 [w3c-dtd-xhtml] RM: w3c-dtd-xhtml -- RoQA; superseded by w3c-sgml-lib Changed Bug title to 'w3c-dtd-xhtml: should not be released with stretch - superseded by w3c-sgml-lib' from 'RM: w3c-dtd-xhtml -- RoQA; superseded by w3c-sgml-lib' severity 795010 serious Bug #795010 [w3c-dtd-xhtml] w3c-dtd-xhtml: should not be released with stretch - superseded by w3c-sgml-lib Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 795010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795002: marked as done (motion fails to detects newer ffmpeg and silently disables all ffmpeg features)
Your message dated Sun, 09 Aug 2015 13:36:51 + with message-id e1zoqmr-dd...@franck.debian.org and subject line Bug#795002: fixed in motion 3.2.12+git20140228-7 has caused the Debian Bug report #795002, regarding motion fails to detects newer ffmpeg and silently disables all ffmpeg features 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.) -- 795002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Dear Release Team, Motion seems to be built in an outdated chroot for the upload. Please rebuild it to use the latest version of libav.*-dev packages which are now built from ffmpeg. nmu motion_3.2.12+git20140228-6 . amd64 . unstable . -m Rebuild against ffmpeg Cheers, Balint signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Source: motion Source-Version: 3.2.12+git20140228-7 We believe that the bug you reported is fixed in the latest version of motion, 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 795...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ximin Luo infini...@pwned.gg (supplier of updated motion 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: Sun, 09 Aug 2015 15:20:24 +0200 Source: motion Binary: motion Architecture: source amd64 Version: 3.2.12+git20140228-7 Distribution: unstable Urgency: medium Maintainer: Ximin Luo infini...@pwned.gg Changed-By: Ximin Luo infini...@pwned.gg Description: motion - V4L capture program supporting motion detection Closes: 795002 Changes: motion (3.2.12+git20140228-7) unstable; urgency=medium . * Block any future buggy builds that don't include ffmpeg. * Fix build against newer ffmpeg libraries. (Closes: #795002) * Enable pgsql and sdl support. Checksums-Sha1: d39d9b040a23de50bbf5ee9fad187d726ba6d85c 2082 motion_3.2.12+git20140228-7.dsc 331f3aff22ea107be64ef8088e769353d79890c5 64396 motion_3.2.12+git20140228-7.debian.tar.xz de962f45e0bb1e0317041904d641ff81ca806016 280176 motion_3.2.12+git20140228-7_amd64.deb Checksums-Sha256: 60b7da07dfa090a0aa7176038c21726342d000bc80a3ca4b539c018f5840802f 2082 motion_3.2.12+git20140228-7.dsc 8d1b0ae1f5d493f42a7d5c9cffea5deff310718e92061c0fd14695a145a909bf 64396 motion_3.2.12+git20140228-7.debian.tar.xz c1f6984b31a7c8395ab64b596f9f9d5c67a3e796d735e99a6c2150a7504dc1eb 280176 motion_3.2.12+git20140228-7_amd64.deb Files: 45efdbed094a4feb3d848594f9673b0b 2082 video optional motion_3.2.12+git20140228-7.dsc 7b6b26727f0adbf0b983e154b7bb6992 64396 video optional motion_3.2.12+git20140228-7.debian.tar.xz 906958b55b6611abecc59907998ce8de 280176 video optional motion_3.2.12+git20140228-7_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJVx1UsAAoJEIYN7zuPZQt5L8kP/jbZFr4Pzcxzg4EmdbQtD52U vYL686kYgikZ98YXYuTVBYEOfi7nraH9uFDCqmo9lOzY5DACbmAijvG+jM3lVaWN iuWktIiVMHEfrVEPbBOd23XupCxs32iY4bTw6WV7CNt7g+EFmoPfH/QF8qqD4ki+ fa8+mJ0dLSmI7LHcDJxjdVLVhdK0YKPWQ8gktegjx+JfWqlwsUAtUA4r+bJFt41z 71oGc2GKOMSfC+U54esnO4hUMzOvz5p6Sy8DbH29AGlOVOBT6b72KlX4IzeX7vvN QK56t5BqOW8BGT14W1yNnkPQwR8xHQUve5tZFKvupF6SUrZ/DaxYNqxiHJtW0x2f iI5s10QwXeNlQtwqtf7RsH7Ip5fUiOWU8WsG14VzgGbLDSmje7lingoPrnsy+jKf p5UJKQVbFcZ3p5ObaR2+W1fGRFzbFcOxn+pk8DbR4hdCFe3KDAL6AAYF2DyiIdtE 738MmJul+gRjWdqqgxkEjaM1K4FWUc3vasNPQ7aqyqJLFKmjTcfOaax24Tf85NNA 0ZFmzVvAjbaehTsOCWUwq1E3hx+gC2KbOr5nFRzkBUwc1uRMfTsxVUsGHw9NLBAn vqky+jEseFp/7iiqwg1IY+vEJYmrdpV16TWC84LnaVaSmzP559boE0j3tq2ZK63O Oo2/EjP8n5ClYkQjXP5J =nkv1 -END PGP SIGNATUREEnd Message---
Bug#794658: Debian Sid: unresolved dependencies (libphonenumber)
On Thu, 6 Aug 2015 17:33:27 +0200 Jordi Pujol Palomer jordipuj...@gmail.com wrote: Hello, dependencies have not been a problem for me, version 1.58 of that libraries was already installed. the real problem is on maven tests, the package compiled after modifying the file debian/maven.properties uncomment the line: #maven.test.skip=true I can confirm that the package builds fine against boost 1.58 and have fixed the issue with the tests. I will upload one more version of 6 with these fixes (essentially a binNMU + a one-liner patch for the tests), and then return to working on the upload of 7.0.8 that Matthias has suggested. Cheers, tony signature.asc Description: OpenPGP digital signature
Processed: tagging 794658
Processing commands for cont...@bugs.debian.org: tags 794658 + pending Bug #794658 [libphonenumber6] libphonenumber6: Debian Sid: unresolved dependencies for libboost* version 1.55 while 1.58 installled Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 794658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: unarchiving 782241
Processing commands for cont...@bugs.debian.org:
unarchive 782241
Bug #782241 {Done: Aurelien Jarno aure...@debian.org} [locales] locales: On
upgrade, generic locales as C.UTF-8 are lost in /etc/default/locale
Unarchived Bug 782241
thanks
Stopping processing here.
Please contact me if you need assistance.
--
782241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 782241 627219
Processing commands for cont...@bugs.debian.org:
forcemerge 782241 627219
Bug #782241 {Done: Aurelien Jarno aure...@debian.org} [locales] locales: On
upgrade, generic locales as C.UTF-8 are lost in /etc/default/locale
Bug #782241 {Done: Aurelien Jarno aure...@debian.org} [locales] locales: On
upgrade, generic locales as C.UTF-8 are lost in /etc/default/locale
Marked as found in versions eglibc/2.13-12 and eglibc/2.13-4.
Added tag(s) l10n.
Bug #636087 [locales] Cannot set /etc/default/locale to C.UTF-8 through
debconf; requires manual editing
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
Marked Bug as done
Marked Bug as done
Marked as fixed in versions glibc/2.19-18.
Marked as fixed in versions glibc/2.19-18.
Marked as found in versions glibc/2.19-17.
Marked as found in versions glibc/2.19-17.
Bug #627219 {Done: Aurelien Jarno aure...@debian.org} [locales] locales:
unable to set C.UTF-8 as default system locale
Merged 627219 636087 782241
thanks
Stopping processing here.
Please contact me if you need assistance.
--
627219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627219
636087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636087
782241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793855: marked as done (DoS, Shibboleth SP software crashes on well-formed but invalid XML (CVE-2015-0851))
Your message dated Sun, 09 Aug 2015 18:35:19 + with message-id e1zovrh-00059d...@franck.debian.org and subject line Bug#793855: fixed in xmltooling 1.3.3-2+deb6u1 has caused the Debian Bug report #793855, regarding DoS, Shibboleth SP software crashes on well-formed but invalid XML (CVE-2015-0851) 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.) -- 793855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: xmltooling Version: 1.3.3-2 Severity: serious Tags: security patch upstream Shibboleth Service Provider software contains a code path with an uncaught exception that can be triggered by an unauthenticated attacker by supplying well-formed but schema-invalid XML in the form of SAML metadata or SAML protocol messages. The result is a crash and so causes a denial of service. Updated versions of OpenSAML-C (V2.5.5) and XMLTooling-C (V1.5.5) are available that correct this bug. This vulnerability has been assigned CVE-2015-0851. Please mention the CVE ID in changelog when fixing this issue. References: * Bulletin http://shibboleth.net/community/advisories/secadv_20150721.txt * Fixing commit (xmltooling) https://git.shibboleth.net/view/?p=cpp-xmltooling.git;a=commitdiff;h=2d795c731e6729309044607154978696a87fd900 Cheers, Luca ---End Message--- ---BeginMessage--- Source: xmltooling Source-Version: 1.3.3-2+deb6u1 We believe that the bug you reported is fixed in the latest version of xmltooling, 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 793...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ferenc Wagner wf...@niif.hu (supplier of updated xmltooling 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: Mon, 03 Aug 2015 13:25:11 +0200 Source: xmltooling Binary: libxmltooling4 libxmltooling-dev xmltooling-schemas libxmltooling-doc Architecture: source i386 all Version: 1.3.3-2+deb6u1 Distribution: squeeze-lts Urgency: high Maintainer: Debian Shib Team pkg-shibboleth-de...@lists.alioth.debian.org Changed-By: Ferenc Wagner wf...@niif.hu Description: libxmltooling-dev - C++ XML parsing library with encryption support (development) libxmltooling-doc - C++ XML parsing library with encryption support (API docs) libxmltooling4 - C++ XML parsing library with encryption support (runtime) xmltooling-schemas - XML schemas for XMLTooling Closes: 793855 Changes: xmltooling (1.3.3-2+deb6u1) squeeze-lts; urgency=high . * Apply security fix from 1.5.5 for CVE-2015-0851 DoS (Closes: #793855): Shibboleth SP software crashes on well-formed but invalid XML Checksums-Sha1: 5a1fa43326d495f336d1d2e8cc03b2a9652f61f7 2227 xmltooling_1.3.3-2+deb6u1.dsc 394aecf4d6a79c10efb904b2fcac7f628cc65069 1475368 xmltooling_1.3.3.orig.tar.gz 10fc4644474eda0b36d308a997682a8a73c4c690 7667 xmltooling_1.3.3-2+deb6u1.diff.gz 620e21753fddffabd032ff59a17cf9ab6a387caf 750808 libxmltooling4_1.3.3-2+deb6u1_i386.deb 6f7c7d58478dc54874995e0239bc63ae5bf177ce 76678 libxmltooling-dev_1.3.3-2+deb6u1_i386.deb 0f62d4bf5ebab2e51210444cec3d49c3ac6a903b 13192 xmltooling-schemas_1.3.3-2+deb6u1_all.deb c8af5662305ee48ce08992f5ecc7c1bdf712757d 925394 libxmltooling-doc_1.3.3-2+deb6u1_all.deb Checksums-Sha256: 8ad622df200fd48e775cdb7986a423591200d5f92c3b68c85f6eaa6c66b86c26 2227 xmltooling_1.3.3-2+deb6u1.dsc 2e60c74aabdf56dc1bf1f92bfa1da1284198aa114d3174539b6ff1f02dc0599b 1475368 xmltooling_1.3.3.orig.tar.gz 6e13166e29c358471f47e20e17d72dc642c37c73016a9553822bf38bf9244c5a 7667 xmltooling_1.3.3-2+deb6u1.diff.gz 3a620155cea8b83d8a7caff781f7a2509bf9d55ee8c2e844ecd35c07f2c86a5d 750808 libxmltooling4_1.3.3-2+deb6u1_i386.deb 21d6e84e8f34a66bbdf154e6f54468bb49a34d5b02a56039719281993930d645 76678 libxmltooling-dev_1.3.3-2+deb6u1_i386.deb 079542a6478d107e5423dcfc75127d59dabbfc9981174db2fd7e205c810017e9 13192 xmltooling-schemas_1.3.3-2+deb6u1_all.deb 54fb67f10d8f72c0cb4115c45c5e687da74c328837385b58a6eca0f59d84c8c3 925394 libxmltooling-doc_1.3.3-2+deb6u1_all.deb Files: e75513fc98f82d050d6d946ad868bbd8 2227 libs extra xmltooling_1.3.3-2+deb6u1.dsc
Bug#790975: fixed in afflib 3.7.6-4
Sorry. You are right. I looked at each dependant package and no need notify the maintainers. Upload to unstable, closing the bug. Regards, Eriberto 2015-08-09 15:43 GMT-03:00 Eriberto eribe...@eriberto.pro.br: Hum... I understand but I prefer notify the maintainers. Thanks Julien! Regards, Eriberto 2015-08-09 14:01 GMT-03:00 Julien Cristau jcris...@debian.org: On Sun, Aug 9, 2015 at 10:42:29 -0300, Eriberto wrote: Hi Julien, Ok. I will do it: 1. Upload to experimental, without close the bug. 2. Notify all maintainers of dependent packages, allowing changes up to next Saturday. 3. In next Saturday, upload to unstable, closing the bug. 4. Notify all maintainers that uploaded their packages to experimental. 5. File bugs (FTBFS) against all dependent packages not updated in experimental. Thanks a lot for your help. I don't think that delay is necessary, uploading to sid right away should be just fine, we'll rebuild reverse dependencies as needed. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794937: Applications crash with phonon-backend-vlc
Am 09.08.2015 um 02:27 schrieb Lisandro Damián Nicanor Pérez Meyer: tag 794937 moreinfo thanks Hi Michael! I have just uploaded a new version, can you check it works for you? (and yes, you might need to wait for the gcc5 transition to be in a more advanced state :-/ ) Upgraded phonon to 4:4.8.3-1, crash still happens with phonon-backend-vlc -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#793991: [Pkg-pascal-devel] Bug#793991: lazarus: armel and armhf builds stall
Hi All, On Fri, 2015-07-31 at 12:07 +0200, Graham Inggs wrote: I tried a simpler package, ddrescueview [1], and instead of building the Debian package, I simply ran: lazbuild source/ddrescueview.lpi --bm=GNU/Linux Release As before, the build appeared to stall, and after hitting ctrl-c I noticed that in the background the build had actually completed successfully and there was a working 'ddrescueview' executable. I'll file a bug upstream. I tried this on porterbox abel and reproduced the issue. However I failed to completely understand it. It looks like it hangs when running ld.bfd. Indeed when pressing ctrl+z I got: (sid_armel-dchroot)abou@abel:~/ddrescueview-0.4~alpha2/source$ ps -elf | grep ddrescueview 0 T abou32221 27954 0 80 0 - 5412 signal 18:25 pts/100:00:00 lazbuild ddrescueview.lpi 0 T abou32232 32221 0 80 0 - 178 signal 18:25 pts/100:00:00 /usr/bin/fpc -B -MObjFPC -Schi -CX -Cirot -g -gl -XX -l -vewnhibq -Fl/opt/gnome/lib -Fu/usr/lib/lazarus/1.4.0/lcl/units/arm-linux/gtk2 -Fu/usr/lib/lazarus/1.4.0/lcl/units/arm-linux -Fu/usr/lib/lazarus/1.4.0/components/lazutils/lib/arm-linux -Fu/usr/lib/lazarus/1.4.0/packager/units/arm-linux -Fu/home/abou/ddrescueview-0.4~alpha2/source/ -dLCL -dLCLgtk2 ddrescueview.lpr 0 T abou32233 32232 4 80 0 - 4031 signal 18:25 pts/100:00:03 /usr/bin/ppcarm -B -MObjFPC -Schi -CX -Cirot -g -gl -XX -l -vewnhibq -Fl/opt/gnome/lib -Fu/usr/lib/lazarus/1.4.0/lcl/units/arm-linux/gtk2 -Fu/usr/lib/lazarus/1.4.0/lcl/units/arm-linux -Fu/usr/lib/lazarus/1.4.0/components/lazutils/lib/arm-linux -Fu/usr/lib/lazarus/1.4.0/packager/units/arm-linux -Fu/home/abou/ddrescueview-0.4~alpha2/source/ -dLCL -dLCLgtk2 ddrescueview.lpr 0 T abou32243 32233 5 80 0 - 17728 signal 18:25 pts/100:00:03 /usr/bin/ld.bfd --dynamic-linker=/lib/ld-linux.so.3 --gc-sections -L. -o ddrescueview link.res 0 S abou32249 27954 0 80 0 - 637 pipe_w 18:26 pts/100:00:00 grep ddrescueview when fg and then ctrl+c it seems to resume. I also recompiled lazbuild to get debug symbols, but then I do not have the issue anymore. I even stripped the newly build binary and did not have the issue. So maybe we need just to rebuild again? -- Cheers, Abou Al Montacir -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: log4cpp: diff for NMU version 1.0-4.1
Processing control commands: tag -1 patch pending Bug #791191 [src:log4cpp] log4cpp: library transition may be needed when GCC 5 is the default Added tag(s) patch and pending. -- 791191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791191: log4cpp: diff for NMU version 1.0-4.1
Control: tag -1 patch pending
Dear maintainer,
I've prepared an NMU for log4cpp (versioned as 1.0-4.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
Jonathan Wiltshire j...@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
diff -u log4cpp-1.0/debian/changelog log4cpp-1.0/debian/changelog
--- log4cpp-1.0/debian/changelog
+++ log4cpp-1.0/debian/changelog
@@ -1,3 +1,11 @@
+log4cpp (1.0-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename library packages for g++ 5 transition, patch
+from Ubuntu (see #791191)
+
+ -- Jonathan Wiltshire j...@debian.org Sun, 09 Aug 2015 19:34:17 +0100
+
log4cpp (1.0-4) unstable; urgency=low
* Add patch to fix FTBFS with gcc 4.3. Thanks to Barry deFreeze.
diff -u log4cpp-1.0/debian/control log4cpp-1.0/debian/control
--- log4cpp-1.0/debian/control
+++ log4cpp-1.0/debian/control
@@ -9,7 +9,7 @@
Package: liblog4cpp5-dev
Section: libdevel
Architecture: any
-Depends: liblog4cpp5 (= ${binary:Version})
+Depends: liblog4cpp5v5 (= ${binary:Version})
Conflicts: liblog4cpp4-dev, liblog4cpp3-dev, liblog4cpp1-dev, liblog4cpp-dev
Replaces: liblog4cpp4-dev, liblog4cpp3-dev, liblog4cpp1-dev, liblog4cpp-dev
Description: C++ library for flexible logging (development)
@@ -20,12 +20,12 @@
.
This package contains the log4cpp development files.
-Package: liblog4cpp5
+Package: liblog4cpp5v5
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
-Conflicts: liblog4cpp4, liblog4cpp3, liblog4cpp1c102
-Replaces: liblog4cpp4, liblog4cpp3, liblog4cpp0, liblog4cpp1c102
+Conflicts: liblog4cpp4, liblog4cpp3, liblog4cpp1c102, liblog4cpp5
+Replaces: liblog4cpp4, liblog4cpp3, liblog4cpp0, liblog4cpp1c102, liblog4cpp5
Description: C++ library for flexible logging (runtime)
Log for C++ is a library of C++ classes for flexible logging to files,
syslog and other destinations. It is modeled after the Log for
reverted:
--- log4cpp-1.0/debian/liblog4cpp5.install
+++ log4cpp-1.0.orig/debian/liblog4cpp5.install
@@ -1 +0,0 @@
-usr/lib/lib*.so.*
diff -u log4cpp-1.0/debian/rules log4cpp-1.0/debian/rules
--- log4cpp-1.0/debian/rules
+++ log4cpp-1.0/debian/rules
@@ -8,7 +8,7 @@
DEB_CONFIGURE_SCRIPT_ENV += LDFLAGS=-Wl,-z,defs -Wl,--as-needed -lpthread
DEB_DH_INSTALL_SOURCEDIR := debian/tmp
-configure/liblog4cpp5::
+configure/liblog4cpp5v5::
aclocal -I m4
autoconf
autoheader
only in patch2:
unchanged:
--- log4cpp-1.0.orig/debian/liblog4cpp5v5.install
+++ log4cpp-1.0/debian/liblog4cpp5v5.install
@@ -0,0 +1 @@
+usr/lib/lib*.so.*
signature.asc
Description: Digital signature
Processed: bug 794657 is forwarded to https://github.com/pry/pry/issues/1338
Processing commands for cont...@bugs.debian.org: forwarded 794657 https://github.com/pry/pry/issues/1338 Bug #794657 [pry] pry: broken with ruby-slop = 4.x Set Bug forwarded-to-address to 'https://github.com/pry/pry/issues/1338'. thanks Stopping processing here. Please contact me if you need assistance. -- 794657: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794909: marked as done (libcolpack0v5: missing Breaks/Replaces against libcolpack0)
Your message dated Sun, 09 Aug 2015 17:04:16 + with message-id e1zou1a-0001xu...@franck.debian.org and subject line Bug#794909: fixed in colpack 1.0.9-3.2 has caused the Debian Bug report #794909, regarding libcolpack0v5: missing Breaks/Replaces against libcolpack0 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.) -- 794909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libcolpack0v5 Version: 1.0.9-3.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package libcolpack0v5:amd64. Preparing to unpack .../libcolpack0v5_1.0.9-3.1_amd64.deb ... Unpacking libcolpack0v5:amd64 (1.0.9-3.1) ... dpkg: error processing archive /var/cache/apt/archives/libcolpack0v5_1.0.9-3.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libColPack.so.0.0.0', which is also in package libcolpack0:amd64 1.0.9-3 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libcolpack0v5_1.0.9-3.1_amd64.deb cheers, Andreas libcolpack0=1.0.9-3_libcolpack0v5=1.0.9-3.1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: colpack Source-Version: 1.0.9-3.2 We believe that the bug you reported is fixed in the latest version of colpack, 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 794...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Wiltshire j...@debian.org (supplier of updated colpack 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: Sun, 09 Aug 2015 17:51:36 +0100 Source: colpack Binary: libcolpack-dev libcolpack0v5 Architecture: source Version: 1.0.9-3.2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Jonathan Wiltshire j...@debian.org Description: libcolpack-dev - Specialized graph vertex coloring library, development files libcolpack0v5 - Specialized graph vertex coloring library, shared library Closes: 794909 Changes: colpack (1.0.9-3.2) unstable; urgency=medium . * Non-maintainer upload. * Add conflicts/replaces libcolpack0 (closes: #794909) Checksums-Sha1: 9ad593c2107d7c6e901ef3b629b5c0201b2b1b1f 2036 colpack_1.0.9-3.2.dsc 28fb74fa91600fe9d407a2ffd7346e8e7146bc65 5060 colpack_1.0.9-3.2.debian.tar.xz Checksums-Sha256: 78af1f1dcaea615e17bf2f48eb6046c31aef0ddc967b5d38cb136a517dec536e 2036 colpack_1.0.9-3.2.dsc a86c096f0875d4ffc9d0d4a9d6ce7e6853bd3686288af46cdaeed168f01c4ee3 5060 colpack_1.0.9-3.2.debian.tar.xz Files: 9e099d3f317e5c9fe10565ba41a19787 2036 libs optional colpack_1.0.9-3.2.dsc 347d31d5e214b69e88775bbd765e82c4 5060 libs optional colpack_1.0.9-3.2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIbBAEBCAAGBQJVx4YnAAoJEGN9Nzz68Z6g08MP+NIBBUu2134g7ZLXCFt+tbdC 0jmjSlXccYciZUmvjAVp8Ly01ZtfmXX/pRZVLwDImkf65WKK6wYVuCqZ3NIFMLFn NO3CMgl8aIeN5pHbxsXhuMmngJf7/YFNEMi2m1mIA+m9xcrqJx6UpButreWL2Jt+ MRHpWVMBUXed1GYqVbbs31jo8eofB+mLDApFyalok9psmEJ9FUHI29QI+Sl2uRRS ahsml1TaV2aC9xxrXRSLqtTpgwStZWPMhrNZUXGIHMHSMGhR0RKCPoKl0KRNScgg hrHqpc9+RGcqtK3b3d5hLzfo57d+ZiPBIeC70vgsUHeWErefjgD+/K9JZZiT/l7X tDMqvwpLLsfkI0er1N41wbf1aoNKH/wf4qJ8UPQZsUT/w2Mx+UaQmZM5U8CMOQZT 5yczyM3rV/NAtuW1lAlayLG6YUBf8ysEtvaM54eUg1RibARGaE97aiuL1nC0nTqB o1+K4yLDJi2I49HF9J/3A1l3GLyYrLh+n3+4Mf7sH57IfYTQA3k15e5k+RvWFBRg WNBX1+bSREW4TvlorfS3MURpl/OgT6TYRClBHE9Mdc59y2ncIj7Toq22T+puUzss roic3E+4p+s7Sxz+QAcO9o0qLrFy+2seqgu3mLIi/K+mE2ZDQ51cnhs+4T0KG+zs RiZNcNv9b/OKNpQKMlI= =8SAZ -END PGP SIGNATUREEnd Message---
Processed: block 794375 with 794657
Processing commands for cont...@bugs.debian.org: block 794375 with 794657 Bug #794375 [src:cucumber] FTBFS: pry/cli.rb: undefined method `new' for Slop:Module (NoMethodError) 794375 was not blocked by any bugs. 794375 was not blocking any bugs. Added blocking bug(s) of 794375: 794657 thanks Stopping processing here. Please contact me if you need assistance. -- 794375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: affects 794657
Processing commands for cont...@bugs.debian.org: affects 794657 cucumber Bug #794657 [pry] pry: broken with ruby-slop = 4.x Added indication that 794657 affects cucumber thanks Stopping processing here. Please contact me if you need assistance. -- 794657: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787178: wdg-html-validator: Remove w3c-dtd-xhtml reference from d/control
On Fri, 29 May 2015 14:04:28 +0200 Mathieu Malaterre ma...@debian.org wrote: Please remove reference to w3c-dtd-xhtml from debian/control. This package will be removed for stretch (see #711332), it has been superseded by w3c-sgml-lib. I just had a look again at wdg-html-validator, this time for real :-) The validate and cgi-bin/validate.pl scripts (perhaps even more bits) hardcode paths to /etc/sgml/sgml-data.cat, /etc/sgml/w3c-dtd-xhtml.cat as well as many .dcl/.decl files provided by the w3c-dtd-xhtml and sgml-data packages. These locations are already patched in the Debian package since upstream assumes a different layout. w3c-sgml-lib ships files with (hopefully) the same functionality but in different locations and named differently. The proper way to locate the needed files is probably via /etc/sgml/catalog and not hardcoding them ... that might even add support for new standards automatically. At least for the validate script a new upstream release is available (1.2.3 from 2011 vs 1.2.2 in the package). That's too much work for a quick QA upload. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790975: fixed in afflib 3.7.6-4
Hi Julien, Ok. I will do it: 1. Upload to experimental, without close the bug. 2. Notify all maintainers of dependent packages, allowing changes up to next Saturday. 3. In next Saturday, upload to unstable, closing the bug. 4. Notify all maintainers that uploaded their packages to experimental. 5. File bugs (FTBFS) against all dependent packages not updated in experimental. Thanks a lot for your help. Regards, Eriberto 2015-08-09 8:50 GMT-03:00 Julien Cristau jul...@cristau.org: The whole point of this transition is that the rebuilt library is not compatible. So it can't provide the old name and there can't be a transitional package. Cheers Julien On August 9, 2015 8:25:46 AM CEST, Eriberto Mota eribe...@debian.org wrote: Hi Julien, I applied your patch and I updated some symbols. However, I added a binary libafflib0 as transitional package to avoid break some packages. Is there any problem in doing that? I attached a debdiff between afflib-3.7.6-4 and 3.7.6-5. Thanks a lot in advance. Regards, Eriberto 2015-08-06 19:14 GMT-03:00 Eriberto eribe...@eriberto.pro.br: Hi Julien, Thanks a lot for your quick reply. I will wait 2 days to fix some symbols for ports. Regards, Eriberto 2015-08-06 18:08 GMT-03:00 Julien Cristau jcris...@debian.org: On Thu, Aug 6, 2015 at 22:55:32 +0200, Julien Cristau wrote: On Thu, Aug 6, 2015 at 17:44:32 -0300, Eriberto wrote: Hum... Sorry, can you detail for me how to proceed? Need I use v5? Yes, something like the patch below. ... except with the .symbols files fixed to refer to libafflib0v5 instead of libafflib0; sorry about that. Cheers, Julien -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: notfound 794916 in 0.7-1
Processing commands for cont...@bugs.debian.org:
# unconfuse BTS again wrt. to BinNMU
notfound 794916 0.7-1
Bug #794916 {Done: Andreas Beckmann a...@debian.org} [aptitude] aptitude is
uninstallable
No longer marked as found in versions aptitude/0.7-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
794916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778062: marked as done (phonon: ftbfs with GCC-5)
Your message dated Sun, 9 Aug 2015 18:05:01 +0200 with message-id 20150809160455.ga30...@gnuservers.com.ar and subject line Re: Bug#778062: add patch has caused the Debian Bug report #778062, regarding phonon: ftbfs with GCC-5 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.) -- 778062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:phonon Version: 4:4.8.0-4 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/phonon_4.8.0-4_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] - _ZN6Phonon17VolumeFaderEffectD0Ev@Base 4:4.6.0really4.5.0 - _ZN6Phonon17VolumeFaderEffectD1Ev@Base 4:4.6.0really4.5.0 - _ZN6Phonon17VolumeFaderEffectD2Ev@Base 4:4.6.0really4.5.0 +#MISSING: 4:4.8.0-4# _ZN6Phonon17VolumeFaderEffectD0Ev@Base 4:4.6.0really4.5.0 +#MISSING: 4:4.8.0-4# _ZN6Phonon17VolumeFaderEffectD1Ev@Base 4:4.6.0really4.5.0 +#MISSING: 4:4.8.0-4# _ZN6Phonon17VolumeFaderEffectD2Ev@Base 4:4.6.0really4.5.0 _ZN6Phonon17registerMetaTypesEv@Base 4:4.6.0really4.4.3 _ZN6Phonon18MediaObjectPrivate15_k_stateChangedENS_5StateES1_@Base 4:4.2.0 _ZN6Phonon18MediaObjectPrivate18setupBackendObjectEv@Base 4:4.2.0 @@ -354,9 +354,9 @@ _ZN6Phonon19AbstractMediaStreamD2Ev@Base 4:4.2.0 _ZN6Phonon19AbstractVideoOutputC1ERNS_26AbstractVideoOutputPrivateE@Base 4:4.2.0 _ZN6Phonon19AbstractVideoOutputC2ERNS_26AbstractVideoOutputPrivateE@Base 4:4.2.0 - _ZN6Phonon19AbstractVideoOutputD0Ev@Base 4:4.6.0really4.5.0 - _ZN6Phonon19AbstractVideoOutputD1Ev@Base 4:4.6.0really4.5.0 - _ZN6Phonon19AbstractVideoOutputD2Ev@Base 4:4.6.0really4.5.0 +#MISSING: 4:4.8.0-4# _ZN6Phonon19AbstractVideoOutputD0Ev@Base 4:4.6.0really4.5.0 +#MISSING: 4:4.8.0-4# _ZN6Phonon19AbstractVideoOutputD1Ev@Base 4:4.6.0really4.5.0 +#MISSING: 4:4.8.0-4# _ZN6Phonon19AbstractVideoOutputD2Ev@Base 4:4.6.0really4.5.0 _ZN6Phonon19BackendCapabilities18availableMimeTypesEv@Base 4:4.2.0 _ZN6Phonon19BackendCapabilities19isMimeTypeAvailableERK7QString@Base 4:4.2.0 _ZN6Phonon19BackendCapabilities21availableAudioEffectsEv@Base 4:4.2.0 @@ -704,13 +704,13 @@ _ZTVN6Phonon6EffectE@Base 4:4.2.0 _ZTVN6Phonon9MediaNodeE@Base 4:4.2.0 (c++)non-virtual thunk to Phonon::AbstractAudioOutput::~AbstractAudioOutput()@Base 4:4.2.0 - (c++)non-virtual thunk to Phonon::AudioDataOutput::~AudioDataOutput()@Base 4:4.6.0really4.5.0 - (c++)non-virtual thunk to Phonon::AudioOutput::~AudioOutput()@Base 4:4.6.0really4.5.0 +#MISSING: 4:4.8.0-4# (c++)non-virtual thunk to Phonon::AudioDataOutput::~AudioDataOutput()@Base 4:4.6.0really4.5.0 +#MISSING: 4:4.8.0-4# (c++)non-virtual thunk to Phonon::AudioOutput::~AudioOutput()@Base 4:4.6.0really4.5.0 (c++)non-virtual thunk to Phonon::Effect::~Effect()@Base 4:4.2.0 (c++)non-virtual thunk to Phonon::EffectWidget::~EffectWidget()@Base 4:4.2.0 (c++)non-virtual thunk to Phonon::MediaObject::~MediaObject()@Base 4:4.2.0 (c++)non-virtual thunk to Phonon::SeekSlider::~SeekSlider()@Base 4:4.2.0 (c++)non-virtual thunk to Phonon::VideoPlayer::~VideoPlayer()@Base 4:4.2.0 - (c++)non-virtual thunk to Phonon::VideoWidget::~VideoWidget()@Base 4:4.6.0really4.5.0 - (c++)non-virtual thunk to Phonon::VolumeFaderEffect::~VolumeFaderEffect()@Base 4:4.6.0really4.5.0 +#MISSING: 4:4.8.0-4# (c++)non-virtual thunk to Phonon::VideoWidget::~VideoWidget()@Base 4:4.6.0really4.5.0 +#MISSING: 4:4.8.0-4# (c++)non-virtual thunk to Phonon::VolumeFaderEffect::~VolumeFaderEffect()@Base 4:4.6.0really4.5.0
Bug#791144: libnzb: diff for NMU version 0.0.20050629-6.2
Control: tag -1 patch pending
Dear maintainer,
I've prepared an NMU for libnzb (versioned as 0.0.20050629-6.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
Jonathan Wiltshire j...@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
diff -u libnzb-0.0.20050629/debian/changelog libnzb-0.0.20050629/debian/changelog
--- libnzb-0.0.20050629/debian/changelog
+++ libnzb-0.0.20050629/debian/changelog
@@ -1,3 +1,11 @@
+libnzb (0.0.20050629-6.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename library packages for g++5 ABI transition, patch
+from Ubuntu (see #791144)
+
+ -- Jonathan Wiltshire j...@debian.org Sun, 09 Aug 2015 19:09:13 +0100
+
libnzb (0.0.20050629-6.1) unstable; urgency=low
* Non-maintainer upload.
diff -u libnzb-0.0.20050629/debian/control libnzb-0.0.20050629/debian/control
--- libnzb-0.0.20050629/debian/control
+++ libnzb-0.0.20050629/debian/control
@@ -9,17 +9,17 @@
Package: libnzb-dev
Section: libdevel
Architecture: any
-Depends: libnzb0c2a (= ${binary:Version})
+Depends: libnzb0v5 (= ${binary:Version})
Description: An nzb based Usenet binary grabber (development files)
libnzb is a library that provides functions to parse nzb files, grab the
content over NNTP and decode the yEnc/uuencode encoded file.
-Package: libnzb0c2a
+Package: libnzb0v5
Section: libs
Architecture: any
Depends: ${shlibs:Depends}
-Conflicts: libnzb0
-Replaces: libnzb0
+Conflicts: libnzb0c2a, libnzb0
+Replaces: libnzb0c2a, libnzb0
Description: An nzb based Usenet binary grabber (runtime library)
libnzb is a library that provides functions to parse nzb files, grab the
content over NNTP and decode the yEnc/uuencode encoded file.
reverted:
--- libnzb-0.0.20050629/debian/libnzb0c2a.install
+++ libnzb-0.0.20050629.orig/debian/libnzb0c2a.install
@@ -1 +0,0 @@
-usr/lib/lib*.so.*
only in patch2:
unchanged:
--- libnzb-0.0.20050629.orig/debian/libnzb0v5.install
+++ libnzb-0.0.20050629/debian/libnzb0v5.install
@@ -0,0 +1 @@
+usr/lib/lib*.so.*
signature.asc
Description: Digital signature
Processed: libnzb: diff for NMU version 0.0.20050629-6.2
Processing control commands: tag -1 patch pending Bug #791144 [src:libnzb] libnzb: library transition may be needed when GCC 5 is the default Added tag(s) pending and patch. -- 791144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790975: fixed in afflib 3.7.6-4
Hum... I understand but I prefer notify the maintainers. Thanks Julien! Regards, Eriberto 2015-08-09 14:01 GMT-03:00 Julien Cristau jcris...@debian.org: On Sun, Aug 9, 2015 at 10:42:29 -0300, Eriberto wrote: Hi Julien, Ok. I will do it: 1. Upload to experimental, without close the bug. 2. Notify all maintainers of dependent packages, allowing changes up to next Saturday. 3. In next Saturday, upload to unstable, closing the bug. 4. Notify all maintainers that uploaded their packages to experimental. 5. File bugs (FTBFS) against all dependent packages not updated in experimental. Thanks a lot for your help. I don't think that delay is necessary, uploading to sid right away should be just fine, we'll rebuild reverse dependencies as needed. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794657: reupload 3.6.0?
Hi, This is affecting packages (build)depending on pry, including cucumber. Since ruby-slop has a unique dependency/build-dependency (pry) and upstream is not ready yet to upgrade to the v4 of ruby-slop (which seems to be a complete rewrite), can we reupload the 3.6.0 version, with a 4.2.0+really3.6.0-1 version number in the mean time? Cédric signature.asc Description: Digital signature
Bug#787018: src:xbmc: xbmc does not build on unstable
On Wed, May 27, 2015 at 10:20:08PM +0200, Bálint Réczey wrote: XBMC has been renamed to Kodi and I have already packaged it. It is waiting for FTP Master approval in the NEW queue for some time. I don't plan updating xbmc, just once, with an empty content to get rid of the epoch while transitioning to kodi. Now kodi is even in testing. What about uploading this empty transition package of xbmc? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: Digital signature
Bug#794993: marked as done (libsnappy1: library transition may be needed when GCC 5 is the default)
Your message dated Sun, 09 Aug 2015 16:00:14 +
with message-id e1zot1c-0001ae...@franck.debian.org
and subject line Bug#794993: fixed in snappy 1.1.3-2
has caused the Debian Bug report #794993,
regarding libsnappy1: library transition may be needed when GCC 5 is the default
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.)
--
794993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:snappy
Version: 1.1.3-1
Severity: serious
Tags: sid stretch patch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11
Control: block 794931 with -1
The short note.
Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI. Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols. If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.
It seems Matthias missed this C++ library transition. Maybe due to the
old style packaging and that this package doesn't provide a symbols
file. But please see the attached symbols change when built with
gcc-4.9 and gcc-5.2 , thus __cxx11 symbols show up.
At the moment it breaks building of mongodb, but may break other
packages as well.
I propose the attached NMU if you don't have time for now - or I can
help update and maintain the packaging as co-maintainer if you want.
Regards,
Laszlo/GCS
[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
--- debian/libsnappy1.symbols 2015-08-08 23:54:52.415075073 +
+++ debian/libsnappy1/DEBIAN/symbols2015-08-08 23:59:25.046660564 +
@@ -1,5 +1,5 @@
libsnappy.so.1 libsnappy1 #MINVER#
- _ZN6snappy10UncompressEPKcmPSs@Base 1.1.3
+
_ZN6snappy10UncompressEPKcmPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
1.1.3
_ZN6snappy10UncompressEPNS_6SourceEPNS_4SinkE@Base 1.1.3
_ZN6snappy11RawCompressEPKcmPcPm@Base 1.1.3
_ZN6snappy13RawUncompressEPKcmPc@Base 1.1.3
@@ -38,8 +38,8 @@
_ZN6snappy6SourceD0Ev@Base 1.1.3
_ZN6snappy6SourceD1Ev@Base 1.1.3
_ZN6snappy6SourceD2Ev@Base 1.1.3
- _ZN6snappy6Varint8Append32EPSsj@Base 1.1.3
- _ZN6snappy8CompressEPKcmPSs@Base 1.1.3
+
_ZN6snappy6Varint8Append32EPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEj@Base
1.1.3
+
_ZN6snappy8CompressEPKcmPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
1.1.3
_ZN6snappy8CompressEPNS_6SourceEPNS_4SinkE@Base 1.1.3
_ZN6snappy8internal13WorkingMemory12GetHashTableEmPi@Base 1.1.3
_ZN6snappy8internal16CompressFragmentEPKcmPcPti@Base 1.1.3
diff -u snappy-1.1.3/debian/changelog snappy-1.1.3/debian/changelog
--- snappy-1.1.3/debian/changelog
+++ snappy-1.1.3/debian/changelog
@@ -1,3 +1,10 @@
+snappy (1.1.3-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename library to libsnappy1v5 for GCC 5 transition.
+
+ -- Laszlo Boszormenyi (GCS) g...@debian.org Sun, 09 Aug 2015 07:28:37 +0200
+
snappy (1.1.3-1) unstable; urgency=medium
* New upstream release.
diff -u snappy-1.1.3/debian/control snappy-1.1.3/debian/control
--- snappy-1.1.3/debian/control
+++ snappy-1.1.3/debian/control
@@ -10,7 +10,7 @@
Section: libdevel
Architecture: any
Multi-Arch: same
-Depends: libsnappy1 (= ${binary:Version}), ${misc:Depends}
+Depends: libsnappy1v5 (= ${binary:Version}), ${misc:Depends}
Description: fast compression/decompression library (development files)
Snappy is a compression/decompression library. It does not aim for
maximum compression, or compatibility with any other compression
@@ -26,12 +26,14 @@
This package contains the development files required to build programs
against Snappy.
-Package: libsnappy1
+Package: libsnappy1v5
Section: libs
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}, ${misc:Depends}
+Conflicts: libsnappy1
+Replaces: libsnappy1
Description: fast compression/decompression library
Snappy is a compression/decompression library. It does not aim for
maximum compression, or compatibility with any other compression
reverted:
--- snappy-1.1.3/debian/libsnappy1.dirs
+++ snappy-1.1.3.orig/debian/libsnappy1.dirs
@@ -1 +0,0 @@
-usr/lib
reverted:
--- snappy-1.1.3/debian/libsnappy1.install
+++ snappy-1.1.3.orig/debian/libsnappy1.install
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.*
only in patch2:
unchanged:
---
Processed: colpack: diff for NMU version 1.0.9-3.2
Processing control commands: tags 794909 + patch pending Bug #794909 [libcolpack0v5] libcolpack0v5: missing Breaks/Replaces against libcolpack0 Added tag(s) pending and patch. -- 794909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794909: colpack: diff for NMU version 1.0.9-3.2
Control: tags 794909 + patch pending
Dear maintainer,
I've prepared an NMU for colpack (versioned as 1.0.9-3.2). The diff
is attached to this message; sorry about the breakage.
Regards.
--
Jonathan Wiltshire j...@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
diff -Nru colpack-1.0.9/debian/changelog colpack-1.0.9/debian/changelog
--- colpack-1.0.9/debian/changelog 2015-08-04 17:56:21.0 +0100
+++ colpack-1.0.9/debian/changelog 2015-08-09 17:51:38.0 +0100
@@ -1,3 +1,10 @@
+colpack (1.0.9-3.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add conflicts/replaces libcolpack0 (closes: #794909)
+
+ -- Jonathan Wiltshire j...@debian.org Sun, 09 Aug 2015 17:51:36 +0100
+
colpack (1.0.9-3.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru colpack-1.0.9/debian/control colpack-1.0.9/debian/control
--- colpack-1.0.9/debian/control 2015-08-04 17:55:09.0 +0100
+++ colpack-1.0.9/debian/control 2015-08-09 17:52:05.0 +0100
@@ -32,6 +32,8 @@
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}, ${misc:Depends}
+Conflicts: libcolpack0
+Replaces: libcolpack0
Description: Specialized graph vertex coloring library, shared library
ColPack is a package comprising of implementation of algorithms for
specialized vertex coloring problems that arise in sparse derivative
signature.asc
Description: Digital signature
Bug#778126: marked as done (soprano: ftbfs with GCC-5)
Your message dated Sun, 09 Aug 2015 19:53:20 + with message-id e1zowem-0006ui...@franck.debian.org and subject line Bug#778126: fixed in soprano 2.9.4+dfsg-2 has caused the Debian Bug report #778126, regarding soprano: ftbfs with GCC-5 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.) -- 778126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:soprano Version: 2.9.4+dfsg-1.1 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/soprano_2.9.4+dfsg-1.1_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] +#MISSING: 2.9.4+dfsg-1.1# (optional=templinst)_ZN5QHashIN7Soprano4NodeEPN6lucene8document8DocumentEED2Ev@Base 2.6.0 (optional=templinst)_ZN5QListI4QUrlE13detach_helperEi@Base 2.6.0 (optional=templinst)_ZN5QListI4QUrlE18detach_helper_growEii@Base 2.6.0 (optional=templinst)_ZN5QListI4QUrlE6appendERKS0_@Base 2.1.1 - (optional=templinst)_ZN5QListI7QStringE13detach_helperEi@Base 2.6.0 +#MISSING: 2.9.4+dfsg-1.1# (optional=templinst)_ZN5QListI7QStringE13detach_helperEi@Base 2.6.0 (optional=templinst)_ZN5QListI7QStringE18detach_helper_growEii@Base 2.6.0 (optional=templinst)_ZN5QListI7QStringE6appendERKS0_@Base 2.1.1 - (optional=templinst)_ZN5QListI7QStringED1Ev@Base 2.6.0 - (optional=templinst)_ZN5QListI7QStringED2Ev@Base 2.4.1 - (optional=external)_ZN7QStringD1Ev@Base 2.1.1 - (optional=external)_ZN7QStringD2Ev@Base 2.6.0 +#MISSING: 2.9.4+dfsg-1.1# (optional=templinst)_ZN5QListI7QStringED1Ev@Base 2.6.0 +#MISSING: 2.9.4+dfsg-1.1# (optional=templinst)_ZN5QListI7QStringED2Ev@Base 2.4.1 + _ZN6QMutex12unlockInlineEv@Base 2.9.4+dfsg-1.1 +#MISSING: 2.9.4+dfsg-1.1# (optional=external)_ZN7QStringD1Ev@Base 2.1.1 +#MISSING: 2.9.4+dfsg-1.1# (optional=external)_ZN7QStringD2Ev@Base 2.6.0 _ZN7Soprano5Index11idFieldNameEv@Base 2.1.1 _ZN7Soprano5Index12CLuceneIndex11getResourceEPN6lucene8document8DocumentE@Base 2.1.1 _ZN7Soprano5Index12CLuceneIndex12addStatementERKNS_9StatementE@Base 2.1.1 @@ -2496,6 +2497,7 @@ _ZN7Soprano5Index12CLuceneIndex5closeEv@Base 2.1.1 _ZN7Soprano5Index12CLuceneIndex6searchEPN6lucene6search5QueryE@Base 2.1.1 _ZN7Soprano5Index12CLuceneIndex6searchERK7QString@Base 2.1.1 + _ZN7Soprano5Index12CLuceneIndex7Private11getDocumentERKNS_4NodeE@Base 2.9.4+dfsg-1.1 _ZN7Soprano5Index12CLuceneIndex7Private6commitEv@Base 2.1.1 _ZN7Soprano5Index12CLuceneIndex8optimizeEv@Base 2.1.67 _ZN7Soprano5Index12CLuceneIndexC1EPN6lucene8analysis8AnalyzerE@Base 2.1.1 @@ -2563,9 +2565,9 @@ (optional=templinst)_ZN7Soprano8IteratorINS_10BindingSetEE4nextEv@Base 2.1.1 (optional=templinst)_ZN7Soprano8IteratorINS_5Index8QueryHitEE4nextEv@Base 2.1.1 (optional=templinst)_ZN7Soprano8IteratorINS_5Index8QueryHitEE5closeEv@Base 2.7.6 - (optional=templinst)_ZN7Soprano8IteratorINS_5Index8QueryHitEEC1EPNS_15IteratorBackendIS2_EE@Base 2.9.2 +#MISSING: 2.9.4+dfsg-1.1# (optional=templinst)_ZN7Soprano8IteratorINS_5Index8QueryHitEEC1EPNS_15IteratorBackendIS2_EE@Base 2.9.2 (optional=templinst)_ZN7Soprano8IteratorINS_5Index8QueryHitEEC1Ev@Base 2.1.1 - (optional=templinst)_ZN7Soprano8IteratorINS_5Index8QueryHitEEC2EPNS_15IteratorBackendIS2_EE@Base 2.9.2 +#MISSING: 2.9.4+dfsg-1.1# (optional=templinst)_ZN7Soprano8IteratorINS_5Index8QueryHitEEC2EPNS_15IteratorBackendIS2_EE@Base 2.9.2 (optional=templinst)_ZN7Soprano8IteratorINS_5Index8QueryHitEEC2Ev@Base 2.6.0 (optional=templinst)_ZN7Soprano8IteratorINS_5Index8QueryHitEED0Ev@Base 2.1.1
Bug#732723: cegui-mk2: Please upgrade OGRE dependency to 1.9 when upstream ready
On 2015-08-09 02:43, Muammar El Khatib wrote: I have prepared an upload¹, I am waiting it passes the NEW process. Hopefully in a couple of weeks it should be done. If it does not pass, I will upload a revision of 0.7.6. Regards, 1. https://ftp-master.debian.org/new/cegui-mk2_0.8.4-2.html Ok, thank you. -Corey -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795030: ruby-dependor: FTBFS: rspec3 issue: undefined method `color_enabled='
Source: ruby-dependor
Version: 1.0.1-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
The package fails to build:
Selecting previously unselected package ruby-rspec-core.
Preparing to unpack .../ruby-rspec-core_3.3.0c0e0m0s0-1_all.deb ...
Unpacking ruby-rspec-core (3.3.0c0e0m0s0-1) ...
Selecting previously unselected package ruby-rspec.
Preparing to unpack .../ruby-rspec_3.3.0c0e0m0s0-1_all.deb ...
Unpacking ruby-rspec (3.3.0c0e0m0s0-1) ...
...
┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake│
└──┘
RUBYLIB=/ruby-dependor-1.0.1/debian/ruby-dependor/usr/lib/ruby/vendor_ruby:.
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
/ruby-dependor-1.0.1/spec/spec_helper.rb:7:in `block in top (required)':
undefined method `color_enabled=' for
#RSpec::Core::Configuration:0x00017053b8 (NoMethodError)
from /usr/lib/ruby/vendor_ruby/rspec/core.rb:97:in `configure'
from /ruby-dependor-1.0.1/spec/spec_helper.rb:6:in `top (required)'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from /ruby-dependor-1.0.1/spec/dependor/auto_inject_spec.rb:1:in `top
(required)'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke'
from /usr/bin/rspec:4:in `main'
/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
failed
ERROR: Test ruby2.1 failed. Exiting.
dh_auto_install: dh_ruby --install /ruby-dependor-1.0.1/debian/ruby-dependor
returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary gave error exit status 2
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-dependor.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789404: pbuilder: insecure use of /tmp
* Mattia Rizzolo mat...@mapreri.org, 2015-08-08, 17:00: I don't see how changing it can fix #789401, though. It would improve the situation, as a malicious local user can not plant the build dir any more Right. But there might be other /tmp vulnerabilities (in pbuilder or elsewhere) that #789401 would ease exploiting. And there's DoS aspect: local user could stuff chroot's /tmp with garbage, which pbuilder then will have to compress and later decompress on every build. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795031: ruby-coercible: FTBFS: rspec3 port needed(?): undefined method `its'
Source: ruby-coercible
Version: 1.0.0-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
The package fails to build:
┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake│
└──┘
RUBYLIB=/ruby-coercible-1.0.0/debian/ruby-coercible/usr/lib/ruby/vendor_ruby:.
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
/usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing':
undefined method `its' for RSpec::ExampleGroups::CoercibleCoercerNew:Class
(NoMethodError)
from
/ruby-coercible-1.0.0/spec/unit/coercible/coercer/class_methods/new_spec.rb:10:in
`block in top (required)'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in
`block in define_example_group_method'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in
expose_example_group_alias'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2
levels) in expose_example_group_alias_globally'
from
/ruby-coercible-1.0.0/spec/unit/coercible/coercer/class_methods/new_spec.rb:3:in
`top (required)'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke'
from /usr/bin/rspec:4:in `main'
/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
failed
ERROR: Test ruby2.1 failed. Exiting.
dh_auto_install: dh_ruby --install /ruby-coercible-1.0.0/debian/ruby-coercible
returned exit code 1
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-coercible.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795040: ruby-fission: FTBFS: test fails: result['output'].empty?.should be_false
Source: ruby-fission
Version: 0.5.0-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
The package fails to build (could be an rspec3 problem around be_falsey):
Failures:
1) Fission::Action::ShellExecutor execute should return a hash of the output
and Process::Status object
Failure/Error: result['output'].empty?.should be_false
expected false to respond to `false?` or perhaps you meant `be false` or
`be_falsey`
# ./spec/fission/action/execute_shell_command_spec.rb:19:in `block (3
levels) in top (required)'
Deprecation Warnings:
Using `should_receive` from rspec-mocks' old `:should` syntax without
explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
explicitly enable `:should` instead. Called from
/ruby-fission-0.5.0/spec/fission/action/execute_shell_command_spec.rb:12:in
`block (3 levels) in top (required)'.
Using `should` from rspec-expectations' old `:should` syntax without explicitly
enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly
enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }`
instead. Called from
/ruby-fission-0.5.0/spec/fission/action/execute_shell_command_spec.rb:18:in
`block (3 levels) in top (required)'.
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-fission.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793015: taoframework: FTBFS, needs update of hardcoded sonames
Hi, On Mon, 20 Jul 2015 15:35:00 +0200 Andreas Cadhalpun andreas.cadhal...@googlemail.com wrote: Source: taoframework Version: 2.1.svn20090801-10 Tags: patch Severity: serious Justification: fails to build from source Dear maintainer, the ffmpeg-libav transition [1] is ongoing and thus the hardcoded sonames in taoframework need to be updated. Please apply attached patch doing that. I will upload an NMU to DELAYED/5 with the attached patch soon. Cheers, Balint diff -u taoframework-2.1.svn20090801/debian/changelog taoframework-2.1.svn20090801/debian/changelog --- taoframework-2.1.svn20090801/debian/changelog +++ taoframework-2.1.svn20090801/debian/changelog @@ -1,3 +1,10 @@ +taoframework (2.1.svn20090801-10.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with ffmpeg (Closes: #793015) + + -- Balint Reczey bal...@balintreczey.hu Sun, 09 Aug 2015 11:36:44 +0200 + taoframework (2.1.svn20090801-10) unstable; urgency=low [ Iain Lane ] diff -u taoframework-2.1.svn20090801/debian/control taoframework-2.1.svn20090801/debian/control --- taoframework-2.1.svn20090801/debian/control +++ taoframework-2.1.svn20090801/debian/control @@ -9,8 +9,8 @@ Build-Depends-Indep: cli-common-dev (= 0.4.4), freeglut3-dev, libalut-dev, - libavcodec-dev (= 5:3:0.svn20090303), - libavformat-dev (= 5:3:0.svn20090303), + libavcodec-dev (= 7:2.7.1), + libavformat-dev (= 7:2.7.1), libdevil-dev, libfreetype6-dev, libftgl-dev, @@ -28,7 +28,7 @@ libsdl-ttf2.0-dev, libsdl1.2-dev, libsmpeg-dev, - libswscale-dev, + libswscale-dev (= 7:2.7.1), libx11-dev, mono-devel (= 2.4.3), monodoc-base diff -u taoframework-2.1.svn20090801/debian/patches/200_libavcodec_update.diff taoframework-2.1.svn20090801/debian/patches/200_libavcodec_update.diff --- taoframework-2.1.svn20090801/debian/patches/200_libavcodec_update.diff +++ taoframework-2.1.svn20090801/debian/patches/200_libavcodec_update.diff @@ -7,7 +7,7 @@ dllmap dll=avcodec-51.dll os=windows target=avcodec-51.dll / dllmap dll=avcodec-51.dll os=osx target=libavcodec.so.51 / -dllmap dll=avcodec-51.dll os=!windows,osx target=libavcodec.so.51 / -+dllmap dll=avcodec-51.dll os=!windows,osx target=libavcodec.so.56 / ++dllmap dll=avcodec-51.dll os=!windows,osx target=libavcodec-ffmpeg.so.56 / dllmap dll=avformat-52.dll os=windows target=avformat-52.dll / dllmap dll=avformat-52.dll os=osx target=libavformat.so.52 / diff -u taoframework-2.1.svn20090801/debian/patches/200_libavformat_update taoframework-2.1.svn20090801/debian/patches/200_libavformat_update --- taoframework-2.1.svn20090801/debian/patches/200_libavformat_update +++ taoframework-2.1.svn20090801/debian/patches/200_libavformat_update @@ -7,7 +7,7 @@ dllmap dll=avformat-52.dll os=windows target=avformat-52.dll / dllmap dll=avformat-52.dll os=osx target=libavformat.so.52 / -dllmap dll=avformat-52.dll os=!windows,osx target=libavformat.so.52 / -+dllmap dll=avformat-52.dll os=!windows,osx target=libavformat.so.56 / ++dllmap dll=avformat-52.dll os=!windows,osx target=libavformat-ffmpeg.so.56 / dllmap dll=avutil-49.dll os=windows target=avutil-49.dll / dllmap dll=avutil-49.dll os=osx target=libavutil.so.49 / diff -u taoframework-2.1.svn20090801/debian/patches/200_libavutil_update.diff taoframework-2.1.svn20090801/debian/patches/200_libavutil_update.diff --- taoframework-2.1.svn20090801/debian/patches/200_libavutil_update.diff +++ taoframework-2.1.svn20090801/debian/patches/200_libavutil_update.diff @@ -10,7 +10,7 @@ dllmap dll=avutil-49.dll os=windows target=avutil-49.dll / dllmap dll=avutil-49.dll os=osx target=libavutil.so.49 / -dllmap dll=avutil-49.dll os=!windows,osx target=libavutil.so.49 / -+dllmap dll=avutil-49.dll os=!windows,osx target=libavutil.so.54 / ++dllmap dll=avutil-49.dll os=!windows,osx target=libavutil-ffmpeg.so.54 / dllmap dll=swscale-0.dll os=windows target=swscale-0.dll / dllmap dll=swscale-0.dll os=osx target=libswscale.so.0 / diff -u taoframework-2.1.svn20090801/debian/patches/200_libswscale_update taoframework-2.1.svn20090801/debian/patches/200_libswscale_update --- taoframework-2.1.svn20090801/debian/patches/200_libswscale_update +++ taoframework-2.1.svn20090801/debian/patches/200_libswscale_update @@ -9,3 +9,3 @@ -dllmap dll=swscale-0.dll os=!windows,osx target=libswscale.so.0 / -+dllmap dll=swscale-0.dll os=!windows,osx target=libswscale.so.3 / ++dllmap dll=swscale-0.dll os=!windows,osx target=libswscale-ffmpeg.so.3 / /configuration
Processed: your mail
Processing commands for cont...@bugs.debian.org:
notfound 793195 1.0.0.49-1
Bug #793195 {Done: Michael Gilbert mgilb...@debian.org} [src:steam] steam:
FTBFS due to missing B-D: libx11-6
No longer marked as found in versions steam/1.0.0.49-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
793195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795037: ruby-filepath: FTBFS: rspec3 port for be_true etc.
Source: ruby-filepath Version: 0.6-2 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: Failures: 1) FilePath#extension? says that foo.bar has an extension Failure/Error: FilePath.new(path).extension?.should be_true expected true to respond to `true?` or perhaps you meant `be true` or `be_truthy` # ./spec/filepath_spec.rb:185:in `block (4 levels) in top (required)' ... 12) FilePath#each_segment goes through all the segments of an absolute path Failure/Error: steps.should have(4).items NoMethodError: undefined method `have' for #RSpec::ExampleGroups::FilePath::EachSegment:0x0002011740 # ./spec/filepath_spec.rb:323:in `block (3 levels) in top (required)' ... 222 examples, 52 failures Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-filepath.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795046: ruby-parslet: FTBFS: undefined method `its'
Source: ruby-parslet
Version: 1.6.1-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
The package fails to build:
┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake│
└──┘
RUBYLIB=/ruby-parslet-1.6.1/debian/ruby-parslet/usr/lib/ruby/vendor_ruby:.
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
/usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing':
undefined method `its' for
RSpec::ExampleGroups::ParsletAtomsDSL::DeprecatedMethods::Absnt:Class
(NoMethodError)
from /ruby-parslet-1.6.1/spec/parslet/atoms/dsl_spec.rb:8:in `block (3
levels) in top (required)'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in
`block in define_example_group_method'
from /ruby-parslet-1.6.1/spec/parslet/atoms/dsl_spec.rb:6:in `block (2
levels) in top (required)'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in
`block in define_example_group_method'
from /ruby-parslet-1.6.1/spec/parslet/atoms/dsl_spec.rb:4:in `block in
top (required)'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in
`block in define_example_group_method'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in
expose_example_group_alias'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2
levels) in expose_example_group_alias_globally'
from /ruby-parslet-1.6.1/spec/parslet/atoms/dsl_spec.rb:3:in `top
(required)'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`load'
...
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-parslet.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794133: marked as done (FTBFS: example_group.rb:656:in `method_missing': undefined method `its' for #Class:..)
Your message dated Sun, 09 Aug 2015 21:44:20 + with message-id e1zoyoc-0003t4...@franck.debian.org and subject line Bug#794133: fixed in ruby-addressable 2.3.8-1 has caused the Debian Bug report #794133, regarding FTBFS: example_group.rb:656:in `method_missing': undefined method `its' for #Class:.. 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.) -- 794133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-addressable Version: 2.3.6-1 Severity: serious Tags: sid stretch Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: RUBYLIB=/ruby-addressable-2.3.6/debian/ruby-addressable/usr/lib/ruby/vendor_ruby:. rake2.1 -f debian/ruby-tests.rak e /usr/bin/ruby2.1 /usr/bin/rspec spec/addressable/idna_spec.rb spec/addressable/template_spec.rb spec/addressable/ur i_spec.rb Could not load native IDN implementation. /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing': undefined method `its' for #Class:0 x00030f4080 (NoMethodError) from /ruby-addressable-2.3.6/spec/addressable/template_spec.rb:756:in `block (3 levels) in top (required) ' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `module_exec' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `subclass' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in `block in define_example_group_method' from /ruby-addressable-2.3.6/spec/addressable/template_spec.rb:750:in `block (2 levels) in top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `module_exec' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `subclass' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in `block in define_example_group_method' from /ruby-addressable-2.3.6/spec/addressable/template_spec.rb:732:in `block in top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `module_exec' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `subclass' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in `block in define_example_group_method' from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in expose_example_group_alias' from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2 levels) in expose_example_group_alias_globally' from /ruby-addressable-2.3.6/spec/addressable/template_spec.rb:731:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke' from /usr/bin/rspec:4:in `main' Loading simplecov-html failed, install ruby-simplecov-html [Coveralls] Set up the SimpleCov formatter. [Coveralls] Using SimpleCov's default settings. [Coveralls] Outside the Travis environment, not sending data. /usr/bin/ruby2.1 /usr/bin/rspec spec/addressable/idna_spec.rb spec/addressable/template_spec.rb spec/addressable/uri_spec.rb failed Full build log (rbuild): https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-addressable.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- Source: ruby-addressable Source-Version: 2.3.8-1 We believe that the bug you reported is fixed in the latest version of ruby-addressable, 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
Bug#794134: marked as done (FTBFS: `require': cannot load such file -- hmac/sha1 (LoadError))
Your message dated Sun, 09 Aug 2015 21:44:27 + with message-id e1zoyoj-0003uo...@franck.debian.org and subject line Bug#794134: fixed in ruby-openid 2.7.0debian-1 has caused the Debian Bug report #794134, regarding FTBFS: `require': cannot load such file -- hmac/sha1 (LoadError) 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.) -- 794134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-openid Version: 2.5.0debian-1 Severity: serious Tags: sid stretch Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: RUBYLIB=/tmp/buildd/ruby-openid-2.5.0debian/debian/ruby-openid/usr/lib/ruby/vendor_ruby:. ruby2.2 debian/ruby-tests.rb /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- hmac/sha1 (LoadError) from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /tmp/buildd/ruby-openid-2.5.0debian/debian/ruby-openid/usr/lib/ruby/vendor_ruby/openid/cryptutil.rb:13:in `rescue in rescue in top (required)' from /tmp/buildd/ruby-openid-2.5.0debian/debian/ruby-openid/usr/lib/ruby/vendor_ruby/openid/cryptutil.rb:7:in `rescue in top (required)' from /tmp/buildd/ruby-openid-2.5.0debian/debian/ruby-openid/usr/lib/ruby/vendor_ruby/openid/cryptutil.rb:4:in `top (required)' from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /tmp/buildd/ruby-openid-2.5.0debian/debian/ruby-openid/usr/lib/ruby/vendor_ruby/openid/dh.rb:2:in `top (required)' from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /tmp/buildd/ruby-openid-2.5.0debian/debian/ruby-openid/usr/lib/ruby/vendor_ruby/openid/consumer/associationmanager.rb:1:in `top (required)' from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /tmp/buildd/ruby-openid-2.5.0debian/test/test_associationmanager.rb:2:in `top (required)' from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require' from debian/ruby-tests.rb:5:in `block in main' from debian/ruby-tests.rb:5:in `each' from debian/ruby-tests.rb:5:in `main' ERROR: Test ruby2.2 failed. Exiting. dh_auto_install: dh_ruby --install /tmp/buildd/ruby-openid-2.5.0debian/debian/ruby-openid returned exit code 1 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-openid.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- Source: ruby-openid Source-Version: 2.7.0debian-1 We believe that the bug you reported is fixed in the latest version of ruby-openid, 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 794...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier bou...@debian.org (supplier of updated ruby-openid 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: Sun, 09 Aug 2015 22:20:03 +0200 Source: ruby-openid Binary: ruby-openid Architecture: source all Version: 2.7.0debian-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Cédric Boutillier bou...@debian.org Description: ruby-openid - Ruby library for verifying and serving OpenID identities Closes: 794134 Changes: ruby-openid (2.7.0debian-1)
Bug#795048: ruby-roxml: FTBFS: rspec3 port(?): ...name_explicit?.should be_true
Source: ruby-roxml Version: 3.3.1-3 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: Failures: 1) ROXML::Definition#name_explicit? should indicate whether from option is present Failure/Error: ROXML::Definition.new(:element, :from = 'somewhere').name_explicit?.should be_true expected true to respond to `true?` or perhaps you meant `be true` or `be_truthy` # ./spec/definition_spec.rb:7:in `block (3 levels) in top (required)' 2) ROXML::Definition#name_explicit? should not consider name proxies as explicit Failure/Error: ROXML::Definition.new(:element, :from = :attr).name_explicit?.should be_false expected false to respond to `false?` or perhaps you meant `be false` or `be_falsey` # ./spec/definition_spec.rb:12:in `block (3 levels) in top (required)' ... 37) ROXML::XMLAttributeRef when the namespaces are different with :namespace = '*' should collect all instances FIXED Expected pending 'Test bug?' to fail. No Error was raised. # ./spec/xml/attributes_spec.rb:58 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-roxml.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795004: marked as done (FTBFS: rspec3: undefined method `color_enabled=' for #RSpec::Core::Config.. (NoMethodError))
Your message dated Sun, 09 Aug 2015 22:22:45 + with message-id e1zoyzn-lr...@franck.debian.org and subject line Bug#795004: fixed in ruby-bogus 0.1.6-1 has caused the Debian Bug report #795004, regarding FTBFS: rspec3: undefined method `color_enabled=' for #RSpec::Core::Config.. (NoMethodError) 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.) -- 795004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-bogus Version: 0.1.5-3 Severity: serious Tags: sid stretch Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build, probably due to incompataility with rspec3: /tmp/buildd/ruby-bogus-0.1.5/spec/spec_helper.rb:12:in `block in top (required)': undefined method `color_enabled=' for #RSpec::Core::Configuration:0x0001637698 (NoMethodError) from /usr/lib/ruby/vendor_ruby/rspec/core.rb:97:in `configure' from /tmp/buildd/ruby-bogus-0.1.5/spec/spec_helper.rb:11:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /tmp/buildd/ruby-bogus-0.1.5/spec/bogus/clean_ruby_spec.rb:1:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke' from /usr/bin/rspec:4:in `main' Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-bogus.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- Source: ruby-bogus Source-Version: 0.1.6-1 We believe that the bug you reported is fixed in the latest version of ruby-bogus, 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 795...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier bou...@debian.org (supplier of updated ruby-bogus 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: Sun, 09 Aug 2015 23:33:37 +0200 Source: ruby-bogus Binary: ruby-bogus Architecture: source all Version: 0.1.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Cédric Boutillier bou...@debian.org Description: ruby-bogus - library creating fakes to make isolated unit tests reliable Closes: 795004 Changes: ruby-bogus (0.1.6-1) unstable; urgency=medium . * Imported Upstream version 0.1.6 + test suite ported to RSpec 3 (Closes: #795004) * Update build-dependencies: add a version for ruby-rspec =3, drop ruby-rr * Update clean_spec_helper.patch * Update packaging with dh-make-ruby -w + Bump Standards-Version to 3.9.6 (no changes needed) Checksums-Sha1: 25a79d034241a5789a2a3eafd3be8a1e35ac8a22 1708 ruby-bogus_0.1.6-1.dsc f8e8f76c06533e151eb14984b1606ec7f9c43cd2 54043 ruby-bogus_0.1.6.orig.tar.gz 4eee453942af54f55505c5464f3b1dc6ce55c74a 3100 ruby-bogus_0.1.6-1.debian.tar.xz 6fdc1cbd2d71d571f410bd00fe5d791ccdbbc19e 36046 ruby-bogus_0.1.6-1_all.deb Checksums-Sha256: 0d83a8b147a2126ea9ba6f56e44cc2ece528a50aa04f889765e3c1c597e1df97 1708 ruby-bogus_0.1.6-1.dsc
Bug#787018: src:xbmc: xbmc does not build on unstable
Hi Mattia, 2015-08-09 16:12 GMT+02:00 Mattia Rizzolo mat...@mapreri.org: On Wed, May 27, 2015 at 10:20:08PM +0200, Bálint Réczey wrote: XBMC has been renamed to Kodi and I have already packaged it. It is waiting for FTP Master approval in the NEW queue for some time. I don't plan updating xbmc, just once, with an empty content to get rid of the epoch while transitioning to kodi. Now kodi is even in testing. What about uploading this empty transition package of xbmc? I think the proper way time of uploading the package would be after uploading replacements for the PVR addons as well. I'm discussing the situation with upstream here: https://github.com/kodi-pvr/pvr.hts/issues/88 Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 777930
Processing commands for cont...@bugs.debian.org: tags 777930 + patch Bug #777930 [src:ksh] ksh: ftbfs with GCC-5 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 777930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777930: ksh: ftbfs with GCC-5
Jakub Wilk wrote: /«BUILDDIR»/ksh-93u+20120801/src/lib/libast/comp/tmpnam.c:48:14: error: storage size of 'buf' isn't known static char buf[L_tmpnam]; ^ Strange error, this is a name-collision error. L_tmpnam was already used for something else, something that obviously was not a number. Please find attached patch that avoids the name-collision simply by replacing the name L_tmpnam in this file with something else. In sid-chroot as-it-is-today and gcc version 5.2.1 20150730 (Debian 5.2.1-14) I now get /bin/ksh93 that starts and .. looks like a shell to me but I'm no Korn shell user so someone who knows how it should behave might want to run a test-suite if there is any to verify that this program really works as expected. This package is scary, instead of using io-functions from libc, this seems to partly implement its own io-functions that are normally found from libc. For linux libc the L_tmpnam is #defined in /usr/include/i386-linux-gnu/bits/stdio_lim.h but this package does not use the same implementation of tmpnam() - anyway here the size of this static buffer is set to be longer than the one in stdio_lim.h so we should be safe for the time being. -- Antti Järvinen gcc5_compiler_fix.patch Description: gcc5 compiler patch for ksh
Bug#795029: ruby-capybara: FTBFS: test failures inc. Capybara.string allows finding only visible nodes
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Source: ruby-capybara
Version: 2.2.1-1
Severity: serious
Justification: fails to build from source
Dear Maintainer,
The package fails to build:
1484 examples, 11 failures, 1274 pending
Failed examples:
rspec ./spec/basic_node_spec.rb:74 # Capybara.string allows finding only
visible nodes
rspec ./spec/basic_node_spec.rb:117 # Capybara.string #has_title? returns
whether the page has the given title
rspec ./spec/basic_node_spec.rb:122 # Capybara.string #has_title? allows regexp
matches
rspec ./spec/basic_node_spec.rb:129 # Capybara.string #has_no_title? returns
whether the page does not have the given title
rspec ./spec/basic_node_spec.rb:134 # Capybara.string #has_no_title? allows
regexp matches
rspec ./spec/rspec/features_spec.rb:18 # Capybara's feature DSL preserves
description
rspec ./spec/rspec/features_spec.rb:26 # Capybara's feature DSL runs background
rspec ./spec/rspec/features_spec.rb:30 # Capybara's feature DSL runs hooks
filtered by file path
rspec ./spec/rspec/features_spec.rb:34 # Capybara's feature DSL doesn't pollute
the Object namespace
rspec ./spec/rspec/features_spec.rb:44 # Capybara's feature DSL nested features
are marked in the metadata as capybara_feature
rspec ./spec/rspec/features_spec.rb:48 # Capybara's feature DSL nested features
have a type of :feature
/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
failed
ERROR: Test ruby2.1 failed. Exiting.
dh_auto_install: dh_ruby --install /ruby-capybara-2.2.1/debian/ruby-capybara
returned exit code 1
debian/rules:4: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary gave error exit status 2
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-capybara.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795034: ruby-fakeweb: FTBFS: test: TypeError(no implicit conversion of Symbol into Integer)
Source: ruby-fakeweb Version: 1.3.0+git20131202.48208f9+dfsg-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: ┌──┐ │ Run tests for ruby2.2 from debian/ruby-tests.rb │ └──┘ RUBYLIB=/ruby-fakeweb-1.3.0+git20131202.48208f9+dfsg/debian/ruby-fakeweb/usr/lib/ruby/vendor_ruby:. ruby2.2 debian/ruby-tests.rb Loaded suite debian/ruby-tests Started ...F === Failure: test_register_uri_without_domain_name(TestFakeWeb) /ruby-fakeweb-1.3.0+git20131202.48208f9+dfsg/test/test_fake_web.rb:38:in `test_register_uri_without_domain_name' 35: end 36: 37: def test_register_uri_without_domain_name = 38: assert_raises URI::InvalidURIError do 39: FakeWeb.register_uri(:get, 'test_example2.txt', fixture_path(test_example.txt)) 40: end 41: end URI::InvalidURIError expected but was TypeError(no implicit conversion of Symbol into Integer) diff: ? URI::InvalidURIError ? Type(no implicit conversion of Symbol into Integer) === ... . Finished in 0.136734476 seconds. -- 188 tests, 351 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-fakeweb.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795035: ruby-fast-gettext: FTBFS: The message expectation for #FastGettext::MoFile (class).new has already been invoked
Source: ruby-fast-gettext Version: 0.9.0-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: ┌──┐ │ Run tests for ruby2.1 from debian/ruby-tests.rb │ └──┘ RUBYLIB=/ruby-fast-gettext-0.9.0/debian/ruby-fast-gettext/usr/lib/ruby/vendor_ruby:. ruby2.1 debian/ruby-tests.rb poparser.ry:244: warning: IO#lines is deprecated; use #each_line instead poparser.ry:244: warning: IO#lines is deprecated; use #each_line instead poparser.ry:244: warning: IO#lines is deprecated; use #each_line instead poparser.ry:244: warning: IO#lines is deprecated; use #each_line instead ... poparser.ry:244: warning: IO#lines is deprecated; use #each_line instead poparser.ry:244: warning: IO#lines is deprecated; use #each_line instead FF. Failures: 1) FastGettext::TranslationRepository::Mo reload can reload Failure/Error: FastGettext::MoFile.stub(:new).and_return(FastGettext::MoFile.empty) The message expectation for #FastGettext::MoFile (class).new has already been invoked and cannot be modified further (e.g. using `and_return`). All message expectation customizations must be applied before it is used for the first time. # ./spec/fast_gettext/translation_repository/mo_spec.rb:27:in `block (3 levels) in top (required)' 2) FastGettext::TranslationRepository::Mo reload returns true Failure/Error: FastGettext::MoFile.stub(:new).and_return(FastGettext::MoFile.empty) The message expectation for #FastGettext::MoFile (class).new has already been invoked and cannot be modified further (e.g. using `and_return`). All message expectation customizations must be applied before it is used for the first time. # ./spec/fast_gettext/translation_repository/mo_spec.rb:27:in `block (3 levels) in top (required)' Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-fast-gettext.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795033: ruby-factory-girl: FTBFS: rspec3 port(?): undefined method `its'
Source: ruby-factory-girl Version: 4.4.0-2 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: ┌──┐ │ Run tests for ruby2.1 from debian/ruby-tests.rake│ └──┘ RUBYLIB=/ruby-factory-girl-4.4.0/debian/ruby-factory-girl/usr/lib/ruby/vendor_ruby:. rake2.1 -f debian/ruby-tests.rake /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing': undefined method `its' for RSpec::ExampleGroups::AliasesAndOverrides:Class (NoMethodError) from /ruby-factory-girl-4.4.0/spec/acceptance/aliases_spec.rb:17:in `block in top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `module_exec' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `subclass' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in `block in define_example_group_method' from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in expose_example_group_alias' from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2 levels) in expose_example_group_alias_globally' from /ruby-factory-girl-4.4.0/spec/acceptance/aliases_spec.rb:3:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke' from /usr/bin/rspec:4:in `main' /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed ERROR: Test ruby2.1 failed. Exiting. Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-factory-girl.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795041: ruby-fssm: FTBFS: monitor with default options test fails: File.exists?
Source: ruby-fssm Version: 0.2.10-2 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: The File System State Monitor paths should accept a valid filesystem directory WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-fssm-0.2.10/spec/path_spec.rb:10:in `block (3 levels) in top (required)'. should not accept an invalid filesystem directory should default the path to the current directory should accept an optional glob array parameter should accept an optional glob string parameter should accept an optional option parameter should default the glob to ['**/*'] should accept a callback for update events should accept a callback for delete events should accept a callback for create events should accept a configuration block should pass file type to callbacks as the third argument if :directories option is used Failures: 1) The File System State Monitor monitor with default options should call create callback upon file creation Failure/Error: File.exists?(file).should be_false expected false to respond to `false?` or perhaps you meant `be false` or `be_falsey` # /usr/lib/ruby/vendor_ruby/rspec/support.rb:86:in `block in module:Support' # /usr/lib/ruby/vendor_ruby/rspec/support.rb:93:in `call' # /usr/lib/ruby/vendor_ruby/rspec/support.rb:93:in `notify_failure' # /usr/lib/ruby/vendor_ruby/rspec/expectations/fail_with.rb:27:in `fail_with' # /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:40:in `handle_failure' # /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:50:in `block in handle_matcher' # /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:27:in `with_matcher' # /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:48:in `handle_matcher' # /usr/lib/ruby/vendor_ruby/rspec/expectations/syntax.rb:45:in `should' # ./spec/monitor_spec.rb:62:in `block (5 levels) in top (required)' # ./spec/monitor_spec.rb:40:in `run_monitor' # ./spec/monitor_spec.rb:60:in `block (4 levels) in top (required)' # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:206:in `instance_exec' ... Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-fssm.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795043: ruby-merb-param-protection: FTBFS: uninitialized constant RSpec::Runner (NameError)
Source: ruby-merb-param-protection Version: 1.1.3-2 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: ... Selecting previously unselected package ruby-rspec-support. Preparing to unpack .../ruby-rspec-support_3.3.0c0e0m0s0-1_all.deb ... Unpacking ruby-rspec-support (3.3.0c0e0m0s0-1) ... Selecting previously unselected package ruby-rspec-expectations. Preparing to unpack .../ruby-rspec-expectations_3.3.0c0e0m0s0-1_all.deb ... Unpacking ruby-rspec-expectations (3.3.0c0e0m0s0-1) ... Selecting previously unselected package ruby-rspec-mocks. Preparing to unpack .../ruby-rspec-mocks_3.3.0c0e0m0s0-1_all.deb ... Unpacking ruby-rspec-mocks (3.3.0c0e0m0s0-1) ... ┌──┐ │ Run tests for ruby2.1 from debian/ruby-tests.rb │ └──┘ RUBYLIB=/ruby-merb-param-protection-1.1.3/debian/ruby-merb-param-protection/usr/lib/ruby/vendor_ruby:. ruby2.1 debian/ruby-tests.rb ~ No Gemfile found! If you're generating new app with merb-gen this is fine, otherwise run: bundle init to create Gemfile Digest::Digest is deprecated; use Digest /usr/lib/ruby/vendor_ruby/rspec/core.rb:179:in `block in const_missing': uninitialized constant RSpec::Runner (NameError) from /usr/lib/ruby/vendor_ruby/rspec/core.rb:179:in `fetch' from /usr/lib/ruby/vendor_ruby/rspec/core.rb:179:in `const_missing' from /ruby-merb-param-protection-1.1.3/spec/spec_helper.rb:19:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /ruby-merb-param-protection-1.1.3/spec/merb_param_protection_spec.rb:1:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from debian/ruby-tests.rb:5:in `block in main' from debian/ruby-tests.rb:5:in `each' from debian/ruby-tests.rb:5:in `main' ERROR: Test ruby2.1 failed. Exiting. Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-merb-param-protection.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789404: pbuilder: insecure use of /tmp
Jakub Wilk dixit: And there's DoS aspect: local user could stuff chroot's /tmp with garbage, which pbuilder then will have to compress and later decompress on every build. Meh, it's probably trivial to let it create the chroot inside a temporary directory other users may not traverse. The current “let's move the build dir” stinks much more, why not pre-create /tmp/build in the chroot to be writable only to the buildd user? bye, //mirabilos -- diogenese Beware of ritual lest you forget the meaning behind it. igli yeah but it means if you really care about something, don't ritualise it, or you will lose it. don't fetishise it, don't obsess. or you'll forget why you love it in the first place. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795044: ruby-packetfu: FTBFS: undefined method `its' for #Class:0x..
Source: ruby-packetfu
Version: 1.1.10-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
The package fails to build:
┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rb │
└──┘
RUBYLIB=/ruby-packetfu-1.1.10/debian/ruby-packetfu/usr/lib/ruby/vendor_ruby:.
ruby2.1 debian/ruby-tests.rb
/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
/usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing':
undefined method `its' for #Class:0x00016c4ae8 (NoMethodError)
from /ruby-packetfu-1.1.10/spec/ethpacket_spec.rb:29:in `block (2
levels) in top (required)'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in
`block in define_example_group_method'
from /ruby-packetfu-1.1.10/spec/ethpacket_spec.rb:13:in `block in top
(required)'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in
`block in define_example_group_method'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in
expose_example_group_alias'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2
levels) in expose_example_group_alias_globally'
from /ruby-packetfu-1.1.10/spec/ethpacket_spec.rb:6:in `top
(required)'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke'
from /usr/bin/rspec:4:in `main'
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-packetfu.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777851: marked as done (flexpart: ftbfs with GCC-5)
Your message dated Sun, 09 Aug 2015 21:35:39 + with message-id e1zoyfn-0001ur...@franck.debian.org and subject line Bug#777851: fixed in flexpart 9.02-11 has caused the Debian Bug report #777851, regarding flexpart: ftbfs with GCC-5 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.) -- 777851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:flexpart Version: 9.02-9 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/flexpart_9.02-9_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include writeheader.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include assignland.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include calcpar_gfs.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include part0.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include caldate.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include partdep.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include coordtrafo.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include psih.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include raerod.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include drydepokernel.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include random.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include erf.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include readavailable.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include ew.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include readcommand.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include advance.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include readdepo.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include releaseparticles.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include psim.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include FLEXPART.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include readlanduse.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include getfields.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include init_domainfill.f90 gfortran -c -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include
Bug#794955: marked as done (gperf: Embedded code copy with missing copyright)
Your message dated Sun, 09 Aug 2015 21:35:51 + with message-id e1zoyfz-0001zg...@franck.debian.org and subject line Bug#794955: fixed in gperf 3.0.4-2 has caused the Debian Bug report #794955, regarding gperf: Embedded code copy with missing copyright 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.) -- 794955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gperf Version: 3.0.4-1 Severity: serious Justification: Policy 4.5 User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps Hi, Your packages contains an embedded code copy of texi2html which is copyright Lionel Cons and others and is licensed under the GPL and Creative Commons Attribution-ShareAlike license. This information is missing from debian/copyright of gperf and is thus a violation of policy §4.5. I found this bug while working on the reproducible builds project [1] to make texi2html produce reproducible output. From that point of view there are two options: 1. remove the embedded code copy [2] and build-depend on texi2html (this would also make policy §4.13 happy). I would prefer this solution and would supply you with a patch if you want. Your package would then automatically become reproducible. 2. keep the embedded code copy and amend your debian/copyright. In this case I would open another bug so that your embedded copy of texi2html is patched to produce reproducible output. Kind regards, akira [1] https://wiki.debian.org/ReproducibleBuilds/About [2] https://wiki.debian.org/EmbeddedCodeCopies ---End Message--- ---BeginMessage--- Source: gperf Source-Version: 3.0.4-2 We believe that the bug you reported is fixed in the latest version of gperf, 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 794...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen ben...@debian.org (supplier of updated gperf 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: Sun, 09 Aug 2015 21:19:41 +0200 Source: gperf Binary: gperf Architecture: source amd64 Version: 3.0.4-2 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen ben...@debian.org Changed-By: Hilko Bengen ben...@debian.org Description: gperf - Perfect hash function generator Closes: 794955 Changes: gperf (3.0.4-2) unstable; urgency=medium . * Bumped Standards-Version * Added doc/texi2html license to debian/copyright; use texinfo instead of texi2html to generate HTML documentation (Closes: #794955) Checksums-Sha1: 2dfd6b865e9693bb16635258635cd9ba94de6fe4 1675 gperf_3.0.4-2.dsc 8d496058be3b9553194b08cf0b5d80a6e5e3ba02 4544 gperf_3.0.4-2.debian.tar.xz 7cfd008c2cbd2762ff251959212b5cae247469bc 142626 gperf_3.0.4-2_amd64.deb Checksums-Sha256: 7bcb2fb491ae6bcef26aacfee578b83cd16e841f9c97edb74322f4340f2a771a 1675 gperf_3.0.4-2.dsc f4c9e00761f26a17c097ea203370345efada79fdeb2641d31614575b00484b18 4544 gperf_3.0.4-2.debian.tar.xz 68fbb9fae50a1e494eab89ed40d626bb0fe44ea527739a8266e39197d788071e 142626 gperf_3.0.4-2_amd64.deb Files: 2eca7e8a72d81156744fbba40519d432 1675 devel optional gperf_3.0.4-2.dsc 7b89c9a0cefcc176a4d1fbf65c25bb1f 4544 devel optional gperf_3.0.4-2.debian.tar.xz f088317528a3dbaaf78da4abaf2cf937 142626 devel optional gperf_3.0.4-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVx65xAAoJEHW3EGNcITp+rEsQAIDIDV3d+GCmDpp9noRdKqFR 1Xj7VCCr0IpfATxdAgYg4wuua5SwiBaEP/ey0TOSelgUlfyVeNiVfULFb8AtJXvB 24XOz3z6+XTV+F9VwZQrPx4Fck+O+83p4wPk0GuxTa0FAPoNlQ/9PrefSboEO7EH UN8xvK8fbirSPsoUUVKMsgysa1ecOYl7W6pg7+AnerVjHyFMwYKi2fE0Xj/lwRVg jshHALGgunFNdosboGESlBa09S/zD+PZqoQx621NT8uptYutIkAuFGlNCM9oIHBh XLCeGhVMb5MvnDTaUc+VVcdRoIFunDQy0+cPI8nvXXmvAFQSomWNUQ6xcsZIfBQ6 zSRJIg2Wl8g5502Du+04OINsjbxgzQYSt7PebpQevaxajMqGMY3HcsptZ/9eDY1t z6ilfdpMwPkq599/pIHlwmoGm+Z/O0UteGWsCnqVzuyBBs+dF9gbth04VULoYSla /qI+OcsPhwtcQw+qGZYVt3tO2h4XoQtUCpq6uRbGwC0k13YAS2FmMFgjBv9oOAPN c79CVO7LEDQorAUXZPvJyQhhanDFih4LI2u3Tt1eoIEzM1ILmL0UACWCbtlx/Qbe 9Ux7T2Ec70dvWG3vCcuDsX79p4NbIJ0Gkwp9yHF8Uk16zEOu1KG+6OxU8dEfuvVc j6JvbNMerz3ODuIKes7i =Fm6C -END PGP
Bug#777967: marked as done (libphonenumber: ftbfs with GCC-5)
Your message dated Sun, 09 Aug 2015 21:36:14 + with message-id e1zoygm-00026i...@franck.debian.org and subject line Bug#777967: fixed in libphonenumber 6.3~svn698-4 has caused the Debian Bug report #777967, regarding libphonenumber: ftbfs with GCC-5 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.) -- 777967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libphonenumber Version: 6.3~svn698-3 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/libphonenumber_6.3~svn698-3_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] ^ /usr/include/boost/thread/once.hpp:35:13: note: template argument deduction/substitution failed: /usr/include/boost/thread/once.hpp:38:18: note: cannot convert 'func' (type 'void (*)()') to type 'boost::once_flag' call_once(flag,func); ^ make[4]: *** [CMakeFiles/phonenumber.dir/src/phonenumbers/phonenumberutil.cc.o] Error 1 make[4]: *** Waiting for unfinished jobs CMakeFiles/phonenumber.dir/build.make:248: recipe for target 'CMakeFiles/phonenumber.dir/src/phonenumbers/phonenumberutil.cc.o' failed In file included from /«PKGBUILDDIR»/cpp/src/phonenumbers/base/memory/singleton.h:23:0, from /«PKGBUILDDIR»/cpp/src/phonenumbers/phonenumbermatcher.cc:41: /usr/include/boost/thread/once.hpp: In instantiation of 'void boost::call_once(Function, boost::once_flag) [with Function = void (*)()]': /«PKGBUILDDIR»/cpp/src/phonenumbers/base/memory/singleton.h:35:21: required from 'static T* i18n::phonenumbers::SingletonT::GetInstance() [with T = i18n::phonenumbers::PhoneNumberMatcherRegExps]' /«PKGBUILDDIR»/cpp/src/phonenumbers/phonenumbermatcher.cc:398:44: required from here /usr/include/boost/thread/once.hpp:38:18: error: no matching function for call to 'call_once(boost::once_flag, void (*)())' call_once(flag,func); ^ In file included from /usr/include/boost/thread/once.hpp:20:0, from /«PKGBUILDDIR»/cpp/src/phonenumbers/base/memory/singleton.h:23, from /«PKGBUILDDIR»/cpp/src/phonenumbers/phonenumbermatcher.cc:41: /usr/include/boost/thread/pthread/once_atomic.hpp:121:15: note: candidate: templateclass Function, class ... ArgTypes void boost::call_once(boost::once_flag, boost::detail::thread_move_tT, boost::detail::thread_move_tArgs...) inline void call_once(once_flag flag, BOOST_THREAD_RV_REF(Function) f, BOOST_THREAD_RV_REF(ArgTypes)... args) ^ /usr/include/boost/thread/pthread/once_atomic.hpp:121:15: note: template argument deduction/substitution failed: In file included from /«PKGBUILDDIR»/cpp/src/phonenumbers/base/memory/singleton.h:23:0, from /«PKGBUILDDIR»/cpp/src/phonenumbers/phonenumbermatcher.cc:41: /usr/include/boost/thread/once.hpp:38:18: note: mismatched types 'boost::detail::thread_move_tT' and 'void (*)()' call_once(flag,func); ^ /usr/include/boost/thread/once.hpp:35:13: note: candidate: templateclass Function void boost::call_once(Function, boost::once_flag) inline void call_once(Function func,once_flag flag) ^ /usr/include/boost/thread/once.hpp:35:13: note: template argument deduction/substitution failed: /usr/include/boost/thread/once.hpp:38:18: note: cannot convert 'func' (type 'void (*)()') to type 'boost::once_flag' call_once(flag,func); ^
Bug#795045: ruby-orm-adapter: FTBFS: undefined method `its' for #Class:0x..
Source: ruby-orm-adapter Version: 0.5.0-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: ┌──┐ │ Run tests for ruby2.1 from debian/ruby-tests.rake│ └──┘ RUBYLIB=/ruby-orm-adapter-0.5.0/debian/ruby-orm-adapter/usr/lib/ruby/vendor_ruby:. rake2.1 -f debian/ruby-tests.rake /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing': undefined method `its' for #Class:0xfa5898 (NoMethodError) from /ruby-orm-adapter-0.5.0/spec/orm_adapter_spec.rb:9:in `block (2 levels) in top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `module_exec' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `subclass' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in `block in define_example_group_method' from /ruby-orm-adapter-0.5.0/spec/orm_adapter_spec.rb:6:in `block in top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `module_exec' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `subclass' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in `block in define_example_group_method' from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in expose_example_group_alias' from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2 levels) in expose_example_group_alias_globally' from /ruby-orm-adapter-0.5.0/spec/orm_adapter_spec.rb:3:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke' from /usr/bin/rspec:4:in `main' Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-orm-adapter.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777852: marked as done (flextra: ftbfs with GCC-5)
Your message dated Sun, 09 Aug 2015 21:35:45 + with message-id e1zoyft-0001x7...@franck.debian.org and subject line Bug#777852: fixed in flextra 5.0-3 has caused the Debian Bug report #777852, regarding flextra: ftbfs with GCC-5 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.) -- 777852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:flextra Version: 5.0-2.1 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/flextra_5.0-2.1_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] fakeroot debian/rules clean dh clean dh_testdir debian/rules override_dh_auto_clean make[1]: Entering directory '/«PKGBUILDDIR»' rm -f *.o flextra.ecmwf flextra.gfs make[1]: Leaving directory '/«PKGBUILDDIR»' dh_clean debian/rules build-arch dh build-arch dh_testdir -a dh_auto_configure -a debian/rules override_dh_auto_build make[1]: Entering directory '/«PKGBUILDDIR»' /usr/bin/make -f makefile.ecmwf LDFLAGS=-Wl,-z,relro FCFLAGS=-g -O2 -fstack-protector-strong make[2]: Entering directory '/«PKGBUILDDIR»' f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o caldate.o caldate.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o openoutput.o openoutput.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o checklimits.o checklimits.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o coordtrafo.o coordtrafo.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o orolininterpol.o orolininterpol.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o etatrafo.o etatrafo.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o petters.o petters.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o eta.ecmwf.o eta.ecmwf.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o FLEXTRA.o FLEXTRA.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o pp.ecmwf.o pp.ecmwf.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o geteta.o geteta.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o getfields.o getfields.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o pvinterpol.o pvinterpol.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o getheight.o getheight.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o random.o random.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o readavailable.o readavailable.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o getwind.o getwind.f f77 -g -O2 -fstack-protector-strong -fPIC -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o
Bug#790975: marked as done (afflib: library transition may be needed when GCC 5 is the default)
Your message dated Sun, 09 Aug 2015 23:00:11 + with message-id e1zozzb-0006dh...@franck.debian.org and subject line Bug#790975: fixed in afflib 3.7.6-5 has caused the Debian Bug report #790975, regarding afflib: library transition may be needed when GCC 5 is the default 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.) -- 790975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:afflib Version: 3.7.6-2 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for BEGIN GCC CXX11 in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition ---End Message--- ---BeginMessage--- Source: afflib Source-Version: 3.7.6-5 We believe that the bug you reported is fixed in the latest version of afflib, 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 790...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho eribe...@debian.org (supplier of updated afflib 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: SHA1 Format: 1.8 Date: Sun, 09 Aug 2015 02:09:04 -0300 Source: afflib Binary: libafflib0v5 libafflib-dev afflib-dbg afflib-tools Architecture: source amd64 Version: 3.7.6-5 Distribution: unstable Urgency: medium Maintainer: Debian Forensics forensics-de...@lists.alioth.debian.org Changed-By: Joao Eriberto Mota Filho eribe...@debian.org Description: afflib-dbg - Advanced Forensics Format Library (debug version) afflib-tools - Advanced Forensics Format Library (utilities) libafflib-dev - Advanced Forensics Format Library (development files) libafflib0v5 - Advanced Forensics Format Library Closes: 790975 Changes: afflib (3.7.6-5) unstable; urgency=medium . [
Bug#793991: [Pkg-pascal-devel] Bug#793991: lazarus: armel and armhf builds stall
Hi On 09-08-15 21:24, Paul Gevers wrote: So maybe we need just to rebuild again? Looking at what Graham already did, it does not appear to help. But maybe it does... the linker was updated yesterday, so maybe that is why your problem didn't appear after stripping. If that is true, we just need a give-back to fix the issue. Paul signature.asc Description: OpenPGP digital signature
Bug#793991: lazarus: armel and armhf builds stall
H Paul, On Sun, 2015-08-09 at 21:29 +0200, Paul Gevers wrote: Hi On 09-08-15 21:24, Paul Gevers wrote: So maybe we need just to rebuild again? Looking at what Graham already did, it does not appear to help. But maybe it does... the linker was updated yesterday, so maybe that is why your problem didn't appear after stripping. If that is true, we just need a give-back to fix the issue. At least my experiments show that a today's built lazbuild does not suffer from that issue. It could be just a matter of luck, or related to the new linker update, but if this could help avoiding to get Lazarus kicked from testing it is worth tried. We can also try to redirect ld.bfd std err to a grep -v '^ *$' to get rid of blank lines maybe. -- Cheers, Abou Al Montacir -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795050: ruby-semverse: FTBFS: rspec3 port(?): undefined method `have'
Source: ruby-semverse
Version: 1.1.0-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
The package fails to build:
┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake│
└──┘
RUBYLIB=/ruby-semverse-1.1.0/debian/ruby-semverse/usr/lib/ruby/vendor_ruby:.
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
Run options: include {:focus=true}
All examples were filtered out; ignoring {:focus=true}
Randomized with seed 19129
..FFF..FF.FF.F.F.FF.F...FF.F..F.FF.F.F...FFF..FFF...FFF...F..F.F.F..F.F..FF..FF.F.F.FF..FF.FF.F.F..FF.F...F...FF..F..F.F.F...F..FF..F...F.F..F.F.F...FF.FF.F.FF..FF..FF.FFF.F.F.FF...F...F...FF.FF..F..F..F....F..F.FF.F..FF..FFF..F...
Failures:
1) Semverse::Constraint#satisfies? should satisfies #Semverse::Version 1.0.0
Failure/Error: it { should satisfies(Semverse::Version.new(1.0.0)) }
expected #Semverse::Constraint = 1.0.0 to satisfies
#Semverse::Version 1.0.0
# ./spec/unit/semverse/constraint_spec.rb:262:in `block (3 levels) in top
(required)'
2) Semverse::Constraint#satisfies? should satisfies 1.0.0
Failure/Error: it { should satisfies(1.0.0) }
expected #Semverse::Constraint = 1.0.0 to satisfies 1.0.0
# ./spec/unit/semverse/constraint_spec.rb:261:in `block (3 levels) in top
(required)'
...
178) Semverse::Version ClassMethods ::split given a string only containing a
major and minor version returns an array containing 4 elements
Failure/Error: expect(subject.split(1.2)).to have(3).items
NoMethodError:
undefined method `have' for
#RSpec::ExampleGroups::SemverseVersion::ClassMethods::Split::GivenAStringOnlyContainingAMajorAndMinorVersion:0x0001b95d10
# ./spec/unit/semverse/version_spec.rb:246:in `block (5 levels) in top
(required)'
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-semverse.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795044: marked as done (ruby-packetfu: FTBFS: undefined method `its' for #Class:0x..)
Your message dated Sun, 09 Aug 2015 23:36:23 +
with message-id e1zoa8d-0003fo...@franck.debian.org
and subject line Bug#795044: fixed in ruby-packetfu 1.1.10-2
has caused the Debian Bug report #795044,
regarding ruby-packetfu: FTBFS: undefined method `its' for #Class:0x..
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.)
--
795044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: ruby-packetfu
Version: 1.1.10-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
The package fails to build:
┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rb │
└──┘
RUBYLIB=/ruby-packetfu-1.1.10/debian/ruby-packetfu/usr/lib/ruby/vendor_ruby:.
ruby2.1 debian/ruby-tests.rb
/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
/usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing':
undefined method `its' for #Class:0x00016c4ae8 (NoMethodError)
from /ruby-packetfu-1.1.10/spec/ethpacket_spec.rb:29:in `block (2
levels) in top (required)'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in
`block in define_example_group_method'
from /ruby-packetfu-1.1.10/spec/ethpacket_spec.rb:13:in `block in top
(required)'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in
`block in define_example_group_method'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in
expose_example_group_alias'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2
levels) in expose_example_group_alias_globally'
from /ruby-packetfu-1.1.10/spec/ethpacket_spec.rb:6:in `top
(required)'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke'
from /usr/bin/rspec:4:in `main'
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-packetfu.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
---End Message---
---BeginMessage---
Source: ruby-packetfu
Source-Version: 1.1.10-2
We believe that the bug you reported is fixed in the latest version of
ruby-packetfu, 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 795...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Cédric Boutillier bou...@debian.org (supplier of updated ruby-packetfu
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: Mon, 10 Aug 2015 01:27:34 +0200
Source: ruby-packetfu
Binary: ruby-packetfu
Architecture: source all
Version: 1.1.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby
Bug#793991: [Pkg-pascal-devel] Bug#793991: lazarus: armel and armhf builds stall
Hi Abou, On 09-08-15 20:39, Abou Al Montacir wrote: I'll file a bug upstream. Graham was able to get a little further as well, which is documented in the upstream bug report [1]. I tried this on porterbox abel and reproduced the issue. However I failed to completely understand it. It looks like it hangs when running ld.bfd. Indeed when pressing ctrl+z I got: (sid_armel-dchroot)abou@abel:~/ddrescueview-0.4~alpha2/source$ ps -elf | grep ddrescueview 0 T abou32221 27954 0 80 0 - 5412 signal 18:25 pts/100:00:00 lazbuild ddrescueview.lpi 0 T abou32232 32221 0 80 0 - 178 signal 18:25 pts/100:00:00 /usr/bin/fpc -B -MObjFPC -Schi -CX -Cirot -g -gl -XX -l -vewnhibq -Fl/opt/gnome/lib -Fu/usr/lib/lazarus/1.4.0/lcl/units/arm-linux/gtk2 -Fu/usr/lib/lazarus/1.4.0/lcl/units/arm-linux -Fu/usr/lib/lazarus/1.4.0/components/lazutils/lib/arm-linux -Fu/usr/lib/lazarus/1.4.0/packager/units/arm-linux -Fu/home/abou/ddrescueview-0.4~alpha2/source/ -dLCL -dLCLgtk2 ddrescueview.lpr 0 T abou32233 32232 4 80 0 - 4031 signal 18:25 pts/100:00:03 /usr/bin/ppcarm -B -MObjFPC -Schi -CX -Cirot -g -gl -XX -l -vewnhibq -Fl/opt/gnome/lib -Fu/usr/lib/lazarus/1.4.0/lcl/units/arm-linux/gtk2 -Fu/usr/lib/lazarus/1.4.0/lcl/units/arm-linux -Fu/usr/lib/lazarus/1.4.0/components/lazutils/lib/arm-linux -Fu/usr/lib/lazarus/1.4.0/packager/units/arm-linux -Fu/home/abou/ddrescueview-0.4~alpha2/source/ -dLCL -dLCLgtk2 ddrescueview.lpr 0 T abou32243 32233 5 80 0 - 17728 signal 18:25 pts/100:00:03 /usr/bin/ld.bfd --dynamic-linker=/lib/ld-linux.so.3 --gc-sections -L. -o ddrescueview link.res 0 S abou32249 27954 0 80 0 - 637 pipe_w 18:26 pts/100:00:00 grep ddrescueview when fg and then ctrl+c it seems to resume. I also recompiled lazbuild to get debug symbols, but then I do not have the issue anymore. I even stripped the newly build binary and did not have the issue. So maybe we need just to rebuild again? Looking at what Graham already did, it does not appear to help. Paul [1] http://bugs.freepascal.org/view.php?id=28448 signature.asc Description: OpenPGP digital signature
Bug#794817: Should mplayer2 be removed from unstable?
On Thu, Aug 6, 2015 at 9:21 PM Sebastian Ramacher sramac...@debian.org wrote: On 2015-08-06 23:05:58, Andreas Cadhalpun wrote: Package: mplayer2 Severity: serious I think mplayer2 should be removed because: * It is dead upstream (even the homepage is gone). * mplayer is back in Debian, which can replace mplayer2. … and one copy of mplayer is surely enough. Alessio, Jonas, Reinhard: What is your opinion on that? I don't think we have the resources (mostly manpower) to maintain mplayer2 without an active upstream. I'm therefore OK with removing it from unstable. If the maintenance situation changes, we can always reconsider. Reinhard
Bug#790796: sensord: RRD data loss
On 2015-08-09 00:21, Vincent Lefevre wrote: Hi, On 2015-08-08 23:30:26 +0200, Aurelien Jarno wrote: From what I have been able to get the problem is that when using a single rrd file for all data, the number of columns (ie sensors) is defined when the file is created. Therefore the upgrade of your kernel changed the number of sensors, and caused this issue. From what I have been able to read in the documentation, one solution would be to use the MULTIPLE mode of RRD, which create one file per column or sensor. But this format is incompatible with the current one, which means people will have to recreate their database, and possibly the scripts extracting the data for them. This could be an option (set by default to avoid problems in the future). But anyway, after upgrading the kernel (even a security update!), the database is currently no longer usable. So, this would not be worse than the current situation. I will try to look if it is something doable. I don't really know what is the solution for this bug, one might be to stop shipping sensord in Debian as it is kind of dead upstream and not build by default. Is there a replacement? Well I am not sure we need a replacement for something which is just unusable. That said, yes there are replacements. I am personally using munin to plot temperatures/voltages/fan speed graphs, but I am sure there are plenty of other monitoring system. Or perhaps it's easy enough for the user to write a daemon in a shell/Perl/whatever script by executing the sensors utility. BTW, I already have written such a utility in Perl, which supports CPU load, disk usage and entropy. Adding sensors support would really be easy. Or by using libsensors instead of parsing the output of sensors, which might slightly change over the time. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795032: ruby-cstruct: FTBFS: rspec3 port needed(?): undefined method `its'
Source: ruby-cstruct Version: 1.0.1-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: ┌──┐ │ Run tests for ruby2.1 from debian/ruby-tests.rake│ └──┘ RUBYLIB=/ruby-cstruct-1.0.1/debian/ruby-cstruct/usr/lib/ruby/vendor_ruby:. rake2.1 -f debian/ruby-tests.rake /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*_spec.rb /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing': undefined method `its' for RSpec::ExampleGroups::NormalMemberPoint:Class (NoMethodError) from /ruby-cstruct-1.0.1/spec/cstruct_spec.rb:18:in `block in top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `module_exec' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `subclass' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in `block in define_example_group_method' from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in expose_example_group_alias' from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2 levels) in expose_example_group_alias_globally' from /ruby-cstruct-1.0.1/spec/cstruct_spec.rb:6:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke' from /usr/bin/rspec:4:in `main' Test CStruct-1.0.1 /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*_spec.rb failed ERROR: Test ruby2.1 failed. Exiting. Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-cstruct.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795042: ruby-gnuplot: FTBFS: test_gnuplot.rb:97: uninitialized constant Config (NameError)
Source: ruby-gnuplot
Version: 2.6.2-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
The package fails to build:
┌──┐
│ Run tests for ruby2.2 from debian/ruby-test-files.yaml │
└──┘
RUBYLIB=/ruby-gnuplot-2.6.2/debian/ruby-gnuplot/usr/lib/ruby/vendor_ruby:.
ruby2.2 -ryaml -e YAML.load_file\(\debian/ruby-test-files.yaml\\).each\ \{\
\|f\|\ require\ f\ \}
created sin_wave.gif
/ruby-gnuplot-2.6.2/test/test_gnuplot.rb:97:in `top (required)':
uninitialized constant Config (NameError)
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
`require'
from -e:1:in `block in main'
from -e:1:in `each'
from -e:1:in `main'
ERROR: Test ruby2.2 failed. Exiting.
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-gnuplot.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794658: marked as done (libphonenumber6: Debian Sid: unresolved dependencies for libboost* version 1.55 while 1.58 installled)
Your message dated Sun, 09 Aug 2015 21:36:14 + with message-id e1zoygm-00026o...@franck.debian.org and subject line Bug#794658: fixed in libphonenumber 6.3~svn698-4 has caused the Debian Bug report #794658, regarding libphonenumber6: Debian Sid: unresolved dependencies for libboost* version 1.55 while 1.58 installled 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.) -- 794658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libphonenumber6 Version: 6.3~svn698-3+b1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.1-towo.2-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libphonenumber6 depends on: WARNING: I MODIFIED THIS! It also depends on libboost-date-time1.55 - cannot be installed (1.58 installed) libboost-threads1.55 - cannot be installed (1.58 installed) ii libc6 2.19-19 ii libgcc11:5.2.1-14 ii libicu52 52.1-10 ii libprotobuf9 2.6.1-1 ii libstdc++6 5.2.1-14 ii multiarch-support 2.19-19 libphonenumber6 recommends no packages. libphonenumber6 suggests no packages. -- no debconf information With this package not working (and does not compile from source, fails one of the tests) all my graphical system (gnome) collapsed and became completely unusable. Why such a package should must be related so strictly to a version of libboost? Why cannot it be related to a version grater than 1.55? ---End Message--- ---BeginMessage--- Source: libphonenumber Source-Version: 6.3~svn698-4 We believe that the bug you reported is fixed in the latest version of libphonenumber, 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 794...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill tmanc...@debian.org (supplier of updated libphonenumber 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: Sun, 09 Aug 2015 13:09:47 -0700 Source: libphonenumber Binary: libphonenumber6-java libphonenumber6-dev libphonenumber6 Architecture: source amd64 all Version: 6.3~svn698-4 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: tony mancill tmanc...@debian.org Description: libphonenumber6 - parsing/formatting/validating phone numbers libphonenumber6-dev - parsing/formatting/validating phone numbers - development files libphonenumber6-java - parsing/formatting/validating phone numbers - java Closes: 777967 794658 794900 Changes: libphonenumber (6.3~svn698-4) unstable; urgency=medium . * Team upload. * Rebuild against libboost in unstable (that is = 1.58). - (Closes: #794900, #794658) * Add patch to remove the deprecated forkMode parameter in the maven-surefire-plugin configuration. This was causing tests to fail and made the package FTBFS. * Test compilations with GCC-5 from experimental also indicate that this package now successfully builds without source changes (surely due to the updated libboost). (Closes: #777967) Checksums-Sha1: f37b251beb35206299d41f5d899b9033228a50f8 2755 libphonenumber_6.3~svn698-4.dsc 879df8d88f90efb0d6d3d39e8f5c5851d0d3671d 8828 libphonenumber_6.3~svn698-4.debian.tar.xz b67668082726d430c0dd2b9d4b22ff139b9d251b 1034638 libphonenumber6-dev_6.3~svn698-4_amd64.deb
Bug#795047: ruby-powerpack: FTBFS: rspec3 port(?): 26 failures around ...to be_true
Source: ruby-powerpack
Version: 0.1.0-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
The package fails to build:
..F.FF..FFF...
Failures:
1) Enumerable#exactly with block returns true for exact number of matches
Failure/Error: expect([1, 2, 3, 4].exactly?(2, :even?)).to be_true
expected true to respond to `true?` or perhaps you meant `be true` or
`be_truthy`
# ./spec/powerpack/enumerable/exactly_spec.rb:6:in `block (3 levels) in
top (required)'
...
25) String#blank? returns true for a string with only whitespace in it
Failure/Error: expect(' '.blank?).to be_true
expected true to respond to `true?` or perhaps you meant `be true` or
`be_truthy`
# ./spec/powerpack/string/blank_spec.rb:9:in `block (2 levels) in top
(required)'
26) String#blank? returns false for a string with non-whitespace chars in it
Failure/Error: expect(' test'.blank?).to be_false
expected false to respond to `false?` or perhaps you meant `be false`
or `be_falsey`
# ./spec/powerpack/string/blank_spec.rb:13:in `block (2 levels) in top
(required)'
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-powerpack.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#795049: ruby-rubyvis: FTBFS: cannot load such file -- rspec/expectations/differ
Source: ruby-rubyvis Version: 0.6.1+dfsg1-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: ┌──┐ │ Run tests for ruby2.1 from debian/ruby-tests.rake│ └──┘ RUBYLIB=/ruby-rubyvis-0.6.1+dfsg1/debian/ruby-rubyvis/usr/lib/ruby/vendor_ruby:. rake2.1 -f debian/ruby-tests.rake /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*_spec.rb /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- rspec/expectations/differ (LoadError) from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /ruby-rubyvis-0.6.1+dfsg1/spec/area_spec.rb:1:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke' from /usr/bin/rspec:4:in `main' /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*_spec.rb failed Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-rubyvis.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
