[Please keep the bug in Cc, thanks.] Andrew McMillan <[EMAIL PROTECTED]> (30/08/2007): > > The reasonable fix is to wait for the package to get out of NEW. > > So where can I get it from until then? How long will it take?
Nowhere, that's the NEW queue (packages may have legal troubles and the like, that's why there are available for no-one but FTP masters). No ETA. Some packages get out really quickly (some hours), some others may wait some days or even weeks, depending on manpower, workload and so on. > > AFAICT, gnome isn't the only UI (network-manager-kde…). By reading > > the changelog, you may also notice that several bugs are fixed by > > this upload, that might explains why the maintainer didn't wait for > > the other package to go out of NEW. > > Sure, I understand that half the world uses KDE, and that > network-manager-kde likely suffered similar problems, but how many of > those installations were broken *before* this upload, vs. how many > Gnome ones are broken *after*. Well, what breaks? There's a conflict, so either one removes the -gnome package, or keep the installed network-manager package. In the former case, one might think that something will be broken, so could tend not to force the upgrade. Then, by reading the changelog, one might understand that another -gnome binary is expected, and then wait for it. That's at least what I would expect from sid users. > AFAICS the package would not normally be installed when it *does* come > out of NEW, either, because it's been uninstalled now, so people will > have to manually go back and reselect it. That's correct, since you ACK'd the removal. Cheers, -- Cyril Brulebois
pgpLqGbNBJclG.pgp
Description: PGP signature
