FYI: 6.2.9-rc7 still has this problem, but it will work if krb5-config is
on the PATH somewhere and --with-kerberos5 is used without path.
Perhaps this information can be used to update build instructions within
Debian.
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
, so we could do the same for arm.
Matthias
Lennert Buytenhek writes:
> Package: gij-4.0
> Version: 4.0.2-2
> Severity: important
>
> On armeb (and the same thing appears to be happening on regular arm),
> gij doesn't seem to work at all -- trying to run any .class f
has some problems in modifying
the server-side contact list, especially adding new contacts.
I hope this information will help somehow.
Matthias Kuehn
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: tulip
Severity: important
Please do not take any action before reading
http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html
This bug report is filed against the source package which builds
a library depending on libstdc++6 and defining or referencing
*mt_alloc* symbols. T
Package: varconf
Severity: important
Please do not take any action before reading
http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html
This bug report is filed against the source package which builds
a library depending on libstdc++6 and defining or referencing
*mt_alloc* symbols.
Package: vips
Severity: important
Please do not take any action before reading
http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html
This bug report is filed against the source package which builds
a library depending on libstdc++6 and defining or referencing
*mt_alloc* symbols. Th
Package: vtk
Severity: important
Please do not take any action before reading
http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html
This bug report is filed against the source package which builds
a library depending on libstdc++6 and defining or referencing
*mt_alloc* symbols. The
Package: wfmath
Severity: important
Please do not take any action before reading
http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html
This bug report is filed against the source package which builds
a library depending on libstdc++6 and defining or referencing
*mt_alloc* symbols.
Package: wftk
Severity: important
Please do not take any action before reading
http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html
This bug report is filed against the source package which builds
a library depending on libstdc++6 and defining or referencing
*mt_alloc* symbols. Th
Package: xalan
Severity: important
Please do not take any action before reading
http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html
This bug report is filed against the source package which builds
a library depending on libstdc++6 and defining or referencing
*mt_alloc* symbols. T
Package: zipios++
Severity: important
Please do not take any action before reading
http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html
This bug report is filed against the source package which builds
a library depending on libstdc++6 and defining or referencing
*mt_alloc* symbols.
Package: usrp
Severity: important
Please do not take any action before reading
http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html
This bug report is filed against the source package which builds
a library depending on libstdc++6 and defining or referencing
*mt_alloc* symbols. Th
reopen 312830
thanks
Stephen R Marenka writes:
> On Sun, Nov 13, 2005 at 03:17:22AM +0100, Matthias Klose wrote:
> > Debian Bug Tracking System writes:
> > > Package: gij-4.0
> > > Version: 4.0.2-3
> > >
> > > I've confirmed that this bug is fi
Package: ftp.debian.org
Please remove readline4, after all packages are converted to use
readline5.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: lib64z1-dev
Severity: serious
Version: 1:1.2.3-6
s/lib64c-dev/lib64c6-dev/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Robert Woodcock writes:
> On Tue, Nov 15, 2005 at 07:55:58AM +0100, Matthias Klose wrote:
> > Package: id3lib3.8.3
> > Severity: important
> >
> > Please do not take any action before reading
> > http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html
Package: alsa-lib
Severity: wishlist
Please build biarch packages for libasound, needed for biarch builds
of libgcj from the gcc-snapshot and gcc-4.1 packages. Patch at
http://people.ubuntu.com/patches/alsa-lib-biarch.diff
Note, that the 32bit directory on Debian is usr/lib32 for ppc64 and
the
Package: binutils
Version: 2.16.1cvs20051109-1
Severity: serious
Tags: patch
Using expect-tcl8.3 lets the build succeed.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
301 - 400 of 14114 matches
Mail list logo
