BUG: aspell-dict-es fails on extract

[yves@…]

---> Extracting aspell-es-0.50-2.tar.bz2 DEBUG: setting option extract.args to /usr/local/var/db/dports/distfiles/textproc/aspell-es-0.50 -2.tar.bz2 DEBUG: Assembled command: 'cd "/Users/Shared/src/darwinports/dports/textproc/aspell-dict-es/ work" && /usr/local/bin/bzip2 -dc /usr/local/var/db/dports/distfiles/textproc/aspell-es-0.50 -2.tar.bz2 | tar -xf -' tar: aspell-es-0.50-2/espa\361ol.alias: ne peut open: (null) tar: Statut d'erreur report'e d'erreurs pr'ec'edentes. Error: Target com.apple.extract returned: shell command "cd "/Users/Shared/src/darwinports/dports/ textproc/aspell-dict-es/work" && /usr/local/bin/bzip2 -dc /usr/local/var/db/dports/distfiles/ textproc/aspell-es-0.50-2.tar.bz2 | tar -xf -" returned error 2 Command output: tar: aspell-es-0.50-2/espa\361ol.alias: ne peut open: (null) tar: Statut d'erreur report'e d'erreurs pr'ec'edentes.

[jmpp@…]

You're probably more fit than any of us to tell what's going on here because you obviously have some customized version of tar installed, since as far as I've seen the default one does not output error messages in French! All I could make out from the error message is that your tar is having problems opening the (uncompressed?) archive. Have you checked if the download was really successful? Do you have a valid tarball in your download are? (I would think the option of a faulty download is ruled out if the checkusming was successful, but I'd check just to make sure). Can you at least translate the error message to us?

-jmpp

[yves@…]

very straight tar

Bilbo:~ root# which tar /usr/bin/tar

it is just that I have LANG=fr environment set.

The checksums do pass well

---> Verifying checksum(s) for aspell-dict-es DEBUG: Executing com.apple.checksum (aspell-dict-es) ---> Checksumming aspell-es-0.50-2.tar.bz2 DEBUG: Correct (md5) checksum for aspell-es-0.50-2.tar.bz2

Here is the output in english :

DEBUG: setting option extract.cmd to /opt/local/bin/bzip2 ---> Extracting aspell-dict-es DEBUG: Executing com.apple.extract (aspell-dict-es) ---> Extracting aspell-es-0.50-2.tar.bz2 DEBUG: setting option extract.args to /opt/local/var/db/dports/distfiles/textproc/aspell-es-0.50 -2.tar.bz2 DEBUG: Assembled command: 'cd "/Volumes/MacOSX/Users/Shared/src/darwinports/dports/textproc/ aspell-dict-es/work" && /opt/local/bin/bzip2 -dc /opt/local/var/db/dports/distfiles/textproc/asp ell-es-0.50-2.tar.bz2 | tar -xf -' tar: aspell-es-0.50-2/espa\361ol.alias: Cannot open: (null) tar: Error exit delayed from previous errors Error: Target com.apple.extract returned: shell command "cd "/Volumes/MacOSX/Users/Shared/src/ darwinports/dports/textproc/aspell-dict-es/work" && /opt/local/bin/bzip2 -dc /opt/local/var/db /dports/distfiles/textproc/aspell-es-0.50-2.tar.bz2 | tar -xf -" returned error 2 Command output: tar: aspell-es-0.50-2/espa\361ol.alias: Cannot open: (null) tar: Error exit delayed from previous errors

I also tried with /usr/bin/bzip2 just in case and the results are exactly the same.

This is in OpenDarwin 7.2.1 and I get the same thing in MacOSX 10.3.8, and Stuffit Expander also complains.

My best guess is that espa\361ol.alias gets its name messed up in the process.

[jmpp@…]

Hi Yves! First off, news to me that tar outputs errors in the language contained in the LANG env variable, nice!

Anyhow, I reproduced the error and realized what's going on, even though I don't have a solution for it. Either tar(1) or bzip2(1), most likely the former, is barfing with non ASCII characters:

tar: aspell-es-0.50-2/espa\361ol.alias: ne peut open: (null)

That file should read "español.alias" but apparently tar is not being able to process it, I'm not too sure why. Hence it bails out. I don't remember if I've extracted files with non ASCII characters in their names with tar before, but I am most intrigued as to why Stuffit Expander is failing as well (error I also reproduced), it should handle non ASCII characters just fine, but then again I can't remember if I've extracted them before either.

I read through tar's and bzip2's man pages but I couldn't find anything with respect to UTF-8, non ASCII, etc, so I don't have a solution yet. I am assigning this bug to the base/ component, at least temporarily because I'm not too sure if tar is at fault or the archive itself, and myself as owner. when I perform further tests I'll update it. I'm gonna play with some non-ASCII archives.

In the mean time, tough luck with aspell-dict-es ;-)

-jmpp

[snu@…]

Please use summary prefix.

[jmpp@…]

I never came up a solution for this problem, so I'm reassigning this bug to the port maintaner, smile Jim! ;-)

At first I thought it was a problem with base/ not handling non ASCII characters in tarballs properly, but I was proved wrong of this. Now I just think the tarball itself is faulty. Jim, can you please look into this? I can confirm the bug still exists, at least... :-P

-jmpp

[markd@…]

* Bug 8500 has been marked as a duplicate of this bug. *

[markd@…]

The problem still exists. No updated tarballs have been released.

[pipping@…]

problem persists with

• gnutar 1.16.1
• star 1.5a77

[ryandesign (Ryan Carsten Schmidt)]

I can confirm the issue still exists. I also see that aspell6-es-1.9a-1.tar.bz2 has been released; maybe that's better.

Jim gave up ownership of this port in r23764.

[ryandesign (Ryan Carsten Schmidt)]

1.9a seems to install just fine so I updated to that version in r36583.

[(none)]

Milestone Port Bugs deleted