Christian Hofstaedtler <[email protected]> writes: > Looking at the m68k buildlogs for ruby-fast-xs ... the version of > ruby-fast-xs installed as part of the telegram build was built for > ruby2.2, but ruby itself was already ruby2.3. This just does not > work.
Good point. I'd missed that discrepancy because the binNMU changelog messages threw me off. I've now reported #860747 to request giving extensions stricter dependencies on the ruby metapackage, which would have allowed generic tools to catch this problem automatically, and meanwhile submitted (off-BTS) a give-back request for telegram-server on m68k. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/[email protected] _______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
