| View previous topic :: View next topic |
| Author |
Message |
craigpratt n00b

Joined: 23 Apr 2008 Posts: 6 Location: portland, or
|
Posted: Mon Apr 28, 2008 6:17 am Post subject: Can't update Portage/coreutils from 2007.0 LiveCD - lzma? |
|
|
Hey all,
So I'm going along installing the 3rd server I've setup from 2007.0 LiveCD and I'm encountering a fresh conundrum.
I do an "emerge --sync", setup my make.conf, and then go about the business of updating Portage (as suggested after the --sync). After dealing with the mktemp/coreutils blockage, I go about updating Portage and run into the following:
| Code: |
(chroot) livecd / # emerge portage
Calculating dependencies... done!
>>> Emerging (1 of 5) sys-apps/coreutils-6.10-r2 to /
* coreutils-6.10-patches-1.3.tar.lzma RMD160 ;-) ... [ ok ]
* coreutils-6.10-patches-1.3.tar.lzma SHA1 ;-) ... [ ok ]
* coreutils-6.10-patches-1.3.tar.lzma SHA256 ;-) ... [ ok ]
* coreutils-6.10-patches-1.3.tar.lzma size ;-) ... [ ok ]
* coreutils-6.10.tar.lzma RMD160 ;-) ... [ ok ]
* coreutils-6.10.tar.lzma SHA1 ;-) ... [ ok ]
* coreutils-6.10.tar.lzma SHA256 ;-) ... [ ok ]
* coreutils-6.10.tar.lzma size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
* checking coreutils-6.10.tar.lzma ;-) ... [ ok ]
* checking coreutils-6.10-patches-1.3.tar.lzma ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking coreutils-6.10.tar.lzma to /var/tmp/portage/sys-apps/coreutils-6.10-r2/work
unpack coreutils-6.10.tar.lzma: file format not recognized. Ignoring.
>>> Unpacking coreutils-6.10-patches-1.3.tar.lzma to /var/tmp/portage/sys-apps/coreutils-6.10-r2/work
unpack coreutils-6.10-patches-1.3.tar.lzma: file format not recognized. Ignoring.
/usr/portage/sys-apps/coreutils/coreutils-6.10-r2.ebuild: line 50: cd: /var/tmp/portage/sys-apps/coreutils-6.10-r2/work/coreutils-6.10: No such file or directory
* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /var/tmp/portage/sys-apps/coreutils-6.10-r2/work/patch
* ( patch )
!!! ERROR: sys-apps/coreutils-6.10-r2 failed.
Call stack:
ebuild.sh, line 1614: Called dyn_unpack
ebuild.sh, line 751: Called qa_call 'src_unpack'
environment, line 3805: Called src_unpack
coreutils-6.10-r2.ebuild, line 53: Called epatch
eutils.eclass, line 181: Called die
!!! Cannot find $EPATCH_SOURCE!
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/sys-apps/coreutils-6.10-r2/temp/build.log'.
|
Same thing happens, of course, if I try to emerge coreutils.
Here's what I've tried:
- 1) Re-merging mktemp and copying /bin/mktemp to /usr/local/bin, then --unmerge-ing it (as suggested in one bug report)
- 2) emerge-ing lzma-utils
- 3) emerge-ing tar
- 4) Unpacking coreutils manually
None of these did the job.
It seems that the issue is that "unpack" requires lzma support. But presumably, this is part of Portage - which is what I'm trying to update. Since the new Portage requires coreutils-6.10 and - apparently - coreutils-6.10 requires the new Portage to unpack, it appears I'm deadlocked.
Any ideas?
Thx,
cp
| Code: |
(chroot) livecd / # emerge --info
Portage 2.1.2.2 (default-linux/x86/2007.0, gcc-4.1.1, glibc-2.5-r0, 2.6.19-gentoo-r5 i686)
=================================================================
System uname: 2.6.19-gentoo-r5 i686 AMD Athlon(tm) 64 Processor 3500+
Gentoo Base System release 1.12.9
Timestamp of tree: Sun, 27 Apr 2008 21:45:01 +0000
app-shells/bash: 3.2_p17-r1
dev-lang/python: 2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
sys-apps/baselayout: 1.12.9
sys-apps/sandbox: 1.2.18.1-r2
sys-devel/autoconf: 2.13, 2.61
sys-devel/automake: 1.5, 1.10.1
sys-devel/binutils: 2.16.1-r3
sys-devel/gcc-config: 1.3.14
sys-devel/libtool: 1.5.22
virtual/os-headers: 2.6.17-r2
ACCEPT_KEYWORDS="x86"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=i686 -pipe -fstack-protector"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo"
CXXFLAGS="-O2 -march=i686 -pipe -fstack-protector"
DISTDIR="/usr/portage/distfiles"
FEATURES="distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.osuosl.org/ http://ftp.ucsb.edu/pub/mirrors/linux/gentoo/"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
USE="acl afs apache2 apm authdaemond berkdb clamav cli cracklib crypt cups doc dovecot-sasl dri examples exif foomaticdb fortran ftp gcrypt gdbm gpm hardened hddtemp ical iconv imap ipv6 isdnlog jpeg ldap maildir midi mime mudflap mysql mysqli ncurses nls nptl nptlonly openmp pam pcap pcre perl php pic png pop3d postfix ppds pppd python readline reflection rrdcgi rrdtool rsync samba sample sasl session smi spamassassin spl ssl syslog tcpd threads tiff tools unicode urandom utils x86 xml xmlreader xmlwriter xorg zip zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i740 i810 imstt mach64 mga neomagic nsc nv r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo"
Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
| [/code] |
|
| Back to top |
|
 |
