| 1 |
On Sun, 18 Jun 2006 04:43:28 -0700 (PDT) |
| 2 |
Andrei Slavoiu <ansla80@×××××.com> wrote: |
| 3 |
|
| 4 |
> Hello, I want to raise a issue with the way that |
| 5 |
> package integrity verification is done by portage. For |
| 6 |
> an example of such an issue see bug 136742. |
| 7 |
> The idea is that portage now checks the Manifest as a |
| 8 |
> whole, not allowing a version of the package to be |
| 9 |
> emerged if any of the files mentioned by the Manifest |
| 10 |
> fail the verification. This makes unstable ebuilds |
| 11 |
> wich change often and have a tendency to break from |
| 12 |
> time to time prevent the emerge of a stable version of |
| 13 |
> the same package. |
| 14 |
> Do you think there is any way to fix this in portage? |
| 15 |
|
| 16 |
This isn't exactly new behavior with FEATURES=strict (which is the |
| 17 |
default setting). |
| 18 |
|
| 19 |
Marius |
| 20 |
|
| 21 |
-- |
| 22 |
Public Key at http://www.genone.de/info/gpg-key.pub |
| 23 |
|
| 24 |
In the beginning, there was nothing. And God said, 'Let there be |
| 25 |
Light.' And there was still nothing, but you could see a bit better. |
Archives