Your message dated Sun, 17 Mar 2013 16:30:38 +0100
with message-id <201303171630.39455.th...@debian.org>
and subject line Re: buildds ready for wheezy-security?
has caused the Debian Bug report #687334,
regarding Please add security queues for armhf and s390x
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
687334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: buildd.debian.org
Severity: serious
Control: affects -1 security.debian.org
Hi,
This is just to keep a record of things that need to be done before the
release:
* Add security queues for armhf
* Add security queues for s390x
Of course the sec archive first needs to know about them, so I'm going
to file a similar bug against ftp-master.d.o for that.
Cheers,
Raphael Geissert
--- End Message ---
--- Begin Message ---
Op vrijdag 15 februari 2013 09:27:14 schreef Thijs Kinkhorst:
> It would be great if we could have a guinea pig security update for wheezy
> through wheezy-security sometime soon, so we can verify that everything is
> in order for the release.
Today, we've installed wireshark/1.8.2-5wheezy1 through wheezy security. All
builds arrived, packages installed, no errors. Adam confirms packages
correctly received in tpu. I can install the packages on my wheezy system. The
security tracker knows about the version in wheezy-security. Looks like we're
ready for wheezy, for the security archive part. Closing this bug.
Cheers,
Thijs
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
