Bug#794573: kwin-style-breeze: broken in testing
reopen 794573 thanks I'm reopening this as it is now broken in testing. This combination: ii kwin-x114:5.3.2-3 ii kwin-style-breeze 4:5.3.2-2 Doesn't work and the user cannot login to a KDE5 session. The only workaround is to move kwin-style-breeze's /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kdecoration2/breezedecoration.so out of the way and then go to system settings and change the style to plastik. FWIW, I see the exact same issue with kwin-decoration-oxygen, leaving plastik as the only decoration that works.
Bug#796729: libfreecontact-perl: hardcoded dependency on shared library package
Source: libfreecontact-perl Version: 0.08-3 Severity: serious libfreecontact-perl hardcodes its dependency on libfreecontact0. Please fix. Cheers, Julien signature.asc Description: Digital signature
Bug#794736: libvigraimpex: library transition is needed when GCC 5 is the default
On Thu, 13 Aug 2015 at 13:47:04 +0200, Daniel Stender wrote: We have some other serious issues open for Vigra (with the Lenna image set [2] and test suite problems in Mips), so I suggest we do it that way: I'm going to prepare a v5 1.9.0+dfsg-11 for unstable in the next days and check the reverse deps. Did this ever happen? I believe the current policy is that maintainers (and NMUers) should upload transitioning packages to unstable as soon as each library build-dependency that needs a transition has started it. If necessary, add versioned build-dependencies, to make sure that your package will go into Dep-Wait state on the buildds until their build-dependencies are at the transitioned version on the relevant architecture. The bug about the Lena sample/test images does not need to block this: while it is a bug that should be fixed, it isn't a regression (the version currently in testing is no better than the one in unstable in this respect), and unlike the libstdc++ transition it can't block work elsewhere in Debian. If the offending files are also present in stable/testing (which I suspect they are), please mark the bug as found in those versions so that the BTS knows what's going on. 1.10.0 in experimental seems to have built successfully on mips, hopefully that's a good sign for that bit. You shouldn't need to go through the NEW queue for a second time when 1.9.0+dfsg-11 is uploaded, because the new binary package name has already been approved. S
Bug#796740: linux-image-4.0.0-2-amd64: kernel gets drugged to sleep when idle
Package: src:linux Version: 4.0.8-2 Severity: grave Tags: upstream Justification: renders package unusable Mommy Mommy he wont wake up seems to summarize this one nicely. System goes to sleep when idle for any length of time. Problem is once asleep, it wont wake. Not using sw suspend or anything like that either. Did not notice this with debian in the past, even with the 990FX board, buggy as it may be. No, I cant use anything newer, kmod causes video driver and virtualbox breakage(yet again).Stuck with #4002 until reformat or kmod issue gets fixed. Making backup set is taking sweet time. -- Package-specific info: ** Version: Linux version 4.0.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.3 (Debian 4.9.3-2) ) #1 SMP Debian 4.0.8-2 (2015-07-22) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.0.0-2-amd64 root=UUID=e26b0d1e-661c-4ee3-8e0b-e1bf691fe8df ro rootflags=data=writeback selinux=1 security=selinux nomodeset quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 579.060877] blk_update_request: I/O error, dev loop0, sector 54571264 [ 582.156555] blk_update_request: I/O error, dev loop0, sector 54575360 [ 583.244735] [UFW BLOCK] IN=wlp12s0 OUT= MAC=1c:87:2c:c8:8e:5c:c0:56:27:60:d6:cd:08:00 SRC=188.165.138.141 DST=192.168.2.116 LEN=595 TOS=0x00 PREC=0x00 TTL=45 ID=47168 DF PROTO=TCP SPT=443 DPT=59490 WINDOW=661 RES=0x00 ACK PSH URGP=0 [ 585.107399] blk_update_request: I/O error, dev loop0, sector 54579456 [ 588.062510] blk_update_request: I/O error, dev loop0, sector 54583552 [ 591.012143] blk_update_request: I/O error, dev loop0, sector 54587648 [ 594.126897] blk_update_request: I/O error, dev loop0, sector 58720512 [ 597.372589] blk_update_request: I/O error, dev loop0, sector 58724608 [ 600.337556] blk_update_request: I/O error, dev loop0, sector 58728704 [ 603.73] blk_update_request: I/O error, dev loop0, sector 58732800 [ 606.281569] blk_update_request: I/O error, dev loop0, sector 58736896 [ 609.164969] blk_update_request: I/O error, dev loop0, sector 58740992 [ 612.232890] blk_update_request: I/O error, dev loop0, sector 58745088 [ 615.210854] blk_update_request: I/O error, dev loop0, sector 58749184 [ 617.913699] blk_update_request: I/O error, dev loop0, sector 58753280 [ 620.589018] blk_update_request: I/O error, dev loop0, sector 58757376 [ 623.345640] blk_update_request: I/O error, dev loop0, sector 58761472 [ 624.756396] blk_update_request: I/O error, dev loop0, sector 58765568 [ 627.856808] blk_update_request: I/O error, dev loop0, sector 58769664 [ 630.320201] blk_update_request: I/O error, dev loop0, sector 58773760 [ 633.368311] blk_update_request: I/O error, dev loop0, sector 58777856 [ 636.273778] blk_update_request: I/O error, dev loop0, sector 58781952 [ 639.265523] blk_update_request: I/O error, dev loop0, sector 62914816 [ 642.175820] blk_update_request: I/O error, dev loop0, sector 62918912 [ 645.342890] blk_update_request: I/O error, dev loop0, sector 62923008 [ 648.636447] blk_update_request: I/O error, dev loop0, sector 62927104 [ 651.671986] blk_update_request: I/O error, dev loop0, sector 62931200 [ 654.584310] blk_update_request: I/O error, dev loop0, sector 62935296 [ 657.511437] blk_update_request: I/O error, dev loop0, sector 62939392 [ 660.430684] blk_update_request: I/O error, dev loop0, sector 62943488 [ 663.678931] blk_update_request: I/O error, dev loop0, sector 62947584 [ 666.783078] blk_update_request: I/O error, dev loop0, sector 62951680 [ 669.875692] blk_update_request: I/O error, dev loop0, sector 62955776 [ 670.379664] [UFW BLOCK] IN=wlp12s0 OUT= MAC=1c:87:2c:c8:8e:5c:c0:56:27:60:d6:cd:08:00 SRC=92.222.4.102 DST=192.168.2.116 LEN=595 TOS=0x00 PREC=0x00 TTL=45 ID=45072 DF PROTO=TCP SPT=9001 DPT=18988 WINDOW=501 RES=0x00 ACK PSH URGP=0 [ 673.068359] blk_update_request: I/O error, dev loop0, sector 62959872 [ 675.895932] blk_update_request: I/O error, dev loop0, sector 62963968 [ 678.575734] blk_update_request: I/O error, dev loop0, sector 62968064 [ 681.285705] blk_update_request: I/O error, dev loop0, sector 62972160 [ 683.681641] [UFW BLOCK] IN=wlp12s0 OUT= MAC=1c:87:2c:c8:8e:5c:c0:56:27:60:d6:cd:08:00 SRC=89.238.161.245 DST=192.168.2.116 LEN=595 TOS=0x00 PREC=0x00 TTL=46 ID=1586 DF PROTO=TCP SPT=49001 DPT=50577 WINDOW=450 RES=0x00 ACK PSH URGP=0 [ 684.039210] blk_update_request: I/O error, dev loop0, sector 62976256 [ 686.682965] blk_update_request: I/O error, dev loop0, sector 67109120 [ 689.299573] blk_update_request: I/O error, dev loop0, sector 67113216 [ 691.935909] blk_update_request: I/O error, dev loop0, sector 67117312 [ 694.623868] blk_update_request: I/O error, dev loop0, sector 67121408 [ 697.274082] blk_update_request: I/O error, dev loop0, sector 67125504 [ 699.972679] blk_update_request: I/O error, dev loop0, sector 67129600 [ 702.675092] blk_update_request: I/O error, dev loop0,
Bug#796731: freecontact: FTBFS on mips (test suite failure)
Source: freecontact Version: 1.0.21-4 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package failed to build on the mips buildd, see the log at https://buildd.debian.org/status/fetch.php?pkg=freecontactarch=mipsver=1.0.21-4stamp=1440138640 Cheers, Julien signature.asc Description: Digital signature
Bug#796735: ruby-omniauth-kerberos: Missing Build-Depends on ruby-rack-test
Source: ruby-omniauth-kerberos Version: 0.3.0-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, ruby-omniauth-kerberos fails to build from source in unstable/amd64 due to missing Build-Depends on ruby-rack-test: [..] ┌──┐ │ Run tests for ruby2.1 from debian/ruby-tests.rake │ └──┘ RUBYLIB=/tmp/buildd/ruby-omniauth-kerberos-0.3.0/debian/ruby-omniauth-kerberos/usr/lib/ruby/vendor_ruby:. rake2.1 -f debian/ruby-tests.rake /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- rack/test (LoadError) from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /tmp/buildd/ruby-omniauth-kerberos-0.3.0/spec/omniauth/strategy/kerberos_spec.rb:2:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke' from /usr/bin/rspec:4:in `main' /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed ERROR: Test ruby2.1 failed. Exiting. dh_auto_install: dh_ruby --install /tmp/buildd/ruby-omniauth-kerberos-0.3.0/debian/ruby-omniauth-kerberos returned exit code 1 debian/rules:18: recipe for target 'binary' failed make: *** [binary] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/ruby-omniauth-kerberos_0.3.0-1.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- I: using fakeroot in build. I: pbuilder: network access will be disabled during build I: Current time: Sat Aug 22 03:39:35 GMT+12 2015 I: pbuilder-time-stamp: 1440257975 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz] I: creating local configuration I: copying local configuration I: mounting /proc filesystem I: mounting /run/shm filesystem I: mounting /dev/pts filesystem I: Mounting /dev/shm I: Mounting /sys I: policy-rc.d already exists I: Installing the build-deps - Attempting to satisfy build-dependencies - Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: debhelper (= 7.0.50~), gem2deb, rake, ruby-omniauth-multipassword, ruby-rspec, ruby-timfel-krb5-auth (= 0.8) dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 20247 files and directories currently installed.) Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ... Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ... dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested: pbuilder-satisfydepends-dummy depends on gem2deb; however: Package gem2deb is not installed. pbuilder-satisfydepends-dummy depends on rake; however: Package rake is not installed. pbuilder-satisfydepends-dummy depends on ruby-omniauth-multipassword; however: Package ruby-omniauth-multipassword is not installed. pbuilder-satisfydepends-dummy depends on ruby-rspec; however: Package ruby-rspec is not installed. pbuilder-satisfydepends-dummy depends on ruby-timfel-krb5-auth (= 0.8); however: Package ruby-timfel-krb5-auth is not installed. Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ... Reading package lists... Building dependency tree... Reading state information... Initializing
Bug#796666: NMU diff attached
Here's the diff I intend to upload shortly.
Scott Kdiff -Nru ois-1.3.0+dfsg0/debian/changelog ois-1.3.0+dfsg0/debian/changelog
--- ois-1.3.0+dfsg0/debian/changelog 2012-04-30 07:55:23.0 -0400
+++ ois-1.3.0+dfsg0/debian/changelog 2015-08-23 13:02:23.0 -0400
@@ -1,3 +1,12 @@
+ois (1.3.0+dfsg0-5.1) unstable; urgency=medium
+
+ * Non-maintainer upload (See #79).
+
+ [ Steve Langasek ]
+ * Rename library packages for g++5 ABI transition.
+
+ -- Scott Kitterman sc...@kitterman.com Sun, 23 Aug 2015 12:48:05 -0400
+
ois (1.3.0+dfsg0-5) unstable; urgency=medium
* Team upload.
diff -Nru ois-1.3.0+dfsg0/debian/control ois-1.3.0+dfsg0/debian/control
--- ois-1.3.0+dfsg0/debian/control 2012-04-30 07:46:58.0 -0400
+++ ois-1.3.0+dfsg0/debian/control 2015-08-23 12:47:38.0 -0400
@@ -24,7 +24,7 @@
Architecture: any
Multi-Arch: same
Depends:
- libois-1.3.0 (= ${binary:Version}),
+ libois-1.3.0v5 (= ${binary:Version}),
${misc:Depends}
Description: Object Oriented Input System library (C++ development headers)
Object Oriented Input System (OIS) is meant to be a cross platform,
@@ -33,7 +33,7 @@
.
This package provides the development files.
-Package: libois-1.3.0
+Package: libois-1.3.0v5
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
@@ -42,8 +42,9 @@
${shlibs:Depends}
Breaks:
libois
-Replaces:
+Replaces: libois-1.3.0,
libois
+Conflicts: libois-1.3.0
Description: Object Oriented Input System library (C++)
Object Oriented Input System (OIS) is meant to be a cross platform,
simple solution for using all kinds of Input Devices
diff -Nru ois-1.3.0+dfsg0/debian/libois-1.3.0.dirs ois-1.3.0+dfsg0/debian/libois-1.3.0.dirs
--- ois-1.3.0+dfsg0/debian/libois-1.3.0.dirs 2012-04-30 07:46:58.0 -0400
+++ ois-1.3.0+dfsg0/debian/libois-1.3.0.dirs 1969-12-31 19:00:00.0 -0500
@@ -1,2 +0,0 @@
-usr/lib
-usr/lib
diff -Nru ois-1.3.0+dfsg0/debian/libois-1.3.0.install ois-1.3.0+dfsg0/debian/libois-1.3.0.install
--- ois-1.3.0+dfsg0/debian/libois-1.3.0.install 2012-04-30 07:46:58.0 -0400
+++ ois-1.3.0+dfsg0/debian/libois-1.3.0.install 1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-usr/lib/*/libOIS-*.so
diff -Nru ois-1.3.0+dfsg0/debian/libois-1.3.0v5.dirs ois-1.3.0+dfsg0/debian/libois-1.3.0v5.dirs
--- ois-1.3.0+dfsg0/debian/libois-1.3.0v5.dirs 1969-12-31 19:00:00.0 -0500
+++ ois-1.3.0+dfsg0/debian/libois-1.3.0v5.dirs 2015-08-23 12:47:38.0 -0400
@@ -0,0 +1,2 @@
+usr/lib
+usr/lib
diff -Nru ois-1.3.0+dfsg0/debian/libois-1.3.0v5.install ois-1.3.0+dfsg0/debian/libois-1.3.0v5.install
--- ois-1.3.0+dfsg0/debian/libois-1.3.0v5.install 1969-12-31 19:00:00.0 -0500
+++ ois-1.3.0+dfsg0/debian/libois-1.3.0v5.install 2015-08-23 12:47:38.0 -0400
@@ -0,0 +1 @@
+usr/lib/*/libOIS-*.so
diff -Nru ois-1.3.0+dfsg0/debian/libois-1.3.0v5.lintian-overrides ois-1.3.0+dfsg0/debian/libois-1.3.0v5.lintian-overrides
--- ois-1.3.0+dfsg0/debian/libois-1.3.0v5.lintian-overrides 1969-12-31 19:00:00.0 -0500
+++ ois-1.3.0+dfsg0/debian/libois-1.3.0v5.lintian-overrides 2015-08-23 12:47:38.0 -0400
@@ -0,0 +1,2 @@
+# G++5 ABI transition
+libois-1.3.0v5: package-name-doesnt-match-sonames libois-1.3.0
Bug#796666: NMU diff attached
Control: tags -1 + pending On 2015-08-23 13:08:04, Scott Kitterman wrote: Here's the diff I intend to upload shortly. Scott K No need to upload this NMU. A fix is already in NEW. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Processed: severity of 796666 is serious
Processing commands for cont...@bugs.debian.org: severity 79 serious Bug #79 [src:ois] ois: library transition needed when GCC 5 is the default Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 79: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=79 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#791173: libstxxl: library transition may be needed when GCC 5 is the default
On 23/08/15 16:10, Sebastiaan Couwenberg wrote: On 23-08-15 16:59, Simon McVittie wrote: The SONAME bump option was only really meant to be taken if the library had an upstream SONAME bump pending anyway (for instance icu and boost went this route). If there is not a SONAME change already in the pipeline, you should do the v5 rename instead. My NMUs of gtkmm2.4, gtkmm3.0, atlas-cpp, bullet etc. should make a reasonable template for how this works. I have the packaging for the libstxll v5 rename mostly ready in my local git, I can push this to Alioth and/or NMU it to DELAYED/2 if you want. Regardless of whether you NMU, please compare what you have done with the Ubuntu patch at http://patches.ubuntu.com/libs/libstxxl/libstxxl_1.4.1-1ubuntu1.patch (you'll probably find it ended up identical), and send a diff against current unstable to this bug. If you've done the work already, and if all the library build-deps either don't need a transition or have already started theirs, then I would personally say you might as well NMU to an appropriate DELAYED queue. This overall transition has broken unstable for 3 weeks already, during which lots of packages are either uninstallable or non-functional, and basically no C++ can migrate to testing; the sooner we can get through it and have our distribution back, the better. S
Processed: Re: Bug#796666: NMU diff attached
Processing control commands: tags -1 + pending Bug #79 [src:ois] ois: library transition needed when GCC 5 is the default Added tag(s) pending. -- 79: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=79 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 791112 is forwarded to https://release.debian.org/transitions/html/auto-libcrypto++.html
Processing commands for cont...@bugs.debian.org: forwarded 791112 https://release.debian.org/transitions/html/auto-libcrypto++.html Bug #791112 [src:libcrypto++] libcrypto++: library transition may be needed when GCC 5 is the default Set Bug forwarded-to-address to 'https://release.debian.org/transitions/html/auto-libcrypto++.html'. thanks Stopping processing here. Please contact me if you need assistance. -- 791112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#791173: libstxxl: library transition may be needed when GCC 5 is the default
Thanks, Bas. Agreed and accepted. Will upload in a few moments. Feel free to join debian-science group on Alioth, I will accept your request, if you want. Best regards Anton 2015-08-23 19:34 GMT+02:00 Sebastiaan Couwenberg sebas...@xs4all.nl: My proposed changes are attached because cannot push to debian-science, I think that should be used instead of Conflicts/Replaces as Ubuntu has done.
Processed: unblock 793593 with 791112
Processing commands for cont...@bugs.debian.org:
unblock 793593 with 791112
Bug #793593 {Done: Christian Hofstaedtler z...@debian.org}
[pdns-backend-mysql] fails to remove if mysql-client is not (no longer)
installed
793593 was blocked by: 791112
793593 was not blocking any bugs.
Removed blocking bug(s) of 793593: 791112
thanks
Stopping processing here.
Please contact me if you need assistance.
--
793593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: affects 796297
Processing commands for cont...@bugs.debian.org: affects 796297 - pdns Bug #796297 [libcrypto++] libcrypto++: FTBFS on armel: DH validation suite: FAILED simple key agreement domain parameters invalid Removed indication that 796297 affects pdns thanks Stopping processing here. Please contact me if you need assistance. -- 796297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796732: cassiopee: library transition needed with GCC 5 as default
Source: cassiopee Version: 1.0.3+dfsg-2 Severity: serious Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Hi, your library exposes std::string or std::list in its public API, and therefore the library package needs to be renamed. Specifically the use of std::list in TreeNode, CassieIndexer and CassieSearch is likely to break ABI. Cheers, Julien The following is a form letter: Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150813/ Search for BEGIN GCC CXX11 in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition signature.asc Description: Digital signature
Bug#796666: NMU diff attached
On Sunday, August 23, 2015 07:24:24 PM Sebastian Ramacher wrote: Control: tags -1 + pending On 2015-08-23 13:08:04, Scott Kitterman wrote: Here's the diff I intend to upload shortly. Scott K No need to upload this NMU. A fix is already in NEW. Even better. I can solve that. Thanks, Scott K signature.asc Description: This is a digitally signed message part.
Bug#796666: marked as done (ois: library transition needed when GCC 5 is the default)
Your message dated Sun, 23 Aug 2015 19:00:13 + with message-id e1ztav3-0006rg...@franck.debian.org and subject line Bug#79: fixed in ois 1.3.0+dfsg0-6 has caused the Debian Bug report #79, regarding ois: library transition needed when GCC 5 is the default to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 79: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=79 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Subject: libois-1.3.0: libois-1.3.0 needs rebuilding using gcc-5.2 Package: libois-1.3.0 Version: 1.3.0+dfsg0-5 Severity: important Dear Maintainer, libois should be rebuilt using gcc-5.2 in a maybe new libois-1.3.0v5 package because it cannot be used to linked other dependencies such as Ogre against it due to the change of signature of std::string when using c++11. Simply deb-building the package using gcc-5.2 is sufficing to make it usable, btw. Best regards, Yohann Ferreira ---End Message--- ---BeginMessage--- Source: ois Source-Version: 1.3.0+dfsg0-6 We believe that the bug you reported is fixed in the latest version of ois, 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 796...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher sramac...@debian.org (supplier of updated ois 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, 23 Aug 2015 18:37:46 +0200 Source: ois Binary: libois-dev libois-1.3.0v5 Architecture: source amd64 Version: 1.3.0+dfsg0-6 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Sebastian Ramacher sramac...@debian.org Description: libois-1.3.0v5 - Object Oriented Input System library (C++) libois-dev - Object Oriented Input System library (C++ development headers) Closes: 723631 79 Changes: ois (1.3.0+dfsg0-6) unstable; urgency=medium . * Team upload. . [ Steve Langasek ] * Rename library packages for g++5 ABI transition. (Closes: #79) . [ Sebastian Ramacher ] * debian/control: - Bump Standards-Version. - Set Priority to optional. (Closes: #723631) Checksums-Sha1: 24066f1530392e3951a8ed25fe774124065063a4 2111 ois_1.3.0+dfsg0-6.dsc 669685423305d831c091c179ec0b6a58a2b6c5d8 7196 ois_1.3.0+dfsg0-6.debian.tar.xz c39be6ab9fe7d5c1b67798535d05b09f7a776e61 44302 libois-1.3.0v5_1.3.0+dfsg0-6_amd64.deb 675e0299d70bf7c5976dcbdf071c7aa602d9508e 80158 libois-dev_1.3.0+dfsg0-6_amd64.deb Checksums-Sha256: 1912ea6b13628b76b82328ed3ff27edcb18dcf3ae661838798400af4a81a5639 2111 ois_1.3.0+dfsg0-6.dsc c2607fe73f07356d32aa8a9d7948bdf65fe21ffcfaa21fc687b07cab6ea41658 7196 ois_1.3.0+dfsg0-6.debian.tar.xz 49de8137377301cdfb62ea30d4a6a6670c20bd243087c653fbdaa01442ffe378 44302 libois-1.3.0v5_1.3.0+dfsg0-6_amd64.deb 7f2d6aca4cc239c0226f458ee85011a41aeafd8ef6f57eea3c83790d93614b0b 80158 libois-dev_1.3.0+dfsg0-6_amd64.deb Files: 90a830ce229a4e57c2660a1fe4cb49a6 2111 libs optional ois_1.3.0+dfsg0-6.dsc acd5475ffa97bcca0b487dd3229112c5 7196 libs optional ois_1.3.0+dfsg0-6.debian.tar.xz 51f13fff3bc7446c12ee67963cb57c40 44302 libs optional libois-1.3.0v5_1.3.0+dfsg0-6_amd64.deb a3909a751477ccf03d78899cd54e7e00 80158 libdevel optional libois-dev_1.3.0+dfsg0-6_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJV2fcpAAoJEGny/FFupxmTq+gQAKZjlYfY3MXqelg8hasOvuLq /6cmaH2EtYEG3cjT8SUO+wblcL/ar16BsBD17iIKpw3m4IFOUUzJhvw1+Tpv/O59 KaJRA7Bd7SdgsfosSd5NN5/us+WI4nQIaJX2bLch5gycZFldeva2wzQzHU2kbAOc 5yCVcE2uTmTF3/9NtWB9XcymCEHRVvicOaRJ+5bZcGAROjSnFAUMj9vuN71ptLbI wmibULNekR/SJZfItEPCjiujLECcHEE7NqOixXy4V5yBQ+iUZHrPtPyUDwwQZYsm nOOSEZJA2k1xxL8/jbhXTgxJpcqMVIGlQ+xZEScuJ6flfsTNxQ4vIkcRXn18SaZV hhJK8Fcz2XU21MjMJpXeiiVR0SmerMl7uozaI83BKNVLKv/qJavniXCIjyM/JNNo 5eOsr5Njs0+CPTZvkGo+5zo6N6Qz9ummuoidh9OlmHba7afQHznPn3ro9aOdDFXL Vw8slQdKwQ/CCNn79wjNNjlAiPHpv5oj0ProfYFK88ZIhP6d4Q7Yi5dBAkl8fuXU nwIApiZ5Sa/t/MY7vjPId/6bNmFzZ9nu1J5lHryP1/uFq+Cz4FeTbcSEy8ZS6k0h RlcSqu0AAyoKepSLxrcDtCsm9PRSIDC1PcFxxOlGNGY7eRqs4aYMTpwfMY6CWgcf X6HZjDja8ytw+2FwpWok =3+pr -END PGP SIGNATUREEnd Message---
Processed: Re: Bug#795638: hnb: FTBFS under some locales
Processing control commands: tag -1 + confirmed pending Bug #795638 [src:hnb] hnb: FTBFS under some locales Added tag(s) confirmed and pending. -- 795638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796592: marked as done (gimagereader does not launch)
Your message dated Sun, 23 Aug 2015 14:26:21 +0200 with message-id 55d9bbed.5080...@inventati.org and subject line Re: Bug#796592: gimagereader does not launch has caused the Debian Bug report #796592, regarding gimagereader does not launch 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.) -- 796592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gimagereader Version: 3.1-1 Severity: grave Tags: stretch Konsole output -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-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 Init: systemd (via /run/systemd/system) Versions of packages gimagereader depends on: ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2 ii libc62.19-19 ii libcairomm-1.0-1 1.10.0-1.1 ii libgcc1 1:5.1.1-14 ii libglib2.0-0 2.44.1-1.1 ii libglibmm-2.4-1c2a 2.44.0-1 ii libgomp1 5.1.1-14 ii libgtk-3-0 3.16.6-1 ii libgtkmm-3.0-1 3.16.0-1 ii libgtksourceviewmm-3.0-0 3.12.0-1 ii libgtkspellmm-3.0-0 3.0.3+dfsg-1 ii libpangomm-1.4-1 2.36.0-1 ii libpoppler-glib8 0.26.5-3 ii libsane 1.0.24-13 ii libsigc++-2.0-0c2a 2.4.1-1 ii libstdc++6 5.1.1-14 ii libtesseract33.04.00-5 gimagereader recommends no packages. gimagereader suggests no packages. -- no debconf information Dear maintainer: I just installed package, rebooted and it does not launch. I tried to open a scanned image with it and it starts launch but then it fails. I need this package. Please help. Thank you. -- *Carlos Kosloff* ---End Message--- ---BeginMessage--- Duplicate, see #794489 - closed. signature.asc Description: OpenPGP digital signature ---End Message---
Bug#796417: marked as done (xcffib: FTBFS: module 'xcffib' from [..] is not a python function)
Your message dated Sun, 23 Aug 2015 15:26:05 +
with message-id e1ztx9p-0004o4...@franck.debian.org
and subject line Bug#796417: fixed in xcffib 0.3.6-1
has caused the Debian Bug report #796417,
regarding xcffib: FTBFS: module 'xcffib' from [..] is not a python function
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.)
--
796417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: xcffib
Version: 0.3.4-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
xcffib fails to build from source in unstable/amd64:
[..]
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:170: cd
/tmp/buildd/xcffib-0.3.4/.pybuild/pythonX.Y_2.7/build; python2.7 -m
nose --with-doctest
E
==
ERROR: test suite for module 'xcffib' from
'/tmp/buildd/xcffib-0.3.4/.pybuild/pythonX.Y_2.7/build/xcffib/__init__.py'
--
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/nose/suite.py, line 209, in
run
self.setUp()
File /usr/lib/python2.7/dist-packages/nose/suite.py, line 292, in
setUp
self.setupContext(ancestor)
File /usr/lib/python2.7/dist-packages/nose/suite.py, line 315, in
setupContext
try_run(context, names)
File /usr/lib/python2.7/dist-packages/nose/util.py, line 466, in
try_run
(name, obj))
TypeError: Attribute setup of module 'xcffib' from
'/tmp/buildd/xcffib-0.3.4/.pybuild/pythonX.Y_2.7/build/xcffib/__init__.py'
is not a python function. Only functions or callables may be used as
fixtures.
--
Ran 0 tests in 6.469s
FAILED (errors=1)
E: pybuild pybuild:262: test: plugin distutils failed with: exit
code=1: cd /tmp/buildd/xcffib-0.3.4/.pybuild/pythonX.Y_2.7/build;
python2.7 -m nose --with-doctest
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7
--dir . returned exit code 13
debian/rules:14: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build gave error exit status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/xcffib_0.3.4-1.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Aug 21 05:22:14 GMT+12 2015
I: pbuilder-time-stamp: 1440177734
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (= 9), dh-python, pkg-config, ghc, xcb-proto,
libxcb-render0-dev, libxcb1-dev, cabal-install, libghc-xcb-types-dev (=
0.7.0), libghc-language-python-dev (= 0.4.0), libghc-split-dev,
libghc-optparse-applicative-dev (= 0.5), libghc-filemanip-dev, libghc-mtl-dev
(= 2.1), libghc-test-framework-hunit-dev, libghc-attoparsec-dev,
python-setuptools, python3-setuptools, python-autopep8, python-all,
python3-all, python-all-dev, python3-all-dev, python-nose, xvfb, x11-apps,
python-flake8, python-six, python3-six, python-cffi (= 0.8.2), python3-cffi
(= 0.8.2), libxcb1
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 files and directories currently installed.)
Preparing to unpack
Bug#796715: coinor-osi: library transition needed with GCC 5 as default
Source: coinor-osi Version: 0.106.9-1 Severity: serious Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Hi, your library exposes std::string or std::list in its public API, and therefore the library package needs to be renamed. Cheers, Julien The following is a form letter: Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150813/ Search for BEGIN GCC CXX11 in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition signature.asc Description: Digital signature
Processed: severity of 796716 is serious, severity of 796719 is serious, severity of 796721 is serious
Processing commands for cont...@bugs.debian.org: severity 796716 serious Bug #796716 [src:urdfdom] urdfdom: library transition needed with GCC 5 as default Severity set to 'serious' from 'normal' severity 796719 serious Bug #796719 [src:tntdb] tntdb: library transition needed with GCC 5 as default Severity set to 'serious' from 'normal' severity 796721 serious Bug #796721 [src:tntnet] tntnet: library transition needed with GCC 5 as default Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 796716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796716 796719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796719 796721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#791173: libstxxl: library transition may be needed when GCC 5 is the default
On 23-08-15 19:15, Simon McVittie wrote: On 23/08/15 16:10, Sebastiaan Couwenberg wrote: On 23-08-15 16:59, Simon McVittie wrote: The SONAME bump option was only really meant to be taken if the library had an upstream SONAME bump pending anyway (for instance icu and boost went this route). If there is not a SONAME change already in the pipeline, you should do the v5 rename instead. My NMUs of gtkmm2.4, gtkmm3.0, atlas-cpp, bullet etc. should make a reasonable template for how this works. I have the packaging for the libstxll v5 rename mostly ready in my local git, I can push this to Alioth and/or NMU it to DELAYED/2 if you want. Regardless of whether you NMU, please compare what you have done with the Ubuntu patch at http://patches.ubuntu.com/libs/libstxxl/libstxxl_1.4.1-1ubuntu1.patch (you'll probably find it ended up identical), and send a diff against current unstable to this bug. Anton has pushed his changes already, but so far I've not seen the upload yet. That's a good thing because the Breaks/Replaces needs to use a version constraint: Breaks: libstxxl1 ( 1.4.1-2~) Replaces: libstxxl1 ( 1.4.1-2~) Ubuntu uses Conflicts/Replaces without a version constraint. And bothered to rename the -dbg package too, which neither I nor Anton have done. My proposed changes are attached because cannot push to debian-science, I think that should be used instead of Conflicts/Replaces as Ubuntu has done. If you've done the work already, and if all the library build-deps either don't need a transition or have already started theirs, then I would personally say you might as well NMU to an appropriate DELAYED queue. This overall transition has broken unstable for 3 weeks already, during which lots of packages are either uninstallable or non-functional, and basically no C++ can migrate to testing; the sooner we can get through it and have our distribution back, the better. It doesn't look like any of the libstxxl build dependencies are a blocker, so I do think we need to go ahead with an upload to unstable soon. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 0001-Use-versioned-Breaks-Replaces.patch Description: application/pgp-encrypted
Bug#796734: monotone: FTBFS in sid (test suite failure)
Source: monotone Version: 1.1-4 Severity: serious Justification: fails to build from source (but built successfully in the past) Tags: sid stretch Hi, your package no longer builds on the buildds, see the logs at https://buildd.debian.org/status/package.php?p=monotone test/unit/tests/merge_3way.cc:20:12: error: 'std::cerr' has not been declared using std::cerr; ^ test/unit/tests/merge_3way.cc:21:12: error: 'std::cout' has not been declared using std::cout; ^ test/unit/tests/merge_3way.cc: In function 'void dump_incorrect_merge(const std::vectorstd::__cxx11::basic_stringchar , const std::vectorstd::__cxx11::basic_stringchar , const string)': test/unit/tests/merge_3way.cc:37:7: error: 'cerr' was not declared in this scope cerr bad merge: i [ prefix ]\t; ^ make[5]: *** [test/unit/tests/merge_3way.o] Error 1 Cheers, Julien signature.asc Description: Digital signature
Bug#771102: upstream license violation
Hi Evan, I have not received a response from you regarding this bug since it was submitted last year. Are you still maintaining abduco in Debian? -- Ned T. Crigler
Bug#796725: libkexiv2: FTBFS with GCC 5
Source: libkexiv2 Version: 4:4.14.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Tags: sid stretch Your symbols file needs to be updated for g++ 5, it seems at least _ZNK11KExiv2Iface6KExiv27Private23detectEncodingAndDecodeERKSs was exported and was renamed due to the std::string changes. See the build log at https://people.debian.org/~doko/logs/gcc5-20150813/archive-gcc-08-13-2015/libkexiv2_4.14.2-1_unstable_gcc5.log Cheers, Julien signature.asc Description: Digital signature
Bug#791173: libstxxl: library transition may be needed when GCC 5 is the default
On 23-08-15 19:59, Anton Gladky wrote: Thanks, Bas. Agreed and accepted. Will upload in a few moments. Thanks. I'll finish up the new osrm revision to close its RC bug after libstxxl hits the mirrors. Feel free to join debian-science group on Alioth, I will accept your request, if you want. Thanks for the offer, I may join debian-science later. For now I'm happy to remain just the GIS guy, although we should consider moving hdf5 and netcdf from the Debian GIS team to Debian Science, -science seems a better fit (but may not have the manpower). Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#796738: ruby-httpclient: FTBFS: Address already in use - bind(2) for 127.0.0.1:50000
Source: ruby-httpclient
Version: 2.3.3-3.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
ruby-httpclient fails to build from source in unstable/amd64. Port 5
is not really in use; I suspect that the ruby2.2 tests fail because
the server has not been cleaned up correctly from the ruby2.1 tests that
run just before it.
[..]
/usr/lib/ruby/2.2.0/socket.rb:459:in `tcp_server_sockets'
/usr/lib/ruby/2.2.0/webrick/utils.rb:70:in `create_listeners'
/usr/lib/ruby/2.2.0/webrick/ssl.rb:152:in `listen'
/usr/lib/ruby/2.2.0/webrick/server.rb:114:in `initialize'
/usr/lib/ruby/2.2.0/webrick/httpserver.rb:45:in `initialize'
/tmp/buildd/ruby-httpclient-2.3.3/test/test_httpclient.rb:1599:in
`new'
/tmp/buildd/ruby-httpclient-2.3.3/test/test_httpclient.rb:1599:in
`setup_server'
/tmp/buildd/ruby-httpclient-2.3.3/test/test_httpclient.rb:11:in
`setup'
===
..E
===
Error: test_set_default_paths(TestSSL): Errno::EADDRINUSE: Address
already in use - bind(2) for 127.0.0.1:5
/usr/lib/ruby/2.2.0/socket.rb:206:in `bind'
/usr/lib/ruby/2.2.0/socket.rb:206:in `listen'
/usr/lib/ruby/2.2.0/socket.rb:461:in `block in tcp_server_sockets'
/usr/lib/ruby/2.2.0/socket.rb:232:in `each'
/usr/lib/ruby/2.2.0/socket.rb:232:in `foreach'
/usr/lib/ruby/2.2.0/socket.rb:459:in `tcp_server_sockets'
/usr/lib/ruby/2.2.0/webrick/utils.rb:70:in `create_listeners'
/usr/lib/ruby/2.2.0/webrick/ssl.rb:152:in `listen'
/usr/lib/ruby/2.2.0/webrick/server.rb:114:in `initialize'
/usr/lib/ruby/2.2.0/webrick/httpserver.rb:45:in `initialize'
/tmp/buildd/ruby-httpclient-2.3.3/test/test_ssl.rb:189:in `new'
/tmp/buildd/ruby-httpclient-2.3.3/test/test_ssl.rb:189:in
`setup_server'
/tmp/buildd/ruby-httpclient-2.3.3/test/test_ssl.rb:14:in `setup'
===
..
Finished in 18.601867468 seconds.
--
184 tests, 586 assertions, 1 failures, 42 errors, 0 pendings, 0
omissions, 0 notifications
76.6304% passed
--
9.89 tests/s, 31.50 assertions/s
ERROR: Test ruby2.2 failed. Exiting.
dh_auto_install: dh_ruby --install
/tmp/buildd/ruby-httpclient-2.3.3/debian/ruby-httpclient returned exit
code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/ruby-httpclient_2.3.3-3.1.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Aug 21 23:35:09 GMT+12 2015
I: pbuilder-time-stamp: 1440243309
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (= 7.0.50~), gem2deb (= 0.2.7~)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring
anyway as you requested:
pbuilder-satisfydepends-dummy depends on gem2deb (= 0.2.7~); however:
Package gem2deb is not installed.
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
ca-certificates{a} devscripts{a} dh-python{a} gem2deb{a}
Processed: your mail
Processing commands for cont...@bugs.debian.org:
tags 793041 pending
Bug #793041 [openexr] Invalid configuration `aarch64-linux-gnu': machine
`aarch64' not recognized
Added tag(s) pending.
tags 791478 pending
Bug #791478 [src:openexr] testOptimizedInterleavePatterns.cpp:238
Bug #793103 [src:openexr] error reading back channel B pixel 96,-62 got -nan
expected -nan
Added tag(s) pending.
Added tag(s) pending.
tags 782098 pending
Bug #782098 [openexr,libopenexr-dev] openexr, libopenexr-dev: directory vs.
symlink conflict: /usr/share/doc/{openexr, libopenexr-dev} -
/usr/share/doc/libopenexr6
Added tag(s) pending.
tags 782106 pending
Bug #782106 [openexr-doc] openexr-doc: fails to upgrade from 'sid' - trying to
overwrite /usr/share/doc-base/openexr-tech-intro
Added tag(s) pending.
tags 793040 pending
Bug #793040 [openexr] Assertion `relError .1' failed.
Added tag(s) pending.
End of message, stopping processing here.
Please contact me if you need assistance.
--
782098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782098
782106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782106
791478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791478
793040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793040
793041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793041
793103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#790984: blitz++: library transition may be needed when GCC 5 is the default
Control: tags 790984 + patch pending
On Tue, 11 Aug 2015 at 00:39:53 +0200, Julien Cristau wrote:
blitz::Timer::ivar_ gets renamed as part of the rebuild. While that
looks like a private variable, it seems to be accessed by inlined
methods, so I think that means libblitz0ldbl needs a rename.
I have uploaded a NMU to DELAYED/2. The only rdep is odin, which builds
successfully against the NMU.
Patch attached. Please let me know if I should reschedule or cancel this
(although this bug has now been RC for almost 2 weeks with no response,
so that seems somewhat unlikely).
Regards,
S
diffstat for blitz++-0.10 blitz++-0.10
changelog |8
control |8
libblitz0.README.Debian | 20
libblitz0ldbl.dirs |1 -
libblitz0ldbl.docs |1 -
libblitz0ldbl.lintian-overrides |5 -
libblitz0v5.README.Debian | 20
libblitz0v5.dirs|1 +
libblitz0v5.docs|1 +
rules |4 ++--
10 files changed, 36 insertions(+), 33 deletions(-)
diff -Nru blitz++-0.10/debian/changelog blitz++-0.10/debian/changelog
--- blitz++-0.10/debian/changelog 2014-12-02 21:37:09.0 +
+++ blitz++-0.10/debian/changelog 2015-08-23 14:46:55.0 +0100
@@ -1,3 +1,11 @@
+blitz++ (1:0.10-3.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename library to libblitz0v5 for the libstdc++ transition
+(Closes: #790984)
+
+ -- Simon McVittie s...@debian.org Sun, 23 Aug 2015 14:46:54 +0100
+
blitz++ (1:0.10-3.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru blitz++-0.10/debian/control blitz++-0.10/debian/control
--- blitz++-0.10/debian/control 2014-12-02 21:36:27.0 +
+++ blitz++-0.10/debian/control 2015-08-23 12:22:11.0 +0100
@@ -20,15 +20,15 @@
Vcs-Svn: svn://anonscm.debian.org/debian-science/packages/libblitz/trunk/
Homepage: http://oonumerics.org/blitz/
-Package: libblitz0ldbl
+Package: libblitz0v5
Architecture: any
Section: libs
Depends: ${shlibs:Depends},
${misc:Depends}
Suggests: libblitz-doc
-Conflicts: libblitz0
+Conflicts: libblitz0, libblitz0ldbl
Provides: libblitz0
-Replaces: libblitz0
+Replaces: libblitz0, libblitz0ldbl
Description: C++ template class library for scientific computing
Blitz++ offers a high level of abstraction,
but performance which rivals Fortran. The
@@ -39,7 +39,7 @@
Package: libblitz0-dev
Architecture: any
Section: libdevel
-Depends: libblitz0ldbl (= ${binary:Version}),
+Depends: libblitz0v5 (= ${binary:Version}),
${misc:Depends}
Recommends: libblitz-doc
Conflicts: libblitz-dev,
diff -Nru blitz++-0.10/debian/libblitz0ldbl.dirs blitz++-0.10/debian/libblitz0ldbl.dirs
--- blitz++-0.10/debian/libblitz0ldbl.dirs 2008-05-29 07:21:53.0 +0100
+++ blitz++-0.10/debian/libblitz0ldbl.dirs 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-usr/lib
diff -Nru blitz++-0.10/debian/libblitz0ldbl.docs blitz++-0.10/debian/libblitz0ldbl.docs
--- blitz++-0.10/debian/libblitz0ldbl.docs 2008-05-29 07:21:53.0 +0100
+++ blitz++-0.10/debian/libblitz0ldbl.docs 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-README
diff -Nru blitz++-0.10/debian/libblitz0ldbl.lintian-overrides blitz++-0.10/debian/libblitz0ldbl.lintian-overrides
--- blitz++-0.10/debian/libblitz0ldbl.lintian-overrides 2008-05-29 07:21:53.0 +0100
+++ blitz++-0.10/debian/libblitz0ldbl.lintian-overrides 1970-01-01 01:00:00.0 +0100
@@ -1,5 +0,0 @@
-# Development of libblitz seems to have been stalled and thus it seems
-# to make less sense to add a version to the package name if there are
-# no new versions to expect. This will change until new versions show
-# up on the horizont
-libblitz0ldbl: package-name-doesnt-match-sonames libblitz0
diff -Nru blitz++-0.10/debian/libblitz0.README.Debian blitz++-0.10/debian/libblitz0.README.Debian
--- blitz++-0.10/debian/libblitz0.README.Debian 2008-05-29 07:21:53.0 +0100
+++ blitz++-0.10/debian/libblitz0.README.Debian 1970-01-01 01:00:00.0 +0100
@@ -1,20 +0,0 @@
-blitz++ for DEBIAN
-
-This is the blitz++ (c++) numerical library for Debian.
-
-In some places, the package is called blitz, in others blitz++.
-For instance, the headers are in /usr/include/blitz .
-
-If you have installed the libblitz-doc package you will
-find some examples in /usr/share/doc/libblitz-doc/examples.
-There is a Makefile.examples to build and test all examples.
-
-The benchmark directory has not been installed here, because it
-tests blitz++ against FORTRAN 90, which is not available for debian.
-
-Packaged by
-John Lapeyre lape...@physics.arizona.edu Thu, 10 Sep 1998 15:58:31 -0700
-Took over by
-Konstantinos Margaritis mar...@debian.org Thu, 20 Apr 2000 12:45:08 +0300
-Group maintained since
-Andreas Tille ti...@debian.org Sun, 29 Apr 2007 17:06:38 +0200
diff -Nru
Processed: Re: Bug#790984: blitz++: library transition may be needed when GCC 5 is the default
Processing control commands: tags 790984 + patch pending Bug #790984 [src:blitz++] blitz++: library transition may be needed when GCC 5 is the default Added tag(s) pending and patch. -- 790984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#791173: libstxxl: library transition may be needed when GCC 5 is the default
Processing commands for cont...@bugs.debian.org: tags 791173 +pending Bug #791173 [src:libstxxl] libstxxl: library transition may be needed when GCC 5 is the default Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 791173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 791127, user bugsqu...@qa.debian.org, usertagging 791127
Processing commands for cont...@bugs.debian.org: tags 791127 + pending Bug #791127 [src:libgtksourceviewmm] libgtksourceviewmm: transition to libgtksourceviewmm-3.0-0v5 needed Added tag(s) pending. user bugsqu...@qa.debian.org Setting user to bugsqu...@qa.debian.org (was s...@debian.org). usertags 791127 + s...@debian.org There were no usertags set. Usertags are now: s...@debian.org. thanks Stopping processing here. Please contact me if you need assistance. -- 791127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#791173: libstxxl: library transition may be needed when GCC 5 is the default
tags 791173 +pending thanks Hi Sebastiaan thanks for you effort, but I have just pushed it already. Thanks Anton 2015-08-23 17:10 GMT+02:00 Sebastiaan Couwenberg sebas...@xs4all.nl: On 23-08-15 16:59, Simon McVittie wrote: The SONAME bump option was only really meant to be taken if the library had an upstream SONAME bump pending anyway (for instance icu and boost went this route). If there is not a SONAME change already in the pipeline, you should do the v5 rename instead. My NMUs of gtkmm2.4, gtkmm3.0, atlas-cpp, bullet etc. should make a reasonable template for how this works. I have the packaging for the libstxll v5 rename mostly ready in my local git, I can push this to Alioth and/or NMU it to DELAYED/2 if you want. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#796647: python-sptest: FTBFS: Missing Build-Depends on python
Source: python-sptest
Version: 0.2.1-2.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
python-sptest fails to build from source in unstable/amd64 due to
missing Build-Depends on python (dh-python Depends on python3):
[..]
debian/rules build
python setup.py build
make: python: Command not found
debian/rules:15: recipe for target 'build' failed
make: *** [build] Error 127
dpkg-buildpackage: error: debian/rules build gave error exit status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/python-sptest_0.2.1-2.1.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sat Aug 22 19:24:17 GMT+12 2015
I: pbuilder-time-stamp: 1440314657
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: dh-python, debhelper (= 5)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring
anyway as you requested:
pbuilder-satisfydepends-dummy depends on dh-python; however:
Package dh-python is not installed.
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
dh-python{a} libexpat1{a} libmpdec2{a} libpython3-stdlib{a}
libpython3.4-minimal{a} libpython3.4-stdlib{a} libssl1.0.0{a}
mime-support{a} python3{a} python3-minimal{a} python3.4{a}
python3.4-minimal{a}
0 packages upgraded, 12 newly installed, 0 to remove and 0 not upgraded.
Need to get 5794 kB of archives. After unpacking 26.9 MB will be used.
Writing extended state information...
Get: 1 http://ftp.de.debian.org/debian/ unstable/main libmpdec2 amd64 2.4.1-1
[85.7 kB]
Get: 2 http://ftp.de.debian.org/debian/ unstable/main libssl1.0.0 amd64
1.0.2d-1 [1274 kB]
Get: 3 http://ftp.de.debian.org/debian/ unstable/main libpython3.4-minimal
amd64 3.4.3-8 [495 kB]
Get: 4 http://ftp.de.debian.org/debian/ unstable/main mime-support all 3.59
[36.4 kB]
Get: 5 http://ftp.de.debian.org/debian/ unstable/main libpython3.4-stdlib amd64
3.4.3-8 [2057 kB]
Get: 6 http://ftp.de.debian.org/debian/ unstable/main libexpat1 amd64 2.1.0-7
[80.0 kB]
Get: 7 http://ftp.de.debian.org/debian/ unstable/main python3.4-minimal amd64
3.4.3-8 [1401 kB]
Get: 8 http://ftp.de.debian.org/debian/ unstable/main python3-minimal amd64
3.4.3-4 [34.7 kB]
Get: 9 http://ftp.de.debian.org/debian/ unstable/main python3.4 amd64 3.4.3-8
[219 kB]
Get: 10 http://ftp.de.debian.org/debian/ unstable/main libpython3-stdlib amd64
3.4.3-4 [18.1 kB]
Get: 11 http://ftp.de.debian.org/debian/ unstable/main dh-python all 2.20150728
[71.3 kB]
Get: 12 http://ftp.de.debian.org/debian/ unstable/main python3 amd64 3.4.3-4
[21.1 kB]
Fetched 5794 kB in 0s (24.1 MB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libmpdec2:amd64.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading
Bug#796400: [pkg-go] Bug#796400: golang-github-jacobsa-ratelimit: Non-determistically FTBFS due to unreliable timing in tests
Aaron, could you take a look at this problem please? It seems to me like this is a shortcoming of your tests, unrelated to Debian. On Fri, Aug 21, 2015 at 8:44 PM, Chris Lamb la...@debian.org wrote: Source: golang-github-jacobsa-ratelimit Version: 0.0~git20150723.0.2ca5e0c-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, golang-github-jacobsa-ratelimit's testsuite appears to use method timing/benchmarking in such a way that it will non-deterministically FTBFS: throttle_test.go: expected := smallerRateHz * (float64(perCaseDuration) / float64(time.Second)) For example: [..] go test -v github.com/jacobsa/ratelimit === RUN TestThrottle [--] Running tests from ThrottleTest [ RUN ] ThrottleTest.IntegrationTest throttle_test.go:202: Expected: greater than 135, and less than 165 Actual: 88 Test case 0. expected: 150.00 throttle_test.go:202: Expected: greater than 180, and less than 220.03 Actual: 138 Test case 1. expected: 200.00 throttle_test.go:202: Expected: greater than 180, and less than 220.03 Actual: 163 Test case 2. expected: 200.00 [ FAILED ] ThrottleTest.IntegrationTest (6.031585896s) [--] Finished with tests from ThrottleTest [--] Running tests from ThrottledReaderTest [ RUN ] ThrottledReaderTest.CallsThrottle [ OK ] ThrottledReaderTest.CallsThrottle [ RUN ] ThrottledReaderTest.ThrottleReturnsError [ OK ] ThrottledReaderTest.ThrottleReturnsError [ RUN ] ThrottledReaderTest.CallsWrapped [ OK ] ThrottledReaderTest.CallsWrapped [ RUN ] ThrottledReaderTest.WrappedReturnsError [ OK ] ThrottledReaderTest.WrappedReturnsError [ RUN ] ThrottledReaderTest.WrappedReturnsEOF [ OK ] ThrottledReaderTest.WrappedReturnsEOF [ RUN ] ThrottledReaderTest.WrappedReturnsFullRead [ OK ] ThrottledReaderTest.WrappedReturnsFullRead [ RUN ] ThrottledReaderTest.WrappedReturnsShortRead_CallsAgain [ OK ] ThrottledReaderTest.WrappedReturnsShortRead_CallsAgain [ RUN ] ThrottledReaderTest.WrappedReturnsShortRead_SecondReturnsError [ OK ] ThrottledReaderTest.WrappedReturnsShortRead_SecondReturnsError [ RUN ] ThrottledReaderTest.WrappedReturnsShortRead_SecondReturnsEOF [ OK ] ThrottledReaderTest.WrappedReturnsShortRead_SecondReturnsEOF [ RUN ] ThrottledReaderTest.WrappedReturnsShortRead_SecondSucceedsInFull [ OK ] ThrottledReaderTest.WrappedReturnsShortRead_SecondSucceedsInFull [ RUN ] ThrottledReaderTest.ReadSizeIsAboveThrottleCapacity [ OK ] ThrottledReaderTest.ReadSizeIsAboveThrottleCapacity [--] Finished with tests from ThrottledReaderTest [--] Running tests from TokenBucketTest [ RUN ] TokenBucketTest.CarefulAccounting [ OK ] TokenBucketTest.CarefulAccounting [--] Finished with tests from TokenBucketTest --- FAIL: TestThrottle (6.03s) === RUN TestThrottledReader --- PASS: TestThrottledReader (0.00s) === RUN TestTokenBucket --- PASS: TestTokenBucket (0.00s) FAIL exit status 1 FAILgithub.com/jacobsa/ratelimit6.074s dh_auto_test: go test -v github.com/jacobsa/ratelimit returned exit code 1 debian/rules:6: recipe for target 'build' failed make: *** [build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/golang-github-jacobsa-ratelimit_0.0~git20150723.0.2ca5e0c-1.build2.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ___ Pkg-go-maintainers mailing list pkg-go-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers -- Best regards, Michael
Bug#796669: tix compiled against tk-8.5 instead of tk-8.6
Package: tix Version: 8.4.3-5 Severity: grave Justification: renders package unusable Dear Maintainer, it looks like tix in Jessie is compiled against tk-8.5 whereas the default version is tk-8.6 which will make it completely unusable for applications written in Perl, Python or Ruby and probably break any existing Tcl/Tk app that uses Tix, unless it explicitely requests to use wish8.5 . A brief example that shows the problem: $ wish8.6 % package require Tix 8.4.3 % tixFileSelectBox .f ..f % pack .f % Speicherzugriffsfehler # (i.e. segmentation fault) $ wish8.5 % package require Tix 8.4.3 % tixFileSelectBox .f ..f % pack .f # it works! Regards Michael -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tix depends on: ii libc62.19-18 ii libx11-6 2:1.6.2-3 ii tcl [tclsh] 8.6.0+8 tix recommends no packages. tix suggests no packages. -- no debconf information
Bug#778178: ping
Pinging bug to prevent auto-removal from testing. Auto-removal achieves nothing here - the fix is for rebuilding with the v5-ed libxapian-dev, and the version of xapian-omega in unstable is fixed and ready to migrate when the newer xapian-core packages are able to. Cheers, Olly
Bug#782098: marked as done (openexr, libopenexr-dev: directory vs. symlink conflict: /usr/share/doc/{openexr, libopenexr-dev} - /usr/share/doc/libopenexr6)
Your message dated Sun, 23 Aug 2015 15:22:37 +
with message-id e1ztx6t-0003pd...@franck.debian.org
and subject line Bug#782098: fixed in openexr 2.2.0-2
has caused the Debian Bug report #782098,
regarding openexr, libopenexr-dev: directory vs. symlink conflict:
/usr/share/doc/{openexr, libopenexr-dev} - /usr/share/doc/libopenexr6
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.)
--
782098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: openexr,libopenexr-dev
Version: 1.6.1-9
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package does not
bahave sanely.
Your package ships:
drwxr-xr-x root/root 0 2015-01-28 13:58 ./usr/share/doc/
drwxr-xr-x root/root 0 2015-01-28 13:58 ./usr/share/doc/openexr/
-rw-r--r-- root/root 9585 2007-10-09 21:30
./usr/share/doc/openexr/changelog.gz
-rw-r--r-- root/root 4092 2015-01-28 13:45
./usr/share/doc/openexr/changelog.Debian.gz
-rw-r--r-- root/root 2003 2011-02-12 16:40
./usr/share/doc/openexr/copyright
but openexr.postinst does:
if [ ! -L /usr/share/doc/openexr ]
then
rm -rf /usr/share/doc/openexr
ln -s /usr/share/doc/libopenexr6 /usr/share/doc/openexr
fi
From the attached log (usually somewhere in the middle...):
0m32.7s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/openexr/changelog.Debian.gz (openexr) !=
/usr/share/doc/libopenexr6/changelog.Debian.gz (libopenexr6:amd64)
/usr/share/doc/openexr - /usr/share/doc/libopenexr6
/usr/share/doc/openexr/changelog.gz (openexr) !=
/usr/share/doc/libopenexr6/changelog.gz (libopenexr6:amd64)
/usr/share/doc/openexr - /usr/share/doc/libopenexr6
/usr/share/doc/openexr/copyright (openexr) !=
/usr/share/doc/libopenexr6/copyright (libopenexr6:amd64)
/usr/share/doc/openexr - /usr/share/doc/libopenexr6
0m33.3s ERROR: FAIL: debsums reports modifications inside the chroot:
/usr/share/doc/openexr/changelog.Debian.gz
Same for libopenexr-dev:
0m39.0s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/libopenexr-dev/changelog.Debian.gz (libopenexr-dev) !=
/usr/share/doc/libopenexr6/changelog.Debian.gz (libopenexr6:amd64)
/usr/share/doc/libopenexr-dev - /usr/share/doc/libopenexr6
/usr/share/doc/libopenexr-dev/changelog.gz (libopenexr-dev) !=
/usr/share/doc/libopenexr6/changelog.gz (libopenexr6:amd64)
/usr/share/doc/libopenexr-dev - /usr/share/doc/libopenexr6
/usr/share/doc/libopenexr-dev/copyright (libopenexr-dev) !=
/usr/share/doc/libopenexr6/copyright (libopenexr6:amd64)
/usr/share/doc/libopenexr-dev - /usr/share/doc/libopenexr6
You'll need to use
dpkg-maintscript-helper symlink_to_dir ...
to clean up the wrong symlinks properly.
cheers,
Andreas
openexr_1.6.1-9.log.gz
Description: application/gzip
---End Message---
---BeginMessage---
Source: openexr
Source-Version: 2.2.0-2
We believe that the bug you reported is fixed in the latest version of
openexr, 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 782...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mathieu Malaterre ma...@debian.org (supplier of updated openexr package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 23 Aug 2015 15:22:44 +0200
Source: openexr
Binary: openexr openexr-doc libopenexr-dev libopenexr22
Architecture: source all
Version: 2.2.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian PhotoTools Maintainers
pkg-phototools-de...@lists.alioth.debian.org
Changed-By: Mathieu Malaterre ma...@debian.org
Description:
libopenexr-dev - development files for the OpenEXR image library
libopenexr22 - runtime files for the OpenEXR image library
openexr- command-line tools for the OpenEXR image format
openexr-doc - documentation and examples for the OpenEXR image format
Closes: 782098 791478 793040 793041
Changes:
openexr (2.2.0-2) experimental; urgency=medium
.
[ Andreas Beckmann ]
* openexr-doc: add missing Replaces: openexr ( 1.6.1-9)
Bug#796600: libgtkmm-3.0-doc: Embedded copy of jquery without source or copyright mention
Am 23.08.2015 um 01:38 schrieb Luke Faraone: Package: libgtkmm-3.0-doc Version: 3.14.0-1 Severity: serious Justification: DFSG Hello, The upstream source tarball contains docs/reference/html/jquery.js , which is included in the binary package libgtkmm-3.0-doc. However, no source code for this copy of jQuery is included, nor is the minified version included rebuilt. That really is a doxygen issue, that file is coming from that tool. You should file that issue against doxygen and get this fixed upstream. Working around that in packages using doxygen looks like the wrong approach to me. -- 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
Processed: Re: Bug#779803: smuxi performs autoconnect on first startup
Processing control commands: severity -1 grave Bug #779803 [smuxi] smuxi performs autoconnect on first startup Severity set to 'grave' from 'normal' tag -1 security Bug #779803 [smuxi] smuxi performs autoconnect on first startup Added tag(s) security. -- 779803: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779803 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 791173 serious Bug #791173 [src:libstxxl] libstxxl: library transition may be needed when GCC 5 is the default Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 791173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#795638: hnb: FTBFS under some locales
Control: tag -1 + confirmed pending Hi Chris, Chris Lamb wrote: hnb fails to build from source on unstable/amd64 under some locales (eg. LANG=fr_CH.UTF-8): Thanks for the bug report. Will upload a fix soon-ish. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#796120: marked as done (texlive-xetex: fails to create document that worked previously: xdvipdfmx:fatal: Parsing charstring failed: (status=-1, stack=0))
Your message dated Sun, 23 Aug 2015 12:39:01 + with message-id e1ztuy9-0002cm...@franck.debian.org and subject line Bug#796120: fixed in texlive-base 2015.20150823-1 has caused the Debian Bug report #796120, regarding texlive-xetex: fails to create document that worked previously: xdvipdfmx:fatal: Parsing charstring failed: (status=-1, stack=0) 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.) -- 796120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: texlive-xetex Version: 2015.20150810-1 Severity: serious Justification: FTBFS Hi, The attached document fails to build in sid or stretch, while it worked perfectly fine in jessie. FTR, this is the german version of developers-reference, causing #792009. 8 $ xelatex index.dbk.tex /dev/null xdvipdfmx:fatal: Parsing charstring failed: (status=-1, stack=0) Output file removed. 8 Thanks, Lucas -- Package-specific info: IMPORTANT INFORMATION: We will only consider bug reports concerning the packaging of TeX Live as relevant. If you have problems with combination of packages in a LaTeX document, please consult your local TeX User Group, the comp.text.tex user group, the author of the original .sty file, or any other help resource. In particular, bugs that are related to up-upstream, i.e., neither Debian nor TeX Live (upstream), but the original package authors, will be closed immediately. *** The Debian TeX Team is *not* a LaTeX Help Desk *** If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Please run your example with (pdf)latex -recorder ... (or any other program that supports -recorder) and send us the generated file with the extension .fls, it lists all the files loaded during the run and can easily explain problems induced by outdated files in your home directory. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.minimalbeispiel.de/mini-en.html (english) or http://www.minimalbeispiel.de/mini.html (german) ## minimal input file ## other files ## List of ls-R files -rw-r--r-- 1 root root 2887 Aug 17 09:38 /var/lib/texmf/ls-R lrwxrwxrwx 1 root root 29 Jun 27 16:08 /usr/share/texmf/ls-R - /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 31 Aug 10 05:16 /usr/share/texlive/texmf-dist/ls-R - /var/lib/texmf/ls-R-TEXLIVEDIST lrwxrwxrwx 1 root root 31 Aug 10 05:16 /usr/share/texlive/texmf-dist/ls-R - /var/lib/texmf/ls-R-TEXLIVEDIST ## Config files -rw-r--r-- 1 root root 1464 Jul 23 21:08 /etc/texmf/web2c/texmf.cnf -rw-r--r-- 1 root root 7121 Jul 23 21:04 /var/lib/texmf/web2c/fmtutil.cnf lrwxrwxrwx 1 root root 32 Aug 10 05:16 /usr/share/texmf/web2c/updmap.cfg - /var/lib/texmf/updmap.cfg-DEBIAN -rw-r--r-- 1 root root 4962 Aug 17 09:38 /var/lib/texmf/tex/generic/config/language.dat ## Files in /etc/texmf/web2c/ total 8 -rw-r--r-- 1 root root 283 Oct 21 2014 mktex.cnf -rw-r--r-- 1 root root 1464 Jul 23 21:08 texmf.cnf ## md5sums of texmf.d ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf 055e06548bac99958d8ab2dd1248f2b4 /etc/texmf/texmf.d/80tex4ht.cnf 1df66bc319cec731e202eaf39f5d85e1 /etc/texmf/texmf.d/96JadeTeX.cnf -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (400, 'stable'), (300, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.1.0-1-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 Init: systemd (via /run/systemd/system) Versions of packages texlive-xetex depends on: ii tex-common 6.02 ii texlive-base 2015.20150810-1 ii texlive-binaries 2015.20150524.37493-5 ii texlive-latex-base 2015.20150810-1 ii
Bug#795661: Regression in subversion
This is caused by a regression in subversion, which means it is no longer possible to pass a nonexistant path to svn_fs_is_dir() or svn_fs_is_file(). Doing so causes a segfault. I'll remove these tests for, so the package will build again. The docstring for these functions doesn't technically say that you can pass nonexistant paths to them, though crashing seems unnecessary. signature.asc Description: Digital signature
Bug#796665: mercurial-server: FTBFS: Missing Build-Depends on python
Source: mercurial-server
Version: 1.2-2.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
mercurial-server fails to build from source in unstable/amd64 due to
missing Build-Depends on python (dh-python Depends on python3):
[..]
dh clean --with python2
dh: unable to load addon python2: Can't locate
Debian/Debhelper/Sequence/python2.pm in @INC (you may need to install
the Debian::Debhelper::Sequence::python2 module) (@INC contains:
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2
/usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20
/usr/share/perl/5.20 /usr/local/lib/site_perl .) at (eval 14) line 2.
BEGIN failed--compilation aborted at (eval 14) line 2.
debian/rules:3: recipe for target 'clean' failed
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit
status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/mercurial-server_1.2-2.1.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sat Aug 22 20:31:58 GMT+12 2015
I: pbuilder-time-stamp: 1440318718
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (= 7.0.50~), dh-python, xsltproc, docbook-xsl
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring
anyway as you requested:
pbuilder-satisfydepends-dummy depends on dh-python; however:
Package dh-python is not installed.
pbuilder-satisfydepends-dummy depends on xsltproc; however:
Package xsltproc is not installed.
pbuilder-satisfydepends-dummy depends on docbook-xsl; however:
Package docbook-xsl is not installed.
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
dh-python{a} docbook-xsl{a} libexpat1{a} libmpdec2{a}
libpython3-stdlib{a} libpython3.4-minimal{a} libpython3.4-stdlib{a}
libssl1.0.0{a} libxslt1.1{a} mime-support{a} python3{a}
python3-minimal{a} python3.4{a} python3.4-minimal{a} sgml-base{a}
xml-core{a} xsltproc{a}
0 packages upgraded, 17 newly installed, 0 to remove and 0 not upgraded.
Need to get 8524 kB of archives. After unpacking 42.6 MB will be used.
Writing extended state information...
Get: 1 http://ftp.de.debian.org/debian/ unstable/main libmpdec2 amd64 2.4.1-1
[85.7 kB]
Get: 2 http://ftp.de.debian.org/debian/ unstable/main libssl1.0.0 amd64
1.0.2d-1 [1274 kB]
Get: 3 http://reproducible.alioth.debian.org/debian/ ./ libxslt1.1
1.1.28-2.0~reproducible5 [233 kB]
Get: 4 http://reproducible.alioth.debian.org/debian/ ./ xsltproc
1.1.28-2.0~reproducible5 [120 kB]
Get: 5 http://ftp.de.debian.org/debian/ unstable/main libpython3.4-minimal
amd64 3.4.3-8 [495 kB]
Get: 6 http://ftp.de.debian.org/debian/ unstable/main mime-support all 3.59
[36.4 kB]
Get: 7 http://ftp.de.debian.org/debian/ unstable/main libpython3.4-stdlib amd64
3.4.3-8 [2057 kB]
Get: 8 http://ftp.de.debian.org/debian/ unstable/main libexpat1 amd64 2.1.0-7
[80.0 kB]
Get: 9 http://ftp.de.debian.org/debian/ unstable/main python3.4-minimal amd64
3.4.3-8 [1401 kB]
Get: 10 http://ftp.de.debian.org/debian/ unstable/main python3-minimal amd64
3.4.3-4 [34.7 kB]
Get: 11 http://ftp.de.debian.org/debian/ unstable/main python3.4 amd64 3.4.3-8
[219 kB]
Get:
Bug#795638: marked as done (hnb: FTBFS under some locales)
Your message dated Sun, 23 Aug 2015 11:19:47 +
with message-id e1zttjt-0006xf...@franck.debian.org
and subject line Bug#795638: fixed in hnb 1.9.18+ds1-1
has caused the Debian Bug report #795638,
regarding hnb: FTBFS under some locales
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.)
--
795638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: hnb
Version: 1.9.18-10
Severity: serious
Justification: fails to build from source
Tags: patch
Dear Maintainer,
hnb fails to build from source on unstable/amd64 under some locales
(eg. LANG=fr_CH.UTF-8):
[..]
echo init_subsystems.c
echo void init_subsystems(){init_subsystems.c
cat *.c | grep ^\!init_ | sort | sed -e s/^\!/
/ginit_subsystems.c
cat: write error: Broken pipe
echo }init_subsystems.c
make[2]: Leaving directory '/tmp/buildd/hnb-1.9.18/src'
dh_auto_build src/hnb
make -j1
make[2]: Entering directory '/tmp/buildd/hnb-1.9.18'
(cd src;make)
make[3]: Entering directory '/tmp/buildd/hnb-1.9.18/src'
(cd libcli;make libcli.a)
make[4]: Entering directory '/tmp/buildd/hnb-1.9.18/src/libcli'
cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-I.. -Ilibcli -DHAVE_CONFIG_H -I/usr/include/ncursesw -Wdate-time
-D_FORTIFY_SOURCE=2 -c -o cli.o cli.c
cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-I.. -Ilibcli -DHAVE_CONFIG_H -I/usr/include/ncursesw -Wdate-time
-D_FORTIFY_SOURCE=2 -c -o cli_history.o cli_history.c
cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-I.. -Ilibcli -DHAVE_CONFIG_H -I/usr/include/ncursesw -Wdate-time
-D_FORTIFY_SOURCE=2 -c -o cli_tokenize.o cli_tokenize.c
ar rc libcli.a cli*.o
make[4]: Leaving directory '/tmp/buildd/hnb-1.9.18/src/libcli'
make[3]: Circular init_subsystems.c - init_subsystems.c dependency
dropped.
cc -c -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-I.. -Ilibcli -DHAVE_CONFIG_H -I/usr/include/ncursesw -Wdate-time
-D_FORTIFY_SOURCE=2 -o init_subsystems.o init_subsystems.c
init_subsystems.c:2:1: error: unknown type name ‘Binary’
Binary file (standard input) matches
^
init_subsystems.c:2:14: error: unknown type name ‘standard’
Binary file (standard input) matches
^
Makefile:9: recipe for target 'init_subsystems.o' failed
make[3]: *** [init_subsystems.o] Error 1
make[3]: Leaving directory '/tmp/buildd/hnb-1.9.18/src'
Makefile:3: recipe for target 'src/hnb' failed
make[2]: *** [src/hnb] Error 2
make[2]: Leaving directory '/tmp/buildd/hnb-1.9.18'
dh_auto_build: make -j1 returned exit code 2
debian/rules:14: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/tmp/buildd/hnb-1.9.18'
debian/rules:11: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/hnb_1.9.18-10.build2.log.gz
This is due to grep's automagic locale detection. Patch attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: samedi 25 juillet 2015, 20:53:45 (UTC+1400)
I: pbuilder-time-stamp: 1437807225
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
I: user script
/var/cache/pbuilder/build//63165/tmp/hooks/D01_modify_environment starting
I: Changing hostname to test build reproducibility
I: user script
/var/cache/pbuilder/build//63165/tmp/hooks/D01_modify_environment finished
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper
Bug#729490: marked as done (libstxxl: [PATCH] Resolve FTBFS from conditional file removal in build infrastructure)
Your message dated Sun, 23 Aug 2015 15:21:51 +0200 with message-id CALF6qJke=arnhcmgffqlltghmhngv4ikulukp-dtfecywfo...@mail.gmail.com and subject line has caused the Debian Bug report #729490, regarding libstxxl: [PATCH] Resolve FTBFS from conditional file removal in build infrastructure 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.) -- 729490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libstxxl Version: 1.3.1-5 Severity: wishlist Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu trusty ubuntu-patch Dear Maintainer, In Ubuntu 14.04, the attached patch was applied to achieve the following: * Resolve FTBFS from extra build infrastructure command Thanks for considering the patch. -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise'), (100, 'precise-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.8.0-33-generic (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 diff -Nru libstxxl-1.3.1/debian/rules libstxxl-1.3.1/debian/rules --- libstxxl-1.3.1/debian/rules 2013-08-31 07:35:20.0 -0400 +++ libstxxl-1.3.1/debian/rules 2013-11-12 17:03:51.0 -0500 @@ -31,7 +31,7 @@ rm $(CURDIR)/debian/libstxxl-dev/usr/include/bits/intel_compatibility.h rmdir $(CURDIR)/debian/libstxxl-dev/usr/include/bits #Remove duplicated changelog - rm $(CURDIR)/debian/libstxxl1/usr/share/doc/libstxxl1/CHANGELOG.gz + -rm $(CURDIR)/debian/libstxxl1/usr/share/doc/libstxxl1/CHANGELOG.gz clean:: -cd lib; \ ---End Message--- ---BeginMessage--- severity 729490 serious fixed 729490 1.4.1-1 thanks---End Message---
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 729490 serious Bug #729490 [libstxxl] libstxxl: [PATCH] Resolve FTBFS from conditional file removal in build infrastructure Severity set to 'serious' from 'wishlist' fixed 729490 1.4.1-1 Bug #729490 [libstxxl] libstxxl: [PATCH] Resolve FTBFS from conditional file removal in build infrastructure There is no source info for the package 'libstxxl' at version '1.4.1-1' with architecture '' Unable to make a source version for version '1.4.1-1' Marked as fixed in versions 1.4.1-1. thanks Stopping processing here. Please contact me if you need assistance. -- 729490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: tagging 791910, tagging 784778, tagging 789988, tagging 790526, tagging 791771, tagging 790772 ...
Processing commands for cont...@bugs.debian.org: severity 790855 serious Bug #790855 [sdrangelove] sdrangelove: FTBFS on !x86 due to unconditional use of -msse2 and immintrin.h Severity set to 'serious' from 'important' kthxbye Stopping processing here. Please contact me if you need assistance. -- 790855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#791173: libstxxl: library transition may be needed when GCC 5 is the default
On Sat, 22 Aug 2015 at 18:57:37 +0200, Sebastiaan Couwenberg wrote: It looks like libstxxl needs a transition after al. At least osrm is a reverse dependency, it cannot be built due to undefined references to stxxl::print_msg() and others. Indeed. When I closed the bug with no rdeps, don't bother, osrm was still in the NEW queue, so my check didn't find that package. On Sun, 23 Aug 2015 at 14:08:16 +0100, D Haley wrote: I have contacted upstream to see which of the two options they would prefer. My preference is for a soname bump, but this risks being out of sync with upstream. I don’t think that is a major problem, as we can fix that on a future stxxl release, but if someone is willing to correct me here, let me know. The SONAME bump option was only really meant to be taken if the library had an upstream SONAME bump pending anyway (for instance icu and boost went this route). If there is not a SONAME change already in the pipeline, you should do the v5 rename instead. My NMUs of gtkmm2.4, gtkmm3.0, atlas-cpp, bullet etc. should make a reasonable template for how this works. This ABI change is entirely about how the package is compiled *in Debian*. Upstream should not change the SONAME for this, because there is no guarantee that the change will be synchronized with the point at which other distributions make the same libstdc++ ABI transition (for instance I think Fedora may have already done it, with a mass-rebuild; and there are probably many distros that have not started yet). S
Bug#791173: libstxxl: library transition may be needed when GCC 5 is the default
On 23-08-15 16:59, Simon McVittie wrote: The SONAME bump option was only really meant to be taken if the library had an upstream SONAME bump pending anyway (for instance icu and boost went this route). If there is not a SONAME change already in the pipeline, you should do the v5 rename instead. My NMUs of gtkmm2.4, gtkmm3.0, atlas-cpp, bullet etc. should make a reasonable template for how this works. I have the packaging for the libstxll v5 rename mostly ready in my local git, I can push this to Alioth and/or NMU it to DELAYED/2 if you want. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#796649: python-popcon: FTBFS: Missing Build-Depends on python
Source: python-popcon
Version: 1.1+nmu1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
X-Debbugs-Cc: d...@debian.org
[doko in CC due to 1.1+nmu1 NMU]
Dear Maintainer,
python-popcon fails to build from source in unstable/amd64 due to
missing Build-Depends on python (dh-python Depends on python3, not
python2):
[..]
fakeroot debian/rules clean
dh clean --with python2
dh: unable to load addon python2: Can't locate
Debian/Debhelper/Sequence/python2.pm in @INC (you may need to install
the Debian::Debhelper::Sequence::python2 module) (@INC contains:
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2
/usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20
/usr/share/perl/5.20 /usr/local/lib/site_perl .) at (eval 14) line 2.
BEGIN failed--compilation aborted at (eval 14) line 2.
debian/rules:13: recipe for target 'clean' failed
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit
status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/python-popcon_1.1+nmu1.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sat Aug 22 18:30:33 GMT+12 2015
I: pbuilder-time-stamp: 1440311433
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (= 7.0.50~), dh-python
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring
anyway as you requested:
pbuilder-satisfydepends-dummy depends on dh-python; however:
Package dh-python is not installed.
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
dh-python{a} libexpat1{a} libmpdec2{a} libpython3-stdlib{a}
libpython3.4-minimal{a} libpython3.4-stdlib{a} libssl1.0.0{a}
mime-support{a} python3{a} python3-minimal{a} python3.4{a}
python3.4-minimal{a}
0 packages upgraded, 12 newly installed, 0 to remove and 0 not upgraded.
Need to get 5794 kB of archives. After unpacking 26.9 MB will be used.
Writing extended state information...
Get: 1 http://ftp.de.debian.org/debian/ unstable/main libmpdec2 amd64 2.4.1-1
[85.7 kB]
Get: 2 http://ftp.de.debian.org/debian/ unstable/main libssl1.0.0 amd64
1.0.2d-1 [1274 kB]
Get: 3 http://ftp.de.debian.org/debian/ unstable/main libpython3.4-minimal
amd64 3.4.3-8 [495 kB]
Get: 4 http://ftp.de.debian.org/debian/ unstable/main mime-support all 3.59
[36.4 kB]
Get: 5 http://ftp.de.debian.org/debian/ unstable/main libpython3.4-stdlib amd64
3.4.3-8 [2057 kB]
Get: 6 http://ftp.de.debian.org/debian/ unstable/main libexpat1 amd64 2.1.0-7
[80.0 kB]
Get: 7 http://ftp.de.debian.org/debian/ unstable/main python3.4-minimal amd64
3.4.3-8 [1401 kB]
Get: 8 http://ftp.de.debian.org/debian/ unstable/main python3-minimal amd64
3.4.3-4 [34.7 kB]
Get: 9 http://ftp.de.debian.org/debian/ unstable/main python3.4 amd64 3.4.3-8
[219 kB]
Get: 10 http://ftp.de.debian.org/debian/ unstable/main libpython3-stdlib amd64
3.4.3-4 [18.1 kB]
Get: 11 http://ftp.de.debian.org/debian/ unstable/main dh-python all 2.20150728
[71.3 kB]
Get: 12 http://ftp.de.debian.org/debian/ unstable/main python3 amd64 3.4.3-4
[21.1 kB]
Fetched 5794 kB in 0s (28.0 MB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting
Bug#796676: amarok: Amarok won't start
Package: amarok Version: 2.8.0-2.1+b2 Severity: grave Justification: renders package unusable Dear maintainer As soon as I open amarok I get: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. unnamed app(8305): Communication problem with amarok , it probably crashed. Error message was: org.freedesktop.DBus.Error.NoReply : Message did not receive a reply (timeout by message bus) KCrash: Application 'amarok' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/user/.kde/socket-PC/kdeinit4__0 I have tried reinstalling, removing and deleting ~/.kde/share/apps/amarok folder with no success -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages amarok depends on: ii amarok-common 2.8.0-2.1 ii amarok-utils 2.8.0-2.1+b2 ii kde-runtime 4:4.14.2-2 ii libaio1 0.3.110-1 ii libavcodec-ffmpeg56 7:2.7.2-1 ii libavformat-ffmpeg56 7:2.7.2-1 ii libavutil-ffmpeg547:2.7.2-1 ii libc6 2.19-19 ii libcurl3-gnutls 7.44.0-1 ii libgcrypt20 1.6.3-2 ii libgdk-pixbuf2.0-02.31.5-1 ii libgl1-mesa-glx [libgl1] 10.6.4-1 ii libglib2.0-0 2.44.1-1.1 ii libgpod4 0.8.3-1.1+b3 ii libkcmutils4 4:4.14.2-5 ii libkdecore5 4:4.14.2-5 ii libkdeui5 4:4.14.2-5 ii libkdewebkit5 4:4.14.2-5 ii libkdnssd44:4.14.2-5 ii libkfile4 4:4.14.2-5 ii libkio5 4:4.14.2-5 ii libknewstuff3-4 4:4.14.2-5 ii liblastfm11.0.8-3 ii libloudmouth1-0 1.4.3-12.1 ii libmtp9 1.1.9-3 ii libmysqlclient18 5.6.25-3 ii libnepomukcore4 4:4.14.0-1+b3 ii libofa0 0.9.3-7 ii libphonon44:4.8.3-1 ii libplasma34:4.14.2-5 ii libqjson0 0.8.1-3 ii libqt4-dbus 4:4.8.7+dfsg-1 ii libqt4-network4:4.8.7+dfsg-1 ii libqt4-opengl 4:4.8.7+dfsg-1 ii libqt4-script 4:4.8.7+dfsg-1 ii libqt4-sql4:4.8.7+dfsg-1 ii libqt4-svg4:4.8.7+dfsg-1 ii libqt4-xml4:4.8.7+dfsg-1 ii libqtcore44:4.8.7+dfsg-1 ii libqtgui4 4:4.8.7+dfsg-1 ii libqtscript4-core 0.2.0-1 ii libqtscript4-gui 0.2.0-1 ii libqtscript4-network 0.2.0-1 ii libqtscript4-sql 0.2.0-1 ii libqtscript4-uitools 0.2.0-1 ii libqtscript4-xml 0.2.0-1 ii libqtwebkit4 2.3.4.dfsg-3 ii libsolid4 4:4.14.2-5 ii libsoprano4 2.9.4+dfsg-3 ii libstdc++65.1.1-14 ii libthreadweaver4 4:4.14.2-5 ii libx11-6 2:1.6.3-1 ii libxml2 2.9.2+dfsg1-3 ii phonon4:4.8.3-1 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages amarok recommends: ii clamz0.5-2+b1 ii kio-audiocd 4:4.14.2-1 Versions of packages amarok suggests: pn amarok-doc none ii libqt4-sql-mysql 4:4.8.7+dfsg-1 pn libqt4-sql-psqlnone ii libqt4-sql-sqlite 4:4.8.7+dfsg-1 pn moodbarnone Versions of packages amarok-common depends on: ii perl 5.20.2-6 amarok-common recommends no packages. Versions of packages amarok is related to: ii phonon-backend-vlc [phonon-backend] 0.8.0-2 -- no debconf information
Bug#796711: sword: library transition is needed with GCC 5 as default
Source: sword Version: 1.7.3+dfsg-2.1 Severity: serious Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Hi, sword's public API relies on types like std::string and std::list provided by libstdc++6, meaning that libsword11 needs to be renamed. Cheers, Julien The following is a form letter: Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150813/ Search for BEGIN GCC CXX11 in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition signature.asc Description: Digital signature
Bug#668254: marked as done (bash-completion: dh_bash-completion still installs files in /etc/bash_completion)
Your message dated Sun, 23 Aug 2015 21:20:57 + with message-id e1ztchf-i3...@franck.debian.org and subject line Bug#668254: fixed in bash-completion 1:2.1-4.2 has caused the Debian Bug report #668254, regarding bash-completion: dh_bash-completion still installs files in /etc/bash_completion 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.) -- 668254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bash-completion Version: 1:1.99-3 Severity: minor Hi, It seems that dh_bash-completion is still installing files in /etc/bash_completion. On my system /etc/bash_completion points to /usr/share/bash-completion/bash_completion. Shouldn't dh_bash-completion install the files directly into /usr/share/bash-completion/bash_completion? Cheers Laurent Bigonville -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bash-completion depends on: ii bash 4.2-2 bash-completion recommends no packages. bash-completion suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: bash-completion Source-Version: 1:2.1-4.2 We believe that the bug you reported is fixed in the latest version of bash-completion, 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 668...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille ti...@debian.org (supplier of updated bash-completion 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: Tue, 18 Aug 2015 21:47:32 +0200 Source: bash-completion Binary: bash-completion Architecture: source all Version: 1:2.1-4.2 Distribution: unstable Urgency: medium Maintainer: Bash Completion Maintainers bash-completion-de...@lists.alioth.debian.org Changed-By: Andreas Tille ti...@debian.org Description: bash-completion - programmable completion for the bash shell Closes: 668254 Changes: bash-completion (1:2.1-4.2) unstable; urgency=medium . * Non-maintainer upload. * fix location of bash-completion files Closes: #668254 Checksums-Sha1: 211965da6f0701ea8121848206bc9480a0f2ff71 2030 bash-completion_2.1-4.2.dsc 1f37c6b589dbf3969fd7c604eda680f195434dbf 19660 bash-completion_2.1-4.2.debian.tar.xz 26a0007f92e01441822433acf2fcb84477b568de 179446 bash-completion_2.1-4.2_all.deb Checksums-Sha256: 89c1341ec979c7fd57150bf0c6b159d9053c7f7613f10fbd67d0ffb93b02533e 2030 bash-completion_2.1-4.2.dsc 5265a0f15d0e73b9644764a9ea60ee9649de8ac4a61ede02f54b228b3d243095 19660 bash-completion_2.1-4.2.debian.tar.xz f56a9c69e1787ab303a218ec125fd55cb26f24d514543f0ada2a758cfc26a2d2 179446 bash-completion_2.1-4.2_all.deb Files: ecb1ad9e9d2bae3b3b41b84466811b3a 2030 shells standard bash-completion_2.1-4.2.dsc 0f90dedac97254fc3a136fb868cdaf37 19660 shells standard bash-completion_2.1-4.2.debian.tar.xz f5a326c7636f4ba7e46aa2307619ec1c 179446 shells standard bash-completion_2.1-4.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJV04wvAAoJEFeKBJTRxkbRFz0P/RAR6zvNAMXmuu4GKrMolCmA gRHiUL9i3+hklCxTPp2WkOONwVzjDR3DNrOCY9WwYyQN8ETthHFSyl7dAyKPDC1w 3L4N7x39yzXK5sCy9qgriPFhfWNtBGZJHup8mA+jfejtckBO/YpTGAMRs//kZDjE QMZieQT1r8fBIkyi3Ds07VK2n7GmhxbcoXHmZadb7coJsJnr+xnVLsBchD5ziEQv TWMWk2nFCuzfWltqc9UcNLCwndv0jm3J0/FVrsz+0L68KV5aK2biq0nOd/wXkDWf TdHXJIjrNENMimpq7aGuIkCPxQ1bwP5pjGIJqqBrgdOQkuPbfHr5E1hOOR38HOkq 3p/e/eFs1yEcgc122AFB5bfKKH0GkxkfTptgHXNjqZLwbaKDVBDttL0+6O0NLIih x8pUNOVw2eK2rlTpQ2tYx1WUpZbvlQhosOlMiu2f1Lax/ao+peXaDwrGiQN6gHeQ BXxp764O+zEi6LWUcp45rh8J+zYE7YNPOERtt55qyA0tYkwD8cUrjN0n4ymtyNWG 8g2XyElk31oL4v1sogsyQkG8CQv7/1/0J8duVvhMY8ao4vlqyr+vUWnktrSiD6E9 fQNTRm2+ru21Iqvu8nNgUFd/gp9c/zHnvghXde58tWBH9HmW8bJQKAGvGeFKK3u6 ku0wCgrT0MQP9FsS6MiE =kU8+ -END PGP SIGNATUREEnd Message---
Bug#795814: FTBFS: boost/math/tools/test.hpp: No such file or directory
On Mon, 17 Aug 2015 at 09:57:16 +0100, Manuel A. Fernandez Montecelo wrote: Today it cannot even start to compile because of conflics of deps to install: The following packages have unmet dependencies: libopenexr6v5 : Conflicts: libopenexr6 but 1.6.1-8 is to be installed. libilmbase6v5 : Conflicts: libilmbase6 but 1.0.1-6.1 is to be installed. libcairomm-1.0-1v5 : Conflicts: libcairomm-1.0-1 but 1.10.0-1.1+b1 is to be installed. I think this was caused by a mis-build of imagemagick on amd64[1] which has now been fixed by a binNMU. Please try again; I can reproduce the original build failure in sbuild today. I think this might be the last sourceful upload needed by the imagemagick sub-transition within the larger libstdc++ mess. S [1] The mirror used by my sbuild chroot hadn't seen libopenexr6v5 yet, causing it to be built against libopenexr6 on amd64 only. I for one welcome our new throw away maintainer-built binaries overlords.
Processed: liborigin2: library transition
Processing commands for cont...@bugs.debian.org: user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was deb...@kitterman.com). usertag 791151 + transition There were no usertags set. Usertags are now: transition. block 791151 by 790756 Bug #791151 [src:liborigin2] liborigin2: library transition may be needed when GCC 5 is the default 791151 was not blocked by any bugs. 791151 was not blocking any bugs. Added blocking bug(s) of 791151: 790756 reassign 791151 release.debian.org Bug #791151 [src:liborigin2] liborigin2: library transition may be needed when GCC 5 is the default Bug reassigned from package 'src:liborigin2' to 'release.debian.org'. No longer marked as found in versions liborigin2/20110117-1. Ignoring request to alter fixed versions of bug #791151 to the same values previously set End of message, stopping processing here. Please contact me if you need assistance. -- 791151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#794027: marked as done (metview: Build dependency on libnetcdf-cxx-legacy-dev required for netcdf transition)
Your message dated Sun, 23 Aug 2015 21:23:50 + with message-id e1ztck2-0001ni...@franck.debian.org and subject line Bug#794027: fixed in metview 4.5.6-5.1 has caused the Debian Bug report #794027, regarding metview: Build dependency on libnetcdf-cxx-legacy-dev required for netcdf transition to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 794027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: metview Version: 4.5.6-3 Severity: normal Tags: patch User: debian-...@lists.debian.org Usertags: netcdf-split-c-f-cxx Dear Maintainer, For the upcoming netcdf transition your package needs a build dependency on libnetcdf-cxx-legacy-dev to build successfully with the netcdf packages in experimental. The attached patches add the build dependency for metview (4.5.6-3) and metview (4.5.6-4exp1). Since NetCDF 4.3.3.1 the upstream developers have split the project into language specific releases, the netcdf Debian package has likewise split into language specific source packages: ┌─┬───┬──┐ │ NetCDF project │ Source package│ -dev package │ ├─┼───┼──┤ │ NetCDF-C│ netcdf│ libnetcdf-dev│ │ NetCDF C++ (cxx4) │ netcdf-cxx│ libnetcdf-c++4-dev │ │ NetCDF C++ (legacy) │ netcdf-cxx-legacy │ libnetcdf-cxx-legacy-dev │ │ NetCDF-Fortran │ netcdf-fortran│ libnetcdff-dev │ └─┴───┴──┘ The netcdf-cxx provides the new NetCDF 4 C++ API in libnetcdf_c++4.so.1, and netcdf-cxx-legacy the legacy NetCDF 3 C++ API in libnetcdf_c++.so.4. For more information about the different NetCDF C++ APIs, see: http://www.unidata.ucar.edu/downloads/netcdf/netcdf-cxx/index.jsp Kind Regards, Bas diff -ruN ../metview-4.5.6-3_debian.orig/control debian/control --- ../metview-4.5.6-3_debian.orig/control 2015-07-29 23:58:25.173989577 +0200 +++ debian/control 2015-07-29 23:59:17.753718664 +0200 @@ -11,8 +11,8 @@ libmotif-dev, libxmu-dev, libgdbm-dev, libcurl4-gnutls-dev, libcairo2-dev, pkg-config, swig, libexpat1-dev, libterralib-dev, ksh, libproj-dev, - libgd-dev, imagemagick, libnetcdf-dev, libopenjpeg-dev, - scm [!arm64 !ppc64], cmake, flextra + libgd-dev, imagemagick, libnetcdf-dev, libnetcdf-cxx-legacy-dev, + libopenjpeg-dev, scm [!arm64 !ppc64], cmake, flextra Build-Conflicts: lesstif2-dev Standards-Version: 3.9.6 Homepage: https://software.ecmwf.int/wiki/display/METV/Metview diff -ruN ../metview-4.5.6-4exp1_debian.orig/control debian/control --- ../metview-4.5.6-4exp1_debian.orig/control 2015-07-30 00:45:06.859445182 +0200 +++ debian/control 2015-07-30 00:44:28.187644158 +0200 @@ -11,7 +11,7 @@ libmotif-dev, libxmu-dev, libgdbm-dev, libcurl4-gnutls-dev, libcairo2-dev, pkg-config, swig, libexpat1-dev, libterralib-dev, ksh, libproj-dev, - libgd-dev, imagemagick, libnetcdf-dev, + libgd-dev, imagemagick, libnetcdf-dev, libnetcdf-cxx-legacy-dev, libopenjpeg-dev, cmake, flextra Build-Conflicts: lesstif2-dev Standards-Version: 3.9.6 ---End Message--- ---BeginMessage--- Source: metview Source-Version: 4.5.6-5.1 We believe that the bug you reported is fixed in the latest version of metview, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 794...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg sebas...@debian.org (supplier of updated metview 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, 22 Aug 2015 17:22:04 +0200 Source: metview Binary: metview metview-data libmetview-dev Architecture: source amd64 all Version: 4.5.6-5.1 Distribution: experimental Urgency: medium Maintainer: Alastair McKinstry mckins...@debian.org Changed-By: Bas Couwenberg sebas...@debian.org Description: libmetview-dev - Development files for MetView metview- Interactive data visualization and analysis environment, metview-data - Data needed for the Metview data analysis environment
Bug#791173: marked as done (libstxxl: library transition may be needed when GCC 5 is the default)
Your message dated Mon, 24 Aug 2015 00:00:15 + with message-id e1ztfbp-00058v...@franck.debian.org and subject line Bug#791173: fixed in libstxxl 1.4.1-2 has caused the Debian Bug report #791173, regarding libstxxl: library transition may be needed when GCC 5 is the default to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 791173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libstxxl Version: 1.4.1-1 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for BEGIN GCC CXX11 in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition ---End Message--- ---BeginMessage--- Source: libstxxl Source-Version: 1.4.1-2 We believe that the bug you reported is fixed in the latest version of libstxxl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky gl...@debian.org (supplier of updated libstxxl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 23 Aug 2015 17:00:29 +0200 Source: libstxxl Binary: libstxxl-dev libstxxl-doc libstxxl1v5 libstxxl1-bin libstxxl1-dbg Architecture: source amd64 all Version: 1.4.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Anton Gladky gl...@debian.org Description: libstxxl-dev - Development libraries for STXXL libstxxl-doc - Documentation for STXXL libstxxl1-bin - STXXL File creation and benchmark tool libstxxl1-dbg - Debugging symbols for STXXL libraries libstxxl1v5 - C++ Standard Template Library for extra large datasets Closes: 791173 Changes: libstxxl
Processed: severity of 791151 is normal
Processing commands for cont...@bugs.debian.org: severity 791151 normal Bug #791151 [release.debian.org] liborigin2: library transition may be needed when GCC 5 is the default Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 791151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796740: linux-image-4.0.0-2-amd64: kernel gets drugged to sleep when idle
Control: severity -1 important Control: tag -1 moreinfo On Sun, 2015-08-23 at 14:52 -0500, Richard Jasmin wrote: Package: src:linux Version: 4.0.8-2 Severity: grave Tags: upstream Justification: renders package unusable Mommy Mommy he wont wake up seems to summarize this one nicely. System goes to sleep when idle for any length of time. Problem is once asleep, it wont wake. Not using sw suspend or anything like that either. Did not notice this with debian in the past, even with the 990FX board, buggy as it may be. No, I cant use anything newer, kmod causes video driver and virtualbox breakage(yet again).Stuck with #4002 until reformat or kmod issue gets fixed. Making backup set is taking sweet time. Please report back when the out-of-tree modules are fixed and you can test with 4.1. Ben. -- Ben Hutchings You can't have everything. Where would you put it? signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#796740: linux-image-4.0.0-2-amd64: kernel gets drugged to sleep when idle
Processing control commands: severity -1 important Bug #796740 [src:linux] linux-image-4.0.0-2-amd64: kernel gets drugged to sleep when idle Severity set to 'important' from 'grave' tag -1 moreinfo Bug #796740 [src:linux] linux-image-4.0.0-2-amd64: kernel gets drugged to sleep when idle Added tag(s) moreinfo. -- 796740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796751: ldc: FTBFS on armhf: gen/asm-x86.h:225:5: error: narrowing conversion of '-1' from 'int' to 'char' inside { }
Source: ldc
Version: 1:0.14.0.dfsg-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
ldc was binNMU'd for the libstdc++ transition (specifically, Rebuild
with libconfig++9v5.
The log:
https://buildd.debian.org/status/fetch.php?pkg=ldcarch=armhfver=1%3A0.14.0.dfsg-1%2Bb1stamp=1440269448
You'll see there are lots of instances of:
In file included from /«PKGBUILDDIR»/gen/asmstmt.cpp:142:0:
/«PKGBUILDDIR»/gen/asm-x86.h:225:5: error: narrowing conversion of '-1' from
'int' to 'char' inside { } [-Wnarrowing]
I'm a little confused as to why a file named asm-x86.h would be included
on the only non-x86 architecture supported by ldc, so perhaps that's the
bug here; or perhaps there's some good reason for it, and something
else is broken.
S
Bug#796753: FTBFS: tries to download from PyPI
Package: python-django-pyscss
Version: 2.0.2-1
Severity: serious
Justification: fails to build from source
User: python-dja...@packages.debian.org
Usertags: django18
Hello,
During a test rebuild of packages dependent on python-django for the upcoming
Django 1.8 transition, your package failed to build from source.
This rebuild was done against unstable on an amd64 system, under python-django
1.7.9-1.
The log from the build is attached. Relevant portions enclosed below.
-- Luke Faraone
=== Testing with python2.7
running test
Searching for mock
Reading https://pypi.python.org/simple/mock/
Download error on https://pypi.python.org/simple/mock/: [SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) -- Some
packages may not be found!
Couldn't find index page for 'mock' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: [SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) -- Some
packages may not be found!
No local packages or download links found for mock
error: Could not find suitable distribution for Requirement.parse('mock')
make[1]: *** [override_dh_auto_test] Error 1
debian/rules:29: recipe for target 'override_dh_auto_test' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build] Error 2
debian/rules:10: recipe for target 'build' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2
python-django-pyscss_2.0.2-1_amd64.build
Description: inode/symlink
Bug#796754: FTBFS: test_filtering_uses_distinct raises AttributeError
Package: django-filter Version: 0.9.2-1 Severity: serious Justification: fails to build from source User: python-dja...@packages.debian.org Usertags: django18 Hello, During a test rebuild of packages dependent on python-django for the upcoming Django 1.8 transition, your package failed to build from source. This rebuild was done against unstable on an amd64 system, under python-django 1.7.9-1. The log from the build is attached. Relevant portions enclosed below. -- Luke Faraone == ERROR: test_filtering_uses_distinct (tests.test_filters.FilterTests) -- Traceback (most recent call last): File /«PKGBUILDDIR»/tests/test_filters.py, line 179, in test_filtering_uses_distinct result = qs.distinct.assert_called_once() File /usr/lib/python2.7/dist-packages/mock/mock.py, line 721, in __getattr__ raise AttributeError(name) AttributeError: assert_called_once -- Ran 205 tests in 0.722s FAILED (errors=1, skipped=13, expected failures=7, unexpected successes=1) django-filter_0.9.2-1_amd64.build Description: inode/symlink
Bug#796443: closing 796443
close 796443 thanks Closed with 2.2.0+dfsg-2 -- Enrico Tassi
Processed: fixup BTS metadata
Processing commands for cont...@bugs.debian.org:
reopen 792685
Bug #792685 {Done: Nikolaus Rath nikol...@rath.org} [s3ql] Unable to upgrade
from wheezy to jessie
'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 2.13.
tags 792685 +jessie
Bug #792685 [s3ql] Unable to upgrade from wheezy to jessie
Added tag(s) jessie.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
792685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#792685: fixup BTS metadata
reopen 792685 tags 792685 +jessie thanks You closed the bug in a nonexistant version. Furthermore the bug isn't fixed per-se it's just not applicable to stretch/sid (because we don't support direct upgrades from wheezy to stretch/sid). The correct way to indicate that a bug is not applicable for particular releases is to use release tags. Hopefully with this metadata fixup the package should be able to migrate to stretch.
Processed: your mail
Processing commands for cont...@bugs.debian.org:
notfound 793195 1.0.0.49-1
Bug #793195 {Done: Michael Gilbert mgilb...@debian.org} [src:steam] steam:
FTBFS due to missing B-D: libx11-6
Ignoring request to alter found versions of bug #793195 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
793195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 787959
Processing commands for cont...@bugs.debian.org: tags 787959 + fixed-upstream upstream Bug #787959 [backintime-common] [backintime-common] backintime failed to start: No such file or directory Added tag(s) upstream and fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 787959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#791127: marked as done (libgtksourceviewmm: transition to libgtksourceviewmm-3.0-0v5 needed)
Your message dated Sun, 23 Aug 2015 22:00:14 + with message-id e1ztdjg-0005n8...@franck.debian.org and subject line Bug#791127: fixed in libgtksourceviewmm 3.12.0-2 has caused the Debian Bug report #791127, regarding libgtksourceviewmm: transition to libgtksourceviewmm-3.0-0v5 needed 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.) -- 791127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libgtksourceviewmm Version: 3.12.0-1 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for BEGIN GCC CXX11 in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition ---End Message--- ---BeginMessage--- Source: libgtksourceviewmm Source-Version: 3.12.0-2 We believe that the bug you reported is fixed in the latest version of libgtksourceviewmm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie s...@debian.org (supplier of updated libgtksourceviewmm 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, 23 Aug 2015 16:05:49 +0100 Source: libgtksourceviewmm Binary: libgtksourceviewmm-3.0-0v5 libgtksourceviewmm-3.0-dev libgtksourceviewmm-3.0-dbg libgtksourceviewmm-3.0-doc Architecture: all amd64 source Version: 3.12.0-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Simon McVittie s...@debian.org Closes: 791127 Description: libgtksourceviewmm-3.0-0v5 - C++ binding of GtkSourceView libgtksourceviewmm-3.0-dbg - C++ binding of GtkSourceView - debugging symbols libgtksourceviewmm-3.0-dev - C++ binding of
Processed: closing 796443
Processing commands for cont...@bugs.debian.org: close 796443 Bug #796443 [src:luarocks] luarocks: FTBFS: configure: appears incompatiable with lua 5.2 as /usr/bin/lua Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 796443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#795014: marked as done (libadplug-2.2.1-0 broke ABI in binNMU due to libstdc++6 transition)
Your message dated Mon, 24 Aug 2015 00:00:14 + with message-id e1ztfbo-00058t...@franck.debian.org and subject line Bug#795014: fixed in adplug 2.2.1+dfsg3-0.3 has caused the Debian Bug report #795014, regarding libadplug-2.2.1-0 broke ABI in binNMU due to libstdc++6 transition to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 795014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mpd Version: 0.19.10-1+b2 Severity: grave Justification: renders package unusable Dear Maintainer, After dist-upgrade, mpd does not start anymore in unstable; indeed, running /usr/bin/mpd yields: /usr/bin/mpd: symbol lookup error: /usr/bin/mpd: undefined symbol: _ZN7CAdPlug7factoryERKSsP4CoplRK8CPlayersRK13CFileProvider All DSOs required by mpd are present on the system: $ LANG=C ldd /usr/bin/mpd | grep 'found' $ After a short investigation, it appears the missing symbol is supposed to be found in /usr/lib/libadplug-2.2.1.so.0; alas, there is a symbol name mismatch: * mpd requires _ZN7CAdPlug7factoryERKSsP4CoplRK8CPlayersRK13CFileProvider * libadplug-2.2.1.so.0 provides _ZN7CAdPlug7factoryERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEP4CoplRK8CPlayersRK13CFileProvider The latter statement can be checked using readelf: $ readelf --wide --symbols /usr/lib/libadplug-2.2.1.so.0 | grep _ZN7CAdPlug7factory 358: 000247d0 692 FUNCGLOBAL DEFAULT 11 _ZN7CAdPlug7factoryERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEP4CoplRK8CPlayersRK13CFileProvider This behaviour was observed with packages: * mpd: 0.19.10-1+b2 * libadplug-2.2.1-0: 2.2.1+dfsg3-0.2+b1 I am unsure whether the fix should occur in mpd or libadplug, so I reported this bug for mpd, as it is rendered unusable by the issue. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mpd depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.23 ii libadplug-2.2.1-0 2.2.1+dfsg3-0.2+b1 ii libao41.1.0-3 ii libasound21.0.29-1 ii libaudiofile1 0.3.6-2+b1 ii libavahi-client3 0.6.31-5 ii libavahi-common3 0.6.31-5 ii libavcodec-ffmpeg56 7:2.7.2-1 ii libavformat-ffmpeg56 7:2.7.2-1 ii libavutil-ffmpeg547:2.7.2-1 ii libbz2-1.01.0.6-8 ii libc6 2.19-19 ii libcdio-cdda1 0.83-4.2 ii libcdio-paranoia1 0.83-4.2 ii libcdio13 0.83-4.2 ii libcurl3-gnutls 7.43.0-1 ii libdbus-1-3 1.8.20-1 ii libexpat1 2.1.0-7 ii libfaad2 2.8.0~cvs20150510-1 ii libflac8 1.3.1-4 ii libfluidsynth11.1.6-2 ii libglib2.0-0 2.44.1-1.1 ii libgme0 0.5.5-2.1 ii libicu52 52.1-10 ii libid3tag00.15.1b-11 ii libiso9660-8 0.83-4.2 ii libjack0 [libjack-0.116] 1:0.124.1+20140122git5013bed0-3 ii libmad0 0.15.1b-8 ii libmikmod33.3.7-1 ii libmms0 0.6.2-4 ii libmodplug1 1:0.8.8.5-1 ii libmp3lame0 3.99.5+repack1-9 ii libmpcdec62:0.1~r459-4.1 ii libmpdclient2 2.9-1 ii libmpg123-0 1.22.2-1 ii libnfs8 1.9.7-2 ii libogg0 1.3.2-1 ii libopenal11:1.16.0-3 ii libopus0 1.1-2 ii libpulse0 6.0-5 ii libresid-builder0c2a 2.1.1-14 ii libroar2 1.0~beta11-3 ii libsamplerate00.1.8-8 ii libshout3 2.3.1-3 ii libsidplay2 2.1.1-14 ii libsidutils0 2.1.1-14 ii libsmbclient 2:4.1.17+dfsg-4 ii libsndfile1 1.0.25-9.1 ii libsoxr0 0.1.1-1 ii libsqlite3-0 3.8.11.1-1 ii libstdc++65.2.1-14 ii libsystemd0 224-1 ii libupnp6 1:1.6.19+git20141001-1 ii libvorbis0a 1.3.4-2 ii libvorbisenc2 1.3.4-2 ii libvorbisfile31.3.4-2 ii libwavpack1 4.75.0-1 ii
Bug#796757: FTBFS: test failures with Django 1.7
Source: djangorestframework-nested-resource Version: 1.2.0-1 Severity: serious Justification: fails to build from source User: python-dja...@packages.debian.org Usertags: django18 Hello, During a test rebuild of packages dependent on python-django for the upcoming Django 1.8 transition, your package failed to build from source. This rebuild was done against unstable on an amd64 system, under python-django 1.7.9-1. The log from the build is attached. -- Luke Faraone sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on aqua.sfba.luke.wf ╔══╗ ║ djangorestframework-nested-resource 1.2.0-1 (amd64)23 Aug 2015 22:35 ║ ╚══╝ Package: djangorestframework-nested-resource Version: 1.2.0-1 Source Version: 1.2.0-1 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 I: NOTICE: Log filtering will replace 'build/djangorestframework-nested-resource-SpneJ8/djangorestframework-nested-resource-1.2.0' with '«PKGBUILDDIR»' I: NOTICE: Log filtering will replace 'build/djangorestframework-nested-resource-SpneJ8' with '«BUILDDIR»' I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/sid-amd64-92439f3c-101e-486b-8cda-87124c7ee486' with '«CHROOT»' ┌──┐ │ Update chroot│ └──┘ Get:1 file: unstable InRelease [215 kB] Reading package lists... Reading package lists... Building dependency tree... Reading state information... The following package was automatically installed and is no longer required: libapt-inst1.5 Use 'apt-get autoremove' to remove it. The following packages will be REMOVED: libasprintf0c2 The following NEW packages will be installed: cpp-5 g++-5 gcc-5 libapparmor1 libapt-inst1.7 libapt-pkg4.16 libasan2 libasprintf0v5 libcc1-0 libgcc-5-dev libmpx0 libprocps4 libseccomp2 libstdc++-5-dev The following packages will be upgraded: apt apt-utils build-essential cpp g++ gcc gettext-base libapt-pkg-perl libparse-debianchangelog-perl libsystemd0 libudev1 procps systemd udev Preconfiguring packages ... 14 upgraded, 14 newly installed, 1 to remove and 0 not upgraded. Need to get 0 B/92.1 MB of archives. After this operation, 428 MB of additional disk space will be used. Selecting previously unselected package libapt-pkg4.16:amd64. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 14293 files and directories currently installed.) Preparing to unpack .../libapt-pkg4.16_1.0.10.2_amd64.deb ... Unpacking libapt-pkg4.16:amd64 (1.0.10.2) ... Setting up libapt-pkg4.16:amd64 (1.0.10.2) ... Processing triggers for libc-bin (2.19-19) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 14342 files and directories currently installed.) Preparing to unpack .../a/apt/apt_1.0.10.2_amd64.deb ... Unpacking apt (1.0.10.2) over (1.0.9.10) ... Processing triggers for man-db (2.7.2-1) ... Not building database; man-db/auto-update is not 'true'. Setting up apt (1.0.10.2) ... Processing triggers for libc-bin (2.19-19) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 14343 files and directories currently installed.) Preparing to unpack .../gettext-base_0.19.5.1-1_amd64.deb ...
Bug#791736: marked as done (FTBFS with GCC 5: changes to symbols file)
Your message dated Mon, 24 Aug 2015 04:04:06 + with message-id e1ztizo-0002vl...@franck.debian.org and subject line Bug#791736: fixed in qdbm 1.8.78-6 has caused the Debian Bug report #791736, regarding FTBFS with GCC 5: changes to symbols file 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.) -- 791736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: qdbm Version: 1.8.78-5 User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 This package fails to build with GCC 5: sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on bl460gen8-30.hlinux.usa.hp.com ... dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libxqdbm3c2/DEBIAN/symbols doesn't match completely debian/libxqdbm3c2.symbols --- debian/libxqdbm3c2.symbols (libxqdbm3c2_1.8.78-5_amd64) +++ dpkg-gensymbolsqzSSVp»··2015-07-07 21:43:37.455876446 + @@ -355,7 +355,7 @@ (c++)virtual thunk to qdbm::Villa_error::message() const@Base 1.8.74 (c++)virtual thunk to qdbm::Villa_error::operator char const*() const@Base 1.8.74 (c++)virtual thunk to qdbm::Villa_error::~Villa_error()@Base 1.8.74 - (c++)vtable for qdbm::ADBM@Base 1.8.74 +#MISSING: 1.8.78-5# (c++)vtable for qdbm::ADBM@Base 1.8.74 (c++)vtable for qdbm::Curia@Base 1.8.74 (c++)vtable for qdbm::Curia_error@Base 1.8.74 (c++)vtable for qdbm::DBM_error@Base 1.8.74 ... dh_makeshlibs: failing due to earlier errors -- Martin Michlmayr Linux for HP Helion, Hewlett-Packard ---End Message--- ---BeginMessage--- Source: qdbm Source-Version: 1.8.78-6 We believe that the bug you reported is fixed in the latest version of qdbm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. KURASHIKI Satoru lur...@gmail.com (supplier of updated qdbm 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: Tue, 04 Aug 2015 14:15:52 +0900 Source: qdbm Binary: libqdbm14 qdbm-doc libqdbm-dev qdbm-util qdbm-cgi libxqdbm3c2 libxqdbm-dev libqdbm3++c2 libqdbm++-dev libqdbm-perl ruby-qdbm libqdbm-java Architecture: source i386 all Version: 1.8.78-6 Distribution: unstable Urgency: medium Maintainer: KURASHIKI Satoru lur...@gmail.com Changed-By: KURASHIKI Satoru lur...@gmail.com Description: libqdbm++-dev - QDBM Database Libraries for C++ [development] (transitional packa libqdbm-dev - QDBM Database Libraries [development] libqdbm-java - QDBM Database Libraries for Java libqdbm-perl - QDBM Database Libraries for Perl libqdbm14 - QDBM Database Libraries without GDBM wrapper[runtime] libqdbm3++c2 - QDBM Database Libraries for C++ [runtime] (transitional package) libxqdbm-dev - QDBM Database Libraries for C++ [development] libxqdbm3c2 - QDBM Database Libraries for C++ [runtime] qdbm-cgi - QDBM Database CGI commands qdbm-doc - QDBM Database Documentation qdbm-util - QDBM Database Utilities ruby-qdbm - QDBM Database Libraries for Ruby Closes: 791736 Changes: qdbm (1.8.78-6) unstable; urgency=medium . * New Standards-Version: 3.9.6. * update symbol file to fix ftbfs with gcc-5. (Closes: #791736) Checksums-Sha1: db4c38260e8cf996876e498e2b9c5e718ecb9053 2510 qdbm_1.8.78-6.dsc a3ad7d5e42dee8a954c828ffab9103d8b6383635 16180 qdbm_1.8.78-6.debian.tar.xz 8852653fbf42ecc5a0ac5d8cc695fefd6d356d63 9544 libqdbm++-dev_1.8.78-6_i386.deb 5f2d4f894af600ff6f7949398736e4aeb3b41382 181974 libqdbm-dev_1.8.78-6_i386.deb 33cd355c04981db48036a25530e0e3a53d75f3fb 44982 libqdbm-java_1.8.78-6_i386.deb f580da75e49031691cb320dfa7d2a503d71c316c 41566 libqdbm-perl_1.8.78-6_i386.deb 7454be52fb25f324ea9de0460e08debb54138299 124234 libqdbm14_1.8.78-6_i386.deb 58ce5aae1193702b4f3e281f963fe5d897d7118a 9370 libqdbm3++c2_1.8.78-6_i386.deb 609dd0503960087e2fa90eac08e5702e152223fb 34270 libxqdbm-dev_1.8.78-6_i386.deb 08efbae95d3020370476b68313bf954f9d7150b0 103172 libxqdbm3c2_1.8.78-6_i386.deb 3b9bc78f245bb4777414b91f8e3250b6d237b9e9 33258 qdbm-cgi_1.8.78-6_i386.deb
Processed (with 1 errors): Re: Bug#796601: encfs: password gets modified in keystore after umount
Processing control commands: tag 796601 +notreproducible Unknown tag/s: notreproducible. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore. Bug #796601 [encfs] encfs: password gets modified in keystore after umount Requested to add no tags; doing nothing. severity 796601 important Bug #796601 [encfs] encfs: password gets modified in keystore after umount Severity set to 'important' from 'grave' -- 796601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796305: python-oauthlib: FTBFS: plugin distutils failed with: exit code=1:
Hello Chris, many thanks for this report and sorry for my late reply but I was not notified (althouth I subscribed to python-oauthlib bugs time ago). On Friday 21 August 2015 10:08:51 Chris Lamb wrote: python-oauthlib fails to build from source on unstable/amd64: Yes, it's due some docstrings that can't be tested as, for example, this: https://github.com/idan/oauthlib/blob/16cd3b255b2c86ec7da412357cad899c72d8dbf7/oauthlib/oauth1/rfc5849/endpoints/authorization.py#L77 But it was fixed in python-oauthlib 1.0.3-1. My usual sponsor tagged it on SVN (6 days ago[¹]) so I'm sure he uploaded it but since it's not in the archive something did not work. I'm sending him an email to sort this out. Sorry for the inconvenience. Kind regards, [¹] https://anonscm.debian.org/viewvc/python-modules/packages/python-oauthlib/trunk/debian/changelog?revision=33818view=markup -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Bug#796601: encfs: password gets modified in keystore after umount
Control: tag 796601 +notreproducible Control: severity 796601 important When using encfs to scramble a backup to an alternate media, the password gets modified somehow during umount.Any further attempts to mount the media fail, even if the password is correct. Cannot reproduce. Please show a sample .encfs6.xml and matching password or we cannot do much for you. I copy the password from keepass to a text file, then copy the password to the There is no keepass package in Debian. Do you mean keepassx or keepass2? terminal.You cannot directly copy from keepass to the terminal due to its secure storage and wiping feature with the clipboard. The password has not been changed by me since initial creation of the encfs storage. After using a terminal... seriously? Terminals hide a lot of invisible but effective characters. Regards, Eduard.
Bug#796754: FTBFS: test_filtering_uses_distinct raises AttributeError
On Mon, 24 Aug 2015 at 09:27 Luke Faraone lfara...@debian.org wrote: Package: django-filter Version: 0.9.2-1 Severity: serious Justification: fails to build from source User: python-dja...@packages.debian.org Usertags: django18 Looks like this is a problem for Django 1.7 too. The latest upstream version 0.11.0 still has this problem. I have opened a bug report upstream: https://github.com/alex/django-filter/issues/283
Processed: help
Processing commands for cont...@bugs.debian.org: tags 796715 + help Bug #796715 [src:coinor-osi] coinor-osi: library transition needed with GCC 5 as default Added tag(s) help. thanks Stopping processing here. Please contact me if you need assistance. -- 796715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#777781: marked as done (aspectc++: ftbfs with GCC-5)
Your message dated Mon, 24 Aug 2015 03:20:31 + with message-id e1ztijd-0005qu...@franck.debian.org and subject line Bug#81: fixed in aspectc++ 1:1.2+svn20150823-1 has caused the Debian Bug report #81, regarding aspectc++: ftbfs with GCC-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 81: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:aspectc++ Version: 1:1.2-1 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/aspectc++_1.2-1_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] /usr/include/c++/5/bits/stl_multimap.h:147: error: `iterator' is not a member of `_Rep_type' /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/CCSemExpr.cc:3721: In instantiation of `std::set::Puma::CTree *' /usr/include/c++/5/bits/stl_set.h:130: error: `const_iterator' is not a member of `_Rep_type' /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/CCSemExpr.cc:3756: In instantiation of `std::set::Puma::CTree *' /usr/include/c++/5/bits/stl_set.h:130: error: `const_iterator' is not a member of `_Rep_type' /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/inc/Puma/PreMacroManager.h:48: In instantiation of `std::mapconst char *,::Puma::PreMacro *' /usr/include/c++/5/bits/stl_map.h:149: error: `iterator' is not a member of `_Rep_type' make[3]: *** [/build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step2/src/CLexer.cc] Error 1 make[3]: *** Waiting for unfinished jobs weave.mk:72: recipe for target '/build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step2/src/CLexer.cc' failed /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/PreFileIncluder.ccmake[3]: *** [/build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step2/src/CCLexer.cc] Error 1 weave.mk:72: recipe for target '/build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step2/src/CCLexer.cc' failed :79: error: `sysDir' undeclared here /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/PreFileIncluder.cc:81: error: `sysDir' undeclared here /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/PreFileIncluder.cc:81: error: left operand of `-' not pointer to class object /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/PreFileIncluder.cc:81: error: invalid operand to binary `==' /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/PreFileIncluder.cc:81: error: undefined type /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/PreFileIncluder.cc:104: error: `lookupIdx' undeclared here /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/PreFileIncluder.cc:104: error: `lookupIdx' undeclared here /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/PreFileIncluder.cc:104: error: left operand of `-' not pointer to class object /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/PreFileIncluder.cc:104: error: invalid operand to binary `==' /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/PreFileIncluder.cc:104: error: undefined type /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/PreFileIncluder.cc:407: error: `iter' undeclared here /build/aspectc++-OAr2XC/aspectc++-1.2/Puma.copy/gen-release/step1/src/PreFileIncluder.cc:408: error: `iter' undeclared here
