View previous topic :: View next topic |
Author |
Message |
raptor Apprentice
Joined: 20 Sep 2002 Posts: 171
|
Posted: Thu Jun 27, 2013 2:42 pm Post subject: unable to install Acrobat reader |
|
|
It is telling me that it does not recognize the .TAR files !!! any idea how to fix this?
Quote: |
>>> Emerging (1 of 1) app-text/acroread-9.5.4
* AdbeRdr9.5.4-1_i486linux_enu.tar.bz2 SHA256 SHA512 WHIRLPOOL size ... [ ok ]
>>> Unpacking source...
>>> Unpacking AdbeRdr9.5.4-1_i486linux_enu.tar.bz2 to /var/tmp/portage/app-text/acroread-9.5.4/work
>>> Unpacking ./ILINXR.TAR to /var/tmp/portage/app-text/acroread-9.5.4/work/AdobeReader
unpack ./ILINXR.TAR: file format not recognized. Ignoring.
>>> Unpacking ./COMMON.TAR to /var/tmp/portage/app-text/acroread-9.5.4/work/AdobeReader
unpack ./COMMON.TAR: file format not recognized. Ignoring.
>>> Source unpacked in /var/tmp/portage/app-text/acroread-9.5.4/work
>>> Preparing source in /var/tmp/portage/app-text/acroread-9.5.4/work/AdobeReader ...
rm: cannot remove ‘/var/tmp/portage/app-text/acroread-9.5.4/work/AdobeReader/Adobe/Reader9/bin/UNINSTALL’: No such file or directory
rm: cannot remove ‘/var/tmp/portage/app-text/acroread-9.5.4/work/AdobeReader/Adobe/Reader9/Browser/install_browser_plugin’: No such file or directory
rm: cannot remove ‘/var/tmp/portage/app-text/acroread-9.5.4/work/AdobeReader/Adobe/Reader9/Resource/Support/vnd.*.desktop’: No such file or directory
sed: can't read /var/tmp/portage/app-text/acroread-9.5.4/work/AdobeReader/Adobe/Reader9/bin/*: No such file or directory
* ERROR: app-text/acroread-9.5.4 failed (prepare phase):
* sed configuration settings failed.
*
* Call stack:
* ebuild.sh, line 93: Called src_prepare
* environment, line 2673: Called die
* The specific snippet of code:
* sed -i -e '/Font-config/,+9d' -e "/acrogre.conf/r ${FILESDIR}/gentoo_config" -e //N "${binfile}" || die "sed configuration settings failed.";
*
* If you need support, post the output of `emerge --info '=app-text/acroread-9.5.4'`,
* the complete build log and the output of `emerge -pqv '=app-text/acroread-9.5.4'`.
* The complete build log is located at '/var/tmp/portage/app-text/acroread-9.5.4/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-text/acroread-9.5.4/temp/environment'.
* Working directory: '/var/tmp/portage/app-text/acroread-9.5.4/work/AdobeReader'
* S: '/var/tmp/portage/app-text/acroread-9.5.4/work/AdobeReader'
>>> Failed to emerge app-text/acroread-9.5.4, Log file:
|
|
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10589 Location: Somewhere over Atlanta, Georgia
|
Posted: Thu Jun 27, 2013 3:26 pm Post subject: |
|
|
You appear have messed up permissions on /var/tmp/portage. What's the output of Code: | ls -ld /var/tmp/portage | and what user are you running emerge under?
- John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
raptor Apprentice
Joined: 20 Sep 2002 Posts: 171
|
Posted: Thu Jun 27, 2013 3:28 pm Post subject: |
|
|
John R. Graham wrote: | You appear have messed up permissions on /var/tmp/portage. What's the output of Code: | ~ # ls -ld /var/tmp/portage | and what user are you running emerge under?
- John |
ls -ld /var/tmp/portage
drwxrwxr-x 7 portage portage 200 Jun 27 10:43 /var/tmp/portage
I'm using root to install things |
|
Back to top |
|
|
raptor Apprentice
Joined: 20 Sep 2002 Posts: 171
|
Posted: Thu Jun 27, 2013 3:29 pm Post subject: |
|
|
audiodef wrote: | Are you adamant about getting acroread? There are other PDF readers that are better in any number of ways. I use Zathura with zathura-pdf-poppler, but there are several other good ones. |
I could check that.. but I was looking for acroread cause I wanted to do comparison between win and lin opening pdf's |
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10589 Location: Somewhere over Atlanta, Georgia
|
Posted: Thu Jun 27, 2013 3:31 pm Post subject: |
|
|
Hmm. Well, the ebuild uses app-arch/tar to unpack those files. You might try re-emerging tar:But, if tar doesn't work, lots of things will be broken. Is your system, by chance, horribly out of date?
- John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
TomWij Retired Dev
Joined: 04 Jul 2012 Posts: 1553
|
Posted: Thu Jun 27, 2013 4:14 pm Post subject: |
|
|
This error comes from /usr/lib*/portage/bin/phase-helpers.sh in the unpack() function. It checks the extension and outputs that message if the extension does not match.
__vecho ">>> Unpacking ${x} to ${PWD}"
suffix=${x##*.}
suffix=$(LC_ALL=C tr "[:upper:]" "[:lower:]" <<< "${suffix}")
I think this has to do with the letters being uppercase and the phase helper somehow not able to make them lowercase with the above code; however, the same code is present in unpacker.eclass as well as a preliminary check where it actually does evaluate it properly. There is a subtle difference, the above code uses LC_ALL=C whereas unpacker.eclass does not; the LC_ALL=C causes the above code to fail. You will want to file a bug against sys-apps/portage at https://bugs.gentoo.org to fix that; there's a small chance they are right about this, in which case unpacker.eclass must be fixed to match it and then the actual bug would be in tr which is from sys-apps/coreutils. But well, best to start by making the Portage maintainers aware and have them look into this to determine where the issue might lie. |
|
Back to top |
|
|
|