Hi all,
This is a quick note to let you know that things are nearly ready to allow
updates of apt, libsigc++1.2, gtkmm2.0, and related packages into etch as
part of the C++ ABI transition. At this point, the main blocker is perl,
which is expected to be a candidate for testing soon once a new
Hi release team,
This is a quick note to let you know that things are nearly ready to allow
updates of apt, libsigc++1.2, gtkmm2.0, and related packages into etch as
part of the C++ ABI transition. At this point, the main blocker is perl,
which is expected to be a candidate for testing soon
Dear Steve,
the package was ready and in place but the URL wrong, the debian
subdir was missing
http://bioinformatics.pzr.uni-rostock.de/~moeller/clustalw-mpi
http://bioinformatics.pzr.uni-rostock.de/~moeller/debian/clustalw-mpi/
I am happy to sponsor an upload of this package for you if you
On Sun, Oct 16, 2005 at 04:07:00PM -0700, Thomas Bushnell BSG wrote:
The big elephant being swallowed by the snake of the gcc-4 transition
is currently the KDE libraries, right? This impacts me because
gnucash/libofx/opensp can't move into testing until kmymoney2 is
ready, which ties it in
Hi!
Please, could you add kfreebsd-i386 to etch_arch_qualify.html ?
I've filled up a wiki page with the information:
http://wiki.debian.org/kfreebsd-i386EtchReleaseRecertification
--
Robert Millan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
* Robert Millan ([EMAIL PROTECTED]) [051017 17:24]:
Please, could you add kfreebsd-i386 to etch_arch_qualify.html ?
Basically, the page is restricted to architectures in unstable. The only
exception is amd64, because we consider the addition of amd64 to
unstable as an release blocker.
On Mon, Oct 17, 2005 at 05:33:55PM +0200, Andreas Barth wrote:
* Robert Millan ([EMAIL PROTECTED]) [051017 17:24]:
Please, could you add kfreebsd-i386 to etch_arch_qualify.html ?
Basically, the page is restricted to architectures in unstable. The only
exception is amd64, because we consider
Hi Kurt (etc.),
I just uploaded openssl version 0.9.8a which features symbol versioning.
It will hit the archive in the next hours and get autobuilded. I think
we should do a proper anouncement to d-d(-a) about the upload and that
the maintainers should at least rebuild their shared library
* Nathanael Nerode:
Note the following apparent facts:
* libssl0.9.7 and libssl0.9.8, if linked in the same binary, will cause
unpredictable failure due to symbol conflicts.
* This could be fixed if libssl0.9.8 had versioned symbols, which it doesn't
yet.
Are you sure? I think it's not
Averett Arif debian-release@lists.debian.org
Please forward this whereever appropriate.
The following packages were built against the libpng with overly strict
shlibs on one or more architectures, and to ease testing transition problems,
binNMUs are desired.
(See http://lists.debian.org/debian-release/2005/10/msg00149.html )
11 matches
Mail list logo