** Changed in: botan1.10 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760263
Title:
RM: will become EOL upstream in December, not in testing
To manage
Understood.
I therefore withdraw this removal request.
** Changed in: botan1.10 (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: monotone (Ubuntu)
Status: Confirmed => Invalid
** Changed in: botan1.10 (Ubuntu)
Status: Won't Fix => Invalid
** Changed in: ovito (Ubunt
I don't agree that it makes any difference to the actual security of the
end user, if the upstream security fixes exist but no one cares enough
about the package to include them in SRUs.
https://people.canonical.com/~ubuntu-security/cve/pkg/botan1.10.html
shows 6 unfixed CVEs against botan1.10 in
> It appears there has been precisely one security SRU of botan1.10
ever, in Ubuntu 14.04. So what difference does a lack of upstream
security support make to the releasability of this package in 18.04?
I think there's a difference between lack of human resources to do these
updates versus updates
It appears there has been precisely one security SRU of botan1.10 ever,
in Ubuntu 14.04. So what difference does a lack of upstream security
support make to the releasability of this package in 18.04?
** Changed in: botan1.10 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this
** Changed in: botan1.10 (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760263
Title:
RM: will become EOL upstream in December, not in testing
To manage notif
RM (RoM) bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889675
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760263
Title:
RM: will become EOL upstream in December, not in testing
To manag
