I maintain a package (remctl) that builds, among other things, a Ruby extension. I noticed that it showed up as affected by the upcoming ruby1.8-removal transition, and I think this may be the relevant bug. (At least, it's the only open bug that looks relevant.)
On my next package upload, should I just drop Ruby 1.8? I can easily do that, but I wasn't sure if we were at the point where that was now desirable, or if the upgrade path for Ruby 1.8 users had been worked out and had any implications for how I should handle matters in my package. (Breaks or whatnot, etc.) For now, I'm continuing to build 1.8 and 1.9.1 modules, but I can quickly change that as soon as I know what to do. (Due to the nature of this source package, it handles which Ruby versions to build for itself, so it requires some minor source changes to fiddle with the supported version list.) -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