AllenJB Veteran


Joined: 02 Sep 2005 Posts: 1282 Location: Ashford, Kent
|
Posted: Mon Apr 28, 2008 7:14 am Post subject: |
|
|
The next version down of coreutils doesn't require the lzma functionality, so first upgrade coreutils to the next version down, which is still higher than what the latest portage wants, with: emerge -a ~sys-apps/coreutils-6.9
Now you should be able to upgrade portage with: emerge -a portage _________________ http://gentoo-wiki.com :: http://lug.org.uk :: http://www.linux.org/groups/ :: User Blogs |
|
| Back to top |
|
 |
craigpratt n00b

Joined: 23 Apr 2008 Posts: 6 Location: portland, or
|
Posted: Mon Apr 28, 2008 10:13 am Post subject: |
|
|
Thanks Allen - but still no joy:
Ran:
| Code: | emerge -a ~sys-apps/coreutils-6.9
emerge portage |
And it still tried to update coreutils to 6.10. So at least on my box, it thinks that 6.10 is required for Portage-2.1.4.4 - accd to "emerge portage --pretend".
I even tried a "emerge \<sys-apps/portage-2.1.4.4" - which installed portage-2.1.2.2. But that version apparently doesn't add the lzma support either and it dies in the same spot.
Thx for any suggestions...
cp
Here's another thread on this topic: http://forums.gentoo.org/viewtopic-t-653033-highlight-.html?sid=b581855cfdb11daa10b1d344ca492ad9.
Here's the output from --pretend. Note that coreutils-6.9 is installed and it still wants to upgrade to 6.10:
| Code: |
(chroot) livecd / # emerge portage --pretend
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] sys-apps/coreutils-6.10-r2 [6.9-r1] USE="-vanilla%"
[ebuild N ] app-text/xmlto-0.0.18
[ebuild U ] sys-apps/portage-2.1.4.4 [2.1.1-r2] USE="-epydoc%"
*** Portage will stop merging at this point and reload itself,
then resume the merge.
[ebuild U ] dev-python/pycrypto-2.0.1-r6 [2.0.1-r5]
|
|
|
| Back to top |
|
 |
DawgG Guru


Joined: 17 Sep 2003 Posts: 491
|
Posted: Mon Apr 28, 2008 11:34 am Post subject: |
|
|
does the command work?
if not, have you done a lot of "optimizing" with CFLAGS?
i've had the sam problem, and it was solved compiling lzma-utils with (it's somewhere around this forum; the post you referenced does really NOT solve the problem at hand).
GOOD LUCK. _________________ DUMM KLICKT GUT. |
|
| Back to top |
|
 |
UTgamer Veteran


Joined: 10 Aug 2003 Posts: 1326 Location: Troisdorf (Köln) Deutschland
|
Posted: Mon Apr 28, 2008 1:11 pm Post subject: |
|
|
| DawgG wrote: | does the command work?
if not, have you done a lot of "optimizing" with CFLAGS?
i've had the sam problem, and it was solved compiling lzma-utils with (it's somewhere around this forum; the post you referenced does really NOT solve the problem at hand).
GOOD LUCK. |
DawgG, CFLAGS weren't a problem, you gave a good tip in the other thread linked above, after reinstalling mktemp the new version of "m4" did solve this problem. So do at first reinstall m4 and coreutils can be emerged fine. _________________ AMD Phenom II x4 >> CFLAGS="-march=amdfam10 -O2 -mmmx -msse3 -mfpmath=sse,387 -pipe -ffast-math" is stable and here in use.
Did Intel produce at any time bugfree HW?
http://www.urbanmyth.org/microcode/
http://www.heise.de/newsticker/meldung/91748 |
|
| Back to top |
|
 |
