On Mon, Jul 25, 2011 at 05:44:00PM +0200, Moritz Muehlenhoff wrote:
Hi wanna-build team,
due to the key rollover a few security packages got rejected after
running dak new-security-install on the changes file; the key was
valid when the files were accepted for upload, but the key expired
when
On Tue, Jul 26, 2011 at 12:51:41PM +0200, Kurt Roeckx wrote:
On Mon, Jul 25, 2011 at 05:44:00PM +0200, Moritz Muehlenhoff wrote:
Hi wanna-build team,
due to the key rollover a few security packages got rejected after
running dak new-security-install on the changes file; the key was
valid
On Mon, Jul 25, 2011 at 05:44:00PM +0200, Moritz Muehlenhoff wrote:
Hi wanna-build team,
due to the key rollover a few security packages got rejected after
running dak new-security-install on the changes file; the key was
valid when the files were accepted for upload, but the key expired
when
On Tue, Jul 26, 2011 at 02:50:42PM +0200, Kurt Roeckx wrote:
On Mon, Jul 25, 2011 at 05:44:00PM +0200, Moritz Muehlenhoff wrote:
Hi wanna-build team,
due to the key rollover a few security packages got rejected after
running dak new-security-install on the changes file; the key was
valid
Hi wanna-build team,
due to the key rollover a few security packages got rejected after
running dak new-security-install on the changes file; the key was
valid when the files were accepted for upload, but the key expired
when the actual release happened.
As discussed with Phil here are the files,
Hello,
2011/7/25 Moritz Muehlenhoff j...@debian.org:
As discussed with Phil here are the files, which need to be re-signed:
opensaml2_2.0-2+lenny3_armel.reason
I have signed armel related packages with newer key, should be
uploaded as soon as cron job picks it up. But I do wonder if we are
