-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 2014-01-07 13:45, Antonio Terceiro wrote: > Hello, > > On Mon, Dec 30, 2013 at 01:52:13AM +0100, Felix C. Stegerman > wrote: >> Package: ruby2.0 Version: 2.0.0.353-1 Severity: normal >> >> Dear Maintainer, >> >> I used `update-alternatives --config ruby` to set ruby2.0 as >> /usr/bin/ruby. This broke apt-listbugs, which could no longer >> require 'debian_version'. >> >> Obviously, the transition to ruby2.0 is not complete and problems >> like these are to be expected. >> >> The underlying problem is that e.g. apt-listbugs requires ruby >> (any version) and uses #!/usr/bin/ruby, whereas ruby-debian >> requires libruby1.8|libruby1.9.1. Thus when /usr/bin/ruby is >> ruby2.0, everything breaks. > > Since the ruby-debian has gained ruby2.0 support and apt-listbugs > works just fine with it: > > $ ruby2.0 /usr/bin/apt-listbugs list apt/0.9.9 Retrieving bug > reports... Done Parsing Found/Fixed information... Done serious > bugs of apt (-> 0.9.9) <Resolved in some Version> #558784 - apt: > re-adds removed keys (Fixed: 0.9.10) Summary: apt(1 bug)
Indeed. Unfortunately, apt-listchanges now breaks when /usr/bin/ruby is ruby1.8 (#734525) ;-( >> The problem would be solved if e.g. apt-listbugs used >> #!/usr/bin/ruby1.9.1, but then it would (need to) require >> ruby1.9.1. >> >> In the mean time, ruby2.0 is not suitable as /usr/bin/ruby. >> I've created symlinks to ruby2.0 in ~/bin instead to fix the >> problem for now, but this may still break other packages that use >> '#!/usr/bin/env ruby'. >> >> I suppose the least brittle solution would be to always use >> #!/usr/bin/ruby1.9.1 (etc.), the downside being that the package >> no longer works with other ruby versions. >> >> I've looked at the wiki and presumably gem2deb should solve the >> problem as well (by using the correct shebang for e.g. ruby1.8 >> and otherwise supporting all ruby versions). However, using >> /usr/bin/env (instead of /usr/bin/ruby) seems problematic to me, >> since one can't know what ruby version a user might have in his >> $PATH. >> >> If none of this is news to you, feel free to ignore this >> bugreport (although having the bug around may prevent others from >> running into the same problem). And if there's anything I can do >> to help, let me know. > > This is no news, besides nothing we do on ruby2.0 can make other > packages work with it, so this bug report against ruby2.0 does not > make much sense. Once we switch to ruby2.0 as the default, then any > package using /usr/bin/ruby and not working with ruby2.0 has to > have bug reports filed against it. I assumed as much. And obviously it's not ruby2.0's fault if other packages break. But because installing ruby2.0 and using update-alternatives to use it as /usr/bin/ruby may break various ruby-using packages, it seemed useful to file this bug report, if only so that someone installing ruby2.0 has a better chance of finding out that it's not ready to be /usr/bin/ruby (before breaking anything). And as for the rest of the bug report: I was just thinking aloud about how to prevent these kinds of problems in the first place. Thanks. And good luck with the ruby transitions. - - Felix -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCgAGBQJSzHd5AAoJELIY/ywn/GzGBF4P+gNZztigAO1wVyhgjVetATcU WDoP/ocbTJZzqSpgYlKSycgGSt+X9MdT5wRczBdwB5xQj2ChgNqY3iNKTVtG/wGI LkgLX4geA1+Ydp19iLsxSoN7Nkdu4i4gZ55pz+uoGVTEVroMwJtCWpnBfxvFplHT XReMd/tihqLBnysDxuuMtzYp8SDYTEt/K8/pADNgfu9szhV+ievjBHIyjQeIGu5b TuWICLiVkJbIYnwKQoLTFQSEJiEvAmmSQo8VgbDhrtrrugRS0oCn2Q/MD1oJzMwq 2InaUUE58oY11MsatkwQhrpx0kimRaDrj2H+2aBBZKo16YwLZobQJSfxrIvb1o3K 3Dpm2U6RImFAPNzLhwKsK/otBcjC+pJXlgYC/6L20F+pQs75N2kIeh50QNZnGFDM PdwrQ4kgu7JVqvhjIG61X6LQa9vGDgDoGZm97IymY7iLPtZw6RbH/kAxpHd1h0xo BqBlE+aPIYswTM8n1KUdqr/yHjefnf3FxOBvyvs/b3Qe+bnLcoEIK7dTRg2zmC+i mYbPW7X/XcHk6uUpjO9sZR2Os4h78F5QITLse7RR61Ze0EPlhyccQT0Jsuavb67t 6xB2LhocvoJTyG4lJEBCYqzVF3TN/MeoH2df4polrvhx7jy5WGuabhw1cS1fxoVa RD2RbdZt8YHNAGj6zdT3 =WO3w -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