krinn Advocate


Joined: 02 May 2003 Posts: 3178
|
Posted: Mon Apr 28, 2008 2:21 pm Post subject: |
|
|
i solve that problem by
emerge -C mktemp
emerge -1 util-linux
emerge -1 coreutils (it is v 6.11 taken here. emerge take automake-1.10-1 and lzma-utils.4.32.5 as dependencies)
emerge --nodeps bash portage (portage v2.1.5_rc6 in my case, my bash was too old also) |
|
| Back to top |
|
 |
craigpratt n00b

Joined: 23 Apr 2008 Posts: 6 Location: portland, or
|
Posted: Tue Apr 29, 2008 3:25 am Post subject: SOLVED (I think) |
|
|
Thx Krinn for the tips. I couldn't run the steps from top-to-bottom - as coreutils still would not update w/o an updated portage. But I was able to hobble together a solution with "emerge --nodeps portage" that got me going.
Here's what I ran:
| Code: |
emerge -1 util-linux
emerge --nodeps xmlto
emerge --nodeps portage
emerge coreutils
|
And all seems to be well now.
Isn't everyone who does an "emerge portage" from a 2007.0 LiveCD install is going to see this - or is this a matter of a new Stage3 tarball?
Thx to all! |
|
| Back to top |
|
 |
Kuang Eleven n00b

Joined: 18 Nov 2005 Posts: 16
|
Posted: Sun May 04, 2008 12:52 pm Post subject: |
|
|
I can attest that I saw the exact same thing. Excruciatingly annoying, and stuff like this has happened to me a few time with recent ebuilds...
Anyways, I tried all the the above steps, but to no avail.
Emerging portage required coreutils
Emerging portage with nodeps shows the error "failed to make docs"
Emerging coreutils shows the error "Cannot find $EPATCH_SOURCE"
Any help here? The system is pretty much unusable now... |
|
| Back to top |
|
 |
krinn Advocate


Joined: 02 May 2003 Posts: 3178
|
Posted: Mon May 05, 2008 4:55 pm Post subject: |
|
|
| Kuang Eleven wrote: |
Emerging portage with nodeps shows the error "failed to make docs"
|
try
FEATURES="nodoc" emerge -1 --nodeps portage
if you keep having problem open a new thread with the src error show and emerge --info output. |
|
| Back to top |
|
 |
jsosic Guru


Joined: 02 Aug 2004 Posts: 510 Location: Split (Croatia)
|
Posted: Sun May 11, 2008 1:47 am Post subject: |
|
|
Kuang Eleven you have to: | Code: | emerge -1 util-linux
emerge -1 mktemp
emerge -1 m4
emerge -1 xmlto --nodeps
emerge -1 portage --nodeps |
This is a major bug in Gentoo... 2008.0 stable should be out there, so thing like this don't happen. Only stable and official gentoo installer was broken Gentoo is really deteriorating  _________________ I avenge with darkness, the blood is the life
The Order of the Dragon, I feed on human life |
|
| Back to top |
|
 |
hossiken n00b

Joined: 08 Jun 2004 Posts: 10
|
Posted: Sat May 24, 2008 5:04 am Post subject: Ya gentoo is about dead at this point .... im sad |
|
|
| Well I have spent just over a full week of my time trying to get my system up to date. I spent 4 days trying to pull up an old build 2006.1 to the latest sync world deep but ran into this crazy lmza crapola and many other crazy bugs. (It’s a good think I took several images along the way … or I would have put a bullet through my gentoo poster!) I finally gave up (or took a new approach .. as I have images) and blasted the disk and started fresh with a stable 2007.0 build and found the same lzma crapola. I have seen all the slashdots about the core developers abandoning gentoo and leaving just the rookies to run the show but tell now I have not really seen the impact. I hate to say it but at this point gentoo is so broken that the average gentoo user (lets face it: average gentoo user == hard core compared to most) is toast. I have a master gentoo friend that says the only way he can still use gentoo is to have all his popular apps scripted to re-compiled his downloaded and tweaked source code after an emerge sync (Note he has almost no use flags! He just sets CHOST… he compiles everything from his custom scripts) My master gentoo friend also informs me that even with all this custom scripting automation, that he now spends many hours every time he –syncs to fix various stuff. This brings me to my final thought … at what point do you draw the line for “customization/speed/performance”? I guess if we all really wanted full low level control of our systems we could start with writing our own assemblers and kernels…. At what point is it too much trouble to have full control over the system? Where do we draw the line? For me it appears to be having a Fubared box right out of the box. I’m very sad as I have been a gentoo fan for so many years. I always told my peers .. “if you wana know what’s really going on with linux then you need to install gentoo … it’s the only true way to learn”. I’m going to try the 2008.X beta and see if its any better … but if I don’t ever respond to this post then I have abandoned gentoo. It was a great run and I will miss it deeply |
|
| Back to top |
|
 |
