DSM-G600, DNS-3xx and NSA-220 Hack Forum
Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Announcement
IRC Channel #funplug on irc.freenode.org
#1 2008-10-02 22:00:17
- deeps
- Member
- Registered: 2007-10-21
- Posts: 12
What's wrong with latest portage?
After total crash, I'm re-installing chroot'ed Gentoo, following the Wiki instructions, as I've done before, with no problems.
But now I get this when updating e2fsprogs:
!!! No package digest file found: /usr/portage/sys-devel/bc/files/digest-bc-1.06
.95
!!! Type "ebuild foo.ebuild digest" to generate it.
Changing to /usr/portage/sys-devel/bc and running ebuild bc-1.06.95.ebuild digest solves the problem, but next package will fail due to same problem: no digest file found.
I noticed that running emerge e2fsprogs caused emerge to perform Global Updates. Did it use to do that? I don't remember...
Anyway, if I continue to build digest files to complete e2fsprogs, I wil finally come up with this:
bash-2.05b# USE=unicode emerge links
Calculating dependencies ...done!
>>> emerge (1 of 4) sys-devel/m4-1.4.11 to /
>>> md5 files ;-) m4-1.4.10-r2.ebuild
>>> md5 files ;-) m4-1.4.11.ebuild
>>> md5 files ;-) m4-1.4.10-r1.ebuild
>>> md5 files ;-) m4-1.4.10.ebuild
>>> md5 files ;-) m4-1.4.10-r3.ebuild
>>> md5 files ;-) ChangeLog
>>> md5 files ;-) metadata.xml
>>> md5 files ;-) files/m4-1.4.10-gnulib-vasnprintf.patch
>>> md5 files ;-) files/m4-1.4.10-seek.patch
>>> md5 files ;-) files/digest-m4-1.4.11
>>> md5 src_uri ;-) m4-1.4.11.tar.lzma
>>> Unpacking source...
>>> Unpacking m4-1.4.11.tar.lzma to /var/tmp/portage/m4-1.4.11/work
unpack m4-1.4.11.tar.lzma: file format not recognized. Ignoring.
>>> Source unpacked.
!!! ERROR: sys-devel/m4-1.4.11 failed.
!!! Function econf, Line 488, Exitcode 1
!!! no configure script found
!!! If you need support, post the topmost build error, NOT this status message.
As have other users. Who also have run into the missing digest files.
So... what have changed????
Offline
#2 2008-10-03 11:27:31
Re: What's wrong with latest portage?
Sounds like a bug http://bugs.gentoo.org/show_bug.cgi?id=217860
But about portage, I suggest you to just delete all portage content and redownload portage-latest and unpack it to portage dir. Its faster (and maybe more reliable) than running emerge --sync
• DSM-G600 - NetBSD hdd-boot - 80GB Samsung SP0802N
• NSA-220 - Gentoo armv5tel 20110121 hdd-boot - 2x 2TB WD WD20EADS
Offline
#3 2008-10-03 11:33:29
- deeps
- Member
- Registered: 2007-10-21
- Posts: 12
Re: What's wrong with latest portage?
Tnx for the reply, but been there, done that....(several times).
Right now I'm trying this:
http://www.gentoo.org/proj/en/portage/d … ifest2.xml
and this:
http://readthefuckingmanual.net/error/983/
I'll let know of progress. But as I understand, there's been no recent changes to the portage download from Wiki?
Offline
#4 2008-10-06 00:39:05
- deeps
- Member
- Registered: 2007-10-21
- Posts: 12
Re: What's wrong with latest portage?
Ok...this is what I found out:
The portage, which is (now) linked to on the Gentoo chroot Wiki, is far to new to co-exist with our poor old stage3-ppc.
The stage3-ppc, which the Wiki links to, doesn't support Manifest2 files, nor does it support lzma-utils, for unpacking lzma files, which are in great numbers on the new portage-tree.
So the first emerge command (emerge e2fsprogs) fails both with the missing ebuild files (due to the Manifest problem) and with .lsma packages. Thus leaving the Wiki useless...
Trying to update portage and python in order to handle the new portage-tree, is a very troublesome process, which I haven't succeded yet. Neither by brute force or gentle touch.
So, for the time being, I'm not able to do a gentoo chroot. Which is quite irritating.
One solution would be, if somebody would link me/us and old portage-tree. Or if we could make a newer stage3-ppc working with support for Manifest2 and other newer features, such as lzma-utils. The latter I have tried but with poor results.
And to those with a working Chroot'ed Gentoo: Back-up :-)
Offline
#5 2008-10-06 10:39:44
Re: What's wrong with latest portage?
You can try out new stage3-ppc from ftp://ftp.linux.ee/pub/gentoo/distfiles … .0.tar.bz2 with the latest portage tree or you can try stage3 posted to wiki and check out some old revison of portage tree from http://sources.gentoo.org/viewcvs.py/gentoo-x86/
If you succeed, then you can fix wiki page so it would not be so useless to others 
//edited, because of confusion between portage package and portage tree
Last edited by sala (2008-10-06 22:17:40)
• DSM-G600 - NetBSD hdd-boot - 80GB Samsung SP0802N
• NSA-220 - Gentoo armv5tel 20110121 hdd-boot - 2x 2TB WD WD20EADS
Offline
#6 2008-10-06 21:44:09
- deeps
- Member
- Registered: 2007-10-21
- Posts: 12
Re: What's wrong with latest portage?
Tnx for the reply, but you got it a bit wrong...
Trying out an older revision of portage, is not a solution, since the problem IS the old revision of portage, which is not compatible with the portage-tree, which is nov linked to, via the Wiki.
That portage tree uses the new format of Manifest files, and files compressed with lzma-utils, whish is also not compatible with our version of portage.
So what we need, is and old portage-TREE... Which I accidently haven't been able to find....
Offline
#7 2008-10-06 22:15:33
Re: What's wrong with latest portage?
I did add link for portage tree cvs. I just said it wrong, with portage I did mean portage tree not portage package.
• DSM-G600 - NetBSD hdd-boot - 80GB Samsung SP0802N
• NSA-220 - Gentoo armv5tel 20110121 hdd-boot - 2x 2TB WD WD20EADS
Offline
#8 2008-10-07 07:40:34
- deeps
- Member
- Registered: 2007-10-21
- Posts: 12
Re: What's wrong with latest portage?
Well, I could have tried the link out first :-)
Offline