Re: RFM: transition of flint
Hi,
Le 04/09/2015 15:21, Tobias Hansen a écrit :
On 09/04/2015 03:06 PM, Julien Puydt wrote:
- singular is in the list, no problem.
In the dep level 2, yes, but not at the start of the page, where it
lists what is affected.
Yes, that's all automatic based on the dependencies. On top is just the
information that has to be fed into the tool. Imagine there are 200
packages that need to be rebuilt for a transition. Then you also don't
create a list manually.
Ok, so things aren't as bad as I thought : that's a relief.
- I'm not sure what smooth-update means (maybe a function of some tool),
but you should set "Section: libs" in debian/control for the lib
package. Since you just forgot to do that, the information that
smooth-update is not possible might be wrong.
Oh. I'll add "Section: libs" to d/control then! And check all my other
packages... Should I prepare a 2.5.2-2 for that, to push into experimental?
Yes, after you checked what's up with the failing builds. i386 was
terminated after less than 3 hours, I don't know if that's normal.
Both the i386 and kfreebsd-i386 builds were terminated after 150
minutes, which is precisely 2h30min, so it does look like some round
time. For hurd-i386, it was 180 minutes which is precisely 3h. I really
think it's just a buildd setting which isn't set to the same value for
each build server. And I think the package is ok but tests are slow and
just hit the deadline.
The alpha failure is a real test failure, was already there for 2.4.5,
and was notified to upstream. It's not one of the first-class
architectures, so it isn't a blocker.
I dug my old i386 debian/unstable box out, updated it, updated its
pbuilder and put it on the matter. It's a slow box, with a slow disk, a
small RAM (hence will swap to the slow disk), so I don't expect to have
the result before tomorrow morning. And that's if none of my children
cut the power since the box is hooked to the same set of sockets as
their little boxes.
Thanks,
Snark on #debian-science
Reply to: