On Thursday 19 May 2011 22:34:27 Philipp Kern wrote:
On Thu, May 19, 2011 at 01:34:10PM +0200, René Mayrhofer wrote:
Attached is only the patch to be applied to fix #616482.
There was no such attachment, I'm afraid.
Mea culpa. The patch is trivial enough so as not to cause any trouble,
On Sunday 26 October 2008, Philipp Kern wrote:
With the CVE number not mentioned in the changelog and probably nobody
including Security and Release Team were informed, oh well.
Well, there was no CVE number (that I was aware of) at the time of this
upload. It is true that security should have
The currently uploaded version of havp compiles and runs with libclamav-dev
version 0.94. Although it is a new upstream version (0.89) in comparison to
the one currently in Lenny (0.88), the changes are minimal:
- fixing the potential DoS issue that was already fixed in the last NMU (same
The currently uploaded version of strongswan disables some experimental
features as suggested by upstream developers especially for the Lenny
release. The package is significantly smaller (and should probably expose
fewer bugs).
Please un-freeze today's strongswan upload for Lenny.
best
Am Mittwoch, 3. Januar 2007 23:47 schrieb Steve Langasek:
I think Andi meant that it should be possible for someone with an interest
in the package to get it back into a releasable state -- not that the
current package would be considered appropriate for inclusion in etch.
I certainly don't
+, Rene Mayrhofer wrote:
Am Donnerstag, 14. Dezember 2006 17:01 schrieb Andreas Barth:
gibraltar-bootcd was removed in March from Etch - I don't think it
would
be appropriate to allow it now back in until there are *very* good
reasons for it.
Yes, the reason was the FTBFS
Dear release managers,
Just a few days ago it cam to my attention (due to an entry in the BTS) that
the problematic uclibc-toolchain breakage that affected gibraltar-bootcd for
too long is connected with gcc 3.3. A small fix actually makes
gibraltar-bootcd compile now - it just needs to
Am Donnerstag, 14. Dezember 2006 17:01 schrieb Andreas Barth:
gibraltar-bootcd was removed in March from Etch - I don't think it would
be appropriate to allow it now back in until there are *very* good
reasons for it.
Yes, the reason was the FTBFS, where everybody agreed that it was
Dear Steve,
Am Saturday 21 May 2005 15:59 schrieb Steve Langasek:
I'd still be happy to let it into sarge if you
wanted to do this. ...
Unfortunately there was a small issue with build-depends (libcurl-dev
transition) in 1:2.2.0-6. Could you please allow 2.2.0-7 to enter sarge,
which
Am Friday 27 May 2005 09:48 schrieb Rene Mayrhofer:
Unfortunately there was a small issue with build-depends (libcurl-dev
transition) in 1:2.2.0-6. Could you please allow 2.2.0-7 to enter sarge,
which only fixes this FTBFS?
Sorry, that should've read 2.2.0-8 (2.2.0-6 was internal
Hi all,
Does anybody want to test the current openswan 1:2.2.0-7 packages at
http://www.gibraltar.at/~rene/openswan/
or should I upload to unstable? If nobody can give it a try, I intent to
upload tomorrow morning (GMT+2).
with best regards,
Rene
pgp3UvPKK5k5I.pgp
Description: PGP signature
Hi list,
mkinitrd-cd 0.52 fixes quite some bugs and should really make it into sarge.
The only reason why it hasn't propagated yet is an override disparity, which
I intend to fix soon enough. However, no changes should be needed to 0.52, it
is perfectly suitable for sarge.
with best regards,
Am Donnerstag, 27. Januar 2005 16:49 schrieb Andreas Barth:
We discussed a bit in the release team.
Our first question is: Why don't you just fix the bug in unstable, and
we push the package through to testing? If the unstable package is not
suitable for sarge, than yes, please upload a
13 matches
Mail list logo
