--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Cc: Eric Dorland <eric@debian.org>
- Subject: release.debian.org: Regression: Recent upgrade of opensc breaks Yubikey NEO support
- From: Hilko Bengen <bengen@debian.org>
- Date: Tue, 13 Nov 2018 22:54:28 +0100
- Message-id: <87r2fomynf.fsf@msgid.hilluzination.de>
Package: release.debian.org
Severity: grave
Tags: stretch
A few weeks ago I reported that a security patch in
opensc/0.16.0-3+deb9u1 broke support for Yubkey NEO devices (#910786,
severity serious). Unfortunately, this did not prevent opensc from being
included in the recent stretch point release. What can we do to fix the
package now?
Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
- To: Hilko Bengen <bengen@debian.org>, 913674-done@bugs.debian.org
- Cc: Eric Dorland <eric@debian.org>
- Subject: Re: Bug#913674: Preparing p-u upload
- From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Date: Thu, 02 Jul 2020 21:01:00 +0100
- Message-id: <610b56fda617de0e2949a3300597c340a9e9cfcf.camel@adam-barratt.org.uk>
- In-reply-to: <8736q2kbzs.fsf@msgid.hilluzination.de>
- References: <87d0p8s6hn.fsf@msgid.hilluzination.de> <1546886720.2823.15.camel@adam-barratt.org.uk> <87r2fomynf.fsf@msgid.hilluzination.de> <877efgs1wd.fsf@msgid.hilluzination.de> <1546979342.2823.19.camel@adam-barratt.org.uk> <87r2fomynf.fsf@msgid.hilluzination.de> <8736q2kbzs.fsf@msgid.hilluzination.de>
On Tue, 2019-01-08 at 23:42 +0100, Hilko Bengen wrote:
> * Adam D. Barratt:
>
> > Ah, I suspect there has been some confusion regarding the quoted
> > text -
> > "that" is "a fixed package", not "the package in unstable". The
> > mention
> > of unstable was a general reference to the workflow requirement for
> > issues to be resolved in unstable first, not a specific suggestion
> > to
> > upload the unstable package to stable.
>
> Ah, I see.
>
> I think I stated my case about not being able to properly fix the
> patch
> within the 0.16 codebase, so I'm going to open a p-u bug for
> 0.19.1~deb9u1.
That became #918744, which has since been closed (without updating the
package, admittedly, but that's no reason for this bug to remain open).
Regards,
Adam
--- End Message ---