Control: tag -1 + wontfix Hello Laurent,
On Wed, Jan 27, 2021 at 10:34:24AM +0100, Laurent Bigonville wrote: > Source: gem2deb > Version: 1.2.1 > Severity: important > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > Hello, > > It looks like that gem2deb FTBFS on ia64 since version 1.2.1: > > debian/rules override_dh_auto_build > make[1]: Entering directory '/<<PKGBUILDDIR>>' > # NO_PKG_MANGLE=1 only useful on Ubuntu buildds, to disable pkgbinarymangler > NO_PKG_MANGLE=1 ruby2.5 -S rake test:unit TESTOPTS=-v > /usr/lib/ruby/2.5.0/rubygems.rb:284:in `find_spec_for_exe': can't find gem > rake (>= 0.a) with executable rake (Gem::GemNotFoundException) > from /usr/lib/ruby/2.5.0/rubygems.rb:303:in `activate_bin_path' > from /usr/bin/rake:23:in `<main>' > make[1]: *** [debian/rules:22: ruby2.5] Error 1 > > Not sure what's happening here, the dependency seems installed According to https://buildd.debian.org/status/fetch.php?pkg=gem2deb&arch=ia64&ver=1.4&stamp=1611285462&raw=0 ia64 doesn't even have ruby2.7. Then ruby-defaults was hacked (I see `ruby-all-dev ia64 1:2.7+3.is.2.5.7.1` in the logs) to still "work" with ruby2.5, while Debian has moved on to ruby2.7 a long time ago. The ia64 archive is stuck in a weird broken state which we cannot support. If there really is someone who cares about ia64, then the first step is fixing src:ruby2.7, then src:ruby-defaults. There is nothing that can be done in gem2deb to fix this.
signature.asc
Description: PGP signature
