Bug#755339: marked as done (foolscap: FTBFS: Tests failures)
Your message dated Sun, 03 Aug 2014 06:18:36 + with message-id e1xdp7s-0003mk...@franck.debian.org and subject line Bug#755339: fixed in foolscap 0.6.4-3 has caused the Debian Bug report #755339, regarding foolscap: FTBFS: Tests failures 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.) -- 755339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: foolscap Version: 0.6.4-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140718 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): test_format ... [OK] === [SKIPPED] new-style classes still broken foolscap.test.test_banana.ThereAndBackAgain.test_boundMethod_newstyle foolscap.test.test_banana.ThereAndBackAgain.test_classMethod_newstyle foolscap.test.test_banana.ThereAndBackAgain.test_class_newstyle foolscap.test.test_banana.ThereAndBackAgain.test_instance_newstyle === [ERROR] Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/twisted/trial/runner.py, line 498, in loadPackage module = modinfo.load() File /usr/lib/python2.7/dist-packages/twisted/python/modules.py, line 383, in load return self.pathEntry.pythonPath.moduleLoader(self.name) File /usr/lib/python2.7/dist-packages/twisted/python/reflect.py, line 303, in namedAny topLevelPackage = _importAndCheckStack(trialname) File /usr/lib/python2.7/dist-packages/twisted/python/reflect.py, line 242, in _importAndCheckStack return __import__(importName) File /«PKGBUILDDIR»/foolscap/test/test_promise.py, line 5, in module from foolscap.promise import makePromise, send, sendOnly, when, UsageError File /«PKGBUILDDIR»/foolscap/promise.py, line 8, in module id = util.unsignedID exceptions.AttributeError: 'module' object has no attribute 'unsignedID' foolscap.test.test_promise --- Ran 452 tests in 89.288s FAILED (skips=4, errors=1, successes=447) make[2]: *** [test] Error 1 dh_auto_test: make -j1 test returned exit code 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/07/18/foolscap_0.6.4-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: foolscap Source-Version: 0.6.4-3 We believe that the bug you reported is fixed in the latest version of foolscap, 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 755...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Taylor jtaylor.deb...@googlemail.com (supplier of updated foolscap 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: Wed, 30 Jul 2014 22:47:24 +0200 Source: foolscap Binary: python-foolscap Architecture: source all Version: 0.6.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: Julian Taylor jtaylor.deb...@googlemail.com Description: python-foolscap - object-capability-based RPC system for Twisted Python Closes: 755339 Changes: foolscap (0.6.4-3) unstable; urgency=medium . * promise.py-make-compatible-with-Twisted-14.0.0.patch: restore compatibility with twisted (Closes: #755339) Checksums-Sha1: 9b2997e4698514f0a67ec752703530f63a30f6a2 2151 foolscap_0.6.4-3.dsc 300c27149f43dad2fbfa418a61c3688af12ae3f9 6824 foolscap_0.6.4-3.debian.tar.xz ef36ce0e194819c4c6f4326beef010856f973b4e
Bug#756784: visp: FTBFS on powerpc
Le 03/08/14 05:37, Thomas Moulard a écrit : I asked for a rebuild a while ago, still waiting for an answer: https://lists.debian.org/debian-wb-team/2014/07/msg00015.html Is there something more to do? I also asked yesterday https://lists.debian.org/debian-wb-team/2014/08/msg4.html Fabien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746084: marked as done (rake-compiler: FTBFS: ERROR: Test ruby2.1 failed: Failure/Error: Rake::Task.should have_defined('compile:universal-known'))
Your message dated Sun, 03 Aug 2014 07:33:39 + with message-id e1xdqiv-0003cx...@franck.debian.org and subject line Bug#746084: fixed in rake-compiler 0.9.2-2 has caused the Debian Bug report #746084, regarding rake-compiler: FTBFS: ERROR: Test ruby2.1 failed: Failure/Error: Rake::Task.should have_defined('compile:universal-known') 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.) -- 746084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rake-compiler Version: 0.9.2-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140426 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): Failure/Error: Rake::Task.should have_defined('compile:universal-known') expected Rake::Task to have defined compile:universal-known # ./spec/lib/rake/extensiontask_spec.rb:454:in `block (5 levels) in top (required)' Finished in 0.2249 seconds 84 examples, 10 failures, 4 pending Failed examples: rspec ./spec/lib/rake/extensiontask_spec.rb:396 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) fake should chain fake task to Makefile generation rspec ./spec/lib/rake/extensiontask_spec.rb:402 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) rbconfig should chain rbconfig tasks to Makefile generation rspec ./spec/lib/rake/extensiontask_spec.rb:406 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) rbconfig should take rbconfig from rake-compiler configuration rspec ./spec/lib/rake/extensiontask_spec.rb:412 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) mkmf should chain mkmf tasks to Makefile generation rspec ./spec/lib/rake/extensiontask_spec.rb:416 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) mkmf should take mkmf from rake-compiler configuration rspec ./spec/lib/rake/extensiontask_spec.rb:423 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) compile:universal-unknown should be defined rspec ./spec/lib/rake/extensiontask_spec.rb:427 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) compile:universal-unknown should depend on 'compile:extension_one:universal-unknown' rspec ./spec/lib/rake/extensiontask_spec.rb:433 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) native:universal-unknown should be defined rspec ./spec/lib/rake/extensiontask_spec.rb:437 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) native:universal-unknown should depend on 'native:my_gem:universal-unknown' rspec ./spec/lib/rake/extensiontask_spec.rb:453 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for multiple platforms) should define task for each supplied platform /usr/bin/ruby2.1 -S rspec ./spec/lib/rake/extensiontask_spec.rb ./spec/lib/rake/javaextensiontask_spec.rb failed ERROR: Test ruby2.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/rake-compiler_0.9.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: rake-compiler Source-Version: 0.9.2-2 We believe that the bug you reported is fixed in the latest version of rake-compiler, 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 746...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Genannt jonas.gena...@capi2name.de (supplier of updated rake-compiler 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
Bug#747723: marked as done (FTBFS: Test ruby2.1 failed. Exiting.)
Your message dated Sun, 03 Aug 2014 07:33:39 + with message-id e1xdqiv-0003cx...@franck.debian.org and subject line Bug#746084: fixed in rake-compiler 0.9.2-2 has caused the Debian Bug report #746084, regarding FTBFS: Test ruby2.1 failed. Exiting. 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.) -- 746084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rake-compiler Version: 0.9.2-1 Severity: serious Justification: fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.0-rm Dear Maintainer, During a rebuild of ruby-related packages your package failed to build with these errors: === rspec ./spec/lib/rake/extensiontask_spec.rb:396 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) fake should chain fake task to Makefile generation rspec ./spec/lib/rake/extensiontask_spec.rb:402 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) rbconfig should chain rbconfig tasks to Makefile generation rspec ./spec/lib/rake/extensiontask_spec.rb:406 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) rbconfig should take rbconfig from rake-compiler configuration rspec ./spec/lib/rake/extensiontask_spec.rb:412 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) mkmf should chain mkmf tasks to Makefile generation rspec ./spec/lib/rake/extensiontask_spec.rb:416 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) mkmf should take mkmf from rake-compiler configuration rspec ./spec/lib/rake/extensiontask_spec.rb:423 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) compile:universal-unknown should be defined rspec ./spec/lib/rake/extensiontask_spec.rb:427 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) compile:universal-unknown should depend on 'compile:extension_one:universal-unknown' rspec ./spec/lib/rake/extensiontask_spec.rb:433 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) native:universal-unknown should be defined rspec ./spec/lib/rake/extensiontask_spec.rb:437 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) native:universal-unknown should depend on 'native:my_gem:universal-unknown' rspec ./spec/lib/rake/extensiontask_spec.rb:453 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for multiple platforms) should define task for each supplied platform /usr/bin/ruby2.1 -S rspec ./spec/lib/rake/extensiontask_spec.rb ./spec/lib/rake/javaextensiontask_spec.rb failed === Please note that the default ruby recently has been switched to 2.1 in sid. If your package doesn't already do this, please switch to the ruby(-all)(-dev) metapackages and `dh_ruby --print-supported` for detecting the ruby to build for. (Also, if everything goes according to plan, this is the last ruby transition for jessie.) About the test rebuild: this build was done in a rather standard sbuild/schroot setup, on an amd64 host where PID1 is provided by systemd, and options passed to sbuild were: DEB_BUILD_OPTIONS=parallel=12 Please find the full build log attached. Thanks, -ch rake-compiler_0.9.2-1_amd64.build Description: inode/symlink ---End Message--- ---BeginMessage--- Source: rake-compiler Source-Version: 0.9.2-2 We believe that the bug you reported is fixed in the latest version of rake-compiler, 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 746...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Genannt jonas.gena...@capi2name.de (supplier of updated rake-compiler 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, 02 Aug 2014 15:33:16 +0200 Source: rake-compiler Binary: rake-compiler
Bug#747723: marked as done (FTBFS: Test ruby2.1 failed. Exiting.)
Your message dated Sun, 03 Aug 2014 07:33:39 + with message-id e1xdqiv-0003d3...@franck.debian.org and subject line Bug#747723: fixed in rake-compiler 0.9.2-2 has caused the Debian Bug report #747723, regarding FTBFS: Test ruby2.1 failed. Exiting. 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.) -- 747723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rake-compiler Version: 0.9.2-1 Severity: serious Justification: fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.0-rm Dear Maintainer, During a rebuild of ruby-related packages your package failed to build with these errors: === rspec ./spec/lib/rake/extensiontask_spec.rb:396 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) fake should chain fake task to Makefile generation rspec ./spec/lib/rake/extensiontask_spec.rb:402 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) rbconfig should chain rbconfig tasks to Makefile generation rspec ./spec/lib/rake/extensiontask_spec.rb:406 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) rbconfig should take rbconfig from rake-compiler configuration rspec ./spec/lib/rake/extensiontask_spec.rb:412 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) mkmf should chain mkmf tasks to Makefile generation rspec ./spec/lib/rake/extensiontask_spec.rb:416 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) mkmf should take mkmf from rake-compiler configuration rspec ./spec/lib/rake/extensiontask_spec.rb:423 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) compile:universal-unknown should be defined rspec ./spec/lib/rake/extensiontask_spec.rb:427 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) compile:universal-unknown should depend on 'compile:extension_one:universal-unknown' rspec ./spec/lib/rake/extensiontask_spec.rb:433 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) native:universal-unknown should be defined rspec ./spec/lib/rake/extensiontask_spec.rb:437 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) native:universal-unknown should depend on 'native:my_gem:universal-unknown' rspec ./spec/lib/rake/extensiontask_spec.rb:453 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for multiple platforms) should define task for each supplied platform /usr/bin/ruby2.1 -S rspec ./spec/lib/rake/extensiontask_spec.rb ./spec/lib/rake/javaextensiontask_spec.rb failed === Please note that the default ruby recently has been switched to 2.1 in sid. If your package doesn't already do this, please switch to the ruby(-all)(-dev) metapackages and `dh_ruby --print-supported` for detecting the ruby to build for. (Also, if everything goes according to plan, this is the last ruby transition for jessie.) About the test rebuild: this build was done in a rather standard sbuild/schroot setup, on an amd64 host where PID1 is provided by systemd, and options passed to sbuild were: DEB_BUILD_OPTIONS=parallel=12 Please find the full build log attached. Thanks, -ch rake-compiler_0.9.2-1_amd64.build Description: inode/symlink ---End Message--- ---BeginMessage--- Source: rake-compiler Source-Version: 0.9.2-2 We believe that the bug you reported is fixed in the latest version of rake-compiler, 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 747...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Genannt jonas.gena...@capi2name.de (supplier of updated rake-compiler 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, 02 Aug 2014 15:33:16 +0200 Source: rake-compiler Binary: rake-compiler
Bug#746084: marked as done (rake-compiler: FTBFS: ERROR: Test ruby2.1 failed: Failure/Error: Rake::Task.should have_defined('compile:universal-known'))
Your message dated Sun, 03 Aug 2014 07:33:39 + with message-id e1xdqiv-0003d3...@franck.debian.org and subject line Bug#747723: fixed in rake-compiler 0.9.2-2 has caused the Debian Bug report #747723, regarding rake-compiler: FTBFS: ERROR: Test ruby2.1 failed: Failure/Error: Rake::Task.should have_defined('compile:universal-known') 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.) -- 747723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rake-compiler Version: 0.9.2-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140426 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): Failure/Error: Rake::Task.should have_defined('compile:universal-known') expected Rake::Task to have defined compile:universal-known # ./spec/lib/rake/extensiontask_spec.rb:454:in `block (5 levels) in top (required)' Finished in 0.2249 seconds 84 examples, 10 failures, 4 pending Failed examples: rspec ./spec/lib/rake/extensiontask_spec.rb:396 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) fake should chain fake task to Makefile generation rspec ./spec/lib/rake/extensiontask_spec.rb:402 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) rbconfig should chain rbconfig tasks to Makefile generation rspec ./spec/lib/rake/extensiontask_spec.rb:406 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) rbconfig should take rbconfig from rake-compiler configuration rspec ./spec/lib/rake/extensiontask_spec.rb:412 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) mkmf should chain mkmf tasks to Makefile generation rspec ./spec/lib/rake/extensiontask_spec.rb:416 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) mkmf should take mkmf from rake-compiler configuration rspec ./spec/lib/rake/extensiontask_spec.rb:423 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) compile:universal-unknown should be defined rspec ./spec/lib/rake/extensiontask_spec.rb:427 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) compile:universal-unknown should depend on 'compile:extension_one:universal-unknown' rspec ./spec/lib/rake/extensiontask_spec.rb:433 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) native:universal-unknown should be defined rspec ./spec/lib/rake/extensiontask_spec.rb:437 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for 'universal-unknown' platform) native:universal-unknown should depend on 'native:my_gem:universal-unknown' rspec ./spec/lib/rake/extensiontask_spec.rb:453 # Rake::ExtensionTask (tasks) (cross platform tasks) (cross for multiple platforms) should define task for each supplied platform /usr/bin/ruby2.1 -S rspec ./spec/lib/rake/extensiontask_spec.rb ./spec/lib/rake/javaextensiontask_spec.rb failed ERROR: Test ruby2.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/rake-compiler_0.9.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: rake-compiler Source-Version: 0.9.2-2 We believe that the bug you reported is fixed in the latest version of rake-compiler, 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 747...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Genannt jonas.gena...@capi2name.de (supplier of updated rake-compiler 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
Bug#755327: gridsite: FTBFS: htcp.c:65:27: error: 'CURLOPT_FILE' undeclared (first use in this function)
Il Domenica 3 Agosto 2014 2:33, Vincent Cheng vch...@debian.org ha scritto: Hi Gianfranco, Hi dear Vincent and Colin since the upload is already in deferred I don't think there is much here rather than finding what breaked your patch. Your proposed debdiff doesn't seem to apply cleanly (did you actually test it?)... Yes, as usual I triple tested it, on my system (old curl), on utopic pbuilder and on sid pbuilder (both new curl) dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building gridsite using existing ./gridsite_2.0.4.orig.tar.gz patching file src/htcp.c Hunk #1 FAILED at 59. 1 out of 1 hunk FAILED dpkg-source: info: fuzz is not allowed when applying patches dpkg-source: info: if patch 'curl-defines.patch' is correctly applied by quilt, use 'quilt refresh' to update it dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/curl-defines.patch/ --reject-file=- gridsite-2.0.4.orig.cAX2KS/debian/patches/curl-defines.patch gave error exit status 1 dpkg-buildpackage: error: dpkg-source -b gridsite-2.0.4 gave error exit status 2 patch -p1 ../debdiff patching file debian/changelog patching file debian/patches/curl-defines.patch patching file debian/patches/series http://mentors.debian.net/package/gridsite I see, the copy-pasted stripped the tab + #define HTCP_GET 1 + #define HTCP_PUT 2 + #define HTCP_DELETE 3 + #define HTCP_GET 1 + #define HTCP_PUT 2 + #define HTCP_DELETE 3 maybe next time I'll send the patch as attachment, to avoid this kind of problems Aside from that, I have to say that I prefer Colin's proposed debdiff rather than yours; testing for older versions of curl rather than just getting rid of legacy code is the right approach and makes it easier to backport this package if desired. I have _nothing_ against Colin's approach (we already discussed it a little on irc). But look at the define ++#if (LIBCURL_VERSION_NUM 0x070907) do you want to really to backport this package to a system with a curl packaged in 2002??? curl (7.9.7-1) unstable; urgency=low Wed, 15 May 2002 21:09:19 +0200 oldstable has already 7.21, so I don't see the point in maintaining such code, moreover because upstream just dropped it completely. So if you want to go with this approach is fine for me, since ubuntu already took the patch. But I still think that having an upstream commit cherry-picked (alrady used by fedora people) can help in maintaining the code https://github.com/CESNET/gridsite/commit/2124d471f9fc1eed4bf5893ed2701350357c01af http://pkgs.fedoraproject.org/cgit/gridsite.git/tree/curl-opts.patch Have a nice day! Just my .02$ Gianfranco Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756895: Ugrade 1.13 - 1.14 fails
Package: tt-rss Version: 1.13+dfsg-1 Severity: grave The database upgrade fails with this message: mysql said: ERROR 1060 (42S21) at line 13: Duplicate column name 'width' -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tt-rss depends on: ii dbconfig-common1.8.47+nmu1 ii debconf [debconf-2.0] 1.5.53 ii init-system-helpers1.20 ii libapache2-mod-php55.6.0~rc2+dfsg-5 ii libjs-dojo-core1.7.2+dfsg-1 ii libjs-dojo-dijit 1.7.2+dfsg-1 ii libjs-scriptaculous1.9.0-2 ii libphp-phpmailer 5.2.8+dfsg-1 ii php-gettext1.0.11-1 ii php5-cli 5.6.0~rc2+dfsg-5 ii php5-json 1.3.5-3 ii php5-mysql 5.6.0~rc2+dfsg-5 ii phpqrcode 1.1.4-1 Versions of packages tt-rss recommends: ii apache2 2.4.10-1 ii apache2-bin [httpd] 2.4.10-1 ii apache2-mpm-prefork [httpd] 2.4.10-1 ii php5-gd 5.6.0~rc2+dfsg-5 ii php5-mcrypt 5.6.0~rc2+dfsg-5 Versions of packages tt-rss suggests: ii mysql-client-5.5 [mysql-client] 5.5.37-1 ii mysql-server 5.5.37-1 ii php5-apcu [php-apc] 4.0.6-1 pn sphinxsearch none -- Configuration Files: /etc/default/tt-rss changed [not included] -- debconf information excluded -- (Not so) Random fortune: Sex *could* kill you. Do you know what the human body goes through when you have sex? Pupils dilate, arteries constrict, core temperature rises, heart races, blood pressure skyrockets, respiration becomes rapid and shallow, the brain fires bursts of electrical impulses from nowhere to nowhere, and secretions spit out of every gland, and the muscles tense and spasm like you're lifting three times your body weight. It's violent. It's ugly. And it's messy. And if God hadn't made it *unbelievably* fun, the human race would have died out eons ago. -- House, M.D. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: jessie
Processing commands for cont...@bugs.debian.org: tags 756492 + sid jessie Bug #756492 [system-config-printer-kde] system-config-printer-kde: Authentication Dialog cannot receive focus Added tag(s) sid and jessie. thanks Stopping processing here. Please contact me if you need assistance. -- 756492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756492 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#699304: libmng: diff for NMU version 1.0.10+dfsg-3.1
tags 699304 + patch tags 699304 + pending tags 745525 + patch tags 745525 + pending thanks Dear maintainer, I've prepared an NMU for libmng (versioned as 1.0.10+dfsg-3.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- tobi Binary files /tmp/gpYxIQ67pL/libmng-1.0.10/contrib/msvc/mngview/sRGB.icm and /tmp/OiF0VWc2ny/libmng-1.0.10+dfsg/contrib/msvc/mngview/sRGB.icm differ diff -Nru libmng-1.0.10/debian/changelog libmng-1.0.10+dfsg/debian/changelog --- libmng-1.0.10/debian/changelog 2011-09-16 17:41:19.0 +0200 +++ libmng-1.0.10+dfsg/debian/changelog 2014-08-03 13:30:49.0 +0200 @@ -1,3 +1,13 @@ +libmng (1.0.10+dfsg-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Buld against lcms2: new patch support-lcms2.patch (Closes: #745525) +The patch cherry-picks the relevant changes from the new upstream version. + * Repack tarball using Exclude-Files in d/copyright to remove non-free +file contrib/msvc/mngview/sRGB.icm (Closes: #699304). + + -- Tobias Frost t...@debian.org Sun, 03 Aug 2014 13:20:17 + + libmng (1.0.10-3) unstable; urgency=low * debian/control: diff -Nru libmng-1.0.10/debian/control libmng-1.0.10+dfsg/debian/control --- libmng-1.0.10/debian/control2011-09-16 18:18:21.0 +0200 +++ libmng-1.0.10+dfsg/debian/control 2014-08-03 13:06:38.0 +0200 @@ -3,7 +3,7 @@ Priority: optional Build-Depends: debhelper (= 8.1.3), libjpeg-dev, - liblcms1-dev, + liblcms2-dev, libtool, zlib1g-dev Maintainer: Kartik Mistry kar...@debian.org @@ -31,7 +31,7 @@ Depends: ${misc:Depends}, libmng1 (= ${binary:Version}), libjpeg-dev, - liblcms1-dev, + liblcms2-dev, zlib1g-dev Description: M-N-G library (Development headers) The libmng library supports decoding, displaying, encoding, and various other diff -Nru libmng-1.0.10/debian/copyright libmng-1.0.10+dfsg/debian/copyright --- libmng-1.0.10/debian/copyright 2011-09-16 17:22:20.0 +0200 +++ libmng-1.0.10+dfsg/debian/copyright 2014-08-03 13:19:56.0 +0200 @@ -1,6 +1,7 @@ -Format: http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?op=filerev=174 +Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: libmng Source: http://www.libmng.com +Files-Excluded: contrib/msvc/mngview/sRGB.icm Files: * Copyright: (C) 2000, Gerard Juyn ger...@libmng.com diff -Nru libmng-1.0.10/debian/patches/series libmng-1.0.10+dfsg/debian/patches/series --- libmng-1.0.10/debian/patches/series 2010-06-12 11:27:40.0 +0200 +++ libmng-1.0.10+dfsg/debian/patches/series2014-08-03 13:01:59.0 +0200 @@ -1,3 +1,4 @@ linux-makefile.diff kfreebsd-build-fix.diff manpage-typo-fixes.diff +support-lcms2.patch diff -Nru libmng-1.0.10/debian/patches/support-lcms2.patch libmng-1.0.10+dfsg/debian/patches/support-lcms2.patch --- libmng-1.0.10/debian/patches/support-lcms2.patch1970-01-01 01:00:00.0 +0100 +++ libmng-1.0.10+dfsg/debian/patches/support-lcms2.patch 2014-08-03 13:25:42.0 +0200 @@ -0,0 +1,189 @@ +Description: Patch to support lcms2 + Cherry-pick lcms2-support from new upstream version 2.0.2 +Author: Tobias Frost t...@debian.org +Forwarded: not-needed +Last-Update: 2014-08-03 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/libmng_cms.c b/libmng_cms.c +@@ -86,6 +86,9 @@ + #pragma option -A /* force ANSI-C */ + #endif + ++#undef HAVE_LIBLCMS1 ++#define HAVE_LIBLCMS2 ++ + /* ** */ + + #ifdef MNG_INCLUDE_DISPLAY_PROCS +@@ -104,7 +107,9 @@ + + void mnglcms_initlibrary () + { ++#ifdef HAVE_LIBLCMS1 + cmsErrorAction (LCMS_ERROR_IGNORE); /* LCMS should ignore errors! */ ++#endif + } + + /* ** */ +@@ -132,14 +137,30 @@ + {0.3000, 0.6000, 1.0}, + {0.1500, 0.0600, 1.0} + }; ++#ifdef HAVE_LIBLCMS1 + LPGAMMATABLEGamma24[3]; ++#elif defined(HAVE_LIBLCMS2) ++ cmsToneCurve* Gamma24[3]; ++#endif + mng_cmsprof hsRGB; + ++#ifdef HAVE_LIBLCMS1 + cmsWhitePointFromTemp(6504, D65); +- Gamma24[0] = Gamma24[1] = Gamma24[2] = cmsBuildGamma(256, 2.4); ++#elif defined(HAVE_LIBLCMS2) ++ cmsWhitePointFromTemp(D65, 6504); ++#endif ++ Gamma24[0] = Gamma24[1] = Gamma24[2] = ++#ifdef HAVE_LIBLCMS1 ++ cmsBuildGamma(256, 2.4); ++#elif defined(HAVE_LIBLCMS2) ++ cmsBuildGamma(NULL, 2.4); ++#endif + hsRGB = cmsCreateRGBProfile(D65, Rec709Primaries, Gamma24); ++#ifdef HAVE_LIBLCMS1 + cmsFreeGamma(Gamma24[0]); +- ++#elif defined(HAVE_LIBLCMS2) ++ cmsFreeToneCurve(Gamma24[0]); ++#endif + return hsRGB; + } + +@@ -368,16 +389,22 @@ +
Bug#756905: python-scipy autopkg test failures, and build failure on mips
Package: python-scipy Version: 0.14.0-1 Severity: serious Tags: sid jessie the package fails to build on mips, but did build before. see https://buildd.debian.org/status/fetch.php?pkg=python-scipyarch=mipsver=0.14.0-1stamp=1406905822 the autopkg tests fail, see http://ci.debian.net/#package/python-scipy please fix these, or disable them. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: libmng: diff for NMU version 1.0.10+dfsg-3.1
Processing commands for cont...@bugs.debian.org: tags 699304 + patch Bug #699304 [src:libmng] libmng: sRGB.icm is non-free Bug #736954 [src:libmng] [src:libmng] Non free file according to dfsg Added tag(s) patch. Added tag(s) patch. tags 699304 + pending Bug #699304 [src:libmng] libmng: sRGB.icm is non-free Bug #736954 [src:libmng] [src:libmng] Non free file according to dfsg Added tag(s) pending. Added tag(s) pending. tags 745525 + patch Bug #745525 [libmng] Please migrate to lcms2 Added tag(s) patch. tags 745525 + pending Bug #745525 [libmng] Please migrate to lcms2 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 699304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699304 736954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736954 745525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745525 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#756907: cinnamon-screensaver: no longer buildable on non-linux
Source: cinnamon-screensaver Version: 2.2.4-4 Severity: serious Justification: FTBFS Hi, your package can no longer be built on non-linux architectures: | cinnamon-screensaver build-depends on missing: | - libsystemd-login-dev as can be seen here: https://buildd.debian.org/status/package.php?p=cinnamon-screensaversuite=sid The outdated binaries on kfreebsd-* are therefore preventing your package from migrating. Hence this pseudo-FTBFS serious bug report. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756908: ergo: FTBFS on mips, mipsel, powerpc, s390x: test suite failures
Source: ergo Version: 3.4.0-1 Severity: serious Justification: FTBFS Hi, everything is in the subject, full summary: https://buildd.debian.org/status/package.php?p=ergosuite=sid Direct links to failing build logs: https://buildd.debian.org/status/fetch.php?pkg=ergoarch=mipsver=3.4.0-1stamp=1406494180 https://buildd.debian.org/status/fetch.php?pkg=ergoarch=mipselver=3.4.0-1stamp=1406450302 https://buildd.debian.org/status/fetch.php?pkg=ergoarch=powerpcver=3.4.0-1stamp=1406399761 https://buildd.debian.org/status/fetch.php?pkg=ergoarch=s390xver=3.4.0-1stamp=1406400721 Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: raise severity of issues blocking removal of gcc-4.8
Processing commands for cont...@bugs.debian.org: severity 751301 serious Bug #751301 [gcc-avr] gcc-avr: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751304 serious Bug #751304 [contextfree] contextfree: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751307 serious Bug #751307 [flexc++] flexc++: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751308 serious Bug #751308 [ccbuild] ccbuild: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751309 serious Bug #751309 [freebsd-glue] freebsd-glue: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751310 serious Bug #751310 [feel++] feel++: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751311 serious Bug #751311 [gcc-arm-none-eabi] gcc-arm-none-eabi: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751314 serious Bug #751314 [higan] higan: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751315 serious Bug #751315 [gpg-remailer] gpg-remailer: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751316 serious Bug #751316 [kfreebsd-10] kfreebsd-10: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751318 serious Bug #751318 [libvpx] libvpx: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751320 serious Bug #751320 [libstdc++-arm-none-eabi] libstdc++-arm-none-eabi: non-standard gcc/g++ used for build Severity set to 'serious' from 'important' severity 751324 serious Bug #751324 [oxref] oxref: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751330 serious Bug #751330 [xd] xd: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751331 serious Bug #751331 [spek] spek: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' severity 751333 serious Bug #751333 [yrmcds] yrmcds: non-standard gcc/g++ used for build (gcc-4.8) Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 751301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751301 751304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751304 751307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751307 751308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751308 751309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751309 751310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751310 751311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751311 751314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751314 751315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751315 751316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751316 751318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751318 751320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751320 751324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751324 751330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751330 751331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751331 751333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751333 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#756909: gnumach: FTBFS on i386
Source: gnumach Version: 2:1.4-7 Severity: serious Justification: FTBFS Hi, your package has been failing to build on i386 all the way up since 2:1.4-7. I'm not sure why from a quick look at the build log though: https://buildd.debian.org/status/logs.php?pkg=gnumacharch=i386 https://buildd.debian.org/status/fetch.php?pkg=gnumacharch=i386ver=2%3A1.4-11stamp=1406332798 Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756910: libapache2-mod-auth-openidc: FTBFS on mips, powerpc, s390x (and sparc): test failure
Source: libapache2-mod-auth-openidc Version: 1.5.3-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on the aforementioned archs due to this test failure: | `/usr/bin/apxs2 -q CC` -DLINUX -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/apr-1.0 -Isrc -o test/test test/*.c src/jose/apr_jwt.c src/jose/apr_jwk.c src/jose/apr_jws.c src/jose/apr_jwe.c -lapr-1 -laprutil-1 -lldap -llber -lssl -lcrypto -ljansson | test/test | Failed: # test_jwt_decryption: error in apr_jwe_decrypt_jwt: result 0 != expected 1 | make[1]: *** [test] Error 1 Build summary with links to full build logs: https://buildd.debian.org/status/package.php?p=libapache2-mod-auth-openidcsuite=sid Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756911: timemon.app: FTBFS on powerpc: undefined reference during linking
Source: timemon.app Version: 4.1-3 Severity: serious Justification: FTBFS Hi, your package no longer builds on powerpc due to undefined reference during linking: | gcc -rdynamic -Wl,-z,relro -Wl,--no-undefined -Wl,--as-needed -pthread -fexceptions -fgnu-runtime -o TimeMon.app/./TimeMon \ | ./obj/TimeMon.obj/loadave.c.o ./obj/TimeMon.obj/NSColorExtensions.m.o ./obj/TimeMon.obj/Percentages.m.o ./obj/TimeMon.obj/TimeMonColors.m.o ./obj/TimeMon.obj/TimeMon_main.m.o ./obj/TimeMon.obj/TimeMonWraps.m.o -L/usr/local/lib -L/usr/lib -lgnustep-gui-lgnustep-base-lobjc -lm | /usr/lib/gcc/powerpc-linux-gnu/4.9/libobjc.so: undefined reference to `rs6000_special_adjust_field_align_p' | collect2: error: ld returned 1 exit status | make[5]: *** [TimeMon.app/./TimeMon] Error 1 | /usr/share/GNUstep/Makefiles/Instance/application.make:131: recipe for target 'TimeMon.app/./TimeMon' failed | make[4]: *** [internal-app-run-compile-submake] Error 2 | /usr/share/GNUstep/Makefiles/Instance/application.make:145: recipe for target 'internal-app-run-compile-submake' failed | make[3]: *** [TimeMon.all.app.variables] Error 2 | /usr/share/GNUstep/Makefiles/Master/rules.make:298: recipe for target 'TimeMon.all.app.variables' failed | make[2]: *** [internal-all] Error 2 | /usr/share/GNUstep/Makefiles/Master/application.make:38: recipe for target 'internal-all' failed | make[2]: Leaving directory '/«PKGBUILDDIR»' | make[1]: *** [override_dh_auto_build] Error 2 | debian/rules:17: recipe for target 'override_dh_auto_build' failed Full build log: https://buildd.debian.org/status/fetch.php?pkg=timemon.apparch=powerpcver=4.1-3stamp=1406330585 Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756911: timemon.app: FTBFS on powerpc: undefined reference during linking
Cyril Brulebois wrote: your package no longer builds on powerpc due to undefined reference during linking: I few days ago I sent a give-back request to powerpc@buildd.d.o (attached). This was due to #756096. ---BeginMessage--- gb timemon.app_4.1-3 . powerpc It failed to build due to a bug in libobjc which has been fixed in gcc-4.9/4.9.1-3.---End Message---
Bug#756914: pulseaudio: FTBFS on kfreebsd-*: portability issue
Source: pulseaudio Version: 5.0-3 Severity: serious Justification: FTBFS Usertags: kfreebsd Hi, your package has been failing to build on kfreebsd-* since 5.0-3, as can be seen here: https://buildd.debian.org/status/logs.php?pkg=pulseaudioarch=kfreebsd-amd64 Build log excerpt: | libtool: link: ranlib .libs/liblo-test-util.a | libtool: link: ( cd .libs rm -f liblo-test-util.la ln -s ../liblo-test-util.la liblo-test-util.la ) | /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../src -I../src/modules -I../src/modules -DPA_ALSA_PATHS_DIR=\\ -DPA_ALSA_PROFILE_SETS_DIR=\\ -D_FORTIFY_SOURCE=2 -DFASTPATH -pthread -DPA_SRCDIR=\/«PKGBUILDDIR»/src\ -DPA_BUILDDIR=\/«PKGBUILDDIR»/src\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -W -Wextra -pipe -Wno-long-long -Wno-overlength-strings -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -fno-common -fdiagnostics-show-option -c -o utils/libpulsedsp_la-padsp.lo `test -f 'utils/padsp.c' || echo './'`utils/padsp.c | libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../src -I../src/modules -I../src/modules -DPA_ALSA_PATHS_DIR=\\ -DPA_ALSA_PROFILE_SETS_DIR=\\ -D_FORTIFY_SOURCE=2 -DFASTPATH -pthread -DPA_SRCDIR=\/«PKGBUILDDIR»/src\ -DPA_BUILDDIR=\/«PKGBUILDDIR»/src\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -W -Wextra -pipe -Wno-long-long -Wno-overlength-strings -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -fno-common -fdiagnostics-show-option -c utils/padsp.c -fPIC -DPIC -o utils/.libs/libpulsedsp_la-padsp.o | In file included from utils/padsp.c:45:0: | utils/padsp.c: In function 'open': | utils/padsp.c:1522:33: warning: 'short unsigned int' is promoted to 'int' when passed through '...' | mode = va_arg(args, mode_t); | ^ | utils/padsp.c:1522:33: note: (so you should pass 'int' not 'short unsigned int' to 'va_arg') | utils/padsp.c:1522:33: note: if this code is reached, the program will abort | utils/padsp.c: In function 'open64': | utils/padsp.c:2561:33: warning: 'short unsigned int' is promoted to 'int' when passed through '...' | mode = va_arg(args, mode_t); | ^ | utils/padsp.c:2561:33: note: if this code is reached, the program will abort | /bin/bash ../libtool --tag=CC --mode=link gcc -std=gnu99 -pthread -DPA_SRCDIR=\/«PKGBUILDDIR»/src\ -DPA_BUILDDIR=\/«PKGBUILDDIR»/src\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -W -Wextra -pipe -Wno-long-long -Wno-overlength-strings -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -fno-common -fdiagnostics-show-option -Wl,-z,nodelete-avoid-version -disable-static -Wl,-z,relro -Wl,--no-as-needed -o libpulsedsp.la -rpath /usr/lib/x86_64-kfreebsd-gnu/pulseaudio utils/libpulsedsp_la-padsp.lo libpulse.la libpulsecommon-5.0.la -lpthread -lrt -ldl -lm | libtool: link: gcc -std=gnu99 -shared -fPIC -DPIC utils/.libs/libpulsedsp_la-padsp.o -Wl,-rpath -Wl,/«PKGBUILDDIR»/src/.libs -Wl,-rpath -Wl,/usr/lib/x86_64-kfreebsd-gnu/pulseaudio ./.libs/libpulse.so ./.libs/libpulsecommon-5.0.so -lpthread -lrt -ldl -lm -pthread -O2 -Wl,-z -Wl,nodelete -Wl,-z -Wl,relro -Wl,--no-as-needed -pthread -Wl,-soname -Wl,libpulsedsp.so -o .libs/libpulsedsp.so | libtool: link: ( cd .libs rm -f libpulsedsp.la ln -s ../libpulsedsp.la libpulsedsp.la ) | gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../src -I../src/modules -I../src/modules -DPA_ALSA_PATHS_DIR=\\ -DPA_ALSA_PROFILE_SETS_DIR=\\ -D_FORTIFY_SOURCE=2 -DFASTPATH -pthread -DPA_SRCDIR=\/«PKGBUILDDIR»/src\ -DPA_BUILDDIR=\/«PKGBUILDDIR»/src\ -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-kfreebsd-gnu/dbus-1.0/include -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -W -Wextra -pipe -Wno-long-long
Bug#756916: vice: FTBFS on kfreebsd-amd64: error while opening src/arch/win32/res.rc.po.c for reading: No such file or directory
Source: vice Version: 2.4.dfsg+2.4.7-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on kfreebsd-amd64: | Making all in po | make[2]: Entering directory '/«BUILDDIR»/vice-2.4.dfsg+2.4.7/po' | gcc -I.. -I../intl -g -O3 -Wall -Wno-inline ./intl2po.c -o intl2po | ( if test 'x.' != 'x.'; then \ | posrcprefix='../'; \ | else \ | posrcprefix=../; \ | fi; \ | rm -f POTFILES-t POTFILES \ | (sed -e '/^#/d' -e '/^[]*$/d' \ | -e s@.*@ $posrcprefix @ ./POTFILES.in \ | | sed -e '$s/\\$//') POTFILES-t \ | chmod a-w POTFILES-t \ | mv POTFILES-t POTFILES ) | PATH=../src:$PATH /usr/bin/xgettext --default-domain=vice --directory=.. --directory=.. \ | --add-comments --keyword=_ --keyword=N_ \ | --files-from=./POTFILES.in \ | -o ./vice.pot | /usr/bin/xgettext: error while opening src/arch/win32/res.rc.po.c for reading: No such file or directory | make[2]: *** [vice.pot] Error 1 Full build log: https://buildd.debian.org/status/fetch.php?pkg=vicearch=kfreebsd-amd64ver=2.4.dfsg%2B2.4.7-1stamp=1406758769 Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756915: libcgroup: error in upstream license version
Source: libcgroup Version: 0.41-4 Severity: serious Justification: Policy 12.5 debian/copyright states that the upstream license is LGPL-2.1+, when in fact it is LGPL-2.1. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755330: marked as done (metamonger: FTBFS: Tests failures)
Your message dated Sun, 03 Aug 2014 13:04:24 + with message-id e1xdvsa-8a...@franck.debian.org and subject line Bug#755330: fixed in metamonger 0.20131228-3 has caused the Debian Bug report #755330, regarding metamonger: FTBFS: Tests failures 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.) -- 755330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: metamonger Version: 0.20131228-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140718 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'inc', 'blib/lib', 'blib/arch') t/000-setup-env.t t/009-save-noact.t t/010-save-data.t t/015-touch-files.t t/020-diff-data.t t/025-restore-noact.t t/030-touch-files.t t/050-restore-data.t t/055-diff-data.t t/060-touch-files.t t/070-untracked-all.t t/099-tear-env.t t/100-config.t t/101-config-.metamonger.t t/150-metamongerignore.t t/151-metamongerignore.t t/152-filetype.t t/200-no-dereference.t t/500-fix-84ee7f6b65.t t/000-setup-env.t ... ok Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: lib /«PKGBUILDDIR»/inc /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at ./metamonger line 13. BEGIN failed--compilation aborted at ./metamonger line 13. # Failed test at t/009-save-noact.t line 16. # Failed test at t/009-save-noact.t line 17. # Looks like you failed 2 tests of 2. t/009-save-noact.t .. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/2 subtests Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: /«PKGBUILDDIR»/inc /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at t/010-save-data.t line 6. BEGIN failed--compilation aborted at t/010-save-data.t line 6. t/010-save-data.t ... Dubious, test returned 2 (wstat 512, 0x200) No subtests run t/015-touch-files.t . ok Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: lib /«PKGBUILDDIR»/inc /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at ./metamonger line 13. BEGIN failed--compilation aborted at ./metamonger line 13. # Failed test at t/020-diff-data.t line 15. # Looks like you failed 1 test of 1. t/020-diff-data.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: lib /«PKGBUILDDIR»/inc /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at ./metamonger line 13. BEGIN failed--compilation aborted at ./metamonger line 13. # Failed test at t/025-restore-noact.t line 20. # Looks like you failed 1 test of 1. t/025-restore-noact.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests t/030-touch-files.t . ok Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: /«PKGBUILDDIR»/inc /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at t/050-restore-data.t line 6. BEGIN failed--compilation aborted at t/050-restore-data.t line 6. t/050-restore-data.t Dubious, test returned 2 (wstat 512, 0x200) No subtests run Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: lib /«PKGBUILDDIR»/inc /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18
Bug#756911: timemon.app: FTBFS on powerpc: undefined reference during linking
Yavor Doganov ya...@gnu.org (2014-08-03): Cyril Brulebois wrote: your package no longer builds on powerpc due to undefined reference during linking: I few days ago I sent a give-back request to powerpc@buildd.d.o (attached). This was due to #756096. OK, thanks; given back. I'll let you close this bug report once the build is confirmed successful if you don't mind? FWIW when no action is required on the buildd administration side, requesting such things through debian-wb-t...@lists.debian.org means someone else can perform the give back. Mraw, KiBi. signature.asc Description: Digital signature
Bug#755330: marked as done (metamonger: FTBFS: Tests failures)
Your message dated Sun, 03 Aug 2014 13:19:23 + with message-id e1xdvh5-00059z...@franck.debian.org and subject line Bug#755330: fixed in metamonger 0.20131228-4 has caused the Debian Bug report #755330, regarding metamonger: FTBFS: Tests failures 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.) -- 755330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: metamonger Version: 0.20131228-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140718 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'inc', 'blib/lib', 'blib/arch') t/000-setup-env.t t/009-save-noact.t t/010-save-data.t t/015-touch-files.t t/020-diff-data.t t/025-restore-noact.t t/030-touch-files.t t/050-restore-data.t t/055-diff-data.t t/060-touch-files.t t/070-untracked-all.t t/099-tear-env.t t/100-config.t t/101-config-.metamonger.t t/150-metamongerignore.t t/151-metamongerignore.t t/152-filetype.t t/200-no-dereference.t t/500-fix-84ee7f6b65.t t/000-setup-env.t ... ok Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: lib /«PKGBUILDDIR»/inc /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at ./metamonger line 13. BEGIN failed--compilation aborted at ./metamonger line 13. # Failed test at t/009-save-noact.t line 16. # Failed test at t/009-save-noact.t line 17. # Looks like you failed 2 tests of 2. t/009-save-noact.t .. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/2 subtests Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: /«PKGBUILDDIR»/inc /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at t/010-save-data.t line 6. BEGIN failed--compilation aborted at t/010-save-data.t line 6. t/010-save-data.t ... Dubious, test returned 2 (wstat 512, 0x200) No subtests run t/015-touch-files.t . ok Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: lib /«PKGBUILDDIR»/inc /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at ./metamonger line 13. BEGIN failed--compilation aborted at ./metamonger line 13. # Failed test at t/020-diff-data.t line 15. # Looks like you failed 1 test of 1. t/020-diff-data.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: lib /«PKGBUILDDIR»/inc /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at ./metamonger line 13. BEGIN failed--compilation aborted at ./metamonger line 13. # Failed test at t/025-restore-noact.t line 20. # Looks like you failed 1 test of 1. t/025-restore-noact.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests t/030-touch-files.t . ok Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: /«PKGBUILDDIR»/inc /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at t/050-restore-data.t line 6. BEGIN failed--compilation aborted at t/050-restore-data.t line 6. t/050-restore-data.t Dubious, test returned 2 (wstat 512, 0x200) No subtests run Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: lib /«PKGBUILDDIR»/inc /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18
Bug#747506: libsikuli-script-java
Control: reassign -1 libsikuli-script-java seeing #752738, this might be an issue with an incomplete java library path in sikuli. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: libsikuli-script-java
Processing control commands: reassign -1 libsikuli-script-java Bug #747506 [src:openjdk-6] openjdk-6: cannot load libsikuli-script-java any more Bug reassigned from package 'src:openjdk-6' to 'libsikuli-script-java'. No longer marked as found in versions openjdk-6/6b31-1.13.3-1~deb7u1. Ignoring request to alter fixed versions of bug #747506 to the same values previously set -- 747506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747506 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#756911: marked as done (timemon.app: FTBFS on powerpc: undefined reference during linking)
Your message dated Sun, 3 Aug 2014 15:37:53 +0200 with message-id 20140803133753.gd9...@mraw.org and subject line Re: Bug#756911: timemon.app: FTBFS on powerpc: undefined reference during linking has caused the Debian Bug report #756911, regarding timemon.app: FTBFS on powerpc: undefined reference during linking 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.) -- 756911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: timemon.app Version: 4.1-3 Severity: serious Justification: FTBFS Hi, your package no longer builds on powerpc due to undefined reference during linking: | gcc -rdynamic -Wl,-z,relro -Wl,--no-undefined -Wl,--as-needed -pthread -fexceptions -fgnu-runtime -o TimeMon.app/./TimeMon \ | ./obj/TimeMon.obj/loadave.c.o ./obj/TimeMon.obj/NSColorExtensions.m.o ./obj/TimeMon.obj/Percentages.m.o ./obj/TimeMon.obj/TimeMonColors.m.o ./obj/TimeMon.obj/TimeMon_main.m.o ./obj/TimeMon.obj/TimeMonWraps.m.o -L/usr/local/lib -L/usr/lib -lgnustep-gui-lgnustep-base-lobjc -lm | /usr/lib/gcc/powerpc-linux-gnu/4.9/libobjc.so: undefined reference to `rs6000_special_adjust_field_align_p' | collect2: error: ld returned 1 exit status | make[5]: *** [TimeMon.app/./TimeMon] Error 1 | /usr/share/GNUstep/Makefiles/Instance/application.make:131: recipe for target 'TimeMon.app/./TimeMon' failed | make[4]: *** [internal-app-run-compile-submake] Error 2 | /usr/share/GNUstep/Makefiles/Instance/application.make:145: recipe for target 'internal-app-run-compile-submake' failed | make[3]: *** [TimeMon.all.app.variables] Error 2 | /usr/share/GNUstep/Makefiles/Master/rules.make:298: recipe for target 'TimeMon.all.app.variables' failed | make[2]: *** [internal-all] Error 2 | /usr/share/GNUstep/Makefiles/Master/application.make:38: recipe for target 'internal-all' failed | make[2]: Leaving directory '/«PKGBUILDDIR»' | make[1]: *** [override_dh_auto_build] Error 2 | debian/rules:17: recipe for target 'override_dh_auto_build' failed Full build log: https://buildd.debian.org/status/fetch.php?pkg=timemon.apparch=powerpcver=4.1-3stamp=1406330585 Mraw, KiBi. ---End Message--- ---BeginMessage--- Cyril Brulebois k...@debian.org (2014-08-03): I'll let you close this bug report once the build is confirmed successful if you don't mind? That was quick, closing. Mraw, KiBi. signature.asc Description: Digital signature ---End Message---
Bug#747637: akonadi-server: upgrade to akonadi-12-1-1 does not work so kmail too
Hello, Last days i was blocked by akonadi-12-1-1 and kmail out of service. I tried to modify the schematic layout of the base Akonadi Mysql to correct the error that akonadi-server meeting as indicates it the message of Markus Meier, not being a specialist Mysql, I looked on Google and found which to have FOREIGN KEY in Mysql it was necessary that the concerned table have an engine InnoDB, I converted a table Myisam in InnoDB, but the same error occurs farther on another table, then I converted all the tables Myisam in InnoDB, unfortunately an error occurs farther and i did not find solution.I then decided as advised me somebody to protect the base(basis) akonadi and to delete it, with the re-creation of the akonadi base I was able to found the use of Kmail. All the modifications introduced by akonadi-server 12-1-1 are optimizations at the level of the plan of the base(basis), I think that a specialist Mysql should deal with the modifications to be brought to allow a transition of 11- 12 which is made without error. Best Regards. Philippe Merlin
Bug#756895: Ugrade 1.13 - 1.14 fails
The subject says 1.13 - 1.14, but 1.14 isn't in Debian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751314: marked as done (higan: non-standard gcc/g++ used for build (gcc-4.8))
Your message dated Sun, 03 Aug 2014 15:50:13 + with message-id e1xdy33-0007xq...@franck.debian.org and subject line Bug#751314: fixed in higan 094-5 has caused the Debian Bug report #751314, regarding higan: non-standard gcc/g++ used for build (gcc-4.8) 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.) -- 751314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: higan Version: 094-4 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-4.7, gcc-4.7-legacy This package builds with a non standard compiler version; please check if this package can be built with the default version of gcc/g++, or with gcc-4.9/g++-4.9. Please drop build dependencies of the form libstdc++6-4.7-dev, these are not needed and fulfilled by build-essential. Please keep this report open until the package uses the default compiler version (or gcc-4.9) for the package build. The severity of this report is likely to be raised before the release, so that the gcc-4.7 package can be removed for the release. ---End Message--- ---BeginMessage--- Source: higan Source-Version: 094-5 We believe that the bug you reported is fixed in the latest version of higan, 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 751...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Hansen than...@debian.org (supplier of updated higan 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, 03 Aug 2014 16:57:25 +0200 Source: higan Binary: higan bsnes Architecture: source amd64 all Version: 094-5 Distribution: sid Urgency: medium Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Tobias Hansen than...@debian.org Description: bsnes - transitional dummy package higan - Accurate Nintendo multi-system emulator Closes: 751314 Changes: higan (094-5) unstable; urgency=medium . * Use standard gcc instead of gcc-4.8. (Closes: #751314) Checksums-Sha1: 8cdaf96dfa55291a94b3676667397f8ee897d834 2027 higan_094-5.dsc 292045d9ff8f9c5312fbb30bf752b8a9288c70be 529188 higan_094-5.debian.tar.xz a2be2502d46f2c2c4d97da0bb51c9e97490f585d 1928270 higan_094-5_amd64.deb f4f7aee62608efc53a5858eda557d228bf667232 6980 bsnes_094-5_all.deb Checksums-Sha256: 81bcd3a4c698ec5fe893d9f41b1d9a2ec247355216f4c552cabce23c622cff76 2027 higan_094-5.dsc 00cc27a33734390b9f4a61a0608a7a794a341e398ba6818fca9b8dea9cb76971 529188 higan_094-5.debian.tar.xz ade11feaef1230bccfb18d2d567928acdf4b1accae04880c2d85e3ed8e0d6b57 1928270 higan_094-5_amd64.deb 963f4a0af0ac3b5326410c18c2030efc90c0fc6fdec84bb05fa4be5676264622 6980 bsnes_094-5_all.deb Files: 1a295544892dcd99e3ec283e3580dd6a 1928270 otherosfs optional higan_094-5_amd64.deb 56fcae8ec64f9eb69a8867be9de6273e 6980 oldlibs optional bsnes_094-5_all.deb 664a346d0c631b7d9eb57a84b9d78572 2027 otherosfs optional higan_094-5.dsc 3c5df47b25b9230d6ded8339e01b89f6 529188 otherosfs optional higan_094-5.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT3lNxAAoJEIyCFp2Ozs0q7ZMP/0XIQ+8qD8W6eMeq0D7rxMCP lDM/q0NSVvoyp9xVKFgQ6V0K8O3ELLwZ9Q15eSEi4bi7Zj1mahw5cYKMnlAeZSY3 P2fGhu1jUoB3TTwrqxWKiN1T5BUhuIiYJq56C6Wk/uXvwCJtYEYugNCHz8RXvuJq yb8RHnfrtMcmv4AYlDtiSZZZsc4GQDm1UUZi6YR29wZzLDxB8Hk1s0lZPXkrKDQ+ Kq1hsqciKkXyi4TAzBd3QFOx5Q4LfYgJqaiGQAhWIyt21eH1ws0P1gubJLWJEkiZ iRS9zv+rN0Izsr0QoK0dPg8IEQVIyZKvQFGxoDkEIpqbKpqdcd48IT6zjdsrMiAb QeSmtjTvb2Kmu6+hA9M4Z0oztJAvOZVSbcWj75IQNg+UTnEO6ftbj/qkxsiSh2UE gxHwc/Vx4ZMFFJGzCP2LvWBoh+ChreHFC+j9hBLnPP3ase/5vCswSwGLyusXGWbh RKg0+y0hQH+W88LJPV2vT42xvRYtCPaYsK0WWltMLIzfbTG/y39xAocXxnLUoNP7 GAHbhsYRDmf1WP12CHdcDZW4L9Oa7UoNAvATpnuN7on8jM8SGaltfZHXwKNvw3w8 plolLO5Ybc57EiNTHaz12624XUcRkuK+ec512ST0p8jxZ18zWus4mDF31T6KFjgB xnDxJvPz8U47Tfs0aegF =79FK -END PGP SIGNATUREEnd Message---
Bug#745530: Please migrate to lcms2
Package: cegui-mk2 Followup-For: Bug #745530 Dear Maintainer, While triaging lcms-related bugs I saw that cegui-mk2 does not actually use lcms: If built in a pdebuilder environment with and without lcms entered as B-D the binary result byte-identical. Same also when additionally dropping libmng-dev, which would also pull in lcms. Therefore I assume that it is safe to drop B-D on liblcms and libmng. I will schedule an NMU later. -- tobi -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739308: libzip-dev: Include file in wrong place
On 08/03/2014 12:59 AM, Simon McVittie wrote: It doesn't force you to think about the include path (in a way, part of the point of it is to *not* have to think about the include path), but it does force you to declare which API version you're trying to use (indirectly, by your choice of .pc file). You got me wrong. What I meant is that you need a little more work than just including the headers files in your source code, but you also have to make sure the headers are actually loadable. This mainly avoids works-for-me code since pkg-config, provided it's properly configured, will find the proper paths for the header files on every target platform. If you are an uploading DD and you actively use libzip, I would prefer you to do an NMU based on my suggested patch: it seems you know how to test it, and I don't really. I found this bug on the RC-bug list, and I have no particular interest in libzip myself. I am an uploading DD and I will take care of the package. Again, thanks for your input and help. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745530: cegui-mk2: diff for NMU version 0.7.6-3.3
tags 745530 + patch tags 745530 + pending thanks Dear maintainer, I've prepared an NMU for cegui-mk2 (versioned as 0.7.6-3.3) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru cegui-mk2-0.7.6/debian/changelog cegui-mk2-0.7.6/debian/changelog --- cegui-mk2-0.7.6/debian/changelog2014-03-04 04:54:44.0 +0100 +++ cegui-mk2-0.7.6/debian/changelog2014-08-03 19:09:44.0 +0200 @@ -1,3 +1,11 @@ +cegui-mk2 (0.7.6-3.3) unstable; urgency=medium + + * Non-maintainer upload. + * Remove unneeded depdendency on liblcms-dev (Closes: #745530) and libmng-dev +which would also pull-in lcms. + + -- Tobias Frost t...@debian.org Sun, 03 Aug 2014 19:09:41 +0200 + cegui-mk2 (0.7.6-3.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru cegui-mk2-0.7.6/debian/control cegui-mk2-0.7.6/debian/control --- cegui-mk2-0.7.6/debian/control 2014-03-04 04:52:53.0 +0100 +++ cegui-mk2-0.7.6/debian/control 2014-08-03 19:13:44.0 +0200 @@ -4,13 +4,14 @@ Maintainer: Muammar El Khatib muam...@debian.org Build-Depends: debhelper (= 6), cdbs, libtool, automake1.11, autoconf, pkg-config, libxerces-c-dev, libboost-signals-dev, - libboost-regex-dev, libfreetype6-dev, liblcms1-dev, + libboost-regex-dev, libfreetype6-dev, libtiff-dev, libgl1-mesa-dev, libglu1-mesa-dev, libdevil-dev, libpcre3-dev, liblua5.1-dev, lua5.1, libois-dev [linux-any], libfreeimage-dev, libxcursor-dev, libxpm-dev, python-dev, - libpng-dev, libmng-dev, libxxf86vm-dev, libexpat1-dev, - liblua5.1-expat-dev, libxml2-dev, libsilly-dev, libogre-1.8-dev, - libglew1.6-dev, libtinyxml-dev, libtolua++5.1-dev (= 1.0.93) + libpng-dev, libxxf86vm-dev, + libexpat1-dev, liblua5.1-expat-dev, libxml2-dev, libsilly-dev, + libogre-1.8-dev, libglew1.6-dev, libtinyxml-dev, + libtolua++5.1-dev (= 1.0.93) Standards-Version: 3.9.4 Homepage: http://www.cegui.org.uk/ @@ -52,8 +53,8 @@ Suggests: libcegui-mk2-0.7.6-doc Depends: ${misc:Depends}, libcegui-mk2-0.7.6 (= ${binary:Version}), libdevil-dev, libxerces-c3.1, libpng12-dev | libpng-dev, - libtiff5-dev | libtiff-dev, libjpeg-dev, libmng-dev, - zlib1g-dev | libz-dev, libfreetype6-dev, liblua5.1-dev, liblcms1-dev, + libtiff5-dev | libtiff-dev, libjpeg-dev, + zlib1g-dev | libz-dev, libfreetype6-dev, liblua5.1-dev, libpcre3-dev, libfreeimage-dev Description: Crazy Eddie's GUI (development files) CEGUI is a free library providing windowing and widgets for graphics -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: cegui-mk2: diff for NMU version 0.7.6-3.3
Processing commands for cont...@bugs.debian.org: tags 745530 + patch Bug #745530 [src:cegui-mk2] Please migrate to lcms2 Added tag(s) patch. tags 745530 + pending Bug #745530 [src:cegui-mk2] Please migrate to lcms2 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 745530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745530 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#751330: marked as done (xd: non-standard gcc/g++ used for build (gcc-4.8))
Your message dated Sun, 03 Aug 2014 17:20:02 + with message-id e1xdzry-00042q...@franck.debian.org and subject line Bug#751330: fixed in xd 3.22.09-2 has caused the Debian Bug report #751330, regarding xd: non-standard gcc/g++ used for build (gcc-4.8) 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.) -- 751330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xd Version: 3.22.09-1 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-4.7, gcc-4.7-legacy This package builds with a non standard compiler version; please check if this package can be built with the default version of gcc/g++, or with gcc-4.9/g++-4.9. Please drop build dependencies of the form libstdc++6-4.7-dev, these are not needed and fulfilled by build-essential. Please keep this report open until the package uses the default compiler version (or gcc-4.9) for the package build. The severity of this report is likely to be raised before the release, so that the gcc-4.7 package can be removed for the release. ---End Message--- ---BeginMessage--- Source: xd Source-Version: 3.22.09-2 We believe that the bug you reported is fixed in the latest version of xd, 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 751...@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 xd 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, 03 Aug 2014 10:02:35 -0700 Source: xd Binary: xd Architecture: source amd64 Version: 3.22.09-2 Distribution: unstable Urgency: medium Maintainer: Frank B. Brokken f.b.brok...@rug.nl Changed-By: tony mancill tmanc...@debian.org Description: xd - smart directory change utility Closes: 751330 Changes: xd (3.22.09-2) unstable; urgency=medium . * Drop build-dep on g++-4.8. (Closes: #751330) * Update VCS URLs to use canonical form. Checksums-Sha1: 5fb3b0fdf78da8085246d47c0e75c964f176ae92 1923 xd_3.22.09-2.dsc ea4c8a41c9f58795cf1b46eabed52aded7813cdd 4824 xd_3.22.09-2.debian.tar.xz c20da3d216ee1a985477417aea5b50437c3e9af8 51392 xd_3.22.09-2_amd64.deb Checksums-Sha256: c8420b814c5297255237fb9c445d3e685f6b8f9f3dfd704eaebe14ffebf2eecf 1923 xd_3.22.09-2.dsc f36fcb7a616537ae22ab3d6f18a0989ae63197132d4982301c5269a42252a240 4824 xd_3.22.09-2.debian.tar.xz 4d6f67e5bc2916b15dcfd285ae1a7f47cba0e5d0a70b62e6eef25516cdf05b49 51392 xd_3.22.09-2_amd64.deb Files: deec032e9f07b6854c3754a744b699f3 51392 utils optional xd_3.22.09-2_amd64.deb 5c054dda0c8045f21f92d9cb38eababb 1923 utils optional xd_3.22.09-2.dsc a77ccaa2e6abd68268d3122e309dea54 4824 utils optional xd_3.22.09-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJT3muZAAoJECHSBYmXSz6WIQ4QAMy31NckYJPO+YZMw3qyJyWv kH/hBlxcOUDQCF9044BdtNp1KgfIwAIU/yMQNDefT608z886XUxh1NbHAFl2R+Mu ucTT4CYM+R4NTmuXiY5Eq0o6kEr2mg7EKXHPCsjqmURrLbW1NbYFRxzHZ05zo9hh YcCj13XtSEhOgWjm8kG+2037XBTfuoydMb+YOgUQANWSujibMNXyhFBclJp1y/sn 4PK4XFEo7RhWehou023IPjiphYxL9SUPsUyWsS3KQqO5NxM0jQXWtn/OnXuRYQih 7rWGeiPk0tPQ45lm5E2XrzLqY5hjIF0GKGbZOO5qS2iCxf2XMfjfXz3y9rlyBcrd 380970gZqH8L4ZdpH/k0zOpiq4fq1c795PmK361km73SUJd3NDYgswKjkpWc2Ug5 B+bJLZOYqArD0LWGGXvHJe8Gyhvbipp/gJn2wzJ8/CYDpf1T05QeBn/FEzN5VBXw b2BboB7x/gOgFOqay2hXMJ+M7fTjDol0YkICzvRJVvgQu/DX3BGhQcWmcazm7p+p NY6pldBUnvR260HUoHHuCFNLzW77QeUI1NmQ9+og883Vv7w/9HXgWf3VkGZZA5Vt OqKWLW5EMCLKpajpObqeH84JkqOgWRfrygRZD5XcF3rvDDFL2VtohyyjTeJIUR5m SwTtVZTjr2whx6dnEeq0 =eZX2 -END PGP SIGNATUREEnd Message---
Bug#751324: marked as done (oxref: non-standard gcc/g++ used for build (gcc-4.8))
Your message dated Sun, 03 Aug 2014 17:19:13 + with message-id e1xdzrb-0003ug...@franck.debian.org and subject line Bug#751324: fixed in oxref 1.00.01-2 has caused the Debian Bug report #751324, regarding oxref: non-standard gcc/g++ used for build (gcc-4.8) 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.) -- 751324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: oxref Version: 1.00.01-1 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-4.7, gcc-4.7-legacy This package builds with a non standard compiler version; please check if this package can be built with the default version of gcc/g++, or with gcc-4.9/g++-4.9. Please drop build dependencies of the form libstdc++6-4.7-dev, these are not needed and fulfilled by build-essential. Please keep this report open until the package uses the default compiler version (or gcc-4.9) for the package build. The severity of this report is likely to be raised before the release, so that the gcc-4.7 package can be removed for the release. ---End Message--- ---BeginMessage--- Source: oxref Source-Version: 1.00.01-2 We believe that the bug you reported is fixed in the latest version of oxref, 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 751...@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 oxref 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, 03 Aug 2014 09:56:06 -0700 Source: oxref Binary: oxref Architecture: source amd64 Version: 1.00.01-2 Distribution: unstable Urgency: medium Maintainer: Frank B. Brokken f.b.brok...@rug.nl Changed-By: tony mancill tmanc...@debian.org Description: oxref - cross reference utility Closes: 751324 Changes: oxref (1.00.01-2) unstable; urgency=medium . * Remove explicit depndency on g++-4.8. (Closes: #751324) * Update Vcs- URLs to canonical forms. Checksums-Sha1: 6535a521380d47151c0fb88490ca09aa0ab8ac75 1954 oxref_1.00.01-2.dsc 9f4d8cdc3fbbe1fb94728f25795d5e27b37cfa7e 3516 oxref_1.00.01-2.debian.tar.xz 55ca9ff68b2c8cb1ef816da5a7e28a6fc7d260c6 27092 oxref_1.00.01-2_amd64.deb Checksums-Sha256: 4d9ddf6a826028b5d5848f1c394f9e7bb20f7a8685c0d379fe9abf6c5026ff38 1954 oxref_1.00.01-2.dsc 1cbe0c304629df046195e4d56a35fff6b43b424a04c8ab9fa2f27d8c7c091c7a 3516 oxref_1.00.01-2.debian.tar.xz 5fe4396d11181393714100aa5f9ce28475b3a632b8618f35fc3a2019d12c2187 27092 oxref_1.00.01-2_amd64.deb Files: 6e736835a3e7115c7c300a4eaf34d951 27092 utils optional oxref_1.00.01-2_amd64.deb 85e3ab3dc0adda36d7961febb8d671dc 1954 utils optional oxref_1.00.01-2.dsc 803fe70a7aaf30a871631dcb2b894f67 3516 utils optional oxref_1.00.01-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJT3msfAAoJECHSBYmXSz6W0nkP/2MiVAT5uCVMsCr9g8AORN1A PgYGNHebsb3CYDmnm2M0g2fl6omj+j5kt12uxUlEmZjAUk7IaDzL7DGmAcw9CnEf UTn9Yxc5YkIhuqnjgPUBTAfRxAwBOaI5e+ht8pWufQCNS8o3bfwveiWQ/kdWR96m RfTLOmaIxj4W8MDoErLMbYkCN964q1Wwyyv5I8MgOzfsksFOdpKPq/w8jJrNUykZ O58oalCTKWep7wErH3f+XczRKgg7jrxJckvmAqq40v8prk+yhug61I/XF3VyIxBD W+zd0IUw8lM+sd9zSA3BR0M/ki+oNWemQUSZLwmTl79/pi9CqTXpJWRQhV46kNsq WuImz5PIhsEJPWfUHrFGcFyCx1Vf+Y0rGXlYOJrlNFvugGM/AtADB6Lm/XewZAFA DBTgY27C7oV8mDvs+LhmZJjVA9SUDl8G0r2d+qPEA4vwFBid9knToUD2ftHqt9mH uW3zmlljvhtzDZs+gCXJ8hliO0Ymn0I4Drtyhk6NidawKfNIpfqtSk3/Io7DoNGc R6MU3e4JOQQYFkg360DCHKSW2UBEHVGbO5Cdk1bdQFk7cOD+rxxuLpQLdJtCLnvm bUaM4FusvF1X1rushvoa93XO3Z6d7julNe196Kj/YPrr3+irGG/UuholK5mzgtTr C3rT1SJKhGryRNkf4E6l =G3Fo -END PGP SIGNATUREEnd Message---
Bug#751315: marked as done (gpg-remailer: non-standard gcc/g++ used for build (gcc-4.8))
Your message dated Sun, 03 Aug 2014 17:18:45 + with message-id e1xdzqj-0003if...@franck.debian.org and subject line Bug#751315: fixed in gpg-remailer 3.00.02-2 has caused the Debian Bug report #751315, regarding gpg-remailer: non-standard gcc/g++ used for build (gcc-4.8) 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.) -- 751315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gpg-remailer Version: 3.00.02-1 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-4.7, gcc-4.7-legacy This package builds with a non standard compiler version; please check if this package can be built with the default version of gcc/g++, or with gcc-4.9/g++-4.9. Please drop build dependencies of the form libstdc++6-4.7-dev, these are not needed and fulfilled by build-essential. Please keep this report open until the package uses the default compiler version (or gcc-4.9) for the package build. The severity of this report is likely to be raised before the release, so that the gcc-4.7 package can be removed for the release. ---End Message--- ---BeginMessage--- Source: gpg-remailer Source-Version: 3.00.02-2 We believe that the bug you reported is fixed in the latest version of gpg-remailer, 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 751...@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 gpg-remailer 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, 03 Aug 2014 10:07:33 -0700 Source: gpg-remailer Binary: gpg-remailer Architecture: source amd64 Version: 3.00.02-2 Distribution: unstable Urgency: medium Maintainer: Frank B. Brokken f.b.brok...@rug.nl Changed-By: tony mancill tmanc...@debian.org Description: gpg-remailer - Forwards re-encrypted PGP/GPG mail to a group Closes: 751315 Changes: gpg-remailer (3.00.02-2) unstable; urgency=medium . * Drop versioned g++ build-dep. (Closes: #751315) Checksums-Sha1: 54874fb54a902ceb65e203e25863c78457eda926 2037 gpg-remailer_3.00.02-2.dsc 08ce38a68920b2e9b7c7eace1f81fb6fa00a9cbd 3640 gpg-remailer_3.00.02-2.debian.tar.xz b6764979b5895f2cbfc4a793b513f7d52c0ef5fe 60318 gpg-remailer_3.00.02-2_amd64.deb Checksums-Sha256: e48622f8b96cfca1be7ebf6baf3429f1ee0fa4c3b4b0726663b3b99e76b2a85b 2037 gpg-remailer_3.00.02-2.dsc 52eca435dddf86908c74d7642673c87f883fdbecee078033344a1cf08c375664 3640 gpg-remailer_3.00.02-2.debian.tar.xz 15d602d140047e9e53c8936b5d21eecb49d4002ba214f0cf9def2ad95fccf41c 60318 gpg-remailer_3.00.02-2_amd64.deb Files: 655db74ad63c09851ca2768de9b6b603 60318 devel optional gpg-remailer_3.00.02-2_amd64.deb 122376ad3cccb5f035f560f6e2116865 2037 devel optional gpg-remailer_3.00.02-2.dsc fe3d292b22f9112a923e794f5adfa21d 3640 devel optional gpg-remailer_3.00.02-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJT3m1xAAoJECHSBYmXSz6W8ioP/0BufOHvBalqbZebAXuke7/G tfB+Pk4TeMD2wleUeoF8iY05QcufuJ7tOqaVv+Txtmt5jgUjBbMKJC8RLjn3MkgG lJRfIWI/AIEmhgm5EZqwcwUelR/lkOum3NhXMulKoAGGLmzr+ZjC28AXdThENIN4 bKgAaygqK61kvfpt60bwJb+ckL742tlhUuioQ/UalkpiOF9s5rHys2MCR7QMxmoR jHx6ktUDd1sjN+V4QDLz7v1uWJjUOWRqzY0jV5uRAWHjoFCmxN58GjN3EKSTkyBl x7MFeeybbdaf7bD//K1mIxM9IvlBSAwQNvPUKJZsVCl/clwhc+L3N0c1iQzk+6Dh WrcAfIb9Uwnmq56wfeUsOAia4BX9UuYBYvSTfernF3ITTZs13s1YBTVvxWa3g3Tn 4l9xtV1ciw/hVeC3M3PDrE7KOck/jy2XarM7OD+XsXLeiiageqQcylzHpsry4U/f vIWF0ck6KkVigJdUp1fjozUJGrngp/GzM+LtXCV+Wd3NK/DIGEMKjHQ3d/vyWvvH oycXAX3SPFvYTQZ7UNujOYwVo1dADSWbupbP74kPDfYBzJ+g6njZqwhZFApH5//P mOePOuWed5KZoHP4hdB+HwTmJxD3KlO/+S4C0DWzCUCTO7smCQ4OE08XK+DtrTKx gzcAsTnRbugJy07v6RFz =tVLH -END PGP SIGNATUREEnd Message---
Bug#753121: [Pkg-libvirt-maintainers] Bug#753121: libvirt: diff for NMU version 1.2.4-3.1
Hi Colin, On Tue, Jul 22, 2014 at 10:09:49AM +0200, Guido Günther wrote: On Tue, Jul 22, 2014 at 08:11:00AM +0100, Colin Watson wrote: On Wed, Jul 16, 2014 at 08:23:59AM +0200, Guido Günther wrote: On Mon, Jul 14, 2014 at 04:05:07PM +0100, Colin Watson wrote: Since this is blocking the parted transition I'm working on, I've prepared an NMU for libvirt (versioned as 1.2.4-3.1) based on Peter's patch in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753121#38, and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. That's perfectly fine. I've already patched this in git but didn't get around to do an upload yet. Thanks a lot for your help and for following standard procedure for NMUs. Would you mind if I did a follow-up NMU to fix #710195? I know you've already fixed it in git, but I'm going to need to get kfreebsd-* building to unblock parted, and I think it would be a good idea to avoid tangling this with a new upstream version of libvirt if we don't have to. Sure. Go ahead and thanks for your work on this! Are you done with your parted transition? Seems 3.1-4 entered testing? Just wanted to be sure I'm not going to screw your work with libvirt 1.2.7. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751307: marked as done (flexc++: non-standard gcc/g++ used for build (gcc-4.8))
Your message dated Sun, 03 Aug 2014 17:33:41 + with message-id e1xdzfb-0005aa...@franck.debian.org and subject line Bug#751307: fixed in flexc++ 2.01.00-2 has caused the Debian Bug report #751307, regarding flexc++: non-standard gcc/g++ used for build (gcc-4.8) 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.) -- 751307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: flexc++ Version: 2.01.00-1 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-4.7, gcc-4.7-legacy This package builds with a non standard compiler version; please check if this package can be built with the default version of gcc/g++, or with gcc-4.9/g++-4.9. Please drop build dependencies of the form libstdc++6-4.7-dev, these are not needed and fulfilled by build-essential. Please keep this report open until the package uses the default compiler version (or gcc-4.9) for the package build. The severity of this report is likely to be raised before the release, so that the gcc-4.7 package can be removed for the release. ---End Message--- ---BeginMessage--- Source: flexc++ Source-Version: 2.01.00-2 We believe that the bug you reported is fixed in the latest version of flexc++, 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 751...@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 flexc++ 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, 03 Aug 2014 10:08:44 -0700 Source: flexc++ Binary: flexc++ Architecture: source amd64 Version: 2.01.00-2 Distribution: unstable Urgency: medium Maintainer: Frank B. Brokken f.b.brok...@rug.nl Changed-By: tony mancill tmanc...@debian.org Description: flexc++- Flex-style scanner generator for C++ Closes: 751307 Changes: flexc++ (2.01.00-2) unstable; urgency=medium . * Drop explicit versioned g++ build-dep. (Closes: #751307) * Drop hardening-* build-deps. Checksums-Sha1: b6be808ebadeda85f2e24586cd27366190ce2355 1983 flexc++_2.01.00-2.dsc 0e6362664c0f05cff7bf8420f7ee9c6ae914c861 5308 flexc++_2.01.00-2.debian.tar.xz 547a7069b0f898351609d7602c5607b9addfb2c6 622788 flexc++_2.01.00-2_amd64.deb Checksums-Sha256: 2b2edb8d370da72ba5f88267bd902d2f2c72f7ce427ea1436681a312aad4a79e 1983 flexc++_2.01.00-2.dsc db0062e0a88873b8db8cadd982406b14e46228cbaa012f9a1dcfddd6d245a489 5308 flexc++_2.01.00-2.debian.tar.xz 8539b356118bcf278ca9af6b1fc29a012f54a182514ecd2a715090d1988c5209 622788 flexc++_2.01.00-2_amd64.deb Files: fb7950a9811d177c298a7f5fc565cc9a 622788 devel optional flexc++_2.01.00-2_amd64.deb 90081e5d349ea15faf0d14c1adfd9587 1983 devel optional flexc++_2.01.00-2.dsc 8def5d5030a16b699b636cea6681a52b 5308 devel optional flexc++_2.01.00-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJT3m5qAAoJECHSBYmXSz6WWkIP/3Q2P0KJpcMp3CfkaazVCR8T pHjQxn11O8DEZYbKs62l14RtFiRwH4+nCAaYqGfqDy9XioCL3bPQ3LWhXqvWJNa2 LNGiPVM2gLvLpWaXXKJzJxZaSbRZ5OlS4/U75GXX/GA3QRV8xl6ONBUUG+MS57Bk /Ov/gZf/6PrN0urLHS50u2MhWF2GBlmf+1qwT1AxFes5GA584IAwKbbrwLUR2Qih /AMu/DJEbLtK2wwb63bwSxmtHDWVBrpN3HoT11C3pRh2huLcXomBUUvxQhfyk/bm gim+qcOlL0wrWixiTmE2xOYCju0mm1jfZIqLwNiXWpJmiHxYV8jr5l9+IvmEyktu GetRXBDU+shmHeBb1T4AzgHhxhwYWo7OxdxQM+3/vjZciQsBTmMEIq+oU1EYeBWK pCinYkhZa4pekVdP91vqHHvNEtWL8YxbKpY15j92loSWZtm/2+5fic1FPX3p8onV 0tJMJ26fHBkBwEJPDvLlVuXkWNx1k7uOkOS7OT2FV3RITD/FYg5BTVVAb/CcxTQR G+aPboRbT1PYQxQwpfCB1B0kiRg9Ol45C00B17jK0wCmtU6y4wbSGMoPDZc/qdE9 bxawZ8ZvzfiMuIoARW4TmM/oD5gzNcQVfCdXMRNkiLBeb5hz/7hle1nKFrn9YTjy MRtYyg80NXwxYKPLV+AI =7YjA -END PGP SIGNATUREEnd Message---
Processed: tagging 741726
Processing commands for cont...@bugs.debian.org: tags 741726 + moreinfo Bug #741726 [src:grub2] grub: generated grub.cfg leads to non booting system. Drops to rescue shell after not finding root device. Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 741726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741726 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#756737: lintian4python: uninstallable: Depends: lintian ( 2.5.23~) but 2.5.25 is to be installed
Control: tags -1 - help * Jakub Wilk jw...@debian.org, 2014-08-01, 10:28: $ lintian4py lintian4python_0.28.1_all.deb internal error: There are missing nodes on the resolver: coll-index at /usr/bin/lintian line 1140. Apparently it means: there's no collection named “index”. From the Lintian changelog: | * checks/*.desc: | + [NT] Replaced index with unpacked in Needs-Info. I suppose we have to do the same in lintian4python. -- Jakub Wilk -- 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#756737: lintian4python: uninstallable: Depends: lintian ( 2.5.23~) but 2.5.25 is to be installed
Processing control commands: tags -1 - help Bug #756737 [lintian4python] lintian4python: uninstallable: Depends: lintian ( 2.5.23~) but 2.5.25 is to be installed Removed tag(s) help. -- 756737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756737 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: limit source to lintian4python, tagging 756737
Processing commands for cont...@bugs.debian.org: limit source lintian4python Limiting to bugs with field 'source' containing at least one of 'lintian4python' Limit currently set to 'source':'lintian4python' tags 756737 + pending Bug #756737 [lintian4python] lintian4python: uninstallable: Depends: lintian ( 2.5.23~) but 2.5.25 is to be installed Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 756737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756737 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#754698: marked as done (libr3: FTBFS on powerpc: test suite failures)
Your message dated Sun, 03 Aug 2014 17:48:38 + with message-id e1xdzte-0007ah...@franck.debian.org and subject line Bug#754698: fixed in libr3 1.3.1-3 has caused the Debian Bug report #754698, regarding libr3: FTBFS on powerpc: test suite failures 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.) -- 754698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libr3 Version: 1.3.1-2 Severity: serious Justification: FTBFS Hi, your package no longer builds on powerpc due to test suite failures: | | Testsuite summary for r3 1.0.0 | | # TOTAL: 4 | # PASS: 3 | # SKIP: 0 | # XFAIL: 0 | # FAIL: 1 | # XPASS: 0 | # ERROR: 0 | | See tests/test-suite.log | Full build log: https://buildd.debian.org/status/fetch.php?pkg=libr3arch=powerpcver=1.3.1-2stamp=1404647676 It would be nice to have the log printed when failures happen… Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: libr3 Source-Version: 1.3.1-3 We believe that the bug you reported is fixed in the latest version of libr3, 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 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. ChangZhuo Chen (陳昌倬) czc...@gmail.com (supplier of updated libr3 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, 04 Aug 2014 01:32:19 +0800 Source: libr3 Binary: libr3-dev libr3-0 libr3-dbg Architecture: source amd64 Version: 1.3.1-3 Distribution: unstable Urgency: medium Maintainer: ChangZhuo Chen (陳昌倬) czc...@gmail.com Changed-By: ChangZhuo Chen (陳昌倬) czc...@gmail.com Description: libr3-0- High-performance URL router library libr3-dbg - High-performance URL router library (debug symbols) libr3-dev - High-performance URL router library (development files) Closes: 754698 Changes: libr3 (1.3.1-3) unstable; urgency=medium . * Fix pcre_exec's return type. Thanks to Kan-Ru Chen (陳侃如) (Closes: #754698) Checksums-Sha1: cc0cf56d24ff152bc37b8615e7c2d14b6651001d 1957 libr3_1.3.1-3.dsc e6553d47b54949a6f0021f1ff946164c36ea2123 4460 libr3_1.3.1-3.debian.tar.xz 4e0377479612bf2194488630558e8b2a7219169e 11224 libr3-dev_1.3.1-3_amd64.deb d9cb6dcc4a14827b89a55f3a0d89016cc8680462 19096 libr3-0_1.3.1-3_amd64.deb bfb4831011e8df208c03099abe3b1b634631d45b 26856 libr3-dbg_1.3.1-3_amd64.deb Checksums-Sha256: 50f27aaf061e1fd6f0e9dece7fc3f9f712205970f58f4a03601ec4bbbd404156 1957 libr3_1.3.1-3.dsc 703b87ece43b5ea3300454b21d57acc94f912a5a2cb6fd3aa6733926b40b4e49 4460 libr3_1.3.1-3.debian.tar.xz 19e90245618aab909477074f3e24bb8e9e8b095cadc4dace90df0b95d2b185ea 11224 libr3-dev_1.3.1-3_amd64.deb 8803e70929134633f87ef44856dccf4894eb8a844783fd662fcd28bdea9ad51d 19096 libr3-0_1.3.1-3_amd64.deb 766995ed051db56744cc8aaad02cb05137ad52585ffde6af825c7580162f8ac3 26856 libr3-dbg_1.3.1-3_amd64.deb Files: 30f3d8ed6d96cdae9a5871be5cb02d61 11224 libdevel optional libr3-dev_1.3.1-3_amd64.deb 3d63a18e6f64e21594f188c47da788e5 19096 libs optional libr3-0_1.3.1-3_amd64.deb 040d97e8ad638244344f307e0b42eba3 26856 debug extra libr3-dbg_1.3.1-3_amd64.deb 059334c6c69d682f47870e28ce508f7e 1957 libs optional libr3_1.3.1-3.dsc cf9f49fb16276860bf7f1c843bffca9b 4460 libs optional libr3_1.3.1-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJT3nJ8AAoJEJ46tXcoXGhlH6QP/0vX+RyWVTow26xB7H/9pgDX M1m1wIK/WTQpXX0F5DRSoB+s1IKC0hDkbfUFckYN2b0LEjj3ZozJQOxHO939PWcd NPkHCwnKZgdDN/oWtDCD2zR0ba7N30jq+YttIqfFkRcdLdfaDDuo0olFyhmBvJvQ +QNUxtxrnvm19sZjXAmT3bYpt7IJq5hKCggLJwhyvjM6HP8c6e3ZmSCTMw++mnwP pQBeyV1EBydGWhcSpzfhqosoiltwhlzP06A2asy0ilSqKm35xncy2YN7p6ivpssw mrhxH2GYrs62PEBLfq93L1Ix6Wd1v9oCZ68lSn8mjFnRXpTXJg6o/lz/csdTYrtB MkO/EZ0vMItVrXpsHbK7OgTws+ewRebRmFMqfdEDWBlmflDKaOnJe0Beaw6952xl fISk1Xpe9FVNS5H5xf/9IAv0/3N1gCetqULlKenC/Q5U7Cj2gAB8U09VNqwf5bn+
Processed: severity of 756819 is grave
Processing commands for cont...@bugs.debian.org: severity 756819 grave Bug #756819 [virtualbox-guest-additions-iso] no support for xorg-xserver 1.16 Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 756819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756819 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#681913: marked as done (lcms: Depend on unversioned libtiff-dev instead of libtiff4-dev)
Your message dated Sun, 03 Aug 2014 20:30:17 +0200 with message-id 1407090617.17849.1.ca...@edoras.loewenhoehle.ip and subject line has caused the Debian Bug report #681913, regarding lcms: Depend on unversioned libtiff-dev instead of libtiff4-dev 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.) -- 681913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lcms Version: 1.19.dfsg-1.1 Severity: minor Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu quantal ubuntu-patch Dear Maintainer, It makes it easier for libtiff transitions, like the upcoming libtiff5 one, if the unversioned virtual libtiff-dev is used instead of libtiff4-dev. Thanks for considering the patch. -- System Information: Debian Release: wheezy/sid APT prefers quantal-updates APT policy: (500, 'quantal-updates'), (500, 'quantal-security'), (500, 'quantal') Architecture: i386 (i686) Kernel: Linux 3.5.0-4-generic (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -u lcms-1.19.dfsg/debian/control lcms-1.19.dfsg/debian/control --- lcms-1.19.dfsg/debian/control +++ lcms-1.19.dfsg/debian/control @@ -1,7 +1,7 @@ Section: libs Priority: optional Maintainer: Oleksandr Moskalenko ma...@debian.org -Build-Depends: debhelper ( 8.1.3), libtiff4-dev, libjpeg-dev, zlib1g-dev, python-all-dev (= 2.3.5-11), swig +Build-Depends: debhelper ( 8.1.3), libtiff-dev, libjpeg-dev, zlib1g-dev, python-all-dev (= 2.3.5-11), swig Standards-Version: 3.9.2 Vcs-Svn: svn://svn.debian.org/svn/collab-maint/deb-maint/lcms/trunk/ Vcs-Browser: http://svn.debian.org/wsvn/collab-maint/deb-maint/lcms/trunk/?op=log ---End Message--- ---BeginMessage--- Control: fixed -1 1.19.dfsg1-1.4 Thanks The changelog says this bug has been fixed. (verified also in d/control) -- tobi---End Message---
Bug#736018: marked as done (please build-depend on libtiff-dev, not libtiff4-dev)
Your message dated Sun, 03 Aug 2014 20:30:17 +0200 with message-id 1407090617.17849.1.ca...@edoras.loewenhoehle.ip and subject line has caused the Debian Bug report #681913, regarding please build-depend on libtiff-dev, not libtiff4-dev 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.) -- 681913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: lcms Version: 1.19.dfsg-1.2 User: q...@debian.org Usertags: libtiff4-dev The libtiff4-dev package is a transitional package that is going to disappear soon. Please update your build dependency from libtiff4-dev to libtiff-dev. ---End Message--- ---BeginMessage--- Control: fixed -1 1.19.dfsg1-1.4 Thanks The changelog says this bug has been fixed. (verified also in d/control) -- tobi---End Message---
Bug#756819: no support for xorg-xserver 1.16
I can confirm that https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_4.3.15-95180.iso is working with the latest xorg packages from testing. I suggest to upload a fixed virtualbox-guest-additions-iso package with the break and to remove it from testing. It is useless at this point. the alternative can be to package this fixed version (taken from the bug report) https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_4.3.15-95180.iso and upload again. I think is better a development iso instead of a completely broken one, specially for testing. Just my .02$ Gianfranco Agreed. I have bumped this back up to grave. It is absolutely a release critical bug and, as Gianfranco said, the current package is completely useless. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756737: marked as done (lintian4python: uninstallable: Depends: lintian ( 2.5.23~) but 2.5.25 is to be installed)
Your message dated Sun, 03 Aug 2014 18:48:40 + with message-id e1xe0pk-00064t...@franck.debian.org and subject line Bug#756737: fixed in lintian4python 0.28.2 has caused the Debian Bug report #756737, regarding lintian4python: uninstallable: Depends: lintian ( 2.5.23~) but 2.5.25 is to be installed 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.) -- 756737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lintian4python Version: 0.28.2 Severity: serious Tags: help lintian4python is not installable: The following packages have unmet dependencies: lintian4python : Depends: lintian ( 2.5.23~) but 2.5.25 is to be installed E: Unable to correct problems, you have held broken packages. Unfortunately, just bumping the dependency is not sufficient: $ lintian4py lintian4python_0.28.1_all.deb internal error: There are missing nodes on the resolver: coll-index at /usr/bin/lintian line 1140. I saw errors like this in the past, and I even used to know how to fix them, but I forgot. :-( -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: lintian4python Source-Version: 0.28.2 We believe that the bug you reported is fixed in the latest version of lintian4python, 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 756...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jakub Wilk jw...@debian.org (supplier of updated lintian4python 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, 03 Aug 2014 20:22:40 +0200 Source: lintian4python Binary: lintian4python Architecture: source all Version: 0.28.2 Distribution: experimental Urgency: low Maintainer: Jakub Wilk jw...@debian.org Changed-By: Jakub Wilk jw...@debian.org Description: lintian4python - Debian package checker (for Python packages) Closes: 756737 Changes: lintian4python (0.28.2) experimental; urgency=low . * checks/python/*.desc: + Replace “index” with “unpacked” in Needs-Info. . * data/python*-projects: + Update. . * debian/control: + Update lintian (build-)dependency to support Lintian 2.5.25 (closes: #756737). Thanks to Paul R. Tagliamonte for the bug report. Checksums-Sha1: cbf30933e85a3ded58bff05efa14daf53299b01b 1886 lintian4python_0.28.2.dsc 570a9544419bdf796370a4c3a3c7a5914348dc39 80224 lintian4python_0.28.2.tar.xz dbc3f1e15cd4d6a0ad3d8ba8f25679673d3188dc 59016 lintian4python_0.28.2_all.deb Checksums-Sha256: 85394c7bf9d1f5315caf82963bdd8b7efbf9969e39a193c8c6e8e99c7aae52a0 1886 lintian4python_0.28.2.dsc df8bd5b6a6def5afab7a87a52dbcada9fcd29243958e9d26ae8ab3bf15a483ab 80224 lintian4python_0.28.2.tar.xz bed2eefa2c225f8119225d3fbc40e27b15935ac321496e654c1e511964d0c6f7 59016 lintian4python_0.28.2_all.deb Files: cff3e6594f089fd9fa08c561f776ad43 59016 devel extra lintian4python_0.28.2_all.deb 2bdc5682a0f9255ec1235b1e60f8f355 1886 devel extra lintian4python_0.28.2.dsc 188f200848c3e80ff05ff43078d6c459 80224 devel extra lintian4python_0.28.2.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT3oC+AAoJEC1Os6YBVHX120wQAL2xIjWQIi1wYSQ5t0wnZ7Sv VQklvMHP+xHd8B0B0h5mhynaCBZK+LBjLI+bXg4umMlOZXdpoK3OKUiuaV0+sY84 Wrxie/49wGEMDVKwPaaQJibJ4Vxzie+wFZSpFq5Cbp3LfKPEzHEtjq2vapp1f2zh SFTQtmATVHhjh+S48Z6SOjxMutLFvjUztqw5w6J/4p/k8eMDp9lfpi9jFF5j+wWG xFiVyH2DTIZNyrMRD9FaEbUUkhfHmUVg/mizNUoyiavzDtmLcwys1bSNB1gHz7Jr XW10O49VHubG3gySanUAMte2uKL522SMNDB+y5w3zhzyIL7CQp+Oz2bTKOtPg/BI iq4q2SDsaucR4Btw9/8aU9m8iucI88gJOdO+YPyriNbrcTOMPIOesaznx02u8YyT 2PMSyhdnFX5KUjK/BI2+zS+tHN8KAnJB738niL7hop1iTx8P644nxYGcpN1Vy+T2 aFblalDSSHUXxIPRSiaDzzeSHSSdsBKVHZi1yiBLOU5mUPHNz0sHvD0GepLsz2az kDVwZX5lqmoNB+Me+IBSwdsMurFP1Bl5WaPqxcBlhObjDY8jXmEzbrwC7pPqIj1h DiP3yMK7RZ4IcRsenJ20KVlO8q0BBthgbLRYXD1JJQZVpjj/al4kSlSgC+PD7ANL /EiH+6LHgIPQU/pEog8Y =jd30 -END PGP SIGNATUREEnd Message---
Processed: Re: Bug#756819: no support for xorg-xserver 1.16
Processing control commands: severity -1 important Bug #756819 [virtualbox-guest-additions-iso] no support for xorg-xserver 1.16 Severity set to 'important' from 'grave' -- 756819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756819 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#756819: no support for xorg-xserver 1.16
Control: severity -1 important On 03.08.2014 20:16, Caitlin Matos wrote: I can confirm that https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_4.3.15-95180.iso is working with the latest xorg packages from testing. I suggest to upload a fixed virtualbox-guest-additions-iso package with the break and to remove it from testing. It is useless at this point. the alternative can be to package this fixed version (taken from the bug report) https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_4.3.15-95180.iso and upload again. I think is better a development iso instead of a completely broken one, specially for testing. Just my .02$ Gianfranco Agreed. virtualbox-guest-additions-iso provides an iso image with guest additions installers for all kinds of operating systems. How is it completely broken when it doesn't work on the development version of one of them? As I said for Debian guests there exists the virtualbox-guest-x11 package as Debian-native way to install guest additions. I have bumped this back up to grave. It is absolutely a release critical bug and, as Gianfranco said, the current package is completely useless. Can we please not play the severity game? kthx Besides, since you are using Windows as the host you are not even using this package. The iso is something you have on the host and pass through to the guest. Felix -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756941: gnome-shell: Gnome-Shell 3.13-1 hangs at GDM
Package: gnome-shell Version: 3.13.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installed then rebooted-Desktop hangs just before GDM login screen. * What exactly did you do (or not do) that was effective (or ineffective)? Tried to reinstall again. * What was the outcome of this action? Hang just before GDM login. * What outcome did you expect instead? Login screen I looked at the logs see that Gnome-session should be updated also. I have downgraded to 3.12 to use the desktop am waiting to see session before trying 3.13 again. -- System Information: Debian Release: jessie/sid APT prefers experimental APT policy: (900, 'experimental'), (900, 'unstable'), (850, 'testing'), (500, 'testing-updates'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-rc6-amd64 (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 Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii evolution-data-server3.12.2-1 ii gconf-gsettings-backend [gsettings-backend] 3.2.6-2 ii gir1.2-accountsservice-1.0 0.6.37-3 ii gir1.2-atspi-2.0 2.12.0-2 ii gir1.2-caribou-1.0 0.4.13-1 ii gir1.2-clutter-1.0 1.18.2-2 ii gir1.2-freedesktop 1.40.0-2 ii gir1.2-gcr-3 3.12.2-1 ii gir1.2-gdesktopenums-3.0 3.13.2-1 ii gir1.2-gdm3 3.12.2-3 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.40.0-2 ii gir1.2-gmenu-3.0 3.10.1-1 ii gir1.2-gnomebluetooth-1.03.12.0-5 ii gir1.2-gnomedesktop-3.0 3.12.2-2 ii gir1.2-gtk-3.0 3.12.2-1+b1 ii gir1.2-ibus-1.0 1.5.7-2 ii gir1.2-mutter-3.03.13.1-1 ii gir1.2-networkmanager-1.00.9.10.0-1 ii gir1.2-nmgtk-1.0 0.9.10.0-2 ii gir1.2-pango-1.0 1.36.3-1 ii gir1.2-polkit-1.00.112-2 ii gir1.2-soup-2.4 2.46.0-2 ii gir1.2-telepathyglib-0.120.24.0-1 ii gir1.2-telepathylogger-0.2 0.8.0-3 ii gir1.2-upowerglib-1.00.99.0-3 ii gjs 1.40.1-2 ii gnome-icon-theme-symbolic3.12.0-1 ii gnome-settings-daemon3.12.2-1 ii gnome-shell-common 3.13.1-1 ii gnome-themes-standard3.12.0-1 ii gsettings-desktop-schemas3.13.2-1 ii libatk-bridge2.0-0 2.12.1-1+b1 ii libatk1.0-0 2.12.0-1 ii libc62.19-7 ii libcairo21.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libclutter-1.0-0 1.18.2-2 ii libcogl-pango20 1.18.2-1 ii libcogl201.18.2-1 ii libcroco30.6.8-2 ii libdbus-glib-1-2 0.102-1 ii libecal-1.2-16 3.12.2-1 ii libedataserver-1.2-183.12.2-1 ii libgcr-base-3-1 3.12.2-1 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libgirepository-1.0-11.40.0-2 ii libgjs0e [libgjs0-libmozjs-24-0] 1.40.1-2 ii libglib2.0-0 2.41.1-2 ii libgstreamer1.0-01.4.0-1 ii libgtk-3-0 3.12.2-1+b1 ii libical1 1.0-1 ii libjson-glib-1.0-0 1.0.2-1 ii libmozjs-24-024.2.0-2 ii libmutter0d 3.13.1-1 ii libnm-glib4 0.9.10.0-1 ii libnm-util2 0.9.10.0-1 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libpolkit-agent-1-0 0.112-2 ii libpolkit-gobject-1-00.112-2 ii libpulse-mainloop-glib0 5.0-4 ii libpulse05.0-4 ii libsecret-1-00.18-1 ii
Bug#754244: guncat: FTBFS: tput: No value for $TERM and no -T specified
Hello Aaron, Thank you for looking into the cause of the error and filing the bug report, and please excuse the delay in responding. I will take a look. Cheers, tony signature.asc Description: OpenPGP digital signature
Bug#754244: marked as done (guncat: FTBFS: tput: No value for $TERM and no -T specified)
Your message dated Sun, 03 Aug 2014 19:33:30 + with message-id e1xe1x8-00048a...@franck.debian.org and subject line Bug#754244: fixed in guncat 0.92.00-2 has caused the Debian Bug report #754244, regarding guncat: FTBFS: tput: No value for $TERM and no -T specified 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.) -- 754244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: guncat Version: 0.92.00-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of guncat in minimal environments (as on the autobuilders) have been failing: ./build program touch version.cc gcc -E VERSION.h | grep -v '#' | sed 's/\//g' release.yo icmbuild program tput clear tput: No value for $TERM and no -T specified system - failure of system call (status 512) system - failure of system call (status 512) system - failure of system call (status 256) make: *** [build-stamp] Error 1 The problem appears to be that icmconf defines CLS, enabling a dubious (at the very least, overly brittle) feature of icmbuild. Could you please take a look? Thanks! ---End Message--- ---BeginMessage--- Source: guncat Source-Version: 0.92.00-2 We believe that the bug you reported is fixed in the latest version of guncat, 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 754...@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 guncat 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, 03 Aug 2014 12:18:29 -0700 Source: guncat Binary: guncat Architecture: source amd64 Version: 0.92.00-2 Distribution: unstable Urgency: medium Maintainer: Frank B. Brokken f.b.brok...@rug.nl Changed-By: tony mancill tmanc...@debian.org Description: guncat - Catenates files while decrypting PGP-encrypted sections Closes: 754244 Changes: guncat (0.92.00-2) unstable; urgency=medium . * Remove versioned build dependency on g++. * Drop build dependency on hardening-* packages. * Disable definition of CLS in icmconf. (Closes: #754244) Checksums-Sha1: c08ceef66b135525fcb9f65367f14610b1ead7f0 1966 guncat_0.92.00-2.dsc efa1f37ebbe18a3d53c391b4940487b2e3a4a3e2 3648 guncat_0.92.00-2.debian.tar.xz 011954c48d9a97356faecec6407a7fc0fac228cb 21550 guncat_0.92.00-2_amd64.deb Checksums-Sha256: 18c0a06ab6f61cbaf2976d6930c602e25e0deb707fd2005273f055d6b2c26366 1966 guncat_0.92.00-2.dsc e7e198a3d3a8a8fcfdcbc5249f7463437ef87f1df6b06c653aae7a6d880e2628 3648 guncat_0.92.00-2.debian.tar.xz eda4eaa6bdde0f4d151704fcbeabb281d8fc1b5c9c568130b3ae11d412ce1ff6 21550 guncat_0.92.00-2_amd64.deb Files: 424e5862ca9f462dc9ea30d0708d1e05 21550 devel optional guncat_0.92.00-2_amd64.deb ccf2471da77635ba6448edd406c4f75e 1966 devel optional guncat_0.92.00-2.dsc 1641e6ed246ab39142347fddfca60c8b 3648 devel optional guncat_0.92.00-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJT3outAAoJECHSBYmXSz6WIVcP/2kma1zNrEkgwJqRbTWXBBbW A13GF9Q8FUN4A1zQ72pQIbQhZvANnn79PwvIgmLo93rhs6juHS1z6B/3hwfrJ06H i1CW4kIOrxdKokrg7DIc9iC9a7eNJ1nxAk8PrMXWFO+y25P33gHtFd+4GfShqKF0 y0Pg8E5RYz6W5dp8gtaPzZLJAfuNdm62GBlGanPXog4PgMxAjbwA4dcIOiBvxNVa 6f/Dlt0NNKUq4pzqO9RoIudF1CcfehowtywCfHZPYHeuSgSotXXBpRfwkracj0AW pRXPLlPwGs6gqnN4rVJKrThXjkKQ0LmWdJKK+iKSITMphebuE9InIxi5NAHu1NIN G7L8H/jYWV585+zUx5XwN7Yr8iM4eFMu7Ta5AgEmZHTgdKLHLbqFSL9wk8gDO8cN BteEOELXszPV/MPVsBcuZw+3gIqUpNcGB+D159YjS4OrL2quDE+BQJQoAguddQnv iC7S8XOYmHYQlfFgfLmx6I39SuW5YyWQIFLUYMrc+TDbv6u5RcdiVw3Ap3GzxJy4 bIL/lWcjP8eS0nG9MhVBN/HvdPccXuy9LyG34HI9yHLFdd93wH3hqGbu9B7khLGk S7MaeLJxHSKVpsloR23GMLP59Dt/cAHcRZf6GOdFOg20bJg6UMITRaTxDIbsUzPP uDBVnad4vNAM+OzrdHR0 =SCRT -END PGP SIGNATUREEnd Message---
Bug#756903: systemd: Boot hangs if filesystems unavailable
Control: -1 important Am 03.08.2014 12:21, schrieb Tony Green: Since my machine recently updated to using systemd, I have experienced a number of occasions when it would just hang at a blank screen when booting. After some searching I managed to work out how to get back to having verbose output during the boot process, which showed me that the system was refusing to initialise because filesystems specified in /etc/fstab were not available (either NFS filesystems, when my network was playing up, or a USB external drive which had not spun up fast enough). It seems that systemd regards ANY missing filesystem as being a fatal error, whether or not that filesystem is actually essential to the boot process. Although this is certainly valid if vital partitions such as / or /usr can't be mounted, it's unhelpful for NFS or external partitions. That's correct. Systemd waits for 90 seconds for devices listed in /etc/fstab to show up. Since it doesn't know (unless you tell it) which devices are essential, it drops you into a rescue shell afterwards to examine the situation (unfortunately emergency mode currently has some issues, but we are dealing with that in a separate bug report). Given the default result of a blank screen with no information about what's gone wrong, this could be very problematic for less experienced or confident users if it goes out beyond Debian Testing. v209 and later will have slightly improved behaviour here. Even if the default is to boot in quiet mode, systemd will switch into verbose mode as soon as a unit fails to load or a timeout occurs. As a workaround, I have been able to ensure my system boots OK if any of these filesystems can't be mounted by adding noauto to /etc/fstab and then mounting the filesystems via /etc/rc.local instead. The better alternative in your case (i.e. mount if available but don't fail otherwise) is to mark the file systems as nofail. See man fstab. I feel that a more robust (and set up by default) fix to this is needed before systemd goes mainstream on Debian, as this aspect of systemd is somewhat less reliable than on the old init system. Please feel free to ask for any more information if it may help fixing this. Well, I consider the sysvinit behaviour buggy and unfortunately this lead to broken fstab configurations in the past. Imho there is no robust and reliable way to determine which file systems are essential and which are not (but I'm happy to be proven wrong). E.g. you might have a mysql server storing its databases on a non-standard location . Failing to mount such a partition could lead to data loss, etc. I think it's better to simply fix-up /etc/fstab once and be done with that. We can try to improve the documentation in that regard (wiki/release notes/ README.Debian) and maybe add a preinst check which tries to detect non-existing devices upon installation. The latter obviously isn't a foolproof method, as in your case you might actually have your external USB drive attached during installation but not during reboot. Comments on how to address this are welcome. Michael -- 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#721450: libscalar-list-utils-perl: uninstallable because it breaks perl upgrades
On Sat, Aug 31, 2013 at 08:11:32PM +0300, Niko Tyni wrote: I've just uploaded Changes: perl (5.18.1-3) unstable; urgency=low . * Make perl-base conflict with all versions of libscalar-list-utils-perl, which overrides Essential functionality in a way that breaks during upgrades. (Closes: #721364) so libscalar-list-utils-perl will soon be uninstallable. Cloning a bug and raising its severity. I think package removal is in order, but I'm happy to be proved wrong. Just a note that I think we have a solution for this with perl 5.20 packages. The vendorarch directory (currently /usr/lib/perl5) is being renamed to include the ABI version, so separately packaged versions of modules in perl-base shouldn't break anything anymore. The only remaining issue is that perl-base_5.20.0-1 bundles Scalar-List-Utils-1.38 and therefore Breaks: libscalar-list-utils-perl ( 1:1.38). So the version currently in sid will still be uninstallable. But that's easily solved by uploading the newest upstream version :) I suppose this bug (#721450) can be closed once the 5.20.0 packages are in sid. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 756903 is important
Processing commands for cont...@bugs.debian.org: severity 756903 important Bug #756903 [systemd] systemd: Boot hangs if filesystems unavailable Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 756903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756903 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#754830: rfcomm invocation still wrong
Processing commands for cont...@bugs.debian.org: reopen 754830 Bug #754830 {Done: Nobuhiro Iwamatsu iwama...@debian.org} [bluez] bluez: rfcomm and bluetoothd fail to start 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions bluez/5.21-2. notfixed 754830 5.21-2 Bug #754830 [bluez] bluez: rfcomm and bluetoothd fail to start Ignoring request to alter fixed versions of bug #754830 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 754830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754830 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#756465: (no subject)
Hi, I have the same Problem (on 3.14-2-686-pae). Here is the output of gdb: gdb ./maxima GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1.1+b1) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/lib/maxima/5.33.0/binary-gcl/maxima...(no debugging symbols found)...done. (gdb) set env MAXIMA_PREFIX /usr/lib/maxima/5.33.0/ (gdb) handle SIGSEGV nostop noprint SignalStop Print Pass to program Description SIGSEGV NoNo Yes Segmentation fault (gdb) b error Breakpoint 1 at 0x2a020 (gdb) r -eval '(run)' Starting program: /usr/lib/maxima/5.33.0/binary-gcl/./maxima -eval '(run)' warning: Could not load shared library symbols for linux-gate.so.1. Do you need set solib-search-path or set sysroot? Breakpoint 1, 0x0002a020 in error () (gdb) bt #0 0x0002a020 in error () #1 0x0002a0ad in ?? () #2 signal handler called #3 __GI__IO_fflush (fp=0x403e0aa0) at iofflush.c:40 #4 0x000c8ac7 in ?? () #5 0x000cb8e6 in ?? () #6 0x000d9e87 in malloc () #7 0xb7c25f2c in __fopen_internal ( filename=filename@entry=0xb7d21d01 /proc/meminfo, mode=mode@entry=0xb7d1f43c rce, is32=is32@entry=1) at iofopen.c:73 #8 0xb7c2600b in _IO_new_fopen ( filename=filename@entry=0xb7d21d01 /proc/meminfo, mode=mode@entry=0xb7d1f43c rce) at iofopen.c:103 #9 0xb7caa237 in phys_pages_info (format=0xb7d21d4a MemTotal: %ld kB) at ../sysdeps/unix/sysv/linux/getsysstats.c:296 #10 0xb7caa696 in __get_phys_pages () at ../sysdeps/unix/sysv/linux/getsysstats.c:340 #11 0xb7c7911a in posix_sysconf (name=85) at ../sysdeps/posix/sysconf.c:632 #12 linux_sysconf (name=85) at ../sysdeps/unix/sysv/linux/x86_64/../sysconf.c:145 #13 __GI___sysconf (name=85) at ../sysdeps/unix/sysv/linux/x86_64/sysconf.c:36 #14 0x000271fd in ?? () #15 0x000d6997 in ?? () ---Type return to continue, or q return to quit--- #16 0x00020cc6 in ?? () #17 0xb7bdba63 in __libc_start_main (main=0x20c90, argc=3, argv=0xb454, init=0x31a0f0, fini=0x31a160, rtld_fini=0xb7fedc90 _dl_fini, stack_end=0xb44c) at libc-start.c:287 #18 0x00021b4c in ?? () (gdb) And here the output of strace: /usr/lib/maxima/5.33.0/binary-gcl$ strace ./maxima execve(./maxima, [./maxima], [/* 35 vars */]) = 0 brk(0) = 0x3595000 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory) mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7737000 access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory) open(/etc/ld.so.cache, O_RDONLY|O_CLOEXEC) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=156484, ...}) = 0 mmap2(NULL, 156484, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb771 close(3)= 0 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory) open(/usr/lib/i386-linux-gnu/libX11.so.6, O_RDONLY|O_CLOEXEC) = 3 read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200D\1\0004\0\0\0..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0644, st_size=1276768, ...}) = 0 mmap2(NULL, 1280816, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb75d7000 mprotect(0xb770b000, 4096, PROT_NONE) = 0 mmap2(0xb770c000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x134000) = 0xb770c000 close(3)= 0 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory) open(/lib/i386-linux-gnu/i686/cmov/libm.so.6, O_RDONLY|O_CLOEXEC) = 3 read(3, \177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0F\0\0004\0\0\0..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0644, st_size=280108, ...}) = 0 mmap2(NULL, 282784, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7591000 mmap2(0xb75d5000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x43000) = 0xb75d5000 close(3)= 0 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory) open(/usr/lib/i386-linux-gnu/libgmp.so.10, O_RDONLY|O_CLOEXEC) = 3 read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\277\0\0004\0\0\0..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0644, st_size=551612, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb759 mmap2(NULL, 554480, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7508000 mmap2(0xb758e000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x85000) = 0xb758e000 close(3)= 0 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
Bug#736039: Patches for #750082 and #736039
Control: tags -1 patch Hi, please find attached a patch that fixes both release critical bugs. Regards, Markus diff -Nru pinball-0.3.1/debian/changelog pinball-0.3.1/debian/changelog --- pinball-0.3.1/debian/changelog 2011-09-22 22:18:40.0 +0200 +++ pinball-0.3.1/debian/changelog 2014-08-03 23:07:26.0 +0200 @@ -1,3 +1,15 @@ +pinball (0.3.1-13.2) unstable; urgency=medium + + * Non-maintainer upload. + * Build-depend on libtiff-dev instead of libtiff4-dev because the latter is +going to disappear soon. (Closes: #736039) + * Add missing-separators.patch. +- Replace spaces with TABS in Makefiles and thus fix a FTBFS with newer + versions of GNU Make which are less fault tolerant. Thanks to Michael + Tautschnig for the report. (Closes: #750082) + + -- Markus Koschany a...@gambaru.de Sun, 03 Aug 2014 23:00:04 +0200 + pinball (0.3.1-13.1) unstable; urgency=low * Non-maintainer upload. diff -Nru pinball-0.3.1/debian/control pinball-0.3.1/debian/control --- pinball-0.3.1/debian/control2010-05-17 18:24:18.0 +0200 +++ pinball-0.3.1/debian/control2014-08-03 23:07:26.0 +0200 @@ -2,7 +2,7 @@ Section: games Priority: optional Maintainer: Jochen Friedrich joc...@scram.de -Build-Depends: debhelper (= 7.0.50~), libgl1-mesa-dev, libpng-dev, libsdl1.2-dev, freeglut3-dev, libsdl-image1.2-dev, libsdl-mixer1.2-dev, libogg-dev, libvorbis-dev, sp, sgmlspl, docbook, docbook-utils, libaa1-dev, libasound2-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], libtiff4-dev, autoconf, automake, libtool, libltdl-dev (= 2.2.6b) +Build-Depends: debhelper (= 7.0.50~), libgl1-mesa-dev, libpng-dev, libsdl1.2-dev, freeglut3-dev, libsdl-image1.2-dev, libsdl-mixer1.2-dev, libogg-dev, libvorbis-dev, sp, sgmlspl, docbook, docbook-utils, libaa1-dev, libasound2-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], libtiff-dev, autoconf, automake, libtool, libltdl-dev (= 2.2.6b) Standards-Version: 3.8.4 Package: pinball diff -Nru pinball-0.3.1/debian/patches/missing-separators.patch pinball-0.3.1/debian/patches/missing-separators.patch --- pinball-0.3.1/debian/patches/missing-separators.patch 1970-01-01 01:00:00.0 +0100 +++ pinball-0.3.1/debian/patches/missing-separators.patch 2014-08-03 23:07:26.0 +0200 @@ -0,0 +1,101 @@ +From: Markus Koschany a...@gambaru.de +Date: Sun, 3 Aug 2014 22:50:46 +0200 +Subject: missing separators + +Bug: https://bugs.debian.org/750082 + +--- + src/Makefile.am | 14 +++--- + src/Makefile.in | 14 +++--- + test/Makefile.am | 2 +- + test/Makefile.in | 2 +- + 4 files changed, 16 insertions(+), 16 deletions(-) + +diff --git a/src/Makefile.am b/src/Makefile.am +index fbd7e8f..96768d3 100755 +--- a/src/Makefile.am b/src/Makefile.am +@@ -29,7 +29,7 @@ Script.cpp \ + StateBehavior.cpp \ + Table.cpp + +-dnl libemilia_pin_la_SOURCES = $(libemilia_pin_a_SOURCES) ++# libemilia_pin_la_SOURCES = $(libemilia_pin_a_SOURCES) + + pininclude_HEADERS = \ + ArmBehavior.h \ +@@ -56,10 +56,10 @@ Table.h + # libemilia_pin.a libemilia_addon.a libemilia_base.a libltdlc.a + wpinball.exe: ${pinball_OBJECTS} ${pinball_DEPENDENCIES} + ${GCCLOCALDIR}g++ -g -W -Wall -O2 -o$@ $^ \ +- -lSDL_mixer -lvorbisfile -lvorbis -logg -lsmpeg \ +- -lSDL_image -lSDLmain -lSDL \ +- -lglu32 -lopengl32 -ljpeg -lpng \ +- -lwinmm -luser32 -lgdi32 -ldxguid \ +- -lmingw32 -lSDLmain -lSDL -mwindows \ +- -L${GCCLOCALDIR}../lib ++ -lSDL_mixer -lvorbisfile -lvorbis -logg -lsmpeg \ ++ -lSDL_image -lSDLmain -lSDL \ ++ -lglu32 -lopengl32 -ljpeg -lpng \ ++ -lwinmm -luser32 -lgdi32 -ldxguid \ ++ -lmingw32 -lSDLmain -lSDL -mwindows \ ++ -L${GCCLOCALDIR}../lib + # !-rzr : # have to solve it later # -lstdc++ +diff --git a/src/Makefile.in b/src/Makefile.in +index ea7651b..8e95cd6 100644 +--- a/src/Makefile.in b/src/Makefile.in +@@ -505,7 +505,7 @@ uninstall-am: uninstall-binPROGRAMS uninstall-info-am \ + uninstall-pinincludeHEADERS uninstall-pinlibLIBRARIES + + +-dnl libemilia_pin_la_SOURCES = $(libemilia_pin_a_SOURCES) ++ dnl libemilia_pin_la_SOURCES = $(libemilia_pin_a_SOURCES) + + # !+rzr : This trick workaround a bad generated rule (under Linux mingw32) + # src/ litool returns: -L/usr/local//lib /usr/lib/libjpeg.so +@@ -514,12 +514,12 @@ dnl libemilia_pin_la_SOURCES = $(libemilia_pin_a_SOURCES) + # libemilia_pin.a libemilia_addon.a libemilia_base.a libltdlc.a + wpinball.exe: ${pinball_OBJECTS} ${pinball_DEPENDENCIES} + ${GCCLOCALDIR}g++ -g -W -Wall -O2 -o$@ $^ \ +- -lSDL_mixer -lvorbisfile -lvorbis -logg -lsmpeg \ +- -lSDL_image -lSDLmain -lSDL \ +- -lglu32 -lopengl32 -ljpeg -lpng \ +- -lwinmm -luser32 -lgdi32 -ldxguid \ +- -lmingw32 -lSDLmain -lSDL -mwindows \ +- -L${GCCLOCALDIR}../lib ++ -lSDL_mixer -lvorbisfile -lvorbis -logg -lsmpeg \ ++ -lSDL_image -lSDLmain -lSDL \ ++ -lglu32 -lopengl32 -ljpeg -lpng \ ++ -lwinmm -luser32 -lgdi32
Processed: Patches for #750082 and #736039
Processing control commands: tags -1 patch Bug #750082 [pinball] pinball: FTBFS - Makefile:820: *** missing separator (did you mean TAB instead of 8 spaces?). Added tag(s) patch. -- 750082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750082 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: Patches for #750082 and #736039
Processing control commands: tags -1 patch Bug #736039 [src:pinball] please build-depend on libtiff-dev, not libtiff4-dev Added tag(s) patch. -- 736039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736039 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#755728: fenics: not installable in sid
Package: fenics Version: 1:1.3.0.1 Followup-For: Bug #755728 To add more info, python-ffc now provides python-ufc and ufc (since 1.4.0-1, 03 June 2014). The problem seems to be version numbers: python-ffc is version 1.4.0-1, but fenics, python-dolfin and libdolfin1.3-dev require ufc = 2.3.0 and python-ufc = 2.30. *** 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: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fenics depends on: ii dolfin-bin1.3.0+dfsg-2 ii dolfin-doc1.3.0+dfsg-2 ii libdolfin1.3-dev 1.3.0+dfsg-2+b1 ii python-dolfin 1.3.0+dfsg-2+b1 ii python-ferari 1.0.0-1 ii python-ffc1.3.0-2 ii python-fiat 1.4.0-1 ii python-instant1.4.0-1 ii python-ufc2.3.0-1 ii python-ufl1.4.0-1 ii python-ufl-doc1.4.0-1 ii ufc 2.3.0-1 Versions of packages fenics recommends: ii python-scitools 0.9.0-1 Versions of packages fenics suggests: pn libsyfi1.0-dev none pn python-syfi none pn sfc none pn syfi-docnone -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756914: marked as done (pulseaudio: FTBFS on kfreebsd-*: portability issue)
Your message dated Sun, 03 Aug 2014 22:20:44 + with message-id e1xe48y-00066h...@franck.debian.org and subject line Bug#756914: fixed in pulseaudio 5.0-5 has caused the Debian Bug report #756914, regarding pulseaudio: FTBFS on kfreebsd-*: portability issue 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.) -- 756914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: pulseaudio Version: 5.0-3 Severity: serious Justification: FTBFS Usertags: kfreebsd Hi, your package has been failing to build on kfreebsd-* since 5.0-3, as can be seen here: https://buildd.debian.org/status/logs.php?pkg=pulseaudioarch=kfreebsd-amd64 Build log excerpt: | libtool: link: ranlib .libs/liblo-test-util.a | libtool: link: ( cd .libs rm -f liblo-test-util.la ln -s ../liblo-test-util.la liblo-test-util.la ) | /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../src -I../src/modules -I../src/modules -DPA_ALSA_PATHS_DIR=\\ -DPA_ALSA_PROFILE_SETS_DIR=\\ -D_FORTIFY_SOURCE=2 -DFASTPATH -pthread -DPA_SRCDIR=\/«PKGBUILDDIR»/src\ -DPA_BUILDDIR=\/«PKGBUILDDIR»/src\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -W -Wextra -pipe -Wno-long-long -Wno-overlength-strings -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -fno-common -fdiagnostics-show-option -c -o utils/libpulsedsp_la-padsp.lo `test -f 'utils/padsp.c' || echo './'`utils/padsp.c | libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../src -I../src/modules -I../src/modules -DPA_ALSA_PATHS_DIR=\\ -DPA_ALSA_PROFILE_SETS_DIR=\\ -D_FORTIFY_SOURCE=2 -DFASTPATH -pthread -DPA_SRCDIR=\/«PKGBUILDDIR»/src\ -DPA_BUILDDIR=\/«PKGBUILDDIR»/src\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -W -Wextra -pipe -Wno-long-long -Wno-overlength-strings -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -fno-common -fdiagnostics-show-option -c utils/padsp.c -fPIC -DPIC -o utils/.libs/libpulsedsp_la-padsp.o | In file included from utils/padsp.c:45:0: | utils/padsp.c: In function 'open': | utils/padsp.c:1522:33: warning: 'short unsigned int' is promoted to 'int' when passed through '...' | mode = va_arg(args, mode_t); | ^ | utils/padsp.c:1522:33: note: (so you should pass 'int' not 'short unsigned int' to 'va_arg') | utils/padsp.c:1522:33: note: if this code is reached, the program will abort | utils/padsp.c: In function 'open64': | utils/padsp.c:2561:33: warning: 'short unsigned int' is promoted to 'int' when passed through '...' | mode = va_arg(args, mode_t); | ^ | utils/padsp.c:2561:33: note: if this code is reached, the program will abort | /bin/bash ../libtool --tag=CC --mode=link gcc -std=gnu99 -pthread -DPA_SRCDIR=\/«PKGBUILDDIR»/src\ -DPA_BUILDDIR=\/«PKGBUILDDIR»/src\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -W -Wextra -pipe -Wno-long-long -Wno-overlength-strings -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -fno-common -fdiagnostics-show-option -Wl,-z,nodelete-avoid-version -disable-static -Wl,-z,relro -Wl,--no-as-needed -o libpulsedsp.la -rpath /usr/lib/x86_64-kfreebsd-gnu/pulseaudio utils/libpulsedsp_la-padsp.lo libpulse.la libpulsecommon-5.0.la -lpthread -lrt -ldl -lm | libtool: link: gcc -std=gnu99 -shared -fPIC -DPIC utils/.libs/libpulsedsp_la-padsp.o -Wl,-rpath
Bug#368297: Does OpenLDAP has any GPLv2 dependency?
On Tue, 05 Nov 2013 at 15:45:07 +0100, Carlos Alberto Lopez Perez wrote: On 24/04/12 17:25, Thorsten Glaser wrote: this bug has been brought to my attention by my boss today. If I understand the situation correctly, the problem is: • OpenLDAP links against GnuTLS (gnutls26) • gnutls26 links against gcrypt, which has the bug • gnutls28 links against nettle, but also gmp which is LGPLv3+ • OpenLDAP thus can’t link against gnutls28, as it has reverse dependencies that are not LGPLv3-/GPLv3-compatible • the package affected is libnss-ldap though If there isn't any GPLv2 reverse dependency, then OpenLDAP can be just recompiled to link against gnutls28 and this long standing bug will be fixed. As far as I understand it, this became simpler in recent months: * gnutls28 links against gmp, which was relicensed to LGPL-3+ or GPL-2+, making it possible to link GPL-2 (only) code to gnutls28 So would linking OpenLDAP to gnutls28 (#745231, tagged pending) close this RC bug as a side-effect? S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752870: latest development version fixes all problems
Hello, back from hollidays with 900+ emails to sort, I was eager to download and test the latest development version. Good news: all problems fixed :-) Hope this helps, -- Rémi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756709: redis-server: fails to start
Hi Chris, sorry for the late answer, I was of in the mountains of backcountry Japan for few days ;-) redis-server[25874]: Can't open the log file: Permission denied Sorry about that, there was a permissions/systemd-related fix and it was obviously incomplete. However, I don't use systemd (yet). Can you send me the output of your: $ ls -al /var/log/redis total 4 drwxr-xr-x 1 redis redis 32 Jul 31 08:41 ./ drwxr-xr-x 1 root root 1072 Aug 1 09:51 ../ -rw-r--r-- 1 root root 2006 Jul 31 09:07 redis-server.log All the best Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756963: direnv: FTBFS due to test suite failures
Source: direnv Version: 2.4.0-1 Severity: serious Justification: FTBFS Hi, your package FBTFS on arm* and i386 in its test suite. Example on i386: |dh_auto_test -a | make[1]: Entering directory '/«PKGBUILDDIR»' | go test | PASS | ok_/«PKGBUILDDIR» 0.005s | ./test/direnv-test.sh | direnv: loading .envrc | ## Testing base ## | direnv: loading .envrc | direnv: export +HELLO | direnv: loading .envrc | direnv: export +HELLO | direnv: loading ../.envrc | | | ## Testing inherit ## | direnv: loading .envrc | world | direnv: export +HELLO | direnv: loading .envrc | ## Testing ruby-layout ## | direnv: loading .envrc | /bin/bash: line 299: ruby: command not found | direnv: export +BUNDLE_BIN +GEM_HOME ~PATH | direnv: loading .envrc | | ## Testing space dir ## | direnv: loading .envrc | direnv: export +SPACE_DIR ~PATH | direnv: loading .envrc | ## Testing child-env ## | direnv: loading .envrc | direnv: export +CHILD +PARENT_POST +PARENT_PRE | direnv: loading .envrc | ## Testing special-vars ## | direnv: error .envrc is blocked. Run `direnv allow` to approve its content. | direnv: error .envrc is blocked. Run `direnv allow` to approve its content. | direnv: error mkdir /sbuild-nonexistent: permission denied Full build log: https://buildd.debian.org/status/fetch.php?pkg=direnvarch=i386ver=2.4.0-1stamp=1406972872 If you need a writable HOME, you could use a subdir of $(CURDIR), and set HOME to that. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 719490 is serious
Processing commands for cont...@bugs.debian.org: severity 719490 serious Bug #719490 [menu-cache] missing authors in copyright file Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 719490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719490 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#755327: gridsite: FTBFS: htcp.c:65:27: error: 'CURLOPT_FILE' undeclared (first use in this function)
Hi Gianfranco, On Sun, Aug 3, 2014 at 1:02 AM, Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote: I see, the copy-pasted stripped the tab + #define HTCP_GET1 + #define HTCP_PUT2 + #define HTCP_DELETE3 + #define HTCP_GET 1 + #define HTCP_PUT 2 + #define HTCP_DELETE 3 maybe next time I'll send the patch as attachment, to avoid this kind of problems Ah, that explains it. Sorry, I didn't realize you already had a package up on mentors, please link it along with your debdiff next time. Aside from that, I have to say that I prefer Colin's proposed debdiff rather than yours; testing for older versions of curl rather than just getting rid of legacy code is the right approach and makes it easier to backport this package if desired. I have _nothing_ against Colin's approach (we already discussed it a little on irc). But look at the define ++#if (LIBCURL_VERSION_NUM 0x070907) do you want to really to backport this package to a system with a curl packaged in 2002??? curl (7.9.7-1) unstable; urgency=low Wed, 15 May 2002 21:09:19 +0200 oldstable has already 7.21, so I don't see the point in maintaining such code, moreover because upstream just dropped it completely. So if you want to go with this approach is fine for me, since ubuntu already took the patch. But I still think that having an upstream commit cherry-picked (alrady used by fedora people) can help in maintaining the code https://github.com/CESNET/gridsite/commit/2124d471f9fc1eed4bf5893ed2701350357c01af http://pkgs.fedoraproject.org/cgit/gridsite.git/tree/curl-opts.patch I'm still of the opinion that Colin's approach is a more technically-correct one, but either debdiff fixes this build failure, and ultimately it's up to gridsite's maintainer to choose the approach they prefer (once they start actively working on their package again). *shrugs* Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: UXA regression causes BENQ FP747 screen to go berserk upon xrandr --auto
Processing commands for cont...@bugs.debian.org: retitle 750605 UXA regression causes BENQ FP747 screen to go berserk upon xrandr --auto Bug #750605 [xserver-xorg-video-intel] screen goes berserk, had to downgrade Changed Bug title to 'UXA regression causes BENQ FP747 screen to go berserk upon xrandr --auto' from 'screen goes berserk, had to downgrade' thanks Stopping processing here. Please contact me if you need assistance. -- 750605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750605 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#750605: UXA regression causes BENQ FP747 screen to go berserk upon xrandr --auto
retitle 750605 UXA regression causes BENQ FP747 screen to go berserk upon xrandr --auto thanks (Fixing title to match my discoveries which I have posted on the https://bugs.freedesktop.org/show_bug.cgi?id=82068 ) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756915: marked as done (libcgroup: error in upstream license version)
Your message dated Mon, 04 Aug 2014 03:49:41 + with message-id e1xe9hj-0003rf...@franck.debian.org and subject line Bug#756915: fixed in libcgroup 0.41-5 has caused the Debian Bug report #756915, regarding libcgroup: error in upstream license version 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.) -- 756915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libcgroup Version: 0.41-4 Severity: serious Justification: Policy 12.5 debian/copyright states that the upstream license is LGPL-2.1+, when in fact it is LGPL-2.1. ---End Message--- ---BeginMessage--- Source: libcgroup Source-Version: 0.41-5 We believe that the bug you reported is fixed in the latest version of libcgroup, 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 756...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Kastner deb...@kvr.at (supplier of updated libcgroup 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, 3 Aug 2014 19:48:13 PDT Source: libcgroup Binary: cgroup-tools libcgroup1 libcgroup-dbg libcgroup-dev libpam-cgroup cgroup-bin Architecture: source all Version: 0.41-5 Distribution: unstable Urgency: low Maintainer: Christian Kastner deb...@kvr.at Changed-By: Christian Kastner deb...@kvr.at Description: cgroup-tools - control and monitor control groups (tools) libcgroup1 - control and monitor control groups (library) libcgroup-dbg - control and monitor control groups (debug) libcgroup-dev - control and monitor control groups (development) libpam-cgroup - control and monitor control groups (PAM) cgroup-bin - control and monitor control groups (transitional package) Closes: 756092 756915 Changes: libcgroup (0.41-5) unstable; urgency=low . * debian/control: - Set myself to new maintainer. Closes: #756092 - Use versioned Breaks instead of Conflicts - Use versioned Replaces instead of unversioned one - Update Vcs- fields to collab-maint - Drop redundant Section - Add Multi-Arch fields * debian/patches (refreshed): - Update headers of existing patches to play more nicely with gbp-pq * debian/watch: - Create watch file * debian/copyright: - Correct upstream license from LGPL-2.1+ to LGPL-2.1. Closes: #756915 - Add myself - src/pam/pam_cgroup.c also contains LGPL-2.1 code * debian/patches (added): - 0005-Syntax-fixes-for-man-pages Checksums-Sha256: bcb65dc22677ed5469484499180145c9757913d0b23c6a7b0a3450c269646c5e 2207 libcgroup_0.41-5.dsc 35a4e6cb2af7127441ef704dfd238c397c1eeaf9e484346295fd5eb1fac30735 14648 libcgroup_0.41-5.debian.tar.xz f2483685d3aa26f621a3179ebccb86c7a58cb1a684be6a0b4f82c8869db66f1c 6034 cgroup-bin_0.41-5_all.deb Checksums-Sha1: d3be0441423ca0ceb4aff8620484587cdc35e649 2207 libcgroup_0.41-5.dsc dffa2ea48e96ae4351fb0051464643d2a20e4499 14648 libcgroup_0.41-5.debian.tar.xz fbe4e4cc6d126f1e63b6185eedeb193dc50bd7eb 6034 cgroup-bin_0.41-5_all.deb Files: cefad360cfe754005dc23eed261045c6 2207 libs optional libcgroup_0.41-5.dsc 3da8ac84b9e2b1c7e4e7a2b05c381878 14648 libs optional libcgroup_0.41-5.debian.tar.xz cab95684a28bbc747cba0bc503277a37 6034 oldlibs extra cgroup-bin_0.41-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT3vRyAAoJEI7tzBuqHzL/n6gQALWFmHEqlqFNtGaRe4tMCpYL jLhDHIWum8sq06TdcCAqbmrF3J7164ITKf6IeXxQRozv4/87SclbbbG7RwozXqrB 0W9p0mjCRrKBefgB1xOgvVx+uLKhH9HculPY1MJT+G5X8y8Tq7NsDTjwTDaXcyMy wsU+eC0fBvxiSONSob4LiTMtxwoLM2DBOT+ERBRotx98SpzBoSzC5T4QASth2jtJ di56b11aUh1NMqO1SimJNzoxWqoZlKFkgMJmc3HtyIdNrSeQz6joQe2OrW02TQ4v NJ8ZJDkSWgioSZYc7v6gLV60/cENjKLrwnsABCzAhqX/4sgP/14gwSCicXkBCqqz G1y1KvNsZFJuoFItNaDeVvCSa71ptFxVTcreYq3NZHTG2fPKfrOe4YW7ylZK1PZE KcRa16rDlfSX8esA04JYZOVJAKSjf1APtWWA8+8vxX66jKh09VtrG1KXZH7ZdJ0s Ls/hJHwDns6vqbOo+XLkC3eJmlsTbrAF9gakG0mrUyTPMEvM2Dzjgrcpd3E97AT8 VdTScFexL98ZVENT0BdqGk9X8mmLL9AUNlA1W7IcmW8n6b2NLLOVHlrjBONaXp0v bLu6+c39beiAZ8UOShgxWLPSy54vgT8c4VWAnNezqlWB9gnYtPft8V4qXW728dwo mE+2z+b9ZHRZPepqOz0C =CU6C -END PGP SIGNATUREEnd Message---
Bug#743685: marked as done (FTBFS: test failures)
Your message dated Sun, 3 Aug 2014 21:56:22 -0700 with message-id CACZd_tAG3UXrFi8JxQAFffB-=rQisKxiB=fje67csimgwi_...@mail.gmail.com and subject line Re: Bug#743685: urwid: FTBFS: test failures has caused the Debian Bug report #743685, regarding FTBFS: test failures 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.) -- 743685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: urwid Version: 1.2.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, urwid 1.2.1-1 currently FTBFS on i386 and mipsel according to the buildd [1] logs. Note that the test suite is now run against all python2 and python3 versions supported in sid (rather than just python2, as was the case with previous versions of urwid); the test failure on i386 is a new one, and only happens with python3. i386 [2]: == FAIL: test_linefeed (urwid.tests.test_vterm.TermTest) -- Traceback (most recent call last): File /«PKGBUILDDIR»/build/lib.linux-i686-3.4/urwid/tests/test_vterm.py, line 128, in test_linefeed self.expect('hello\nworld') File /«PKGBUILDDIR»/build/lib.linux-i686-3.4/urwid/tests/test_vterm.py, line 120, in expect self.assertEqual(got, what, desc) AssertionError: b'hello' != b'hello\nworld' : Expected: b'hello\nworld' Got: b'hello' -- Ran 280 tests in 0.758s FAILED (failures=1) mipsel [3]: == FAIL: test_run (urwid.tests.test_event_loops.TwistedEventLoopTest) -- Traceback (most recent call last): File /«PKGBUILDDIR»/urwid/tests/test_event_loops.py, line 128, in test_run self.assertIn(da, out) AssertionError: 'da' not found in ['waiting', 'hello', 'clean exit'] -- Ran 289 tests in 6.329s FAILED (failures=1) [1] https://buildd.debian.org/status/package.php?p=urwid [2] https://buildd.debian.org/status/fetch.php?pkg=urwidarch=i386ver=1.2.1-1stamp=1396632579 [3] https://buildd.debian.org/status/fetch.php?pkg=urwidarch=mipselver=1.2.1-1stamp=1396648217 Regards, Vincent -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (700, 'testing'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-5-vclaptop-amd64 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Version: 1.2.1-2 Looks like the latest round of binNMUs don't FTBFS...so I'm closing this bug report. Regards, Vincent---End Message---
Bug#747506: openjdk-6: cannot load libsikuli-script-java any more
Thank you for the bug report. Do you think you could attach a test case to reproduce this error please? Do you know if it also fails with openjdk-7? Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756465: maxima: Segmentation fault during startup
Here we go, maybe|hopefully it is helpful: - cut -- jomo@mars [/home/jomo] gdb /usr/lib/maxima/5.33.0/binary-gcl/maxima GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1.1+b1) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/lib/maxima/5.33.0/binary-gcl/maxima...(no debugging symbols found)...done. (gdb) set env MAXIMA_PREFIX /usr/lib/maxima/5.33.0/ (gdb) handle SIGSEGV nostop noprint SignalStop Print Pass to program Description SIGSEGV NoNo Yes Segmentation fault (gdb) b error Breakpoint 1 at 0x2a020 (gdb) r -eval '(run)' Starting program: /usr/lib/maxima/5.33.0/binary-gcl/maxima -eval '(run)' warning: Could not load shared library symbols for linux-gate.so.1. Do you need set solib-search-path or set sysroot? Breakpoint 1, 0x0002a020 in error () (gdb) where #0 0x0002a020 in error () #1 0x0002a0ad in ?? () #2 signal handler called #3 __GI__IO_fflush (fp=0x403e0aa0) at iofflush.c:40 #4 0x000c8ac7 in ?? () #5 0x000cb8e6 in ?? () #6 0x000d9e87 in malloc () #7 0x4b274f2c in __fopen_internal (filename=filename@entry=0x4b370d01 /proc/meminfo, mode=mode@entry=0x4b36e43c rce, is32=is32@entry=1) at iofopen.c:73 #8 0x4b27500b in _IO_new_fopen (filename=filename@entry=0x4b370d01 /proc/meminfo, mode=mode@entry=0x4b36e43c rce) at iofopen.c:103 #9 0x4b2f9237 in phys_pages_info (format=0x4b370d4a MemTotal: %ld kB) at ../sysdeps/unix/sysv/linux/getsysstats.c:296 #10 0x4b2f9696 in __get_phys_pages () at ../sysdeps/unix/sysv/linux/getsysstats.c:340 #11 0x4b2c811a in posix_sysconf (name=85) at ../sysdeps/posix/sysconf.c:632 #12 linux_sysconf (name=85) at ../sysdeps/unix/sysv/linux/x86_64/../sysconf.c:145 #13 __GI___sysconf (name=85) at ../sysdeps/unix/sysv/linux/x86_64/sysconf.c:36 #14 0x000271fd in ?? () #15 0x000d6997 in ?? () #16 0x00020cc6 in ?? () #17 0x4b22aa63 in __libc_start_main (main=0x20c90, argc=3, argv=0xb464, init=0x31a0f0, fini=0x31a160, rtld_fini=0x4b1fcc90 _dl_fini, stack_end=0xb45c) at libc-start.c:287 #18 0x00021b4c in ?? () (gdb) - cut -- - cut -- jomo@mars [/home/jomo] strace -f /usr/lib/maxima/5.33.0/binary-gcl/maxima execve(/usr/lib/maxima/5.33.0/binary-gcl/maxima, [/usr/lib/maxima/5.33.0/binary-gc...], [/* 44 vars */]) = 0 brk(0) = 0x2f27000 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory) mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb77c3000 access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory) open(/etc/ld.so.cache, O_RDONLY|O_CLOEXEC) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=194548, ...}) = 0 mmap2(NULL, 194548, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7793000 close(3)= 0 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory) open(/usr/lib/i386-linux-gnu/libX11.so.6, O_RDONLY|O_CLOEXEC) = 3 read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200\4OK4\0\0\0..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0644, st_size=1278448, ...}) = 0 mmap2(0x4b4dc000, 1280816, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x4b4dc000 mprotect(0x4b61, 4096, PROT_NONE) = 0 mmap2(0x4b611000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x134000) = 0x4b611000 close(3)= 0 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory) open(/lib/i386-linux-gnu/i686/cmov/libm.so.6, O_RDONLY|O_CLOEXEC) = 3 read(3, \177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0\226K4\0\0\0..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0644, st_size=281844, ...}) = 0 mmap2(0x4b3c5000, 282784, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x4b3c5000 mmap2(0x4b409000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x43000) = 0x4b409000 close(3)= 0 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory) open(/usr/lib/i386-linux-gnu/libgmp.so.10, O_RDONLY|O_CLOEXEC) = 3 read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\377\242L4\0\0\0..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0644, st_size=553124, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7792000 mmap2(0x4ca24000, 554480, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x4ca24000 mmap2(0x4caaa000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE,