Your message dated Thu, 11 Sep 2014 13:35:44 +0200
with message-id <20140911113544.gb19...@inutil.org>
and subject line Re: Bug#482577: still applicable today? (pending notation)
has caused the Debian Bug report #482577,
regarding pending notation
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.)
--
482577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: security-tracker
I've been trying to use the tracker repository more actively for
tracking kernel updates and so far it is going pretty well. One
feature request I have is the ability to mark an issue as
pending. Usually multiple issues are queued up for a kernel DSA, and
its nice to be able to filter out issues that have already been
committed to the kernel repository.
I know I could use NOTEs for this, but I'd prefer to be able to note
this on a per-package basis. Something like the following would work
for my use case:
CVE-2008-2136 (Memory leak in the ipip6_rcv function in net/ipv6/sit.c in the
Linux ...)
- linux-2.6 <unfixed>
- linux-2.6 <unfixed> (pending 2.6.18.dfsg.1-18etch5)
- linux-2.6.24 <unfixed> (pending 2.6.24-6~etchnhalf.3)
NOTE: Upstream commit: 36ca34cc3b8335eb1fe8bd9a1d0a2592980c3f02
Or, maybe it makes more sense to add a new status - e.g. <pending> instead of
<unfixed>;
I don't have enough experience with the tracker to say for sure. (And
I realize that I could write my own tool to cross-reference the
security tracker w/ the kernel repository, but hey - I'm lazy.. and
this might be a good feature for the tracker in general).
--
dann frazier
--- End Message ---
--- Begin Message ---
On Thu, Sep 11, 2014 at 12:42:09PM +0200, Holger Levsen wrote:
> Hi,
>
> is this bug still of concern today? No activity since 5 years so I assume
> this
> problem has been solved or disappeared by now ;)
We can close this. With the current gen-dsa script the update can be prepared
in advance.
Cheers,
Moritz
--- End Message ---
