stderr: CPAN::Meta::YAML found a duplicate key
'dynamic_config' in line '1' at /usr/share/perl/5.24/CPAN/Meta/YAML.pm line 515.
It looks like CPAN::Meta::YAML has become more strict about
duplicate keys with Perl 5.24.
--
Niko Tyni nt...@debian.org
FAIL stderr: CPAN::Meta::YAML found a duplicate key
'no_index' in line '' at /usr/share/perl/5.24/CPAN/Meta/YAML.pm line 515.
It looks like CPAN::Meta::YAML has become more strict about
duplicate keys with Perl 5.24.
--
Niko Tyni nt...@debian.org
you failed 1 test of 128.
This seems to have regressed with Perl 5.24.1, which
bundles Cwd 3.63_01 while 5.24.0 had 3.63.
--
Niko Tyni nt...@debian.org
On Tue, Sep 27, 2016 at 10:58:40PM +0200, gregor herrmann wrote:
> On Tue, 27 Sep 2016 23:36:35 +0300, Niko Tyni wrote:
>
> > However, any versioned dependencies on these packages must first
> > be changed, at least as long as we don't use versioned Provides (see
> > #7581
you're still supposed to list the module
packages manually. See for instance #81547.
> Also I tried `perl-depends', but it hanged for me. If you are
> interested, I can provide details.
I have never tried perl-depends. You may want to ask its maintainer
and/or file a bug, although #784025 indicates it may be simply broken.
--
Niko Tyni nt...@debian.org
hunting for
versioned dependencies on these uninstallable packages. I'm not sure how
cleanly this could be implemented, and I'm still not sure where to draw
the line for failures.
Filing this to at least track the issue. Thoughts?
--
Niko Tyni nt...@debian.org
>F
.
If you need to depend on something in perl-modules-5.xx that isn't
provided as a virtual package, please declare the dependency on 'perl'
instead. The perl-modules-5.xx packages should be considered internal
implementation details of the perl package that only exist to save
archive space.
--
Niko
.
If you need to depend on something in perl-modules-5.xx that isn't
provided as a virtual package, please declare the dependency on 'perl'
instead. The perl-modules-5.xx packages should be considered internal
implementation details of the perl package that only exist to save
archive space.
--
Niko
On Sun, Sep 25, 2016 at 03:30:45PM -0400, John David Anglin wrote:
> On 2016-09-25, at 4:09 AM, Niko Tyni wrote:
>
> > - building with gcc-5 or at -O0 makes it go away
> > - I've bisected with gcc #pragmas that disabling optimization for just
> > Perl_custom_op_regist
Policy.
--
Niko Tyni nt...@debian.org
partially upgrade
their systems to a combination of a newer perl and an older dh-haskell.
--
Niko Tyni nt...@debian.org
L_REVISION}, $Config{PERL_VERSION}, $Config{PERL_SUBVERSION})'`
debian/rules:8: recipe for target 'regenerated-stamp' failed
make[1]: *** [regenerated-stamp] Error 1
It looks like we only tested rebuilds with 5.24.0 and therefore missed this.
Similar to #825613, the fix is hopefully trivial
(>= 5.23.4) | libio-compress-perl (>= 2.069)
--
Niko Tyni nt...@debian.org
ibgraphics-colornames-perl
libgraphics-colorobject-perl
--
Niko Tyni nt...@debian.org
-144185424.
Upstream 6.5 changelog has this:
- adjust to PL_savestack changes in perl 5.24 (adapted from
the debian patch, which unfortunately gets it wrong).
so it's probably time to try the upstream code which should work on
5.24 nowadays.
--
Niko Tyni nt...@debian.org
On Fri, Sep 23, 2016 at 07:44:13AM -0400, John David Anglin wrote:
> On 2016-09-23, at 2:24 AM, Niko Tyni wrote:
> > On Thu, Sep 22, 2016 at 08:49:42PM -0400, John David Anglin wrote:
> >> Since 5.22.2-4, the ext/XS-APItest/t/customop test fails on hppa and perl
> >>
unless somebody
objects?
FWIW, it looks like Fedora has been offering DBD::mysql linked
against MariaDB for a while already, and upstream seems receptive (see
lib/DBD/mysql/INSTALL.pod).
--
Niko Tyni nt...@debian.org
or if UR is somehow misusing it. Anyway, filing this to at least
track the issue.
--
Niko Tyni nt...@debian.org
f it still builds with gcc5, and possibly
play with different optimization levels.
--
Niko Tyni nt...@debian.org
tag 838394 unreproducible
close 838394
thanks
On Thu, Sep 22, 2016 at 04:32:34PM +0200, gregor herrmann wrote:
> On Thu, 22 Sep 2016 10:59:13 +0200, Julien Cristau wrote:
>
> > On Thu, Sep 22, 2016 at 10:34:29 +0300, Niko Tyni wrote:
> > > @debian-wb-team: could you pleas
On Tue, Sep 20, 2016 at 10:43:39PM +0300, Niko Tyni wrote:
> Package: openbabel
> Version: 2.3.2+dfsg-2.4
> Severity: serious
> Control: block 830200 with -1
>
> This package failed to build on mips and mips64el.
>
> - on mips:
> "c++: internal compiler error: Seg
t; - on mips64el:
> "openbabel-perl.cpp:17073:86: internal compiler error: in
> df_reg_chain_unlink, at df-scan.c:790"
> https://buildd.debian.org/status/fetch.php?pkg=openbabel=mips64el=2.3.2%2Bdfsg-2.4=1474385515
Thanks for noticing. I've filed #838394 (just one for starters
porter boxes to see if these are
reproducible there and to gather data for gcc bug reports.
This blocks the Perl 5.24 transition so workarounds such as temporarily
building with an older compiler may be desirable.
--
Niko Tyni nt...@debian.org
re seems to be that when the integer is bigger than
the range of IPv4 addresses (2^32-1), the address gets treated as an
IPv6 one but the version field doesn't reflect that.
I've forwarded this upstream at
https://rt.cpan.org/Public/Bug/Display.html?id=117995
--
Niko TYni nt...@debian.org
On Sat, Sep 17, 2016 at 01:25:36PM +0300, Niko Tyni wrote:
> Package: libconfig-crontab-perl
> Version: 1.41-1
> Severity: minor
> Tags: upstream
>
> The test suite gets totally skipped for me with the message
> "no crontab available".
> Furthermore, the crontab
Control: forwarded -1 https://github.com/genome/UR/issues/126
Control: tag -1 - unreproducible
On Sat, Aug 20, 2016 at 08:57:40PM +0300, Niko Tyni wrote:
> On Sat, Aug 20, 2016 at 06:38:03PM +0200, gregor herrmann wrote:
> > Control: tag -1 + unreproducible
> >
> > On Sat,
On Fri, Sep 09, 2016 at 11:00:32AM +0300, Niko Tyni wrote:
> Package: libsdl-perl:
> Version: 2.546-2
> User: debian-p...@lists.debian.org
> Usertags: autopkgtest
>
> This package is failing its autopkgtest checks on current sid.
>
> I haven't really found out what's h
t done in upstream Perl yet
(it's currently slated for 5.26).
--
Niko Tyni nt...@debian.org
>From d37e8eaa84e91c03b3f15ab873cc081152dd8b39 Mon Sep 17 00:00:00 2001
From: Niko Tyni <nt...@debian.org>
Date: Sun, 18 Sep 2016 16:23:59 +0300
Subject: [PATCH] Make the build process w
to mark this log-reading test as TODO since this seems a
> bit fragile.
No objections, but let's try the patch first?
--
Niko
>From 96209b5ba3df009a495da31bee8e2540c3365ec5 Mon Sep 17 00:00:00 2001
From: Niko Tyni <nt...@debian.org>
Date: Sat, 17 Sep 2016 21:16:16 +0300
Subject: [PAT
: 1-2
Files=22, Tests=54, 8 wallclock secs ( 0.07 usr 0.01 sys + 4.93 cusr 0.45
csys = 5.46 CPU)
Result: FAIL
--
Niko Tyni nt...@debian.org
On Fri, Sep 09, 2016 at 09:52:23AM +0300, Niko Tyni wrote:
> Package: libgnome2-gconf-perl
> Version: 1.044-6
> User: debian-p...@lists.debian.org
> Usertags: autopkgtest
> X-Debbugs-Cc: terce...@debian.org
>
> This package is failing its autopkgtest runs on ci.debian.net.
&g
us. I
intend to patch it away for now.
--
Niko Tyni nt...@debian.org
m line 307.
--
Niko Tyni nt...@debian.org
emaphore.c
that triggers it; apparently not all optimizations on -O1 have flags of
their own.
Ideally this should be distilled into a smaller test case for
a gcc bug while it's reliably reproducible, but I'm not sure
if I have the time for that myself.
László, thanks for working around it for now. Much ap
packages can get away without an explicit build dependency. Also, some
packages (looks like this includes xemacs21) only need perl-base, which
is Essential:yes so no build dependency is fine.
Apologies for the inconvenience,
--
Niko Tyni nt...@debian.org
On Fri, Sep 16, 2016 at 12:56:37PM +0300, Niko Tyni wrote:
> I haven't found the exact optimization that's triggering it yet,
At -O1 it goes away with -fno-inline-functions-called-once .
> and I haven't looked at the code GCC generates.
Diffstat for timer.s between -O1 and "-O1
ation that's triggering it yet,
and I haven't looked at the code GCC generates.
--
Niko Tyni nt...@debian.org
You planned 1 tests but ran 0.
[...]
Files=32, Tests=0, 1 wallclock secs ( 0.08 usr 0.04 sys + 0.56 cusr 0.17
csys = 0.85 CPU)
Result: FAIL
Failed 32/32 test programs. 0/0 subtests failed.
Makefile:993: recipe for target 'test_dynamic' failed
make[5]: *** [test_dynamic] Error 255
--
Niko Tyni nt...@debian.org
perl dlopens Embperl.so without Apache, the ap_* functions
aren't needed but still get loaded (unsuccessfully).
I think the fix/workaround for this is explicitly opting out of bindnow
with something like
export DEB_BUILD_MAINT_OPTIONS=hardening=-bindnow
in debian/rules, and possibly a wishlist bug upstre
On Fri, Sep 09, 2016 at 10:19:14AM +0300, Niko Tyni wrote:
> Package: libnet-easytcp-perl
> Version: 0.26-3
> User: debian-p...@lists.debian.org
> Usertags: autopkgtest perl-cwd-inc-removal
>
> This package is failing its autopkgtest checks on current sid.
>
> This regr
for the rationale.
t/core_audiospec.t .. skipped: (no reason given)
[...]
t/core_audiospec.t(Wstat: 0 Tests: 10 Failed: 0)
Parse errors: Bad plan. You planned 0 tests but ran 10.
--
Niko Tyni nt...@debian.org
- podname=t/test.pod
# Failed test 'podname=t/test.pod'
# at t/Search.t line 38.
# got:
'/tmp/autopkgtest-virt-lxc.shared.wmugwu80/downtmp/autopkgtest_tmp/smokev8NcAt/t/test.pod'
# expected: 't/test.pod'
--
Niko Tyni nt...@debian.org
/5.22
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at t/01defaults.t
line 18.
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run
--
Niko Tyni nt...@debian.org
-linux-gnu/perl-base) at t/23graph.t
line 20.
# Looks like your test exited with 2 before it could output anything.
Dubious, test returned 2 (wstat 512, 0x200)
Failed 226/226 subtests
--
Niko Tyni nt...@debian.org
.
# Test::More::subtest('ht_test at t/500-all.t, line 11',
'CODE(0x2822008)') called at
/tmp/autopkgtest-virt-lxc.shared.hcgg07kt/downtmp/autopkgtest_tmp/smokeJfJ20Y/t/lib/Test/HT.pm
line 145
# expect : (?^s:500 Internal Server Error.+at t.lib.Test.HT.pm)
--
Niko Tyni nt
( 0.06 usr 0.02 sys + 0.27 cusr
0.02 csys = 0.37 CPU)
Result: FAIL
--
Niko Tyni nt...@debian.org
led: 1)
Failed test: 19
Non-zero exit status: 1
--
Niko Tyni nt...@debian.org
/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base).
# BEGIN failed--compilation aborted.
not ok 1 - /usr/bin/perl -w -M"EasyTCP" -e 1 2>&1 exited successfully
not ok 2 - /usr/bin/perl -w -M"EasyTCP" -e 1 2>&1 produced no output
--
Niko Tyni nt...@debian.org
to / or something like that in use.t to
prevent similar false positives occurring in the future.
--
Niko Tyni nt...@debian.org
ith 25 just after 25.
--
Niko Tyni nt...@debian.org
at:
# $got->[22] = 'fid_fileinfo 1 [ t/test01.p 1 2 0 0 ]'
# $expected->[22] = 'fid_fileinfo 1 [ test01.p 1 2 0 0 ]'
--
Niko Tyni nt...@debian.org
om /usr/share/pkg-perl-autopkgtest/build-deps.d/smoke
TEMP=${ADTTMP:-${TMPDIR:-/tmp}}
TDIR=$(mktemp -d $TEMP/smokeXX)
So is ADTTMP now significantly longer than before?
--
Niko Tyni nt...@debian.org
=#'
Syntax error: spurious char at command end: '=#'. Did you forget double
quotes ?
# Looks like you planned 8 tests but ran 4.
# Looks like your test exited with 2 just after 4.
Dubious, test returned 2 (wstat 512, 0x200)
Failed 4/8 subtests
--
Niko Tyni nt...@debian.org
onfig does not blow up with "Required plugin inc::MyMetadata
isn't installed."'
# at t/tester-local-plugins.t line 36.
# got: 'Required plugin inc::MyMetadata isn't installed.
--
Niko Tyni nt...@debian.org
-gnu/perl-base) at t/01_comment.t
line 6.
Dubious, test returned 2 (wstat 512, 0x200)
--
Niko Tyni nt...@debian.org
your test exited with 2 before it could output anything.
--
Niko Tyni nt...@debian.org
contains something like
| | +-> test::square(1) from test::wrap_square() at
/home/niko/tmp/libcarp-datum-perl-0.1.3/t/test.pl:41
[/home/niko/tmp/libcarp-datum-perl-0.1.3/t/test.pl:31]
but the test is matching for 'at t/test.pl', i.e. without the absolute path.
--
Niko Tyni nt...@debian.org
/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at t/foo.t line 8.
1..6
Dubious, test returned 2 (wstat 512, 0x200)
Failed 6/6 subtests
--
Niko Tyni nt...@debian.org
Package: libextutils-parsexs-perl
Version: 3.30-2
User: debian-p...@lists.debian.org
Usertags: autopkgtest perl-cwd-inc-removal
This package is failing its autopkgtest checks on current sid.
Looks like it regressed with perl 5.22.2-4, which
removed cwd from @INC.
t/001-basic.t
close 832936 5.24.1~rc3-1
found 832936 5.22.2-5
tag 832936 + jessie wheezy
thanks
On Fri, Jul 29, 2016 at 09:24:22PM +0300, Niko Tyni wrote:
> Package: perl
> Version: 5.22.2-3
> Control: found -1 5.20.2-3+deb8u6
>
> With the CVE-2016-1238 patch that made base.pm temporarily re
Version: 5.24.1~rc3-1
On Mon, Jul 25, 2016 at 04:39:16PM +0100, Dominic Hargreaves wrote:
> Source: perl
> Version: 5.24.0-1
> Severity: critical
>
> As a reminder, fixes equivalent to those applied to jessie and sid today
> should also be applied to experimental.
Done in 5.24.1~rc3-1, but I
Control: tag -1 patch
On Sun, Sep 04, 2016 at 11:17:50AM +0300, Niko Tyni wrote:
> However, while building with --add-depends=sbuild fixes (most?) of
> the gnupg issues, we also have new failures - probably related to perl
> removing cwd from @INC in 5.22.2-4 (which happened after the
On Sat, Sep 03, 2016 at 09:18:49PM +0300, Niko Tyni wrote:
> Control: found -1 4.2.13-1
>
> > request-tracker4 (4.2.13-1) unstable; urgency=medium
> >* Fix FTBFS with gpg 2.1 by no longer explicitly configuring the
> > path to gpg (Closes: #835536)
>
> Th
were run but no plan was declared and done_testing() was not seen.
t/mail/gnupg-bad.t . skipped: gpg
executable is required.
Maybe it's just missing a build dependency on gnupg?
--
Niko Tyni nt...@debian.org
On Sun, Aug 21, 2016 at 10:56:20PM +0300, Niko Tyni wrote:
> On Fri, Aug 19, 2016 at 01:37:36PM +0200, Jakub Wilk wrote:
> >
> > * Niko Tyni <nt...@debian.org>, 2016-08-19, 09:42:
> > > This package depends and/or build-depends on libdata-alias-perl, which
> >
t one.
The intention is not to push dpkg-buildflags contents to $Config{ccflags},
so that packages can opt in or out of their usage independently. (Normally
they get dpkg-buildflags via debhelper anyway.) So apparently there's
something wrong with filtering dpkg-buildflags from %Config.
erhaps (<< 2.86~) though I'm not sure where that would matter, to make
sure installing an earlier separately packaged version will not override
the fixes in the core version.
--
Niko Tyni nt...@debian.org
Control: found -1 5.24.0-1
On Mon, Aug 29, 2016 at 11:44:02PM +0300, Niko Tyni wrote:
> - ExtUtils::MakeMaker has a problem in non-UTF8 locales where it can
> write UTF8 metadata from for instance META.yml into Makefile through an
> ASCII-only file handle, causing the "&
0x004b69a6 in Perl_runops_standard (my_perl=0x7d3010) at run.c:41
#12 0x0044409d in S_run_body (oldscope=,
my_perl=) at perl.c:2453
#13 perl_run (my_perl=0x7d3010) at perl.c:2381
#14 0x0041cb6b in main (argc=5, argv=0x7fffe8d8,
env=0x7fffe908) at perlmain.c:116
--
Niko Tyni nt...@debian.org
for testing/unstable.
(Not sure if this should be 'serious', feel free to bump as you see fit.)
--
Niko Tyni nt...@debian.org
ackaged due to an RFP, so presumably
there's at least some need for it.
That said, I think kicking these out of testing for now and going ahead
with the transition would be totally appropriate if you don't want
to do NMUs. Hopefully somebody who cares can then fix them.
--
Niko Tyni nt...@debian.org
m would be much better than doing so against their
wish, particularly as this would create a functionality difference.
The embedded libyaml is not a regression (see #664224) and not a release
critical issue as far as I am aware. The lintian tag is overriddable.
So I suggest we override the lintian error in order to fix this RC bug.
--
Niko Tyni nt...@debian.org
is seems particularly topical:
https://rt.perl.org/Public/Bug/Display.html?id=116110#txn-1180016
--
Niko Tyni nt...@debian.org
On Fri, Aug 19, 2016 at 01:37:36PM +0200, Jakub Wilk wrote:
>
> * Niko Tyni <nt...@debian.org>, 2016-08-19, 09:42:
> > This package depends and/or build-depends on libdata-alias-perl, which
> > breaks with Perl 5.24 (currently in experimental.)
>
> This depend
On Sun, Aug 21, 2016 at 05:13:51PM +0300, Niko Tyni wrote:
> On Sun, Aug 21, 2016 at 03:13:23PM +0200, gregor herrmann wrote:
> > On Sun, 21 Aug 2016 15:27:34 +0300, Niko Tyni wrote:
>
> > "\x{00c2}" does not map to ascii at
> > /usr/share/perl/5.22/ExtUtils/Ma
On Sun, Aug 21, 2016 at 03:13:23PM +0200, gregor herrmann wrote:
> On Sun, 21 Aug 2016 15:27:34 +0300, Niko Tyni wrote:
> "\x{00c2}" does not map to ascii at
> /usr/share/perl/5.22/ExtUtils/MakeMaker.pm line 1187.
> "\x{00a1}" does not map to ascii at
keMaker.pm line 1187.
"\x{00d0}" does not map to ascii at
/usr/share/perl/5.22/ExtUtils/MakeMaker.pm line 1187.
panic: sv_setpvn called with negative strlen -1 at
/usr/share/perl/5.22/ExtUtils/MakeMaker.pm line 1187.
Close with partial character at /usr/share/perl/5.22/ExtUtils/Ma
On Sat, Aug 20, 2016 at 07:56:56PM +0200, gregor herrmann wrote:
> On Sat, 20 Aug 2016 20:51:51 +0300, Niko Tyni wrote:
>
> > > > flAbsPath on /var/lib/apt/var/lib/dpkg/status failed - realpath (2: No
> > > > such file or directory)
> > > > Co
loop makes it fail every now and
then. Presumably it's a race condition in the test suite.
--
Niko Tyni nt...@debian.org
On Sat, Aug 20, 2016 at 07:27:22PM +0200, gregor herrmann wrote:
> On Sat, 20 Aug 2016 20:14:41 +0300, Niko Tyni wrote:
>
> > > FWIW, the package builds fine for me (amd64 sid cowbuilder).
> >
> > The failures seem to be related to these log entries:
> >
>
l is quite slow in
this case. Setting $SIG{INT} to IGNORE did not happen yet in the child,
so it was unexpectedly killed, and the next write() call caused a
SIGPIPE in the parent
--
Niko Tyni nt...@debian.org
file - open (2: No such file or directory)
Problem opening
The package lists or status file could not be parsed or opened.
which suggests this is #833656.
--
Niko Tyni nt...@debian.org
block 830200 with 834795
block 830200 with 834796
block 830200 with 834797
block 830200 with 834798
block 830200 with 834799
block 830200 with 834800
thanks
On Fri, Aug 19, 2016 at 09:10:09AM +0300, Niko Tyni wrote:
> The freeze for the next Debian release (stretch) is approaching,
> so it
ely on having
a sufficiently recent Perl version, you should prefer to use the
core facility rather than use this module. If you are already
using this module and are now using a sufficiently recent Perl,
you should attempt to migrate to the core facility.
--
N
ely on having
a sufficiently recent Perl version, you should prefer to use the
core facility rather than use this module. If you are already
using this module and are now using a sufficiently recent Perl,
you should attempt to migrate to the core facility.
--
Niko Tyni nt...@debian.org
you can rely on having
a sufficiently recent Perl version, you should prefer to use the
core facility rather than use this module. If you are already
using this module and are now using a sufficiently recent Perl,
you should attempt to migrate to the core facility.
--
N
you can rely on having
a sufficiently recent Perl version, you should prefer to use the
core facility rather than use this module. If you are already
using this module and are now using a sufficiently recent Perl,
you should attempt to migrate to the core facility.
--
N
you can rely on having
a sufficiently recent Perl version, you should prefer to use the
core facility rather than use this module. If you are already
using this module and are now using a sufficiently recent Perl,
you should attempt to migrate to the core facility.
--
N
. If you can rely on having
a sufficiently recent Perl version, you should prefer to use the
core facility rather than use this module. If you are already
using this module and are now using a sufficiently recent Perl,
you should attempt to migrate to the core facility.
On Sun, Jul 03, 2016 at 09:00:53PM +0300, Niko Tyni wrote:
> On Sun, May 22, 2016 at 04:41:50PM +0300, Niko Tyni wrote:
> > Package: libdata-alias-perl
> > Version: 1.20-1
> > Severity: important
> > User: debian-p...@lists.debian.org
> > Usertags: perl-5.24-transi
#
# BODY
# '
# Looks like you failed 1 test of 26.
There's a proposed patch upstream at
https://github.com/genehack/Git-Wrapper/pull/72
--
Niko Tyni nt...@debian.org
g 100% success probability. Thank you for the clarification.
> Please note that I'm not even asking that the .deb package is always
> the same (that would be the goal of the reproducible builds project) I'm
> just saying that package building should not be a lottery.
I'm well aware of the diffe
skips
the failing test. The skip should possibly be extended to cover
autopkgtest setups too.
--
Niko Tyni nt...@debian.org
st with the release
team and/or on the debian-devel list would be appropriate IMHO.
--
Niko Tyni nt...@debian.org
thout
arguments, so your "exit 1" in cr2.sh usage() now makes it fail.
+The interestingness test should not expect any command line arguments.
Hope this helps,
--
Niko Tyni nt...@debian.org
that this was judged necessary. This should probably be advertised more
prominently; we'll have to think about possible ways to do that.
Any breakage of apps bundled with Debian should be reported to our bug
tracking system, and we (the Perl maintainers) will do what we can to
assist in fixing those.
--
Niko Tyni nt...@debian.org
no longer
in effect.
This is from https://rt.perl.org/Public/Bug/Display.html?id=128769
but filing so we don't overlook it.
--
Niko Tyni nt...@debian.org
ho did the NMU.
--
Niko Tyni nt...@debian.org
ly fine here (also amd64, sid cowbuilder chroot).
>
> I also just tried pbuilder with a fresh sid chroot (amd64), again it
> builds with no problems. I'm inclined to call this a one-time rebuilding
> quirk?
Looks like #832831 et al. in javahelper, fixed already.
HTH,
--
Niko Tyni nt...@debian.org
h libmojolicious-perl_7.0+dfsg-1. This changelog
entry is probably relevant:
* Removed support for smart whitespace trimming from all_text and text
methods in Mojo::DOM.
--
Niko Tyni nt...@debian.org
1101 - 1200 of 4637 matches
Mail list logo