Re: plans for d-i string freeze

[Christian Perrier <bubulle@debian.org>]

Quoting David Nusinow (dnusinow@sbcglobal.net):

> Hi Joey and everyone, thanks for the cc. I'm willing to maintain
> discover in maintainance mode, but if Progeny plans to focus on
> discover2, I don't really see the point in keeping discover1 alive
> beyond the sarge release. The fix from Thomas Poindessous isn't really
> a fix at all, if you look at it. It seems the real bug is in
> linux-kernel-headers, from what I can tell, so once that's fixed an
> upload can be made. If anyone at all is interested in maintaining
> discover1, I won't stand in their way.

When reading Thomas fix, I had this feeling, yes.

However, the point is to remove this FTBFS bug from discover1 so that
it can be part of the sarge release.

Thomas fix may be called a ugly hack, I guees, but it works...and thus
allows me to do what I first intended to do --> switch to po-debconf
and have the debconf templates translated.

I'm currently inthe process of having a quick NMU uploaded (with the
help of Joey), by using Thomas dirty fix.

I don't have the skills for doing a better job, unfotunately.

I propose that I send you a copy of the "fixed" diff file for the
1.5-1.4.2 NMU. Then you may have a look at it and propose a better
fix. Thus, you may then be able to propose a clean 1.4.3 fix.

Are you OK with this way to deal with this ?

Discover1 needs to be kept alive in sarge....at least because d-i is
using it.