Processed: tagging 707585
Processing commands for cont...@bugs.debian.org: tags 707585 + pending Bug #707585 [why] why: FTBFS in unstable Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 707585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 735576 with 735647
Processing commands for cont...@bugs.debian.org: block 735576 with 735647 Bug #735576 [rubygems] rubygems: Remove rubygems from the archive 735576 was blocked by: 735579 735585 735576 was not blocking any bugs. Added blocking bug(s) of 735576: 735647 thanks Stopping processing here. Please contact me if you need assistance. -- 735576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735648: x11vnc: buffer overflow detected: x11vnc terminated
Package: x11vnc Version: 0.9.13-1.1+b1 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, I use x11vnc to connect remotely to my linux PC through a SSH tunnel. All works like a charm until one week ago when, after an update (using aptitude) of my remote Debian Testing PC, I tried to connect to it from my home PC. From a console I run: $ ssh -L 5900:localhost:5900 my.remote.host.IP 'x11vnc -localhost -display :0' then, when I tried to open a vnc session with krdc, in the console I had this error message: *** buffer overflow detected ***: x11vnc terminated === Backtrace: = /lib/i386-linux-gnu/i686/cmov/libc.so.6(__fortify_fail+0x45)[0xb7029a15] /lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x10381a)[0xb702881a] /lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x10491a)[0xb702991a] /usr/lib/i386-linux-gnu/libvncserver.so.0(rfbProcessNewConnection+0x123)[0xb76c4b33] /usr/lib/i386-linux-gnu/libvncserver.so.0(rfbCheckFds+0x390)[0xb76c5040] /usr/lib/i386-linux-gnu/libvncserver.so.0(rfbProcessEvents+0x2e)[0xb76bb5be] x11vnc[0x80eba6d] x11vnc[0x80ade17] x11vnc[0x8056163] /lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xf5)[0xb6f3e8c5] x11vnc[0x8062eb7] === Memory map: 08048000-0818e000 r-xp 08:03 17059619 /usr/bin/x11vnc 0818e000-081d3000 rw-p 00145000 08:03 17059619 /usr/bin/x11vnc 081d3000-083ae000 rw-p 00:00 0 08bbd000-08c43000 rw-p 00:00 0 [heap] b626a000-b6652000 rw-s 00:04 159514662 /SYSV (deleted) b6652000-b6a3b000 rw-p 00:00 0 b6a51000-b6a6c000 r-xp 08:03 14368906 /lib/i386-linux-gnu/libgcc_s.so.1 b6a6c000-b6a6d000 rw-p 0001a000 08:03 14368906 /lib/i386-linux-gnu/libgcc_s.so.1 b6a95000-b6abd000 rw-s 00:04 160825423 /SYSV (deleted) b6abd000-b6ae4000 rw-s 00:04 160792654 /SYSV (deleted) b6ae4000-b6b0a000 rw-s 00:04 160759885 /SYSV (deleted) b6b0a000-b6b2f000 rw-s 00:04 160727116 /SYSV (deleted) b6b2f000-b6b53000 rw-s 00:04 160694347 /SYSV (deleted) b6b53000-b6b76000 rw-s 00:04 160661578 /SYSV (deleted) b6b76000-b6b98000 rw-s 00:04 160628809 /SYSV (deleted) b6b98000-b6bb9000 rw-s 00:04 160596040 /SYSV (deleted) b6bb9000-b6bd9000 rw-s 00:04 160563271 /SYSV (deleted) b6bd9000-b6bf8000 rw-s 00:04 160530502 /SYSV (deleted) b6bf8000-b6c16000 rw-s 00:04 160497733 /SYSV (deleted) b6c16000-b6c33000 rw-s 00:04 160464964 /SYSV (deleted) b6c33000-b6c4f000 rw-s 00:04 160432195 /SYSV (deleted) b6c4f000-b6c6a000 rw-s 00:04 160399426 /SYSV (deleted) b6c6a000-b6c84000 rw-s 00:04 160366657 /SYSV (deleted) b6c84000-b6c9d000 rw-s 00:04 160333888 /SYSV (deleted) b6c9d000-b6cb5000 rw-s 00:04 160301119 /SYSV (deleted) b6cb5000-b6ccc000 rw-s 00:04 160268350 /SYSV (deleted) b6ccc000-b6ce2000 rw-s 00:04 160235581 /SYSV (deleted) b6ce2000-b6cf7000 rw-s 00:04 160202812 /SYSV (deleted) b6cf7000-b6d0b000 rw-s 00:04 160170043 /SYSV (deleted) b6d0b000-b6d1e000 rw-s 00:04 160137274 /SYSV (deleted) b6d1e000-b6d3 rw-s 00:04 160104505 /SYSV (deleted) b6d3-b6d41000 rw-s 00:04 160071736 /SYSV (deleted) b6d41000-b6d51000 rw-s 00:04 160038967 /SYSV (deleted) b6d51000-b6d6 rw-s 00:04 160006198 /SYSV (deleted) b6d6-b6d6e000 rw-s 00:04 159973429 /SYSV (deleted) b6d6e000-b6d7b000 rw-s 00:04 159940660 /SYSV (deleted) b6d7b000-b6d87000 rw-s 00:04 159907891 /SYSV (deleted) b6d87000-b6d92000 rw-s 00:04 159875122 /SYSV (deleted) b6d92000-b6d9c000 rw-s 00:04 159842353 /SYSV (deleted) b6d9c000-b6da5000 rw-s 00:04 159809584 /SYSV (deleted) b6da5000-b6e29000 rw-p 00:00 0 b6e29000-b6e3 r-xp 08:03 14369033 /lib/i386-linux-gnu/i686/cmov/librt-2.17.so b6e3-b6e31000 r--p 6000 08:03 14369033 /lib/i386-linux-gnu/i686/cmov/librt-2.17.so b6e31000-b6e32000 rw-p 7000 08:03 14369033 /lib/i386-linux-gnu/i686/cmov/librt-2.17.so b6e32000-b6e37000 r-xp 08:03 19726675 /usr/lib/i386-linux-gnu/libXdmcp.so.6.0.0 b6e37000-b6e38000 rw-p 4000 08:03 19726675 /usr/lib/i386-linux-gnu/libXdmcp.so.6.0.0 b6e38000-b6e39000 rw-p 00:00 0 b6e39000-b6e3b000 r-xp 08:03 19726969 /usr/lib/i386-linux-gnu/libXau.so.6.0.0 b6e3b000-b6e3c000 r--p 1000 08:03 19726969 /usr/lib/i386-linux-gnu/libXau.so.6.0.0 b6e3c000-b6e3d000 rw-p 2000 08:03 19726969 /usr/lib/i386-linux-gnu/libXau.so.6.0.0 b6e3d000-b6e42000 r-xp 08:03 19727306 /usr/lib/i386-linux-gnu/libffi.so.6.0.1
Bug#728027: marked as done (libgringotts: package versioning leads to reused versions and thus rejects)
Your message dated Fri, 17 Jan 2014 09:36:03 + with message-id e1w45qn-0006k3...@franck.debian.org and subject line Bug#728027: fixed in libgringotts 1:1.2.1-13 has caused the Debian Bug report #728027, regarding libgringotts: package versioning leads to reused versions and thus rejects 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.) -- 728027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libgringotts Version: 1:1.2.1-2 Severity: serious Hi, About a year ago, libgringotts acquired an epoch in its version so that a lower version number could be used. Unfortunately this approach _does not_ permit version numbers to be re-used when the only difference is the epoch. Filenames for items such as .changes and .deb files do not contain the epoch, leading to rejects from the archive management software on architectures where libgringotts 1.2.1-2 was previously built; see the architectures stuck in uploaded on https://buildd.debian.org/status/package.php?p=libgringotts The solution to this is to ensure that version numbers are unique other than via epochs. Regards, Adam ---End Message--- ---BeginMessage--- Source: libgringotts Source-Version: 1:1.2.1-13 We believe that the bug you reported is fixed in the latest version of libgringotts, 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 728...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jose G. López josg...@gmail.com (supplier of updated libgringotts 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, 15 Dec 2013 15:37:32 +0100 Source: libgringotts Binary: libgringotts-dev libgringotts2 Architecture: source amd64 Version: 1:1.2.1-13 Distribution: unstable Urgency: low Maintainer: Jose G. López josg...@gmail.com Changed-By: Jose G. López josg...@gmail.com Description: libgringotts-dev - development files for the gringotts data encapsulation library libgringotts2 - gringotts data encapsulation and encryption library Closes: 728027 Changes: libgringotts (1:1.2.1-13) unstable; urgency=low . * Bump Debian version to avoid getting rejected due to a previous version (1.2.1-12). (Closes: #728027). * Bump Standards-Version to 3.9.5. No changes required. Checksums-Sha1: 321d8d4a3c4d6425d8ddfcdc19a5e387690cf880 1987 libgringotts_1.2.1-13.dsc 40a93bdec9927613978cc5e124a7d9c11664bc98 4624 libgringotts_1.2.1-13.debian.tar.xz 243369c65ec42da8d5006087c9cd30ee23fe3017 23572 libgringotts-dev_1.2.1-13_amd64.deb b469e25dd1423137046e4edb06a15414a4903548 16446 libgringotts2_1.2.1-13_amd64.deb Checksums-Sha256: 2879c6ec8057f792c0a338f5435d23046b4c2d9d2477a77200ef6f46c086bb33 1987 libgringotts_1.2.1-13.dsc d638da4ed8f60061028a8ef0c906d6e531a85ab37bd08dd87421b27bcf4bdf6b 4624 libgringotts_1.2.1-13.debian.tar.xz ab116c959d3a3b645415c5771fb09ddffda2ac36800a1cbf63b1b15de2ad0fb3 23572 libgringotts-dev_1.2.1-13_amd64.deb 2c120d96a6022f61213aea7af8aef365f49dbf1ac4ccad54181a1e0a244be3b0 16446 libgringotts2_1.2.1-13_amd64.deb Files: 89233832235a966db6ef1b61557a0c48 1987 libs optional libgringotts_1.2.1-13.dsc f4b6ccd94217f436162651c39dc30500 4624 libs optional libgringotts_1.2.1-13.debian.tar.xz af6fe349769647f099af52e15e1f6da5 23572 libdevel optional libgringotts-dev_1.2.1-13_amd64.deb 27fdde12e1614d6f229a228984f00a21 16446 libs optional libgringotts2_1.2.1-13_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJS2OJIAAoJEI7tzBuqHzL/4fgP/RSlHbfjVT8FnsIQM2TgZL8s uwfD2uYuKs8G2DRpfQRnXprhkqrm3Ad5Gj8EJHe24UvSSfXdfNFup2PfOOZhpnMY BCFr/jbDpFRxBya/EMNnQJpCHcjn+0/MAOiMcNMvgPn0AadBgHt8hLvalaqefmLJ AI0P9lzNtNxZZ5/BZbZEoyiFCALz7yXjtkMmmCo75MNGETNplGptkjHeBvsaB3Ht gDdhr3lrYH7XMnA+p6L0f/6+l5hgWnulftN5ugPve4onw4TyHrkQvAt0Ba4nUnsZ 8iKKKmkdhjiKIruAKUq0AZ5kEdbhnL8r3HSOR9/b5RL3gYZGhV1aLSZUyzWYqUsA Qm2NenUiByJuQ4W9McIQahbG1xDaYGvfCT/4SfMdM7G/OKH/0tn9kmOC5B4b7mz9 wC2wUa9teRddY3RWp6Rmwx2u5rhqNSzzOt263KtsAC0ARq5+opL3xDBXkAwyYOG/ cLTUB0x2q+R2ZoS85JvDajngaNi+4SvVzC6xmVK7FOwyieSW75zs/AdI1WcqfLxQ 9dZv542OUm/3uRb7MM+uAcvBGMHI8IJhmo/38PCZuJaaRznLHB9xBnI0dxVejCjc
Bug#734406: marked as done (openrc: uninstallable - overwrites files in file-rc)
Your message dated Fri, 17 Jan 2014 09:37:31 + with message-id e1w45rn-0007ke...@franck.debian.org and subject line Bug#734406: fixed in openrc 0.12.4+20131230-4 has caused the Debian Bug report #734406, regarding openrc: uninstallable - overwrites files in file-rc 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.) -- 734406: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: openrc severity: grave version:0.12.4+20131230-3 Hi, openrc is currently uninstallable: # apt-get install openrc [...] dpkg: error processing /var/cache/apt/openrc_0.12.4+20131230-3_i386.deb (--unpack) trying to overwrite '/usr/sbin/update-rc.d', which is also in package file-rc 0.8.16 ---End Message--- ---BeginMessage--- Source: openrc Source-Version: 0.12.4+20131230-4 We believe that the bug you reported is fixed in the latest version of openrc, 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 734...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated openrc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 17 Jan 2014 07:01:23 + Source: openrc Binary: openrc openrc-dbg librc1 librc-dev libeinfo1 libeinfo-dev Architecture: source amd64 Version: 0.12.4+20131230-4 Distribution: experimental Urgency: medium Maintainer: Roger Leigh rle...@debian.org Changed-By: Thomas Goirand z...@debian.org Description: libeinfo-dev - dependency based init system (pretty control display development) libeinfo1 - dependency based init system (pretty console display library) librc-dev - dependency based init system (runtime development) librc1 - dependency based init system (runtime library) openrc - dependency based init system (runlevel change mechanism) openrc-dbg - dependency based init system (runlevel change mechanism) - debug Closes: 734283 734406 Changes: openrc (0.12.4+20131230-4) experimental; urgency=medium . [ Benda Xu ] * Add myself to the uploaders field. * rc-update: Add the feature of removing a service from all runlevels. update-rc.d: make use of the new rc-update feature. * Rename single runlevel to recovery. OpenRC treats single runlevel specially. . [ Thomas Goirand ] * Added etc/rc.conf.GNU and mk/os-GNU.mk to have a chance to be able to build under GNU Hurd. * Patches librc.h so that it works for Hurd. * Added missing dependency on insserv (Closes: 734283). Thanks to Axel Beckert a...@debian.org for finding this out and his bug report. * Now conflicts with file-rc (Closes: #734406), thanks to Michael Gilbert mgilb...@debian.org for reporting the problem. Checksums-Sha1: 529e09081f3d4540430ca354529537c08b255e2e 2160 openrc_0.12.4+20131230-4.dsc fa0ea1c97c454312fa8fec5f46c36beedc6a1cc5 18413 openrc_0.12.4+20131230-4.debian.tar.gz 036001c7fb3fd8289e33253144a953c20c8b1d98 83096 openrc_0.12.4+20131230-4_amd64.deb d2de3d0dd8e689a94847164bde4fe4bf0051b994 196688 openrc-dbg_0.12.4+20131230-4_amd64.deb 71eb6d8d5c8d1391f448779c5bf105136420c285 22942 librc1_0.12.4+20131230-4_amd64.deb 3fbca936ef62b9a443b6a1029a1db1ac095c5e31 19714 librc-dev_0.12.4+20131230-4_amd64.deb 7131e83ad88d0a041b7cbd93d86c09da81a95f12 10656 libeinfo1_0.12.4+20131230-4_amd64.deb 48f524a5f1f13be09a6ab7190391ebfa0e67608e 7746 libeinfo-dev_0.12.4+20131230-4_amd64.deb Checksums-Sha256: 224527c1eb7d867000a29a30b1a0872314822973aec454b58a12a3bed1621599 2160 openrc_0.12.4+20131230-4.dsc 94d08b8928822250ec24490ead52f89596513f7fd775f03a4906cf7fc200333d 18413 openrc_0.12.4+20131230-4.debian.tar.gz f1ca355e330e444b737297efcdb85cacc09507d62975a504d57674d5d6f86ae7 83096 openrc_0.12.4+20131230-4_amd64.deb a01b3d1c2dbb7b75305433eb61eead1bcf087cb0f1942924f3fee8d3d5929e24 196688 openrc-dbg_0.12.4+20131230-4_amd64.deb 6fa92b8bfc7787532b313be8730d52c31e106df320cc75d1aa49e5f2eba75d53 22942 librc1_0.12.4+20131230-4_amd64.deb 37060e6ab05186b96ca1073b66b484cc929ba45224b6f14387d1699a48fac894 19714 librc-dev_0.12.4+20131230-4_amd64.deb
Bug#735649: ruby-amrita2: FTBFS: does not work with newer rubies version
Package: ruby-amrita2 Severity: serious Usertags: ruby18-removal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, your packag does not work with newer rubies: Entering dh_ruby --install install -d /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2.rb install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2/testsupport.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/testsupport.rb install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2/gettext.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/gettext.rb install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2/macro.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/macro.rb install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2/version.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/version.rb install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2/rails_bridge.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/rails_bridge.rb install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2/template.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/template.rb /usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/template.rb:1352:in `process_block': undefined method `to_a' for #String:0x000139e198 (NoMethodError) from /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/template.rb:1335:in `process' from /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/template.rb:1178:in `setup' from /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/template.rb:1202:in `render_with' from /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/sample/hello/hello.rb:13:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from debian/ruby-tests.rb:1:in `main' ERROR: Test ruby1.9.1 failed. Exiting. dh_auto_install: dh_ruby --install /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2 returned exit code 1 make: *** [binary] Error 1 Thanks, Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJS2PiDAAoJEPBM7/YBbP/QZ9AP/2HbFfC1UuOxVMzhjH+m1h1v ua7urlbzMxvzJTcLfnMNzoDtEE7NOSa1f/Zha9eReE6qTVALKhafesT0KF88GTJf 8lfnCtdeSDUB7OT1c7/JrGypiOvsukeEdrlyF49YO0YISrjHLlP304SNiAEeofoj JFxwOWYm1VU4izZ08S5Sl57u0VP3bJnBtQwJWdXvNmDsMU33Pa9pnQWMJV1pmuNM xv3bS8GVXk/McEP0GLPs8ITawAyQKAGeg9gtPbXa0UGoofts4n8Uv5Gwm8MWx2ZO aloBRCXuZE57PuwGBHpQXXBRmYhc0vBc3Et0bC11+/s+jMlUYrQFRnfcmJxC4HBz 3qN4Ht/p9olre4Lwyie5pp/A1b8EoL2CQMPhaNUOoPsxHnDFNVmhwjy/5TfcqMKu fcNSGBs8IJ+X4K5QE+DmslvfaJ1DqQM5sl7rJxyXdRgK3SiKU4Pj+nk21G8z1AQS BfIATOjMIBLvHMc45jU5fXGwOb/hCvvere5oijQr88WYbgkpcPpEBY7cGZbCWoND rSfMsy0gDwM2WvAUD5m3H3kc8X5u+ENaTnvLanXBZHpPIi7mDxakey15AJ1lc+iE kyV06izltKOA+mQN6fq/URbrfz6NweJMvBUKWff2TrdacxE84FzSgOPQ4NWI8yZI p4cnS9RdDhpXzv2bz4SZ =6nox -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735651: dlr-languages: ruby1.8 won't be available on Jessie
Source: dlr-languages Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, dlr-languages produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#735652: geos: ruby1.8 won't be available on Jessie
Source: geos Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, geos produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#733496: Code copy of older Mozilla code
On Thu, Jan 16, 2014 at 1:52 PM, Moritz Mühlenhoff j...@inutil.org wrote: On Sun, Jan 05, 2014 at 02:47:39AM -0800, Vincent Cheng wrote: Hi, Package: mozjs17 Severity: serious This package forks a local copy of the Iceweasel Javascript engine which is no longer supported with security updates (currently only the ESR24 series is maintained) Out of curiosity, why is this a RC bug when there seems to be no issues from the security team with regards to src:mozjs (which is even older, based on Firefox 4 code AFAIU, and is currently in stable)? I hadn't notice it so far. That is even worse since it even up in a stable release! Will file a bug soon, thanks for point this out. Why do we need a copy of the old version anyway? What are the expected applications using it and why can't they be migrated to the mozjs provided by the iceweasel source package. The following packages are currently depending against libmozjs185-1.0: 0ad cinnamon couchdb dehydra gnome-shell libgjs0b libgjs0c libmozjs185-dev libpeas-1.0-0 mediatomb-common oolite policykit-1 (taken from mozjs17's ITP bug report, #709434) GNOME Shell stands out in that list above as a major package that depends on mozjs/Spidermonkey. I myself am maintainer for 0ad, hence why I'm interested in this bug report as well. My understanding is that Spidermonkey, as a standalone release (snapshot?) of FF's javascript engine, is meant to be embedded in applications that use it. I can't answer for all the packages above, but I know that 0ad requires a very specific version of Spidermonkey, and that transitioning between different releases seems to be rather painful for upstream. I guess one possible way to deal with this is to dump mozjs and mozjs17 (and future Spidermonkey releases) in the same category as webkit, i.e. unsupported by the security team? We can do that, but only as a matter of last resort. For practical purposes this will leave an endless amount of spidermonkey copies around. What other alternatives does the security team consider viable? My understanding is that spidermonkey has the same duration of support as the ESR release it was based on, so that's ~1 year. But unlike FF/Chromium, which we can continue pulling in new upstream releases to maintain security support during the lifecycle of a release, I'm not sure if that's doable with spidermonkey given all of the reverse dependencies that it has. And it would likely be an unsustainable burden on the security team and/or individual maintainers to backport changes to their packages in stable to make them work with newer spidermonkey releases, each time a new ESR release comes out and uploaded to stable. If no (standalone) spidermonkey copies were allowed into the archive, I suppose individual packages that depend on it would have to use an embedded copy instead...that's not ideal either. I can see the point for 0ad, but there needs to be some effort by apps to migrate to a proper supported version. 0ad upstream is already working (and making good progress) on migrating to ESR 24, and should be done in time for their next release. I can't speak on behalf of all the other packages that depend on spidermonkey currently though. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735600: marked as done (ekiga: Segmentation fault after libpt2.10.10 upgrade)
Your message dated Fri, 17 Jan 2014 09:40:41 + with message-id e1w45ur-0008sx...@franck.debian.org and subject line Bug#735600: fixed in ptlib 2.10.10~dfsg-4 has caused the Debian Bug report #735600, regarding ekiga: Segmentation fault after libpt2.10.10 upgrade 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.) -- 735600: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ekiga Version: 4.0.1-2+b2 Severity: grave Justification: renders package unusable After the upgrade of libpt2.10.10 from 2.10.10~dfsg-2.1 to 2.10.10~dfsg-3, Ekiga crashes on every startup, when it registers at ekiga.net. Downgrading to 2.10.10~dfsg-2.1 fixes the problem. Here is the gdb backtrace that led me to suspect libpt2: .. .. .. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffd4eb0700 (LWP 4753)] 0x73217621 in ?? () from /usr/lib/libpt.so.2.10.10 (gdb) bt #0 0x73217621 in ?? () from /usr/lib/libpt.so.2.10.10 #1 0x7321830f in PTimeParse () from /usr/lib/libpt.so.2.10.10 #2 0x73225b73 in PTime::ReadFrom(std::istream) () from /usr/lib/libpt.so.2.10.10 #3 0x73227263 in PTime::Parse(PString const) () from /usr/lib/libpt.so.2.10.10 #4 0x742f5815 in SIPPresenceInfo::ParseXML(PString const, std::listSIPPresenceInfo, std::allocatorSIPPresenceInfo , PString) () from /usr/lib/libopal.so.3.10.10 #5 0x74305723 in SIP_Presentity::OnPresenceNotify(SIPSubscribeHandler, SIPSubscribe::NotifyCallbackInfo) () from /usr/lib/libopal.so.3.10.10 #6 0x74310e3d in SIP_Presentity::OnPresenceNotify_PNotifier::Call(PObject, SIPSubscribe::NotifyCallbackInfo) const () from /usr/lib/libopal.so.3.10.10 #7 0x73f013dd in PNotifierTemplateSIPSubscribe::NotifyCallbackInfo::operator()(PObject, SIPSubscribe::NotifyCallbackInfo) const () from /usr/lib/libopal.so.3.10.10 #8 0x742f2c36 in SIPSubscribeHandler::DispatchNOTIFY(SIP_PDU, SIP_PDU) () from /usr/lib/libopal.so.3.10.10 #9 0x742f1e95 in SIPSubscribeHandler::OnReceivedNOTIFY(SIP_PDU) () from /usr/lib/libopal.so.3.10.10 #10 0x742939b4 in SIPEndPoint::OnReceivedNOTIFY(OpalTransport, SIP_PDU) () from /usr/lib/libopal.so.3.10.10 #11 0x74291689 in SIPEndPoint::OnReceivedConnectionlessPDU(OpalTransport, SIP_PDU*) () from /usr/lib/libopal.so.3.10.10 #12 0x74290e25 in SIPEndPoint::OnReceivedPDU(OpalTransport, SIP_PDU*) () from /usr/lib/libopal.so.3.10.10 #13 0x7428f2f9 in SIPEndPoint::HandlePDU(OpalTransport) () from /usr/lib/libopal.so.3.10.10 #14 0x7428df19 in SIPEndPoint::NewIncomingConnection(OpalTransport*) () from /usr/lib/libopal.so.3.10.10 #15 0x73e738fd in OpalEndPoint::ListenerCallback(PThread, long) () from /usr/lib/libopal.so.3.10.10 #16 0x73e75017 in OpalEndPoint::ListenerCallback_PNotifier::Call(PObject, long) const () from /usr/lib/libopal.so.3.10.10 #17 0x73ebe812 in OpalListener::ListenForConnections(PThread, long) () from /usr/lib/libopal.so.3.10.10 #18 0x73ec77af in OpalListener::ListenForConnections_PNotifier::Call(PObject, long) const () from /usr/lib/libopal.so.3.10.10 #19 0x731ffad2 in PThread::PX_ThreadStart(void*) () from /usr/lib/libpt.so.2.10.10 #20 0x71d6ee0e in start_thread (arg=0x7fffd4eb0700) at pthread_create.c:311 #21 0x71aa40fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 The output of ekiga -d 2 at the segfault is: $ ekiga -d 2 on Unix Linux (3.12-1-amd64-x86_64) with PTLib (v2.10.10 (svn:29149)) at 2014/1/16 19:46:48.675 2014/01/16 19:46:48.718 0:00.042 OpalPlugin Not adding H.323 capability for plugin codec MPEG4 as this has been specifically disabled 2014/01/16 19:46:48.722 0:00.046 PTLib No permission to set priority level 4 2014/01/16 19:46:48.722 0:00.046 PTLib No permission to set priority level 4 2014/01/16 19:46:48.722 0:00.046 PTLib No permission to set priority level 4 2014/01/16 19:46:48.724 0:00.048 PTLib No permission to set priority level 4 2014/01/16 19:46:48.725 0:00.049 HalManager_dbus Populating full device list failed - The name org.freedesktop.Hal was not provided by any .service files 2014/01/16 19:46:48.726 0:00.050 HalManager_dbus Populating full interface list failed - Method
Bug#735653: khronos-opencl-man: ruby1.8 won't be available on Jessie
Source: khronos-opencl-man Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, khronos-opencl-man produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#735650: ctioga2: ruby1.8 won't be available on Jessie
Source: ctioga2 Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, ctioga2 produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#735657: rbbr: ruby1.8 won't be available on Jessie
Source: rbbr Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, rbbr produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#735656: quickml: ruby1.8 won't be available on Jessie
Source: quickml Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, quickml produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#735654: libfilesystem-ruby: ruby1.8 won't be available on Jessie
Source: libfilesystem-ruby Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, libfilesystem-ruby produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#735658: rdtool: ruby1.8 won't be available on Jessie
Source: rdtool Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, rdtool produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#735659: remctl: ruby1.8 won't be available on Jessie
Source: remctl Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, remctl produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#735660: ruby-filesystem: ruby1.8 won't be available on Jessie
Source: ruby-filesystem Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, ruby-filesystem produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#735655: nadoka: ruby1.8 won't be available on Jessie
Source: nadoka Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, nadoka produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#735661: ruby-gnome2: ruby1.8 won't be available on Jessie
Source: ruby-gnome2 Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, ruby-gnome2 produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#735662: ruby-pkg-tools: ruby1.8 won't be available on Jessie
Source: ruby-pkg-tools Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, ruby-pkg-tools produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#735663: ruby-tioga: ruby1.8 won't be available on Jessie
Source: ruby-tioga Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, ruby-tioga produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#718444: ruby1.8 won't be available on Jessie
Dear maintainer, Your package still uses ruby1.8, which is unmaintainable at this point. We can't keep ruby1.8 around for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#730850: marked as done (libghc-xmonad-dev: is not installable)
Your message dated Fri, 17 Jan 2014 10:07:25 +
with message-id 1389953245.2519.4.camel@kirk
and subject line Pandoc has been uploaded, this can be closed
has caused the Debian Bug report #730850,
regarding libghc-xmonad-dev: is not installable
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.)
--
730850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libghc-xmonad-dev
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The libghc-xmonad-dev package is not installable because it depends on
a virtual package. Here is the log my attempt to install it:
balisto:~% apt-cache show libghc-xmonad-dev | grep Version
Version: 0.11-6
balisto:~% LANG=C sudo aptitude -R install libghc-xmonad-dev
The following NEW packages will be installed:
ghc{a} libbsd-dev{a} libghc-extensible-exceptions-dev{a} libghc-mtl-dev{a}
libghc-transformers-dev{a} libghc-utf8-string-dev{a} libghc-x11-dev{ab} libghc-xmonad-dev
libgmp-dev{a}
The following packages are RECOMMENDED but will NOT be installed:
libghc-xmonad-contrib-dev
0 packages upgraded, 9 newly installed, 0 to remove and 5 not upgraded.
Need to get 28.3 MB of archives. After unpacking 309 MB will be used.
The following packages have unmet dependencies:
libghc-x11-dev : Depends: libghc-data-default-dev-0.4.0-cf4a6 which is a
virtual package.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) libghc-x11-dev [Not Installed]
2) libghc-xmonad-dev [Not Installed]
Accept this solution? [Y/n/q/?]
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
(° Nicolas Évrard
( ) Liège
`¯
---End Message---
---BeginMessage---
Version: 0.11-6
Greetings,
Joachim
--
Joachim nomeata Breitner
Debian Developer
nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
signature.asc
Description: This is a digitally signed message part
---End Message---
Processed: severity of 718444 is serious, severity of 721618 is serious, severity of 722362 is serious ...
Processing commands for cont...@bugs.debian.org:
severity 718444 serious
Bug #718444 [ruby-krb5-auth] ruby-krb5-auth does not work with ruby 1.9
Severity set to 'serious' from 'grave'
severity 721618 serious
Bug #721618 [schleuder] Ruby 1.8 is going away
Ignoring request to change severity of Bug 721618 to the same value.
severity 722362 serious
Bug #722362 [libroot-bindings-ruby5.34] Updating the Ruby packaging policy for
your package «libroot-bindings-ruby5.34»
Severity set to 'serious' from 'normal'
severity 722364 serious
Bug #722364 [librdf-ruby] Updating the Ruby packaging policy for your package
«librdf-ruby»
Severity set to 'serious' from 'normal'
severity 722365 serious
Bug #722365 [libmaruku-ruby] Updating the Ruby packaging policy for your
package «libmaruku-ruby»
Severity set to 'serious' from 'normal'
severity 722366 serious
Bug #722366 [librfilter-ruby1.8] Updating the Ruby packaging policy for your
package «librfilter-ruby1.8»
Severity set to 'serious' from 'normal'
severity 722367 serious
Bug #722367 [libzip-ruby1.8] Updating the Ruby packaging policy for your
package «libzip-ruby1.8»
Severity set to 'serious' from 'normal'
severity 722369 serious
Bug #722369 [libhtml-htmltokenizer-ruby] Updating the Ruby packaging policy for
your package «libhtml-htmltokenizer-ruby»
Severity set to 'serious' from 'normal'
severity 722372 serious
Bug #722372 [libvorbisfile-ruby] Updating the Ruby packaging policy for your
package «libvorbisfile-ruby»
Severity set to 'serious' from 'normal'
severity 722374 serious
Bug #722374 [libraspell-ruby] Updating the Ruby packaging policy for your
package «libraspell-ruby»
Severity set to 'serious' from 'normal'
severity 722376 serious
Bug #722376 [libamazon-ruby] Updating the Ruby packaging policy for your
package «libamazon-ruby»
Severity set to 'serious' from 'normal'
severity 722377 serious
Bug #722377 [librrd-ruby] Updating the Ruby packaging policy for your package
«librrd-ruby»
Severity set to 'serious' from 'normal'
severity 722379 serious
Bug #722379 [libhdfeos5-ruby1.8] Updating the Ruby packaging policy for your
package «libhdfeos5-ruby1.8»
Ignoring request to change severity of Bug 722379 to the same value.
severity 722380 serious
Bug #722380 [libneedle-ruby] Updating the Ruby packaging policy for your
package «libneedle-ruby»
Severity set to 'serious' from 'normal'
severity 722381 serious
Bug #722381 [libhdfeos5-ruby] Updating the Ruby packaging policy for your
package «libhdfeos5-ruby»
Severity set to 'serious' from 'normal'
severity 722382 serious
Bug #722382 [libstfl-ruby] Updating the Ruby packaging policy for your package
«libstfl-ruby»
Ignoring request to change severity of Bug 722382 to the same value.
severity 722384 serious
Bug #722384 [libtcltk-ruby] Updating the Ruby packaging policy for your package
«libtcltk-ruby»
Severity set to 'serious' from 'normal'
severity 722387 serious
Bug #722387 [libroot-bindings-ruby-dev] Updating the Ruby packaging policy for
your package «libroot-bindings-ruby-dev»
Severity set to 'serious' from 'normal'
severity 722389 serious
Bug #722389 [libneedle-extras-ruby1.8] Updating the Ruby packaging policy for
your package «libneedle-extras-ruby1.8»
Severity set to 'serious' from 'normal'
severity 722390 serious
Bug #722390 [libobexftp-ruby] Updating the Ruby packaging policy for your
package «libobexftp-ruby»
Severity set to 'serious' from 'normal'
severity 722392 serious
Bug #722392 [libabstract-ruby] Updating the Ruby packaging policy for your
package «libabstract-ruby»
Severity set to 'serious' from 'normal'
severity 722396 serious
Bug #722396 [libgv-ruby] Updating the Ruby packaging policy for your package
«libgv-ruby»
Ignoring request to change severity of Bug 722396 to the same value.
severity 722625 serious
Bug #722625 {Done: James McCoy james...@debian.org} [ruby-svn] ruby-svn:
build with default ruby(1.9.1) instead of obsolete ruby1.8
Bug #722393 {Done: James McCoy james...@debian.org} [ruby-svn] Updating the
Ruby packaging policy for your package «libsvn-ruby»
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
severity 723642 serious
Bug #723642 [libcaca] libcaca: please drop ruby1.8-dev (to be removed from the
archive) as build-dep
Severity set to 'serious' from 'important'
severity 723648 serious
Bug #723648 [xdotool] xdotool: please build against ruby1.9.1
Severity set to 'serious' from 'important'
severity 730719 serious
Bug #730719 [ruby-xmmsclient] ruby-xmmsclient: please drop support for Ruby1.8
and build for Ruby 2.0
Severity set to 'serious' from 'important'
severity 730880 serious
Bug #730880 [src:stompserver] stompserver: FTBFS: Hard dependency on ruby1.8
Ignoring request to change severity of Bug 730880 to the same value.
severity 730943 serious
Bug #730943 [src:libnet-netrc-ruby] libnet-netrc-ruby: FTBFS: /usr/bin/ruby1.8:
No such file or directory -- debian-setup.rb (LoadError)
Ignoring request to change
Processed: jpoker: please stop depend on rubygems
Processing control commands: block 735576 with -1 Bug #735576 [rubygems] rubygems: Remove rubygems from the archive 735576 was blocked by: 735647 735579 735585 735576 was not blocking any bugs. Added blocking bug(s) of 735576: 735666 -- 735576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735576 735666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735666: jpoker: please stop depend on rubygems
Package: jpoker Severity: serious Justification: rubygems is to be removed Control: block 735576 with -1 Dear Maintainer, Your package build-depends on rubygems and/or rubygem1.8. Those packages were needed for ruby1.8 but newer versions of the interpreter already include rubygems. The source package rubygems is going to be removed from the archive in a couple of weeks. Please update your dependencies to get rid of them. Cheers, Cédric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735623: pdl: FTBFS on mips, powerpc, s390x, sparc, (ia64): testsuite failures
On Fri, Jan 17, 2014 at 03:30:49AM +0100, Andreas Beckmann wrote: pdl FTBFS with testsuite failures on several architectures These testsuite failures were actually there before, but I only now made a successful testsuite run _mandatory_ in the build process... (are they all big-endian architectures?): powerpc, mips, s390x, sparc are indeed big-endian. debian's ia64 port AFAIK uses little-endian mode. Besides the potential endianness issues, there is a bug hidden in the depths of PDL. To summarize [1]: In a couple of locations within the core, there is an assumption that double is the largest datatype and some return values are casted/converted to double. long long int is indeed longer than the mantissa of a double, so when the conversion happens and the value of the longlong is large, the least significant bits are lost. The address space layout on ia64 leads to large pointer addresses, leading to segfaults during the test suite run. In some sense, it is just by luck that the same does not happen to pointers on other 64bit architectures. And, as PDL is a language used in the context of numerical computation (think of it like MatLab/NumPy for perl), this implicit precision loss may also affect real calculations performed with it. [1] http://thread.gmane.org/gmane.comp.lang.perl.pdl.devel/5637/focus=5641 -- c u henning -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735667: ruby-opennebula: please stop depending on rubygems
Package: ruby-opennebula
Version: please stop depending on rubygems
Severity: serious
Justification: rubygems is to be removed
Control: block 735576 with -1
Dear Maintainer,
Please do not make ruby-opennebula on rubygems. The rubygems package is
useful only for ruby1.8 (newer versions of the Ruby interpreter ship
their own rubygems directly).
Ruby1.8 is to be removed from the archive soon, and rubygems even
sooner.
The patch below does the trick.
Cheers,
Cédric
--- opennebula-3.4.1/debian/control 2013-08-13 15:23:25.0 +0200
+++ opennebula-3.4.1-new/debian/control 2014-01-17 11:43:47.851880613 +0100
@@ -120,7 +120,6 @@
ruby-password,
ruby-sequel,
ruby-sqlite3,
- rubygems,
${misc:Depends},
${ruby:Depends}
Replaces: opennebula ( 3.2.1-1~)
signature.asc
Description: Digital signature
Processed: ruby-opennebula: please stop depending on rubygems
Processing control commands: block 735576 with -1 Bug #735576 [rubygems] rubygems: Remove rubygems from the archive 735576 was blocked by: 735579 735647 735666 735585 735576 was not blocking any bugs. Added blocking bug(s) of 735576: 735667 -- 735576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735576 735667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730880: marked as done (stompserver: FTBFS: Hard dependency on ruby1.8)
Your message dated Fri, 17 Jan 2014 10:49:17 + with message-id e1w46zf-0007sh...@franck.debian.org and subject line Bug#730880: fixed in stompserver 0.9.9gem-3 has caused the Debian Bug report #730880, regarding stompserver: FTBFS: Hard dependency on ruby1.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 730880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: stompserver Version: 0.9.9gem-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131128 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): fakeroot debian/rules binary dh binary --buildsystem=ruby --with ruby dh_testroot -O--buildsystem=ruby dh_prep -O--buildsystem=ruby dh_installdirs -O--buildsystem=ruby dh_auto_install -O--buildsystem=ruby /usr/lib/ruby/vendor_ruby/gem2deb.rb:17: warning: setting Encoding.default_external /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:31: warning: method redefined; discarding old visit_String /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:4: warning: previous definition of visit_String was here /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:39: warning: method redefined; discarding old register /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:12: warning: previous definition of register was here /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:43: warning: method redefined; discarding old format_time /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:16: warning: previous definition of format_time was here /usr/lib/ruby/1.9.1/rubygems/syck_hack.rb:115: warning: method redefined; discarding old to_s /usr/lib/ruby/1.9.1/rubygems/syck_hack.rb:44: warning: previous definition of to_s was here Entering dh_ruby --install install -d /«PKGBUILDDIR»/debian/stompserver/usr/bin install -D -m755 /«PKGBUILDDIR»/bin/stompserver /«PKGBUILDDIR»/debian/stompserver/usr/bin/stompserver install -d /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby install -D -m644 /«PKGBUILDDIR»/lib/stomp_server.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/test_server.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/test_server.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/protocols/http.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/protocols/http.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/protocols/stomp.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/protocols/stomp.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue/activerecord_queue.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue/activerecord_queue.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue/ar_message.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue/ar_message.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue/dbm_queue.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue/dbm_queue.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue/file_queue.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue/file_queue.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue/memory_queue.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue/memory_queue.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue_manager.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue_manager.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/stomp_auth.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/stomp_auth.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/stomp_frame.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/stomp_frame.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/stomp_id.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/stomp_id.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/stomp_user.rb /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/stomp_user.rb install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/topic_manager.rb
Processed: severity of 735585 is serious
Processing commands for cont...@bugs.debian.org: severity 735585 serious Bug #735585 [sisu] sisu: please do not depend on rubygems and depend on ruby | ruby-interpreter Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 735585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734371: lsb.pl not accessible?
Dear Klaus, Thank you for trying OpenRC out on Debian and sorry for the trouble. The bug is strange and I could not reproduce it on a box of single /. lsb.pl is used to convert from LSB init scripts to a set of shell declarations that OpenRC could understand, which is crucial in the second earliest boot stage of OpenRC. The error message indicates that lsb.pl is not accessible from /lib/rc/sh/gendepends.sh. Could you please paste the output of `dpkg -L openrc`, especially the location of lsb.pl? BTW, before the reboot, did openrc install well? If so, it has rc-update -u executed in postinst, which calls lsb.pl without a problem. I suspect /lib/rc/bin/lsb.pl is not yet mounted during early boot. But given /lib/rc/sh/gendepends.sh, at least /lib/rc is mounted. the source of the bug is out of my imagination now.. BTW++, the version 0.12.4+20131230-4 will soon be in the mirrors. Cheers, Benda -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735434: ruby1.8 won't be available on Jessie
Control: tag -1 + fixed-upstream Hi, Antonio Terceiro wrote: Your package still uses ruby1.8, which is unmaintainable at this point. We can't keep ruby1.8 around for Jessie. We plan to request its removal in 4 weeks. Despite there is no new upstream release yet (upstream website says 0.6 is 93% finished), the git repository at https://gitorious.org/ditz/mainline seems to work with at least 1.9.x if not even with 2.0 since a branch called ruby2 has been merged 5 months ago. See also https://gitorious.org/ditz Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735668: missing license in debian/copyright
Package: fwknop Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please update debian/copyright of your package. For example fwknop-2.6.0/android/* is licensed under GPLv3+. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#735434: ruby1.8 won't be available on Jessie
Processing control commands: tag -1 + fixed-upstream Bug #735434 [ditz] ditz: Please migrate to Ruby 1.9/2.0 Added tag(s) fixed-upstream. -- 735434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): no longer blocked by #720816
Processing control commands:
merge -1 718385
Bug #719396 [src:libcitygml] libcitygml: FTBFS: debian/gencontrol: 6:
debian/gencontrol: Illegal number: 0~rc1
Unable to merge bugs because:
affects of #718385 is 'openscenegraph-plugin-citygml-static' not ''
Failed to merge 719396: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x3071508)',
'requester', 'Rebecca N. Palmer r.pal...@bham.ac.uk', 'request_addr',
'719396-sub...@bugs.debian.org', 'request_msgid',
'52d90df7.2010...@bham.ac.uk', 'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
Debbugs::Control::Service::control_line('line', 'merge -1 718385',
'clonebugs', 'HASH(0x3088af8)', 'limit', 'HASH(0x3088d20)',
'common_control_options', 'ARRAY(0x3088df8)', 'errors', ...) called at
/usr/lib/debbugs/process line 1039
--
718385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718385
719396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719396: no longer blocked by #720816
Control: merge -1 718385 openscenegraph is now installable again, still with an ~rc version. Note that this assumes that release candidates are sufficiently compatible with the corresponding final versions. They have different sonames (libopenscenegraph99/100 in the present case), but this *appears* to be a standard this is not the final release notice rather than a real API break. Note however that the libopenscenegraph-dev package no longer contains static libraries at all since 3.2.0~rc1-1, so if that's what -static in the package name means, that part will have to go altogether. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734371: lsb.pl not accessible?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Benda, thanks for your answer. Am Fr den 17. Jan 2014 um 11:47 schrieb hero...@gentoo.org: Thank you for trying OpenRC out on Debian and sorry for the trouble. I would like to see a working init (and rc) system in future debian as an alternative to the broken design of upstart and systemd. So I have a high interest in this package. The bug is strange and I could not reproduce it on a box of single /. Well, I have no single /, I did try it on my laptop where I have the following disk layout: /dev/rootxfs ... / devtmpfs devtmpfs ... /dev tmpfstmpfs ... /run tmpfstmpfs ... /run/lock tmpfstmpfs ... /run/shm /dev/mapper/crypt0 btrfs ... /home /dev/mapper/sysvg-lv_usr btrfs ... /usr /dev/mapper/sysvg-lv_var btrfs ... /var tmpfstmpfs ... /tmp tmpfstmpfs ... /media none tmpfs ... /sys/fs/cgroup So you can see that my /usr is separated from /. Moreover I do not use initrd than booting direct in my kernel. (I have only little machines booting with the normal debian kernel. Most have a optimized kernel for the system without initrd.) lsb.pl is used to convert from LSB init scripts to a set of shell declarations that OpenRC could understand, which is crucial in the second earliest boot stage of OpenRC. Hmm... The error message indicates that lsb.pl is not accessible from /lib/rc/sh/gendepends.sh. Could you please paste the output of `dpkg -L openrc`, especially the location of lsb.pl? I'll try to build a test kvm to do this. As you might expect, I will be a bit more cautiously with my running laptop. :-) BTW, before the reboot, did openrc install well? I looked as it was. I was warned by Axel that there could be some problems so I did check. If so, it has rc-update -u executed in postinst, which calls lsb.pl without a problem. I suspect /lib/rc/bin/lsb.pl is not yet mounted during early boot. But given /lib/rc/sh/gendepends.sh, at least /lib/rc is mounted. the source of the bug is out of my imagination now.. As you can see above, /lib is not separated (and I do not know how it could work with a separated /lib). But maybe openrc expects to run from initrd? Gruß Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJS2RBvAAoJEKZ8CrGAGfas8ZwL/RTNMi4Jk2GDtjPoAGdAS9K8 pUUK6blaZs92g2s9ESwSIjUel2DHXk0N2J4OXboGeEIvwzIEJ8jscoKfPLkXSOox 6NxP4wx1d7RAWLUc8OKf6i49qElomNH5pDTCjsss73fJ9rfPzsx59dXoX6umFAbJ 8PNKVE2U3XST8RGX3cQuXR9VrFHcl30w1wW5Mubfyng5RL5NnzgfZe8X1JXfzXTv NzYCclmM3cJNUuInOG8URMzVsYMM1rU/74r4FGAD3Ga0DWR1x8A7S3VoudAQ+z3z GIHHZWU8PdR7myTIn0bF2fkGGR4mPGQ7OQtB+Tz8VldlUrCkBAZBA1qBbEKbAmfy tWLtqUVMPYFxQYzmpb9DkssSWKR8qHnQwx27FlqlMxrGO82KQo0BbaqTyKd5drKX WwUOH58TgHRQlSGjTaCtC/+XATcZ8tjwqj7afNU3qN1klUJRncqgeQhdMgUI+CUw A7ItM8/RnVEOOish/02QfjLcUgRwAqbwhdlbCNxihQ== =6N/9 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: affects 733423
Processing commands for cont...@bugs.debian.org: affects 733423 ruby-fixture-builder Bug #733423 [ruby-activesupport-3.2] ruby-activesupport-3.2 should depend on ruby-minitest Added indication that 733423 affects ruby-fixture-builder thanks Stopping processing here. Please contact me if you need assistance. -- 733423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): retry failed merges
Processing commands for cont...@bugs.debian.org:
merge 704713 732848
Bug #704713 [src:gimp-plugin-registry] gimp-plugin-registry: fails to build
with ld --no-add-needed
Bug #723875 [src:gimp-plugin-registry] FTBFS: /usr/bin/ld: brush.o: undefined
reference to symbol 'hypotf@@GLIBC_2.2.5'
Unable to merge bugs because:
package of #732848 is 'gimp-plugin-registry' not 'src:gimp-plugin-registry'
Failed to merge 704713: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x331a718)',
'requester', 'Rebecca N. Palmer r.pal...@bham.ac.uk', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid', '52d91cfc.2090...@bham.ac.uk',
'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
Debbugs::Control::Service::control_line('line', undef, 'clonebugs',
'HASH(0x329c4c8)', 'limit', 'HASH(0x32927e8)', 'common_control_options',
'ARRAY(0x3292830)', 'errors', ...) called at /usr/lib/debbugs/service line 474
affects 719396 openscenegraph-plugin-citygml-static
Bug #719396 [src:libcitygml] libcitygml: FTBFS: debian/gencontrol: 6:
debian/gencontrol: Illegal number: 0~rc1
Added indication that 719396 affects openscenegraph-plugin-citygml-static
merge 719396 718385
Bug #719396 [src:libcitygml] libcitygml: FTBFS: debian/gencontrol: 6:
debian/gencontrol: Illegal number: 0~rc1
Bug #718385 [src:libcitygml] libcitygml: Please recompile against
OpenSceneGraph 3.2
Added tag(s) patch.
Merged 718385 719396
End of message, stopping processing here.
Please contact me if you need assistance.
--
704713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704713
718385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718385
719396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719396
723875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723875
732848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 735614 in 1.1.0-22, found 735649 in 2.0.2+dfsg.1-3, tagging 735649, found 735650 in 0.8-1 ...
Processing commands for cont...@bugs.debian.org:
found 735614 1.1.0-22
Bug #735614 {Done: Dmitry Smirnov only...@debian.org} [ifenslave] ifenslave:
properly transition from ifenslave-2.6 to ifenslave
There is no source info for the package 'ifenslave' at version '1.1.0-22' with
architecture ''
Unable to make a source version for version '1.1.0-22'
Marked as found in versions 1.1.0-22.
found 735649 2.0.2+dfsg.1-3
Bug #735649 [ruby-amrita2] ruby-amrita2: FTBFS: does not work with newer rubies
version
Marked as found in versions ruby-amrita2/2.0.2+dfsg.1-3.
tags 735649 + jessie sid
Bug #735649 [ruby-amrita2] ruby-amrita2: FTBFS: does not work with newer rubies
version
Added tag(s) sid and jessie.
found 735650 0.8-1
Bug #735650 [src:ctioga2] ctioga2: ruby1.8 won't be available on Jessie
Marked as found in versions ctioga2/0.8-1.
found 735652 3.4.2-1
Bug #735652 [src:geos] geos: ruby1.8 won't be available on Jessie
Marked as found in versions geos/3.4.2-1.
found 735654 0.5-3.1
Bug #735654 [src:libfilesystem-ruby] libfilesystem-ruby: ruby1.8 won't be
available on Jessie
Marked as found in versions libfilesystem-ruby/0.5-3.1.
tags 735654 + jessie sid
Bug #735654 [src:libfilesystem-ruby] libfilesystem-ruby: ruby1.8 won't be
available on Jessie
Added tag(s) sid and jessie.
found 735655 0.7.6-1
Bug #735655 [src:nadoka] nadoka: ruby1.8 won't be available on Jessie
Marked as found in versions nadoka/0.7.6-1.
tags 735655 + jessie sid
Bug #735655 [src:nadoka] nadoka: ruby1.8 won't be available on Jessie
Added tag(s) sid and jessie.
found 735656 0.7-4
Bug #735656 [src:quickml] quickml: ruby1.8 won't be available on Jessie
Marked as found in versions quickml/0.7-4.
tags 735656 + jessie sid
Bug #735656 [src:quickml] quickml: ruby1.8 won't be available on Jessie
Added tag(s) sid and jessie.
found 735658 0.6.38-1
Bug #735658 [src:rdtool] rdtool: ruby1.8 won't be available on Jessie
Marked as found in versions rdtool/0.6.38-1.
found 735659 3.6-1
Bug #735659 [src:remctl] remctl: ruby1.8 won't be available on Jessie
Marked as found in versions remctl/3.6-1.
found 735661 1.1.3-2
Bug #735661 [src:ruby-gnome2] ruby-gnome2: ruby1.8 won't be available on Jessie
Marked as found in versions ruby-gnome2/1.1.3-2.
tags 735661 + sid
Bug #735661 [src:ruby-gnome2] ruby-gnome2: ruby1.8 won't be available on Jessie
Added tag(s) sid.
found 735662 0.20
Bug #735662 [src:ruby-pkg-tools] ruby-pkg-tools: ruby1.8 won't be available on
Jessie
Marked as found in versions ruby-pkg-tools/0.20.
found 735663 1.17-1
Bug #735663 [src:ruby-tioga] ruby-tioga: ruby1.8 won't be available on Jessie
Marked as found in versions ruby-tioga/1.17-1.
found 722362 5.34.14-1
Bug #722362 [libroot-bindings-ruby5.34] Updating the Ruby packaging policy for
your package «libroot-bindings-ruby5.34»
Marked as found in versions root-system/5.34.14-1.
found 722364 1.0.16.1-1
Bug #722364 [librdf-ruby] Updating the Ruby packaging policy for your package
«librdf-ruby»
Marked as found in versions redland-bindings/1.0.16.1-1.
found 722365 0.6.0-2
Bug #722365 [libmaruku-ruby] Updating the Ruby packaging policy for your
package «libmaruku-ruby»
Marked as found in versions ruby-maruku/0.6.0-2.
tags 722365 + jessie sid
Bug #722365 [libmaruku-ruby] Updating the Ruby packaging policy for your
package «libmaruku-ruby»
Added tag(s) sid and jessie.
found 722367 0.9.4-1
Bug #722367 [libzip-ruby1.8] Updating the Ruby packaging policy for your
package «libzip-ruby1.8»
Marked as found in versions libzip-ruby/0.9.4-1.
tags 722367 + sid
Bug #722367 [libzip-ruby1.8] Updating the Ruby packaging policy for your
package «libzip-ruby1.8»
Added tag(s) sid.
found 722366 0.12-2
Bug #722366 [librfilter-ruby1.8] Updating the Ruby packaging policy for your
package «librfilter-ruby1.8»
Marked as found in versions rubyfilter/0.12-2.
tags 722366 + jessie sid
Bug #722366 [librfilter-ruby1.8] Updating the Ruby packaging policy for your
package «librfilter-ruby1.8»
Added tag(s) sid and jessie.
found 722369 1.0-3
Bug #722369 [libhtml-htmltokenizer-ruby] Updating the Ruby packaging policy for
your package «libhtml-htmltokenizer-ruby»
Marked as found in versions libhtml-htmltokenizer-ruby/1.0-3.
tags 722369 + jessie sid
Bug #722369 [libhtml-htmltokenizer-ruby] Updating the Ruby packaging policy for
your package «libhtml-htmltokenizer-ruby»
Added tag(s) sid and jessie.
found 722372 0.2-8.1
Bug #722372 [libvorbisfile-ruby] Updating the Ruby packaging policy for your
package «libvorbisfile-ruby»
Marked as found in versions libvorbisfile-ruby/0.2-8.1.
tags 722372 + jessie sid
Bug #722372 [libvorbisfile-ruby] Updating the Ruby packaging policy for your
package «libvorbisfile-ruby»
Added tag(s) sid and jessie.
found 722374 1.2-2
Bug #722374 [libraspell-ruby] Updating the Ruby packaging policy for your
package «libraspell-ruby»
Marked as found in versions raspell/1.2-2.
tags 722374 + jessie sid
Bug #722374 [libraspell-ruby] Updating the Ruby packaging policy for your
Bug#734346: marked as done (qdbm: Please migrate to Ruby 1.9/2.0)
Your message dated Fri, 17 Jan 2014 12:13:24 + with message-id e1w48ie-000559...@franck.debian.org and subject line Bug#734346: fixed in qdbm 1.8.78-3 has caused the Debian Bug report #734346, regarding qdbm: Please migrate to Ruby 1.9/2.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.) -- 734346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: qdbm Severity: normal Dear Maintainer, Binaries built from your source package qdbm depend on ruby1.8, an obsolete version of the Ruby interpreter. The Debian Ruby team is willing to remove this version soon from jessie and sid. Please migrate to Ruby 1.9 and/or 2.0 (and remove dependencies on 1.8) to ensure your package continues to be installable. Thank you, Christian ---End Message--- ---BeginMessage--- Source: qdbm Source-Version: 1.8.78-3 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 734...@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, 07 Jan 2014 20:59:20 +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 all i386 Version: 1.8.78-3 Distribution: unstable Urgency: low 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: 734346 Changes: qdbm (1.8.78-3) unstable; urgency=low . * Drop ruby1.8 bindings. (Closes: #734346) Checksums-Sha1: 09fdec2583ce0e4c8d8e6c7dc805c39efaccfb24 2427 qdbm_1.8.78-3.dsc 69527fa27bd0ae278ea7235f16dff55c68972988 18572 qdbm_1.8.78-3.debian.tar.gz 160e3940cdae39332a62a7968bc04d76730668dd 212178 qdbm-doc_1.8.78-3_all.deb 0a3de33b0b33fa84109c6ee2458a265db9c95379 110758 libqdbm14_1.8.78-3_i386.deb 1bbe7d6ef8d926ef49ad67782202e98c6e418224 168050 libqdbm-dev_1.8.78-3_i386.deb 04e8f350bfe0fd72ad847988d7dbc988b3acdd29 72972 qdbm-util_1.8.78-3_i386.deb 731dcd6569e83d40b3734798fcc3c27129570c07 31066 qdbm-cgi_1.8.78-3_i386.deb 8616239822c576ef68570ea279878bf77f6c2794 102856 libxqdbm3c2_1.8.78-3_i386.deb 9391df5d533523625e4b1b913f1ce3ad6d758e57 34610 libxqdbm-dev_1.8.78-3_i386.deb d3c61a0bf680bf9ee85ea64b9aba1ba3fb75ac30 9016 libqdbm3++c2_1.8.78-3_i386.deb db23387cd05cb2da7f558794df087c254dbf31b4 9192 libqdbm++-dev_1.8.78-3_i386.deb 2152c0816346e9c7c221485fd736bc8183b928cb 40506 libqdbm-perl_1.8.78-3_i386.deb 15270b39b8337daa1d737cdf31088bc424d68d01 26572 ruby-qdbm_1.8.78-3_i386.deb 18bbe127f3cad0c865d0cb3c62fa3a6511d4be19 44326 libqdbm-java_1.8.78-3_i386.deb Checksums-Sha256: 4a63e57c145bbdd10b39c71f6af9b3190e975d95a166c343b229d6d94e0e4fb0 2427 qdbm_1.8.78-3.dsc 43b8cabb1a31506c567d98f6801635e28ec38bf1cdd3776a380684ada32cf8b9 18572 qdbm_1.8.78-3.debian.tar.gz c82bda2afd98be84b1dae7a47ad388c163b676de5830656bf15c862bbc987ce4 212178 qdbm-doc_1.8.78-3_all.deb d7738298e1198e46181fd1e757b7252b36457ed23dd80e8c34148e6b615542f7 110758 libqdbm14_1.8.78-3_i386.deb 2ae4904634f574be37f2a91b6ad0444c25a082c03c720539a6565a495a616dd2 168050 libqdbm-dev_1.8.78-3_i386.deb 9c3dbccee8fd26e183a618480fcb554b4072ef7c719b479997ade7af8ee54bd9 72972 qdbm-util_1.8.78-3_i386.deb
Bug#734371: perl is inside /usr/bin
Dear Klaus, I figured out the cause: perl, by which lsb.pl is written, is inside /usr. Roger has expressed this concern before. I did not take it seriously at that time. Now it bites us.. We should rewrite lsb.pl with POSIX shell or even C, or rely on functions from insserv (which has a LSB parser) to get rid of this extra dependency on perl. @Roger, is it easy to borrow the LSB parser from insserv? For the moment, you could have an ugly hack to copy a subsystem of perl over /. I would like to see a working init (and rc) system in future debian as an alternative to the broken design of upstart and systemd. So I have a high interest in this package. Great, I have exactly the same motivation. Cheers, Benda -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709877: marked as done (spotweb: fails to install, purge, and install again)
Your message dated Fri, 17 Jan 2014 12:22:18 +
with message-id e1w48rg-0006vr...@franck.debian.org
and subject line Bug#709877: fixed in spotweb 20130826+dfsg2-1
has caused the Debian Bug report #709877,
regarding spotweb: fails to install, purge, and install again
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.)
--
709877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: spotweb
Version: 20111002+dfsg-4.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install,
remove+purge, and install again.
Like a plain failure on initial install this makes the package too buggy
for a release, thus the severity.
This is often a problem with the home directory of a system user:
the user is not deleted during purge (which is fine), but the home
directory is removed. Since the user already exists on the next
installation, adduser won't recreate the home.
From the attached log (scroll to the bottom...):
Selecting previously unselected package spotweb.
(Reading database ... 11023 files and directories currently installed.)
Unpacking spotweb (from .../spotweb_20111002+dfsg-4.1_all.deb) ...
Setting up spotweb (20111002+dfsg-4.1) ...
dbconfig-common: writing config to /etc/dbconfig-common/spotweb.conf
Creating config file /etc/dbconfig-common/spotweb.conf with new version
Creating config file /etc/spotweb/dbconfig.php with new version
granting access to database spotweb for spotweb@localhost: already exists.
creating database spotweb: already exists.
dbconfig-common: flushing administrative password
Creating config file /etc/spotweb/nntpconfig.php with new version
Updating schema..(mysql)
Database schema of settings upgrade mislukt:
Unable to connect to MySQL server: Access denied for user
'spotweb'@'localhost' (using password: YES)
#0 /usr/share/spotweb/lib/SpotDb.php(59): dbeng_mysql-connect()
#1 /usr/share/spotweb/lib/SpotUpgrader.php(9): SpotDb-connect()
#2 /usr/share/spotweb/scripts/upgrade-db.php(21):
SpotUpgrader-__construct(Array)
#3 {main}dpkg: error processing spotweb (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
spotweb
cheers,
Andreas
spotweb_20111002+dfsg-4.1.log.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: spotweb
Source-Version: 20130826+dfsg2-1
We believe that the bug you reported is fixed in the latest version of
spotweb, 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 709...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jan-Pascal van Best janpas...@vanbest.org (supplier of updated spotweb
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 17 Jan 2014 11:51:12 +0100
Source: spotweb
Binary: spotweb
Architecture: source all
Version: 20130826+dfsg2-1
Distribution: unstable
Urgency: low
Maintainer: Jan-Pascal van Best janpas...@vanbest.org
Changed-By: Jan-Pascal van Best janpas...@vanbest.org
Description:
spotweb- web interface to search and filter Usenet spots
Closes: 662123 669806 709877 718528 722404
Changes:
spotweb (20130826+dfsg2-1) unstable; urgency=low
.
* New upstream version (v20130826)
* Updated debian/copyright
* Update README.source and get-orig-source
* Add upstream changelog
* Updates for Apache 2.4 configuration snippets. Closes: #669806
* Use Debian-supplied jquery-form javascript library instead of upstream
embedded version.
* Remove upstream embedded font files, use Debian-packaged fonts instead.
* The news server information is now maintained in the spotweb database, and
not in the configuration files. That means you will need to configure your
news server information again (admin/config/settings/newsservers).
* Disable Notifo notifications, the service has been discontinued.
* Do not exit postinst script with error if database update fails.
Closes: #709877
* Have
Bug#734715: cpushare: diff for NMU version 0.48-4.1
Control: tag -1 pending Dear maintainer, I've prepared an NMU for cpushare (versioned as 0.48-4.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, -- Colin Watson [cjwat...@debian.org] diff -u cpushare-0.48/debian/cpushare.init cpushare-0.48/debian/cpushare.init --- cpushare-0.48/debian/cpushare.init +++ cpushare-0.48/debian/cpushare.init @@ -39,7 +39,7 @@ case $1 in start) log_begin_msg Starting CPUShare daemon... - if ! su nobody -c /usr/lib/cpushare/seccomp-test /dev/null 21; then + if ! su nobody -s /bin/sh -c /usr/lib/cpushare/seccomp-test /dev/null 21; then log_begin_msg kernel was not built with CONFIG_SECCOMP=y log_end_msg 1 exit 0 diff -u cpushare-0.48/debian/changelog cpushare-0.48/debian/changelog --- cpushare-0.48/debian/changelog +++ cpushare-0.48/debian/changelog @@ -1,3 +1,11 @@ +cpushare (0.48-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Pass -s /bin/sh to su nobody to cope with the change of nobody's +shell in base-passwd 3.5.30 (closes: #734715). + + -- Colin Watson cjwat...@debian.org Fri, 17 Jan 2014 11:57:04 + + cpushare (0.48-4) unstable; urgency=low * debian/.noinit: added content to this file because dpkg-buildpackage
Processed: cpushare: diff for NMU version 0.48-4.1
Processing control commands: tag -1 pending Bug #734715 [cpushare] cpushare: fails to start due to change in nobody's shell Added tag(s) pending. -- 734715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: retry failed merges
Processing commands for cont...@bugs.debian.org: reassign 704713 gimp-plugin-registry 5.20120621 Bug #704713 [src:gimp-plugin-registry] gimp-plugin-registry: fails to build with ld --no-add-needed Bug #723875 [src:gimp-plugin-registry] FTBFS: /usr/bin/ld: brush.o: undefined reference to symbol 'hypotf@@GLIBC_2.2.5' Bug reassigned from package 'src:gimp-plugin-registry' to 'gimp-plugin-registry'. Bug reassigned from package 'src:gimp-plugin-registry' to 'gimp-plugin-registry'. No longer marked as found in versions gimp-plugin-registry/5.20120621. No longer marked as found in versions gimp-plugin-registry/5.20120621. Ignoring request to alter fixed versions of bug #704713 to the same values previously set Ignoring request to alter fixed versions of bug #723875 to the same values previously set Bug #704713 [gimp-plugin-registry] gimp-plugin-registry: fails to build with ld --no-add-needed Bug #723875 [gimp-plugin-registry] FTBFS: /usr/bin/ld: brush.o: undefined reference to symbol 'hypotf@@GLIBC_2.2.5' Marked as found in versions gimp-plugin-registry/5.20120621. Marked as found in versions gimp-plugin-registry/5.20120621. merge 704713 732848 Bug #704713 [gimp-plugin-registry] gimp-plugin-registry: fails to build with ld --no-add-needed Bug #723875 [gimp-plugin-registry] FTBFS: /usr/bin/ld: brush.o: undefined reference to symbol 'hypotf@@GLIBC_2.2.5' Bug #732848 [gimp-plugin-registry] gimp-plugin-registry: Packages uninstallable Added tag(s) patch. Bug #723875 [gimp-plugin-registry] FTBFS: /usr/bin/ld: brush.o: undefined reference to symbol 'hypotf@@GLIBC_2.2.5' Merged 704713 723875 732848 End of message, stopping processing here. Please contact me if you need assistance. -- 704713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704713 723875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723875 732848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734371: Problem is that perl isn't available
Hi, Your problem is that, when lsb.pl starts, it needs /usr/bin/perl. So we have no choice here, but to re-write lsb.pl completely in another language. Our options would be: 1/ POSIX shell 2/ C (with possibilities to steal the LSB parser from insserv) We'll work on it, it shouldn't be that hard, the lsb.pl script is quite small. Help would of course be welcome. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713449: (no subject)
This issue has been fixed in qpid 0.22 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734719: distributed-net: fails to install due to change in daemon's shell
On Sat, Jan 11, 2014 at 06:01:11PM -0500, James Stark wrote: I have no objections to an NMU on this one, however I think that I may be able to deal with it today or tomorrow. I have been planning an update for a while now, but I've been distracted by writing a thesis. I'll look at getting this bug fixed, and bringing the package up to date, along with the output of lintian. #655922 will have to wait for a future upload. This is now the last non-pending bug blocking #734946; please let me know if there's anything I can do to help. Thanks, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: forwarded 713449 https://issues.apache.org/jira/browse/QPID-4579 Bug #713449 [src:qpid-cpp] qpid-cpp: FTBFS: ./qpid/framing/Handler.h:52:47: error: invalid use of incomplete type 'struct qpid::framing::HandlerT' [-Werror] Set Bug forwarded-to-address to 'https://issues.apache.org/jira/browse/QPID-4579'. End of message, stopping processing here. Please contact me if you need assistance. -- 713449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731461: marked as done (libre2-dev: Unit test parse_test fails causing FTBFS)
Your message dated Fri, 17 Jan 2014 13:00:28 + with message-id e1w492c-0005w3...@franck.debian.org and subject line Bug#731461: fixed in re2 20140111+dfsg-1 has caused the Debian Bug report #731461, regarding libre2-dev: Unit test parse_test fails causing FTBFS 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.) -- 731461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libre2-dev Version: 0+hg80+dfsg-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, When building with debuild -us -uc -b, I got: g++ -o obj/re2/testing/parse_test.o -D_FORTIFY_SOURCE=2 -g -O3 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -pthread -Wno-sign-compare -c -I.-DNDEBUG re2/testing/parse_test.cc g++ -o obj/test/parse_test obj/re2/testing/parse_test.o obj/util/pcre.o obj/util/random.o obj/util/thread.o obj/re2/testing/backtrack.o obj/re2/testing/dump.o obj/re2/testing/exhaustive_tester.o obj/re2/testing/null_walker.o obj/re2/testing/regexp_generator.o obj/re2/testing/string_generator.o obj/re2/testing/tester.o obj/util/test.o obj/libre2.a -Wl,-z,relro -pthread obj/test/parse_test running ... obj/test/parse_test FAIL; Output: TestParse.SimpleRegexps make[2]: *** [obj/test/parse_test.log] Erreur 1 make[2]: quittant le répertoire « /home/calixte/debian/re2-0+hg80+dfsg » dh_auto_test: make -j1 test CXXFLAGS=-g -O3 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -pthread LDFLAGS=-Wl,-z,relro -pthread CPPFLAGS=-D_FORTIFY_SOURCE=2 returned exit code 2 make[1]: *** [override_dh_auto_test] Erreur 2 make[1]: quittant le répertoire « /home/calixte/debian/re2-0+hg80+dfsg » make: *** [build] Erreur 2 dpkg-buildpackage: erreur: debian/rules build a produit une erreur de sortie de type 2 debuild: fatal error at line 1361: dpkg-buildpackage -rfakeroot -D -us -uc -b failed -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (988, 'testing'), (986, 'testing'), (982, 'stable'), (978, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information ---End Message--- ---BeginMessage--- Source: re2 Source-Version: 20140111+dfsg-1 We believe that the bug you reported is fixed in the latest version of re2, 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 731...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera stefa...@debian.org (supplier of updated re2 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: Thu, 16 Jan 2014 23:34:30 +0200 Source: re2 Binary: libre2-1 libre2-1-dbg libre2-dev Architecture: source amd64 Version: 20140111+dfsg-1 Distribution: experimental Urgency: low Maintainer: Stefano Rivera stefa...@debian.org Changed-By: Stefano Rivera stefa...@debian.org Description: libre2-1 - efficient, principled regular expression library libre2-1-dbg - efficient, principled regular expression library, debugging symbo libre2-dev - efficient, principled regular expression library, development kit Closes: 728090 731461 731475 Changes: re2 (20140111+dfsg-1) experimental; urgency=low . * New upstream version (Closes: #728090). - Upstream now provides date-based releases, switch to them. - Refresh patches. * Bump Standards-Version to 3.9.5. * Add -Wall to CXXFLAGS * Use valgrind headers on mips. * Drop Jakub from Uploaders, at his request. * perl-5.18.diff: The vertical tab \cK (0x0b) is matched by \s. Update test_parse to be aware of this. (Closes: #731461) * FLAGS_filtered_re2_min_atom_len.diff: Export a flag symbol, fixing a unit test failure. * Build a shared library again. (Closes: #731475) - This time, multi-arch: + Build-Depends on dpkg-dev (= 1.16~). * Bump debhelper compat level to 9. This adds a bunch of
Bug#734371: perl is inside /usr/bin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am Fr den 17. Jan 2014 um 13:24 schrieb hero...@gentoo.org: I figured out the cause: perl, by which lsb.pl is written, is inside /usr. Ah, ok. We should rewrite lsb.pl with POSIX shell or even C, or rely on functions from insserv (which has a LSB parser) to get rid of this extra dependency on perl. @Roger, is it easy to borrow the LSB parser from insserv? I like perl and think that it is great and safe for system administration. But in this case I also think it should be plain POSIX shell script. Even if that mean to be very carefully with variables and its content. For the moment, you could have an ugly hack to copy a subsystem of perl over /. I don't think that this work. You have to have all dependencies (libraries and perl modules) also ported to /. And that would be a big job. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJS2Sp6AAoJEKZ8CrGAGfasJfYL/0ed2PsPfYv8uQ011l5zrvFh EjsHVg18/5JZSgWxiDgGGz0G+8SaLGAa58rixUPomfo1BN75jTMgZ+/jgzwIb78L 5UgyiYJpbijkgcaR0gVwcfRxfJOOutjmMgaHklF7cyHzj7BNdZwLCpZnb/U6HvAP 7lxMe7HtLtjVHA1AVYjmaXSfw5znU2a9NM+Ry9M2tY0plV6q4jnAOk13XZWp5OhH QaB9GFy9rfEtM8nMWZIJsjpEY0tlKCMyAlqZzwwPopdUuKXFHudeD7wd7Fne1SNG SIKopJP9oxafFXhfU12YviW0v8MTVUAGr1Wnw8vMrpCNkk6u0OnfdeubZa0Njtfd WQmkYG557IYTNKko04NDK+zwCj9bTaw3xyVPx9ne45fCpwIlMr750fX1vFO5bAPN 7CtRlHLt2sMDW/T5PbMEqCOhYMpMYyfbr1VFIqavieEI51yN7S+EP6of/9buuuAF ZYhVYI+0F/Z/7tuKy1U1qwzC+NCWIG8AvUMb1jCjeA== =haxW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735585: sisu: please do not depend on rubygems and depend on ruby | ruby-interpreter
Package: sisu
Followup-For: Bug #735585
Dear Maintainer,
The changes to make it run with the default interpreter (ruby1.9.1 is
going away at some point before jessie) are a bit larger than the ones I
mentionned in my previous patch.
Please find attached a debdiff fixing this issue.
Unless you say otherwise, I consider sending an NMU next week to
DELAYED/5 to fix this problem and be able to remove rubygems.
Thanks!
Cédric
diff -Nru sisu-4.2.18/debian/changelog sisu-4.2.18/debian/changelog
--- sisu-4.2.18/debian/changelog2014-01-13 03:31:34.0 +0100
+++ sisu-4.2.18/debian/changelog2014-01-17 12:54:32.0 +0100
@@ -1,3 +1,12 @@
+sisu (4.2.18-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop unneeded dependency on rubygems (Closes: #735585)
+ * Depend on the default Ruby interpreter instead of ruby1.9.1
+ * Use upstream version of bin/sisu with the default ruby shebang
+
+ -- Cédric Boutillier bou...@debian.org Fri, 17 Jan 2014 11:58:50 +0100
+
sisu (4.2.18-1) unstable; urgency=medium
[ Ralph Amissah ]
diff -Nru sisu-4.2.18/debian/control sisu-4.2.18/debian/control
--- sisu-4.2.18/debian/control 2014-01-13 03:31:34.0 +0100
+++ sisu-4.2.18/debian/control 2014-01-17 12:29:11.0 +0100
@@ -11,11 +11,11 @@
Package: sisu
Architecture: all
-Depends: ${misc:Depends}, ruby1.9.1 (= 1.9.2.180), rsync, unzip, zip
+Depends: ${misc:Depends}, ruby | ruby-interpreter, rsync, unzip, zip
Recommends:
sisu-pdf, sisu-sqlite, sisu-postgresql, imagemagick | graphicsmagick,
keychain,
openssl, openssh-client | lsh-client, po4a, qrencode, rake, ruby-rmagick,
- rubygems, tidy, tree, vim-addon-manager
+ tidy, tree, vim-addon-manager
Suggests: lv, calibre, pinfo, poedit, texinfo, trang
Conflicts: sisu-markup-samples (= 1.0.11)
Replaces: sisu-markup-samples (= 1.0.11)
@@ -67,7 +67,7 @@
Package: sisu-complete
Architecture: all
Depends:
- ${misc:Depends}, ruby1.9.1 (= 1.9.2.180), sisu (= ${source:Version}),
+ ${misc:Depends}, ruby | ruby-interpreter, sisu (= ${source:Version}),
sisu-pdf (= ${source:Version}), sisu-postgresql (= ${source:Version}),
sisu-sqlite (= ${source:Version})
Description: installs all SiSU related packages
@@ -82,7 +82,7 @@
Package: sisu-pdf
Architecture: all
Depends:
- ${misc:Depends}, ruby1.9.1 (= 1.9.2.180), sisu (= ${source:Version}),
+ ${misc:Depends}, ruby | ruby-interpreter, sisu (= ${source:Version}),
texlive-latex-base, texlive-fonts-recommended, texlive-generic-recommended,
texlive-latex-recommended, texlive-latex-extra, texlive-math-extra,
texlive-xetex, fonts-liberation, lmodern, latex-cjk-all, texlive-lang-cjk
@@ -96,8 +96,8 @@
Package: sisu-postgresql
Architecture: all
Depends:
- ${misc:Depends}, ruby1.9.1 (= 1.9.2.180), sisu (= ${source:Version}),
- postgresql, ruby-dbd-pg, ruby-dbi, libfcgi-ruby1.9.1
+ ${misc:Depends}, ruby | ruby-interpreter, sisu (= ${source:Version}),
+ postgresql, ruby-dbd-pg, ruby-dbi, ruby-fcgi
Suggests: postgresql-contrib
Description: SiSU dependencies for use with PostgreSQL database
SiSU is a lightweight markup based document structuring, publishing and search
@@ -115,8 +115,8 @@
Package: sisu-sqlite
Architecture: all
Depends:
- ${misc:Depends}, ruby1.9.1 (= 1.9.2.180), sisu (= ${source:Version}),
sqlite3,
- ruby-sqlite3, ruby-dbd-sqlite3, ruby-dbi, libfcgi-ruby1.9.1
+ ${misc:Depends}, ruby | ruby-interpreter, sisu (= ${source:Version}), sqlite3,
+ ruby-sqlite3, ruby-dbd-sqlite3, ruby-dbi, ruby-fcgi
Description: SiSU dependencies for use with SQLite database
SiSU is a lightweight markup based document structuring, publishing and search
framework for document collections.
diff -Nru sisu-4.2.18/debian/sisu.install sisu-4.2.18/debian/sisu.install
--- sisu-4.2.18/debian/sisu.install 2014-01-13 03:31:34.0 +0100
+++ sisu-4.2.18/debian/sisu.install 2014-01-17 12:43:28.0 +0100
@@ -1,4 +1,4 @@
-debian/bin/sisuusr/bin
+bin/sisu usr/bin
bin/sisu4 usr/bin
bin/sisu5 usr/bin
bin/sisu-concordance usr/bin
signature.asc
Description: Digital signature
Bug#650575: prima: diff for NMU version 1.28-1.2
tags 650575 + pending
tags 732405 + pending
thanks
Dear maintainer,
I've prepared an NMU for prima (versioned as 1.28-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
Sebastian Ramacher
diff -u prima-1.28/debian/control prima-1.28/debian/control
--- prima-1.28/debian/control
+++ prima-1.28/debian/control
@@ -14,7 +14,7 @@
libpng-dev,
libxpm-dev,
libjpeg-dev,
- libtiff4-dev
+ libtiff-dev
Standards-Version: 3.8.2
Homepage: http://search.cpan.org/dist/Prima/
diff -u prima-1.28/debian/changelog prima-1.28/debian/changelog
--- prima-1.28/debian/changelog
+++ prima-1.28/debian/changelog
@@ -1,3 +1,18 @@
+prima (1.28-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Rebecca Palmer ]
+ * Cherry-pick from upstream: allow compilation with newer versions of
+libtiff and libpng. Closes: #732405, #650575.
+
+ [ Sebastian Ramacher ]
+ * debian/control: Build-Depend on libtiff-dev instead of libtiff4-dev.
+ * img/codec_png.c: Call png_get_io_ptr instead of accessing io_ptr directly.
+Backported from upstream to fix compilation with libpng 1.5 and 1.6.
+
+ -- Sebastian Ramacher sramac...@debian.org Fri, 17 Jan 2014 13:54:34 +0100
+
prima (1.28-1.1) unstable; urgency=medium
* Non-maintainer upload.
only in patch2:
unchanged:
--- prima-1.28.orig/img/codec_png.c
+++ prima-1.28/img/codec_png.c
@@ -279,25 +279,29 @@
{
char * buf = ( char *) png_get_error_ptr( png_ptr);
if ( buf) strncpy( buf, msg, 256);
+#if PNG_LIBPNG_VER_MAJOR == 1 PNG_LIBPNG_VER_MINOR 5
longjmp( png_ptr- jmpbuf, 1);
+#else
+ png_longjmp( png_ptr, 1);
+#endif
}
static void
img_png_read (png_structp png_ptr, png_bytep data, png_size_t size)
{
- req_read( (( PImgLoadFileInstance) png_ptr- io_ptr)- req, size, data);
+ req_read( (( PImgLoadFileInstance) png_get_io_ptr(png_ptr))- req, size, data);
}
static void
img_png_write (png_structp png_ptr, png_bytep data, png_size_t size)
{
- req_write( (( PImgLoadFileInstance) png_ptr- io_ptr)- req, size, data);
+ req_write( (( PImgLoadFileInstance) png_get_io_ptr(png_ptr))- req, size, data);
}
static void
img_png_flush (png_structp png_ptr)
{
- req_flush( (( PImgLoadFileInstance) png_ptr- io_ptr)- req);
+ req_flush( (( PImgLoadFileInstance) png_get_io_ptr(png_ptr))- req);
}
static void *
only in patch2:
unchanged:
--- prima-1.28.orig/img/codec_tiff.c
+++ prima-1.28/img/codec_tiff.c
@@ -161,6 +161,10 @@
{ COMPRESSION_SGILOG24, SGILOG24},
};
+#ifndef TIFF_VERSION
+#define TIFF_VERSION TIFF_VERSION_CLASSIC
+#endif
+
static ImgCodecInfo codec_info = {
TIFF Bitmap,
www.libtiff.org,
signature.asc
Description: Digital signature
Bug#735624: Work-around
I had the same problem and found that the work-around is to add this line to /etc/polipo/config: logFile=/var/log/polipo/polipo.log Francois -- Francois Marier identi.ca/fmarier http://fmarier.org twitter.com/fmarier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: prima: diff for NMU version 1.28-1.2
Processing commands for cont...@bugs.debian.org: tags 650575 + pending Bug #650575 [src:prima] prima: FTBFS: img/codec_png.c:282:20: error: dereferencing pointer to incomplete type Added tag(s) pending. tags 732405 + pending Bug #732405 [src:prima] prima: FTBFS (TIFF_VERSION undeclared) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 650575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650575 732405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735025: libgit-pure-perl: FTBFS: test failures; remove?
Hello Dominic, dh_auto_test make[1]: Entering directory `/build/dom-libgit-pure-perl_0.48-2-i386-YrkwGg/libgit-pure-perl-0.48' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'inc', 'blib/lib', 'blib/arch') t/*.t syntax error at t/00_setup.t line 7, near $name qw(test-project test-project-packs test-project-packs2 test-encoding) etc. This is the same previously reported as #711443 and fixed along with a rename of the package to libgit-pureperl-perl; this package should presumably therefore be removed. yes. Upstream seems not to fix the problems. libgit-pure-perl doesn't have any rdeps. So yes, you can remove it. Thanks, Jonas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 708293 is grave
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 severity 708293 grave Bug #708293 [libhawtjni-runtime-java] libhawtjni-runtime-java: /tmp race condition with arbitrary code execution (CVE-2013-2035) Severity set to 'grave' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 708293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 704063 is grave
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 severity 704063 grave Bug #704063 [ibutils] ibutils: CVE-2013-2561 Severity set to 'grave' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 704063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 705690 is grave
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 severity 705690 grave Bug #705690 [libuser] libuser: CVE-2012-5630 CVE-2012-5644 Severity set to 'grave' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 705690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 729873 is grave
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 severity 729873 grave Bug #729873 [libjpeg-turbo] libjpeg-turbo: CVE-2013-6629 CVE-2013-6630 Severity set to 'grave' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 729873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: opennebula: diff for NMU version 3.4.1-4.1
Processing commands for cont...@bugs.debian.org: tags 735667 + patch Bug #735667 [ruby-opennebula] ruby-opennebula: please stop depending on rubygems Added tag(s) patch. tags 735667 + pending Bug #735667 [ruby-opennebula] ruby-opennebula: please stop depending on rubygems Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 735667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735667: opennebula: diff for NMU version 3.4.1-4.1
tags 735667 + patch
tags 735667 + pending
thanks
Dear maintainer,
I've prepared an NMU for opennebula (versioned as 3.4.1-4.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru opennebula-3.4.1/debian/changelog opennebula-3.4.1/debian/changelog
--- opennebula-3.4.1/debian/changelog 2013-08-13 15:23:25.0 +0200
+++ opennebula-3.4.1/debian/changelog 2014-01-17 14:32:30.0 +0100
@@ -1,3 +1,11 @@
+opennebula (3.4.1-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop deprecated rubygems package from dependencies of ruby-opennebula
+(Closes: #735667)
+
+ -- Cédric Boutillier bou...@debian.org Fri, 17 Jan 2014 14:30:58 +0100
+
opennebula (3.4.1-4) unstable; urgency=low
[ Damien Raude-Morvan ]
diff -Nru opennebula-3.4.1/debian/control opennebula-3.4.1/debian/control
--- opennebula-3.4.1/debian/control 2013-08-13 15:23:25.0 +0200
+++ opennebula-3.4.1/debian/control 2014-01-17 15:35:22.0 +0100
@@ -120,7 +120,6 @@
ruby-password,
ruby-sequel,
ruby-sqlite3,
- rubygems,
${misc:Depends},
${ruby:Depends}
Replaces: opennebula ( 3.2.1-1~)
signature.asc
Description: Digital signature
Bug#735116: apt-listbugs: […]/debian.rb:24:in `require': no such file to load -- debian_version (LoadError)
On Thu, Jan 16, 2014 at 07:33:09PM +0100, Francesco Poli wrote: On Thu, 16 Jan 2014 11:52:45 +0100 Antonio Terceiro wrote: On Wed, Jan 15, 2014 at 09:48:57PM +0100, Francesco Poli wrote: [...] What if both ruby1.8 and ruby1.9.1 are already installed and ruby1.8 was previously (manually) configured as the system-wide alternative for /usr/bin/ruby? Which package will pull in ruby, thus forcing the removal of ruby1.8? All packages depending on ruby | ruby-interpreter will be satisfied by ruby1.9.1, if I understand correctly... Is there a way to fix this scenario too? You are right! I will do another last upload of ruby1.8 dropping the alternatives entries ... :-/ Excellent, thanks a lot! Actually, that's not what I'll do. We are having a Ruby team sprint in Paris, and together we just figured out a way of fixing the problem for both stable and testing/unstable. There should be uploads soon. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Processed: severity of 735587 is serious
Processing commands for cont...@bugs.debian.org: severity 735587 serious Bug #735587 [opendnssec] opendnssec: please do not build-depend on rubygems anymore Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 735587: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735736: ruby-tokyocabinet: ruby1.8 won't be available on Jessie
Source: ruby-tokyocabinet Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear Maintainer, ruby-tokyocabinet produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735737: missing licenses in debian/copyright
Package: libpng1.6 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please update debian/copyright with all missing licenses. Especially in libpng-1.6.8/contrib/gregbook/* files with BSD or GPL licenses exist. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Processed (with 3 errors): Re: Bug#735504: Sourceless file
Processing commands for cont...@bugs.debian.org:
package src:pluxml
Limiting to bugs with field 'package' containing at least one of 'src:pluxml'
Limit currently set to 'package':'src:pluxml'
reopen 735504
Bug #735504 {Done: Tanguy Ortolo tanguy+deb...@ortolo.eu} [src:pluxml]
Sourceless file
Bug reopened
Ignoring request to alter fixed versions of bug #735504 to the same values
previously set
retitle 735504 Add a lintian override for themes/defaut/js/respond.min.js
Bug #735504 [src:pluxml] Sourceless file
Changed Bug title to 'Add a lintian override for
themes/defaut/js/respond.min.js' from 'Sourceless file'
severity 735504 wishlist
Bug #735504 [src:pluxml] Add a lintian override for
themes/defaut/js/respond.min.js
Severity set to 'wishlist' from 'serious'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
735504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731305: gimp: CVE-2013-1913 CVE-2013-1978
On Wed, Dec 04, 2013 at 08:48:59PM -0500, Ari Pollak wrote: Just a note, I plan on updating unstable but not stable gimp. We took care of oldstable/stable, but what's the status of unstable? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731305: gimp: CVE-2013-1913 CVE-2013-1978
I was hoping upstream would release a new stable version, since it would also fix a FTBFS. That still hasn't happened, so I might just end up releasing a git snapshot. On Fri, Jan 17, 2014 at 10:10 AM, Moritz Muehlenhoff j...@inutil.org wrote: On Wed, Dec 04, 2013 at 08:48:59PM -0500, Ari Pollak wrote: Just a note, I plan on updating unstable but not stable gimp. We took care of oldstable/stable, but what's the status of unstable? Cheers, Moritz
Bug#734344: ruby1.8 removal
Hi, JFTR I have my Debian bugsquashing week planned for next week, so I will remove the dependency on ruby1.8 very soon now. Ondrej. -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 735194 is serious
Processing commands for cont...@bugs.debian.org: severity 735194 serious Bug #735194 [ruby-amrita] can we remove ruby-amrita from archive in favour of ruby-amrita2? Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 735194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735312: moodle: deletes files from packages libjs-yui-*
On Tue, January 14, 2014 16:40, Robert Bihlmeyer wrote: Package: moodle Version: 2.5.3-3 Severity: serious Having libjs-yui-common and libjs-yui-common installed, an upgrade of moodle from 2.5.3-2 to -3 results in loss of a large number of files from these two packages. What I think happens here is that dpkg first sets the symlink of /usr/share/moodle/lib/yuilib/3.9.1/build to /usr/share/javascript/yui3, and then goes on to remove all the files from /u/s/m/lib/yuilib/3.9.1/build/ that are no longer contained in the new version of moodle. It *will* follow the symlink and this results in removal of these files from /usr/share/javascript/yui3 instead. This is perfectly reproducable for me: install -2, then upgrade to -3. dpkg -L libjs-yui3-common | while read f; do [ -e $f ] || echo $f; done will list a lot of missing files afterwards. Apart from being a policy violation this bug also cripples the functionality of moodle itself. My suggestion would be: 1. elide the dir removal from preinst 2. don't include the symlink in the package contents 3. remove the dir and create the symlink in the postinst When transplanting the dir removal code, remember that [ -d ... ] will return true for a symlink to a directory. Thanks. I'll investigate early next week. Thijs -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: ruby-tioga: ruby1.8 won't be available on Jessie
Processing commands for cont...@bugs.debian.org: tags 735663 patch Bug #735663 [src:ruby-tioga] ruby-tioga: ruby1.8 won't be available on Jessie Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 735663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735663: ruby-tioga: ruby1.8 won't be available on Jessie
tags 735663 patch
thanks
Hello,
I have created an patch against your package to fix that bug.
Thanks,
Jonasdiff --git a/debian/control b/debian/control
index 9f606e1..ed4a275 100644
--- a/debian/control
+++ b/debian/control
@@ -1,12 +1,10 @@
Source: ruby-tioga
Section: ruby
Priority: optional
-Maintainer: Vincent Fourmond fourm...@debian.org
-Uploaders: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org
-Build-Depends: debhelper (= 7.0.50~), ruby1.8-dev, ruby1.8, zlib1g-dev,
- rdoc1.8, libfftw3-dev, ruby1.9.1, ruby1.9.1-dev,
- gem2deb (= 0.3.0~)
-Standards-Version: 3.9.3
+Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org
+Uploaders: Vincent Fourmond fourm...@debian.org
+Build-Depends: debhelper (= 7.0.50~), zlib1g-dev, rdoc1.8, libfftw3-dev, gem2deb (= 0.3.0~)
+Standards-Version: 3.9.5
Homepage: http://tioga.rubyforge.org
Vcs-Git: git://anonscm.debian.org/pkg-ruby-extras/ruby-tioga.git
Vcs-Browser: http://anonscm.debian.org/gitweb?p=pkg-ruby-extras/ruby-tioga.git;a=summary
@@ -17,20 +15,13 @@ Architecture: any
XB-Ruby-Versions: ${ruby:Versions}
Depends: ${shlibs:Depends}, ${misc:Depends}, ruby | ruby-interpreter,
texlive-latex-base | tetex-bin
-Suggests: libtioga-ruby-doc, xpdf | pdf-viewer,
- irb | irb1.8 | irb1.9.1
-Replaces: libtioga-ruby1.8 ( 1.13-4~),
- libtioga-ruby1.9.1 ( 1.13-4~),
- libtioga-ruby ( 1.13-4~)
-Breaks: libtioga-ruby1.8 ( 1.13-4~),
-libtioga-ruby1.9.1 ( 1.13-4~),
-libtioga-ruby ( 1.13-4~)
-Description: Ruby library for scientific graphs
+Suggests: libtioga-ruby-doc, xpdf | pdf-viewer, irb
+Description: Ruby library for scientific graphs
Tioga is a blend of PDF, pdfTex and ruby into a library to make
- scientific graphs of high quality. It is fairly complete and
+ scientific graphs of high quality. It is fairly complete and
extensive, and comes with examples and (online) complete documentation.
.
- Tioga is useful for scripting the generation of graphs, and comes
+ Tioga is useful for scripting the generation of graphs, and comes
with a configuration file for irb for interactive plotting of pictures.
.
A PDF viewer is strongly recommended if you want to make use of the
@@ -49,12 +40,12 @@ Architecture: all
Depends: ${misc:Depends}
Section: doc
Recommends: ruby-tioga, irb
-Description: Ruby library for scientific graphs
+Description: documentation for Ruby library for scientific graphs
Tioga is a blend of PDF, pdfTex and ruby into a library to make
- scientific graphs of high quality. It is fairly complete and
+ scientific graphs of high quality. It is fairly complete and
extensive, and comes with examples and (online) complete documentation.
.
- Tioga is useful for scripting the generation of graphs, and comes
+ Tioga is useful for scripting the generation of graphs, and comes
with a configuration file for irb for interactive plotting of pictures.
.
This package provides the rdoc documentation generated from tioga's
diff --git a/debian/libtioga-ruby1.8.preinst b/debian/libtioga-ruby1.8.preinst
deleted file mode 100644
index 99f070a..000
--- a/debian/libtioga-ruby1.8.preinst
+++ /dev/null
@@ -1,13 +0,0 @@
-#!/bin/sh
-
-set -e
-
-if [ $1 = upgrade ]
-then
- update-alternatives --remove tioga /usr/bin/tioga-1.8
-fi
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
diff --git a/debian/libtioga-ruby1.9.1.preinst b/debian/libtioga-ruby1.9.1.preinst
deleted file mode 100644
index 3705aca..000
--- a/debian/libtioga-ruby1.9.1.preinst
+++ /dev/null
@@ -1,13 +0,0 @@
-#!/bin/sh
-
-set -e
-
-if [ $1 = upgrade ]
-then
- update-alternatives --remove tioga /usr/bin/tioga-1.9.1
-fi
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
Processed: r2247 - in mysql-5.5/branches/unstable/debian: . patches
Processing commands for cont...@bugs.debian.org: tags 732306 pending Bug #732306 [mysql-5.5] mysql-5.5: installation creates database test and sets up insecure database permissions Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 732306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650575: prima: diff for NMU version 1.28-1.2
On 2014-01-17 14:29:05, Sebastian Ramacher wrote: tags 650575 + pending tags 732405 + pending thanks Dear maintainer, I've prepared an NMU for prima (versioned as 1.28-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Seems like I've missed #734974 so there is already a NMU in the delayed queue. Regards -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#731967: FW: Bug#731967: libqb FTBFS: build failed on post-compile-test on mips/mipsel
Hi,
The bug is fixed upstream.
Can you consider getting the latest source from
upstream?
https://github.com/ClusterLabs/libqb
Regards,
Dejan LatinovićAuthor: Dejan Latinovic dejan.latino...@rt-rk.com
Description: Check if call of function will go through lazy binding stub for mips.
Index: patch.gammaray-1.2.2/launcher/injector/preloadcheck.cpp
===
--- patch.gammaray-1.2.2.orig/launcher/injector/preloadcheck.cpp 2012-12-21 21:38:15.0 +
+++ patch.gammaray-1.2.2/launcher/injector/preloadcheck.cpp 2013-11-27 16:31:07.0 +
@@ -99,10 +99,99 @@
}
}
+//Mips, besides the plt, has another method of
+//calling functions from .so files, and this method doesn't need JUMP_SLOT
+//relocations (in fact, it doesn't need any relocations). This method uses .got
+//entries and lazy binding stubs.
+#ifdef __mips__
+ if (testMips(symbol, fileName)){
+qDebug() Call of function symbol will go through lazy binding stub;
+setErrorString(QString());
+return true;
+ }
+#endif
+
setErrorString(QObject::tr(Symbol is not marked as relocatable: %1).arg(symbol));
return false;
}
+
+//The way to determine whether the call to function will go
+//through .got and lazy binding stub is:
+//- find the value of dynamic symbol index of the function with the command
+// readelf --dyn-syms
+//- find the value of dynamic tag MIPS_GOTSYM with the command readelf -d
+//- if (dyn_sym_index = MIPS_GOTSYM) then the function has entry in the global
+// part of the .got, and the call will go through lazy binding stub and be
+// resolved by dynamic linker.
+
+#ifdef __mips__
+bool PreloadCheck::testMips(const QString symbol, const QString fileName)
+{
+ QProcess proc;
+ proc.setProcessChannelMode(QProcess::MergedChannels);
+ proc.start(readelf, QStringList() --dyn-syms -d fileName, QIODevice::ReadOnly);
+
+ if (!proc.waitForFinished()) {
+setErrorString(QObject::tr(Failed to run 'readelf' (binutils) binary: %1).
+ arg(QString(proc.errorString(;
+return false;
+ }
+
+ if (proc.exitCode() != 0) {
+setErrorString(QObject::tr(Cannot read shared object: %1).arg(QString(proc.readAll(;
+return false;
+ }
+
+ //Example line of dynamic symbol table on mips:
+ //3851: 001e66f4 8 FUNCGLOBAL DEFAULT 11 qt_startup_hook
+ QRegExp rxSym(^(\\d+):\\s+(?:[^ ]+\\s+){6}([^ ]+)(?:.*)$);
+
+ //Example line of dynamic tag on mips:
+ //0x7013 (MIPS_GOTSYM)0xec3
+ QRegExp rxGot(^0x[0-9a-fA-F]+\\s+\\((.+)\\)\\s+(0x[0-9a-fA-F]+)(?:.*)$);
+
+ int dyn_sym_index = 0;
+ int mips_gotsym = 0;
+ bool foundDynSymbol = false;
+ bool foundGotTag = false;
+
+ while (proc.canReadLine()) {
+const QString line = proc.readLine().trimmed();
+QString currentMatch;
+const QString tag = MIPS_GOTSYM;
+
+if (rxGot.exactMatch(line)) {
+ currentMatch = rxGot.cap(1);
+
+ if (currentMatch == tag) {
+bool conversionOk = false;
+int value = rxGot.cap(2).toInt(conversionOk, 16);
+if (conversionOk){
+ mips_gotsym = value;
+ foundGotTag = true;
+}
+ }
+}
+else if (rxSym.exactMatch(line)) {
+ currentMatch = rxSym.cap(2);
+ if (currentMatch == symbol) {
+dyn_sym_index = rxSym.cap(1).toInt();
+foundDynSymbol = true;
+ }
+}
+if (foundGotTag foundDynSymbol)
+ break;
+ }
+ if (foundGotTag foundDynSymbol (dyn_sym_index = mips_gotsym)) {
+return true;
+ }
+
+ return false;
+}
+#endif
+
+
void PreloadCheck::setErrorString(const QString err)
{
m_errorString = err;
Index: patch.gammaray-1.2.2/launcher/injector/preloadcheck.h
===
--- patch.gammaray-1.2.2.orig/launcher/injector/preloadcheck.h 2012-12-21 21:38:15.0 +
+++ patch.gammaray-1.2.2/launcher/injector/preloadcheck.h 2013-11-27 16:31:07.0 +
@@ -44,6 +44,10 @@
private:
static QString findSharedObjectFile(const QString symbol);
+#ifdef __mips__
+bool testMips(const QString symbol, const QString fileName);
+#endif
+
QString m_errorString;
};
Bug#713449: (no subject)
Here is a patch to fix this error: https://github.com/ebourg/qpid-cpp-debian/commit/43f1c0afe7ad3c9042b426fc4fbb20ee797a9761 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735746: pillow: FTBFS: _imagingtk.cpython-33m.so not found
Source: pillow
Version: 2.2.1-3
Severity: serious
Hi,
pillow FTBFS like this:
...
Writing
/home/rst/temp/debian/pillow-2.2.1/debian/python3-sane/usr/lib/python3/dist-packages/pysane-2.0.egg-info
incdir=$(python3.3 -c 'import sysconfig;
print(sysconfig.get_path(include))'); \
mkdir -p debian/python3-pil/$incdir; \
install -o root -g root -m 644 \
libImaging/Imaging.h \
libImaging/ImPlatform.h \
libImaging/ImDib.h \
debian/python3-pil/$incdir
abitag=.$(python3.3 -c import sysconfig;
print(sysconfig.get_config_var('SOABI'))); \
dh_movefiles -ppython3-pil.imagetk \
--sourcedir=debian/python3-pil \
usr/lib/python3/$(basename $(_py_=3.3; python${_py_#python*} -c
'from distutils import sysconfig;
print(sysconfig.get_python_lib())'))/PIL/_imagingtk$abitag.so \
usr/lib/python3/$(basename $(_py_=3.3; python${_py_#python*} -c
'from distutils import sysconfig;
print(sysconfig.get_python_lib())'))/PIL/ImageTk.py
dh_movefiles:
debian/python3-pil/usr/lib/python3/dist-packages/PIL/_imagingtk.cpython-33m.so
not found (supposed to put it in python3-pil.imagetk)
make: *** [install3-python3.3] Error 1
...
See also the build logs of powerpcspe and ppc64 at
http://buildd.debian-ports.org/status/package.php?p=pillowsuite=sid
I checked that the same happens on i386.
Roland
-- System Information:
Debian Release: 7.0
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: powerpcspe (ppc)
Kernel: Linux 3.9.0-dirty (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735745: oar: Jessie will not have Ruby 1.8
Source: oar Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, oar produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal in 4 weeks. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734719: distributed-net: fails to install due to change in daemon's shell
On Fri, Jan 17, 2014 at 12:55:41PM +, Colin Watson wrote: On Sat, Jan 11, 2014 at 06:01:11PM -0500, James Stark wrote: I have no objections to an NMU on this one, however I think that I may be able to deal with it today or tomorrow. I have been planning an update for a while now, but I've been distracted by writing a thesis. I'll look at getting this bug fixed, and bringing the package up to date, along with the output of lintian. #655922 will have to wait for a future upload. This is now the last non-pending bug blocking #734946; please let me know if there's anything I can do to help. Hi Colin, We tried to upload earlier this week, but the upload was rejected due to a lintian error. (/me thinks the pre-build binaries are evil... :) I'll take a look at it this weekend to see how we can get it into the archive. Thanks for your follow-up, tony -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 735453 is serious
Processing commands for cont...@bugs.debian.org: severity 735453 serious Bug #735453 [libsbml5-ruby1.8] libsbml5-ruby1.8: build-depend on default ruby/comply with Ruby policy Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 735453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735336: git-svn fails 'tempfile' can't be called as a method at /usr/share/perl5/Git.pm line 1042.
The problem that I originally had is resolved. git version 1.8.5.2 I will continue with testing that. This bug in git.pm occured the in the workaround that is not needed any more but should be applied anyway. mike On Thu, Jan 16, 2014 at 5:24 PM, Jonathan Nieder jrnie...@gmail.com wrote: James Michael DuPont wrote: Using the freshly built version the problem does not occur : git version 1.8.5.3.321.g14598b9 Weird. I don't think there's been a change that should have fixed it. Does 1.8.5.2 from testing or sid (putting /usr/bin earlier in $PATH again) still reproduce the problem? Puzzled, Jonathan
Processed: block 731866 with 520901 718444 721618 722362 722364 722365 722366 722367 722369 722371 722372 722373 722374 722375 722376 722377 722379 722380 722381 722382 722384 722385 722387 722389 722
Processing commands for cont...@bugs.debian.org: block 731866 with 520901 718444 721618 722362 722364 722365 722366 722367 722369 722371 722372 722373 722374 722375 722376 722377 722379 722380 722381 722382 722384 722385 722387 722389 722390 722392 722393 722395 722396 722625 723642 723648 725602 730719 730880 730940 730943 730944 730960 730972 731462 731557 732916 732922 732931 733004 733019 733102 733105 733110 733641 733724 733773 733775 734330 734342 734344 734346 734954 735194 735417 735425 735426 735427 735430 735433 735434 735435 735466 735468 735476 735511 735650 735651 735652 735653 735654 735655 735656 735657 735658 735659 735660 735661 735662 735663 735736 735745 Bug #731866 [libruby1.8] Remove ruby1.8 for jessie 731866 was not blocked by any bugs. 731866 was not blocking any bugs. Added blocking bug(s) of 731866: 722390, 735663, 722364, 733102, 722389, 730940, 735425, 722372, 735468, 735426, 735511, 735417, 733775, 722371, 733110, 722366, 733641, 722380, 735427, 735430, 734344, 722367, 730972, 730943, 735658, 722374, 735662, 735659, 735476, 722375, 722381, 722392, 735434, 725602, 722377, 734954, 735661, 722396, 731557, 734346, 722384, 520901, 722376, 735657, 733004, 722382, 735652, 732916, 735653, 730719, 722385, 730944, 735433, 730880, 732922, 734330, 735651, 733724, 735655, 731462, 735654, 722395, 733773, 735466, 735736, 723648, 735650, 722393, 735435, 721618, 722369, 722379, 735194, 722625, 735745, 733105, 722362, 730960, 722365, 735656, 735660, 733019, 718444, 732931, 722373, 723642, 734342, and 722387 thanks Stopping processing here. Please contact me if you need assistance. -- 731866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735752: ruby-usb: ruby1.8 won't be available on Jessie
Source: ruby-usb Severity: serious User: debian-r...@lists.debian.org Usertags: ruby18-removal Dear maintainer, ruby-usb produces one or more binary packages that depends on ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point, and we can't keep it for Jessie. We plan to request its removal from unstable in 4 weeks, and from testing in the next few days. Recommendations for some common cases: If your package contains Ruby programs that are hardcoded to use ruby1.8, you need to port those to a more recent version. Please use /usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 If your package calls `ruby1.8` during build, please make it call `ruby` instead. If your scripts don't work with a newer Ruby, you need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as it will require more work later when we want to get rid of ruby1.9.1 (and we will). If your packages builds binary extensions for ruby1.8, you need to remove those. Please consider building binary extensions for all supported Ruby versions. You can get a list of supported Ruby versions at runtime by build-depending on gem2deb and running $ dh_ruby --print-supported I'm flagging this bug as release critical, since it's impossible to have ruby1.8 in the next release. If you need advice on the best way to handle your package, please feel free to get in touch with debian-r...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Processed: Re: Bug#734719: distributed-net: fails to install due to change in daemon's shell
Processing commands for cont...@bugs.debian.org: tags 734719 + fixed pending Bug #734719 [distributed-net] distributed-net: fails to install due to change in daemon's shell Added tag(s) fixed and pending. End of message, stopping processing here. Please contact me if you need assistance. -- 734719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735668: missing license in debian/copyright
On Friday 17 January 2014 11:56:42 you wrote: Package: fwknop Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please update debian/copyright of your package. For example fwknop-2.6.0/android/* is licensed under GPLv3+. Thanks for catching this. I will update d.copyright accordingly. Regards, -- Franck Joncourt signature.asc Description: This is a digitally signed message part.
Bug#735753: libncursesada: FTBFS: ./gen.c:249:5: error: missing binary operator before token (
Source: libncursesada Version: 5.9.20110404-7 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140114 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): gcc -I. -I../include -I../../include -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -DNDEBUG -I. -I../include -DHAVE_CONFIG_H -I. -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o gen.o ./gen.c In file included from /usr/include/menu.h:42:0, from ./gen.c:57: ./gen.c: In function 'gen_attr_set': ./gen.c:249:5: error: missing binary operator before token ( #if A_STANDOUT ^ ./gen.c:252:5: error: missing binary operator before token ( #if A_UNDERLINE ^ ./gen.c:255:5: error: missing binary operator before token ( #if A_REVERSE ^ ./gen.c:258:5: error: missing binary operator before token ( #if A_BLINK ^ ./gen.c:261:5: error: missing binary operator before token ( #if A_DIM ^ ./gen.c:264:5: error: missing binary operator before token ( #if A_BOLD ^ ./gen.c:267:5: error: missing binary operator before token ( #if A_ALTCHARSET ^ ./gen.c:270:5: error: missing binary operator before token ( #if A_INVIS ^ ./gen.c:273:5: error: missing binary operator before token ( #if A_PROTECT ^ ./gen.c:276:5: error: missing binary operator before token ( #if A_HORIZONTAL ^ ./gen.c:279:5: error: missing binary operator before token ( #if A_LEFT ^ ./gen.c:282:5: error: missing binary operator before token ( #if A_LOW ^ ./gen.c:285:5: error: missing binary operator before token ( #if A_RIGHT ^ ./gen.c:288:5: error: missing binary operator before token ( #if A_TOP ^ ./gen.c:291:5: error: missing binary operator before token ( #if A_VERTICAL ^ make[3]: *** [gen.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/01/14/libncursesada_5.9.20110404-7_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735754: dragonegg: FTBFS: ABIHack.inc:1666:36: error: 'TARGET_CPU_DEFAULT_max' was not declared in this scope
Source: dragonegg Version: 3.3-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140114 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory `/«PKGBUILDDIR»' gcc-4.8 --version /dev/null /usr/lib/llvm-3.3/bin/llvm-config --version /dev/null Compiling utils/TargetInfo.cpp g++-4.8 -c \ -D_FORTIFY_SOURCE=2 -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-rtti -MD -MP -DIN_GCC -DLLVM_VERSION=\3.3\ -DTARGET_TRIPLE=\x86_64-linux-gnu\ -DGCC_MAJOR=4 -DGCC_MINOR=8 -DGCC_MICRO=0 -I/«PKGBUILDDIR»/include -isystem/usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/include -DDISABLE_VERSION_CHECK -DENABLE_BUILD_WITH_CXX -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wextra -fvisibility=hidden -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -g -O2 -fomit-frame-pointer -fvisibility-inlines-hidden -fno-exceptions -fPIC -Woverloaded-virtual -Wcast-qual /«PKGBUILDDIR»/utils/TargetInfo.cpp Linking TargetInfo g++-4.8 -o TargetInfo TargetInfo.o -lLLVMSupport \ -L/usr/lib/llvm-3.3/lib -lpthread -lffi -ldl -lm -L/usr/lib/llvm-3.3/lib -Wl,-z,relro Compiling Aliasing.cpp g++-4.8 -c -I/«PKGBUILDDIR»/include/x86 -I/«PKGBUILDDIR»/include/linux -D_FORTIFY_SOURCE=2 -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-rtti -MD -MP -DIN_GCC -DLLVM_VERSION=\3.3\ -DTARGET_TRIPLE=\x86_64-linux-gnu\ -DGCC_MAJOR=4 -DGCC_MINOR=8 -DGCC_MICRO=0 -I/«PKGBUILDDIR»/include -isystem/usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/include -DDISABLE_VERSION_CHECK -DENABLE_BUILD_WITH_CXX -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wextra -fvisibility=hidden -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -g -O2 -fomit-frame-pointer -fvisibility-inlines-hidden -fno-exceptions -fPIC -Woverloaded-virtual -Wcast-qual /«PKGBUILDDIR»/src/Aliasing.cpp Compiling Backend.cpp g++-4.8 -c -I/«PKGBUILDDIR»/include/x86 -I/«PKGBUILDDIR»/include/linux -D_FORTIFY_SOURCE=2 -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-rtti -MD -MP -DIN_GCC -DLLVM_VERSION=\3.3\ -DTARGET_TRIPLE=\x86_64-linux-gnu\ -DGCC_MAJOR=4 -DGCC_MINOR=8 -DGCC_MICRO=0 -I/«PKGBUILDDIR»/include -isystem/usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/include -DDISABLE_VERSION_CHECK -DENABLE_BUILD_WITH_CXX -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wextra -fvisibility=hidden -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -g -O2 -fomit-frame-pointer -fvisibility-inlines-hidden -fno-exceptions -fPIC -Woverloaded-virtual -Wcast-qual /«PKGBUILDDIR»/src/Backend.cpp In file included from /usr/lib/llvm-3.3/include/llvm/CodeGen/Passes.h:19:0, from /usr/lib/llvm-3.3/include/llvm/CodeGen/MachinePassRegistry.h:21, from /usr/lib/llvm-3.3/include/llvm/CodeGen/RegAllocRegistry.h:18, from /«PKGBUILDDIR»/src/Backend.cpp:37: /usr/lib/llvm-3.3/include/llvm/Target/TargetMachine.h:251:16: warning: unused parameter 'StartAfter' [-Wunused-parameter] virtual bool addPassesToEmitFile(PassManagerBase , ^ /usr/lib/llvm-3.3/include/llvm/Target/TargetMachine.h:251:16: warning: unused parameter 'StopAfter' [-Wunused-parameter] Compiling Cache.cpp g++-4.8 -c -I/«PKGBUILDDIR»/include/x86 -I/«PKGBUILDDIR»/include/linux -D_FORTIFY_SOURCE=2 -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-rtti -MD -MP -DIN_GCC -DLLVM_VERSION=\3.3\ -DTARGET_TRIPLE=\x86_64-linux-gnu\ -DGCC_MAJOR=4 -DGCC_MINOR=8 -DGCC_MICRO=0 -I/«PKGBUILDDIR»/include -isystem/usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/include -DDISABLE_VERSION_CHECK -DENABLE_BUILD_WITH_CXX -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wextra -fvisibility=hidden -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -g -O2 -fomit-frame-pointer -fvisibility-inlines-hidden -fno-exceptions -fPIC -Woverloaded-virtual -Wcast-qual /«PKGBUILDDIR»/src/Cache.cpp Compiling ConstantConversion.cpp g++-4.8 -c -I/«PKGBUILDDIR»/include/x86 -I/«PKGBUILDDIR»/include/linux -D_FORTIFY_SOURCE=2 -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
Bug#735755: wmcoincoin: FTBFS: ld: wmcoincoin_player.o: undefined reference to symbol 'XGetWindowAttributes'
Source: wmcoincoin Version: 2.5.1e-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140114 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): x86_64-linux-gnu-gcc -g -O2 -Wall -W -fsigned-char -Wno-pointer-sign -Wl,-O1 -Wl,--as-needed -rdynamic -o wmcoincoin_player fmalloc.o giffunc.o gifread.o wmcoincoin_player.o `imlib2-config --libs` /usr/bin/ld: wmcoincoin_player.o: undefined reference to symbol 'XGetWindowAttributes' //usr/lib/x86_64-linux-gnu/libX11.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/01/14/wmcoincoin_2.5.1e-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735757: fizmo: FTBFS: fizmo-ncursesw.c:46:21: fatal error: ncurses.h: No such file or directory
Source: fizmo Version: 0.7.7-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140114 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): gcc -DPACKAGE_NAME=\fizmo\ -DPACKAGE_TARNAME=\fizmo\ -DPACKAGE_VERSION=\0.7.7\ -DPACKAGE_STRING=\fizmo\ 0.7.7\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DHAVE_LIBXML2=1 -DHAVE_LIBM=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DPACKAGE=\fizmo\ -DVERSION=\0.7.7\ -I. -D_FORTIFY_SOURCE=2 -I/«PKGBUILDDIR»/build/include/fizmo -I/«PKGBUILDDIR»/build/include/fizmo-I/«PKGBUILDDIR»/build/include/fizmo -I/usr/include -I/usr/include/libpng12-DENABLE_X11_IMAGES= -I/«PKGBUILDDIR»/build/include/fizmo -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -DSOUND_INTERFACE_STRUCT_NAME=sound_interface_sdl -DSOUND_INTERFACE_INCLUDE_FILE=sound_sdl/sound_sdl.h -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o fizmo-ncursesw.o fizmo-ncursesw.c fizmo-ncursesw.c:46:21: fatal error: ncurses.h: No such file or directory #include ncurses.h ^ compilation terminated. make[3]: *** [fizmo-ncursesw.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/01/14/fizmo_0.7.7-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735759: lua-posix: FTBFS: lcurses.c:47:18: fatal error: term.h: No such file or directory
Source: lua-posix Version: 29-5 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140114 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory `/«PKGBUILDDIR»' dh_auto_build Making target build for debian/lua5.1.curses.dh-lua.conf libtool --silent --tag=CC --mode=compile cc -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -I/usr//include/lua5.1 -I. -DHAVE_CONFIG_H -Wall -Wextra -o /«PKGBUILDDIR»/5.1-curses/lcurses.lo lcurses.c lcurses.c:47:18: fatal error: term.h: No such file or directory #include term.h ^ compilation terminated. make[3]: *** [/«PKGBUILDDIR»/5.1-curses/lcurses.lo] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/01/14/lua-posix_29-5_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735760: handbrake: FTBFS: dvdnav.c:1230: undefined reference to `dvdnav_dup'
Source: handbrake Version: 0.9.9+dfsg-2~2.gbpa4c3e9 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140114 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /usr/bin/g++ -pipe -Wl,-z,relro -Wl,-z,defs -Wl,--as-needed -fmessage-length=0 -Wall -g2 -O3 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -I./libhb/ -I./contrib/include -o HandBrakeCLI -Wl,--start-group test/parsecsv.o test/test.o ./libhb/libhb.a -la52 -lass -lavcodec -lavformat -lavutil -lavresample -ldvdnav -ldvdread -lfontconfig -lfreetype -lmkv -lmpeg2 -lmp3lame -logg -lsamplerate -lswscale -ltheoraenc -ltheoradec -lvorbis -lvorbisenc -lx264 -lbluray -lxml2 -lbz2 -lz -lpthread -ldl -lm -Wl,--end-group ./libhb/libhb.a(dvdnav.o): In function `try_menu': /«BUILDDIR»/handbrake-0.9.9+dfsg/build/../libhb/dvdnav.c:1230: undefined reference to `dvdnav_dup' /«BUILDDIR»/handbrake-0.9.9+dfsg/build/../libhb/dvdnav.c:1237: undefined reference to `dvdnav_free_dup' collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/01/14/handbrake_0.9.9+dfsg-2~2.gbpa4c3e9_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735758: hsetroot: FTBFS: ld: hsetroot.o: undefined reference to symbol 'XClearWindow'
Source: hsetroot Version: 1.0.2-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140114 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wl,-z,relro -o hsetroot hsetroot.o -L/usr/lib/x86_64-linux-gnu -lImlib2 /usr/bin/ld: hsetroot.o: undefined reference to symbol 'XClearWindow' //usr/lib/x86_64-linux-gnu/libX11.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/01/14/hsetroot_1.0.2-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735762: bzr-git: FTBFS: AssertionError: /«PKGBUILDDIR»/branch.py:558: DeprecationWarning: Repo.ref(name) is deprecated. Use Repo.refs[name] instead.
Source: bzr-git
Version: 0.6.12-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140114 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
bzrlib.plugins.git.tests.test_unpeel_map.TestUnpeelMap.test_load OK
2ms
bzrlib.plugins.git.tests.test_unpeel_map.TestUnpeelMap.test_new OK
2ms
bzrlib.plugins.git.tests.test_unpeel_map.TestUnpeelMap.test_update OK
2ms
bzrlib.plugins.git.tests.test_workingtree.GitWorkingTreeTests.test_conflicts
OK7ms
==
FAIL: bzrlib.plugins.git.tests.test_blackbox.TestGitBlackBox.test_branch
--
_StringException: log: {{{
0.478 creating repository in file:///tmp/testbzr-uk04tc.tmp/.bzr/.
0.482 creating branch bzrlib.branch.BzrBranchFormat7 object at 0x2deaed0
in file:///tmp/testbzr-uk04tc.tmp/
0.491 trying to create missing lock
'/tmp/testbzr-uk04tc.tmp/.bzr/checkout/dirstate'
0.492 opening working tree '/tmp/testbzr-uk04tc.tmp'
0.510 run bzr: ['branch', 'gitbranch', 'bzrbranch']
0.511 bazaar version: 2.6.0
0.511 bzr arguments: [u'branch', u'gitbranch', u'bzrbranch']
0.514 encoding stdout as sys.stdout encoding 'ascii'
0.526 creating repository in
file:///tmp/testbzr-uk04tc.tmp/bzrlib.plugins.git.tests.test_blackbox.TestGitBlackBox.test_branch/work/bzrbranch/.bzr/.
0.550 creating branch bzrlib.branch.BzrBranchFormat7 object at 0x3ef6310
in
file:///tmp/testbzr-uk04tc.tmp/bzrlib.plugins.git.tests.test_blackbox.TestGitBlackBox.test_branch/work/bzrbranch/
0.562 trying to create missing lock
'/tmp/testbzr-uk04tc.tmp/bzrlib.plugins.git.tests.test_blackbox.TestGitBlackBox.test_branch/work/bzrbranch/.bzr/checkout/dirstate'
0.563 opening working tree
'/tmp/testbzr-uk04tc.tmp/bzrlib.plugins.git.tests.test_blackbox.TestGitBlackBox.test_branch/work/bzrbranch'
INFO Branched 1 revision.
0.587 errors:
'/«PKGBUILDDIR»/branch.py:558: DeprecationWarning: Repo.ref(name) is
deprecated. Use Repo.refs[name] instead.\n return
self.repository._git.ref(self.ref or HEAD)\nBranched 1 revision.\n'
}}}
Traceback (most recent call last):
File /«PKGBUILDDIR»/tests/test_blackbox.py, line 77, in test_branch
error)
File /usr/lib/python2.7/unittest/case.py, line 424, in assertTrue
raise self.failureException(msg)
AssertionError: /«PKGBUILDDIR»/branch.py:558: DeprecationWarning:
Repo.ref(name) is deprecated. Use Repo.refs[name] instead.
return self.repository._git.ref(self.ref or HEAD)
Branched 1 revision.
--
Ran 244 tests in 6.317s
FAILED (failures=1, known_failure_count=2)
1 test skipped
make[1]: *** [override_dh_auto_test] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/01/14/bzr-git_0.6.12-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735756: libguestfs: FTBFS: _guestfs.c:444:10: error: variable 'optargs_s' has initializer but incomplete type
Source: libguestfs
Version: 1:1.24.3-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140114 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
make[5]: Entering directory
`/«PKGBUILDDIR»/debian/build-ruby2.0/ruby/ext/guestfs'
compiling
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c: In
function 'ruby_guestfs_internal_test':
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:444:10:
error: variable 'optargs_s' has initializer but incomplete type
struct guestfs_internal_test_argv optargs_s = { .bitmask = 0 };
^
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:444:10:
error: unknown field 'bitmask' specified in initializer
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:444:10:
warning: excess elements in struct initializer [enabled by default]
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:444:10:
warning: (near initialization for 'optargs_s') [enabled by default]
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:444:37:
error: storage size of 'optargs_s' isn't known
struct guestfs_internal_test_argv optargs_s = { .bitmask = 0 };
^
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:450:26:
error: 'GUESTFS_INTERNAL_TEST_OBOOL_BITMASK' undeclared (first use in this
function)
optargs_s.bitmask |= GUESTFS_INTERNAL_TEST_OBOOL_BITMASK;
^
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:450:26:
note: each undeclared identifier is reported only once for each function it
appears in
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:455:26:
error: 'GUESTFS_INTERNAL_TEST_OINT_BITMASK' undeclared (first use in this
function)
optargs_s.bitmask |= GUESTFS_INTERNAL_TEST_OINT_BITMASK;
^
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:460:26:
error: 'GUESTFS_INTERNAL_TEST_OINT64_BITMASK' undeclared (first use in this
function)
optargs_s.bitmask |= GUESTFS_INTERNAL_TEST_OINT64_BITMASK;
^
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:465:26:
error: 'GUESTFS_INTERNAL_TEST_OSTRING_BITMASK' undeclared (first use in this
function)
optargs_s.bitmask |= GUESTFS_INTERNAL_TEST_OSTRING_BITMASK;
^
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:483:26:
error: 'GUESTFS_INTERNAL_TEST_OSTRINGLIST_BITMASK' undeclared (first use in
this function)
optargs_s.bitmask |= GUESTFS_INTERNAL_TEST_OSTRINGLIST_BITMASK;
^
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c: In
function 'ruby_guestfs_internal_test_only_optargs':
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:511:10:
error: variable 'optargs_s' has initializer but incomplete type
struct guestfs_internal_test_only_optargs_argv optargs_s = { .bitmask = 0
};
^
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:511:10:
error: unknown field 'bitmask' specified in initializer
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:511:10:
warning: excess elements in struct initializer [enabled by default]
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:511:10:
warning: (near initialization for 'optargs_s') [enabled by default]
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:511:50:
error: storage size of 'optargs_s' isn't known
struct guestfs_internal_test_only_optargs_argv optargs_s = { .bitmask = 0
};
^
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:517:26:
error: 'GUESTFS_INTERNAL_TEST_ONLY_OPTARGS_TEST_BITMASK' undeclared (first
use in this function)
optargs_s.bitmask |= GUESTFS_INTERNAL_TEST_ONLY_OPTARGS_TEST_BITMASK;
^
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c: In
function 'ruby_guestfs_internal_test_63_optargs':
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:544:10:
error: variable 'optargs_s' has initializer but incomplete type
struct guestfs_internal_test_63_optargs_argv optargs_s = { .bitmask = 0 };
^
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:544:10:
error: unknown field 'bitmask' specified in initializer
/«PKGBUILDDIR»/debian/build-ruby2.0/../../ruby/ext/guestfs/_guestfs.c:544:10:
warning: excess elements in struct initializer [enabled by default]
Bug#735763: svnkit: FTBFS: [javac] /«BUILDDIR»/svnkit-1.7.5+dfsg/svnkit-javahl16/src/main/java/org/apache/subversion/javahl/SVNClient.java:32: error: SVNClient is not abstract and does not overrid
Source: svnkit
Version: 1.7.5+dfsg-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140114 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
make[1]: Entering directory `/«BUILDDIR»/svnkit-1.7.5+dfsg'
VERSION=$(dpkg-parsechangelog | grep Version: | cut -d' ' -f 2); \
echo $VERSION | { \
IFS='.-+' read MAJOR MINOR MICRO DFSG DEBIAN; \
export MAJOR MINOR MICRO DEBIAN; \
ant -f debian/build.xml -propertyfile debian/ant.properties; \
};
Buildfile: /«BUILDDIR»/svnkit-1.7.5+dfsg/debian/build.xml
init-environment:
compile-library:
[mkdir] Created dir: /«BUILDDIR»/svnkit-1.7.5+dfsg/svnkit/bin
[mkdir] Created dir: /«BUILDDIR»/svnkit-1.7.5+dfsg/svnkit-cli/bin
[mkdir] Created dir: /«BUILDDIR»/svnkit-1.7.5+dfsg/svnkit-javahl16/bin
[javac] /«BUILDDIR»/svnkit-1.7.5+dfsg/debian/build.xml:20: warning:
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set
to false for repeatable builds
[javac] Compiling 925 source files to
/«BUILDDIR»/svnkit-1.7.5+dfsg/svnkit/bin
[javac] warning: [options] bootstrap class path not set in conjunction
with -source 1.5
[javac]
/«BUILDDIR»/svnkit-1.7.5+dfsg/svnkit/src/main/java/org/tmatesoft/svn/core/internal/util/SVNPathUtil.java:62:
warning: non-varargs call of varargs method with inexact argument type for
last parameter;
[javac] SVNErrorMessage err =
SVNErrorMessage.create(SVNErrorCode.FS_PATH_SYNTAX, Invalid control
character ''{0}'' in path ''{1}'', new String[]{0x +
SVNFormatUtil.getHexNumberFromByte((byte) ch), path});
[javac]
^
[javac] cast to Object for a varargs call
[javac] cast to Object[] for a non-varargs call and to suppress this
warning
[javac]
/«BUILDDIR»/svnkit-1.7.5+dfsg/svnkit/src/main/java/org/tmatesoft/svn/core/wc/admin/SVNAdminClient.java:1617:
warning: non-varargs call of varargs method with inexact argument type for
last parameter;
[javac] SVNErrorMessage err =
SVNErrorMessage.create(SVNErrorCode.IO_ERROR, Session is rooted at ''{0}''
but the repos root is ''{1}'', new SVNURL[] {
[javac]
^
[javac] cast to Object for a varargs call
[javac] cast to Object[] for a non-varargs call and to suppress this
warning
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 3 warnings
[javac] /«BUILDDIR»/svnkit-1.7.5+dfsg/debian/build.xml:23: warning:
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set
to false for repeatable builds
[javac] Compiling 122 source files to
/«BUILDDIR»/svnkit-1.7.5+dfsg/svnkit-cli/bin
[javac] warning: [options] bootstrap class path not set in conjunction
with -source 1.5
[javac] Note:
/«BUILDDIR»/svnkit-1.7.5+dfsg/svnkit-cli/src/main/java/org/tmatesoft/svn/cli/svn/SVNBlameCommand.java
uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 warning
[javac] /«BUILDDIR»/svnkit-1.7.5+dfsg/debian/build.xml:26: warning:
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set
to false for repeatable builds
[javac] Compiling 29 source files to
/«BUILDDIR»/svnkit-1.7.5+dfsg/svnkit-javahl16/bin
[javac] warning: [options] bootstrap class path not set in conjunction
with -source 1.5
[javac]
/«BUILDDIR»/svnkit-1.7.5+dfsg/svnkit-javahl16/src/main/java/org/apache/subversion/javahl/SVNClient.java:32:
error: SVNClient is not abstract and does not override abstract method
propertyGet(String,String,Revision,Revision,CollectionString) in ISVNClient
[javac] public class SVNClient implements ISVNClient {
[javac]^
[javac]
/«BUILDDIR»/svnkit-1.7.5+dfsg/svnkit-javahl16/src/main/java/org/tmatesoft/svn/core/javahl17/SVNClientImpl.java:159:
error: SVNClientImpl is not abstract and does not override abstract method
propertyGet(String,String,Revision,Revision,CollectionString) in ISVNClient
[javac] public class SVNClientImpl implements ISVNClient {
[javac]^
[javac]
