Your message dated Fri, 22 Sep 2006 09:17:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379886: fixed in gcc-snapshot 20060922-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the c
Your message dated Fri, 22 Sep 2006 09:17:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381176: fixed in gcc-snapshot 20060922-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the c
Your message dated Fri, 22 Sep 2006 09:17:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379885: fixed in gcc-snapshot 20060922-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the c
Your message dated Fri, 22 Sep 2006 09:17:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#385342: fixed in gcc-snapshot 20060922-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the c
Your message dated Fri, 22 Sep 2006 09:17:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#387368: fixed in gcc-snapshot 20060922-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the c
Your message dated Fri, 22 Sep 2006 09:17:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#387271: fixed in gcc-snapshot 20060922-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the c
Your message dated Fri, 22 Sep 2006 09:17:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381384: fixed in gcc-snapshot 20060922-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the c
Your message dated Fri, 22 Sep 2006 09:17:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#387257: fixed in gcc-snapshot 20060922-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the c
Accepted:
gcc-snapshot_20060922-1.diff.gz
to pool/main/g/gcc-snapshot/gcc-snapshot_20060922-1.diff.gz
gcc-snapshot_20060922-1.dsc
to pool/main/g/gcc-snapshot/gcc-snapshot_20060922-1.dsc
gcc-snapshot_20060922-1_amd64.deb
to pool/main/g/gcc-snapshot/gcc-snapshot_20060922-1_amd64.deb
gcc-snapsh
#
# bts-link upstream status pull for source package gcc-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #380121
# * http://gcc.gnu.org/PR21299
# * remote status changed: ASSIGNED -> NEW
usertags 380121 - status-A
#
# bts-link upstream status pull for source package gcc-snapshot
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #381176
# * http://gcc.gnu.org/PR28574
# * remote status changed: NEW -> RESOLVED
# * remote resolutio
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #388560
# * http://gcc.gnu.org/PR15305
# * remote status changed: (?) -> RESOLVED
# * remote resolution ch
On Sep 21, Matthias Klose <[EMAIL PROTECTED]> wrote:
> - the man pages (all except gfortran.1) are not built from
>source. -> RC
As long as the source is available in the package this is not a bug at
all.
--
ciao,
Marco
signature.asc
Description: Digital signature
Your message dated Fri, 22 Sep 2006 12:39:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Accepted gcc-snapshot 20060912-1 (source amd64)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Fri, 22 Sep 2006 12:39:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Accepted gcc-snapshot 20060912-1 (source amd64)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Fri, 22 Sep 2006 12:39:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Accepted gcc-snapshot 20060912-1 (source amd64)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Fri, 22 Sep 2006 12:39:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Accepted gcc-snapshot 20060912-1 (source amd64)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Fri, 22 Sep 2006 12:39:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Accepted gcc-snapshot 20060912-1 (source amd64)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Fri, 22 Sep 2006 12:39:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Accepted gcc-snapshot 20060912-1 (source amd64)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Fri, 22 Sep 2006 12:39:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Accepted gcc-snapshot 20060912-1 (source amd64)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Fri, 22 Sep 2006 12:39:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Accepted gcc-snapshot 20060912-1 (source amd64)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
> Nikita V. Youshchenko writes:
> > Hello.
> >
> > I've updated gcc-4.1 documentation packages (Section: non-free/doc).
> > Packages are no longer debian-native, also several issues have been
> > fixed.
> >
> > Also, I've created gcc-doc-defaults package (Section: contrib/doc)
> > that builds gcc-
gcc-4.1_4.1.1ds1-13+b1_arm.changes uploaded successfully to localhost
along with the files:
gcc-4.1-base_4.1.1-13+b1_arm.deb
libgcc1_4.1.1-13+b1_arm.deb
cpp-4.1_4.1.1-13+b1_arm.deb
protoize_4.1.1-13+b1_arm.deb
fixincludes_4.1.1-13+b1_arm.deb
libmudflap0_4.1.1-13+b1_arm.deb
libmudflap0
gcj-4.1_4.1.1-13_m68k.changes uploaded successfully to localhost
along with the files:
gcj-4.1-base_4.1.1-13_m68k.deb
gcj-4.1_4.1.1-13_m68k.deb
gij-4.1_4.1.1-13_m68k.deb
libgcj7-0_4.1.1-13_m68k.deb
libgcj7-awt_4.1.1-13_m68k.deb
gappletviewer-4.1_4.1.1-13_m68k.deb
libgcj7-dev_4.1.1-13_
Processing commands for [EMAIL PROTECTED]:
> tags 379885 + pending
Bug#379885: [ia64] ICE in ia64_expand_move, at config/ia64/ia64.c:1088
Tags were: fixed-upstream upstream
Tags added: pending
> tags 379886 + pending
Bug#379886: [ia64] ICE in final_scan_insn, at final.c:2448
Tags were: fixed-upst
Le jeudi 21 septembre 2006 à 14:32 +0200, Matthias Klose a écrit :
> - build-depend on gcc-4.1-source (including the -doc patches),
>build the package (bootstrap_target=all), then just package
>the documentation.
If the source packages still contain some GFDL documents, then this is a
RC
Processing commands for [EMAIL PROTECTED]:
> forwarded 388596 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29178
Bug#388596: gcj-4.1: CharsetEncoder.canEncode() gives different results than
Sun version
Noted your statement that Bug has been forwarded to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id
Nikita V. Youshchenko writes:
> Hello.
>
> I've updated gcc-4.1 documentation packages (Section: non-free/doc).
> Packages are no longer debian-native, also several issues have been fixed.
>
> Also, I've created gcc-doc-defaults package (Section: contrib/doc) that
> builds gcc-doc, cpp-doc, gfor
28 matches
Mail list logo