[gentoo-portage-dev] Manifest verification

2006-06-18 Thread Andrei Slavoiu
Hello, I want to raise a issue with the way that
package integrity verification is done by portage. For
an example of such an issue see bug 136742.
The idea is that portage now checks the Manifest as a
whole, not allowing a version of the package to be
emerged if any of the files mentioned by the Manifest
fail the verification. This makes unstable ebuilds
wich change often and have a tendency to break from
time to time prevent the emerge of a stable version of
the same package.
Do you think there is any way to fix this in portage?

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-- 
gentoo-portage-dev@gentoo.org mailing list



Re: [gentoo-portage-dev] Manifest verification

2006-06-18 Thread Marius Mauch
On Sun, 18 Jun 2006 04:43:28 -0700 (PDT)
Andrei Slavoiu [EMAIL PROTECTED] wrote:

 Hello, I want to raise a issue with the way that
 package integrity verification is done by portage. For
 an example of such an issue see bug 136742.
 The idea is that portage now checks the Manifest as a
 whole, not allowing a version of the package to be
 emerged if any of the files mentioned by the Manifest
 fail the verification. This makes unstable ebuilds
 wich change often and have a tendency to break from
 time to time prevent the emerge of a stable version of
 the same package.
 Do you think there is any way to fix this in portage?

This isn't exactly new behavior with FEATURES=strict (which is the
default setting).

Marius

-- 
Public Key at http://www.genone.de/info/gpg-key.pub

In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.


signature.asc
Description: PGP signature


Re: [gentoo-portage-dev] Manifest verification

2006-06-18 Thread Alec Warner

 Now I get it. So could somebody add a line to
 make.conf.example that says which features are on by
 default? I didn't notice strict was on.

We can't tell you that, FEATURES are stacked, first make.defaults, and
then from your profile setting; aka the default FEATURES are only known
at runtime ;)

Look at your emerge --info output.
-- 
gentoo-portage-dev@gentoo.org mailing list