New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #1884 - hardcode a version number for Debian's testing/unstable suites #351
Conversation
…g/unstable suites
thanks @olasd!, @GregSutcliffe mind having a look? |
@olasd I just tested this by running Since unstable and testing are always in that state (i.e. unstable never directly turns into sid), I think this will cause some confusion once sid final is shipped. |
The How about:
|
On dim., janv. 06 2013, Dominic Cleal wrote:
Hmm. It seems that wheezy only got this number a few days ago (in
Hmm, orel is set to lsbdistrelease already, so the testing case is a I'm not sure what to do next. The bug report is moot for current Thoughts?
|
On 06/01/13 23:59, Nicolas Dandrimont wrote:
Ack, bad time for me to test.
Oh, you're right - I thought it was just operatingsystemrelease. Sorry for the noise! Dominic Cleal |
@skottler sid is never released. It's the equivalent of rawhide. Once a package has been in sid for a while it moves to the current testing release. @olasd looks pretty awesome to me. I agree that we can;t really avoid a lookup table, since the version number only appears at the end of the release cycle. It's not too much work to maintain it, given Debian's release cycle :) @ohadlevy not tested, but looks fine to me 👍 |
@GregSutcliffe makes sense. Since Debian releases relatively rarely I don't think this will become a maintenance burden; just would have been nice to avoid maintenance altogether. Anyhow, looks good style and code-wise to me in it's current state so 👍 |
merged - thanks @olasd! |
Remove posix-spawn dependency for JRuby
Here's the patch as attached to http://theforeman.org/issues/1884