Re: Bug#214955: libgc6c102: cannot dist-upgrade from woody (libgc6) to sarge (libgc6c102)
[I am not subscribed to debian-release.]
On Thu, Oct 09, 2003 at 09:22:30AM -0700, Ryan Murray wrote:
> On Thu, Oct 09, 2003 at 10:59:23AM -0500, Branden Robinson wrote:
> > It's not possible to apt-get dist-upgrade the w3m package from woody to
> > sarge because there is no transition path from libgc6 to libgc6c102 that
> > apt can figure out.
>
> This is already fixed by libgc1.
...which doesn't yet exist in testing, but thanks for bringing it to my
attention.
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?
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.
> You filed the original bug on libgc.
> Please check for duplicates before you file bugs.
I did, thanks to reportbug.
Please see:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libgc
and
http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libgc&archived=yes
...and I think you'll agree that there is no evidence of the bug having
been previously filed.
--
Branden Robinson | GPG signed/encrypted mail welcome
branden@progeny.com | 1024D/9C0BCBFB
Progeny Linux Systems | D5F6 D4C9 E25B 3D37 068C
| 72E8 0F42 191A 9C0B CBFB
Reply to: