On Sat, 2008-08-09 at 17:29 +0200, Luk Claes wrote: > Adam C Powell IV wrote: > > > So what should I do now? > > 1. Do nothing, let all the bugs in testing enter the lenny release > > 2. Do nothing, get a freeze exception for the new scotch, which > > would let libmesh go in > > 3. Upload scotch 5.0.1.dfsg-1lenny1 (which needs to go through the > > NEW queue, but the changes are much smaller than 5.0.6) and > > libmesh 0.6.2.dfsg-1lenny1 depending on it > > 4. Upload libmesh 0.6.2.dfsg-1lenny1 depending on the old scotch > > with only static libs, but closing the other six bugs in libmesh > > > > Which would you accept? > > As the bugs are not that important from a release point of view, I'm > afraid that option 1 is the one we would prefer. Option 4 could also be > a possibility, though please upload to unstable in that case using > debian revision 3.
Thanks, but that won't work, as uploading -3 to unstable will link it with the new scotch's shared libs, which isn't and won't be in testing. I think the only way to do option 4 is to do -1lenny1. Will you likely accept that, with minimal changes vs. -1? Fixing the examples adds about 16 new Makefiles, but the rest doesn't change that much. -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/
signature.asc
Description: This is a digitally signed message part
