Bug#747740: FTBFS: Test ruby2.1 failed. Exiting.
Source: ruby-omniauth-facebook Version: 1.6.0-1 Severity: serious Justification: fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.0-rm Dear Maintainer, During a rebuild of ruby-related packages your package failed to build with these errors: === 1) Failure: CallbackUrlTest#test_returns_the_default_callback_url [/«PKGBUILDDIR»/test/test.rb:29]: unexpected invocation: #Mock:Request.scheme() 2) Failure: CallbackUrlTest#test_returns_path_from_callback_path_option [/«PKGBUILDDIR»/test/test.rb:37]: unexpected invocation: #Mock:Request.scheme() [..] 72 runs, 111 assertions, 2 failures, 0 errors, 0 skips ERROR: Test ruby2.1 failed. Exiting. dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-omniauth-facebook returned exit code 1 make: *** [binary] Error 1 debian/rules:15: recipe for target 'binary' failed dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 === Please note that the default ruby recently has been switched to 2.1 in sid. If your package doesn't already do this, please switch to the ruby(-all)(-dev) metapackages and `dh_ruby --print-supported` for detecting the ruby to build for. (Also, if everything goes according to plan, this is the last ruby transition for jessie.) About the test rebuild: this build was done in a rather standard sbuild/schroot setup, on an amd64 host where PID1 is provided by systemd, and options passed to sbuild were: DEB_BUILD_OPTIONS=parallel=12 Please find the full build log attached. Thanks, -ch ruby-omniauth-facebook_1.6.0-1_amd64.build Description: inode/symlink
Bug#747719: FTBFS: configure: error: The pkg-config script could not be found or is too old
Control: affects 747719 mkvtoolnix severity 747719 normal I must disagree with this severity change; mkvtoolnix does FTBFS, which is certainly severiy serious. Also it appears the `configure` script shipped in the mkvtoolnix source is the one calling and expecting `pkg-config`, so I'm not sure if reassigning to zlib is the correct thing to do here. (There are probably other means of finding zlib other than pkg-config.) -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#747720: FTBFS: install: cannot stat './libOpenCL.html': No such file or directory
* Vincent Danjean vdanjean...@free.fr [140511 15:37]: + exec faketime -f 2014-02-06 22:23:27+00:00 asciidoc -d manpage -b xhtml11 -olibOpenCL.html libOpenCL.7.txt shm_open: Bad address [...] In some setup, faketime does not work. See #747078 for more information for example. faketime is required to ensure the exact same file on all architectures as the package is multi-arch same. If you want ocl-icd build into your environment, please work on 747078 (or give me another way to ensure idempotent documentation build). I do not plan to take time to fix this issue myself (too much other things to do, sorry). While I agree that this is a faketime bug, I don't see why you need faketime here: 15:50 ch@nq:~/tmp/ocl-icd-2.1.3/doc % date Son Mai 11 15:50:27 CEST 2014 15:50 ch@nq:~/tmp/ocl-icd-2.1.3/doc % asciidoc -d manpage -b xhtml11 -olibOpenCL.html libOpenCL.7.txt 15:50 ch@nq:~/tmp/ocl-icd-2.1.3/doc % mv libOpenCL.html libOpenCL.html.backup 15:50 ch@nq:~/tmp/ocl-icd-2.1.3/doc % date Son Mai 11 15:51:03 CEST 2014 15:51 ch@nq:~/tmp/ocl-icd-2.1.3/doc % asciidoc -d manpage -b xhtml11 -olibOpenCL.html libOpenCL.7.txt 15:51 ch@nq:~/tmp/ocl-icd-2.1.3/doc % diff -u libOpenCL.html libOpenCL.html.backup 15:51 ch@nq:~/tmp/ocl-icd-2.1.3/doc % echo $? 0 Now I don't know M-A same specifics, but IIRC the files only need to be identical on a byte level, not on their mtime. But maybe I'm mistaken. Thanks, -ch -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#747681: FTBFS: Fatal: can't open /dev/urandom: Bad address
* Hilko Bengen ben...@debian.org [140511 16:49]: Control: tag -1 unreproducible * Christian Hofstaedtler: during a rebuild of ruby-related packages, your package failed to build. The rebuild was done in a current schroot using sbuild. I just rebuilt twice using sbuild and I can't reproduce the behavior. Can you reproduce it? Yes, I just did another rebuild (this time without parallel build), and it failed the same. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#747681: FTBFS: Fatal: can't open /dev/urandom: Bad address
* Hilko Bengen ben...@debian.org [140511 16:49]: I just rebuilt twice using sbuild and I can't reproduce the behavior. For reference, I'd believe my /dev/urandom works: % sudo sbuild-shell u I: 10mount: mount: warning: /var/lib/schroot/mount/unstable-amd64-sbuild-a9f09367-10a4-47a6-bee5-8fbaa85f2771/apt seems to be mounted read-write. I: /bin/sh # ls -la /dev/urandom crw-rw-rw- 1 root root 1, 9 Dec 30 07:02 /dev/urandom # stat /dev/urandom File: '/dev/urandom' Size: 0 Blocks: 0 IO Block: 4096 character special file Device: fe00h/65024dInode: 3150108 Links: 1 Device type: 1,9 Access: (0666/crw-rw-rw-) Uid: (0/root) Gid: (0/root) Access: 2014-01-27 11:39:45.488207458 + Modify: 2013-12-30 07:02:49.0 + Change: 2014-01-27 11:39:45.488207458 + Birth: - # dd if=/dev/urandom of=/tmp/foo bs=1024 count=1 1+0 records in 1+0 records out 1024 bytes (1.0 kB) copied, 0.000156614 s, 6.5 MB/s # Feel free to downgrade/close this bug if you think this is a chroot configuration issue on my side. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpQCg8xZJVxj.pgp Description: PGP signature
Bug#747078: #747078: faketime: fails with `shm_open: Bad address` inside chroot
Antonio, do you happen to use eatmydata in combination with your chroot? I'm seeing similar failures with sbuild/schroot + eatmydata. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747580: RM: ruby1.9.1 -- ROM; obsolete, replaced by ruby2.1, unsupported
Package: ftp.debian.org Severity: normal Dear ftpmasters, Please remove ruby1.9.1 from unstable, it has been replaced by ruby2.1. There are two or three packages left that still depend on it apart from a long list of sparc related dependencies. I'll add blockers for the non-sparc dependencies. Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747582: htree: Depends on obsolete versions of ruby
Source: htree Version: 0.8-1 Severity: serious Dear Maintainer, Your package depends on an obsolete version of Ruby. Please migrate it to use the ruby(-all)(-dev) metapackages. Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747609: transition: ruby2.0 removal
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear Release Team, now that ruby1.9.1 is gone, we, the Ruby maintainers, need to make sure that ruby2.0 is also not included in jessie. Similar to the ruby1.9.1-rm transition, we expect this to be rather smooth, but work on this is only starting now. What we'll need from you in the first step is the ben page. During the ruby1.9.1-rm transition we discovered very late in the process that we were missing some packages, esp. xapian-bindings. As I know very little about ben, please crosscheck the ben file. Thanks, Christian Ben file: title = ruby2.0; is_affected = .depends ~ /ruby/ | .build-depends ~ /ruby/; is_good = !.depends ~ /ruby2.0/ !.build-depends ~ /ruby2.0/; is_bad = .depends ~ /ruby2.0/ | .build-depends ~ /ruby2.0/; signature.asc Description: Digital signature
Bug#734342: Please migrate to ruby2.1
Control: retitle 734342 ruby-luabridge: Please migrate to ruby2.1 Hello, Ruby 1.9 has been removed from testing; Ruby 2.0 is in the process of being removed. Please migrate to Ruby 2.1 - or the metapackages - instead. Thank you, -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#747679: ruby2.0: Don't ship with jessie
Package: ruby2.0 Version: 2.0.0.484+really457-3 Severity: serious ruby2.0 is not meant to be shipped with jessie. This bug documents this and also makes sure it doesn't reenter testing when it is finally removed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747609: transition: ruby2.0 removal
* Julien Cristau jcris...@debian.org [140511 01:35]: Please file a serious bug against ruby2.0 titled something like do not ship with jessie, and tag it jessie and sid. Filed as #747679. -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747688: FTBFS: ERROR: Test ruby2.1 failed. Exiting
Source: ruby-imagesize Version: 0.1.1-5 Severity: serious Justification: fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.0-rm Dear Maintainer, During a rebuild of ruby-related packages your package failed to build with these errors: 1) Failure: TestImageSize#test_0_string [/«PKGBUILDDIR»/test/test_image_size.rb:43]: 640 expected but was nil. 2) Failure: TestImageSize#test_1_io [/«PKGBUILDDIR»/test/test_image_size.rb:65]: PNG expected but was OTHER. 2 tests, 10 assertions, 2 failures, 0 errors, 0 skips ruby -v: ruby 2.1.1p76 (2014-02-24) [x86_64-linux-gnu] ERROR: Test ruby2.1 failed. Exiting. dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/tmp returned exit code 1 make: *** [binary] Error 1 Please note that the default ruby has been switched to 2.1 in sid. If possible, please switch to the metapackages and `dh_ruby --print-supported` for detecting the ruby to build for. (Also, if everything goes according to plan, this is the last ruby transition for jessie.) Please find the full build log attached. Thanks, -ch ruby-imagesize_0.1.1-5_amd64.build Description: inode/symlink
Bug#747690: FTBFS: `require': cannot load such file -- spec_helper
Source: ruby-merb-haml Version: 1.1.3-2 Severity: serious Justification: fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.0-rm Dear Maintainer, During a rebuild of ruby-related packages your package failed to build with these errors: Running tests for ruby2.1 using debian/ruby-tests.rb... /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- spec_helper (LoadError) from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /«PKGBUILDDIR»/spec/haml_spec.rb:1:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from debian/ruby-tests.rb:4:in `block in main' from debian/ruby-tests.rb:3:in `each' from debian/ruby-tests.rb:3:in `main' ERROR: Test ruby2.1 failed. Exiting. dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/tmp returned exit code 1 make: *** [binary] Error 1 Please note that the default ruby has been switched to 2.1 in sid. If possible, please switch to the metapackages and `dh_ruby --print-supported` for detecting the ruby to build for. (Also, if everything goes according to plan, this is the last ruby transition for jessie.) Please find the full build log attached. Thanks, -ch ruby-merb-haml_1.1.3-2_amd64.build Description: inode/symlink
Bug#747406: rubygems intall/upgrade bug has corrupted the apt packaging system
* Stephen McGregor x...@stephen-mcgregor.com [140509 10:27]: Thanks for getting back on this. In answer to your questions: ls -al /usr/bin/ruby* -rwxr-xr-x 1 root root 5468 Apr 13 00:48 /usr/bin/ruby -rwxr-xr-x 1 root root 5544 Dec 2 12:52 /usr/bin/ruby1.8 -rwxr-xr-x 1 root root 5600 Dec 2 14:13 /usr/bin/ruby1.9.1 -rwxr-xr-x 1 root root 5468 Apr 13 00:48 /usr/bin/ruby2.0 It's unclear to me how you can end up with this configuration. Under both the old and the new regime, /usr/bin/ruby is always a symlink to one of the versioned files. Can you shed some light on this? -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747487: apt-listbugs: please don't break apt on failures
Package: apt-listbugs Version: 0.1.13 Severity: important Dear Francesco, please add a failure catcher to apt-listbugs, so that in common configurations apt doesn't break during an upgrade of ruby and related packages. As you know, the ruby wheezy-jessie upgrade path is already a little bit fragile, so it'd be nice if apt-listbugs could catch a missing ruby-debian extension. See #747406 for an example where apt-listbugs and ruby are already upgraded, but ruby-debian is still the old version (due to missing Breaks on ruby), and the user is left with a broken apt. Thanks! -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747489: Package descriptions talks about ruby 1.8
Package: ruby-httpclient Version: 2.3.3-2 Dear Maintainer, the description for your package ruby-httpclient is: HTTP client library for ruby (ruby 1.8 version) The part (ruby 1.8 version) is likely a leftover of the previous Ruby policy with per-version split packages; please remove it. Thanks, -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747490: how-can-i-help: Please don't break APT/dpkg on failures
Package: how-can-i-help Version: 6 Severity: important Dear Lucas, how-can-i-help plugs into apt/dpkg but apparently does not guard against import (and other) errors that can arise during package upgrades, especially when the upgrade is aborted before it's complete. It'd be great if how-can-i-help would always exit with status 0 when it's called from apt/dpkg, regardless if it worked or not. (LoadErrors and other possible errors cause ruby to exit with 1.) Thanks, -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747487: apt-listbugs: please don't break apt on failures
Hi Francesco, * Francesco Poli invernom...@paranoici.org [140509 19:20]: On Fri, 9 May 2014 11:39:05 +0200 Christian Hofstaedtler wrote: please add a failure catcher to apt-listbugs, so that in common configurations apt doesn't break during an upgrade of ruby and related packages. Could you elaborate a bit, please? Yeah, sorry for writing this in a not really clear way. Do you think that apt-listbugs should realize that it's failing to load the debian_version (binary) module and just exit with zero status without doing anything? I /think/ in cases where it's hopeless for apt-listbugs to start working again, it should just exit with zero. A LoadError exception (and maybe others?) might be a good indicator for such a condition. The fact is that, if the user wants apt-listbugs to run before each installation or upgrade by APT in order to check whether the installation/upgrade is safe, apt-listbugs should stop APT whenever it is *not* able to perform its normal checks (running and querying the BTS, and so forth...). I think this is a feature, not a bug. At least as far as I am personally concerned, if I am about to upgrade, say, some 60 or 70 packages and apt-listbugs cannot run, I want to stop the upgrade immediately, examine the situation, fix the minimum needed to let apt-listbugs run correctly, and *only after that* proceed with the upgrade! I am of course open to any suggestion to improve apt-listbugs, as long as it takes this need into account. I do agree with you on basically everything you said above; altough I'm concerned about users that somehow use apt-listbugs because it's there, not because it was their concious choice. Now I don't know how they end up with that -- I haven't installed Debian using d-i in a long time, so I might have missed any defaults set by d-i -- but apparently there are users that can't fix temporary issues such as this one on their own. As you know, the ruby wheezy-jessie upgrade path is already a little bit fragile, so it'd be nice if apt-listbugs could catch a missing ruby-debian extension. I think that the ruby upgrade path should be made less fragile. I don't think that compensating for a fragile language interpreter upgrade path should be the responsibility of each single application... See #747406 for an example where apt-listbugs and ruby are already upgraded, but ruby-debian is still the old version (due to missing Breaks on ruby), and the user is left with a broken apt. As I have previously said in the past, I think that some Breaks would be highly useful to make the upgrade path more robust... Please consider addressing the issue from this side. Yes, I agree; ruby (from src:ruby-defaults) needs to Break ruby-debian, but I didn't think of that -- will fix that (hopefully tomorrow). I hope this line of reasoning makes sense to you. Thanks for the great work on Ruby packaging! Yep. Thanks for your insight. Most of the Ruby packaging is really Antonio's work though :-) Christian -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgp96htsmp1o4.pgp Description: PGP signature
Bug#747232: Ruby should support SystemTap
* Sebastian Boehm sebast...@sometimesfood.org [140508 00:12]: The current probe selection syntax is rather basic, but if the patch above is accepted, I could add a simple tap file in order to turn process(/usr/lib/x86_64-linux-gnu/libruby-2.1.so.2.1).mark(method__entry”) into ruby.method.entry I would add another bug report for this, though. Please expand on this - would this mean additional changes to the Ruby package? If so, please show us :-) -ch -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpsgAc3GJvPs.pgp Description: PGP signature
Bug#747406: rubygems intall/upgrade bug has corrupted the apt packaging system
Thanks for your report. Please provide the output of these commands: ls -la /usr/bin/ruby* dpkg -l ruby\* how-can-i-help apt-listbugs -ch -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpaJBLFUdDc9.pgp Description: PGP signature
Bug#739611: ruby1.9.1-rm transition
Dear Release Team, Please remove ruby1.9.1 at your earliest convenience from testing. `dak rm -s testing ruby1.9.1` gives the following leftovers: - xapian-bindings: should go in today if I haven't missed anything - ruby-patron: FTBFS, will certainly take a long time to fix - ruby-gnome2: fix in sid, but new RC bug has appeared - coquelicot: fix in sid, uploaded with prio=low - sup-mail: FTBFS, no fix in sight yet A full rm list would be: ruby-patron ruby-faraday ruby-omniauth-twitter ruby-sham-rack rabbit ruby-faraday-middleware ruby-oauth2 ruby-sawyer ruby-twitter ruby-carrierwave ruby-typhoeus ruby-octokit ruby-omniauth-oauth2 ruby-tinder ruby-omniauth-facebook ruby-omniauth-facebook ruby-omniauth-google-oauth2 ruby-gnome2 ruby-atk ruby-cairo-gobject ruby-gdk-pixbuf2 ruby-gdk3 ruby-gio2 ruby-glib2 ruby-gobject-introspection ruby-gstreamer ruby-gtk2 ruby-gtk3 ruby-gtksourceview2 ruby-gtksourceview3 ruby-pango ruby-poppler ruby-rsvg2 ruby-vte ruby-vte3 kindleclip mhc mikutter rabbit ruby-globalhotkeys screenruler coquelicot sup-mail ruby1.9.1 Thank you, -ch -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpSyN1AF5bUi.pgp Description: PGP signature
Bug#739611: Current status of ruby1.9.1-rm transition
A quick status update of the current state of the transition. If ruby1.9.1 was removed today, the following things would break / removed too: coquelicot # FTBFS (ruby1.9.1) sup-mail # FTBFS (ruby1.9.1) + waiting for xapian-bindings ruby-libvirt # not-ruby-caused FTBFS # ruby-gnome2 FTBFS 744809 - autoremoval scheduled for 2014-05-29 ruby-gnome2 ruby-atk ruby-cairo-gobject ruby-gdk-pixbuf2 ruby-gdk3 ruby-gio2 ruby-glib2 ruby-gobject-introspection ruby-gstreamer ruby-gtk2 ruby-gtk3 ruby-gtksourceview2 ruby-gtksourceview3 ruby-pango ruby-poppler ruby-rsvg2 ruby-vte ruby-vte3 kindleclip mhc mikutter rabbit ruby-globalhotkeys screenruler rabbit # ruby-patron FTBFS 744034 - autoremoval scheduled for 2014-05-08 ruby-patron ruby-faraday ruby-omniauth-twitter ruby-sham-rack rabbit ruby-faraday-middleware ruby-oauth2 ruby-sawyer ruby-twitter ruby-carrierwave ruby-typhoeus ruby-octokit ruby-omniauth-oauth2 ruby-tinder ruby-omniauth-facebook ruby-omniauth-facebook ruby-omniauth-google-oauth2 # waiting to transition to testing cairo-dock-plug-ins evernote-mode swig2.0 xapian-bindings Some more details for select packages: - a fixed version of xapian-bindings has been uploaded today, and it built everywhere. - work on a newer ruby-gnome2 is ongoing. The packages that are currently waiting to transition unfortuntely don't appear in the transition tracker as bad; for the next transition we need to be more careful with the ben filters. Apart from the packages waiting to transition my personal opinion would be to break/remove the listed packages from testing. Thoughts? -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#746495: xapian-bindings: diff for NMU version 1.2.17-1.1
* Christian Hofstaedtler z...@debian.org [140501 02:30]: I also certainly see why it'd be better if you'd do the upload instead of my NMU -- I didn't feel comfortable with the diff. So... should I cancel that NMU? Thanks, -ch -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpCGSUSG9677.pgp Description: PGP signature
Bug#746495: xapian-bindings: diff for NMU version 1.2.17-1.1
* Olly Betts o...@survex.com [140502 11:49]: On Fri, May 02, 2014 at 10:53:00AM +0200, Christian Hofstaedtler wrote: * Christian Hofstaedtler z...@debian.org [140501 02:30]: I also certainly see why it'd be better if you'd do the upload instead of my NMU -- I didn't feel comfortable with the diff. So... should I cancel that NMU? I think that's best - I should be able to sort this out over the weekend. Alright, cancelled. Thanks, -ch -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpVwH_JzAXSt.pgp Description: PGP signature
Bug#746495: xapian-bindings: diff for NMU version 1.2.17-1.1
Package: xapian-bindings
Version: 1.2.17-1
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for xapian-bindings (versioned as 1.2.17-1.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.
[Chosing 3 days because this affects the ruby1.9.1-rm transition and
apparently upcoming ports.]
Regards.
diff -Nru xapian-bindings-1.2.17/debian/changelog
xapian-bindings-1.2.17/debian/changelog
--- xapian-bindings-1.2.17/debian/changelog 2014-01-31 02:59:53.0
+0100
+++ xapian-bindings-1.2.17/debian/changelog 2014-04-30 16:58:40.0
+0200
@@ -1,3 +1,24 @@
+xapian-bindings (1.2.17-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Christian Hofstaedtler ]
+ * Rebuild for Ruby 2.0/2.1, dropping Ruby 1.9.1. (Closes: #745924)
+Thanks to Matthias Klose d...@ubuntu.com for the missing pieces
+when I couldn't get this to build. (Basically this merges the
+Ubuntu patch.)
+ * Apply patch to fix binary-indep build from Matthias Klose
+d...@ubuntu.com.
+ * Apply patch to fix build on ppc64el from Matthias Klose
+d...@ubuntu.com.
+
+ [ Matthias Klose ]
+ * Fix the binary-indep build.
+ * Explicitely use automake1.11.
+ * Build using dh-autoreconf. (Closes: #746239)
+
+ -- Christian Hofstaedtler z...@debian.org Wed, 30 Apr 2014 16:31:01 +0200
+
xapian-bindings (1.2.17-1) unstable; urgency=medium
* New upstream release.
diff -Nru xapian-bindings-1.2.17/debian/control
xapian-bindings-1.2.17/debian/control
--- xapian-bindings-1.2.17/debian/control 2014-01-31 04:13:00.0
+0100
+++ xapian-bindings-1.2.17/debian/control 2014-04-30 17:02:37.0
+0200
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Olly Betts o...@survex.com
Standards-Version: 3.9.5
-Build-Depends: debhelper (= 7.0.50~), python, python-all-dev (= 2.6.6-3~),
tcl-dev, ruby1.9.1-dev, ruby2.0-dev, ruby1.9.1, ruby2.0, libxapian-dev (=
1.2.17), libxapian-dev ( 1.3.0), autotools-dev
+Build-Depends: debhelper (= 7.0.50~), python, python-all-dev (= 2.6.6-3~),
tcl-dev, ruby2.0-dev, ruby2.1-dev, ruby2.0, ruby2.1, libxapian-dev (= 1.2.17),
libxapian-dev ( 1.3.0), autotools-dev, automake1.11, dh-autoreconf
X-Python-Version: = 2.3
XS-Ruby-Versions: all
Homepage: http://xapian.org/
@@ -59,7 +59,6 @@
Depends: ruby | ruby-interpeter, ${shlibs:Depends}, ${misc:Depends}
Replaces: libxapian-ruby1.8 ( 1.2.15-1~), libxapian-ruby1.9.1 ( 1.2.15-1~)
Breaks: libxapian-ruby1.8 ( 1.2.15-1~), libxapian-ruby1.9.1 ( 1.2.15-1~)
-Provides: libxapian-ruby1.9.1
Suggests: xapian-doc
Description: Xapian search engine interface for Ruby
This package provides Xapian Ruby bindings built for Ruby.
@@ -74,12 +73,3 @@
.
The Xapian Ruby bindings provide an interface to the Xapian library from the
Ruby programming language, allowing both indexing and retrieval operations.
-
-Package: libxapian-ruby1.9.1
-Section: oldlibs
-Priority: extra
-Architecture: all
-depends: ${misc:Depends}, ruby-xapian
-Description: Transitional package for ruby-xapian
- This is a transitional package to ease upgrades to the ruby-xapian package.
- It can be safely removed.
diff -Nru xapian-bindings-1.2.17/debian/control.in
xapian-bindings-1.2.17/debian/control.in
--- xapian-bindings-1.2.17/debian/control.in2014-01-24 02:50:09.0
+0100
+++ xapian-bindings-1.2.17/debian/control.in2014-04-30 16:59:59.0
+0200
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Olly Betts o...@survex.com
Standards-Version: 3.9.5
-Build-Depends: @BUILD_DEPS@ autotools-dev
+Build-Depends: @BUILD_DEPS@ autotools-dev, automake1.11, dh-autoreconf
@X_PYTHON_VERSION@
@XS_RUBY_VERSIONS@
Homepage: http://xapian.org/
diff -Nru xapian-bindings-1.2.17/debian/control-ruby-new.in
xapian-bindings-1.2.17/debian/control-ruby-new.in
--- xapian-bindings-1.2.17/debian/control-ruby-new.in 2014-01-30
23:20:21.0 +0100
+++ xapian-bindings-1.2.17/debian/control-ruby-new.in 2014-04-30
16:36:25.0 +0200
@@ -6,7 +6,6 @@
Depends: ruby | ruby-interpeter, ${shlibs:Depends}, ${misc:Depends}
Replaces: libxapian-ruby1.8 ( 1.2.15-1~), libxapian-ruby1.9.1 ( 1.2.15-1~)
Breaks: libxapian-ruby1.8 ( 1.2.15-1~), libxapian-ruby1.9.1 ( 1.2.15-1~)
-Provides: @RUBY_PROVIDES@
Suggests: xapian-doc
Description: Xapian search engine interface for Ruby
This package provides Xapian Ruby bindings built for Ruby.
diff -Nru xapian-bindings-1.2.17/debian/ruby-xapian.install
xapian-bindings-1.2.17/debian/ruby-xapian.install
--- xapian-bindings-1.2.17/debian/ruby-xapian.install 2014-01-31
04:13:00.0 +0100
+++ xapian-bindings-1.2.17/debian/ruby-xapian.install 2014-04-30
17:02:37.0 +0200
@@ -1,5 +1,4 @@
-usr/lib/ruby/vendor_ruby/1.9.1/xapian.rb usr/lib/ruby/vendor_ruby
-usr/lib/ruby/vendor_ruby/*.*/*-*
-usr/share/doc/xapian-bindings-ruby1.9.1/ruby/* usr/share/doc/ruby-xapian
-usr/share/doc/xapian-bindings-ruby1.9.1/ruby/examples/*.rb
usr/share/doc
Bug#746495: xapian-bindings: diff for NMU version 1.2.17-1.1
* Olly Betts o...@survex.com [140501 00:02]: On Wed, Apr 30, 2014 at 05:09:00PM +0200, Christian Hofstaedtler wrote: I've prepared an NMU for xapian-bindings (versioned as 1.2.17-1.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. [Chosing 3 days because this affects the ruby1.9.1-rm transition and apparently upcoming ports.] A DELAYED/3 NMU for a 4 day old bug seems rather impatient. This bug is already on my list to deal with, but I'm a bit backlogged after being away last week. How urgent is this? I'd rather not have to deal with fall-out from a bad NMU on top of everything else I have to do. I tried to look at the transition tracker to get an idea, but it shows xapian-bindings as good already: https://release.debian.org/transitions/html/ruby1.9.1-rm.html I don't know why it does that, but it's wrong. `dak rm -s testing ruby1.9.1` still shows that xapian-bindings would need to go, but given the list of rdepends it really needs fixing. Given that the transition tracker is wrong on this, it hasn't been noticed early enough, and I expect that in 3 days all packages that would block the removal are at least in sid, plus on their good way into testing. IIRC (excluding xapian-bindings) we should reach a good state in jessie on 5th or 6th of May. If you want, I can certainly cancel the DELAYED upload, but I really want to see this [the ruby parts] fixed ASAP. I also certainly see why it'd be better if you'd do the upload instead of my NMU -- I didn't feel comfortable with the diff. Thank you, -ch -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpeQxO4UYqWt.pgp Description: PGP signature
Bug#745923: evernote-mode: Build-Depends on obsolete ruby1.9.1
Source: evernote-mode Version: 0.41-3 Severity: serious Dear Maintainer, Your package has a Build-Depends on ruby1.9.1, which is obsolete. Please migrate to the ruby metapackage or if that is not possible, ruby2.1. Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745924: xapian-bindings: Build-Depends on obsolete ruby1.9.1(-dev)
Source: xapian-bindings Version: 1.2.17-1 Severity: serious Dear Maintainer, Your package Build-Depends on the obsolete ruby1.9.1 and ruby1.9.1-dev packages. Please migrate to the ruby and ruby-all-dev metapackages, or if that is not possible to ruby2.1(-dev). Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745926: cairo-dock-plug-ins: Build-Depends on obsolete ruby1.9.1(-dev)
Source: cairo-dock-plug-ins Version: 3.3.2-3 Severity: serious Dear Maintainer, Your package Build-Depends on the obsolete ruby1.9.1 and ruby1.9.1-dev packages. Please migrate to the ruby and ruby-all-dev metapackages, or, if that is not possible, to ruby2.1(-dev). Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745927: swig2.0: Build-Depends on obsolete ruby1.9.1(-dev)
Source: swig2.0 Version: 2.0.11-1 Severity: serious Dear Maintainer, Your package Build-Depends on the obsolete ruby1.9.1 and ruby1.9.1-dev packages. Please migrate to the ruby and ruby-all-dev metapackages, or, if that is not possible, to ruby2.1(-dev). Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745928: ruby-hiredis: FTBFS on s390x: test_no_eagain_after_cumulative_wait_exceeds_timeout
Source: ruby-hiredis Version: 0.5.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Your package FTBFS on s390x, with this output: 1) Error: test_no_eagain_after_cumulative_wait_exceeds_timeout(ExtConnectionTest): Errno::EAGAIN: Resource temporarily unavailable /«PKGBUILDDIR»/lib/hiredis/ext/connection.rb:19:in `read' /«PKGBUILDDIR»/lib/hiredis/ext/connection.rb:19:in `read' /«PKGBUILDDIR»/test/connection_test.rb:335:in `block in test_no_eagain_after_cumulative_wait_exceeds_timeout' /«PKGBUILDDIR»/test/connection_test.rb:26:in `block in listen' /«PKGBUILDDIR»/test/connection_test.rb:17:in `popen' /«PKGBUILDDIR»/test/connection_test.rb:17:in `listen' /«PKGBUILDDIR»/test/connection_test.rb:316:in `test_no_eagain_after_cumulative_wait_exceeds_timeout' /usr/lib/ruby/2.0.0/minitest/unit.rb:1301:in `run' /usr/lib/ruby/2.0.0/test/unit/testcase.rb:17:in `run' /usr/lib/ruby/2.0.0/minitest/unit.rb:919:in `block in _run_suite' /usr/lib/ruby/2.0.0/minitest/unit.rb:912:in `map' /usr/lib/ruby/2.0.0/minitest/unit.rb:912:in `_run_suite' /usr/lib/ruby/2.0.0/test/unit.rb:657:in `block in _run_suites' /usr/lib/ruby/2.0.0/test/unit.rb:655:in `each' /usr/lib/ruby/2.0.0/test/unit.rb:655:in `_run_suites' /usr/lib/ruby/2.0.0/minitest/unit.rb:867:in `_run_anything' /usr/lib/ruby/2.0.0/minitest/unit.rb:1060:in `run_tests' /usr/lib/ruby/2.0.0/minitest/unit.rb:1047:in `block in _run' /usr/lib/ruby/2.0.0/minitest/unit.rb:1046:in `each' /usr/lib/ruby/2.0.0/minitest/unit.rb:1046:in `_run' /usr/lib/ruby/2.0.0/minitest/unit.rb:1035:in `run' /usr/lib/ruby/2.0.0/test/unit.rb:21:in `run' /usr/lib/ruby/2.0.0/test/unit.rb:774:in `run' /usr/lib/ruby/2.0.0/test/unit.rb:366:in `block (2 levels) in autorun' /usr/lib/ruby/2.0.0/test/unit.rb:27:in `run_once' /usr/lib/ruby/2.0.0/test/unit.rb:365:in `block in autorun' 72 tests, 94 assertions, 0 failures, 1 errors, 0 skips ruby -v: ruby 2.0.0p457 (2014-03-03) [s390x-linux-gnu] ERROR: Test ruby2.0 failed. Exiting. See the buildd log for details: https://buildd.debian.org/status/fetch.php?pkg=ruby-hiredisarch=s390xver=0.5.1-1stamp=1396619115 Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745929: ruby-sqlite3: FTBFS on mips, powerpc, s390x
Source: ruby-sqlite3 Version: 1.3.9-1 Severity: serious Justification: fails to build from source Dear Maintainer, Your packages failed to build from source on these architectures: mips, powerpc, s390x On all of them these tests fail: 1) Failure: SQLite3::TestEncoding#test_insert_encoding [/«PKGBUILDDIR»/test/test_encoding.rb:42]: Expected: foo Actual: \u6600\u6F00\u6F00 2) Error: SQLite3::TestEncoding#test_select_encoding_on_utf_16: SQLite3::SQLException: table ex already exists /«PKGBUILDDIR»/debian/ruby-sqlite3/usr/lib/ruby/vendor_ruby/sqlite3/database.rb:91:in `initialize' /«PKGBUILDDIR»/debian/ruby-sqlite3/usr/lib/ruby/vendor_ruby/sqlite3/database.rb:91:in `new' /«PKGBUILDDIR»/debian/ruby-sqlite3/usr/lib/ruby/vendor_ruby/sqlite3/database.rb:91:in `prepare' /«PKGBUILDDIR»/debian/ruby-sqlite3/usr/lib/ruby/vendor_ruby/sqlite3/database.rb:134:in `execute' /«PKGBUILDDIR»/test/test_encoding.rb:17:in `test_select_encoding_on_utf_16' /usr/lib/ruby/vendor_ruby/minitest/test.rb:106:in `block (3 levels) in run' /usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions' /usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/minitest/test.rb:256:in `time_it' /usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `block in run' /usr/lib/ruby/vendor_ruby/minitest.rb:317:in `on_signal' /usr/lib/ruby/vendor_ruby/minitest/test.rb:276:in `with_info_handler' /usr/lib/ruby/vendor_ruby/minitest/test.rb:101:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:759:in `run_one_method' /usr/lib/ruby/vendor_ruby/minitest.rb:293:in `run_one_method' /usr/lib/ruby/vendor_ruby/minitest.rb:287:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/minitest.rb:286:in `each' /usr/lib/ruby/vendor_ruby/minitest.rb:286:in `block in run' /usr/lib/ruby/vendor_ruby/minitest.rb:317:in `on_signal' /usr/lib/ruby/vendor_ruby/minitest.rb:306:in `with_info_handler' /usr/lib/ruby/vendor_ruby/minitest.rb:285:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:149:in `block in __run' /usr/lib/ruby/vendor_ruby/minitest.rb:149:in `map' /usr/lib/ruby/vendor_ruby/minitest.rb:149:in `__run' /usr/lib/ruby/vendor_ruby/minitest.rb:126:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:55:in `block in autorun' 232 runs, 371 assertions, 1 failures, 1 errors, 1 skips You have skipped tests. Run with --verbose for details. ERROR: Test ruby2.0 failed. Exiting. For details please see the buildd logs at: https://buildd.debian.org/status/package.php?p=ruby-sqlite3 Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745927: swig2.0: diff for NMU version 2.0.11-1.1
tags 745927 + patch tags 745927 + pending thanks Dear maintainer, I've prepared an NMU for swig2.0 (versioned as 2.0.11-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru swig2.0-2.0.11/debian/changelog swig2.0-2.0.11/debian/changelog --- swig2.0-2.0.11/debian/changelog 2013-10-25 23:37:32.0 +0200 +++ swig2.0-2.0.11/debian/changelog 2014-04-26 17:26:42.0 +0200 @@ -1,3 +1,11 @@ +swig2.0 (2.0.11-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Build with the default Ruby instead of hardcoding ruby1.9.1. + (Closes: #745927) + + -- Christian Hofstaedtler christ...@hofstaedtler.name Sat, 26 Apr 2014 17:23:59 +0200 + swig2.0 (2.0.11-1) unstable; urgency=low * Merge new upstream release 2.0.11 (closes: #727188). diff -Nru swig2.0-2.0.11/debian/control swig2.0-2.0.11/debian/control --- swig2.0-2.0.11/debian/control 2013-10-25 22:59:42.0 +0200 +++ swig2.0-2.0.11/debian/control 2014-04-26 17:27:15.0 +0200 @@ -18,8 +18,8 @@ php5-cgi, php5-dev, python-dev, - ruby1.9.1, - ruby1.9.1-dev, + ruby, + ruby-dev, tcl-dev, tk-dev diff -Nru swig2.0-2.0.11/debian/rules swig2.0-2.0.11/debian/rules --- swig2.0-2.0.11/debian/rules 2013-10-25 23:37:32.0 +0200 +++ swig2.0-2.0.11/debian/rules 2014-04-26 17:23:50.0 +0200 @@ -20,7 +20,7 @@ --prefix=/usr --mandir=/usr/share/man \ --with-tclconfig=/usr/lib \ --with-python=/usr/bin/python \ - --with-ruby=/usr/bin/ruby1.9.1 \ + --with-ruby=/usr/bin/ruby \ --with-pike=/usr/bin/pike7.6\ --with-pikeincl=/usr/include/pike/7.6.24\ --with-swiglibdir=/usr/share/swig2.0\ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745923: evernote-mode: diff for NMU version 0.41-3.1
tags 745923 + patch tags 745923 + pending thanks Dear maintainer, I've prepared an NMU for evernote-mode (versioned as 0.41-3.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru evernote-mode-0.41/debian/changelog evernote-mode-0.41/debian/changelog --- evernote-mode-0.41/debian/changelog 2012-07-04 13:24:08.0 +0200 +++ evernote-mode-0.41/debian/changelog 2014-04-26 17:45:42.0 +0200 @@ -1,3 +1,11 @@ +evernote-mode (0.41-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Build using/for the default Ruby, instead of hardcoding 1.9.1. + (Closes: #745923) + + -- Christian Hofstaedtler z...@debian.org Sat, 26 Apr 2014 17:45:39 +0200 + evernote-mode (0.41-3) unstable; urgency=low * Update/refresh patches: use gbp-pq diff -Nru evernote-mode-0.41/debian/control evernote-mode-0.41/debian/control --- evernote-mode-0.41/debian/control 2012-07-04 13:24:33.0 +0200 +++ evernote-mode-0.41/debian/control 2014-04-26 17:41:44.0 +0200 @@ -2,7 +2,7 @@ Section: lisp Priority: optional Maintainer: Youhei SASAKI uwab...@gfd-dennou.org -Build-Depends: debhelper (= 7.0.50~), ruby1.9.1 +Build-Depends: debhelper (= 7.0.50~), ruby | ruby-interpreter Standards-Version: 3.9.3 DM-Upload-Allowed: yes Homepage: http://code.google.com/p/emacs-evernote-mode/ diff -Nru evernote-mode-0.41/debian/rules evernote-mode-0.41/debian/rules --- evernote-mode-0.41/debian/rules 2012-06-14 20:51:18.0 +0200 +++ evernote-mode-0.41/debian/rules 2014-04-26 17:44:43.0 +0200 @@ -6,6 +6,7 @@ PKG_DESTDIR := $(CURDIR)/debian/$(PKG_NAME) PKG_DOCDIR := $(PKG_DESTDIR)/usr/share/doc/$(PKG_NAME) libdir=$(shell ruby -rrbconfig -e 'puts Config::CONFIG[vendordir]') +rubylibdir=$(shell ruby -rrbconfig -e 'puts RbConfig::CONFIG[rubylibdir]') %: dh $@ @@ -29,11 +30,11 @@ override_dh_installdocs: (cd $(PKG_DESTDIR) \ - rdoc1.9.1 -a --fmt=darkfish -o $(PKG_DOCDIR)/rdoc usr/lib/ruby/vendor_ruby/ ) + rdoc -a --fmt=darkfish -o $(PKG_DOCDIR)/rdoc usr/lib/ruby/vendor_ruby/ ) rm -f $(PKG_DESTDIR)/usr/share/doc/$(PKG_NAME)/rdoc/js/*.js for f in darkfish jquery quicksearch thickbox-compressed ; do \ (cd $(PKG_DESTDIR)/usr/share/doc/$(PKG_NAME)/rdoc/js \ - ln -s ../../../../../lib/ruby/1.9.1/rdoc/generator/template/darkfish/js/$$f.js . ) ;\ + ln -s $(rubylibdir)/rdoc/generator/template/darkfish/js/$$f.js . ) ;\ done dh_installdocs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745926: cairo-dock-plug-ins: diff for NMU version 3.3.2-3.1
tags 745926 + patch
tags 745926 + pending
thanks
Dear maintainer,
I've prepared an NMU for cairo-dock-plug-ins (versioned as 3.3.2-3.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru cairo-dock-plug-ins-3.3.2/debian/changelog
cairo-dock-plug-ins-3.3.2/debian/changelog
--- cairo-dock-plug-ins-3.3.2/debian/changelog 2013-11-18 06:25:15.0
+0100
+++ cairo-dock-plug-ins-3.3.2/debian/changelog 2014-04-26 17:57:23.0
+0200
@@ -1,3 +1,11 @@
+cairo-dock-plug-ins (3.3.2-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Build for the default Ruby version, instead of hardcoding any.
+ (Closes: #745926)
+
+ -- Christian Hofstaedtler z...@debian.org Sat, 26 Apr 2014 17:56:53 +0200
+
cairo-dock-plug-ins (3.3.2-3) unstable; urgency=low
* Update debian/rules.
diff -Nru cairo-dock-plug-ins-3.3.2/debian/control
cairo-dock-plug-ins-3.3.2/debian/control
--- cairo-dock-plug-ins-3.3.2/debian/control2013-11-18 00:18:42.0
+0100
+++ cairo-dock-plug-ins-3.3.2/debian/control2014-04-26 17:52:42.0
+0200
@@ -43,8 +43,8 @@
mono-gmcs [amd64 armel i386 kfreebsd-any powerpc s390x],
python,
python3,
- ruby1.9.1,
- ruby1.9.1-dev,
+ ruby,
+ ruby-dev,
valac,
x11proto-xf86vidmode-dev
Standards-Version: 3.9.4
diff -Nru cairo-dock-plug-ins-3.3.2/debian/patches/ruby-vendor-dir.patch
cairo-dock-plug-ins-3.3.2/debian/patches/ruby-vendor-dir.patch
--- cairo-dock-plug-ins-3.3.2/debian/patches/ruby-vendor-dir.patch
1970-01-01 01:00:00.0 +0100
+++ cairo-dock-plug-ins-3.3.2/debian/patches/ruby-vendor-dir.patch
2014-04-26 18:06:23.0 +0200
@@ -0,0 +1,24 @@
+Index: cairo-dock-plug-ins-3.3.2/CMakeLists.txt
+===
+--- cairo-dock-plug-ins-3.3.2.orig/CMakeLists.txt 2013-10-29
11:27:30.0 +0100
cairo-dock-plug-ins-3.3.2/CMakeLists.txt 2014-04-26 18:06:15.528495946
+0200
+@@ -533,7 +533,7 @@ if (enable-ruby-interface)
+ message (STATUS * Ruby:)
+ # find_package(Ruby) found libs of ruby-dev but we only need a
directory where we can install ruby libs.
+ find_program (RUBY_EXECUTABLE ruby)
+- EXECUTE_PROCESS(COMMAND ${RUBY_EXECUTABLE} -r rbconfig -e print
RbConfig::CONFIG['rubylibdir']
++ EXECUTE_PROCESS(COMMAND ${RUBY_EXECUTABLE} -r rbconfig -e print
RbConfig::CONFIG['vendordir']
+ OUTPUT_VARIABLE RUBY_LIB_DIR)
+ message (STATUSRuby library dir: ${RUBY_LIB_DIR})
+ if (${RUBY_LIB_DIR} STREQUAL OR ${RUBY_LIB_DIR} STREQUAL nil)
+@@ -542,10 +542,6 @@ if (enable-ruby-interface)
+ set (PROGRAMS_MISSING ${PROGRAMS_MISSING} ruby)
+ set (with_ruby no)
+ else()
+- # /usr/lib/ruby/1.8 or /usr/lib/ruby/1.9.1
+- string (REGEX REPLACE lib/ruby/[0-9].[0-9]?.+
RUBY_LIB_DIR_INSTALL ${RUBY_LIB_DIR})
+- string (REGEX REPLACE ${RUBY_LIB_DIR_INSTALL}
RUBY_LIB_DIR_INSTALL ${RUBY_LIB_DIR})
+- set (RUBY_LIB_DIR
${CMAKE_INSTALL_PREFIX}/${RUBY_LIB_DIR_INSTALL})
+ message (STATUSwill be installed in: ${RUBY_LIB_DIR})
+ set (RUBY_FOUND TRUE)
+ set (with_ruby yes)
diff -Nru cairo-dock-plug-ins-3.3.2/debian/patches/series
cairo-dock-plug-ins-3.3.2/debian/patches/series
--- cairo-dock-plug-ins-3.3.2/debian/patches/series 2013-10-25
18:25:39.0 +0200
+++ cairo-dock-plug-ins-3.3.2/debian/patches/series 2014-04-26
17:55:04.0 +0200
@@ -1,2 +1,3 @@
0001-Fix-typo-about-SystemMonitor-Mail-dnd2share-Stack-GV.patch
0001-Fix-MATCH-as-FreeBSD.patch
+ruby-vendor-dir.patch
diff -Nru cairo-dock-plug-ins-3.3.2/debian/rules
cairo-dock-plug-ins-3.3.2/debian/rules
--- cairo-dock-plug-ins-3.3.2/debian/rules 2013-11-18 06:24:47.0
+0100
+++ cairo-dock-plug-ins-3.3.2/debian/rules 2014-04-26 17:56:50.0
+0200
@@ -20,10 +20,6 @@
CLI_ARCH=zamd64z zarmelz zi386z zkfreebsd-i386z \
zkfreebsd-amd64z zpowerpcz zs390xz
-install/ruby-cdapplet::
- install -m 644 -D debian/tmp/usr/lib/ruby/1.9.1/CDApplet.rb \
- debian/tmp/usr/lib/ruby/vendor_ruby/1.9.1/CDApplet.rb
-
common-binary-predeb-arch::
ifneq (,$(findstring z$(DEB_HOST_ARCH)z, $(CLI_ARCH)))
dh_clifixperms
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745724: supermin: FTBFS on mips, mipsel, powerpc
Source: supermin Version: 5.1.7-1 Severity: serious Justification: fails to build from source Dear Maintainer, Your package supermin FTBFS on multiple archs on buildd.debian.org: mips, mipsel and powerpc On all of these archs the test suite apparently fails: FAIL: test-build-bash.sh [...] Testsuite summary for supermin 5.1.7 # TOTAL: 4 # PASS: 3 # SKIP: 0 # XFAIL: 0 make[4]: *** [test-suite.log] Error 1 # FAIL: 1 # XPASS: 0 # ERROR: 0 [...] make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Thanks, -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742283: #742283: supermin 5.1.5 issue - close?
Hi, The bug #742283 apparently is about supermin 5.1.5, and there's a message indicating this doesn't occur with 5.1.6. Now sid already's got 5.1.7, so should this bug be marked fixed + closed? Thanks, -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745465: ruby2.1: FTBFS: usr/lib/ruby/gems/2.1.0/specifications/default/json-1.8.1.gemspec should exist: FAIL
* Thorsten Glaser t...@mirbsd.de [140422 03:30]: Source: ruby2.1 Version: 2.1.1-2 Severity: important Justification: fails to build from source Hi, I cannot build ruby2.1 on m68k. Build log attached. I’ve got no ruby-related skills and cannot discover the reason. From the looks of the log, you've got rubygems-integration installed. I think the version in sid currently can not be built when rubygems-integration is installed at the same time (it redirects install paths). If ruby2.0 again hard Depends on rubygems-integration (and it has good reasons to), then I'd better upload a fix for this sooner than later. -ch -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744813: [DRE-maint] Bug#744813: this segfault is inconsistent
* Pirate Praveen prav...@debian.org [140415 03:09]: and hard to reproduce https://github.com/toland/patron/issues/72 Srihari was trying to reproduce this but couldn't https://poddery.com/posts/1048346 The buildds apparently are good reproducer hosts, and by the look of it it might happen more often on slower or !64bit archs. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpoVFEPM0i_c.pgp Description: PGP signature
Bug#739611: Second round of binNMUs for ruby1.9.1-rm
* Niels Thykier ni...@thykier.net [140415 07:21]: On 2014-04-14 22:25, Christian Hofstaedtler wrote: Dear Release Team, Please schedule this second round of binNMUs to remove ruby1.9.1 support: [...] ruby-gd_0.8.0-6 Not scheduled as it has an open FTBFS bug (#743982) Thanks, not sure how it ended up in my list. The following packages were blocked by a broken ruby-narray which has been fixed in the meantime; please schedule binNMU for those as well: ruby-fftw3_0.4-6 ruby-lapack_1.6-1 ruby-multibitnums_0.1.4-2 ruby-hdfeos5_1.2-1 ruby-netcdf_0.6.6-2 ruby-grib_0.2.2-3 ruby-mpi_0.2.0-1 Thank you, -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#743990: subtle: Depends on obsolete version of ruby
Control: severity -1 serious Upgrading severity for upcoming removal of ruby1.9.1 from testing. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgp6tWXENASan.pgp Description: PGP signature
Bug#744788: FTBFS: ERROR: Test ruby2.0 failed. Exiting
Source: ruby-mysql2 Version: 0.3.14-2 Severity: serious Justification: fails to build from source Dear Maintainer, your package ruby-mysql2 failed to build on all buildds, with this or a similar error message: Failures: 1) Mysql2::Client should raise an exception upon connection failure Failure/Error: Unable to find matching line from backtrace Mysql2::Error: Unknown database 'test' # ./lib/mysql2/client.rb:67:in `connect' # ./lib/mysql2/client.rb:67:in `initialize' /usr/bin/ruby2.0 -S rspec ./spec/mysql2/client_spec.rb ./spec/mysql2/error_spec.rb ./spec/mysql2/result_spec.rb failed ERROR: Test ruby2.0 failed. Exiting. dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-mysql2 returned exit code 1 Please check the logs here: https://buildd.debian.org/status/package.php?p=ruby-mysql2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739611: Second round of binNMUs for ruby1.9.1-rm
Dear Release Team, Please schedule this second round of binNMUs to remove ruby1.9.1 support: qdbm_1.8.78-3 stfl_0.22-1.1 xmms2_0.8+dfsg-9 ruby-hpricot_0.8.6-5 ruby-http-parser.rb_0.6.0-2 ruby-msgpack_0.5.5-2 ruby-password_0.5.3-4 thin_1.3.1-5 unicorn_4.7.0-1 ruby-gd_0.8.0-6 hivex_1.3.9-2 Thank you, -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#744804: FTBFS: ruby-mapscript missing files (usr/lib/ruby/vendor_ruby/*/*/mapscript.so)
Source: mapserver Version: 6.4.1-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, your package mapserver failed to build from source during a test rebuild of all ruby related packages, with this output: -- Installing: /«PKGBUILDDIR»/debian/tmp-ruby2.1/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/mapscript.so [...] debian/rules override_dh_install make[1]: Entering directory `/«PKGBUILDDIR»' dh_install --autodest --list-missing dh_install: ruby-mapscript missing files (usr/lib/ruby/vendor_ruby/*/*/mapscript.so), aborting make[1]: *** [override_dh_install] Error 2 make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 The full build log can be found at: http://aws-logs.debian.net/ftbfs-logs/ruby-14-4-14/logs/mapserver_6.4.1-2_unstable.log -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744805: FTBFS: ruby.h:1116:30: error: assignment of read-only member klass
Source: ruby-gsl Version: 1.15.3+dfsg-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, your package ruby-gsl failed to build from source during a test rebuild of all ruby related packages, with this output: gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -DHAVE_ROUND -DHAVE_TAMU_ANOVA_TAMU_ANOVA_H -I/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0 -D_FORTIFY_SOURCE=2 -fPIC -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -fPIC -Wall -I../include -I/usr/include -o linalg_complex.o -c linalg_complex.c In file included from /usr/include/ruby-2.1.0/ruby.h:33:0, from ../include/rb_gsl_array.h:34, from linalg_complex.c:14: linalg_complex.c: In function 'rb_gsl_linalg_complex_LU_decomp': /usr/include/ruby-2.1.0/ruby/ruby.h:1116:30: error: assignment of read-only member 'klass' #define RBASIC(obj) (R_CAST(RBasic)(obj)) ^ /usr/include/ruby-2.1.0/ruby/ruby.h:1115:30: note: in definition of macro 'R_CAST' #define R_CAST(st) (struct st*) ^ (...) The full build log can be found at: http://aws-logs.debian.net/ftbfs-logs/ruby-14-4-14/logs/ruby-gsl_1.15.3+dfsg-1_unstable.log -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744807: FTBFS: ERROR: Test ruby2.1 failed.
Source: ruby-gherkin Version: 2.12.2-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, your package ruby-gherkin failed to build from source during a test rebuild of all ruby related packages, with this output: Running tests for ruby2.1 using debian/ruby-tests.rake ... (...) 1) Gherkin::Formatter::PrettyFormatter should prettify scenario Failure/Error: output.should == expected_output ArgumentError: invalid byte sequence in US-ASCII # ./spec/gherkin/formatter/pretty_formatter_spec.rb:28:in `block in assert_pretty' # ./spec/gherkin/formatter/pretty_formatter_spec.rb:22:in `each' # ./spec/gherkin/formatter/pretty_formatter_spec.rb:22:in `assert_pretty' # ./spec/gherkin/formatter/pretty_formatter_spec.rb:125:in `block (2 levels) in module:Formatter' 2) Gherkin::Formatter::StepPrinter should replace 1 unicode arg Failure/Error: @io.string.should == (I hæve )[øæ]( cåkes) expected: (I h\u00E6ve )[\u00F8\u00E6]( c\u00E5kes) got: (I h\xC3\xA6ve )[\xC3\xB8\xC3\xA6]( c\xC3\xA5kes) (using ==) # ./spec/gherkin/formatter/step_printer_spec.rb:41:in `block (2 levels) in module:Formatter' (...) The full build log can be found at: http://aws-logs.debian.net/ftbfs-logs/ruby-14-4-14/logs/ruby-gherkin_2.12.2-2_unstable.log -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744808: FTBFS: make[1]: /usr/bin/ruby1.9.1: Command not found
Source: ruby-passenger Version: 4.0.37-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, your package ruby-passenger failed to build from source during a test rebuild of all ruby related packages, with this output: dh_auto_configure -O--buildsystem=ruby debian/rules override_dh_auto_build make[1]: Entering directory `/«PKGBUILDDIR»' /usr/bin/ruby1.9.1 /usr/bin/rake fakeroot make[1]: /usr/bin/ruby1.9.1: Command not found make[1]: *** [override_dh_auto_build] Error 127 make[1]: Leaving directory `/«PKGBUILDDIR»' Please note that ruby1.9.1 is about to be removed from jessie. The full build log can be found at: http://aws-logs.debian.net/ftbfs-logs/ruby-14-4-14/logs/ruby-passenger_4.0.37-2_unstable.log -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744809: FTBFS: writes to file outside package build dir
Source: ruby-gnome2 Version: 2.1.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, your package ruby-gnome2 failed to build from source during a test rebuild of all ruby related packages, with this output: + make install DESTDIR=/«PKGBUILDDIR»/debian/tmp sitelibdir=/usr/lib/ruby/vendor_ruby sitearchdir=/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0 make[2]: Leaving directory `/«PKGBUILDDIR»' make[2]: Entering directory `/«PKGBUILDDIR»' (cd 'glib2' make install) make[3]: Entering directory `/«PKGBUILDDIR»/glib2' (cd ext/glib2 make install) make[4]: Entering directory `/«PKGBUILDDIR»/glib2/ext/glib2' /usr/bin/install -c -m 644 /«PKGBUILDDIR»/glib2/ext/glib2/rbglib.h /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0 /usr/bin/install: cannot create regular file '/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/rbglib.h': Permission denied make[4]: *** [install-headers] Error 1 The full build log can be found at: http://aws-logs.debian.net/ftbfs-logs/ruby-14-4-14/logs/ruby-gnome2_2.1.0-1_unstable.log -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744812: ruby-pgplot: Depends on obsolete version of ruby
Source: ruby-pgplot Version: 0.1.3-8 Severity: serious Justification: obsolete dependency Dear Maintainer, Your package depends on ruby1.9.1, which is obsolete and is going to be removed from jessie very soon. Please update your package to use either the ruby metapackage, or if that is not an option, to depend on ruby2.1 (the soon new default ruby). Thanks, -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744813: FTBFS: Segmentation fault in ruby2.0
Package: ruby-patron Version: 0.4.18-2 Severity: serious Justification: fails to build from source Since the 0.4.18-2 upload, rspec crashes during build almost everywhere, except on my build machine and the powerpc buildd. -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744359: RM: ruby-rjb [kfreebsd-amd64 kfreebsd-i386] -- ANAIS; no longer built on ![amd64 i386]
Package: ftp.debian.org Severity: normal Dear ftpmasters, ruby-rjb is now limited to build only on amd64 i386; please remove the old binaries. Thanks, -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740744: closing 740744 - dns323-firmware-tools still depends on ruby1.9.1
Control: reopen -1 Control: notfixed -1 0.6-1 * Matt Palmer mpal...@debian.org [140412 13:03]: close 740744 0.6-1 close 743787 0.6-1 thanks 0.6-1 still Depends on ruby1.9.1, therefore I'm reopening this bug. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpuuv2MYaO3I.pgp Description: PGP signature
Bug#739611: #701349: ruby-ffi: fixed in 1.9.0debian-1
As previously marked, this has been fixed already. I've double checked that the current version builds fine on sid (with gcc 4.8). RT: please schedule the binNMU for ruby-ffi. Thanks, -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgps3HVGLTlbX.pgp Description: PGP signature
Bug#744016: Improve dh_ruby for language binding packages
Package: gem2deb Severity: wishlist Russ Allbery noticed that dh_ruby expects to be the top-level build system in dh7, which means that while it can be used for packages that use another primary buildsystem (i.e. autoconf), it's extra work (see #743991 for details). In particular: - dh_ruby doesn't run through dh_auto_install - XB-Ruby-Versions doesn't get added automatically Also it'd be nice to automatically hook dh_ruby in if there was a ruby/extconf.rb and similar files. (Wouldn't help for remctl, but still.) -ch -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpP9cLSQgvtC.pgp Description: PGP signature
Bug#744016: disregard XB-Ruby-Versions
Please disregard the comment about XB-Ruby-Versions for obvious reasons. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744033: FTBFS: E: ruby1.9.1 is not supported by gem2deb anymore
Package: vagrant Version: 1.4.3-1 Severity: serious Justification: fails to build from source Dear Maintainer, During a test rebuild of ruby-related packages your package failed to build from source, with this output: dh binary --buildsystem=ruby --with ruby --with bash_completion dh_testroot -O--buildsystem=ruby dh_prep -O--buildsystem=ruby dh_auto_install -O--buildsystem=ruby Entering dh_ruby --install E: ruby1.9.1 is not supported by gem2deb anymore dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/vagrant returned exit code 1 make: *** [binary] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 Full build log attached. Christian sbuild (Debian sbuild) 0.64.1 (13 Oct 2013) on nq.home.zeha.at ╔══╗ ║ vagrant 1.4.3-1 (amd64)09 Apr 2014 15:36 ║ ╚══╝ Package: vagrant Version: 1.4.3-1 Source Version: 1.4.3-1 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 I: 10mount: mount: warning: /var/lib/schroot/mount/unstable-amd64-sbuild-52e16edd-6178-4687-baef-48bc5e139eb4/apt seems to be mounted read-write. I: NOTICE: Log filtering will replace 'build/vagrant-lPNbcx/vagrant-1.4.3' with '«PKGBUILDDIR»' I: NOTICE: Log filtering will replace 'build/vagrant-lPNbcx' with '«BUILDDIR»' I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/unstable-amd64-sbuild-52e16edd-6178-4687-baef-48bc5e139eb4' with '«CHROOT»' ┌──┐ │ Update chroot│ └──┘ Get:1 http://ftp.at.debian.org sid InRelease [206 kB] Get:2 http://ftp.at.debian.org sid/main Sources [7108 kB] Get:3 http://ftp.at.debian.org sid/main amd64 Packages [6676 kB] Get:4 http://ftp.at.debian.org sid/main Translation-en [4549 kB] Fetched 18.5 MB in 5s (3195 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: startpar The following packages will be upgraded: bash cpp cpp-4.8 g++ g++-4.8 gcc gcc-4.8 gcc-4.8-base initscripts libasan0 libatomic1 libgcc-4.8-dev libgcc1 libgmp10 libgomp1 libitm1 libpam-modules libpam-modules-bin libpam-runtime libpam0g libpcre3 libquadmath0 libreadline6 libstdc++-4.8-dev libstdc++6 libtsan0 readline-common sysv-rc sysvinit sysvinit-core sysvinit-utils 31 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 23.8 MB of archives. After this operation, 302 kB of additional disk space will be used. Get:1 http://ftp.at.debian.org/debian/ sid/main bash amd64 4.3-6 [1166 kB] Get:2 http://ftp.at.debian.org/debian/ sid/main sysvinit amd64 2.88dsf-53 [82.2 kB] Get:3 http://ftp.at.debian.org/debian/ sid/main startpar amd64 0.58-5 [21.3 kB] Get:4 http://ftp.at.debian.org/debian/ sid/main sysvinit-utils amd64 2.88dsf-53 [82.3 kB] Get:5 http://ftp.at.debian.org/debian/ sid/main readline-common all 6.3-6 [57.1 kB] Get:6 http://ftp.at.debian.org/debian/ sid/main libreadline6 amd64 6.3-6 [142 kB] Get:7 http://ftp.at.debian.org/debian/ sid/main libitm1 amd64 4.8.2-19 [28.7 kB] Get:8 http://ftp.at.debian.org/debian/ sid/main libgomp1 amd64 4.8.2-19 [23.2 kB] Get:9 http://ftp.at.debian.org/debian/ sid/main gcc-4.8-base amd64 4.8.2-19 [153 kB] Get:10 http://ftp.at.debian.org/debian/ sid/main libstdc++6 amd64 4.8.2-19 [255 kB] Get:11 http://ftp.at.debian.org/debian/ sid/main libasan0 amd64 4.8.2-19 [63.1 kB] Get:12 http://ftp.at.debian.org/debian/ sid/main libatomic1 amd64 4.8.2-19 [8588 B] Get:13 http://ftp.at.debian.org/debian/ sid/main libtsan0 amd64 4.8.2-19 [94.7 kB] Get:14 http://ftp.at.debian.org/debian/ sid/main libquadmath0 amd64 4.8.2-19 [125 kB] Get:15 http://ftp.at.debian.org/debian/ sid/main cpp-4.8 amd64 4.8.2-19 [4577 kB] Get:16 http://ftp.at.debian.org/debian/ sid/main libstdc++-4.8-dev amd64 4.8.2-19 [1052 kB] Get:17 http://ftp.at.debian.org/debian/ sid/main g++-4.8 amd64 4.8.2-19 [7832 kB] Get:18 http://ftp.at.debian.org/debian/ sid/main gcc-4.8 amd64 4.8.2-19 [4767 kB] Get:19 http://ftp.at.debian.org/debian/ sid/main libgcc-4.8-dev amd64 4.8.2-19 [1689 kB] Get:20 http://ftp.at.debian.org/debian/ sid/main libgcc1 amd64 1:4.8.2-19 [37.8 kB] Get:21 http://ftp.at.debian.org/debian/ sid/main libgmp10 amd64 2:6.0.0+dfsg-2 [232 kB] Get:22 http://ftp.at.debian.org/debian/ sid/main libpam0g amd64 1.1.8-3 [126 kB] Get:23 http://ftp.at.debian.org/debian/ sid/main libpam-modules-bin amd64 1.1.8-3 [103 kB] Get:24 http://ftp.at.debian.org/debian/ sid/main libpam-modules amd64 1.1.8-3 [303 kB] Get:25 http://ftp.at.debian.org/debian/ sid/main libpcre3 amd64 1:8.31-3 [294 kB] Get:26
Bug#744035: imaprowl: Depends on obsolete version of Ruby (1.9)
Package: imaprowl Version: 1.2.1-1 Severity: serious Dear Maintainer, Your package imaprowl depends on an obsolete version of Ruby: 1.9. This version will not be available in jessie. Please update your package to use either the metapackage ruby, or if that is not an option, ruby2.1. Thanks, -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744036: FTBFS: E: ruby1.9.1 is not supported by gem2deb anymore
Package: adlint Version: 3.2.0-1 Severity: serious Justification: fails to build from source Dear Maintainer, During a test rebuild of ruby-related packages your package failed to build from source, with the following output (full build log attached). dh binary --buildsystem=ruby --with ruby dh_testroot -O--buildsystem=ruby dh_prep -O--buildsystem=ruby dh_auto_install -O--buildsystem=ruby Entering dh_ruby --install E: ruby1.9.1 is not supported by gem2deb anymore dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/adlint returned exit code 1 make: *** [binary] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 -ch sbuild (Debian sbuild) 0.64.1 (13 Oct 2013) on nq.home.zeha.at ╔══╗ ║ adlint 3.2.0-1 (amd64) 09 Apr 2014 15:37 ║ ╚══╝ Package: adlint Version: 3.2.0-1 Source Version: 3.2.0-1 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 I: 10mount: mount: warning: /var/lib/schroot/mount/unstable-amd64-sbuild-d12a1f7b-f527-4b89-ac3c-383040958fe5/apt seems to be mounted read-write. I: NOTICE: Log filtering will replace 'build/adlint-_CuJmo/adlint-3.2.0' with '«PKGBUILDDIR»' I: NOTICE: Log filtering will replace 'build/adlint-_CuJmo' with '«BUILDDIR»' I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/unstable-amd64-sbuild-d12a1f7b-f527-4b89-ac3c-383040958fe5' with '«CHROOT»' ┌──┐ │ Update chroot│ └──┘ Get:1 http://ftp.at.debian.org sid InRelease [206 kB] Get:2 http://ftp.at.debian.org sid/main Sources [7108 kB] Get:3 http://ftp.at.debian.org sid/main amd64 Packages [6676 kB] Get:4 http://ftp.at.debian.org sid/main Translation-en [4549 kB] Fetched 18.5 MB in 2s (8191 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: startpar The following packages will be upgraded: bash cpp cpp-4.8 g++ g++-4.8 gcc gcc-4.8 gcc-4.8-base initscripts libasan0 libatomic1 libgcc-4.8-dev libgcc1 libgmp10 libgomp1 libitm1 libpam-modules libpam-modules-bin libpam-runtime libpam0g libpcre3 libquadmath0 libreadline6 libstdc++-4.8-dev libstdc++6 libtsan0 readline-common sysv-rc sysvinit sysvinit-core sysvinit-utils 31 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 23.8 MB of archives. After this operation, 302 kB of additional disk space will be used. Get:1 http://ftp.at.debian.org/debian/ sid/main bash amd64 4.3-6 [1166 kB] Get:2 http://ftp.at.debian.org/debian/ sid/main sysvinit amd64 2.88dsf-53 [82.2 kB] Get:3 http://ftp.at.debian.org/debian/ sid/main startpar amd64 0.58-5 [21.3 kB] Get:4 http://ftp.at.debian.org/debian/ sid/main sysvinit-utils amd64 2.88dsf-53 [82.3 kB] Get:5 http://ftp.at.debian.org/debian/ sid/main readline-common all 6.3-6 [57.1 kB] Get:6 http://ftp.at.debian.org/debian/ sid/main libreadline6 amd64 6.3-6 [142 kB] Get:7 http://ftp.at.debian.org/debian/ sid/main libitm1 amd64 4.8.2-19 [28.7 kB] Get:8 http://ftp.at.debian.org/debian/ sid/main libgomp1 amd64 4.8.2-19 [23.2 kB] Get:9 http://ftp.at.debian.org/debian/ sid/main gcc-4.8-base amd64 4.8.2-19 [153 kB] Get:10 http://ftp.at.debian.org/debian/ sid/main libstdc++6 amd64 4.8.2-19 [255 kB] Get:11 http://ftp.at.debian.org/debian/ sid/main libasan0 amd64 4.8.2-19 [63.1 kB] Get:12 http://ftp.at.debian.org/debian/ sid/main libatomic1 amd64 4.8.2-19 [8588 B] Get:13 http://ftp.at.debian.org/debian/ sid/main libtsan0 amd64 4.8.2-19 [94.7 kB] Get:14 http://ftp.at.debian.org/debian/ sid/main libquadmath0 amd64 4.8.2-19 [125 kB] Get:15 http://ftp.at.debian.org/debian/ sid/main cpp-4.8 amd64 4.8.2-19 [4577 kB] Get:16 http://ftp.at.debian.org/debian/ sid/main libstdc++-4.8-dev amd64 4.8.2-19 [1052 kB] Get:17 http://ftp.at.debian.org/debian/ sid/main g++-4.8 amd64 4.8.2-19 [7832 kB] Get:18 http://ftp.at.debian.org/debian/ sid/main gcc-4.8 amd64 4.8.2-19 [4767 kB] Get:19 http://ftp.at.debian.org/debian/ sid/main libgcc-4.8-dev amd64 4.8.2-19 [1689 kB] Get:20 http://ftp.at.debian.org/debian/ sid/main libgcc1 amd64 1:4.8.2-19 [37.8 kB] Get:21 http://ftp.at.debian.org/debian/ sid/main libgmp10 amd64 2:6.0.0+dfsg-2 [232 kB] Get:22 http://ftp.at.debian.org/debian/ sid/main libpam0g amd64 1.1.8-3 [126 kB] Get:23 http://ftp.at.debian.org/debian/ sid/main libpam-modules-bin amd64 1.1.8-3 [103 kB] Get:24 http://ftp.at.debian.org/debian/ sid/main libpam-modules amd64 1.1.8-3 [303 kB] Get:25 http://ftp.at.debian.org/debian/ sid/main libpcre3 amd64 1:8.31-3 [294 kB] Get:26
Bug#740744: Raising severity so that 1.9.1 can be removed
Control: severity -1 serious Raising the severity as ruby-defaults has dropped it's dependency on ruby1.9.1, and we want to remove [from testing] ruby1.9.1 ASAP. As noted in #743787 dns323-firmware-tools no longer works because of a dependency/interpreter mismatch. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#744072: RM: libfilesystem-ruby/0.5-3.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Dear Release-Team, it appears src:libfilesystem-ruby is halfway stuck in testing: - it's binary libfilesystem-ruby1.8 is NOT in testing - source and binary libfilesystem-ruby1.9.1 are in testing - src:libfilesystem-ruby Build-Depends on ruby1.8 which is NOT in testing. - there's no indication of a pending autoremove triggered by #735654. I think it's safe to just entirely remove this package from testing, so I'd suggest doing exactly that. Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744036: fixed
Control: fixed -1 3.2.0-2 Fixed by an upload; now builds for all current Ruby versions. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744076: RM: libfilesystem-ruby -- RoQA; replaced by ruby-filesystem
Package: ftp.debian.org Severity: normal Dear ftpmasters, apparently libfilesystem-ruby got replaced by ruby-filesystem, but the old (source) package never got removed from unstable. Please remove libruby-filesystem from unstable. Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744081: FTBFS: minitest/unit.rb:28:in const_missing: uninitialized constant MiniTest::Test (NameError)
Source: ruby-escape-utils Version: 1.0.1-1 Severity: serious Justification: fails to build from source Dear Maintainer, your package is failing to build on the buildds: /bin/mkdir -p . ./.gem.20140409-24791-u8yi50/escape_utils exit .RUBYARCHDIR.-.escape_utils.time /usr/bin/install -c -m 0755 escape_utils.so ./.gem.20140409-24791-u8yi50/escape_utils make[1]: Leaving directory `/«PKGBUILDDIR»/ext/escape_utils' Running tests for ruby2.0 using debian/ruby-tests.rb... /usr/lib/ruby/2.0.0/minitest/unit.rb:28:in `const_missing': uninitialized constant MiniTest::Test (NameError) from /«PKGBUILDDIR»/test/html_safety_test.rb:29:in `top (required)' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from debian/ruby-tests.rb:1:in `block in main' from debian/ruby-tests.rb:1:in `each' from debian/ruby-tests.rb:1:in `main' ERROR: Test ruby2.0 failed. Exiting. dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-escape-utils returned exit code 1 make: *** [binary-arch] Error 1 This happened on all archs that managed to attempt a build so far, see: https://buildd.debian.org/status/package.php?p=ruby-escape-utils -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722084: obsolete ruby1.9.1
Chiming in on this, we've started removing ruby1.9.1. Please add it to the list of obsolete packages. More info can be found in the release bug #739611. Thanks, -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpPBR9uYWcSD.pgp Description: PGP signature
Bug#743729: way out
* Antonio Terceiro terce...@debian.org [140408 03:57]:
I admit that hacking /var/lib/dpkg/info/ruby{1.8,1.9.1}.postinst from
ruby.postinst is not very pretty, but the situation as a whole is
already not pretty. ;-)
Not sure what to say. If this works and doesn't violate policy...
upload it!
--
,''`. Christian Hofstaedtler z...@debian.org
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
pgp6HnLlnj_PV.pgp
Description: PGP signature
Bug#743980: FTBFS: DataObjects::Mysql::Connection it should behave like a Connection with authentication support ...
Package: ruby-dataobjects-mysql
Version: 0.10.13-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
In a test rebuild your package failed to build from source, with this output:
Failures:
1) DataObjects::Mysql::Connection it should behave like a Connection with
authentication support with an invalid URI should raise an error with a
meaningless URI
Failure/Error: connecting_with(#{@driver}://peekaboo$2!@#4543).should
raise_error(Addressable::URI::InvalidURIError)
expected Addressable::URI::InvalidURIError, got
#DataObjects::ConnectionError: Access denied for user
'peekaboo$2!'@'localhost' (using password: NO) (code: 1045, sql state: 28000,
query: , uri: ) with backtrace:
# /usr/lib/ruby/vendor_ruby/data_objects/connection.rb:79:in
`initialize'
# /usr/lib/ruby/vendor_ruby/data_objects/connection.rb:79:in `new'
# /usr/lib/ruby/vendor_ruby/data_objects/pooling.rb:181:in `block in
new'
# /usr/lib/ruby/vendor_ruby/data_objects/pooling.rb:176:in
`synchronize'
# /usr/lib/ruby/vendor_ruby/data_objects/pooling.rb:176:in `new'
# /usr/lib/ruby/vendor_ruby/data_objects/pooling.rb:121:in `new'
# /usr/lib/ruby/vendor_ruby/data_objects/connection.rb:68:in `new'
#
/usr/lib/ruby/vendor_ruby/data_objects/spec/shared/connection_spec.rb:113:in
`block in connecting_with'
#
/usr/lib/ruby/vendor_ruby/rspec/matchers/built_in/raise_error.rb:36:in `call'
#
/usr/lib/ruby/vendor_ruby/rspec/matchers/built_in/raise_error.rb:36:in
`matches?'
# /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:24:in
`handle_matcher'
# /usr/lib/ruby/vendor_ruby/rspec/expectations/syntax.rb:53:in `should'
#
/usr/lib/ruby/vendor_ruby/data_objects/spec/shared/connection_spec.rb:133:in
`block (3 levels) in top (required)'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:114:in
`instance_eval'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:114:in `block in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in
`with_around_each_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:111:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:390:in `block
in run_examples'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:386:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:386:in
`run_examples'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:371:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:372:in `block
in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:372:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:372:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:372:in `block
in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:372:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:372:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:28:in `block (2
levels) in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:28:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:28:in `block in
run'
# /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:58:in `report'
# /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:25:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:80:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:17:in `block in
autorun'
Shared Example Group: a Connection with authentication support called
from ./spec/connection_spec.rb:20
Finished in 0.39874 seconds
77 examples, 1 failure, 1 pending
Failed examples:
rspec /usr/lib/ruby/vendor_ruby/data_objects/spec/shared/connection_spec.rb:132
# DataObjects::Mysql::Connection it should behave like a Connection with
authentication support with an invalid URI should raise an error with a
meaningless URI
/usr/bin/ruby2.0 -S rspec ./spec/command_spec.rb ./spec/connection_spec.rb
./spec/encoding_spec.rb ./spec/reader_spec.rb ./spec/result_spec.rb failed
ERROR: Test ruby2.0 failed. Exiting.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743987: FTBFS: ERROR: Test ruby2.1 failed. Exiting.
Package: ruby-opengl Version: 0.60.1+dfsg2-2 Severity: serious Justification: fails to build from source Dear Maintainer, During a test rebuild your package failed to build in unstable with this output: # Running tests: freeglut (debian/ruby-tests.rb): failed to open display '' ..WARNING: Test ruby2.0 failed, but ignoring this test result. Running tests for ruby2.1 using debian/ruby-tests.rb... test/unit warning: method Test_10_11#test_glclear is redefined test/unit warning: method Test_EXT_NV#test_gl_nv_gpu_program4 is redefined Run options: # Running tests: freeglut (debian/ruby-tests.rb): failed to open display '' ..ERROR: Test ruby2.1 failed. Exiting. dh_auto_install: dh_ruby --install /«BUILDDIR»/ruby-opengl-0.60.1+dfsg2/debian/ruby-opengl returned exit code 1 make: *** [binary] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739611: ruby1.9.1-rm transition: binNMU request
Dear Release Team, We've determined a new set of packages that need to be rebuilt and that also can be rebuilt now. Please binNMU the packages below. (This list has been filtered for a few FTBFS issues, except for mysql packages which likely FTBFS due to an issue in the test environment.) rrdtool ohcount raspell ruby-augeas ruby-blockenspiel ruby-bluecloth ruby-cairo ruby-charlock-holmes ruby-dataobjects-mysql ruby-dataobjects-sqlite3 ruby-debian ruby-dep-selector ruby-eb ruby-exif ruby-fast-stemmer ruby-fast-xs ruby-fcgi ruby-ferret ruby-ffi ruby-fusefs ruby-globalhotkeys ruby-god ruby-gpgme ruby-inotify ruby-kyotocabinet ruby-ldap ruby-levenshtein ruby-libxml ruby-mecab ruby-multimap ruby-mysql ruby-mysql2 ruby-ncurses ruby-odbc ruby-oily-png ruby-oj ruby-pcaprub ruby-pg ruby-posix-spawn ruby-rdiscount ruby-redcloth ruby-rinku ruby-rmagick ruby-rpatricia ruby-sdl ruby-sequel-pg ruby-serialport ruby-shadow ruby-taglib2 ruby-termios ruby-tioga ruby-tokyocabinet ruby-uconv ruby-unf-ext ruby-unicode ruby-xmlparser ruby-zoom -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpmvbpmQxDhb.pgp Description: PGP signature
Bug#743989: ruby-marisa: Please support building with Ruby 2.0/2.1
Source: ruby-marisa Version: 0.2.4-5 Severity: serious Dear Maintainer, When building ruby-marisa with Ruby 2.0, it ends up installing files into either /build/... or /usr/local/, both of which are violations of policy. Please update your package so that it can be built with the current Ruby interpreter versions (2.0 and 2.1). For your convenience, the package ruby-all-dev depends on all current interpreter versions. Thanks, -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743990: subtle: Depends on obsolete version of ruby
Package: subtle Version: 0.11.3224-xi-1 Severity: important Dear Maintainer, Your package depends on ruby1.9.1, which is an obsolete version of Ruby. The 1.9 series will not be available in jessie. Please update your package so that it depends on ruby or ruby2.1 instead. It is preferable to depend on the ruby metapackage, but if this doesn't work for your package, please depend on ruby2.1, which will become the default interpreter soon. Thanks, -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743991: FTBFS: Failed 3/1877 tests, 99.84% okay, 42 tests skipped.
Package: remctl Version: 3.8-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, During a test rebuild your package failed to build. The test rebuild was done using sbuild, in unstable. The build produced this output: util/network/client.FAILED 21-22 util/network/server.ok util/tokens.FAILED 10 util/vector.ok util/xmallocskipped (xmalloc tests only run for maintainer) util/xwrite.ok Failed Set Fail/Total (%) Skip Stat Failing Tests -- -- util/network/client 2/22 9%00 21-22 util/tokens 1/12 8%00 10 Failed 3/1877 tests, 99.84% okay, 42 tests skipped. Files=50, Tests=1877, 13.00 seconds (0.32 usr + 0.02 sys = 0.34 CPU) make[3]: *** [check-local] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/«PKGBUILDDIR»' dh_auto_test: make -j12 check REMCTL_RUBY=ruby1.9.1 returned exit code 2 I notice that this also uses an obsolete version of Ruby (1.9). Please update your package to use either the meta package (ruby) or ruby2.1. Thanks, -ch -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743992: zeroc-ice: Depends on obsolete version of Ruby (1.9)
Package: zeroc-ice Version: 3.5.1-5.2 Severity: serious Dear Maintainer, Your package depends on an obsolete version of Ruby (1.9). This version will not be available in jessie. Please update your package to use either the metapackage ruby (there is a matching ruby-dev and ruby-all-dev package), or, if that is not an option, to use ruby2.1. Thanks, -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743994: uwsgi: (Build-)Depends on obsolete version of Ruby (1.9)
Source: uwsgi Version: 1.9.17.1-5 Severity: serious Dear Maintainer, Your package Build-Depends and Depends on an obsolete version of Ruby, ruby1.9.1. This version will not be available in jessie. Please update your package to use the ruby/ruby-dev/ruby-all-dev meta- packages, or if this is not an option, the ruby2.1 package. Thanks, -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743991: FTBFS: Failed 3/1877 tests, 99.84% okay, 42 tests skipped.
* Russ Allbery r...@debian.org [140409 02:46]: Christian Hofstaedtler z...@debian.org writes: During a test rebuild your package failed to build. The test rebuild was done using sbuild, in unstable. The build produced this output: util/network/client.FAILED 21-22 util/network/server.ok util/tokens.FAILED 10 util/vector.ok util/xmallocskipped (xmalloc tests only run for maintainer) util/xwrite.ok Hm. Those are timing-sensitive tests that can fail on extremely slow systems, but I did have them tweaked so that they pass on all of Debian's buildds. Actually this should be quite a fast system. I notice that this also uses an obsolete version of Ruby (1.9). Please update your package to use either the meta package (ruby) or ruby2.1. Yeah, I was getting ready to make that change. (There's no way for this package to use the metapackage.) It currently builds against 1.9 and 2.0; I'll change that to build against 2.0 and 2.1 and upload without any changes to the tests and see if the buildds are still happy. If so, I think the FTBFS is spurious. Note that there's also a ruby-all-dev metapackage. Maybe you can make use of it... Thanks for the report! Thanks for your fast reply! -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#743991: FTBFS: Failed 3/1877 tests, 99.84% okay, 42 tests skipped.
* Russ Allbery r...@debian.org [140409 02:55]:
Christian Hofstaedtler z...@debian.org writes:
Note that there's also a ruby-all-dev metapackage. Maybe you can
make use of it...
Unfortunately, Ruby's mkmf system doesn't, so far as I can tell, have any
way of building for all installed versions, so I need to know what
versions to build for so that I can iterate through the Ruby interpreters.
If there are tools available to do this for a build system that uses mkmf
directly, I'd be happy to switch over. (But I don't mind doing uploads
for new Ruby versions; it's not hard, and I should be able to generally do
so quickly.)
I've attached a patch that uses dh_ruby to build the Ruby
extensions; I haven't done any further checking other than it
builds.
Note that this still builds with `--enable-ruby` to get `extconf.rb` in
ruby/, and then `make install` ends up installing an additional copy
of the .so into a weird path in debian/tmp. (dh_ruby takes care of
installing into the correct paths in debian/ruby-remctl.)
-ch
--
,''`. Christian Hofstaedtler z...@debian.org
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
diff -Nru remctl-3.8/debian/control remctl-3.8/debian/control
--- remctl-3.8/debian/control 2014-01-29 04:50:23.0 +0100
+++ remctl-3.8/debian/control 2014-04-09 03:07:24.0 +0200
@@ -20,11 +20,9 @@
php5-dev,
pkg-config,
python-all-dev,
- ruby1.9.1,
- ruby1.9.1-dev,
- ruby2.0,
- ruby2.0-dev
+ gem2deb
XS-Python-Version: = 2.6
+XS-Ruby-Versions: all
Standards-Version: 3.9.5
Homepage: http://www.eyrie.org/~eagle/software/remctl/
Vcs-Git: git://git.eyrie.org/kerberos/remctl.git -b debian
@@ -146,6 +144,7 @@
Section: ruby
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, ruby | ruby-interpreter
+X-DhRuby-Root: ruby
Description: Ruby extension for Kerberos-authenticated command execution
remctl is a client/server protocol for executing specific commands on a
remote system with Kerberos authentication. The allowable commands must
diff -Nru remctl-3.8/debian/ruby-remctl.install remctl-3.8/debian/ruby-remctl.install
--- remctl-3.8/debian/ruby-remctl.install 2014-01-29 04:50:23.0 +0100
+++ remctl-3.8/debian/ruby-remctl.install 1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-usr/lib/ruby/vendor_ruby
-usr/lib/*/ruby/vendor_ruby
diff -Nru remctl-3.8/debian/rules remctl-3.8/debian/rules
--- remctl-3.8/debian/rules 2014-01-29 04:50:23.0 +0100
+++ remctl-3.8/debian/rules 2014-04-09 03:07:59.0 +0200
@@ -18,7 +18,7 @@
export REMCTL_PYTHON_VERSIONS := $(shell pyversions -s)
%:
- dh $@ --parallel --with python2,autoreconf
+ dh $@ --parallel --with python2,autoreconf,ruby
override_dh_autoreconf:
dh_autoreconf --as-needed
@@ -29,23 +29,6 @@
--enable-reduced-depends --enable-perl --enable-php \
--enable-python --enable-ruby
-# For the first pass, build the Ruby 1.9.1 extension. We'll go back and
-# build the extension for 2.0.
-override_dh_auto_build:
- dh_auto_build --parallel -- REMCTL_RUBY=ruby1.9.1
-
-override_dh_auto_test:
- dh_auto_test --parallel -- REMCTL_RUBY=ruby1.9.1
-
-# After installing the build for the default version of Ruby, go back and
-# rebuild for the newer version.
-override_dh_auto_install:
- dh_auto_install -- RUBYARCHDIR='$$(vendorarchdir)$$(target_prefix)'
- cd ruby $(MAKE) distclean
- dh_auto_build --parallel -- REMCTL_RUBY=ruby2.0
- cd ruby $(MAKE) install DESTDIR='$(CURDIR)/debian/tmp' \
- RUBYARCHDIR='$$(DESTDIR)$$(vendorarchdir)$$(target_prefix)'
-
# Override install to check for missing installed files.
override_dh_install:
dh_install --fail-missing -Xlibremctl.la
signature.asc
Description: Digital signature
Bug#739611: ruby1.9.1-rm transition: binNMU request
Dear Release-Team, In addition to my previous list, please binNMU the following packages to remove the (lib)ruby1.9.1 dependencies: vim notmuch hyperestraier -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#743729: way out
* Christian Hofstaedtler z...@debian.org [140406 23:33]: I /think/ we should add this to all interpreter preinsts: update-alternatives --remove-all ruby On second thought, there are probably some corner cases; for one this needs to be done in src:ruby-defaults, and we must ensure that 1.8 never gets configured again after the preinst runs. I don't see how to guarantee that whatever workaround we come up with won't break in a random way. I'd be much more comfortable with readding the Conflicts on ruby1.8. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgp57FcGlPAz2.pgp Description: PGP signature
Bug#743729: way out
I /think/ we should add this to all interpreter preinsts: update-alternatives --remove-all ruby -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpkwHw8bqs9E.pgp Description: PGP signature
Bug#743787: dns323-firmware-tools: breaks armel d-i builds since ruby-defaults 1:2.0.0.1 hit unstable
* Cyril Brulebois k...@debian.org [140406 15:51]:
[ shuffling your message a bit ]
since this upload[1],
1. http://packages.qa.debian.org/r/ruby-defaults/news/20140330T152352Z.html
dns323-firmware-tools depends on ruby1.9.1 but then just uses
/usr/bin/ruby in the shebang, rendering the dependency on a specific
interpreter version useless and wrong.
we're getting a failure when building the armel
orion5x_network-console flavour:
| mkdns323fw -k ./tmp/orion5x_network-console/dns-323/kernel.uboot -i
./tmp/orion5x_network-console/dns-323/initrd.uboot -p 7 -c 1 -m 1 -o
./dest/orion5x/network-console/d-link/dns-323/netboot.img
| /usr/bin/mkdns323fw:73: invalid multibyte escape:
/^\x55\xAA(.{7})\0\x55\xAA$/
| make[2]: *** [dns-323] Error 1
I haven't tried with actual files, but it looks like this change
might work on 1.9 and 2.0:
--- mkdns323fw~ 2014-04-07 00:07:27.560331402 +0200
+++ mkdns323fw 2014-04-07 00:08:39.796220588 +0200
@@ -70,7 +70,7 @@
# Return the signature of this firmware file.
def signature
- if @signature =~ /^\x55\xAA(.{7})\0\x55\xAA$/
+ if @signature =~
Regexp.new(^\x55\xAA(.{7})\x55\xAA$.force_encoding(binary),
Regexp::FIXEDENCODING)
return $1
else
raise RuntimeError.new(Unparseable signature string:
#{@signature.inspect})
-ch
--
,''`. Christian Hofstaedtler z...@debian.org
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
pgpcEKmJ8R0og.pgp
Description: PGP signature
Bug#743826: nmu: packages affected by gem2deb #743671
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Please schedule binNMUs for these packages, their current binaries ship conflicting files because of a bug in the build tool gem2deb (see #743671 for details). nmu ruby-atomic_1.1.16-1 . ALL . -m 'Rebuild to remove mkmf.log' nmu ruby-bcrypt_3.1.7-2 . ALL . -m 'Rebuild to remove mkmf.log' nmu ruby-bson-ext_1.10.0-1 . ALL . -m 'Rebuild to remove mkmf.log' nmu ruby-curb_0.8.5-2 . ALL . -m 'Rebuild to remove mkmf.log' nmu ruby-eventmachine_1.0.3-5 . ALL . -m 'Rebuild to remove mkmf.log' nmu ruby-hiredis_0.5.1-1 . ALL . -m 'Rebuild to remove mkmf.log' nmu ruby-hitimes_1.2.1-2 . ALL . -m 'Rebuild to remove mkmf.log' nmu ruby-nokogiri_1.6.1+ds-2 . ALL . -m 'Rebuild to remove mkmf.log' Thank you, -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#743425: autopkgtest: adt-build-lxc broken
Package: autopkgtest Version: 2.13 Severity: important Dear Maintainer, adt-build-lxc apparently assumes various stuff that's not present with the current versions of dependencies on sid: Snip # adt-build-lxc debian jessie /usr/bin/adt-build-lxc: 1: /usr/bin/adt-build-lxc: lxc-config: not found /usr/bin/adt-build-lxc: 1: /usr/bin/adt-build-lxc: lxc-config: not found lxc-create: No config file specified, using the default config /etc/lxc/default.conf getopt: invalid option -- 'r' lxc-debian -h|--help -p|--path=path --clean lxc-create: failed to execute template 'debian' lxc-create: aborted Snip I don't really know what to do about this, so adt-build-lxc is unusable for me. Thank you, Christian -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages autopkgtest depends on: ii apt-utils 0.9.16.1 ii debhelper 9.20140228 ii pbuilder 0.215 ii python 2.7.5-5 ii python-debian 0.1.21+nmu2 autopkgtest recommends no packages. Versions of packages autopkgtest suggests: pn autopkgtest-xenlvm none ii lxc 0.9.0~alpha3-2+deb8u1 ii qemu-system 1.7.0+dfsg-5 ii qemu-utils 1.7.0+dfsg-5 ii schroot 1.6.8-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743427: autopkgtest: Error message mentions not existing option --build-tree
Package: autopkgtest Version: 2.13 Severity: normal Dear Maintainer, Running `adt-run . --- schroot` gives a confusing error message: adt-run: error: do not know how to handle filename `.'; specify --source, --binary, --build-tree, or --apt-source Rerunning as `adt-run --build-tree . --- schroot` yields the same message. I suspect this should have been `built-tree` instead? Thanks, Christian -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages autopkgtest depends on: ii apt-utils 0.9.16.1 ii debhelper 9.20140228 ii pbuilder 0.215 ii python 2.7.5-5 ii python-debian 0.1.21+nmu2 autopkgtest recommends no packages. Versions of packages autopkgtest suggests: pn autopkgtest-xenlvm none ii lxc 0.9.0~alpha3-2+deb8u1 ii qemu-system 1.7.0+dfsg-5 ii qemu-utils 1.7.0+dfsg-5 ii schroot 1.6.8-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743210: libruby2.0: circular dependency on ruby2.0
Thank you for your bug report. * Eric Cooper e...@cooper-siegel.org [140331 16:12]: I only have libruby2.0 installed because I use the weechat-plugins package. On my most recent apt-get upgrade, upgrading to the latest libruby2.0 would have pulled in all of these: libruby1.9.1 ruby ruby1.9.1 ruby2.0 rubygems-integration I'm not familiar with ruby packaging, so maybe it's really necessary, but it seems excessive. Part of this (1.9) is an interim situation; as of today in sid, this would only pull in those packages: ruby ruby2.0 rubygems-integration Where ruby is a meta-package (almost no installed size), ruby2.0 has only the interpreter binaries (which are very small as they mostly just load libruby), and rubygems-integration is a code configuration package (very small as well). -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgp1W3GxSA4Ij.pgp Description: PGP signature
Bug#740733: closed by Antonio Terceiro terce...@debian.org (Bug#740733: fixed in ruby-defaults 1:2.0.0.1~exp3)
Hi, * Axel Beckert a...@debian.org [140331 01:36]: Hi, * ruby: remove Breaks/Conflicts/Replaces against old interpreter packages as this will force the removal of old interpreters from users' systems (Closes: #740733) . The following upgrade scenarios from wheezy were tested, still work fine, and leave the old interpreters alone: - ruby - ruby + ruby1.8 - ruby + apt-listbugs - ruby + ruby1.8 + apt-listbugs - ruby1.8 + apt-listbugs I've just run into a scenario not listed above in which left me without /usr/bin/ruby afterwards. This scenario is likely not happening during an dist-upgrade from Wheezy to Jessie as it's planned now, but may still hit other people who are running unstable. After I've read this changelog entry, I installed glark (which is currently ruby1.8 only) again to notice when there's an updated version working with a newer release of Ruby. [..] I noticed that /usr/bin/ruby points back to ruby1.8: update-alternatives: using /usr/bin/ruby1.8 to provide /usr/bin/ruby (ruby) in auto mode I'm not sure if this is a bug in update-alternatives as it seems to happily overwrite a file which was installed by a package -- I would expect that it should prevent that. One could argue that this is a bug in u-a, but u-a itself does not violate policy; certainly (now that ruby1.9.1, 2.0 have stopped being part of the scheme), ruby1.8 violates policy. At least I think, it's worthwile to consider Marga's idea of uploading ruby1.8 once more to remove that call to update-alternatives to prevent this kind of issue. This really only helps users of unstable, and likely is quite some work (IIRC 1.8 now FTBFS). Another option I can imagine is to keep the update-alternatives mechanism for one more release but with just one alternative. ... or make update-alternatives not to overwrite package-installed files. That's dpkg-divert's job. Keeping update-alternatives breaks when a user has previously manually chosen ruby1.8. I don't see a way out of this other than 1) cyclic dependencies 2) uploading an empty ruby1.8 package. Both of these options prevent users from keeping a working 1.8 interpreter, but because of update-alternatives in 1.8 this goal directly conflicts with any way of making any new version the new blessed default. I'm neither sure where to actually file a bug report for that issue nor which severity it should have (I can imagine everything, from minor to grave -- as it deletes a file installed by another package). Any advice or comment is appreciated. Cloning this bug with severity minor saying 'please allow keeping ruby1.8 installed [for stable users]' is probably welcome, but at this point I do not see how it's possible to do this. Thanks for the feedback, -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#738387: Not applicable at this time
Control: severity -1 normal Downgrading because this was caused by a premature upload of ruby-tilt, which has been reverted in the meantime. Thanks, -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739123: Please support building with Ruby 2.0
Dear Maintainer, The default ruby in unstable has now been changed to be 2.0. I expect that your package now FTBFS, therefore I'm raising the severity of this bug. (The bug was filed because your package FTBFS in a test rebuild earlier.) Some more info about the version change can be found in this email: http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2014-March/018856.html Thank you, -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#730095: ruby2.0: RbConfig::CONFIG['libdir'] does not point to the multiarch dir
Lisandro, Thanks for writing the patch. Cédric, Thanks for trying it and working on it further! Regarding ruby 1.9.1: I think it's safe to ignore 1.9.1; from what I've seen, packages that use cmake to build ruby extensions generally build only for one version, so if 1.9.1 would be broken with a patched cmake, that would only be a temporary situation that can be quickly remedied. Thanks! Christian -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#742407: rails-4.0: Provide README.source
Source: rails-4.0 Version: 4.0.2+dfsg-2 Severity: normal Dear Maintainer, please provide a README.source which demonstrates how to package a new upstream version. Neither uscan nor uscan + debian/dfsg-repack.sh yield a useful new orig.tar.gz. Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722390: 1.8 part is fixed
Control: severity -1 wishlist Control: retitle -1 Updating the Ruby packaging policy for your package «libobexftp-ruby» Control: unblock 731866 -1 Apparently libobexftp-ruby dropped it's dependency on ruby1.8 sometime. The package name and policy changes still apply. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#742107: RM: libneedle-extras-ruby -- RoQA; broken; dead upstream
Package: ftp.debian.org Severity: normal Dear ftpmasters, libneedle-extras-ruby is dead upstream (together with it's parent project needle), last update was sometime in 2005. To get it to work again on current versions of Ruby the package would need a serious makeover packaging- and possibly code-wise. When fixing packaging, the source package should be renamed to follow the current ruby extras policy. Please remove it, as reintroducing it through NEW is likely needed anyway, if somebody really is interested. Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742108: RM: libneedle-ruby -- RoQA; broken; dead upstream
Package: ftp.debian.org Severity: normal Dear ftpmasters, libneedle-ruby is dead upstream, last update was sometime in 2005. To get it to work again on current versions of Ruby the package would need a serious makeover packaging- and possibly code-wise. When fixing packaging, the source package should be renamed to follow the current ruby extras policy. Please remove it, as reintroducing it through NEW is likely needed anyway, if somebody really is interested. Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742114: dependency on tcl not tight enough
* Erwan David er...@rail.eu.org [140319 11:30]: /usr/share/tcltk/tcl8.5/init.tcl: version conflict for package Tcl: have 8.5.14, need exactly 8.5.15 version conflict for package Tcl: have 8.5.14, need exactly 8.5.15 while executing package require -exact Tcl 8.5.15 (file /usr/share/tcltk/tcl8.5/init.tcl line 19) This file is shipped by tcl, not by ruby. This looks suspiciously, and I doubt this is a dependency or ruby problem. Please verify that this command works on your system: tclsh8.5 /usr/share/tcltk/tcl8.5/init.tcl Thanks, Christian -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#741941: munin-node: processes plugin should run privileged for /proc with hidepid
Source: munin-node Version: 2.1.5-1 Severity: wishlist Dear Maintainer, Thank you for maintaining munin in Debian. As the security team has announced, they want to see /proc mounted with the hidepid option for jessie. [1] It would seem that (*) - to have no regression -, the processes plugin would then need to run as root so it can correctly count the number of running processes. I believe this can be achieved by adding this section to /etc/munin/plugin-conf.d/munin-node: [processes] user root Not sure if this is actually a good solution. Thanks, Christian [1] https://lists.debian.org/debian-devel-announce/2014/03/msg4.html * haven't verified this on jessie with hidepid=1, but only on stable with hidepid=2. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741331: unreproducible
Hi, Quoting very selectively here: [Original report] Fails to find rspec: Could not find rspec (= 2.0.0) amongst [] [unreproducible] I'm unable to reproduce the problem. ii ruby 1:1.9.3 ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-1 ii ruby 1:1.9.3.4 ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-2 It's very likely that ruby-rspec-puppet is missing a dependency on rubygems-integration here (or it should drop it's code dependency on loading gems). The versions of ruby and ruby1.9.1 suggest that in the unreproducible case ruby2.0 is installed too, which brings in rubygems-integration - causing the gem to be found. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#741458: RM: ruby1.8/1.8.7.358-10
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Dear Release Team, Ruby 1.8 is an old version of the Ruby interpreter. It is no longer security-supported upstream. #731866 has been opened by the security team to track removal of 1.8. We, the current interpreter maintainers, believe it's time for 1.8 to finally be removed from testing. There are two minor r-deps that need to go with it: dak rm -nR -s testing ruby1.8 ruby-bdb libfilesystem-ruby [...] Checking reverse dependencies... No dependency problem found. Thank you! Christian -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741459: release.debian.org: ignore SSL bug in ruby1.9.1 and ruby2.0
Package: release.debian.org Severity: normal Dear Release Team, #736287 and #736289 are about the same bug, broken upstrea default settings for SSL connections in Ruby; this bug is present in ruby1.9.1, ruby2.0 and ruby2.1. We agree that this is a real bug, but it's not a regression. The Ruby team intends to transition to ruby2.1 for jessie, incl. removal of ruby1.9.1 and ruby2.0 before the freeze. As such we hope that upstream comes up with a fix for 2.1, otherwise I promise to come up with a patch; but in any case I see little value in fixing the bug in all three packages when we want to kill two of them sooner than later. Also, there have been changes in dependencies, which right now means (I think) that src:ruby-defaults, ruby1.9.1 and ruby2.0 have to migrate to testing in one batch. Therefore I'd like to request a jessie-ignore tag for the above mentioned bugs. Thank you, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741050: RM: ruby-switch -- ROM; obsolete
Package: ftp.debian.org Severity: normal Dear ftpmasters, ruby-switch has been obsoleted by src:ruby-defaults = 1:1.9.3.1, which no longer allows switching the system default interpreter. Additional discussion is available in bug #737782. With my Debian Ruby Extras Maintainer hat on, I therefore request removal of ruby-switch from unstable. Thank you, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740564: apt-listbugs: auxiliary script send-hook-info.rb fails to work with Ruby 2.0
Hi, * Francesco Poli invernom...@paranoici.org [140305 22:52]: Hello Debian Ruby regulars, could some of you please take a look at bug #740564, hoping it is not too much bother? Does anyone have any idea of what's wrong? [...] However, I failed to understand how I could fix the script: I tried with the following modification --- apt-listbugs/examples/send-hook-info.rb 2014-02-23 16:31:54.0 +0100 +++ TEST_send-hook-info.rb 2014-03-03 23:17:29.0 +0100 @@ -52,7 +52,7 @@ if Process.fork().nil? # the child write_fd.close - exec command + exec(command, :close_others=false) read_fd.close exit 0 else but it does not seem to change anything in the tests described in bug #740564... Having looked at ruby/process.c and ruby/io.c in 1.9.3 and 2.0, I'd say the 2.0 behaviour is what always was intended, but it's very poorly documented. I believe (haven't verified) that you need to explicitly list the FDs that you want to pass on to the child in the exec options (see Process#spawn redirection); it appears :close_others changed meaning a bit to any non-standard FD that's not in the redirection list (from any non-standard FD if enabled) and setting it to false no longer does anything. P.S.: please keep the bug address in Cc:, thanks! -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#740744: dns323-firmware-tools: Please migrate to Ruby 2.0/2.1
* Matt Palmer mpal...@debian.org [140304 22:54]: On Tue, Mar 04, 2014 at 05:02:31PM +0100, Christian Hofstaedtler wrote: As per the Debian Ruby team bits, all versions of Ruby 2.1 will be removed from jessie. A month ago you told me to migrate to Ruby 1.9, now you're saying that isn't enough. Can you make up your mind, please? The purpose of the previous bug was to have everybody migrate away from 1.8, because it was clear that jessie won't ship with 1.8. IIRC, at that point in time, no other decision had been made, and we didn't even have 2.1 in sid. Please test your package with Ruby 2.0 and 2.1, and then switch the Why do I need to test against 2.0 if you're removing everything earlier than 2.1? Feel free to skip 2.0 if you want and can. Depends: line to read ruby instead of ruby1.9.1. Is that going to break when you upgrade the ruby package to pull in Ruby 2.2, and my code isn't 2.2 compatible? Or has Ruby upstream finally decided that backwards-compatibility is a worthy goal? The current plan is to have the ruby meta-package depend on the one and only shipping Ruby version for a given Debian release. If you decide on staying with a Depends: on a specific ruby version you'll need to update your package even if it would work without any other changes. Regarding backwards-compatibility this is not something I can answer; I'm not Ruby upstream. If you have issues with Ruby upstream, please talk to them. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
