[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Processed (with 2 errors): merging, tagging and CVE number



Processing commands for control@bugs.debian.org:

> forcemerge 398470 415112
Bug#398470: 2.6.18: mysterious, possibly race-y oops in key/keyring code
Bug#415112: linux-image-2.6.18-4-amd64: kernel oops in keyring_destroy
Mismatch - only Bugs in the same package can be forcibly merged:
Bug 415112 is not in the same package as 398470
> tags 398470 +patch
Bug#398470: 2.6.18: mysterious, possibly race-y oops in key/keyring code
There were no tags set.
Tags added: patch

> tags 398470 +security
Bug#398470: 2.6.18: mysterious, possibly race-y oops in key/keyring code
Tags were: patch
Tags added: security

> tags 398470 serious
Unknown tag/s: serious.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore.

Bug#398470: 2.6.18: mysterious, possibly race-y oops in key/keyring code
Tags were: security patch
Tags added: 

> retitle 398470 key serial number collision (CVE-2007-0006)
Bug#398470: 2.6.18: mysterious, possibly race-y oops in key/keyring code
Changed Bug title to key serial number collision (CVE-2007-0006) from 2.6.18: mysterious, possibly race-y oops in key/keyring code.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



Reply to: