| Summary: | sys-apps/pcsc-lite-1.6.4 && app-crypt/ccid-1.4.0 stable request | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Arfrever Frehtes Taifersar Arahesis (RETIRED) <arfrever> |
| Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | enhancement | CC: | tparys |
| Priority: | High | Keywords: | STABLEREQ |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 341371 | ||
| Bug Blocks: | |||
|
Description
Arfrever Frehtes Taifersar Arahesis (RETIRED)
2010-10-30 14:24:19 UTC
And since Arfrever decided on this, remember that you HAVE to mark stable app-crypt/ccid-1.4.0 as well, or the stable tree will be unusable. Oh and you'll likely break the stabletree nonetheless because of bug #341371. And likely a few more since there is API breakage in this version. Do tell me why are we stabling this right now? It was on my list of scheduled stabilizations. We can wait more time. app-crypt/ccid-1.4.0 breaks my laptop's O2 Micro Oz776. OTOH, my usb-based SCM SCR 331 still works fine. As a followup. It looks like this isn't breakage in app-crypt/ccid, but a change in dev-libs/libusb. Moreso, the Oz776 hardware appears to be nonstandard, and the workaround that made it work in the first place no longer appears to be feasible. So, bummer for me and anyone who has one. But no reason to not stabilize the new version. Just please keep around the old version of ccid, for those of us who have that hardware. (In reply to comment #4) > app-crypt/ccid-1.4.0 breaks my laptop's O2 Micro Oz776. > > OTOH, my usb-based SCM SCR 331 still works fine. > If I see right then sys-apps/pcsc-lite-1.6.6 and app-crypt/ccid-1.4.1-r1 are already marked as stable now in Portage |