From: Kumba <kumba@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Manifest issues in the tree
Date: Wed, 16 Jul 2003 04:25:48 -0400 [thread overview]
Message-ID: <3F150C0C.7030102@gentoo.org> (raw)
Lately, I've been running into an awful lot of manifest issues in the
portage tree. Not just on x86, but sparc and mips too. For those that
may doubt me, add "manifest strict" to FEATURES and see for yourself.
Where these issues are coming from is anyone's guess. Probable suspects
are those devs not using repoman to check ebuilds into the tree, or we
might have some kind of corruption running around on the rsync servers,
or there's some odd bug in portage.
To quote actual evidence, sys-devel/gettext, app-arch/zip,
app-admin/mirrorselect, and app-admin/gentoolkit gave manifest errors.
on x86, gettext-0.12.1 gives this:
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-devel/gettext-0.12.1 to /
>>> md5 files ;-) gettext-0.12.ebuild
>>> md5 files ;-) gettext-0.11.3-r1.ebuild
>>> md5 files ;-) gettext-0.11.1.ebuild
!!! File is corrupt or incomplete. (Digests do not match)
>>> our recorded digest: 3ae8937c9dd834eff566b1291cd0438a
>>> your file's digest: 172a26a4a6ab693018ad4b352c7daf36
!!! File does not exist:
/usr/portage/sys-devel/gettext//gettext-0.12.1.ebuild
on sparc:
>>> emerge (1 of 1) sys-devel/gettext-0.12.1 to /
>>> md5 files ;-) gettext-0.12.ebuild
!!! File is corrupt or incomplete. (Digests do not match)
>>> our recorded digest: f1002900097f883163423147dce6d9d9
>>> your file's digest: b696d10b2ea72a2dc08b55020f8f79d7
!!! File does not exist: /usr/portage/sys-devel/gettext//ChangeLog
(mips gettext is not included as I already re-digested on that machine,
and an rsync takes ~20mins)
Why these two differ on different machines, I'm not exactly sure on.
Below are some other snippets between sparc, x86, and mips.
x86/sparc/mips app-admin/mirrorselect:
Calculating dependencies ...done!
>>> emerge (1 of 1) app-admin/mirrorselect-0.6 to /
>>> md5 files ;-) mirrorselect-0.6.ebuild
>>> md5 files ;-) mirrorselect-0.3.ebuild
!!! File is corrupt or incomplete. (Digests do not match)
>>> our recorded digest: 6d748dbe957886a5ca691637d94ec1b3
>>> your file's digest: 100d61a5fe0f28e65afbcad758984d6a
!!! File does not exist: /usr/portage/app-admin/mirrorselect//ChangeLog
In this case, the error is the exact same on all three machines.
x86 app-arch/zip:
>>> emerge (1 of 1) app-arch/zip-2.3-r2 to /
>>> md5 files ;-) zip-2.3-r1.ebuild
!!! File is corrupt or incomplete. (Digests do not match)
>>> our recorded digest: 3276fb2669785d06bfb6c2cec123521d
>>> your file's digest: f56548176b22628e4a08abadbcbad329
!!! File does not exist: /usr/portage/app-arch/zip//zip-2.3-r2.ebuild
on sparc:
Calculating dependencies ...done!
>>> emerge (1 of 1) app-arch/zip-2.3-r2 to /
>>> md5 files ;-) zip-2.3-r1.ebuild
!!! File is corrupt or incomplete. (Digests do not match)
>>> our recorded digest: 97e7d71520a7e2309f49e5d7f4951a9b
>>> your file's digest: 9d33eb6208ea6babfe81ca1113d7258a
!!! File does not exist: /usr/portage/app-arch/zip//ChangeLog
(masked on mips)
In these cases, two different machines report different md5sums and
apparent errors in the manifest.
I suspect something similar will happen if one tried the same on
gentoolkit, but this mail is long enough already, so I'll exclude it.
I've been running into these issues quite often, and I suspect several
reasons. In some cases, it seems like some people aren't using repoman,
as I'll redigest and commit via repoman, and half an hour later, the
manifest errors are gone after an rsync. In other cases, like where two
different machines report different errors in the manifests, I'm
thinking either corruption on the rsync servers, or a bug in portage
somewheres.
If someone wants to give this a shot, again, add "manifest strict" to
FEATURES, and start emerging updates over the next few days. You're
bound to run into the same issues I'm seeing on multiple machines.
Ideas, thoughts? Or am I just going insane?
--Kumba
--
"Such is oft the course of deeds that move the wheels of the world:
small hands do them because they must, while the eyes of the great are
elsewhere." --Elrond
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-07-16 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 8:25 Kumba [this message]
2003-07-16 10:00 ` [gentoo-dev] Manifest issues in the tree 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
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=3F150C0C.7030102@gentoo.org \
--to=kumba@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