When emerges tries to untar the following error occurs: >>> emerge (1 of 1) app-admin/realpath-1.9.10 to / >>> Downloading http://gentoo.osuosl.org/distfiles/dwww_1.9.10.tar.gz ######################################################################## 100.0% >>> md5 src_uri ;-) dwww_1.9.10.tar.gz >>> Unpacking source... >>> Unpacking dwww_1.9.10.tar.gz to /var/tmp/portage/realpath-1.9.10/work tar: dwww-1.9.10/dwww: Cannot open: (null) tar: Error exit delayed from previous errors I believe the reason is that the file is called Dwww and not dwww, some HPFS case problem. Reproducible: Always Steps to Reproduce: 1. emerge it
Does your keyword set include ppc-macos? Please include the output of `emerge --info`. You are correct in that the issue does have to do with HPSF not being case-sensitive.
s/HPSF/HPFS
yes, I do use the ppc-macos flag. Here's my emerge --info !!! Relying on the shell to locate gcc, this may break !!! DISTCC, installing gcc-config and setting your current gcc !!! profile will fix this Portage 2.0.51-r8 (default-macos-10.3, gcc-3.3, libsystem-7.1-r0, 7.7.0 Power Macintosh) ================================================================= System uname: 7.7.0 Power Macintosh powerpc macos-20040726 Python: dev-lang/python-2.3.3 [2.3 (#1, Sep 13 2003, 00:49:11)] distcc 2.0.1-zeroconf powerpc-apple-darwin7.0 (protocol 1) (default port 3632) [disabled] dev-lang/python: 2.3.3 sys-devel/autoconf: 2.59-r4 sys-devel/automake: 1.8.3 sys-devel/binutils: [Not Present] sys-devel/libtool: 2.4.4 virtual/os-headers: [Not Present] ACCEPT_KEYWORDS="ppc ppc-macos ~ppc-macos" AUTOCLEAN="yes" CFLAGS="-fast -mcpu=7450 -pipe" CHOST="powerpc-apple-darwin" 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/env.d" CXXFLAGS="-fast -mcpu=7450 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache cvs distlocks" GENTOO_MIRRORS="http://gentoo.osuosl.org/" LDFLAGS="" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aac aim altivec ansi aqua atlas auctex ba-completion blas bzlib c++ cdr cdrom cups curl curlwrappers dio dvd emacs extlib faac fftw ftp gif gmp gmtfull gmthigh gmtsuppl gmttria gnustep icq idea imagemagick imlib java jpeg kadu-modules layout-osx-like lzw-tiff macos mcal mime mng mpeg mpeg4 mysql mysqli ncurses nethack nocardbus nocd nojoystick nomultilib nosendmail objc offensive oggvorbis openal opengl pcre pdflib perl plotutils png posix quicktime radeon readline recode samba sbcl silc sockets spell sqlite ssl stencil-buffer svg szip tetex theora tiff truetype type1 usb wifi wmf xml2 xmlrpc xpm zlib"
Out of curiosity, when's the last time you ran `emerge --sync`? This is the kind of error I was seeing before I patched this bug for macos. If you're using an old snapshot of the portage tree, the ppc keyword will allow the package to be emerged without the applied macos patch. Try syncing and emerging again. If you're using an updated tree, it should attempt to pull version 1.9.16. Let me know how it goes.
No, even after syncing and with either ppc or ppc-macos, I always get the same error as above. And yes, it is version 1.9.16.
Here's what happens: When tar untars the distfile, it first creates a folder 'Dwww' then a little later it tries to write a file with name 'dwww' -- on HPFS that's the same name. I guess the fix will be a little more involved, untarring the distfile part by part and changing the all references to one of the two (D/d)www The cleanest would probably be if the realpath maintainers didn't use names that differ only by case.
...except:
...except: »···if use ppc-macos; then »···»···local dirname="dwww-${PV}" »···»···tar xzf ${DISTDIR}/${A} \ »···»···»···${dirname}/Makefile \ »···»···»···${dirname}/realpath.c \ »···»···»···${dirname}/README \ »···»···»···${dirname}/TODO \ »···»···»···${dirname}/BUGS \ »···»···»···${dirname}/man/realpath.1 || die "unpack failed." )>»···else »···»···unpack ${A} »···fi Shouldn't be touching dwww on macos...
I'm not sure what to say here. You have the ppc-macos keyword and yet it's skiping right over the conditional. Maybe the use function is mucked up on your install, but that would cause all sorts of other problems and would fix itself after a sync. I can always repackage the sources but I'd prefer not to deviate from the upstream distribution. We also might contact the maintainer (a Debian rep, I think) and ask that they rename either the file or the directory in future releases. Anyone else have any ideas here?
Conditional is now userland_Darwin. I could never reproduce this anyway....reopen if problem persists after an emerge sync
