On Sat, Apr 09, 2005 at 11:28:00PM -0500, Dirk Eddelbuettel wrote: > | > The current version is a release candidate for the upcoming 0.3.9 release. > | > I don't typically make ql-python and ql-ruby release for release > | > candidate. Should I this time for mipsel? Or can this wait til 0.3.9 > | > comes out ?
> | It can wait, and be fixed by the t-p-u autobuilder for mipsel once sarge is > | frozen; but it sounds to me in this case like the release-candidate version > | of quantlib should not have been uploaded to unstable, as it's not actually > | a candidate for the Debian release... > Well, it is for me (bug fixes upstream) and we're not yet frozen, are we? In that case, AIUI this will become an RC bug on quantlib-ruby in testing as soon as the new version of libquantlib0-dev package reaches testing. If so, then yes, you should be fixing quantlib-ruby and quantlib-python since from what I see, the quantlib update will be in testing in 6 days. > | quantlib-ruby (together with quantlib-python) is one of the last two > | out-of-date packages on mipsel following the arch's problems earlier this > | year. It *should* not be a problem to get fixed versions into testing via > | t-p-u, unless there's an RC build problem that likely affects other > I'm a little rusty on the details. How would I get 0.3.8 on mipsel into > testing ? Do I need to upload anything new? No, it would be the porters' responsibility to pick up out-of-date testing packages autobuilding; but I believe the above issue is controlling. -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
