Please give back evolution-sharp/0.16.0-1 on amd64 and ia64
I uploaded evolution-sharp after uploading a new mono release, which was
not that good :-P as it lets all packages fails to build till mono is
built on each arch. (mono on amd64 and ia64 are built already)
--
Regards,
Mirco 'meebey'
Hi!
aba made me aware of that the Release Management could go well with a
link to release.debian.org so I added it. While doing so I noticed that
the whole thing looks a bit chaotic:
Release Managers --
...
Release Managers for ``stable'' --
...
Release Assistants --
...
On Tuesday 08 April 2008, Michael Meskes wrote:
On Sun, Apr 06, 2008 at 09:45:15PM -0400, Jay Berkenbilt wrote:
To all maintainers of packages that have dependencies on libxerces27
or libxerces28:
If you do not have a build dependency on libxerces27-dev or
libxerces28-dev, then please
Hi,
I've uploaded openssl 0.9.8c-4etch2 to proposed-updates a few days ago.
It contains 2 security fixes of which 1 is rather large.
Could this be accepted in proposed-updates and later maybe move to a
stable point release?
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
On Tue, Apr 08, 2008 at 12:26:49PM +0200, Mirco Bauer wrote:
Please give back evolution-sharp/0.16.0-1 on amd64 and ia64
I uploaded evolution-sharp after uploading a new mono release, which was
not that good :-P as it lets all packages fails to build till mono is
built on each arch. (mono on
Package: ftp.debian.org
Severity: normal
When investigating a fix for CVE-2007-1047 upstream told us that the
ancient version of DCC in stable causes problems for the public
DCC servers. Since newer versions are non-free and have already been
removed from unstable, DCC should rather be removed
Dear maintainer and Stable release team,
One user on the debian-user-french mailing list noted that the bug
432665 was rendering the package useless but is apparently not fixed in
a point release of Etch. If the bug really originates from a single ''
missing, is there a chance that a stable
7 matches
Mail list logo