|
Home > Archive > Debian Developers > August 2004 > Gcc-3.4 holds back packages from testing?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Gcc-3.4 holds back packages from testing?
|
|
| Andreas Tille 2004-08-11, 2:51 am |
| Hi,
perhaps I missed something in my three weeks holidays but something
seems strange to me. If I look at the nice extended graph for the
excuses available in PTS (MANY THANKS FOR THIS!) for instance of the
package xteddy I get
...
xteddy is waiting for libungif4, tiff
* libungif4 is waiting for gcc-3.4
o gcc-3.4 has release-critical bugs
o gcc-3.4 is waiting for gcc-3.3
+ gcc-3.3 has release-critical bugs
+ gcc-3.3 is waiting for gcc-3.4
...
I wonder in how far gcc-3.4 is able to prevent packages from moving to
testing if it is not even in testing and packages should be builded with
gcc-3.3. Anybody able to enlighten me?
Kind regards
Andreas.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Goswin von Brederlow 2004-08-11, 2:51 am |
| Andreas Tille <tillea@rki.de> writes:
> Hi,
>
> perhaps I missed something in my three weeks holidays but something
> seems strange to me. If I look at the nice extended graph for the
> excuses available in PTS (MANY THANKS FOR THIS!) for instance of the
> package xteddy I get
>
> ...
>
> xteddy is waiting for libungif4, tiff
>
> * libungif4 is waiting for gcc-3.4
> o gcc-3.4 has release-critical bugs
> o gcc-3.4 is waiting for gcc-3.3
> + gcc-3.3 has release-critical bugs
> + gcc-3.3 is waiting for gcc-3.4
>
> ...
>
> I wonder in how far gcc-3.4 is able to prevent packages from moving to
> testing if it is not even in testing and packages should be builded with
> gcc-3.3. Anybody able to enlighten me?
Linked against libgcc1 build by gcc-3.4 in sid.
gcc-3.4 is in t-p-u and is waiting for the arm build to finish.
After that all tif and ocaml packages can/have to go in together.
> Kind regards
>
> Andreas.
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Andreas Metzler 2004-08-11, 2:51 am |
| On 2004-08-11 Andreas Tille <tillea@rki.de> wrote:
[...]
> * libungif4 is waiting for gcc-3.4
> o gcc-3.4 has release-critical bugs
[...]
> I wonder in how far gcc-3.4 is able to prevent packages from moving to
> testing if it is not even in testing and packages should be builded with
> gcc-3.3. Anybody able to enlighten me?
I'll just quote from http://people.debian.org/~aba/sarge.html#gcc-3.4
| Although gcc-3.4 is not the default compiler for sarge or even
| used by many packages (because the C++ ABI is incompatible) it is
| nevertheless a package that can block sarge. - Every other package
| has a "Depends: libgcc1" at least on ARM and since gcc-3.4 has been
| uploaded libgcc1 is built from the gcc-3.4 source package.
| gcc-3.4 (and a new version of gcc-3.3 on which it depends)
| have not made the base freeze, there were multiple problems
| including very limited time. gcc-3.3/gcc-3.4 will go in through
| testing-proposed-updates; gcc-3.3 1:3.3.4-6sarge1 and gcc-3.4
| 3.4.1ds1-4sarge1 have already been uploaded and are just waiting
| for the missing builds [...] build manually) and after that
| approval by the release-managers.
Afaict currently the only build that is still missing is gcc-3.3 on
ARM, but that is been taken care of by Kyle McMartin, therefore this
should be resolved *really* soon.
cu andreas
--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Steve Langasek 2004-08-11, 5:57 pm |
| On Wed, Aug 11, 2004 at 08:15:49AM +0200, Andreas Tille wrote:
> Hi,
> perhaps I missed something in my three weeks holidays but something
> seems strange to me. If I look at the nice extended graph for the
> excuses available in PTS (MANY THANKS FOR THIS!) for instance of the
> package xteddy I get
> ...
> xteddy is waiting for libungif4, tiff
> * libungif4 is waiting for gcc-3.4
> o gcc-3.4 has release-critical bugs
> o gcc-3.4 is waiting for gcc-3.3
> + gcc-3.3 has release-critical bugs
> + gcc-3.3 is waiting for gcc-3.4
> ...
> I wonder in how far gcc-3.4 is able to prevent packages from moving to
> testing if it is not even in testing and packages should be builded with
> gcc-3.3. Anybody able to enlighten me?
The original hope had been that gcc-3.3 and gcc-3.4, with the new
libgcc1, would make it into testing before the freeze. This didn't
happen due to various complicating factors, so we're instead working on
getting an update in through testing-proposed-updates; it looks like
this should be ready to happen tonight, at which point the rest of
unstable will thankfully be unstuck.
--
Steve Langasek
postmodern programmer
|
|
|
|
|