Summary: | [~x86] Can't emerge portage-2.0.46-r11 - the digest file is missing. | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Phil Richards <news> |
Component: | Unclassified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | CC: | amills, timhaughton |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Self created digest file
Self created digest file |
Description
Phil Richards
2003-02-07 12:36:20 UTC
Me too.
I am tring a new install (stage1 x86 1.4rc2).
Anything I can do to work around this step?
I ran scripts/bootstrap.sh from /usr/protage
cdimage portage # scripts/bootstrap.sh
Using >=sys-apps/baselayout-1.7.9-r1
Using >=sys-apps/portage-2.0.25
Using >=sys-devel/binutils-2.13.90.0.4
Using >=sys-devel/gcc-3.2
Using sys-devel/gettext
Using >=sys-libs/glibc-2.2.5
Using >=sys-apps/texinfo-4.2-r1
Using sys-libs/zlib
Using >=sys-libs/ncurses-5.2.20020112a
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-apps/portage-2.0.46-r11 to /
!!! No message digest file found: /usr/portage/sys-apps/portage/files/digest-portage-2.0.46-r11
!!! Type "ebuild foo.ebuild digest" to generate a digest.
Created attachment 8015 [details]
Self created digest file
Use at your own risk. I have now way of knowing if this is the correct digest.
I am not affilated with Gentoo in anyway.
Created attachment 8016 [details]
Self created digest file
Use at your own risk. I have now way of knowing if this is the correct digest.
I am not affilated with Gentoo in anyway.
no, do not use -r11 please emerge sync again, and downgrade to -r9 |