On Mon, Jun 28, 2004 at 12:32:33PM -0400, Christopher Martin wrote:
> On June 28, 2004 10:38, Andreas Metzler wrote:
> > Afaict if kdelibs went into testing and qt3 did not KDE would be
> > completely broken.
> Martin Loschwitz has stated that he plans to upload Qt 3.3 to unstable
> shortly after the FTP masters allow it into experimental. Once Qt 3.3
> hits Sid, presumably with an updated shlibs, kdelibs could then be
> rebuilt and this whole problem would disappear. However, this would take
> a long time, and in the meanwhile cupsys and dozens of other packages
> would continue to be stuck in Sid due to the gnutls transition.
s/dozens of/400/
> I doubt Martin Loschwitz is going to make another update to the current Qt
> 3.2, as he has not reacted in any way to #255539. He has stated that he
> doesn't like NMUs, though perhaps he might relent this time. Kdelibs
> would still need to be rebuilt against this new Qt, however, so this
> solution would still take a while to complete.
Unless a autobuilder breaks down imho it could be done in less than 7
days, taken together with:
| kdesdk is only 3 days old. It must be 10 days to go in.
which is one of the packages blocking cups/gnome/kdelibs you see that
almost no time is wasted.
> One possible fudge would be simply to downgrade #255539 (and this bug,
> #256690) and ensure that the current kdelibs and Qt (and kdeartwork) make
> Sarge at the same time. This is imperfect, but it would at least help to
> break the current logjam in Sid.
As it is probably not possible to the sarge migration without
temporarily broken KDE anyway this is a valid alternative.
cu andreas
