Your message dated Wed, 19 Aug 2015 14:48:21 +0200
with message-id <[email protected]>
and subject line Re: please use secure testing svn repo as data source
has caused the Debian Bug report #776903,
regarding please use secure testing svn repo as data source
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 [email protected]
immediately.)
--
776903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776903
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: debian-security-supprt
severity: wishlist
Hi,
TTBOMK debian-security-support uses a manually maintained file to display EOL
informaton for packages, yet the security team also stores this data in the
secure-testing SVN repo.
This data source duplication is bad, because it's manual work, errorprone and
thus lacking behind.
So please secure testing as data source _durin build time_.
eg. one example is the newly introduced EOL for chromium in wheezy, which is
not reflected in this package yet and which needs to be manually tracked and
added.
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
On Tue, Feb 03, 2015 at 08:35:58AM +0100, Holger Levsen wrote:
> package: debian-security-supprt
> severity: wishlist
>
> Hi,
>
> TTBOMK debian-security-support uses a manually maintained file to display EOL
> informaton for packages, yet the security team also stores this data in the
> secure-testing SVN repo.
>
> This data source duplication is bad, because it's manual work, errorprone and
> thus lacking behind.
>
> So please secure testing as data source _durin build time_.
We shouldn't do that. That data should only be controlled by the group
of uploaders, not the far wider group of people with access to the security-
tracker.
> eg. one example is the newly introduced EOL for chromium in wheezy, which is
> not reflected in this package yet and which needs to be manually tracked and
> added.
That's because it is not yet in wheezy.
Cheers,
Moritz
--- End Message ---
