Upstream is http://bugs.icu-project.org/trac/ticket/9426 and is in
reviewing state.
** Bug watch added: bugs.icu-project.org/trac/ #9426
http://bugs.icu-project.org/trac/ticket/9426
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That does sound like a bug. if invoked w/o a path it should not assume a
path.
please file a bug upstream http://bugs.icu-project.org/trac/newticket
Also, the 'configure' i was referring to was configure when ICU was built.
but, it's moot.
-s
On Sun, Jul 15, 2012 at 10:33 AM, Massimo Dal
There isn't any configure, I'm invoking pkgdata from the shell. The
./icu-config path comes from some pkgdata default. The same commands
works fine with libicu-4.2.1-3 but fails with libicu-4.4.2-2 and later,
so I assume it is a recent libicu bug.
--
You received this bug notification because
I found this interesting behaviour:
$ pkgdata -v -p bin_mkltfs -m static -q packagelist.txt
# Calling icu-config: ./icu-config --incpkgdatafile
sh: 1: ./icu-config: not found
pkgdata: icu-config: Could not read from icu-config. (fix PATH or use -O option)
required parameter is missing: -O is
The bug is not present in version 2.4.1-3 of the package.
Sorry, the bug is not present in version 4.2.1-3 of the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024009
Title:
pkgdata
How is 'configure' being called, particularly, what prefix? The
./icu-config should actually be a full path to where ICU was installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024009
Title:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024009
Title:
pkgdata calls ./icu-config
To manage notifications about this bug go to:
