From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Manifest issues in the tree
Date: Wed, 16 Jul 2003 20:25:43 -0400 [thread overview]
Message-ID: <200307162025.45442.vapier@gentoo.org> (raw)
In-Reply-To: <3F157446.8000101@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
no corruption, people just dont update their Manifest files ...
i run scripts on the tree every few days that updates them all :p
- -mike
On Wednesday 16 July 2003 11:50, Kumba wrote:
> Dhruba Bandopadhyay wrote:
> > Is there really a keyword in FEATURES called 'manifest'? It is
> > certainly not documented in make.conf. Where is this declared?
>
> It was in portage for a time, during the 2.0.48_preX series of portage.
> It basically cross-checks every file related to that package against
> the manifest. Coupled with the "strict" keyword, it makes portage
> extremely stingy on md5summing files. A single mismatch like I'm
> getting and it will refuse to go any further.
>
> This is why I am wondering if 'manifest' may be buggy, or we have some
> kind of minor corruption plaguing rsync somehow.
>
> --Kumba
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iQIVAwUBPxXtB0FjO5/oN/WBAQLVJBAA3cHWhnv+qjs80hu0wDphFm1jWOw9uqMd
2dYaqROEpj+pRtvrUmtdE3gVb6Rg3NXcP9ilu/M+hG6WwetShvpA292FYsZXF47w
kORwCqVJ3dpt82I7OgsrJxPKTpARptt1t7LRRcw02WYcTPBB5DctKjb9rEkpLV4f
P0GvtUnvQcLLDf+lzu8/wIaXOBGeYcRDpDyNnTW6fP6vmf1BR0j4DkYdeJSxQq1y
4yr80tnMPleCl23Qe1PHXG1Ozq9z273uOoW7L5bvgOa/e+evMdtOYRwa91KYiApQ
ukp3TRCPM4rvMrMIE+J0hkb8b+1d2mJFtSB9IVMTNn1gBVmF0tsE2FujOIfJ3hNk
dLh+na0TnWZDOoY0D7X3/cnkwfuR/zPRWF3d1qQuGnlus+sowHpWdhWCasFs4PiG
T5u067Y0Kk4HreSBfwuPbJDNwhrXZOKm6160sAaiBqZBgyz2d15NO4xfFfAhv5rI
A2E1tgdsY3GcoThhtEjfJ9bzKXPp2Z6GzwqvjfKPcuBqLatIqzD25FYLB1WAaxx7
EXMMFE9pEoBHNzEF7KSiu3oOSkPm2SVaNmRyuumUFwtxjZ1xNmqQSlD8LeR+CCpU
bg7xBhqLdGnfmMJn/PDKwp2I80m5lbd+8Wme+jj+KJr0Fnb+qtNpKDRNgHaZZoqV
jeTBvNpR8AA=
=DF84
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-17 0:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 8:25 [gentoo-dev] Manifest issues in the tree Kumba
2003-07-16 10:00 ` Dhruba Bandopadhyay
2003-07-16 11:50 ` Tavis Ormandy
2003-07-17 9:40 ` Dhruba Bandopadhyay
2003-07-17 8:58 ` Kumba
2003-07-17 9:55 ` Dhruba Bandopadhyay
2003-07-17 22:59 ` Mike Frysinger
2003-07-16 15:50 ` Kumba
2003-07-17 0:25 ` Mike Frysinger [this message]
2003-07-17 2:05 ` Brad Cowan
2003-07-17 6:06 ` Kumba
2003-07-17 21:58 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200307162025.45442.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox