Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#39598 - [arch-wiki-lite] broken due to incompatible update to arch-wiki-docs

Attached to Project: Community Packages
Opened by Jakub Klinkovský (lahwaacz) - Sunday, 23 March 2014, 08:49 GMT
Last edited by Kyle Keen (keenerd) - Monday, 02 June 2014, 23:59 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Kyle Keen (keenerd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


Recent incompatible update to arch-wiki-docs [1] has broken arch-wiki-lite. arch-wiki-docs now uses the script presented in [2]. The main purpose of the update was to make arch-wiki-docs more "lite", plus I'm working on conversion to man pages format using pandoc, so there would be console browsing. Will this be fine or should I work on fixing arch-wiki-lite?

This task depends upon

Closed by  Kyle Keen (keenerd)
Monday, 02 June 2014, 23:59 GMT
Reason for closing:  Fixed
Additional comments about closing:  arch-wiki-lite-20140321-1
Comment by Kyle Keen (keenerd) - Sunday, 23 March 2014, 14:08 GMT
Just for clairification, arch-wiki-lite is fine but the update script and the wiki-search-html are broken. I can fix up -lite.
Comment by Dan McGee (toofishes) - Saturday, 29 March 2014, 16:10 GMT
I'm not sure if it is fully related to the new script, but the filenames in this new package are crazy for i18n articles. See things like the following- no, these are not escaped, this is what they look like on the filesystem.

Comment by Jakub Klinkovský (lahwaacz) - Saturday, 29 March 2014, 21:04 GMT
I was told by Sergej that I should force ASCII filenames to maintain compatibility with the C locale. I'm working on it, but it will take some time since it will be necessary to handle internal links.
The filenames should be fine with unicode locale, supposedly pacman will even fail to install the package on system with C locale.
Comment by Daniel Micay (thestinger) - Thursday, 01 May 2014, 08:06 GMT
I don't think there's any reason to avoid UTF-8 in file names. It won't really break anything for silly people using the C locale because files are just byte strings with no '/' or '\0'.
Comment by Kyle Keen (keenerd) - Monday, 02 June 2014, 23:56 GMT
thestinger: Pacman can't install packages with non-C-lang filenames inside a C-lang build chroot. There is probably some way around this, but I don't know our build tools well enough.