On Thu, Jan 14, 2010 at 02:46:25AM +0100, Matthias Klose wrote:
doesn't matter. GCC-4.5 won't be the default for squeeze. if the GCC-4.5
release is done before the squeeze freeze, then it will be uploaded to
unstable and enabled to build for architectures where it doesn't show
regressions
On Fr, Jan 15, 2010 at 17:29:58 (CET), Neil McGovern wrote:
On Thu, Jan 14, 2010 at 02:46:25AM +0100, Matthias Klose wrote:
doesn't matter. GCC-4.5 won't be the default for squeeze. if the GCC-4.5
release is done before the squeeze freeze, then it will be uploaded to
unstable and enabled to
On Thu, Jan 14, 2010 at 02:28:41AM +0100, Holger Levsen wrote:
Hi,
On Donnerstag, 14. Januar 2010, Julien Cristau wrote:
Except you don't want the squeeze tag for gcc-4.5 bugs, you want the
squeeze+1 tag, which doesn't exist.
I'd hope that tagging them sid is the right + working thing
On Tue, Jan 12, 2010 at 10:20:38AM +0100, Holger Levsen wrote:
Hi,
On Dienstag, 12. Januar 2010, Raphael Geissert wrote:
Please don't forget to usertag the reports. Using the ftbfs-gcc-4.5
usertag should make it easier to track them (which would later make them
show up on the
Kurt Roeckx wrote:
On Tue, Jan 12, 2010 at 10:20:38AM +0100, Holger Levsen wrote:
Hi,
On Dienstag, 12. Januar 2010, Raphael Geissert wrote:
Please don't forget to usertag the reports. Using the ftbfs-gcc-4.5
usertag should make it easier to track them (which would later make them
show up on
Hi,
On Mittwoch, 13. Januar 2010, Luk Claes wrote:
Please also tag them sid (and squeeze?), so they wont show up affecting
stable, if the version in stable is the same as in sid...
I wouldn't worry about that just yet. Unless we're planning
on switching to gcc-4.5 before the release.
On Thu, Jan 14, 2010 at 01:13:19 +0100, Holger Levsen wrote:
In both cases it would be nice if you'd tag those bugs (FTBFS with
gcc-4.4 and 4.5) with sid+squeeze, so that they dont show up as RC
bugs for stable, for packages which have the same version in lenny.
Except you don't want the
Hi,
On Donnerstag, 14. Januar 2010, Julien Cristau wrote:
Except you don't want the squeeze tag for gcc-4.5 bugs, you want the
squeeze+1 tag, which doesn't exist.
I'd hope that tagging them sid is the right + working thing then :)
cheers,
Holger
signature.asc
Description: This is a
On 12.01.2010 10:20, Holger Levsen wrote:
Hi,
On Dienstag, 12. Januar 2010, Raphael Geissert wrote:
Please don't forget to usertag the reports. Using the ftbfs-gcc-4.5
usertag should make it easier to track them (which would later make them
show up on the ddpo-by-mail emails, but please only
Le lundi 11 janvier 2010 à 19:25 +0100, Matthias Klose a écrit :
A rebuild test of the current Debian unstable distribution on
x86_64-linux-gnu
was done, one rebuild test with the current gcc-4.4 from the branch, and
another
one with GCC trunk 20100107.
Thanks for taking care of this.
Hi,
On Dienstag, 12. Januar 2010, Raphael Geissert wrote:
Please don't forget to usertag the reports. Using the ftbfs-gcc-4.5
usertag should make it easier to track them (which would later make them
show up on the ddpo-by-mail emails, but please only use one email as User).
Please also tag
On 12.01.2010 00:00, Cyril Brulebois wrote:
Matthias Klosed...@debian.org (11/01/2010):
I'll go through the list of build failures this week, trying to file
appropriate bug reports for GCC or the distribution. Please let me
know if somebody wants to work on this list as well.
Hi,
I might
A rebuild test of the current Debian unstable distribution on x86_64-linux-gnu
was done, one rebuild test with the current gcc-4.4 from the branch, and another
one with GCC trunk 20100107. The latter did show about 200 additional build
failures, which are listed in [1] (minus some already known
Matthias Klose d...@debian.org (11/01/2010):
I'll go through the list of build failures this week, trying to file
appropriate bug reports for GCC or the distribution. Please let me
know if somebody wants to work on this list as well.
Hi,
I might want to join this kind of effort for next runs:
Hi Matthias,
Matthias Klose wrote:
I'll go through the list of build failures this week, trying to file
appropriate bug reports for GCC or the distribution. Please let me know if
somebody wants to work on this list as well.
Please don't forget to usertag the reports. Using the ftbfs-gcc-4.5
15 matches
Mail list logo
