Summary: | Please stabilize app-crypt/truecrypt-7.1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marko Steinberger <marko.steinberger> |
Component: | [OLD] Keywording and Stabilization | Assignee: | Dane Smith (RETIRED) <c1pher> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | crypto+disabled |
Priority: | Normal | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marko Steinberger
2011-12-12 14:21:24 UTC
You meant bug #381717. Anyway, it's never been marked stable before for any architecture, it seems... app-crypt/truecrypt was stable some years ago and was destabilized due to restrictive license and the fact that upstream deletes source tarballs for previous versions after releasing new versions. With RESTRICT="mirror fetch bindist", a stable version would be broken after release of a new unstable version. This bug should be closed as WONTFIX. This isn't going to happen since upstream doesn't keep old tarballs from past releases around. In fact, I doubt they still provide the 7.1 tarball for downloading. |