Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 56651 - Changing GUID error when emerge'ing system with USE="java jikes"
Summary: Changing GUID error when emerge'ing system with USE="java jikes"
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords:
: 53960 55639 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-07-10 22:45 UTC by Shalom Naumann
Modified: 2004-07-14 13:30 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shalom Naumann 2004-07-10 22:45:35 UTC
I was trying to emerge system. First I had a different problem which seems to be quite common with OpenSSL, so I had to emerge perl. Then I tried emerge system again and OpenSSL worked, but when it got up to j2re-1.4.1 (or something, I'm not 100% sure that was the package name), it said "unable to untar. Can't change GUID to group 1000 user 1000, no such file j2re-1.4.1/man/ja". That's from memory, so it might not be the exact error, but I got the idea right, and I'm certain about the man/ja and the unable to untar and the fact that it was trying to chown to the regular users on a non-existent file. I tried USE="-java -jikes" emerge system and it worked (so far).

Reproducible: Didn't try
Steps to Reproduce:
What I did was:
1. Download stage2 for pentium4, untar it, chroot, etc.
2. set the USE flags to include "java jikes"
3. emerge perl to fix known issue.
4. emerge system
Actual Results:  
Came up with error about tar unsuccesfully trying to chown a nonexist file
(man/ja) to the user and group with the IDs 1000.

Expected Results:  
Emerged normally

Portage 2.0.50-r5 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 2.4.22-xfs)
=================================================================
System uname: 2.4.22-xfs i686 Intel(R) Pentium(R) 4 CPU 1300MHz
Gentoo Base System version 1.4.3.13
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=pentium4 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=pentium4 -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alsa apm arts avi berkdb bidi bindist crypt cups directfb emacs encode
fbcon foomaticdb ftp gdbm gif gpm gtk gtk2 icc imlib java jikes jpeg kde libg++
libwww mad mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib
perl png python qt quicktime readline sdl slang spell ssl svga tcpd tidy
truetype usb wxwindows x86 xml2 xmms xv zlib"
Comment 1 Thomas Matthijs (RETIRED) gentoo-dev 2004-07-11 02:29:47 UTC
this is a problem with the gcc/glibc on the stage3(maybe2) tarball of the 2004.1 release, if you upgrade you gcc glibc first
-> emerge glibc gcc --oneshot
it will be able to unpack it without problems and
you can continue to emerge system without problems
Comment 2 Thomas Matthijs (RETIRED) gentoo-dev 2004-07-13 23:48:05 UTC
this is a problem with the gcc/glibc on the stage3(maybe2) tarball of the 2004.1 release, if you upgrade you gcc glibc first
-> emerge glibc gcc --oneshot
it will be able to unpack it without problems and
you can continue to emerge system without problems
Comment 3 Thomas Matthijs (RETIRED) gentoo-dev 2004-07-14 12:48:47 UTC
*** Bug 55639 has been marked as a duplicate of this bug. ***
Comment 4 Thomas Matthijs (RETIRED) gentoo-dev 2004-07-14 13:30:31 UTC
*** Bug 53960 has been marked as a duplicate of this bug. ***