On 29/10/11 09:08, Allan McRae wrote:

On 29/10/11 02:23, Pierre Schmitz wrote:

...

Hi all,

we found some issues with libarchive and some file names when using the C locale. For example try $ bsdtar tf ca-certificates-20111025-1-any.pkg.tar.xz (from testing) The result will be "bsdtar: Pathname in pax header can't be converted to current locale." Fun fact: The package was created using the C locale. Due to this pacman will refuse to install this package when using the C locale which is used e.g. by our build tools.

Has anyone tested whether the package is created correctly using the previous version of libarchive? The previous ca-certificates package has non-ASCII filenames in it too and worked fine, so I would suspect this is an issue with the current libarchive.

Downgrading libarchive is not enough. So maybe not a libarchive issue. And rebuilding the ca-certificates package that is in [core] results in the same issue. So what has changed between the time the package in [core] was built and now to cause this issue? Allan

Am Sat, 29 Oct 2011 21:08:45 +1000 schrieb Allan McRae :

The answer is initscripts... makepkg resources /etc/profile after installing deps to get updated PATH etc. Now this changes the locale. Yay!

Allan

Any workaround known? It holds back the LibreOffice build in staging and probably more. -Andy

On Saturday 29 October 2011 16:23:14 s Radke wrote:

Any workaround known?

It holds back the LibreOffice build in staging and probably more. $ sudo makechrootpkg -c -r /var/tmp/archbuild/$repo-arch/ -I ca- certificates-20110502+nmu1-1-any.pkg.tar.xz $ cd svn-packages/$pkg/trunk $ sudo makechrootpkg -r /var/tmp/archbuild/$repo-arch/

-- Andrea