Conversation
Increase alternatives priority so 2.0 is preferred over 1.8. This brings it into line with the packaging for [1.9](https://github.com/brightbox/deb-ruby1.9.1/blob/master/debian/ruby1.9.1.postinst) and [2.1](https://github.com/brightbox/deb-ruby2.1/blob/master/debian/ruby2.1.postinst).
|
I wanted to check if this fix could make it into the bright boxrepo this week. |
|
Looks good - I'll get it merged and new packages built, but it's not quite a priority for me just right now - perhaps this week. |
|
Thanks for letting me know! |
|
Still planning to merge this? |
|
Ping. |
|
I'd kind of let the 2.0 packages go stale - I presumed anyone capable of using 2.0 would be using 2.1 now. Am I wrong? |
|
I'm afraid we don't proactively move applications to a new ruby version. New applications are launched on 2.1, but we still run many on 2.0 and 1.9.3. |
|
I fixed this because I was already having to build a new ruby2.0 package for a security update, and I noticed the same problem on another package too. I'm sorry that I did this independently and didn't just merge your pull request - I'd totally forgotten about it. I was initially uncertain about your changes because I didn't understand the repercussions but since then, I wrote a test suite to check all this stuff so was more confident this time around. Anyway, again, sorry Brian! Thanks for the contribution. |
|
No worries! I'm glad it was straightened out. |
2 participants
Increase alternatives priority so 2.0 is preferred over 1.8. This brings it into line with the packaging for 1.9 and 2.1.