desultory Administrator


Joined: 04 Nov 2005 Posts: 6901
|
Posted: Sat May 24, 2008 7:17 am Post subject: |
|
|
| hossiken wrote: | | I spent 4 days trying to pull up an old build 2006.1 to the latest sync world deep but ran into this crazy lmza crapola and many other crazy bugs. | Aside from demonstrating your ability to do so, why start with old stages?
| hossiken wrote: | | (It’s a good think I took several images along the way … or I would have put a bullet through my gentoo poster!) | Keeping backups is a good practice, especially once the system is in use.
| hossiken wrote: | | I finally gave up (or took a new approach .. as I have images) and blasted the disk and started fresh with a stable 2007.0 build and found the same lzma crapola. | Which is not surprising considering when that dependency was introduced.
| hossiken wrote: | | I have a master gentoo friend that says the only way he can still use gentoo is to have all his popular apps scripted to re-compiled his downloaded and tweaked source code after an emerge sync (Note he has almost no use flags! He just sets CHOST… he compiles everything from his custom scripts) My master gentoo friend also informs me that even with all this custom scripting automation, that he now spends many hours every time he –syncs to fix various stuff. | It is quite likely that the scripts and the modifications they make cause more problems than they solve. Start with a recent stage tarball, whether an official release or one released on a more rapid schedule, then try updating the system without using the scripts. Note that more rapid release cycles imply less testing.
| hossiken wrote: | | This brings me to my final thought … at what point do you draw the line for “customization/speed/performance”? I guess if we all really wanted full low level control of our systems we could start with writing our own assemblers and kernels…. | Only if we all were sufficiently versed in such things and had sufficient time and interest to do so.
| hossiken wrote: | | At what point is it too much trouble to have full control over the system? Where do we draw the line? | Such decisions should be made by individual system administrators, or those specifying the software present on a given set of systems. Bear in mind that regardless of which distribution of which operating system, anyone maintaining a system is a system administrator, regardless of their proficiency in doing so. |
|
| Back to top |
|
 |
yngwin Retired Dev


Joined: 19 Dec 2002 Posts: 4174 Location: Suzhou, China
|
Posted: Sat May 24, 2008 9:55 am Post subject: |
|
|
I recommend to always use the most recent stage3 from funtoo.org/linux. I follow my own advice and have never had a problem with these unofficial stage3 tarballs. Instead it saves you a lot of hassle.
Fixed the link, even with tags links are not generated as may be expected when the protocol is not specified. --desultory _________________ "Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF |
|
| Back to top |
|
 |
BiynaYahu n00b

Joined: 11 May 2008 Posts: 40
|
Posted: Mon May 26, 2008 5:25 pm Post subject: |
|
|
Peace Everyone....
| jsosic wrote: | | Code: |
emerge -1 util-linux
emerge -1 mktemp
emerge -1 m4
emerge -1 xmlto --nodeps
emerge -1 portage --nodeps |
|
I still get the error at m4 about $EPATCH_SOURCE doing this... |
|
| Back to top |
|
 |
meyerm Veteran


Joined: 27 Jun 2002 Posts: 1307 Location: Munich / Germany
|
Posted: Sun Aug 24, 2008 2:20 pm Post subject: |
|
|
Hi guys,
I just ran into the same problems when trying to update some old server which is only touched when a security warning tells me so.
After portage no longer wanting to update coreutils and m4 because of the missing lzma-support, and portage itself not beeing able to be updated thanks to the block of a newer bash, I finally solved it by updating portage manually (without dependencies) to 2.1.4.4. This version works with the lzma-stuff.
| Code: | emerge -u --nodeps =sys-apps/portage-2.1.4.4
emerge -u coreutils |
After that I updated portage to the newest version, again without dependencies, followed by a new bash. From there on, everything is "back to normal" again. |
|
| Back to top |
|
 |
wan-geek n00b


Joined: 03 Apr 2003 Posts: 66 Location: knee-deep in the ether
|
Posted: Thu Aug 28, 2008 5:50 pm Post subject: |
|
|
What's bothering me is that I _just_ built a machine 2 days ago with the latest 'current' stage-3 and am running into this problem upon trying to get the system up to date.
-C |
|
| Back to top |
|
 |
|