Summary: | app-crypt/tpm-tools-1.3.8 stable request (to fix underlinking issue) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Christopher Byrne <salah.coronya> |
Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alonbl, mark, zerochaos |
Priority: | Normal | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 372079 |
Description
Christopher Byrne
2014-05-13 04:50:57 UTC
Hi arch, Please stabilize tpm-tools-1.3.8 Thanks! same error for me tpm-tools-1.3.8 compile fine, please stabalize! or atleast confirm... USE='pkcs11' emerge -1 =app-crypt/tpm-tools-1.3.8 pulls unstable deps: The following keyword changes are necessary to proceed: (see "package.accept_keywords" in the portage(5) man page for more details) # required by app-crypt/tpm-tools-1.3.8[pkcs11] # required by =app-crypt/tpm-tools-1.3.8 (argument) =dev-libs/opencryptoki-2.4.3 ~amd64 (In reply to Chema Alonso from comment #3) > USE='pkcs11' emerge -1 =app-crypt/tpm-tools-1.3.8 pulls unstable deps: > > The following keyword changes are necessary to proceed: > (see "package.accept_keywords" in the portage(5) man page for more details) > # required by app-crypt/tpm-tools-1.3.8[pkcs11] > # required by =app-crypt/tpm-tools-1.3.8 (argument) > =dev-libs/opencryptoki-2.4.3 ~amd64 dev-libs/opencryptoki which was never stable upstream, options: 1. remove the pkcs11 use flag. 2. remove stable from app-crypt/tpm-tools (In reply to Alon Bar-Lev from comment #4) > (In reply to Chema Alonso from comment #3) > > USE='pkcs11' emerge -1 =app-crypt/tpm-tools-1.3.8 pulls unstable deps: > > > > The following keyword changes are necessary to proceed: > > (see "package.accept_keywords" in the portage(5) man page for more details) > > # required by app-crypt/tpm-tools-1.3.8[pkcs11] > > # required by =app-crypt/tpm-tools-1.3.8 (argument) > > =dev-libs/opencryptoki-2.4.3 ~amd64 > > dev-libs/opencryptoki which was never stable upstream, options: > > 1. remove the pkcs11 use flag. > > 2. remove stable from app-crypt/tpm-tools 3. stable.use.mask pkcs11 I suggestion option 3 (In reply to Rick Farina (Zero_Chaos) from comment #5) > 3. stable.use.mask pkcs11 > > I suggestion option 3 thanks! but how do I set this to specific package? (In reply to Alon Bar-Lev from comment #6) > (In reply to Rick Farina (Zero_Chaos) from comment #5) > > 3. stable.use.mask pkcs11 > > > > I suggestion option 3 > > thanks! but how do I set this to specific package? profiles/base/package.use.stable.mask It's just like package.use.mask but only applies to stable users. Thanks! I was not aware of this, added: # Alon Bar-Lev <alonbl@gentoo.org> # dev-libs/opencryptoki will not be stabile any time soon (bug#510204) app-crypt/tpm-tools pkcs11 (In reply to Alon Bar-Lev from comment #8) > # Alon Bar-Lev <alonbl@gentoo.org> > # dev-libs/opencryptoki will not be stabile any time soon (bug#510204) > app-crypt/tpm-tools pkcs11 amd64 stable btw, I think you missed to include the date in your entry in profiles/base/package.use.stable.mask x86 stable, closing Recently this became overkill, so, someone please take this out of package.stable.mask again: # Alon Bar-Lev <alonbl@gentoo.org> (21 Jul 2014) # dev-libs/opencryptoki will not be stabile any time soon (bug#510204) app-crypt/tpm-tools pkcs11 If the packages require keywords like ~amd64 to be used on stable, that is enough. Right now, users who use stable are hindered, even if they have keyworded e.g. ~amd64 for this specific package. As a result I cannot build simple-tpm-pk11, because it relies on tpm-tools + pkcs11, and that is impossible until someone takes it out (or if i manually do it for myself.) |