Re: Bug#633561: kfreebsd-i386 d-i/squeeze FTBFS (was Re: Bug#633561: pu: package kfreebsd-8/8.1+dfsg-8+squeeze1)

2011-10-07 Thread Adam D. Barratt
On Thu, 2011-10-06 at 23:12 +0200, Robert Millan wrote: 2011/10/6 Julien Cristau jcris...@debian.org: On Thu, Oct 6, 2011 at 07:20:50 +0200, Robert Millan wrote: Attached patch should fix the problem. I can upload a fixed kfreebsd-8 this evening (feel free to NMU if someone has time to

Re: Bug#633561: kfreebsd-i386 d-i/squeeze FTBFS (was Re: Bug#633561: pu: package kfreebsd-8/8.1+dfsg-8+squeeze1)

2011-10-06 Thread Julien Cristau
On Thu, Oct 6, 2011 at 07:20:50 +0200, Robert Millan wrote: Attached patch should fix the problem. I can upload a fixed kfreebsd-8 this evening (feel free to NMU if someone has time to verify earlier than that). What's the status of that upload? Cheers, Julien -- To UNSUBSCRIBE, email

Re: Bug#633561: kfreebsd-i386 d-i/squeeze FTBFS (was Re: Bug#633561: pu: package kfreebsd-8/8.1+dfsg-8+squeeze1)

2011-10-06 Thread Robert Millan
2011/10/6 Julien Cristau jcris...@debian.org: On Thu, Oct  6, 2011 at 07:20:50 +0200, Robert Millan wrote: Attached patch should fix the problem.  I can upload a fixed kfreebsd-8 this evening (feel free to NMU if someone has time to verify earlier than that). What's the status of that

Re: Bug#633561: kfreebsd-i386 d-i/squeeze FTBFS (was Re: Bug#633561: pu: package kfreebsd-8/8.1+dfsg-8+squeeze1)

2011-10-05 Thread Philipp Kern
On Wed, Oct 05, 2011 at 11:20:00PM +0100, Adam D. Barratt wrote: [tl,dr; these changes broke d-i in stable] I think in the worst case we can just keep the current (as in non-point release version) of d-i on kfreebsd-* for the next point release and don't update to the binNMU. It's actually from

Re: Bug#633561: kfreebsd-i386 d-i/squeeze FTBFS (was Re: Bug#633561: pu: package kfreebsd-8/8.1+dfsg-8+squeeze1)

2011-10-05 Thread Robert Millan
2011/10/6 Philipp Kern pk...@debian.org: That said, this needs to be fixed, and we're all not very happy, given the fact that we actually did ask before if something changes in the udeb output. I have to say in my defense that I did check for changes in udeb output. However these changes