Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 586954 - app-text/docbook-xml-dtd-4.4-r2 - replace UTF8 encoded single quotes in the ebuild?
Summary: app-text/docbook-xml-dtd-4.4-r2 - replace UTF8 encoded single quotes in the e...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Prefix
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-24 14:30 UTC by Martin Mokrejš
Modified: 2016-06-24 19:44 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Mokrejš 2016-06-24 14:30:42 UTC
>>> Installing (1 of 1) app-text/docbook-xml-dtd-4.5-r1::gentoo_prefix
Found DocBook XSL stylesheets (xsl) in /scratch/mmokrejs/gentoo/usr/share/sgml/docbook/xsl-stylesheets
DocBook XSL stylesheets (xsl-ns) not found
DocBook XSL stylesheets (xsl-saxon) not found
DocBook XSL stylesheets (xsl-xalan) not found
find: �xml-simple-dtd-*/�: No such file or directory
Comment 1 Mike Gilbert gentoo-dev 2016-06-24 15:23:45 UTC
The error is coming from the ${EPREFIX}/usr/sbin/build-docbook-catalog script.

SIMPLE_DTDS=$(find xml-simple-dtd-*/ -name sdocbook.dtd)

The script does not have any quotes. The quotes are appearing in an error message output by the find command.
Comment 2 Martin Mokrejš 2016-06-24 15:35:13 UTC
Thank you for your analysis, I am slowly realizing Gentoo:Prefix really has a modified repository, I thought the portage tree will be same but is not.

Do you think it is a bug in sys-apps/findutils which should stick to us-ascii chars? I would think so ...
Comment 3 Mike Gilbert gentoo-dev 2016-06-24 15:46:53 UTC
It depends on what locale you have set in the environment.

floppym@naomi tmp % LANG=C find foo -name foo
find: 'foo': No such file or directory

floppym@naomi tmp % LANG=en_US.UTF-8 find foo -name foo
find: ‘foo’: No such file or directory
Comment 4 Martin Mokrejš 2016-06-24 17:14:56 UTC
Hmm, I have:

$ locale
LANG=
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
$

so in both cases I get:

$ LANG=C find foo -name foo
find: ‘foo’: No such file or directory
$ LANG=en_US.UTF-8 find foo -name foo
find: ‘foo’: No such file or directory
$

But I understand it depends on the environment, thank you for reminding me. Does portage sandbox have UTF8 set in its environment settings? I would assume that is the relevant environment here.
Comment 5 Martin Mokrejš 2016-06-24 17:15:32 UTC
Eventually, under root I have:

# locale
LANG=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
#
Comment 6 Mike Gilbert gentoo-dev 2016-06-24 19:44:55 UTC
(In reply to Martin Mokrejš from comment #4)

LC_CTYPE is the relevant setting which you clearly have set to en_US.UTF-8.

portage inherits the environment of whatever process calls it.