Issues with non-ASCII path names in packages
On 29/10/11 10:27, Allan McRae wrote:
On 29/10/11 09:08, Allan McRae wrote:
On 29/10/11 02:23, Pierre Schmitz wrote:
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
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?
The answer is initscripts... makepkg resources /etc/profile after
installing deps to get updated PATH etc. Now this changes the locale.