Re: Bug#214955: libgc6c102: cannot dist-upgrade from woody (libgc6) to sarge (libgc6c102)
On Thu, Oct 09, 2003 at 11:31:36AM -0500, Branden Robinson wrote:
> Also, the bug de-facto still exists. It's still not possible to
> dist-upgrade w3m or libgc6 from woody to sarge.
>
> http://packages.qa.debian.org/libg/libgc.html
>
> "The package has not yet entered testing even though the 10-day delay is over.
>
> # 53 days old (needed 10 days)
> # Valid candidate"
>
> 43 days of extra delay for no apparent reason is pretty bad. Have you
> spoken to the Release Manager or his deputies about this?
We're aware of it (or, well, I am anyway - I imagine others noticed
too).
> In the event you haven't, I am CCing this message to debian-release;
> hopefully this problem can be resolved, or the QA site's output improved
> to reveal the actual reason libgc is being prevented from entering
> testing.
packages.qa.debian.org shows only output from update_excuses.html, which
is essentially just an initial optimization step and as such incomplete.
To get full information you also need to check update_output.txt.
http://bjorn.haxx.se/debian/ does this.
trying: libgc
skipped: libgc (0 <- 208)
got: 52+0: a-52
* alpha: bock, chase, goo, libooc-x11-dev, libooc-xml-dev, oo2c, openc++, stklos, w3m, w3m-img, w3mmee, w3mmee-img, wmanager
Library soname changes often cause this kind of problem, since all their
reverse-dependencies need to be updated. In this case, my notes say that
the following problems need to be resolved:
* oo2c needs to be rebuilt: #211342.
* stalin needs to be built on arm and m68k.
* stklos needs to be rebuilt: #207027.
* w3m's release-critical bugs need to be fixed so that it's a
candidate for testing.
(The other packages listed have been updated; they're just listed
because upgrading libgc *on its own* does break them. I know of no fully
automatic way to find this out other than running britney in a
simulation setup.)
Once these problems are fixed, libgc will need a "hint" from a
release-type person; Ryan is fully capable of doing that himself, or
else one of us will do it.
Cheers,
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: