You are not logged in.

#1 2012-03-01 13:37:40

heavytull
Member
Registered: 2012-02-29
Posts: 8

pacman Pathname in pax header can't be converted to current locale

I installed archlinuxppc about 6 months ago and I tried to update it today but I gor the following error:
error: error while reading package /var/cache/pacman/pkg/ca-certificates-2012XXXX-X-any.pkg.tar.xz: Pathname in pax header can't be converted to current locale.
error: failed to commit transaction (invalid or corrupted package)
ca-certificates-2012XXXX-X-any.pkg.tar.xz is invalid or corrupted
Errors occurred, no packages were upgraded.

I searched quite a bit on the internet to solve this issue and found many solutions, but unfortunately no one solved my problem.
Among the suggested solutions are: add en_US.UTF-8 UTF-8 and en_US ISO-8859-1 to locale.gen and rune locale-gen.
I also tried by setting LC_ALL or LC_COLLATE on the fly this way:
# LC_ALL=C pacman -S pacman
The same problem occured

I also cleaned with pacman -Scc but it is the same problem.

Offline

#2 2012-03-01 22:24:01

Allan
Developer
From: Brisbane, AU
Registered: 2007-06-09
Posts: 10,416
Website

Re: pacman Pathname in pax header can't be converted to current locale

Report it to the archlinuxppc people...   they are packaging wrong.

Offline

#3 2012-03-02 13:58:46

kevin89
Arch Linux f@h Team Member
From: Netherlands
Registered: 2007-03-14
Posts: 218

Re: pacman Pathname in pax header can't be converted to current locale

I had the same problem. What worked for me was editing /etc/locale.gen and adding to following:

en_US ISO-8859-1
en_US.UTF-8 UTF-8

After editing, run locale-gen. Do this before you enter setup on your powerpcc (so before issueing /arch/setup).

Offline

#4 2012-03-02 16:16:12

fsckd
Forum Moderator
Registered: 2009-06-15
Posts: 3,565

Re: pacman Pathname in pax header can't be converted to current locale

moderator action: Moving from Pacman & Package Upgrade Issues to Other Architectures.


aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies

Offline

#5 2012-03-02 17:40:09

heavytull
Member
Registered: 2012-02-29
Posts: 8

Re: pacman Pathname in pax header can't be converted to current locale

kevin89 wrote:

I had the same problem. What worked for me was editing /etc/locale.gen and adding to following:

en_US ISO-8859-1
en_US.UTF-8 UTF-8

After editing, run locale-gen. Do this before you enter setup on your powerpcc (so before issueing /arch/setup).

re-read the OP.

Offline

#6 2012-03-02 21:59:59

Allan
Developer
From: Brisbane, AU
Registered: 2007-06-09
Posts: 10,416
Website

Re: pacman Pathname in pax header can't be converted to current locale

The solution is for ArchPPC not to build broken packages.  If they really can not figure out what they are doing wrong, then they can email me and I will tell them...

Offline

#7 2012-03-10 18:53:36

stber321
Member
Registered: 2012-03-10
Posts: 3

Re: pacman Pathname in pax header can't be converted to current locale

Hello this is my first post on these forums!

build ca-certificates from the ABS after regenerating your locales, it works on ARM(the N900 anyways)

Last edited by stber321 (2012-03-10 18:56:45)

Offline

#8 2012-03-10 23:31:28

Allan
Developer
From: Brisbane, AU
Registered: 2007-06-09
Posts: 10,416
Website

Re: pacman Pathname in pax header can't be converted to current locale

Or report it to the people doing that packaging...  they can not fix bugs if no-one tells them.

Offline

#9 2012-03-10 23:36:26

Pierre
Developer
From: Bonn
Registered: 2004-07-05
Posts: 1,950
Website

Re: pacman Pathname in pax header can't be converted to current locale

Also: using devtools prevents such failures and avoids reinventing the wheel.

Offline

Board footer

Powered by FluxBB