4:35 a.m.
Dear developers,
v0.44 has an annoying bug with the last perl version:
'tempfile' can't be called as a method at
/usr/share/perl5/vendor_perl/Locale/Po4a/Po.pm line 575.
I checked the repository and I know it has been fixed by a contributor.
Since it is quite critical, is it possible to release a new version soon
for users who have an up-to-date system?
Thank you very much for your efforts.
--
François Boulogne.
http://www.sciunto.org
GPG fingerprint: 25F6 C971 4875 A6C1 EDD1 75C8 1AA7 216E 32D5 F22F
4:06 a.m.
New subject: [Po4a-devel] New release
On 2013/7/14 François Boulogne wrote:
Dear developers,
v0.44 has an annoying bug with the last perl version:
'tempfile' can't be called as a method at
/usr/share/perl5/vendor_perl/Locale/Po4a/Po.pm line 575.
I checked the repository and I know it has been fixed by a contributor.
Since it is quite critical, is it possible to release a new version soon
for users who have an up-to-date system?
Hello François,
I will try to make a new release next week.
Denis
4:09 a.m.
New subject: [Po4a-devel] New release
Le 16/07/2013 11:06, D. Barbier a écrit :
On 2013/7/14 François Boulogne wrote:
> Dear developers,
>
> v0.44 has an annoying bug with the last perl version:
> 'tempfile' can't be called as a method at
> /usr/share/perl5/vendor_perl/Locale/Po4a/Po.pm line 575.
>
> I checked the repository and I know it has been fixed by a contributor.
> Since it is quite critical, is it possible to release a new version soon
> for users who have an up-to-date system?
Hello François,
I will try to make a new release next week.
Denis
great! thank you very much.
--
François Boulogne.
http://www.sciunto.org
GPG fingerprint: 25F6 C971 4875 A6C1 EDD1 75C8 1AA7 216E 32D5 F22F
4:56 p.m.
New subject: [Po4a-devel] New release
On 2013/7/16 François Boulogne wrote:
Le 16/07/2013 11:06, D. Barbier a écrit :
> On 2013/7/14 François Boulogne wrote:
>> Dear developers,
>>
>> v0.44 has an annoying bug with the last perl version:
>> 'tempfile' can't be called as a method at
>> /usr/share/perl5/vendor_perl/Locale/Po4a/Po.pm line 575.
>>
>> I checked the repository and I know it has been fixed by a contributor.
>> Since it is quite critical, is it possible to release a new version soon
>> for users who have an up-to-date system?
> Hello François,
>
> I will try to make a new release next week.
>
> Denis
great! thank you very much.
Hello,
It took much longer than expected, sorry about that.
Current SVN looks good to me now, I will make a new release very soon,
unless problems are reported.
Denis
4:22 p.m.
New subject: [Po4a-devel] New release
On 15/08/2013 23:56, D. Barbier wrote:
On 2013/7/16 François Boulogne wrote:
> Le 16/07/2013 11:06, D. Barbier a écrit :
>> On 2013/7/14 François Boulogne wrote:
>>> Dear developers,
>>>
>>> v0.44 has an annoying bug with the last perl version:
>>> 'tempfile' can't be called as a method at
>>> /usr/share/perl5/vendor_perl/Locale/Po4a/Po.pm line 575.
>>>
>>> I checked the repository and I know it has been fixed by a contributor.
>>> Since it is quite critical, is it possible to release a new version soon
>>> for users who have an up-to-date system?
>> Hello François,
>>
>> I will try to make a new release next week.
>>
>> Denis
>
> great! thank you very much.
Hello,
It took much longer than expected, sorry about that.
Current SVN looks good to me now, I will make a new release very soon,
unless problems are reported.
Denis
Good news: Build succeeds
Not so good news: Build test fails.
I tried with:
perl Build.PL \
prefix=/usr \
installdirs=vendor \
destdir=$PKG
./Build -verbose=1 --debug=1
./Build test -verbose=1 --debug=1
./Build install \
--install_path bindoc=/usr/man/man1 \
--install_path libdoc=/usr/man/man3
log of this attempt is attached.
PS I made a tarball of /trunk but named it po4a-0.44, please don't be misled by that.
TIA for any clue,
Didier
4:46 p.m.
New subject: [Po4a-devel] New release
On 2013/8/16 Didier Spaier wrote:
[...]
Good news: Build succeeds
Not so good news: Build test fails.
I tried with:
perl Build.PL \
prefix=/usr \
installdirs=vendor \
destdir=$PKG
./Build -verbose=1 --debug=1
./Build test -verbose=1 --debug=1
./Build install \
--install_path bindoc=/usr/man/man1 \
--install_path libdoc=/usr/man/man3
log of this attempt is attached.
PS I made a tarball of /trunk but named it po4a-0.44, please don't be misled
by that.
TIA for any clue,
Hello Didier,
Thanks, your report is very helpful. My development machine is a
Debian box, and at the moment Perl is at version 5.14 only, so there
may be issues with more recent versions of Perl that I am not aware
of.
If I read your log file right, there are several issues here:
* Your Perl spits out several warnings (not fatal, but annoying). I
just pushed a commit to fix these warnings.
* Sgml tests fail because you use opensp instead of James Clark's
sp. I cannot reproduce your issue when installing opensp.
* Html tests fail because there is no Html.pm module in your
tarball. This is strange, Html.pm is indeed not shipped in tarballs
(it is considered as experimental and not fully supported), but
associated test files should also be absent. Run './Build dist' to
build the tarball, this should solve this issue.
* TeX tests fail. I do not see what happens. Can you please run
cd t && LC_ALL=C perl ../po4a-gettextize -f latex -m data-24/simple.tex
and send output?
Denis
4:41 p.m.
New subject: [Po4a-devel] New release
On 17/08/2013 23:46, D. Barbier wrote:
[...]
If I read your log file right, there are several issues here:
* Your Perl spits out several warnings (not fatal, but annoying). I
just pushed a commit to fix these warnings.
* Sgml tests fail because you use opensp instead of James Clark's
sp. I cannot reproduce your issue when installing opensp.
* Html tests fail because there is no Html.pm module in your
tarball. This is strange, Html.pm is indeed not shipped in tarballs
(it is considered as experimental and not fully supported), but
associated test files should also be absent. Run './Build dist' to
build the tarball, this should solve this issue.
* TeX tests fail. I do not see what happens. Can you please run
cd t && LC_ALL=C perl ../po4a-gettextize -f latex -m data-24/simple.tex
and send output?
Hello Denis,
I downgraded perl, now perl -v now reports:
This is perl 5, version 14, subversion 4 (v5.14.4) built for x86_64-linux-thread-multi
I pulled trunk with following command:
svn checkout svn://anonscm.debian.org/po4a/trunk -> Revision 2733 extracted
output of "cd t && LC_ALL=C perl ../po4a-gettextize -f latex -m
data-24/simple.tex" is:
Can't locate Locale/Po4a/Chooser.pm in @INC (@INC contains: /usr/local/lib64/perl5
/usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl
/usr/lib64/perl5 /usr/share/perl5 .) at ../po4a-gettextize line 165.
BEGIN failed--compilation aborted at ../po4a-gettextize line 165.
That's right, I don't have Locale/Po4a/Chooser.pm in any of these locations. But
how could it be there as po4a is not installed yet?
./Build dist fails (see attached log_Build_dist) as this target implies running the tests,
it seems.
Any way to simply exclude experimental modules and associated test from a tarball (that I
can make myself)?
I couldn't find a way to build sp-1.3.4 (see attached log_pm-1.3.4), I would need help
on that.
Maybe it's a compatibility problem with my gtcc version (4.8.1) or the Makefile needs
a tuning that I'm not able to determine.
Maybe there is a Debian patch that allows building to succeed, but I couldn't find
one. Could you help me to locate one, if any?
Anyway I did run again ./Build -verbose=1 --debug=1 then ./Build test-verbose=1 --debug=1
and output are attached, as Build_log and Build_test_log respectively.
At least Tex tests don't fail anymore (and I don't care for html failing).
Best regards,
Didier
4:48 p.m.
New subject: [Po4a-devel] New release
On 2013/8/19 Didier Spaier wrote:
[...]
output of "cd t && LC_ALL=C perl ../po4a-gettextize -f
latex -m
data-24/simple.tex" is:
Can't locate Locale/Po4a/Chooser.pm in @INC (@INC contains:
/usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
/usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at
../po4a-gettextize line 165.
BEGIN failed--compilation aborted at ../po4a-gettextize line 165.
That's right, I don't have Locale/Po4a/Chooser.pm in any of these locations.
But how could it be there as po4a is not installed yet?
[...]
My bad, should have been
LC_ALL=C PERLLIB=../lib perl ../po4a-gettextize -f latex -m data-24/simple.tex
I will have a look at your other comments, thanks.
Denis
5:33 p.m.
New subject: [Po4a-devel] New release
My bad, should have been
LC_ALL=C PERLLIB=../lib perl ../po4a-gettextize -f latex -m data-24/simple.tex
np (and I could have figured that out myself), output is attached.
I tried with perl-5.14.4 and 5.18.0, same result (but the date of the POT file as it took
me 5 minutes to switch perl versions :-)
Cheers,
Didier
6:25 p.m.
New subject: [Po4a-devel] New release
On 2013/8/19 Didier Spaier wrote:
[...]
./Build dist fails (see attached log_Build_dist) as this target
implies
running the tests, it seems.
Indeed; I see no simple solution.
Any way to simply exclude experimental modules and associated test
from a
tarball (that I can make myself)?
Delete t/22-html.t, or better:
for f in t/*.t; do grep -q $f MANIFEST || rm $f; done
I couldn't find a way to build sp-1.3.4 (see attached
log_pm-1.3.4), I would
need help on that.
Maybe it's a compatibility problem with my gtcc version (4.8.1) or the
Makefile needs a tuning that I'm not able to determine.
Maybe there is a Debian patch that allows building to succeed, but I
couldn't find one. Could you help me to locate one, if any?
You have to edit include/config.h and add
#define SP_HAVE_TYPENAME
around line 12.
Anyway I did run again ./Build -verbose=1 --debug=1 then ./Build
test-verbose=1 --debug=1 and output are attached, as Build_log and
Build_test_log respectively.
At least Tex tests don't fail anymore (and I don't care for html failing).
Denis
5:22 a.m.
New subject: [Po4a-devel] New release
Hello Denis,
[...]
> Any way to simply exclude experimental modules and associated test from a
> tarball (that I can make myself)?
Delete t/22-html.t, or better:
for f in t/*.t; do grep -q $f MANIFEST || rm $f; done
Thanks, I will do that till the new release
> I couldn't find a way to build sp-1.3.4 (see attached
log_pm-1.3.4), I would
> need help on that.
> Maybe it's a compatibility problem with my gtcc version (4.8.1) or the
> Makefile needs a tuning that I'm not able to determine.
> Maybe there is a Debian patch that allows building to succeed, but I
> couldn't find one. Could you help me to locate one, if any?
You have to edit include/config.h and add
#define SP_HAVE_TYPENAME
around line 12.
I did and compilation did go farther but still failed, please see attached log.
I know I'm a bit out of this forum's topic but I really would want to try if
using sp-1.3.4 would solve tests issue for SGML module...
Thanks again,
Didier
5:04 p.m.
New subject: [Po4a-devel] New release
On 2013/8/20 Didier Spaier wrote:
[...]
I did and compilation did go farther but still failed, please see
attached
log.
I know I'm a bit out of this forum's topic but I really would want to try if
using sp-1.3.4 would solve tests issue for SGML module...
Hello,
I have been able to build sp-1.3.4 with the attached patch.
Anyway I am afraid that this won't solve your problem.
Can you please run
cd t && PERLLIB=../lib perl ../po4a-normalize \
-o debug="tag generic refs entities nsgmls" \
-f sgml data-20/test2.sgml > log.out 2>&1
and send the log.out file?
Denis
6:48 a.m.
New subject: [Po4a-devel] New release
On 21/08/2013 00:04, D. Barbier wrote:
I have been able to build sp-1.3.4 with the attached patch.
Anyway I am afraid that this won't solve your problem.
Can you please run
cd t && PERLLIB=../lib perl ../po4a-normalize \
-o debug="tag generic refs entities nsgmls" \
-f sgml data-20/test2.sgml > log.out 2>&1
and send the log.out file?
Hello,
this patch fails on my system because it tries to patch spgrove/GroveBuilder.cxx
which is missing in ftp://ftp.jclark.com/pub/sp/sp-1.3.4.tar.gz
that I used (and if I leave out this part of the parch make fails anyway).
So I figured that instead you applied it against
ftp://ftp.jclark.com/pub/jade/jade-1.2.1.tar.gz, thus downloaded
the source jade package for sid and applied the big patch jade_1.2.1-47.3.diff.
The build went OK, so I replaced slackware-current's binary nsgmls by
the one I just made.
Unfortunately something should be wrong as then running aforementioned
command just gave me attached output log.out.debian (and if I run
./Build test I get similar result).l
Then I reverted to the nsgmls shipped with Slackware and got something
more useful, I hope, see attached log.out.slack.
I hope that helps you investigate further, thanks for your time.
Didier
7:18 a.m.
New subject: [Po4a-devel] New release
On 2013/8/21 Didier Spaier wrote:
On 21/08/2013 00:04, D. Barbier wrote:
>
> I have been able to build sp-1.3.4 with the attached patch.
> Anyway I am afraid that this won't solve your problem.
> Can you please run
> cd t && PERLLIB=../lib perl ../po4a-normalize \
> -o debug="tag generic refs entities nsgmls" \
> -f sgml data-20/test2.sgml > log.out 2>&1
> and send the log.out file?
Hello,
this patch fails on my system because it tries to patch
spgrove/GroveBuilder.cxx
which is missing in ftp://ftp.jclark.com/pub/sp/sp-1.3.4.tar.gz
that I used (and if I leave out this part of the parch make fails anyway).
So I figured that instead you applied it against
ftp://ftp.jclark.com/pub/jade/jade-1.2.1.tar.gz, thus downloaded
the source jade package for sid and applied the big patch
jade_1.2.1-47.3.diff.
The build went OK, so I replaced slackware-current's binary nsgmls by
the one I just made.
Unfortunately something should be wrong as then running aforementioned
command just gave me attached output log.out.debian (and if I run
./Build test I get similar result).l
Hello,
This error message means that nsgmls could not find some DTD file.
You can let it know about the location of your catalogs by setting the
SGML_CATALOG_FILES environment variable.
Then I reverted to the nsgmls shipped with Slackware and got
something
more useful, I hope, see attached log.out.slack.
I hope that helps you investigate further, thanks for your time.
I see nothing wrong with this output :-/
Can you please post files po4a-normalize.po and po4a-normalize.output
which have also been generated?
Denis
10:31 a.m.
New subject: [Po4a-devel] New release
On 21/08/2013 14:18, D. Barbier wrote:
On 2013/8/21 Didier Spaier wrote:
> On 21/08/2013 00:04, D. Barbier wrote:
>>
>> I have been able to build sp-1.3.4 with the attached patch.
>> Anyway I am afraid that this won't solve your problem.
>> Can you please run
>> cd t && PERLLIB=../lib perl ../po4a-normalize \
>> -o debug="tag generic refs entities nsgmls" \
>> -f sgml data-20/test2.sgml > log.out 2>&1
>> and send the log.out file?
>
>
> Hello,
>
> this patch fails on my system because it tries to patch
> spgrove/GroveBuilder.cxx
> which is missing in ftp://ftp.jclark.com/pub/sp/sp-1.3.4.tar.gz
> that I used (and if I leave out this part of the parch make fails anyway).
>
> So I figured that instead you applied it against
> ftp://ftp.jclark.com/pub/jade/jade-1.2.1.tar.gz, thus downloaded
> the source jade package for sid and applied the big patch
> jade_1.2.1-47.3.diff.
> The build went OK, so I replaced slackware-current's binary nsgmls by
> the one I just made.
>
> Unfortunately something should be wrong as then running aforementioned
> command just gave me attached output log.out.debian (and if I run
> ./Build test I get similar result).l
Hello,
This error message means that nsgmls could not find some DTD file.
You can let it know about the location of your catalogs by setting the
SGML_CATALOG_FILES environment variable.
Hello,
Yes, it seems it couldn't find docbook.dtd for DocBook 4.1 as only the most
recent one last (for DocBook V4.5) is shipped in Slackware.
> Then I reverted to the nsgmls shipped with Slackware and got
something
> more useful, I hope, see attached log.out.slack.
>
> I hope that helps you investigate further, thanks for your time.
I see nothing wrong with this output :-/
Can you please post files po4a-normalize.po and po4a-normalize.output
which have also been generated?
These files are attached.
In t/20, the doctype declaration refers to DocBook V4.1
As I have only the DTD for V4.5, could the test fail because of a difference
between the two DTD ?
Didier
10:46 a.m.
New subject: [Po4a-devel] New release
On 2013/8/21 Didier Spaier wrote:
[...]
In t/20, the doctype declaration refers to DocBook V4.1
As I have only the DTD for V4.5, could the test fail because of a difference
between the two DTD ?
Bingo, that's it!
I have the same issue when using DTD v4.5, now let me find a workaround.
Denis
12:30 p.m.
New subject: [Po4a-devel] New release
On 2013/8/21 D. Barbier wrote:
On 2013/8/21 Didier Spaier wrote:
[...]
> In t/20, the doctype declaration refers to DocBook V4.1
>
> As I have only the DTD for V4.5, could the test fail because of a difference
> between the two DTD ?
Bingo, that's it!
I have the same issue when using DTD v4.5, now let me find a workaround.
Should be fixed now in SVN.
Denis
12:59 p.m.
New subject: [Po4a-devel] New release
On 21/08/2013 19:30, D. Barbier wrote:
On 2013/8/21 D. Barbier wrote:
> On 2013/8/21 Didier Spaier wrote:
> [...]
>> In t/20, the doctype declaration refers to DocBook V4.1
>>
>> As I have only the DTD for V4.5, could the test fail because of a difference
>> between the two DTD ?
>
> Bingo, that's it!
> I have the same issue when using DTD v4.5, now let me find a workaround.
Should be fixed now in SVN.
Fix confirmed, huge thanks Denis!
Didier
Here is the log:
bash-4.2$ ./Build test -verbose=1 --debug=1 2>&1|tee
/home/didier/Build_test_2735_log
Starting ACTION_test
Starting ACTION_code
Starting ACTION_config_data
Finished ACTION_config_data
Finished ACTION_code
t/01-classes.t ........ ok
t/02-TransTractors.t .. ok
t/03-addendums.t ...... ok
t/04-charsets.t ....... ok
t/05-config.t ......... ok
t/06-addendums.t ...... ok
t/10-discard-fuzzy.t .. ok
t/11-plural.t ......... ok
t/12-porefs.t ......... ok
t/20-sgml.t ........... ok
t/21-dia.t ............ ok
t/23-man.t ............ ok
t/24-tex.t ............ ok
t/25-xhtml.t .......... ok
t/26-ini.t ............ ok
t/27-xml.t ............ ok
t/28-msguntypot.t ..... ok
t/29-wml.t ............ ok
t/30-asciidoc.t ....... ok
All tests successful.
Files=19, Tests=360, 54 wallclock secs ( 0.20 usr 0.04 sys + 31.64 cusr 4.19 csys =
36.07 CPU)
Result: PASS
Finished ACTION_test
bash-4.2$
3901
days inactive
3939
days old
17 comments
3 participants
participants (3)
-
D. Barbier -
Didier Spaier -
François Boulogne