Bug#1086655: libgeo-libproj-ffi-perl: (autopkg)test failures on armel and armhf
Source: libgeo-libproj-ffi-perl Version: 1.00-2 Severity: serious Justification: broken on 2 release architectures -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 After fixing (by skipping) an autopkgtest problem in this package in the -2 upload, we now see that the prove autopkgtest (i.e. running the upstream testsuite) fails on 2 architectures, namely armel and armhf: https://ci.debian.net/packages/libg/libgeo-libproj-ffi-perl/testing/armel/53943002/ https://ci.debian.net/packages/libg/libgeo-libproj-ffi-perl/testing/armhf/53943157/ This probably means that the packages is broken on those architectures. Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmcm0EJfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgY39BAAmOPm5jHfbRSCC7Bnkm8t5/gmMcnBNQbPWwl/55GNqlVlIu43shCbNfng kylGlc4pxCFx8kA19ongM5h0NDApQ0rV6gTZVCrKCod6m3ycH8UZeq1kZEqgiC4o iW7N1l+wrP/o1PD9bh3AXUb5ZW3SpFVmQKglNf+Tz4HdMq3wXlN80QSuRv63oS4V 7uMRw7qrOKBSdKEe1P7chJGVXAXvKgKCy0LY+RdVfl+0vI8H/b3ayGriDTBVnCsL RJF720Af3V5gkSW/I7nPhOog+ZEOZoy0pzA3KXblruLJw8O7g4f3Sh8GIxnAJeUt uJOAoNFDGB1/1MkXsqX1M2IFOA+1Q+GiyOk+kBSVyaM6I09izkOseMRe3Lnjb4Qj cbDaq35tYiE+YCnl6V6BulK0k6jqLH8cRjAq0BSjghyD1lfoj7+5CJ0mRRefs0sz gg6ZtBdX3GVpKdeB9WwT8DQrJjhpKlCZmKKq6b/PdFQFLQ5mYvEGBCS1hY4rMJSp Ru8Z9JskkGA9ZCBalJqxUI+hZGLWy+WhLQZHil5SV4jNnxoXtUwWRl3fMWSzORC5 bleaoJZdNcrHacrUf0fmzMlxN0wwqRDl8jXNrXC3cprLiGUUWBNQVmFxdi61OE3n E+yLMLH0K5ReB4ypWkaI+n5X40XV6cOEyru7jORhW3l0y1BQc/I= =U1fX -END PGP SIGNATURE-
Bug#1086287: marked as pending in libtime-parsedate-perl
Control: tag -1 pending Hello, Bug #1086287 in libtime-parsedate-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libtime-parsedate-perl/-/commit/2c157d1c4b76f91b6813f62d1115ee2141b73149 Add test dependency on tzdata-legacy. Thanks: Santiago Vila for the bug report. Closes: #1086287 (this message was generated automatically) -- Greetings https://bugs.debian.org/1086287
Bug#1085167: libmemcached-libmemcached-perl: FTBFS on riscv64: t/11-set-get-by-key.t failure
Control: severity -1 important On Tue, 15 Oct 2024 21:08:13 +0300, Niko Tyni wrote: > On Tue, Oct 15, 2024 at 07:57:53PM +0300, Niko Tyni wrote: > > Source: libmemcached-libmemcached-perl > > Version: 1.001801+dfsg-5 > > Severity: serious > > > > This package failed to build on riscv64 with Perl 5.40. > > > > > > https://buildd.debian.org/status/logs.php?pkg=libmemcached-libmemcached-perl&arch=riscv64 > > > > # Failed test at t/11-set-get-by-key.t line 44. > > # got: undef > > # expected: 't/11-set-get-by-key.t test value 1728978154' > > Somewhat surprisingly it builds for me on ricci.debian.org. > > For now I've given it back once more, let's see how it goes. And it built (and passed the autopkgtests). Lowering the severity (or maybe we want to close it?). Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1086281: marked as pending in libclass-date-perl
Control: tag -1 pending Hello, Bug #1086281 in libclass-date-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libclass-date-perl/-/commit/8df5075733eb081fc9ec1bd06680d1ff0bddcc0a Add test dependency on tzdata-legacy for GMT timezone. Thanks: Santiago Vila for the bug report. Closes: #1086281 (this message was generated automatically) -- Greetings https://bugs.debian.org/1086281
Bug#1086224: RC: Argument " " isn't numeric in division (/) at /usr/share/perl5/GD/SecurityImage/Magick.pm
On Tue, 29 Oct 2024 16:08:30 +, Niko Tyni wrote: > This gives a list of thirteen integers on trixie, but > just one undef on sid. > > Is this an intentional API change in ImageMagick 7 that GD::SecurityImage > should adapt to, or possibly a regression on the ImageMagick side? Nice finding. I also have a small info point to add. The first of the 2 (now) failing test looks like this (same for the second in principle): #v+ # cat debian/tests/perlmagick-gd-7.q16 #!/usr/bin/perl # regression test for #1032998 use GD::SecurityImage use_magick => 1; my $image = GD::SecurityImage->new( width=> 200, height => 100, lines=> 4, gd_font => 'Giant', scramble => 1, rndmax => 10, ); $image->random; $image->create( 'normal', 'default', "#403030", "#FF644B" ); print $image->out( force => 'png' ); #v- Now GD::SecurityImage has two backends: GD::SecurityImage:GD has a gd_font property but GD::SecurityImage::Magick only has a font property (which needs an absolute path to a *.ttf file). And you are of course using the ::Magick backend :) (with use_magick => 1). I wonder how this has ever worked; with use_magick gd_font attribute is never used (because it's in GD.pm) -- which amounts to Niko's finding where he used an empty 'font'. If I change your test to #v+ # cat debian/tests/perlmagick-gd-7.q16 #!/usr/bin/perl # regression test for #1032998 use GD::SecurityImage use_magick => 1; my $image = GD::SecurityImage->new( width=> 200, height => 100, lines=> 4, gd_font => 'Giant', font => '/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf', scramble => 1, rndmax => 10, ); $image->random; $image->create( 'normal', 'default', "#403030", "#FF644B" ); print $image->out( force => 'png' ); #v- i.e. I add a 'font' value (and I picked DejaVuSans.ttf randomly as it was installed in the chroot where I built imagemagick; gd_font can be removed), it passes. > > I suppose a depends on fonts is missing: > Please elaborate. Did ImageMagick 7 change something in (default?) font > handling? I couldn't easily find a summary of the changes. My tenatative conclusion so far is: - The test was always incorrect, and passed by chance. - This luck is gone as apparently something changed in imagemagick. > > Moreinformation here: > > https://ci.debian.net/packages/i/imagemagick/testing/amd64/53694127/ > Printing the generated image to the terminal at the end of your > autopkgtest check seems useless and clutters the log BTW. Also my terminal :) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1085475: marked as pending in sqitch
Control: tag -1 pending Hello, Bug #1085475 in sqitch reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/sqitch/-/commit/ef0201fc7c9f87598567d80f8ead05b9dbb91c00 autopkgtests: skip t/sqlite.t which is flaky on ci.debian.net. Closes: #1085475 (this message was generated automatically) -- Greetings https://bugs.debian.org/1085475
Bug#1085309: latex2html: autopkgtest regression with Perl 5.40: 318s Possible precedence issue with control flow operator
Control: tag -1 + confirmed Control: tag -1 + patch On Fri, 18 Oct 2024 08:55:27 +0300, Niko Tyni wrote: > This package fails its autopkgtest checks with Perl 5.40 (currently > in unstable.) > > It looks like pstoimg started warning and stderr output causes > a test failure. > > https://ci.debian.net/packages/l/latex2html/testing/amd64/ > > 319s autopkgtest [00:13:05]: test command1: - - - - - - - - - - results - > - - - - - - - - - > 319s command1 FAIL stderr: Possible precedence issue with > control flow operator (exit) at /usr/bin/pstoimg line 874. > 319s autopkgtest [00:13:05]: test command1: - - - - - - - - - - stderr - - > - - - - - - - - > 319s Possible precedence issue with control flow operator (exit) at > /usr/bin/pstoimg line 874. >From >https://metacpan.org/release/HAARG/perl-5.40.0/view/pod/perldelta.pod#Changes-to-Existing-Diagnostics Possible precedence issue with control flow operator (%s) … Now it is also shown for misleading code like this: exit $x ? 0 : 1; # actually parses as: exit($x) ? 0 : 1; exit $x == 0; # actually parses as: exit($x) == 0; Trivial patch attached. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- diff -Nru latex2html-2024-debian1/debian/patches/series latex2html-2024-debian1/debian/patches/series --- latex2html-2024-debian1/debian/patches/series 2024-09-17 12:23:55.0 +0200 +++ latex2html-2024-debian1/debian/patches/series 2024-10-18 12:43:10.0 +0200 @@ -4,3 +4,4 @@ upstream/002-fix-rootdir debian/remove-references-to-cweb2html debian/install.patch +upstream/bug1085309 diff -Nru latex2html-2024-debian1/debian/patches/upstream/bug1085309 latex2html-2024-debian1/debian/patches/upstream/bug1085309 --- latex2html-2024-debian1/debian/patches/upstream/bug1085309 1970-01-01 01:00:00.0 +0100 +++ latex2html-2024-debian1/debian/patches/upstream/bug1085309 2024-10-18 12:45:27.0 +0200 @@ -0,0 +1,17 @@ +Description: fix warning "Possible precedence issue with control flow operator (exit) at /usr/bin/pstoimg line 874." +Origin: vendor +Bug-Debian: https://bugs.debian.org/1085309 +Author: gregor herrmann +Last-Update: 2024-10-18 + +--- a/pstoimg.pin b/pstoimg.pin +@@ -969,7 +969,7 @@ + + =cut + +-exit $exit ? 1 : 0; ++exit ($exit ? 1 : 0); + + ## + # Subroutines signature.asc Description: Digital Signature
Bug#1085310: marked as pending in libmousex-getopt-perl
Control: tag -1 pending Hello, Bug #1085310 in libmousex-getopt-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libmousex-getopt-perl/-/commit/baaedf1626e683b31a621160ae207076d7b131cb Add patch from upstream PR to adapt tests to Getopt::Long::Descriptive >= 0.113. Closes: #1085310 (this message was generated automatically) -- Greetings https://bugs.debian.org/1085310
Bug#1085288: marked as pending in libtest2-plugin-uuid-perl
Control: tag -1 pending Hello, Bug #1085288 in libtest2-plugin-uuid-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libtest2-plugin-uuid-perl/-/commit/4afa15545078c053aa6e859f0db4e9fdaca9b3d7 Remove backends from alternative runtime dependency list which cause warnings. Closes: #1085288 (this message was generated automatically) -- Greetings https://bugs.debian.org/1085288
Bug#1085288: libtest2-plugin-uuid-perl: autopkgtest needs update for new version of perl
On Fri, 18 Oct 2024 08:33:10 +0300, Niko Tyni wrote: > I do wonder if we're testing the right thing in the autopkgtest checks > at the moment. If a test doesn't pass with some permutation of the > alternative dependencies, either the test dependencies or the test > itself seem buggy to me. Hm … > I'm tempted to say we should only Depend on those alternatives that > don't cause a warning. Right … Allowing warnings at runtime seems suboptimal (and if a consumer wants one of the warning backends they can still use it). So: dependency list pruned. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1085288: libtest2-plugin-uuid-perl: autopkgtest needs update for new version of perl
On Thu, 17 Oct 2024 22:20:04 +0200, gregor herrmann wrote: > So I guess this needs either > - some friendly hint for the autopkgtest system > - or we can add the TEST2_UUID_NO_WARN env variable, which I didn't > know about before this bug report > > I'm happy to do the latter, as it seems fair in general. Except that we can only set environment variables for the "smoke" test but not for the failing "use.t" test. *sigh* So either some intervention in the autopkgtest system is needed, or we drop all arch:all packages from Depends or something like that :/ Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1085288: libtest2-plugin-uuid-perl: autopkgtest needs update for new version of perl
On Thu, 17 Oct 2024 21:47:46 +0200, Paul Gevers wrote: > Currently this regression is blocking the migration of perl to testing [1]. Ouch. > Of course, perl shouldn't just break your autopkgtest (or even worse, your > package), but it seems to me that the change in perl was intended and your > package needs to update to the new situation. This appears to me the test > fails on a new warning. I think this is an unfortunate artifact; and the warning has nothing to do with perl 5.40 itself, AFAICS. The warning comes from: % grep -r "Using UUID::Tiny" lib/Test2/Util/UUID.pm:warn "Using UUID::Tiny for uuid generation. UUID::Tiny is significantly slower than the 'UUID' or 'Data::UUID::MT' modules, please install 'UUID' or 'Data::UUID::MT' if possible. If you insist on using UUID::Tiny you can set the TEST2_UUID_NO_WARN environment variable.\n" This module can use all kinds of UUID* modules, and that's why it has Depends: … libuuid-perl (>= 0.35) | libdata-uuid-mt-perl | libuuid-tiny-perl | libdata-uuid-perl | libossp-uuid-perl in d/control. What seems to be happening here is that the first two are not yet installable in testing (arch:any packages which are part of the transition and haven't migrated yet), [0] so the third one -- libuuid-tiny-perl -- gets installed which causes this warning. [1] All going as planned, just that we are running into some corner case of the Debian machinery (testing migration during transitions vs. autopkgtests with a mixture of testing and unstable and different dependency resolution [1]). So I guess this needs either - some friendly hint for the autopkgtest system - or we can add the TEST2_UUID_NO_WARN env variable, which I didn't know about before this bug report I'm happy to do the latter, as it seems fair in general. Cheers, gregor [0] Cf. for the first test -- which needs build dependencies: 130s Some packages could not be installed. This may mean that you have 130s requested an impossible situation or if you are using the unstable 130s distribution that some required packages have not yet been created 130s or been moved out of Incoming. 130s The following information may help to resolve the situation: 130s 130s The following packages have unmet dependencies: 130s satisfy:command-line : Depends: libdata-uuid-mt-perl but it is not installable 130s Depends: libdata-uuid-perl or 130s libossp-uuid-perl but it is not installable 130s Depends: libuuid-perl (>= 0.35) but it is not installable 130s E: Unable to correct problems, you have held broken packages. 131s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from unstable [1] which doesn't happen at build time as AFAIK buildds only use the first alternative -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1085153: rrdtool: FTBFS on armel and armhf: passing argument 2 of ‘_sql_fetchrow’ from incompatible pointer type
On Tue, 15 Oct 2024 17:05:38 +0300, Niko Tyni wrote:
> This package failed to build against Perl 5.40 on armhf and armel.
>
> https://buildd.debian.org/status/package.php?p=rrdtool
>
> Looks like a time64 related thing that was already warning earlier but
> has now become a hard error. Presumably that changed with GCC-14 ?
>
>
>rrd_fetch_libdbi.c:625:45: error: passing argument 2 of ‘_sql_fetchrow’
> from incompatible pointer type [-Wincompatible-pointer-types]
> 625 |
> while((r_status=_sql_fetchrow(&table_help,&r_timestamp,&r_value,derive))>0) {
> | ^~~~
> | |
> | long int *
>rrd_fetch_libdbi.c:220:62: note: expected ‘time_t *’ {aka ‘long long int
> *’} but argument is of type ‘long int *’
> 220 | static int _sql_fetchrow(struct sql_table_helper* th,time_t
> *timestamp, rrd_value_t *value,int ordered) {
> |
> ^
>make[4]: *** [Makefile:1006: librrd_la-rrd_fetch_libdbi.lo] Error 1
Friendly ping: Is one of the maintainers in the situation to do an
upload with the upstream commit [0] shortly? Otherwise I'm happy to
help with an NMU.
(This is one of a handful blockers for the Perl 5.40 transition.)
Cheers,
gregor
[0] https://github.com/oetiker/rrdtool-1.x/pull/1265 or
https://github.com/oetiker/rrdtool-1.x/pull/1265/commits/5f954c9aa84420dca3c05caea5feb0f918d6bc47
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
signature.asc
Description: Digital Signature
Bug#1085145: marked as pending in libnet-kafka-perl
Control: tag -1 pending Hello, Bug #1085145 in libnet-kafka-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libnet-kafka-perl/-/commit/e5acc23eb360888dbe9b56aa7105852e4f88c6ff Fix FTBFS on 32-bit with gcc 14. Closes: #1085145 (this message was generated automatically) -- Greetings https://bugs.debian.org/1085145
Bug#1085133: marked as pending in liblmdb-file-perl
Control: tag -1 pending Hello, Bug #1085133 in liblmdb-file-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/liblmdb-file-perl/-/commit/91176f693cca665c7149986672ba5f60f30909a1 Fix FTBFS on 32-bit with gcc 14. Closes: #1085133 (this message was generated automatically) -- Greetings https://bugs.debian.org/1085133
Bug#1085132: marked as pending in libnet-libdnet-perl
Control: tag -1 pending Hello, Bug #1085132 in libnet-libdnet-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libnet-libdnet-perl/-/commit/5793df2e71bd648a5a266c98609727268a30d970 Refresh gcc-14.patch. Thanks: Adrian Bunk for the fix. Closes: #1085132 (this message was generated automatically) -- Greetings https://bugs.debian.org/1085132
Bug#1084502: lemonldap-ng: FTBFS: autobuilder hangs
On Mon, 14 Oct 2024 12:22:52 +0200, Yadd wrote: > I tested the patch given into > https://patch-diff.githubusercontent.com/raw/libtom/libtomcrypt/pull/672 > (libtomcrypt is embedded into CryptX), it fixes the bug Thanks for checking! I've uploaded CryptX-0.082_001 to unstable. Chers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1084502: lemonldap-ng: FTBFS: autobuilder hangs
On Sat, 12 Oct 2024 15:24:31 +0200, Yadd wrote: > it seems that the new libtomcrypt is not stable. Could we downgrade to > version 0.80 ? Downgrading the vendored version of libtomcrypt withing libcryptx-perl might be a bit difficult … But the lates messages in https://github.com/DCIT/perl-CryptX/issues/110 look promising. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1082979: marked as pending in libgnupg-interface-perl
Control: tag -1 pending Hello, Bug #1082979 in libgnupg-interface-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libgnupg-interface-perl/-/commit/f9574e5a101c4f799e2f93a9fd0011dd21b133a1 Adjust 0007-Handle-versions-of-GnuPG-2.2.x-that-report-the-RENC-.patch to GnuPG 2.2.44 which has changed RENC usage_flag again. Closes: #1082979 (this message was generated automatically) -- Greetings https://bugs.debian.org/1082979
Bug#1084899: marked as pending in libhtml-form-perl
Control: tag -1 pending Hello, Bug #1084899 in libhtml-form-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libhtml-form-perl/-/commit/557c536c9a50a09c3f3bb8117105301ebb77f112 Add patch to fix test failing with HTTP::Message 7.00. Closes: #1084899 (this message was generated automatically) -- Greetings https://bugs.debian.org/1084899
Bug#1084899: libhtml-form-perl: t/form.t fails with HTTP::Message 7.00
Source: libhtml-form-perl Version: 6.11-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 After upgrading HTTP::Message to 7.00, we see the following test failure, probably caused by https://github.com/libwww-perl/HTTP-Message/commit/968789db338f0c4f4756573614d26e4757d56deb t/form.t ... ok 1 ok 2 ok 3 ok 4 ok 5 ok 6 ok 7 ok 8 ok 9 ok 10 ok 11 ok 12 ok 13 ok 14 not ok 15 # Failed test at t/form.t line 86. # got: 'POST http://localhost/ # Content-Length: 80 # Content-Type: application/x-www-form-urlencoded # # i.x=1&i.y=1&c=on&r=b&t=&p=&tel=&date=&h=xyzzy&f=&x=&a=%0Aabc%0A+++&s=bar&m=a&m=b # ' # expected: 'POST http://localhost/ # Content-Length: 86 # Content-Type: application/x-www-form-urlencoded # # i.x=1&i.y=1&c=on&r=b&t=&p=&tel=&date=&h=xyzzy&f=&x=&a=%0D%0Aabc%0D%0A+++&s=bar&m=a&m=b # ' ok 16 ... Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmcH+HZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgb12w//fkb6aSJMlPB13ggGEBcMkU2/GhyrRR5eJowAMzzlo+d1q+ytJ8jwibET cFPQqf2XU6rjSZpzkAM23Vu9hrJ66IrJ0Uy4GtJHOJywZqCMSeD8gDPHo965wMju J8N8yu0IAHbdmYrtGcdS5pXvyYFIBKsrSWcD6nH1jEomoz/CDSJXRTaUzJ4tfXVS OkJ6CgTzo/eAhGK9wO1UJg0LP+JjN72DkNScVPiGUth4KIN4EM6lOAUarmfgIYWX PLdAE0gmShQ7EtzMdoueTGqHCHrWqkUm+hllEdRI+uHV5Kj5ngQis4yspRDdzuME WUeZF1WquInPlHpFT9047XtqUB2s7UtkfSCjhoMw8q2q5GwwFSF/VoDcpgYaVQRv b+QnPJPqY7F2JdAt16JqOyUbX/hzrLX7vffyPR78VVStQ3JGm0f/PLdH0Q4yHYtK uD1pOs52Dad2pROs/DvHu3/OQd9LlZLBqfyWG3zDOdf/LY1YIyrqMNA+TABn5gLd 5vNnrvgYa/BoX7h022lOPZ+lOXVaDsX1eRRJ2VQ4SQC2M+ZJ8bU3PqAP5Qu0SdKJ +QewnW0Wxjotx96QCfKSDANTpnC+myrswMtZOoyabEcrfKggkSHXc06RUySkCuQq VZ3dMf/6p1ZoesAYH9HAlp0yKOE9x/fvSPjGbEPb45WjODpOrTY= =VsbG -END PGP SIGNATURE-
Bug#1084502: Processed: found 1084502 in 0.081-2
Control: found -1 0.081-1 Control: found -1 0.082-1 On Tue, 08 Oct 2024 19:02:27 +0200, Yadd wrote: > > > > found 1084502 0.081-2 > > > Bug #1084502 [libcryptx-perl] Crypt::PK::RSA initialization fails with > > > RSA key passed as reference > > > Marked as found in versions libcryptx-perl/0.081-2. > > How about 0.082-1? (And 0.081-1 but that's history) > it seems that both are affected Alright, thanks. (I was just surprised why escpecially 0.081-2 should be the problematic version :)) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1084502: Processed: found 1084502 in 0.081-2
On Tue, 08 Oct 2024 16:15:11 +, Debian Bug Tracking System wrote: > > found 1084502 0.081-2 > Bug #1084502 [libcryptx-perl] Crypt::PK::RSA initialization fails with RSA > key passed as reference > Marked as found in versions libcryptx-perl/0.081-2. How about 0.082-1? (And 0.081-1 but that's history) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1084214: libgit-raw-perl: FTBFS with libgit2 1.8.2~rc1: t/17-filter.t fails
Source: libgit-raw-perl Version: 0.90+ds-2 Severity: serious Tags: ftbfs trixie sid Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: libg...@packages.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libgit2 was updated to 1.8.2~rc1+ds-2 in unstable. During the binNMU libgit-raw-perl failed: https://buildd.debian.org/status/logs.php?pkg=libgit-raw-perl&ver=0.90%2Bds-2%2Bb3 # Failed test at t/17-filter.t line 148. # 'no error at t/17-filter.t line 147' # doesn't match '(?^:Throwing an exception here!)' # Looks like you failed 1 test of 38. t/17-filter.t ... ok 1 - An object of class 'Git::Raw::Filter' isa 'Git::Raw::Filter' ok 2 ok 3 - An object of class 'Git::Raw::Filter::Source' isa 'Git::Raw::Filter::Source' ok 4 ok 5 ok 6 ok 7 - An object of class 'Git::Raw::Filter::Source' isa 'Git::Raw::Filter::Source' ok 8 - A reference of type 'SCALAR' isa 'SCALAR' ok 9 ok 10 ok 11 ok 12 ok 13 ok 14 ok 15 ok 16 ok 17 ok 18 ok 19 not ok 20 ok 21 ok 22 ok 23 ok 24 ok 25 ok 26 ok 27 ok 28 ok 29 ok 30 ok 31 - An object of class 'Git::Raw::Filter::List' isa 'Git::Raw::Filter::List' ok 32 ok 33 ok 34 ok 35 - An object of class 'Git::Raw::Filter::List' isa 'Git::Raw::Filter::List' ok 36 ok 37 ok 38 1..38 Dubious, test returned 1 (wstat 256, 0x100) Failed 1/38 subtests Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmcC2DdfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgYuqhAAk/bvAPonmusizLKimcZ8zsmL6H7Nbj7vDdBClsBCfwPInEjaHQ4SVO53 P2C238b7iCKdkqOMLe9039Q5FpHHLqTf6exROqJJvLOn/D+QeS4vHF2hVpXXMRza M2zLP0w2yUm77axOJAKwsuSFHCiaYc4E+tXb2C47bQAIsmIAX4OIglr/keubjKxK R6DvzC8zTyIPnfhvH0kk/Rlm0RAlj72Lz5/QVgyuGff+Hq5zI+IyvBs7CFV+s4BP XgmYSZfRuWmwtJZCwzjwlTw3l0LbtGZrXfOL7xY9cZmYZzl07/XAuY/b5L+lLhs2 5DFQi+JMLq8xY4Z3wutlwcuTdltiVORziDprY/zvWPEGS4KHZn4719t3B+cIV55w OtxMQV1T35GzF+X1wXJbJSHWx9BDBR/NHt6G/1cFOIpwL9vWEsk5sZT4z5KsO8iu 1pY0QiVOFLRQf4bgcg3NONI/u4FPmMkKehrMfs8JRX3bpoOf7XPoHBcbcAlz3rQ/ wa056R2OcuzdSwN8+iKJeupahc9jCoCZfpIk7PH6e2/sDywSbO7AzzHmtteIsSOV Drl5Ql4bLf4PAlS4b/dgYyNieJdFAdSygXZ+SDoF6+GsShUQ5OMz4+QGA24VF5xS vCUnNTwcTHuArdoqYEjnHUg8jWF0MAVEORZKRQsve0QdkXPYaRw= =OB1E -END PGP SIGNATURE-
Bug#1084154: libdatetime-format-flexible-perl: Test failures with libdatetime-timezone-perl 1:2.63-1+2024b / DateTime::TimeZone 2.63 - Olson DB 2024b
Source: libdatetime-format-flexible-perl Version: 0.34-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libdatetime-format-flexible-perl's tests fail against libdatetime-timezone-perl 1:2.63-1+2024b / DateTime::TimeZone 2.63, which is based on Olson DB 2024b. The latter removes the old System V timezone names [0]. Cf. https://ci.debian.net/packages/libd/libdatetime-format-flexible-perl/testing/amd64/52761211/ 66s not ok 3504 - timezone => EST 66s 66s # Failed test 'timezone => EST' 66s # at t/lib/helper.pm line 88. 66s # got: 'America/Panama' 66s # expected: 'EST' 66s not ok 3666 - timezone => EST 66s 66s # Failed test 'timezone => EST' 66s # at t/lib/helper.pm line 88. 66s # got: 'America/Panama' 66s # expected: 'EST' 66s ok 3667 - 12 Mar 2010 10:06:39 EST => 2010-03-12T10:06:39 66s not ok 3668 - timezone => EST 66s 66s # Failed test 'timezone => EST' 66s # at t/lib/helper.pm line 88. 66s # got: 'America/Panama' 66s # expected: 'EST' 66s not ok 3724 - timezone => EST 66s 66s # Failed test 'timezone => EST' 66s # at t/lib/helper.pm line 88. 66s # got: 'America/Panama' 66s # expected: 'EST' 66s not ok 3760 - timezone => EST 66s 66s # Failed test 'timezone => EST' 66s # at t/lib/helper.pm line 88. 66s # got: 'America/Panama' 66s # expected: 'EST' 66s not ok 3776 - timezone => EST 66s 66s # Failed test 'timezone => EST' 66s # at t/lib/helper.pm line 88. 66s # got: 'America/Panama' 66s # expected: 'EST' 66s not ok 3784 - timezone => EST 66s 66s # Failed test 'timezone => EST' 66s # at t/lib/helper.pm line 88. 66s # got: 'America/Panama' 66s # expected: 'EST' 66s not ok 3844 - timezone => EST 66s 66s # Failed test 'timezone => EST' 66s # at t/lib/helper.pm line 88. 66s # got: 'America/Panama' 66s # expected: 'EST' etc. Cheers, gregor [0] https://lists.iana.org/hyperkitty/list/tz-annou...@iana.org/thread/IZ7AO6WRE3W3TWBL5IR6PMQUL433BQIE/ -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmcBjYNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZNKQ/8Dgw0i+ZceU6eyLvVAJVjt8T+clWUkhyUTfzP1bAdsK1TjglwoPoCVhh2 ZMHqaaEWb8YTwhaEloRu+QLUVIueczxde0Rp3MJZq3ckzjRbnjGjIrykQW9iWZCg 6Vu+u4N85MuR/XfdgixGddNqFbqm0WRKgTkJhkGQLd+xgriJb1ldrgKTgfqjpRmN rLUpf20RyGTSFIwJWStMfr5wqCMLzFK4a2oZ9xr4QPzVdVd0pKA/H9xZkoH6PK4Z f0DbnE6fhurEC6VJQHtwKWDROG7EyP1YFdc6a/i1QmL1Siekp6gMW+NfD8e0bEZh BFiUHzO0M446MVjE1zp8eOCpDAVDBnusCdtKCxs8H89EzBew5AOhGME94T6i05ZI herkdjuKcsFsydiHmorlUssrGEDUjau17WPm8K4fWaPS+Ws97+W8/+TJn84qv5Jw zlkXozFtT4OLonwPIcOgZI4s7NwU5BDP6KX+U5HThZVZOayxmLpRoFo2iwPUk5Ly Zr90ZthyI+JkQHhfmxVTIVF+30MrOF+WCaVO3xUmdQrIg5jzpwgzedaz1Q3IW+Bs 4bFaO3Sqy7QUJtelv3uOS7aRqy727YpNoqMQDEMYcxSQCL9S7+y1/Llo2gOcmX2l JbxvKj7DVdLJ4iHU+OYdi1A+U6hAo3tY64u8lG8DYiPQPR5Hvs4= =fSJi -END PGP SIGNATURE-
Bug#1084155: libdatetimex-easy-perl: Test failures with libdatetime-timezone-perl 1:2.63-1+2024b / DateTime::TimeZone 2.63 - Olson DB 2024b
Source: libdatetimex-easy-perl Version: 0.091-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libdatetimex-easy-perl's tests fail against libdatetime-timezone-perl 1:2.63-1+2024b / DateTime::TimeZone 2.63, which is based on Olson DB 2024b. The latter removes the old System V timezone names [0]. Cf. https://ci.debian.net/packages/libd/libdatetimex-easy-perl/testing/amd64/52761219/ 62s not ok 69 62s 62s # Failed test at t/01-basic.t line 180. 62s # got: 'America/Los_Angeles' 62s # expected: 'PST8PDT' 62s ok 70 62s not ok 71 62s 62s # Failed test at t/01-basic.t line 184. 62s # got: 'America/Los_Angeles' 62s # expected: 'PST8PDT' 62s ok 72 62s not ok 73 62s 62s # Failed test at t/01-basic.t line 188. 62s # got: 'America/Los_Angeles' 62s # expected: 'PST8PDT' Cheers, gregor [0] https://lists.iana.org/hyperkitty/list/tz-annou...@iana.org/thread/IZ7AO6WRE3W3TWBL5IR6PMQUL433BQIE/ -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmcBjYdfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbkDA//cUtx8diehgZAzkJ0fTfpTBkJHvZQ2A+X/PdjBiPP/E2+cW5x2dAd8MAD PJ1cchhCkoTfSYGg8MqM/WuDAeohCx7rMoCgRKCE7vIZgHQODHX0hZ+1hNuMt61f uLSYQwyUUrqsyTIG4UoizXPBkCT3rzrPrI31s4iQlqsiFhqoOOa3VDRXIogKL8PY wCu52LoHJVf0aaS254wOf6cM/sqG62nEv7H7P9Ffiyn9F76zr9IvdijbVlRfzucl 1DQihqicPpS1mmNqXDRs/gGsRjn+Y1O5GaNQOio8hC8IOeTiGE0DPGvV9indOoiX 1Np4GyBzogW/hRZY0JajCWRd8FZbwg4IAwW1eNn7rh3i6w9nKdwfHL4OQzdS/kGw Dj5CHYVTwE0XTSGj39kgtnmLeLT6rw7GlOR0gv1Q3PdhVvqI4ANA44OyiZMJ1veo W9p3v8g1eTzcThvdQifZ+XXOia5SzzrSTBPtO25IfiC6HZpSr9sAHrb0S8+yvTev bO9sGNfc5+o28MYgcxIxlnHAT+8ijysULmQgbO7a9jabLP7qf/H3cNs46Wcmwg3O D9By4Y7jx9cVY3efjGJYeHOZ70amS7FRAqgBU+RrROkcCpCBytPJFuaCl/NNwFV3 PP59nXwkZYmjbBBL6kHiby+UQ/g2nvClAvDubxzI+JBwF5FT1J0= =Xe1a -END PGP SIGNATURE-
Bug#1083279: biber: can't build debian-package-book-* with pbuilder anymore because aof missing dependency
On Thu, 03 Oct 2024 21:17:39 +0200, Mechtilde Stehmann wrote: > While updating the package 'debian-package-book-*" > https://salsa.debian.org/ddp-team/dpb > I strumple about the following problem. > When I build in pbuilder I get the message: > > The following packages have unmet dependencies: > libtext-csv-xs-perl : Depends: libencode-perl (>= 3.20) but it is not going > to > be installed > The following actions will resolve these dependencies: > > Install the following packages: > 1) libencode-perl [3.21-1+b1 (unstable)] > > But it isn't installable. so the build failed I've seen this a couple of times in the last weeks (not with biber but some other random packages) when I tried to build with cowbuilder. My workaround was to change PBUILDERSATISFYDEPENDSCMD="/usr/lib/pbuilder/pbuilder-satisfydepends" (/usr/lib/pbuilder/pbuilder-satisfydepends is a symlink to pbuilder-satisfydepends-aptitude) to PBUILDERSATISFYDEPENDSCMD="/usr/lib/pbuilder/pbuilder-satisfydepends-apt" in my pbuilderrc. I never looked why the aptitude resolver fails but the apt resolver works. In any case I'm sure this is not a problem in the biber package; I also don't think it's a problem in libencode-perl or any of the packages depending on it. I don't know - maybe a bug in pbuilder/cowbuilder? > It also works If I build with sbuild. Which confirms my hunch that the problem is not with biber and not with libencode-perl. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1076488: src:libxml-libxslt-perl: fails to migrate to testing for too long: autopkgtest issues
On Wed, 02 Oct 2024 22:08:13 +0200, Paul Gevers wrote: > On 02-10-2024 20:22, gregor herrmann wrote: > > I seem to remember that I also expressed my unhappiness about the > > warning to the libxml2 maintainer but oh well … > Wait, that warning comes from libxml2? That feels... wrong. That's what I meant :) Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072012#42 ff Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1076488: src:libxml-libxslt-perl: fails to migrate to testing for too long: autopkgtest issues
On Mon, 30 Sep 2024 20:26:15 +0200, Paul Gevers wrote: > On 30-09-2024 00:14, gregor herrmann wrote: > > >Warning: program compiled against libxml 212 using older 209 > > Oh, that simple; somehow embarrassing that I missed this :) > I didn't check what got implemented exactly (sorry I'm assuming wrongly or > don't understand the problem), but I feel that a stricter dependency is only > there to prevent the warning. I *think* the warning should be patched out > instead and is a sign of the lack of proper SONAME bumping by upstream > libxml. I seem to remember that I also expressed my unhappiness about the warning to the libxml2 maintainer but oh well … > Although I recognize: pick your battles. *nod* Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1076488: src:libxml-libxslt-perl: fails to migrate to testing for too long: autopkgtest issues
On Sun, 29 Sep 2024 22:03:46 +0300, Niko Tyni wrote: > > I wonder what still was compiled against libxml2 2.12 … One guess is libxslt > > which hasn't seen any upload or binNMU since July. > > Um, seems to me that libxml-libxslt-perl itself needs a rebuild (and > possibly tighter dependencies) against the "new" libxml2 before it > can migrate? > > (sid)# perl -we 'use XML::LibXSLT' > Warning: program compiled against libxml 212 using older 209 > (sid)# objdump -p > /usr/lib/x86_64-linux-gnu/perl5/5.38/auto/XML/LibXSLT/LibXSLT.so |grep libxml2 > NEEDED libxml2.so.2 > > Apologies if I'm missing something :) Oh, that simple; somehow embarrassing that I missed this :) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1076488: src:libxml-libxslt-perl: fails to migrate to testing for too long: autopkgtest issues
On Sun, 29 Sep 2024 00:49:29 +0200, gregor herrmann wrote: > Now we have libxml2 2.9 back in testing > (2.12.7+dfsg+really2.9.14-0.1), and a libxml-libxml-perl which > depends on this version and has been built against it, but the > autopkgtest failures are still there: > https://tracker.debian.org/pkg/libxml-libxslt-perl > with our friend > Warning: program compiled against libxml 212 using older 209 > I wonder what still was compiled against libxml2 2.12 … One guess is libxslt > which hasn't seen any upload or binNMU since July. Or whatever … I just install a local .deb and also saw Warning: program compiled against libxml 212 using older 209 Processing triggers for shared-mime-info (2.4-5) ... Warning: program compiled against libxml 212 using older 209 Processing triggers for mailcap (3.72) ... Processing triggers for desktop-file-utils (0.27-2) ... Looks like there is still stuff compiled against libxml2 2.12 lying around. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1076488: src:libxml-libxslt-perl: fails to migrate to testing for too long: autopkgtest issues
On Thu, 18 Jul 2024 08:46:00 +0200, Paul Gevers wrote: > On 17-07-2024 11:20 p.m., gregor herrmann wrote: > > So I guess I'd just wait (the new libxml-libxslt-perl version also > > has no groundbreaking changes); but I might miss something which > > others may add. > I think that's acceptable if only warnings are involved indeed. Now we have libxml2 2.9 back in testing (2.12.7+dfsg+really2.9.14-0.1), and a libxml-libxml-perl which depends on this version and has been built against it, but the autopkgtest failures are still there: https://tracker.debian.org/pkg/libxml-libxslt-perl with our friend Warning: program compiled against libxml 212 using older 209 I wonder what still was compiled against libxml2 2.12 … One guess is libxslt which hasn't seen any upload or binNMU since July. Maybe a binNMU of libxslt against libxml2 2.12.7+dfsg+really2.9.14-0.1 would help? Or maybe someone else has better ideas … Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1082952: libcryptx-perl: t/sshkey.t fails on some architectures
Source: libcryptx-perl Version: 0.081-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 0.081-1 has test failures on some architectures (s390x, ppc64, sparc64, x32): https://buildd.debian.org/status/package.php?p=libcryptx-perl At least for the first three the failure is the same: FATAL: pem_decode_openssh failed: Invalid argument provided. at t/sshkey.t line 129. # Looks like your test exited with 255 just after 54. t/sshkey.t .. 1..756 ok 1 - RSA new ok 2 - ECC new ok 3 - DSA new ok 4 - ssh_rsa_1024/ssh_rsa_1024_pkcs8/e ok 5 - ssh_rsa_1024/ssh_rsa_1024_pkcs8/N ok 6 - ssh_rsa_1024/ssh_rsa_1024_pkcs8/is_private ok 7 - ssh_rsa_1024/ssh_rsa_1024_pkcs8/d ok 8 - ssh_rsa_1024/ssh_rsa_1024_pkcs8/p ok 9 - ssh_rsa_1024/ssh_rsa_1024_pkcs8/q ok 10 - ssh_rsa_1024/ssh_rsa_1024_pkcs8/qP ok 11 - ssh_rsa_1024/ssh_rsa_1024_pkcs8/dP ok 12 - ssh_rsa_1024/ssh_rsa_1024_pkcs8/dQ ok 13 - ssh_rsa_1024/ssh_rsa_1024_pkcs8_pw/e ok 14 - ssh_rsa_1024/ssh_rsa_1024_pkcs8_pw/N ok 15 - ssh_rsa_1024/ssh_rsa_1024_pkcs8_pw/is_private ok 16 - ssh_rsa_1024/ssh_rsa_1024_pkcs8_pw/d ok 17 - ssh_rsa_1024/ssh_rsa_1024_pkcs8_pw/p ok 18 - ssh_rsa_1024/ssh_rsa_1024_pkcs8_pw/q ok 19 - ssh_rsa_1024/ssh_rsa_1024_pkcs8_pw/qP ok 20 - ssh_rsa_1024/ssh_rsa_1024_pkcs8_pw/dP ok 21 - ssh_rsa_1024/ssh_rsa_1024_pkcs8_pw/dQ ok 22 - ssh_rsa_1024/ssh_rsa_1024_pkcs8.pub/e ok 23 - ssh_rsa_1024/ssh_rsa_1024_pkcs8.pub/N ok 24 - ssh_rsa_1024/ssh_rsa_1024_pkcs8.pub/is_not_private ok 25 - ssh_rsa_1024/ssh_rsa_1024_pem/e ok 26 - ssh_rsa_1024/ssh_rsa_1024_pem/N ok 27 - ssh_rsa_1024/ssh_rsa_1024_pem/is_private ok 28 - ssh_rsa_1024/ssh_rsa_1024_pem/d ok 29 - ssh_rsa_1024/ssh_rsa_1024_pem/p ok 30 - ssh_rsa_1024/ssh_rsa_1024_pem/q ok 31 - ssh_rsa_1024/ssh_rsa_1024_pem/qP ok 32 - ssh_rsa_1024/ssh_rsa_1024_pem/dP ok 33 - ssh_rsa_1024/ssh_rsa_1024_pem/dQ ok 34 - ssh_rsa_1024/ssh_rsa_1024_pem_pw/e ok 35 - ssh_rsa_1024/ssh_rsa_1024_pem_pw/N ok 36 - ssh_rsa_1024/ssh_rsa_1024_pem_pw/is_private ok 37 - ssh_rsa_1024/ssh_rsa_1024_pem_pw/d ok 38 - ssh_rsa_1024/ssh_rsa_1024_pem_pw/p ok 39 - ssh_rsa_1024/ssh_rsa_1024_pem_pw/q ok 40 - ssh_rsa_1024/ssh_rsa_1024_pem_pw/qP ok 41 - ssh_rsa_1024/ssh_rsa_1024_pem_pw/dP ok 42 - ssh_rsa_1024/ssh_rsa_1024_pem_pw/dQ ok 43 - ssh_rsa_1024/ssh_rsa_1024_pem.pub/e ok 44 - ssh_rsa_1024/ssh_rsa_1024_pem.pub/N ok 45 - ssh_rsa_1024/ssh_rsa_1024_pem.pub/is_not_private ok 46 - ssh_rsa_1024/ssh_rsa_1024_openssh/e ok 47 - ssh_rsa_1024/ssh_rsa_1024_openssh/N ok 48 - ssh_rsa_1024/ssh_rsa_1024_openssh/is_private ok 49 - ssh_rsa_1024/ssh_rsa_1024_openssh/d ok 50 - ssh_rsa_1024/ssh_rsa_1024_openssh/p ok 51 - ssh_rsa_1024/ssh_rsa_1024_openssh/q ok 52 - ssh_rsa_1024/ssh_rsa_1024_openssh/qP ok 53 - ssh_rsa_1024/ssh_rsa_1024_openssh/dP ok 54 - ssh_rsa_1024/ssh_rsa_1024_openssh/dQ Dubious, test returned 255 (wstat 65280, 0xff00) Failed 702/756 subtests Test Summary Report - --- t/sshkey.t(Wstat: 65280 (exited 255) Tests: 54 Failed: 0) Non-zero exit status: 255 Parse errors: Bad plan. You planned 756 tests but ran 54. Files=137, Tests=24533, 14 wallclock secs ( 0.77 usr 0.08 sys + 12.84 cusr 0.63 csys = 14.32 CPU) Result: FAIL Failed 1/137 test programs. 0/24533 subtests failed. make[1]: *** [Makefile:1771: test_dynamic] Error 255 Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmb4gyVfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbcqBAAj8+cQwMyQYl+G5Qn5RVUFOv4YBS5q5DIEjh+huZD1S9j8UTLyTGcGW2h sds03054GcHLONMI/EqF8269FGhm7ibF6grety/Vcgij2ZvsY7KDCZHcBLf9Ic1Q U43mcpN8zzeklN7ZFl1SeCklkeYJ9ktDGTQ+Wq5eib50WdKc7QhcdBSwzjgcirSE 7kwNI7G4tA3gk9HbohRZNgYLP6VRC8oJb/dazL0kO6sPnzoSvjpijGdWZ3zdOVjW kDvCExybRFTpfgbFVAWkY2RY/jRKj/2xYU4RGpmN+BHdE/lz4MPbJS3L7akjiBKJ X3z2rgVtvv25Y+ugGi80GeqQi26ixDorAFvxwdZ5FYReAHnIFr1o2G0u/W2gB79H CM0Yb0dXYtFvDmhzVhANH6mSlabhS/T+FDgNj80NP2pDv5HzDI+rCXzHwrTYG836 Fl8XH7p6cmkMs6+lFS7rpYMmXIMU+jvavufXP5z9bzRthDhisQqT+i3RPubXsAZW bRVXoO23YXlQkE/pZ9D/od4UlvLTGtWClvnJxl1l9tx3li2XhjXzxoMAp+tg1H9x WzLVpdphx8DE0sB2L4oMgCHmrgIxazHSiwzThP6faAPx1rVr+tTjr/V1CrdJUpyF 8pF96hURVOFZjDUdnVL/zKCK+OUOZ5+ciaBW6NK9slCbsbYrkS0= =gZ0M -END PGP SIGNATURE-
Bug#1082893: libxs-parse-sublike-perl: Compiler warnings on 32bit architecures cause autopkgtest failures
Source: libxs-parse-sublike-perl
Version: 0.27-1
Severity: serious
Tags: upstream
Justification: autopkgtest failure prevent migration to testing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The update to 0.27 causes compiler warnings on 32bit architectures,
as seen on
https://ci.debian.net/packages/libx/libxs-parse-sublike-perl/testing/armel/52370765/
https://ci.debian.net/packages/libx/libxs-parse-sublike-perl/testing/armel/52370765/
https://ci.debian.net/packages/libx/libxs-parse-sublike-perl/testing/armel/52370765/
The warnings look like this (from i386):
55s i686-linux-gnu-gcc -I/usr/lib/i386-linux-gnu/perl/5.38/CORE
'-DVERSION="0.27"' '-DXS_VERSION="0.27"' -fPIC -Ishare/include -Iinclude -Ihax
-Wall -Wno-unused-function -Wno-unused-value -c -D_REENTRANT -D_GNU_SOURCE
-DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include
-D_LARGEFILE_SOURCE '-D_FILE_OFFSET_BITS=64' -O2 -g -o t/func.o t/func.c
55s In file included from /usr/lib/i386-linux-gnu/perl/5.38/CORE/perl.h:6227,
55s from t/func.xs:8:
55s t/func.xs: In function ‘post_defop_Attribute’:
55s t/func.xs:61:33: warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
55s61 | hv_stores(n, "op",newSVuv((UV)ctx->op));
55s | ^
55s /usr/lib/i386-linux-gnu/perl/5.38/CORE/embed.h:293:86: note: in definition
of macro ‘hv_common_key_len’
55s 293 | # define hv_common_key_len(a,b,c,d,e,f)
Perl_hv_common_key_len(aTHX_ a,b,c,d,e,f)
55s |
^
55s /usr/lib/i386-linux-gnu/perl/5.38/CORE/hv.h:565:5: note: in expansion of
macro ‘hv_store’
55s 565 | hv_store((hv), ASSERT_IS_LITERAL(key), (sizeof(key)-1), (val),
0)
55s | ^~~~
55s t/func.xs:61:3: note: in expansion of macro ‘hv_stores’
55s61 | hv_stores(n, "op",newSVuv((UV)ctx->op));
55s | ^
55s t/func.xs:61:25: note: in expansion of macro ‘newSVuv’
55s61 | hv_stores(n, "op",newSVuv((UV)ctx->op));
55s | ^~~
55s t/func.xs:62:33: warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
55s62 | hv_stores(n, "varop", newSVuv((UV)ctx->varop));
55s | ^
55s /usr/lib/i386-linux-gnu/perl/5.38/CORE/embed.h:293:86: note: in definition
of macro ‘hv_common_key_len’
55s 293 | # define hv_common_key_len(a,b,c,d,e,f)
Perl_hv_common_key_len(aTHX_ a,b,c,d,e,f)
55s |
^
55s /usr/lib/i386-linux-gnu/perl/5.38/CORE/hv.h:565:5: note: in expansion of
macro ‘hv_store’
55s 565 | hv_store((hv), ASSERT_IS_LITERAL(key), (sizeof(key)-1), (val),
0)
55s | ^~~~
55s t/func.xs:62:3: note: in expansion of macro ‘hv_stores’
55s62 | hv_stores(n, "varop", newSVuv((UV)ctx->varop));
55s | ^
55s t/func.xs:62:25: note: in expansion of macro ‘newSVuv’
55s62 | hv_stores(n, "varop", newSVuv((UV)ctx->varop));
55s | ^~~
55s t/func.xs:63:33: warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
55s63 | hv_stores(n, "defop", newSVuv((UV)ctx->defop));
55s | ^
55s /usr/lib/i386-linux-gnu/perl/5.38/CORE/embed.h:293:86: note: in definition
of macro ‘hv_common_key_len’
55s 293 | # define hv_common_key_len(a,b,c,d,e,f)
Perl_hv_common_key_len(aTHX_ a,b,c,d,e,f)
55s |
^
55s /usr/lib/i386-linux-gnu/perl/5.38/CORE/hv.h:565:5: note: in expansion of
macro ‘hv_store’
55s 565 | hv_store((hv), ASSERT_IS_LITERAL(key), (sizeof(key)-1), (val),
0)
55s | ^~~~
55s t/func.xs:63:3: note: in expansion of macro ‘hv_stores’
55s63 | hv_stores(n, "defop", newSVuv((UV)ctx->defop));
55s | ^
55s t/func.xs:63:25: note: in expansion of macro ‘newSVuv’
55s63 | hv_stores(n, "defop", newSVuv((UV)ctx->defop));
55s | ^~~
55s ExtUtils::Mkbootstrap::Mkbootstrap('t/blib/arch/auto/t/func/func.bs')
Unfortunately these warnings cause autopkgtest's smoke test to fail …
Cheers,
gregor
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmb3CqlfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYNARAAhBcjGUGWh9v1PvgdhfTTdtNXwyiNipGhswXWHrjqxxjLYrDnjAch3t9f
1zrfmEHcmW7f6xM5WtZS1d9tYv3+AxJgLqsFxAvtKwnhbEGpOSd9n7HMzVAsf0r6
sWBajwxBMdzrLVxwT6VFbopEutXK228HNNAmkZybHVD/f3R5MonggL68hFlHnNg1
rsESJVBLQAZNuROevRtONqS0fUwtfOXJmoeBjZGSxdi9rmEiesqElMepq46pf2uM
HWwtkntVB/XOdON1otYOcoFHi8fjAojBa85gjgV8SQx6z3K2IoJVJMru875N68T8
IbGJQet6TNxV7QIDadnaOphcecNyv6g36
Bug#1082815: analizo: FTBFS (tests fail) on sid
On Thu, 26 Sep 2024 20:52:23 +0200, наб wrote: > Caught this in ratt for src:ossp-uuid, > but it fails on a clean sbuild -d unstable analizo. Thanks for your bug report. Unfortunately I can't reproduce it, the package still builds fine for me in my sid cowbuilder chroot. Can you provide any further hints? Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1082747: cod-tools: FTBFS (only) on riscv64
On Thu, 26 Sep 2024 09:57:26 +0300, Andrius Merkys wrote: > > Observations and thoughts: > > * -1 built everywhere, including riscv64 > > * -1.1 still builds everywhere, except for riscv64 > > * I don't think the changes from the NMU (Niko's Perl exporter() > >patch) are related > > * The build on riscv64 failed 4 times, so not a > >parallelization/timing issue probably (and d/rules uses > >--no-parallel) > Thanks a lot for giving this issue a look. I scratched my head a lot on this > issue this week. What I find even more interesting, is that -1.1 > successfully builds on riscv64 porterbox (ricci.debian.org). Oh dear :/ Thanks for trying, that's what Niko also proposed as a next step (on IRC), and I at least had found out about ricci's existence :) > This is really strange, because, as you have noticed, > src/components/codcif/cif_list_tags is successfully built earlier: Ack. I was wondering if the build could be made more verbose, or if digging into the various makefiles would help … > > I've been staring at the logs for some time but haven't found out > > what's happening here on riscv64; help welcome. > Same. I wonder if we can ask buildds to test-rebuild -1. Hm, I don't (know|think so). Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1082747: cod-tools: FTBFS (only) on riscv64
Source: cod-tools Version: 3.10.0+dfsg-1.1 Severity: serious Tags: help ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-p...@lists.debian.org, debian-ri...@lists.debian.org User: debian-p...@lists.debian.org Usertags: perl-5.40-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I noticed that cod-tools 3.10.0+dfsg-1.1 fails to build but only on riscv64: https://buildd.debian.org/status/package.php?p=cod-tools https://buildd.debian.org/status/logs.php?pkg=cod-tools I care about this issue because 1) I uploaded the -1.1 NMU, and 2) this will get in the way of the Perl 5.40 transition (#1082293), which was the reason for the NMU in the first place, as it blocks the migration of cod-tools. Observations and thoughts: * -1 built everywhere, including riscv64 * -1.1 still builds everywhere, except for riscv64 * I don't think the changes from the NMU (Niko's Perl exporter() patch) are related * The build on riscv64 failed 4 times, so not a parallelization/timing issue probably (and d/rules uses --no-parallel) On riscv64 the build fails with #v+ tools/help2man scripts/utf8-to-cif --bugs-email cod-b...@ibt.lt > doc/man/utf8-to-cif.1 make[1]: *** No rule to make target 'doc/man/cif_list_tags.1', needed by 'man'. Stop. make[1]: Leaving directory '/<>' v- On amd64 we see: #v+ tools/help2man scripts/utf8-to-cif --bugs-email cod-b...@ibt.lt > doc/man/utf8-to-cif.1 src/components/codcif/cif_list_tags --help | tools/help2man --stdin --name cif_list_tags --bugs-email cod-b...@ibt.lt > doc/man/cif_list_tags.1 src/components/codcif/cifparse --help | tools/help2man --stdin --name cifparse --bugs-email cod-b...@ibt.lt > doc/man/cifparse.1 src/components/codcif/cifvalues --help | tools/help2man --stdin --name cifvalues --bugs-email cod-b...@ibt.lt > doc/man/cifvalues.1 make[1]: Leaving directory '/<>' #v- So it looks like src/components/codcif/cif_list_tags exists on amd64 et al., but not in riscv64. The compliation step on amd64: #v+ gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wsign-compare -g -O3 -funroll-loops -fomit-frame-pointer -foptimize-register-move -DYYDEBUG=1 -D_YACC_ -I. -I../../externals/cexceptions -I../../externals/getoptions -fPIC -DSVN_VERSION="\"10068\"" -Wl,-z,relro -Wl,-z,now -o cif_list_tags programs/cif_list_tags.c obj/cif2_grammar.tab.o obj/cif_grammar.tab.o lib/libcodcif.a ../../externals/cexceptions/lib/libcexceptions.a ../../externals/getoptions/lib/libgetoptions.a version.h -lm #v- and on riscv64: #v+ gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wsign-compare -g -O3 -funroll-loops -fomit-frame-pointer -foptimize-register-move -DYYDEBUG=1 -D_YACC_ -I. -I../../externals/cexceptions -I../../externals/getoptions -fPIC -DSVN_VERSION="\"10068\"" -Wl,-z,relro -Wl,-z,now -o cif_list_tags programs/cif_list_tags.c obj/cif2_grammar.tab.o obj/cif_grammar.tab.o lib/libcodcif.a ../../externals/cexceptions/lib/libcexceptions.a ../../externals/getoptions/lib/libgetoptions.a version.h -lm #v- I've been staring at the logs for some time but haven't found out what's happening here on riscv64; help welcome. Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmb0LJNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgY+bg//VBndn6WMjaQG2mzNs0JWRp1YyCLO/mj+HfaLfsS4RD7ilmleTDlauHsl 3XEeIjjHyfd8bLQATYujHCsUCUzJHWgcpmdo9Sq//ItoAnYJFFPY8WHCMokCZejb kOVW32+rgdLfUMkMNVfao0lgAJ6aFmgc69+OKdWOWoCn9Qw6UpRxiBNzUA8g//CC WIG44ThrWxohW1+OApmGYijtVDCpy3wsO8P2kl+A8Un4YjbnAQ7KwN3n05dTXFr0 9981IevQxIkuuBLynl6WMqCuq/HcY2FTnZRozxrNx7UKbulWy1dsrXkcuWBA3648 eUxGr9WovyfRckLQujji5hqYrjHwm9y3YXaG1u9ORnn4dE41igKk1giBFv7IMOCA OMxY4G39OPhd7zXtXqVRzMzgU55cIbqhllHYYLb3fnkx5uN2mBjA0q1c9CKyxptx BujFCUUnO5aCPaXs7Q3AE6P9OzAnLVZvdFzrxuXQxXLnxqrq8xfr0FfCDd0ndEde DGciUaBfWko5+kbQIDc93VXBikj7tHmpzyxstkYoDvPtS69flfpbHanGcJ/k7F2H Ko0LljzaVxOftUXCh3ES5Rm/ZUuujjwUVd33a/rkmu1jqPQOZTITywwoXeR2H4cA Aay1b7KkEDKk7bBFTTX9ufH1qQIbBYHBk5aGLYrlq1r/2r8BWLc= =C7lE -END PGP SIGNATURE-
Bug#1082542: FTBFS: test failure in t/signer.t with CryptX 0.081
Source: libmail-dkim-perl Version: 1.20240827-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 After updating CryptX to 0.081 one test fails: t/signer.t .. 1..35 ok 1 - new() works ok 2 - signature() works # signature=DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=example.org; h=from:subject; s=test; bh=5EPkzXwxglEaVOaXSvuqWjSMqEs=; b=dpM67y4q9hG+TKu5vSoxuky/U1m+cWRcApiIABsyhwDTRhKbtmycb2ZJgY0iz0HNtCIDMVc94VWhLZ4Ktq2Q05011qBXSO/hzuhOlQdg1WuG6SsZiSwgb+u1YWU2KlO3jFhKH8pUVMBjvgq0GnvmDPXChEexI3nYA5lFAQYAz9A= ok 3 - got expected signature value ok 4 - new() works ok 5 - signature() works ok 6 - new() works ok 7 - signature() works # signature=DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=example.org; h=from:subject; s=test; i=b...@example.org; t=1726943807; bh=5EPkzXwxglEaVOaXSvuqWjSMqEs=; b=Afx0IfjCBDl/LtF+ktI7IlDbIm2i9i/ASUo+sqoB3XvGmRp0rCwqca+3oFW7qRf3kEl/F3qJaVGeY3xWSBvWMrwS/EyO59hIw2RmwuKoahCIJEZ6f9bY7pFK9jXw/uxDKaPp3fVlrBCFaAsNL+dgInV8ptWQWspq+ov9jfQwObY= ok 8 - subject was signed ok 9 - from was signed ok 10 - received was excluded ok 11 - comments was excluded ok 12 - got expected identity value ok 13 - found timestamp value ok 14 - new() works ok 15 - signature() works # signature=DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=example.org; h=from:subject:subject:x-test:x-test:x-tests; s=test; i=b...@example.org; t=1726943807; bh=5EPkzXwxglEaVOaXSvuqWjSMqEs=; b=b9oedWevw+DetNbq8k44DreFSDwYmM6XiGQNrMzS4ujYgQBftmcJTThor+bfNkqnJIIOZGyMivIXxkhvW/rZGpRbgBsEPcb9YT7D1FPxZBhda8O0z77zPodOwKXDGU5R0ubcf5SBK+JeNqXkirNxkSopVaGNjQTwvdkkZggZsiA= ok 16 - subject was over signed ok 17 - x-test was all signed ok 18 - x-tests was signed ok 19 - x-tests was signed only once ok 20 - from was signed ok 21 - date was excluded ok 22 - comments was excluded ok 23 - got expected identity value ok 24 - found timestamp value # Error: cannot read t/non_existent_file_!!: No such file or directory ok 25 - new() with bogus key file dies as expected # Error: cannot read t/unreadable_file: No such file or directory ok 26 - new() with bogus key file dies as expected ok 27 - signature() works ok 28 - signature() works ok 29 - signature() works ok 30 - subject was signed ok 31 - from was signed ok 32 - new() works Ed25519 failed: FATAL: invalid or unsupported Ed25519 key format at /build/libmail-dkim-perl-1.20240827/blib/lib/Mail/DKIM/PrivateKey.pm line 106. ...propagated at /build/libmail-dkim-perl-1.20240827/blib/lib/Mail/DKIM/PrivateKey.pm line 172. # Looks like your test exited with 255 just after 32. Dubious, test returned 255 (wstat 65280, 0xff00) Failed 3/35 subtests Cheers, gregor - -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'stable-security'), (500, 'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.10.3-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmbvEwtfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbFOA/8C91n25ShgEYZ4BN+ZSi+MXIq/yzEpa5KAE+YoYbhXevU8CQzkJkjryAs xkYz0EudN/zzRU94EPvGGG32CV/NbsobLr5Mhh65mZ4TppiOOwMrMi8AMO+n8Wxp nN8cqWyTlkncP1Y79ng6KL2uO8OyvSg5nosNpcNAqGVn60gwRI5kp20dQ35YScJJ fuDnEVHitt17DmoGSG2b8Ne4JeF/xsV2/zx1Ql1CqwWlU9QRjUUg76CAMvdPCf5D fnzpxWGuMTKGTleFNzZvkqrlelxvsm5WY8Fcw3NVIfmuMLzQSlmB3ECviFWMMPDu /yuvnYnA6mCl104xN+fX2kQk28KfXsqYMhwXQx87Gkc1+RrnsFbBxXujXo2Dvuq0 dBm0BP6xX1OVrcA31EWDTDi3VwyTPSDV1UdCujGhYdPDoOxIt8ULtB7WGyzPv04e A4pawG3Ld0RZD3tXjSWBnQAT77pKlv67PkTeu63YAm4wLvk96JVl582ZAayHNqZm P4eKZRzIPop+oL8hgjJuUC3pHL+OseIDbvjhz9LSRKjWHd4j/2bc6NKSuXCLq5ul emcy8FOJ4kiLFTJzmO5sXF5q0oGlNf0ZhQUz0yRMKf270KWeNR1K8+3AWL0Zq/yi SK806nyhZ1x9KjE+F5EiQtQGW1pNpaHoFK/9D35FDUnamjkhuic= =CN4R -END PGP SIGNATURE-
Bug#1081869: marked as pending in libsub-handlesvia-perl
Control: tag -1 pending Hello, Bug #1081869 in libsub-handlesvia-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libsub-handlesvia-perl/-/commit/e582b806c3c5978a1afa150bdb4f861bf44bd86a Add patch from upstream PR to fix test failure with newer Object::Pad. Thanks: Santiago Vila for the bug report. Closes: #1081869 (this message was generated automatically) -- Greetings https://bugs.debian.org/1081869
Bug#1081821: marked as pending in libimager-perl
Control: tag -1 pending Hello, Bug #1081821 in libimager-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libimager-perl/-/commit/9dc34d13ec3cda4b2f11fdf3f94240bdf141ef97 Add patch from Niko Tyno for compatibility with FreeType 2.13.3. Closes: #1081821 (this message was generated automatically) -- Greetings https://bugs.debian.org/1081821
Bug#1081701: marked as pending in libglib-object-introspection-perl
Control: tag -1 pending Hello, Bug #1081701 in libglib-object-introspection-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libglib-object-introspection-perl/-/commit/5610eea59144b6686cfb86f0b1295c8c833eab0f Add proposed patch to fix test failures with gobject-introspection 1.81.x Closes: #1081701 Thanks: Emmanuele Bassi (this message was generated automatically) -- Greetings https://bugs.debian.org/1081701
Bug#1075589: marked as pending in tuxguitar
Control: tag -1 pending Hello, Bug #1075589 in tuxguitar reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/tuxguitar/-/commit/ead951af438d55ae7db42c5e28120540aef472e3 Import Debian changes 1.6.4+dfsg1-1 tuxguitar (1.6.4+dfsg1-1) unstable; urgency=medium . * QA upload. * New upstream release (Closes: #1063268) * Upstream removed package tuxguitar-oss (Closes: #1075589) * TuxGuitar now supports custom tuning presets (Closes: #590982) * Merged package tuxguitar-jsa into tuxguitar (default audio output method) * debian/*: - Updated all debian files to the new upstream source directory structure and new file names * debian/control: - Updated dependencies - Updated upstream homepage * debian/copyright: - Updated upstream contact and source repository - Updated copyright holders * debian/rules: - Replace the pseudo build version 9.99-SNAPSHOT by the current Version of TuxGuitar in all xml and html files because upstream changed the way the upstream tarballs are provided - Added --buildsystem=maven to dh_auto_configure to make sure that mh_patchpoms is called * debian/watch: - Updated upstream download URL * debian/upstream/metadata: - Updated upstream source repository from SF to Github * debian/source/lintian-overrides updated * debian/tuxguitar.desktop removed (upstream version can be used now) * debian/tuxguitar.triggers added * /debian/patches/: - 04-hardening-cppflags.patch updated - 10-fix-CVE-2020-14940.patch removed (fixed upstream) - 11-eclipse-swt.patch updated - 12-remove-thirth-party-libs.patch updated - 13-remove-vst.patch removed (VST plugin was removed upstream) - 14-replace-soundfont.patch updated - 15-path-to-lv2.patch updated - 16-fix-cflags.patch updated - 26-tuxguitar-sh.patch added (replaces debian/tuxguitar.sh) (this message was generated automatically) -- Greetings https://bugs.debian.org/1075589
Bug#1076788: adequate: Messes up the console apt was running from
On Thu, 15 Aug 2024 23:20:13 +0200, Serafeim Zanikolas wrote: > awesome, thanks guys! Thanks to you for tracking down and fixing the issue in the go code :) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1076788: adequate: Messes up the console apt was running from
On Wed, 14 Aug 2024 23:21:35 +0200, Serafeim Zanikolas wrote: > I was able to reproduce the issue and have uploaded what I believe to be a > fix, > as 0.16.12 in experimental. please verify. I can confirm that I can't reproduce the bug anymore after upgrading to 0.16.12. Thanks! Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1076788: adequate: Messes up the console apt was running from
On Tue, 13 Aug 2024 23:59:52 +0200, Serafeim Zanikolas wrote: > thank you both. I'm tagging this as help as I can't even reproduce the issue > at > this point. Hm … > # emulate effect of preinst hook > echo bash | sudo tee /var/lib/adequate/pending > > # emulate self-spawning from postinst hook > debconf -oadequate -- adequate --debconf --pending In a fresh root shell (bash under urxvt): Let's check # cat /var/lib/adequate/pending adequate Interesting that this is still there; the file is from 16:50 localtime, probably when I reinstalled … Oh, I currently have 0.16.10 installed. Let's upgrade to 0.16.11. /var/lib/adequate/pending is now empty and is from now(). bash has no job control any more … New root shell. # echo bash > /var/lib/adequate/pending # debconf -oadequate -- adequate --debconf --pending No output, no damaged shell apparently. # echo bash > /var/lib/adequate/pending # adequate --debconf --pending bash lost job control. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1076788: adequate: Messes up the console apt was running from
On Tue, 13 Aug 2024 03:16:58 +0300, Antti Kultanen wrote: > > I've now been able to reproduce the entire issue and uploaded 0.16.11 to > > experimental. I'll wait on your feedback before uploading also to unstable. > unfortunately 0.16.11 regresses back to the original broken behavior: > my text console login shells terminate (tested: zsh, sash) and shells inside > screen or ssh session lose job control (tested: zsh, bash). Same here: logout on text console (bash), job control broken in terminal emulator (urxvt/bash). Good news: the needrestart hook is not backgrounded anymore. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1076788: adequate: Messes up the console apt was running from
On Sun, 11 Aug 2024 23:41:54 +0200, Serafeim Zanikolas wrote: > > Bug #1076788 [adequate] adequate: Messes up the console apt was running from > I can reproduce the loss of job control but not exiting the shell. I've seen both: the broken job control in a terminal emulator under X11, the exit-from-shell in a plain kernel console. > anyway, > 0.16.10 in experimental fixes the job control issue for me. 0.16.10 from experimental installed, and: It's getting better but something is still weird. Tested in a kernel console, logged in as root directly into bash; and in urxvt with zsh as gregoa -> su -> bash as root; effect is the same: A shortened log with some comments addedd: # apt reinstall adequate Summary: Upgrading: 0, Installing: 0, Reinstalling: 1, Removing: 0, Not Upgrading: 6 Download size: 0 B / 803 kB Space needed: 0 B / 28.1 GB available (Reading database ... 566177 files and directories currently installed.) Preparing to unpack .../adequate_0.16.10_amd64.deb ... Unpacking adequate (0.16.10) over (0.16.10) ... Setting up adequate (0.16.10) ... Processing triggers for man-db (2.12.1-3) ... ↑ everything fine so far localepurge: Disk space freed: 0 KiB in /usr/share/locale […] ↑ still everyhing ok == How can you help? (doc: https://wiki.debian.org/how-can-i-help ) == […] ↑ nothing interesting ↓ this is needrestart starting Scanning processes... Scanning candidates... Scanning processor microcode... Scanning linux images... Running kernel seems to be up-to-date. The processor microcode seems to be up-to-date. Restarting services... Daemons using outdated libraries 1. cron 2. geoclue (Enter the items or ranges you want to select, separated by spaces.) [1]+ Stopped apt reinstall adequate ↑ oops, the needrestart hook is backgrounded? ↓ let's fg it. it still works. # fg apt reinstall adequate Which services should be restarted? 1 2 invoke-rc.d cron restart invoke-rc.d geoclue restart […] # ↑ finished, shell seems to be healthy Now how the adequate hooks messes with the later needrestart hook -- no idea … (needrestart asking questions, maybe?) After removing adequate the phenomenon with the backgrounded needrestart hook ist gone. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1072429: libmediascan: FTBFS with ffmpeg 7.0: result.c:386:29: error: ‘AVCodecContext’ has no member named ‘channels’
On Sun, 02 Jun 2024 15:21:32 +0200, Sebastian Ramacher wrote: > > result.c:386:29: error: ‘AVCodecContext’ has no member named ‘channels’ > > 386 | a->channels = codecs->ac->channels; > > | ^~ I've pushed [0] a patch to the Git repo replacing all ->channels with the newer API. Tests pass … But I don't really know if this all works as intended … Cheers, gregor [0] https://salsa.debian.org/perl-team/modules/packages/libmediascan/-/commit/1a9d7a8716f812271e37cf9cc643359f44d94688 -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1072429: marked as pending in libmediascan
Control: tag -1 pending Hello, Bug #1072429 in libmediascan reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libmediascan/-/commit/1a9d7a8716f812271e37cf9cc643359f44d94688 Add patch to adjust to ffmpeg 7.0 API. Closes: #1072429 (this message was generated automatically) -- Greetings https://bugs.debian.org/1072429
Bug#1074938: epic4: diff for NMU version 1:2.10.10-1.2
Control: tags 1074938 + pending Dear maintainer, I've prepared an NMU for epic4 (versioned as 1:2.10.10-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- diff -Nru epic4-2.10.10/debian/changelog epic4-2.10.10/debian/changelog --- epic4-2.10.10/debian/changelog 2024-04-19 18:46:14.0 +0200 +++ epic4-2.10.10/debian/changelog 2024-08-10 04:03:31.0 +0200 @@ -1,3 +1,13 @@ +epic4 (1:2.10.10-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix "ftbfs with GCC-14": +- Niko Tyni: Run dh_autoreconf before the build. +- Niko Tyni: add patch fix-configure-probes-for-sockaddr_storag.patch +(Closes: #1074938) + + -- gregor herrmann Sat, 10 Aug 2024 04:03:31 +0200 + epic4 (1:2.10.10-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru epic4-2.10.10/debian/control epic4-2.10.10/debian/control --- epic4-2.10.10/debian/control 2020-08-24 15:15:16.0 +0200 +++ epic4-2.10.10/debian/control 2024-08-10 04:00:38.0 +0200 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Kurt Roeckx Standards-Version: 3.8.3 -Build-depends: debhelper (>= 5), libncurses5-dev, libssl-dev, libperl-dev +Build-depends: debhelper (>= 5), libncurses5-dev, libssl-dev, libperl-dev, dh-autoreconf Homepage: http://www.epicsol.org/ Package: epic4 diff -Nru epic4-2.10.10/debian/patches/fix-configure-probes-for-sockaddr_storag.patch epic4-2.10.10/debian/patches/fix-configure-probes-for-sockaddr_storag.patch --- epic4-2.10.10/debian/patches/fix-configure-probes-for-sockaddr_storag.patch 1970-01-01 01:00:00.0 +0100 +++ epic4-2.10.10/debian/patches/fix-configure-probes-for-sockaddr_storag.patch 2024-08-10 03:57:34.0 +0200 @@ -0,0 +1,54 @@ +From: Niko Tyni +Date: Fri, 2 Aug 2024 09:31:19 +0100 +X-Dgit-Generated: 1:2.10.10-1.1 0171eb699acbdd8569c31b2a5ebe0ac173571ed3 +Subject: Fix configure probes for sockaddr_storage et al on glibc >= 2.39 + +glibc 2.39 changed the socket headers to include the may_alias attribute +in https://sourceware.org/git/?p=glibc.git;a=commit;h=26e7005728 + + -struct sockaddr + +struct __attribute_struct_may_alias__ sockaddr + +This makes the tightly specified regex in the corresponding +AC_EGREP_HEADER probe miss the definition. + +Pre-emptively loosen other AC_EGREP_HEADER as well. + +--- + +diff --git a/configure.in b/configure.in +index 50cc684..d1e5fd4 100644 +--- a/configure.in b/configure.in +@@ -297,7 +297,7 @@ dnl check for struct linger + dnl + + AC_MSG_CHECKING(for struct linger) +-AC_EGREP_HEADER([struct( | )*linger], sys/socket.h, ++AC_EGREP_HEADER([struct.*linger], sys/socket.h, + AC_MSG_RESULT(yes), + AC_DEFINE(NO_STRUCT_LINGER) + AC_MSG_RESULT(no. ugh.)) +@@ -518,19 +518,19 @@ AC_ARG_WITH(ipv6, + ],[AC_MSG_RESULT(yes)]) + + AC_MSG_CHECKING(for struct sockaddr_storage) +-AC_EGREP_HEADER([struct( | )*sockaddr_storage], sys/socket.h, ++AC_EGREP_HEADER([struct.*sockaddr_storage], sys/socket.h, + AC_MSG_RESULT(yes) + AC_DEFINE(HAVE_STRUCT_SOCKADDR_STORAGE), + AC_MSG_RESULT(no)) + + AC_MSG_CHECKING(for struct sockaddr_in6) +-AC_EGREP_HEADER([struct( | )*sockaddr_in6], netinet/in.h, ++AC_EGREP_HEADER([struct.*sockaddr_in6], netinet/in.h, + AC_MSG_RESULT(yes) + AC_DEFINE(HAVE_STRUCT_SOCKADDR_IN6), + AC_MSG_RESULT(no)) + + AC_MSG_CHECKING(for struct addrinfo) +-AC_EGREP_HEADER([struct( | )*addrinfo], netdb.h, ++AC_EGREP_HEADER([struct.*addrinfo], netdb.h, + AC_MSG_RESULT(yes) + AC_DEFINE(HAVE_STRUCT_ADDRINFO), + AC_MSG_RESULT(no)) diff -Nru epic4-2.10.10/debian/patches/series epic4-2.10.10/debian/patches/series --- epic4-2.10.10/debian/patches/series 2024-04-19 18:46:14.0 +0200 +++ epic4-2.10.10/debian/patches/series 2024-08-10 04:01:00.0 +0200 @@ -5,3 +5,4 @@ man.patch reproducible_build.patch implicit-function-declarations.patch +fix-configure-probes-for-sockaddr_storag.patch diff -Nru epic4-2.10.10/debian/rules epic4-2.10.10/debian/rules --- epic4-2.10.10/debian/rules 2020-08-24 15:15:16.0 +0200 +++ epic4-2.10.10/debian/rules 2024-08-10 04:00:38.0 +0200 @@ -11,6 +11,7 @@ build-indep: build-stamp build-stamp: dh_testdir + dh_autoreconf ./configure --prefix=/usr --mandir=/usr/share/man \ --with-ssl \ --with-ipv6 \ signature.asc Description: Digital Signature
Bug#1074972: ftpmirror: diff for NMU version 1.96+dfsg-16.1
Control: tags 1074972 + pending
Dear maintainer,
I've prepared an NMU for ftpmirror (versioned as 1.96+dfsg-16.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
diff -Nru ftpmirror-1.96+dfsg/debian/changelog ftpmirror-1.96+dfsg/debian/changelog
--- ftpmirror-1.96+dfsg/debian/changelog 2018-09-14 14:10:15.0 +0200
+++ ftpmirror-1.96+dfsg/debian/changelog 2024-08-10 03:39:18.0 +0200
@@ -1,3 +1,11 @@
+ftpmirror (1.96+dfsg-16.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix "ftbfs with GCC-14": add patch from ntyni to fix type confusion with
+Fan::Usage::LOG (Closes: #1074972)
+
+ -- gregor herrmann Sat, 10 Aug 2024 03:39:18 +0200
+
ftpmirror (1.96+dfsg-16) unstable; urgency=medium
* Package refreshment.
diff -Nru ftpmirror-1.96+dfsg/debian/patches/fix-type-confusion-with-fanusagelog.patch ftpmirror-1.96+dfsg/debian/patches/fix-type-confusion-with-fanusagelog.patch
--- ftpmirror-1.96+dfsg/debian/patches/fix-type-confusion-with-fanusagelog.patch 1970-01-01 01:00:00.0 +0100
+++ ftpmirror-1.96+dfsg/debian/patches/fix-type-confusion-with-fanusagelog.patch 2024-08-10 03:37:42.0 +0200
@@ -0,0 +1,25 @@
+From: Niko Tyni
+Date: Mon, 5 Aug 2024 08:04:58 +0100
+X-Dgit-Generated: 1.96+dfsg-16 9f666f759b9329781768efe594624838e1f5810a
+Subject: Fix type confusion with Fan::Usage::LOG
+
+The default is 5 in both DESTROY() below, and on the Perl side in
+Usage.pm. So presumably it's fine here as well.
+
+Bug-Debian: https://bugs.debian.org/1074972
+
+---
+
+diff --git a/Fan/Usage/Usage.xs b/Fan/Usage/Usage.xs
+index 0d45cc1..9c21876 100644
+--- a/Fan/Usage/Usage.xs
b/Fan/Usage/Usage.xs
+@@ -64,7 +64,7 @@ getrusage(who = RUSAGE_SELF)
+ CODE:
+ {
+ SV *sv = perl_get_sv("Fan::Usage::LOG", FALSE);
+- int log = sv ? SvIV(sv) : NULL;
++ int log = sv ? SvIV(sv) : 5;
+
+ if (!(RETVAL = malloc(sizeof(Usage
+ XSRETURN_UNDEF;
diff -Nru ftpmirror-1.96+dfsg/debian/patches/series ftpmirror-1.96+dfsg/debian/patches/series
--- ftpmirror-1.96+dfsg/debian/patches/series 2018-09-14 13:13:22.0 +0200
+++ ftpmirror-1.96+dfsg/debian/patches/series 2024-08-10 03:37:42.0 +0200
@@ -5,3 +5,4 @@
06-translated-files.diff
07-deal_with_unresolved_UIDs_and_GIDs.diff
00-fix-makefile.diff
+fix-type-confusion-with-fanusagelog.patch
signature.asc
Description: Digital Signature
Bug#1074973: fungw: diff for NMU version 1.2.1-3.1
Control: tags 1074973 + pending Dear maintainer, I've prepared an NMU for fungw (versioned as 1.2.1-3.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- diff -Nru fungw-1.2.1/debian/changelog fungw-1.2.1/debian/changelog --- fungw-1.2.1/debian/changelog 2023-06-12 17:09:29.0 +0200 +++ fungw-1.2.1/debian/changelog 2024-08-10 03:31:50.0 +0200 @@ -1,3 +1,11 @@ +fungw (1.2.1-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix "ftbfs with GCC-14": add patch frm ntyni to add explicit void pointer +cast for Perl user data. (Closes: #1074973) + + -- gregor herrmann Sat, 10 Aug 2024 03:31:50 +0200 + fungw (1.2.1-3) unstable; urgency=medium * change control file VCS references to Debian salsa packaging repo diff -Nru fungw-1.2.1/debian/patches/add-explicit-void-pointer-cast-for-perl-.patch fungw-1.2.1/debian/patches/add-explicit-void-pointer-cast-for-perl-.patch --- fungw-1.2.1/debian/patches/add-explicit-void-pointer-cast-for-perl-.patch 1970-01-01 01:00:00.0 +0100 +++ fungw-1.2.1/debian/patches/add-explicit-void-pointer-cast-for-perl-.patch 2024-08-10 03:30:02.0 +0200 @@ -0,0 +1,35 @@ +From: Niko Tyni +Date: Fri, 2 Aug 2024 08:44:28 +0100 +X-Dgit-Generated: 1.2.1-3 dd68747f561a8cb027d3a3d53cec0d1d48712da5 +Subject: Add explicit void pointer cast for Perl user data + +This fixes a compilation error on GCC 14. + +Quoting https://gcc.gnu.org/gcc-14/porting_to.html + + GCC no longer allows implicitly casting all pointer types to all + other pointer types. This behavior is now restricted to the void * + type and its qualified variations. + + To fix compilation errors resulting from that, you can add the + appropriate casts, and maybe consider using void * in more places + (particularly for old programs that predate the introduction of void * + into the C language). + +Bug-Debian: https://bugs.debian.org/1074973 + +--- + +diff --git a/libfungwbind/perl/fungw_perl.c b/libfungwbind/perl/fungw_perl.c +index 2b3a91e..a8580bc 100644 +--- a/libfungwbind/perl/fungw_perl.c b/libfungwbind/perl/fungw_perl.c +@@ -283,7 +283,7 @@ static int fgws_perl_init(fgw_obj_t *obj, const char *filename, const char *opts + PERL_SET_CONTEXT(ctx->interp); + perl_construct(ctx->interp); + obj->script_data = ctx; +- ctx->interp->perl_user_data = ctx; ++ ctx->interp->perl_user_data = (void *)ctx; + ctx->obj = obj; + ctx->freg_delay = 1; + diff -Nru fungw-1.2.1/debian/patches/series fungw-1.2.1/debian/patches/series --- fungw-1.2.1/debian/patches/series 2023-06-12 17:09:29.0 +0200 +++ fungw-1.2.1/debian/patches/series 2024-08-10 03:30:02.0 +0200 @@ -0,0 +1 @@ +add-explicit-void-pointer-cast-for-perl-.patch signature.asc Description: Digital Signature
Bug#1075197: libprelude: diff for NMU version 5.2.0-5.6
Dear maintainer, I've uploaded an NMU for libprelude (versioned as 5.2.0-5.6). The diff is attached to this message. Regards. -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- diff -Nru libprelude-5.2.0/debian/changelog libprelude-5.2.0/debian/changelog --- libprelude-5.2.0/debian/changelog 2024-04-28 01:13:06.0 +0200 +++ libprelude-5.2.0/debian/changelog 2024-08-09 02:03:31.0 +0200 @@ -1,3 +1,12 @@ +libprelude (5.2.0-5.6) unstable; urgency=medium + + * Non-maintainer upload. + * Add patch from Niko Tyni: +Fix idmef_class_get_child_attributes() return value. +Closes: #1075197 + + -- gregor herrmann Fri, 09 Aug 2024 02:03:31 +0200 + libprelude (5.2.0-5.5) unstable; urgency=medium * Non-maintainer upload. diff -Nru libprelude-5.2.0/debian/patches/fix-idmef_class_get_child_attributes-ret.patch libprelude-5.2.0/debian/patches/fix-idmef_class_get_child_attributes-ret.patch --- libprelude-5.2.0/debian/patches/fix-idmef_class_get_child_attributes-ret.patch 1970-01-01 01:00:00.0 +0100 +++ libprelude-5.2.0/debian/patches/fix-idmef_class_get_child_attributes-ret.patch 2024-08-09 02:01:38.0 +0200 @@ -0,0 +1,26 @@ +From: Niko Tyni +Date: Fri, 2 Aug 2024 20:50:01 +0100 +X-Dgit-Generated: 5.2.0-5.5 d5540bbe1d13013371cc058216cdd3365ce4abe7 +Subject: Fix idmef_class_get_child_attributes() return value + +This became a compile error with GCC 14: + + idmef-class.c:164:24: error: returning ‘int’ from a function with return type ‘const char **’ makes pointer from integer without a cast [-Wint-conversion] + +Bug-Debian: https://bugs.debian.org/1075197 + +--- + +diff --git a/src/idmef-class.c b/src/idmef-class.c +index 4d93334..c7281f8 100644 +--- a/src/idmef-class.c b/src/idmef-class.c +@@ -161,7 +161,7 @@ const char **idmef_class_get_child_attributes(idmef_class_id_t class, idmef_clas + + ret = is_child_valid(class, child); + if ( ret < 0 ) +-return ret; ++return NULL; + + return object_data[class].children_list[child].attributes; + } diff -Nru libprelude-5.2.0/debian/patches/series libprelude-5.2.0/debian/patches/series --- libprelude-5.2.0/debian/patches/series 2024-04-28 01:13:06.0 +0200 +++ libprelude-5.2.0/debian/patches/series 2024-08-09 02:01:38.0 +0200 @@ -14,3 +14,4 @@ 025-Fix-PyIOBase_Type.patch cross.patch configure-Fix-va_copy-check-for-Wimplicit-function-declar.patch +fix-idmef_class_get_child_attributes-ret.patch signature.asc Description: Digital Signature
Bug#1075172: marked as pending in libgraphics-libplot-perl
Control: tag -1 pending Hello, Bug #1075172 in libgraphics-libplot-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libgraphics-libplot-perl/-/commit/bc0ebd1266c089d8405f9fcbc8f375325af6fdf4 Add patch to drop nonsensical "constants" from .xs file. Closes: #1075172 (this message was generated automatically) -- Greetings https://bugs.debian.org/1075172
Bug#1075185: marked as pending in libmemcached-libmemcached-perl
Control: tag -1 pending Hello, Bug #1075185 in libmemcached-libmemcached-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libmemcached-libmemcached-perl/-/commit/2e35bcd3c2a5e745e5add134eba6b74e72f3156c Remove constant MEMCACHED_DEFAULT_PORT_STRING from debian/libmemcached/**. Closes: #1075185 (this message was generated automatically) -- Greetings https://bugs.debian.org/1075185
Bug#1075214: marked as pending in libtext-unaccent-perl
Control: tag -1 pending Hello, Bug #1075214 in libtext-unaccent-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libtext-unaccent-perl/-/commit/52dc46c706b2d9ec3f594c348dd10916e0fb9e9d Explicitly set HAS_VPRINTF, no longer defined by Perl. Closes: #1075214 (this message was generated automatically) -- Greetings https://bugs.debian.org/1075214
Bug#1078098: marked as pending in libcrypt-gcrypt-perl
Control: tag -1 pending Hello, Bug #1078098 in libcrypt-gcrypt-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libcrypt-gcrypt-perl/-/commit/1afebb2eafaa4dea48d5cc84e82b1fe8340a29b1 Add patch to fix build with GCC-14. Thanks: Niko Tyni for the patch. Closes: #1078098 (this message was generated automatically) -- Greetings https://bugs.debian.org/1078098
Bug#1078098: libcrypt-gcrypt-perl: Can't link/include C library 'gcrypt', aborting
On Wed, 07 Aug 2024 00:30:47 +0300, Niko Tyni wrote: > Rebuilding this package on current sid produces an empty package. Ouch. Once again … > So this is a GCC 14 related regression and is fixed by including > the gcrypt.h header with the version check. Patch attached. Great! > As for not failing the build, looks like the upstream part of that is > intentional so that CPAN testers don't report failures due to lack of > external libraries. Ack, quite common behaviour. > Not sure where that leaves us. Some solutions I can think of: > - patch Makefile.PL to use assert_lib() instead > - add a check in debian/rules to detect the failure > - call dh explicitly with --buildsystem=perl_makemaker > - change dh to fail the build if 'perl Makefile.PL' does not produce a > Makefile There is prior art for the first option (assert_lib()): % grep assert_lib ../*/debian/patches/* ../libauthen-krb5-simple-perl/debian/patches/fix-checklib-fail.patch:+assert_lib( ../libcrypt-dh-gmp-perl/debian/patches/fix-checklib-fail.patch:+ Devel::CheckLib::assert_lib(@dcl_args); ../libdata-structure-util-perl/debian/patches/fix-checklib-fail.patch:+assert_lib(); ../libipc-sharelite-perl/debian/patches/fix-checklib-fail.patch:+assert_lib(); ../libmath-tamuanova-perl/debian/patches/fix-checklib-fail.patch:+assert_lib( ../libopengl-xscreensaver-perl/debian/patches/fix-checklib-fail.patch:+assert_lib(lib => ['X11', 'GL']); > The last option is the only generic one, but might interfere > with the dh buildsystem automatic detection. Hm, something generic would be nice but I'm also a bit afraid of side effects. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1077440: marked as pending in libsys-hostip-perl
Control: tag -1 pending Hello, Bug #1077440 in libsys-hostip-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libsys-hostip-perl/-/commit/e0b0402183de5d91494ee5a9fbf088f497eeab87 Update patch to find `ip' in /usr/bin. Closes: #1077440 (this message was generated automatically) -- Greetings https://bugs.debian.org/1077440
Bug#1010115: marked as pending in libhtml-tidy5-perl
Control: tag -1 pending Hello, Bug #1010115 in libhtml-tidy5-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libhtml-tidy5-perl/-/commit/0a2d218b505acdc0097c4fe8693b233fdde585f4 Remove tests-tidy-html5-5.6.patch, activate tests-tidy-html5-5.8.patch. Closes: #1010115 (this message was generated automatically) -- Greetings https://bugs.debian.org/1010115
Bug#1077194: marked as pending in libmath-gsl-perl
Control: tag -1 pending Hello, Bug #1077194 in libmath-gsl-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libmath-gsl-perl/-/commit/c092d32e6e4dbaecf29f611b9737c95d862b6aee Add a patch from upstream Git to fix a test failure with GSL 2.8. Closes: #1077194 (this message was generated automatically) -- Greetings https://bugs.debian.org/1077194
Bug#1077194: libmath-gsl-perl: FTBFS on many architectures: test failure in t/Linalg.t
Source: libmath-gsl-perl Version: 0.45-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As seen at https://buildd.debian.org/status/logs.php?pkg=libmath-gsl-perl&ver=0.45-1 libmath-gsl-perl 0.45-1 has test failure on many architectures. Output from a manual test run in an i386 chroot: # prove --blib --verbose t/Linalg.t t/Linalg.t .. # # Math::GSL::Linalg::Test->GSL_GIVENS ok 1 - givens rotation with 1,0 # # Math::GSL::Linalg::Test->GSL_LINALG_BIDIAG_DECOMP_UNPACK_UNPACK2_UNPACK_B ok 2 - ok 3 - ok 4 - GSL LINALG BIDIAG DECOMP UNPACK UNPACK2 UNPACK B ok 5 - GSL LINALG BIDIAG DECOMP UNPACK UNPACK2 UNPACK B ok 6 - GSL LINALG BIDIAG DECOMP UNPACK UNPACK2 UNPACK B not ok 7 - GSL LINALG BIDIAG DECOMP UNPACK UNPACK2 UNPACK B # TODO look into this # Failed (TODO) test 'GSL LINALG BIDIAG DECOMP UNPACK UNPACK2 UNPACK B' # at t/Linalg.t line 434. # (in Math::GSL::Linalg::Test->GSL_LINALG_BIDIAG_DECOMP_UNPACK_UNPACK2_UNPACK_B) not ok 8 - GSL LINALG BIDIAG DECOMP UNPACK UNPACK2 UNPACK B # TODO look into this # Failed (TODO) test 'GSL LINALG BIDIAG DECOMP UNPACK UNPACK2 UNPACK B' # at t/Linalg.t line 435. # (in Math::GSL::Linalg::Test->GSL_LINALG_BIDIAG_DECOMP_UNPACK_UNPACK2_UNPACK_B) # # Math::GSL::Linalg::Test->GSL_LINALG_CHOLESKY_DECOMP ok 9 - ok 10 - GSL LINALG CHOLESKY DECOMP # # Math::GSL::Linalg::Test->GSL_LINALG_COMPLEX_LU_DET # # Elements start differing at index 0, delta = 6 # $x->[0] = 0 # $y->[0] = -6 not ok 11 - real # TODO $gsl_det is wrong or Math::Complex conversion is # Failed (TODO) test 'real' # at t/Linalg.t line 231. # (in Math::GSL::Linalg::Test->GSL_LINALG_COMPLEX_LU_DET) # # Elements start differing at index 0, delta = 8 # $x->[0] = -4 # $y->[0] = 4 not ok 12 - imag # TODO $gsl_det is wrong or Math::Complex conversion is # Failed (TODO) test 'imag' # at t/Linalg.t line 232. # (in Math::GSL::Linalg::Test->GSL_LINALG_COMPLEX_LU_DET) # # Math::GSL::Linalg::Test->GSL_LINALG_HESSENBERG_DECOMP_UNPACK_UNPACK_ACCUM_SET_ZERO ok 13 - ok 14 - ok 15 - GSL LINALG HESSENBERG DECOMP UNPACK UNPACK ACCUM SET ZERO ok 16 - GSL LINALG HESSENBERG DECOMP UNPACK UNPACK ACCUM SET ZERO ok 17 - GSL LINALG HESSENBERG DECOMP UNPACK UNPACK ACCUM SET ZERO ok 18 - GSL LINALG HESSENBERG DECOMP UNPACK UNPACK ACCUM SET ZERO ok 19 - GSL LINALG HESSENBERG DECOMP UNPACK UNPACK ACCUM SET ZERO ok 20 - GSL LINALG HESSENBERG DECOMP UNPACK UNPACK ACCUM SET ZERO ok 21 - GSL LINALG HESSENBERG DECOMP UNPACK UNPACK ACCUM SET ZERO ok 22 - GSL LINALG HESSENBERG DECOMP UNPACK UNPACK ACCUM SET ZERO ok 23 - GSL LINALG HESSENBERG DECOMP UNPACK UNPACK ACCUM SET ZERO ok 24 - GSL LINALG HESSENBERG DECOMP UNPACK UNPACK ACCUM SET ZERO ok 25 - GSL LINALG HESSENBERG DECOMP UNPACK UNPACK ACCUM SET ZERO ok 26 - GSL LINALG HESSENBERG DECOMP UNPACK UNPACK ACCUM SET ZERO ok 27 - ok 28 - ok 29 - Set zero ok 30 - Set zero ok 31 - Set zero # # Math::GSL::Linalg::Test->GSL_LINALG_LU_DECOMP not ok 32 - GSL LINALG LU DECOMP # Failed test 'GSL LINALG LU DECOMP' # at t/Linalg.t line 64. # (in Math::GSL::Linalg::Test->GSL_LINALG_LU_DECOMP) # Structures begin differing at: # $got->[0] = '0' # $expected->[0] = '4' ok 33 - resulting row 0 ok 34 - resulting row 1 ok 35 - resulting row 2 ok 36 - resulting row 3 # # Math::GSL::Linalg::Test->GSL_LINALG_LU_DET ok 37 - GSL LINALG LU DET # # Math::GSL::Linalg::Test->GSL_LINALG_LU_INVERT ok 38 - GSL LINALG LU INVERT ok 39 - GSL LINALG LU INVERT ok 40 - GSL LINALG LU INVERT ok 41 - GSL LINALG LU INVERT ok 42 - GSL LINALG LU INVERT ok 43 - GSL LINALG LU INVERT ok 44 - GSL LINALG LU INVERT ok 45 - GSL LINALG LU INVERT ok 46 - GSL LINALG LU INVERT ok 47 - GSL LINALG LU INVERT ok 48 - GSL LINALG LU INVERT ok 49 - GSL LINALG LU INVERT ok 50 - GSL LINALG LU INVERT ok 51 - GSL LINALG LU INVERT ok 52 - GSL LINALG LU INVERT ok 53 - GSL LINALG LU INVERT # # Math::GSL::Linalg::Test->GSL_LINALG_LU_LNDET ok 54 - GSL LINALG LU LNDET # # Math::GSL::Linalg::Test->GSL_LINALG_LU_SOLVE # # Math::GSL::Linalg::Test->GSL_LINALG_LU_SVX # # Math::GSL::Linalg::Test->GSL_LINALG_QR_DECOMP ok 55 - ok 56 - GSL LINALG QR DECOMP ok 57 - GSL LINALG QR DECOMP ok 58 - GSL LINALG QR DECOMP ok 59 - GSL LINALG QR DECOMP ok 60 - GSL LINALG QR DECOMP ok 61 - GSL LINALG QR DECOMP ok 62 - GSL LINALG QR DECOMP ok 63 - GSL LINALG QR DECOMP ok 64 - GSL LINALG QR DECOMP ok 65 - GSL LINALG QR DECOMP ok 66 - GSL LINALG QR DECOMP ok 67 - GSL LINALG QR DECOMP ok 68 - GSL LINALG QR DECOMP ok 69 - GSL LINALG QR DECOMP ok 70 - GSL LINALG QR DECOMP ok 71 - GSL LINALG QR DECOMP 1..71 # Looks like you failed 1 test of 71. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/71 subtests Test Summary Report - --- t/Linalg.t (Wstat: 256 (exited 1) Tests: 71 Failed: 1) Failed test: 32 Non-zero exit status:
Bug#1071967: marked as pending in libdata-fake-perl
Control: tag -1 pending Hello, Bug #1071967 in libdata-fake-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libdata-fake-perl/-/commit/005878ee5d7ce4fa522a665107fdd4edb95783e5 Add patch to workaround 32bit time failures. Closes: #1071967 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071967
Bug#1076488: src:libxml-libxslt-perl: fails to migrate to testing for too long: autopkgtest issues
On Wed, 17 Jul 2024 21:55:04 +0200, Paul Gevers wrote: > > This should fix itself once libxml-libxml-perl 2.0207+dfsg+really+2.0134-4 > > migrates (and libxml2). > That's a slight variant of "This is usually a missing > *versioned* (test) dependency in your reverse (test) dependencies or a > missing Breaks in this package or both. However, if this is *only* a > test issue, it's possible that it's considered wrong to declare that in > the package meta data; in that case reach out to the Release Team to > ignore the apparent autopkgtest regressions for this case." Right. > So, should libxml-libxslt-perl have a versioned Depends on > libxml-libxml-perl? Or vise versa, a versioned Breaks? We already tightend the dependencies between libxml-libxml-perl and libxml2 (the warnings are in libxml2, the perl module triggers them); I guess doing the same dance with all reverse-dependencies of libxml-libxml-perl for something that appears rarely (cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072012#62 ), wouldn't have shown up without libxml2 being blocked for a long time, and should hopefully be fixed by the migration of libxml-libxml-perl and libxml2 is overkill. So I guess I'd just wait (the new libxml-libxslt-perl version also has no groundbreaking changes); but I might miss something which others may add. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1076488: src:libxml-libxslt-perl: fails to migrate to testing for too long: autopkgtest issues
On Wed, 17 Jul 2024 06:57:01 +0200, Paul Gevers wrote: > The Release Team considers packages that are out-of-sync between testing and > unstable for more than 30 days as having a Release Critical bug in testing > [1]. Your package src:libxml-libxslt-perl has been trying to migrate for 31 > days [2]. This should fix itself once libxml-libxml-perl 2.0207+dfsg+really+2.0134-4 migrates (and libxml2). Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1074399: marked as pending in libcgi-application-plugin-authentication-perl
Control: tag -1 pending Hello, Bug #1074399 in libcgi-application-plugin-authentication-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libcgi-application-plugin-authentication-perl/-/commit/5d7045429a90a25f3613ce0a566f7a57139e79c0 Add patch for CGI.pm >= 4.66 compatibility. Taken from upstream Git commit. Thanks: Chris Peterson for the bug report. Closes: #1074399 LP: #2071369 (this message was generated automatically) -- Greetings https://bugs.debian.org/1074399
Bug#1072693: smiles-scripts: FTBFS (test failures) with newer libxml2 (or libxml-libxml-perl)
Source: smiles-scripts Version: 0.2.0+dfsg1-5 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On libxml-libxml-perl's tracker page I noticed that autopkgtest failures in smiles-scripts and had a look at the package. And it currently doesn't build, as the tests fail here as well: #v+ debian/rules override_dh_auto_test make[1]: Entering directory '/build/smiles-scripts-0.2.0+dfsg1' rm tests/cases/cdkcif2smiles_002.* rm tests/cases/cdkcif2smiles_003.* rm tests/cases/cdkcif2xyz_002.* rm tests/cases/cdkcif2xyz_003.* rm tests/cases/cdkdepict_001.* rm tests/cases/cdkdepict_004.* rm tests/cases/cdkdepict_005.* rm tests/cases/cdkdepict_006.* rm tests/cases/cdkdepict_008.* rm tests/cases/cdkdepict_009.* rm tests/cases/cdkdepict_010.* rm tests/cases/cdkdepict_022.* rm tests/cases/cdkdepict_023.* rm tests/cases/cdkdepict-cgi_001.* rm tests/cases/cdksdf2smiles_005.* rm tests/cases/cdksdf2smiles_007.* rm tests/cases/cdksdf2smiles_009.* rm tests/cases/cdksdf2smiles_010.* rm tests/cases/sdf-to-smi_002.* dh_auto_test -- MODULE_BUILD_PARSE_YAPP= CHEMISTRY_OPENSMILES= make -j4 test MODULE_BUILD_PARSE_YAPP= CHEMISTRY_OPENSMILES= make[2]: Entering directory '/build/smiles-scripts-0.2.0+dfsg1' find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory find: 'externals': No such file or directory tests/cases/cdkcif2smiles_001.opt: tests/cases/cdkcif2xyz_001.opt: tests/cases/cdkdepict-cgi_002.sh: tests/cases/cdkdepict_002.inp: OK tests/cases/cdkdepict_003.opt: OK tests/cases/cdkdepict_007.inp: OK tests/cases/cdkdepict_021.opt: OK tests/cases/cdkrecharge_001.opt: OK FAILED: tests/cases/cdkrecharge_002.sh:1c1 < cdkdepict: tests/cases/cdkdepict_007.inp(1): ERROR, org.openscience.cdk.exception.InvalidSmilesException: could not parse 'n11', a valid kekulé structure could not be assigned - --- > cdkdepict: tests/cases/cdkdepict_007.inp(1): ERROR, > org.openscience.cdk.exception.InvalidSmilesException: could not parse > 'n11', a valid kekul? structure could not be assigned tests/cases/cdkrecharge_003.opt: OK tests/cases/cdkrecharge_004.opt: OK tests/cases/cdkrecharge_005.opt: OK tests/cases/cdkrecharge_006.inp: OK tests/cases/cdkrecharge_007.opt: OK OK tests/cases/cdkrecharge_008.inp: OK tests/cases/cdkrecharge_009.opt: tests/cases/cdkrecharge_010.opt: OK tests/cases/cdkrecharge_011.opt: OK OK tests/cases/cdkrecharge_012.inp: tests/cases/cdkrecharge_013.inp: OK tests/cases/cdkrecharge_014.inp: OK tests/cases/cdkrecharge_015.inp: OK tests/cases/cdkrecharge_016.sh:OK tests/cases/cdkrecharge_017.sh:OK tests/cases/cdkrecharge_018.inp: OK tests/cases/cdkrecharge_019.inp: OK OK tests/cases/cdkrecharge_020.inp: tests/cases/cdksdf2smiles_001.opt: OK tests/cases/cdksdf2smiles_002.inp: OK tests/cases/cdksdf2smiles_003.inp: OK tests/cases/cdksdf2smiles_004.inp: OK tests/cases/cdksdf2smiles_006.inp: OK tests/cases/cdksdf2smiles_008.inp: OK tests/cases/cml-to-smi_001.inp:OK tests/cases/cml-to-smi_002.inp:OK tests/cases/cml-to-smi_003.inp:OK tests/cases/cml-to-smi_004.inp:OK tests/cases/cml-to-smi_005.inp:OK tests/cases/cml-to-smi_006.inp:OK tests/cases/cml-to-smi_007.inp:FAILED: 10,12d9 < tests/cases/cml-to-smi_005.inp:2: parser error : Extra content at the end of the document < g/schema" id="id/opt/eprints3/archives/ecrystals/documents/disk0/00/00/07/15/01/ < ^ tests/cases/cml-to-smi_008.inp:OK tests/cases/cml-to-smi_009.i
Bug#1072012: libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11
On Wed, 29 May 2024 23:15:10 +0300, Niko Tyni wrote: > But I think we should add dependency metadata so that the release team, > britney, debci etc. can see the need for a rebuild when we have a > "broken" combination, and then hint the "correct" versions for testing > migration together. Updating libxml2 "middle version" would then mean > a mini-transition. Ack. > At the moment that would mean having libxml-libxml-perl > Depends: libxml2 (>> 2.12), libxml2 (<< 2.13~) > or something like that, with the numbers automatically generated during > the build of course. Implemented in 2.0207+dfsg+really+2.0134-3: Depends: perl (>= 5.38.2-5), perlapi-5.38.2, libc6 (>= 2.14), libxml2 (>= 2.12), libxml2 (<< 2.13~), libxml-namespacesupport-perl, libxml-sax-perl On Fri, 31 May 2024 15:12:03 +0800, Aron Xu wrote: > I'm fine with the resolution and I have committed a similar thing to > libxml2 following gregoa's advice: > https://salsa.debian.org/xml-sgml-team/libxml2/-/commit/f0f2fc3a207aed66e651b0d75ecea2d9b2028c8c Thanks, please adjust the Breaks to Breaks: libxml-libxml-perl (<< 2.0207+dfsg+really+2.0134-3~), Also, please don't close _this_ bug in the upload; getting the dependency meta-information in order should fix the autopkgtest failures, but the core problem most probably will persist: The test failures on several architectures which makes the package FTBFS: https://buildd.debian.org/status/package.php?p=libxml-libxml-perl Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1072012: libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11
On Wed, 29 May 2024 14:16:47 +0800, Aron Xu wrote:
> > They all seem to fail with:
> > Warning: program compiled against libxml 212 using older 209
> >
> > and this comes from libxml:
> >
> > if ((myversion / 100) < (version / 100)) {
> > xmlGenericError(xmlGenericErrorContext,
> > "Warning: program compiled against libxml %d using older
> > %d\n",
> > (version / 100), (myversion / 100));
> > }
> >
> >
> > Not sure if this is should be fixed in libxml2 or if we should add an
> > artifical dependency on a newer libxml2 (to avoid testing against the
> > version in testing). The former sounds more logic to me.
>
> Although it looks trivial to remove the warning from libxml2, I'm
> reluctant since this piece of code existed for a very long time, a
> random check shows that version 2.2.3 (in 2000) has the logic:
> https://gitlab.gnome.org/GNOME/libxml2/-/blob/04698d9e1c56467007fcbb9472e5db67cf5938f5/parserInternals.c#L66
Maybe an alternative is to add
Breaks: libxml-libxml-perl (<< 2.0207+dfsg+really+2.0134-2~)
to libxml2?
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`- BOFH excuse #351: PEBKAC (Problem Exists Between Keyboard And Chair)
Bug#1072012: libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11
On Mon, 27 May 2024 22:33:45 +0200, gregor herrmann wrote: > … on amd64 and some other architectures; on others the testsuite now > fails in t/13dtd.t with SIGSEGV or SIGBUS etc.: > https://buildd.debian.org/status/package.php?p=libxml-libxml-perl Additionally the upload triggers a gazillion of autopkgtest failures in reverse dependencies: Issues preventing migration: ∙ ∙ autopkgtest for libatteanx-endpoint-perl/0.002-6: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libauthen-cas-client-perl/0.08-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libcatmandu-fedoracommons-perl/0.5-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libcatmandu-xsd-perl/0.05-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libhtml-html5-builder-perl/0.004-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libhtml-html5-microdata-parser-perl/0.100-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libhtml-html5-outline-perl/0.006-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libhtml-html5-parser-perl/0.992-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libhtml-html5-sanity-perl/0.105-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libhtml-html5-writer-perl/0.201-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libhtml-microformats-perl/0.105-6: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libhtml-treebuilder-libxml-perl/0.26-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libhttp-oai-perl/4.13-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libmarc-parser-xml-perl/0.03-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libmarc-xml-perl/1.0.5-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libnet-amazon-s3-perl/0.991-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libnet-amqp-perl/0.06~dfsg-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libnet-epp-perl/0.27-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for libnetsds-kannel-perl/1.300-7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ ∙ ∙ autopkgtest for libpoe-filter-xml-perl/1.140700-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for librdf-closure-perl/0.001-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), riscv64: Pass ∙ ∙ autopkgtest for librdf-endpoint-perl/0.11-2: amd64: Regression or new test ♻ (reference
Bug#1072012: libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11
Control: reopen -1 On Mon, 27 May 2024 19:03:56 +0200, gregor herrmann wrote: > As a quick bandaid to fix the FTBFS bug and unblock libxml2, I've > prepared an upload with only the one upstream commit added as an > additional quilt patch (which makes the test suite pass on sid and > trixie, i.e. with libxml2 2.9.14 and 2.12.7); … on amd64 and some other architectures; on others the testsuite now fails in t/13dtd.t with SIGSEGV or SIGBUS etc.: https://buildd.debian.org/status/package.php?p=libxml-libxml-perl So we are back to a FTBFS bug … Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1072012: marked as pending in libxml-libxml-perl
Control: tag -1 pending Hello, Bug #1072012 in libxml-libxml-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libxml-libxml-perl/-/commit/19087d56ec2f5d800155eb3a4bb2c2e6ad87e058 Add patch from upstream Git repo (and 2.0209 release) to fix a test failure with libxml2 >= 2.11. Thanks: Aron Xu for the bug report. Closes: #1072012 (this message was generated automatically) -- Greetings https://bugs.debian.org/1072012
Bug#1072012: libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11
Control: clone -1 -2 Control: retitle -1 libxml-libxml-perl: FTBFS with libxml2 >= 2.11 Control: retitle -2 libxml-libxml-perl: update to current upstream release Control: severity -2 normal Control: tags -2 = trixie sid On Mon, 27 May 2024 22:12:06 +0800, Aron Xu wrote: > libxml2 has been updated to upstream 2.12.7 release and the > autopkgtest shows regressions[1] regarding libxml-libxml-perl: Thanks! > 72s t/35huge_mode.t > 72s 1..5 > 72s ok 1 - huge mode disabled by default > 72s not ok 2 - exception thrown during parse > 72s > 72s # Failed test 'exception thrown during parse' > 72s # at t/35huge_mode.t line 56. > 72s # got: '' > 72s # expected: anything else > 72s not ok 3 - exception refers to entity reference loop > 72s > 72s # Failed test 'exception refers to entity reference loop' > 72s # at t/35huge_mode.t line 57. > 72s # '' > 72s # doesn't match '(?^si:entity.*loop)' > 72s ok 4 - no exception thrown during parse > 72s ok 5 - entity was parsed and expanded correctly > 72s # Looks like you failed 2 tests of 5. > 72s Dubious, test returned 2 (wstat 512, 0x200) > 72s Failed 2/5 subtests This also makes the package FBTFS in sid, therefore I've raised the severity of the (original) bug report. > It appears that upstream has fixed this issue in 2.0209 with commit > 57e712c9[2]. Since we have only 2.0207 in sid, I therefore request to > update this package to the latest upstream release, 2.0210, which > would help unblock the migration of libxml2 to testing. Well, actually we have 2.0207+dfsg+really+2.0134-1 in Debian, i.e. upstream 2.0134; d/changelog reads: [ Niko Tyni] * Temporarily revert to upstream version 2.0134 while changes in external DTD handling are revisited upstream. Thanks to Vincent Lefevre for the reports. (Closes: #1005281, #1003810) -- Niko Tyni Fri, 11 Feb 2022 21:29:49 +0200 Uploading 2.0210 would be desirable, but needs checking of those bugs and other changes, and also involves some work as the structure of the distribution has changed. As a quick bandaid to fix the FTBFS bug and unblock libxml2, I've prepared an upload with only the one upstream commit added as an additional quilt patch (which makes the test suite pass on sid and trixie, i.e. with libxml2 2.9.14 and 2.12.7); I'm now also cloning the bug as a reminder that we need to invest the time to try and update to a newer upstream version. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1066575: kakasi: diff for NMU version 2.3.6-4.2
Control: tags 1066575 + patch
Control: tags 1066575 + pending
Dear maintainer,
I've prepared an NMU for kakasi (versioned as 2.3.6-4.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
diff -Nru kakasi-2.3.6/debian/changelog kakasi-2.3.6/debian/changelog
--- kakasi-2.3.6/debian/changelog 2021-01-03 12:25:42.0 +0100
+++ kakasi-2.3.6/debian/changelog 2024-05-26 18:34:15.0 +0200
@@ -1,3 +1,12 @@
+kakasi (2.3.6-4.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix "FTBFS: configure: error: can not use EUC-JP or UTF-8 encoding
+on iconv": add patch kakasi-configure-c99.patch from Fedora.
+(Closes: #1066575)
+
+ -- gregor herrmann Sun, 26 May 2024 18:34:15 +0200
+
kakasi (2.3.6-4.1) unstable; urgency=medium
* Non maintainer upload by the Reproducible Builds team.
diff -Nru kakasi-2.3.6/debian/patches/kakasi-configure-c99.patch kakasi-2.3.6/debian/patches/kakasi-configure-c99.patch
--- kakasi-2.3.6/debian/patches/kakasi-configure-c99.patch 1970-01-01 01:00:00.0 +0100
+++ kakasi-2.3.6/debian/patches/kakasi-configure-c99.patch 2024-05-26 18:34:08.0 +0200
@@ -0,0 +1,20 @@
+Origin: https://src.fedoraproject.org/rpms/kakasi/blob/rawhide/f/kakasi-configure-c99.patch
+Bug-Debian: https://bugs.debian.org/1066575
+
+Avoid an implicit declaration of exit and build failures with future
+compilers which do not support implicit function declarations by
+default.
+
+diff --git a/configure.in b/configure.in
+index e865b04ffd027f3c..4a15beffd0e252a4 100644
+--- a/configure.in
b/configure.in
+@@ -85,7 +85,7 @@ AS_VAR_IF(utf8, "yes",[
+ LIBS="$LIBICONV $LIBS"
+ AC_DEFINE(KAKASI_SUPPORT_UTF8, 1, [KAKASI_SUPPORT_UTF8])
+ AC_RUN_IFELSE([AC_LANG_PROGRAM([#include ],
+- [if (iconv_open("EUC-JP", "UTF-8") == -1) exit(1);])],
++ [if (iconv_open("EUC-JP", "UTF-8") == -1) return 1;])],
+ [],
+ [AC_MSG_ERROR([can not use EUC-JP or UTF-8 encoding on iconv])])
+ ])
diff -Nru kakasi-2.3.6/debian/patches/series kakasi-2.3.6/debian/patches/series
--- kakasi-2.3.6/debian/patches/series 2018-12-02 10:10:55.0 +0100
+++ kakasi-2.3.6/debian/patches/series 2024-05-26 18:30:47.0 +0200
@@ -1,2 +1,3 @@
0003-prefix.patch
0004-multiarch.patch
+kakasi-configure-c99.patch
signature.asc
Description: Digital Signature
Bug#1071967: libdata-fake-perl: Test failures on 32bit architectures
Source: libdata-fake-perl Version: 0.006-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source Forwarded: https://github.com/dagolden/Data-Fake/issues/15 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 t/dates.t fails on i386, looks like time_t 32 bit issues (via Time::Piece's strptime). https://ci.debian.net/packages/libd/libdata-fake-perl/testing/i386/46574760/#S6 Cf. https://github.com/dagolden/Data-Fake/issues/15 This (autopkgtest) failure blocks migration to testing, and also appears during build in an i386 chroot. Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmZTXwRfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbqUQ//alYyFmLcn9TQX4DJghlWRA07qlL7FkHwlYz7MTKzZwDGwNVkKV2vMDys X+bI0nT57TNX/QTsxBQZ5CbAeOIRkefd/J7unE5+LSvdnXJN0P80gxcL0Oja0T7Q dvieqShF7xll2h0y/D2swB+6GCTQZngfo6wx8ty6OG3pFAu2zaXL0sNiUvkjEMA1 vwi8/jEy2f5tz+PFJULS0SQfkcsf3dSzTBWJe8xjANOTithBzyPqbe3NI5A2Dk+F icAw90oOKotgciTHm2qufpp+AtCDr+QJQOaa085KiGleVwk0HSIoInZsriH6Hoxj E2buKvrMQSZ3EqfziS5u7EILnikV+ihGU27ZLbDTNPnIqsUmETRa5WNlRfC0PSu3 n0o6nCWp8lSpXsV4VafXDHwaQQyzjkzHH69UrQWUYLVC2CvG3hG5TW2of+UGa0aq zpmgI/GVjVmbD6Lpga6t5Ni+4RcPSTSXfIIf4dJCYCQZmEhmqJrvMxbuSIehaH1r BfggsEjrk8QBoDpcCGGcUJQCFBMEX7pbBJVnTg6mQowKZvc8Qj6ELvPZREvEpm4N jcbD/aD6m1VsTtP1aSoEDrkD8qdJzmrV0bsAy90zyR1TNl1HLyzl6eKvBWG08C8m 4I3gIY+ADEWTNYhr+yjn5LaXDEuWNHnONeN/32Bzmxlqjyn5MMw= =nwHw -END PGP SIGNATURE-
Bug#1071326: marked as pending in libnet-interface-perl
Control: tag -1 pending Hello, Bug #1071326 in libnet-interface-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libnet-interface-perl/-/commit/6b5581714b0869a7e0cd232131a0c5b26811b65f debian/rules: set buildflags. Take from Ubuntu's 1.016-2ubuntu1 upload, which has the following changelog entry from Matthias Klose : * d/rules: Work around test failures. See https://rt.cpan.org/Public/Bug/Display.html?id=57413. export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-fortify export DEB_CFLAGS_MAINT_APPEND = -D_FORTIFY_SOURCE=0 The second one is necessary, because dpkg-buildflags doesn't disable these flags turned on by default in GCC. See LP 2049686. Closes: #1071326 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071326
Bug#1071326: libnet-interface-perl: FTBFS: failing tests
Control: tag -1 + confirmed On Fri, 17 May 2024 22:39:03 +0200, Santiago Vila wrote: > *** buffer overflow detected ***: terminated > t/simplesets.t > 1..2 > ok 1 - use Net::Interface; > Failed 1/2 subtests Thanks for your bug report! I can confirm it in a sid cowbuilder chroot, also when running the test manually: # prove --blib --verbose t/simplesets.t t/simplesets.t .. 1..2 ok 1 - use Net::Interface; *** buffer overflow detected ***: terminated Failed 1/2 subtests Test Summary Report --- t/simplesets.t (Wstat: 134 (Signal: ABRT, dumped core) Tests: 1 Failed: 0) Non-zero wait status: 134 Parse errors: Bad plan. You planned 2 tests but ran 1. Files=1, Tests=1, 0 wallclock secs ( 0.03 usr 0.00 sys + 0.05 cusr 0.01 csys = 0.09 CPU) Result: FAIL No idea what's going on there yet :) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1069101: libdbd-oracle-perl: requires rebuild for time_t transition
On Thu, 09 May 2024 16:41:10 +0200, Alex Muntada wrote: > > > It turns out that it's oracle-instantclient-basic that needs > > > libaio.so.1. I'm not sure what could be done to address this > > > issue, since the soname renaming to libaio.so.1t64 is Debian > > > specific. > > I came up with an easy solution to this: since libaio.so.1 is > required by oracle-instantclient-basic (not in Debian), we could > add libaio (from Oracle Linux) in Depends and then explain in > README.Debian to download it from Oracle, build the .deb with > alien and install it, like the other external dependencies. Sounds viable to me, with good instructions in the README.Debian downloading alien'ing two packages instead of one shouldn't be too terrible for users. > The thing is that maybe a hint on libaio will be needed? What do you mean be "hint" here? Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1069247: libconfig-model-dpkg-perl: test failures
Control: reassign 1069247 apt 2.9.0 Control: reassign 1069246 apt 2.9.0 Control: forcemerge 1069247 1069246 Control: retitle 1069247 apt: apt 2.9.0's output breaks libapt-pkg-perl Control: affects 1069247 + libapt-pkg-perl libconfig-model-dpkg-perl dh-make-perl Control: tag 1069247 = sid Control: fixed 1069247 2.9.2 On Mon, 22 Apr 2024 19:44:38 +0200, Julian Andres Klode wrote: > On Mon, Apr 22, 2024 at 07:41:42PM +0200, Dominique Dumont wrote: > > On Sunday, 21 April 2024 18:07:00 CEST Julian Andres Klode wrote: > > > This should be fixed in apt git already, just needs an upload, > > > which is waiting-ish for some more merges > > Given [1], I need to ask... > > Is this a definitive fix or will this feature come back with apt 3.0 ? … > This should be fixed in apt side on 2.9.2 I just uploaded, but > either way it's a weird thing to break because we change progress > messages for interactive output, maybe run with -q instead or don't > pretend to be a tty. I can confirm that the issues in dh-make-perl's and libconfig-model-dpkg-perl's test suites (via libapt-pkg-perl) are gone with apt 2.9.2. Thanks! (Further change requests should probably go to libapt-pkg-perl, if necessary.) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1069247: libconfig-model-dpkg-perl: test failures
On Sat, 20 Apr 2024 11:09:17 +0200, Dominique Dumont wrote: > This really looks like a bug with prove: > > $ perl t/reorder.t > ok 1 - test re-ordered list > 1..1 > $ prove -l -v -p t/reorder.t > t/reorder.t .. > ok 1 - test re-ordered list > 1..1 > Failed 1/1 subtests > > Test Summary Report > --- > t/reorder.t (Wstat: 0 Tests: 0 Failed: 0) > Parse errors: Bad plan. You planned 1 tests but ran 0. > Files=1, Tests=0, 1 wallclock secs ( 0.02 usr 0.00 sys + 0.92 cusr 0.07 > csys = 1.01 CPU) > Result: FAIL Good idea to run this directly with `perl'. > I can't see what's wrong with the output of reorder test... Ack, and same for the failing test in dh-make-perl (#1069246). But I don't see that `prove' has changed recently … So maybe this is in fact even somewhere "deeper"? > I'll try to dig this later on.. Thanks! Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1069247: libconfig-model-dpkg-perl: test failures
Source: libconfig-model-dpkg-perl Version: 3.004 Severity: serious Tags: ftbfs Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As seen on https://ci.debian.net/packages/libc/libconfig-model-dpkg-perl/unstable/amd64/45274399/ libconfig-model-dpkg-perl has test failures: 183s Test Summary Report 183s --- 183s t/dependency-check.t (Wstat: 0 Tests: 109 Failed: 0) 183s Parse errors: Tests out of sequence. Found (3) but expected (2) 183s Tests out of sequence. Found (4) but expected (3) 183s Tests out of sequence. Found (5) but expected (4) 183s Tests out of sequence. Found (6) but expected (5) 183s Tests out of sequence. Found (7) but expected (6) 183s Displayed the first 5 of 109 TAP syntax errors. 183s Re-run prove with the -p option to see them all. 183s t/dpkg.t (Wstat: 0 Tests: 50 Failed: 0) 183s Parse errors: Tests out of sequence. Found (3) but expected (2) 183s Tests out of sequence. Found (4) but expected (3) 183s Tests out of sequence. Found (5) but expected (4) 183s Tests out of sequence. Found (6) but expected (5) 183s Tests out of sequence. Found (7) but expected (6) 183s Displayed the first 5 of 50 TAP syntax errors. 183s Re-run prove with the -p option to see them all. 183s t/reorder.t(Wstat: 0 Tests: 0 Failed: 0) 183s Parse errors: Bad plan. You planned 1 tests but ran 0. 183s Files=18, Tests=1786, 106 wallclock secs ( 0.20 usr 0.03 sys + 103.34 cusr 3.44 csys = 107.01 CPU) 183s Result: FAIL This also happens locally for autopkgtest but also for the tests during build. (The version in git has more and unrelated test failure due to the last commit.) We see bascially the same -- the "Tests out of sequence." errors -- also in dh-make-perl, hence I think that there's some underlying problem. Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmYhVrNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgYXgQ/+ISS+Mo+83JAstQtZtiX4wWhUQbJDXG4xnQeu5YTj04AF/2WgCaDLzQf9 73iSweb9AJ+epJhQTuUxoo78XghIJkGaD7QiYaTCX1egOCmG72ZKVjIl2Hvr+C1n nqMDVRhKX21TW2tD0dQRQ+WaZYEd+pB5gkfq3hgPyYnIgwB4LubU8F2M7uo1cxf9 J5aD7Fv0fMGmuwPQ5ncflljf8yRSuocRLvMQLlHB0JjcpeFPKGgQ6ZyoKBfGWvZ0 x0qp4Ez2oqIXNNiDTz+8jET7m+bSdE2lL73dlADRjt2wqaQf7O8i2MCuf4krMqwJ owOyjBYzi//0qhOEj7Eh846Fclz4WMpwSO3+pns2du4gvaB6jN5mWK1uQrC4ohAi CSAlWqjXFyZ1kchuYxiejlvVPQrJ9EyAW4yeDzWAnXWCsI3gMAE/TUGUchc0dWyY nVviLMkdRSpgaOp08ITJ1se2yDapHXP/pIFSxeqzCj8L7hflzUPqC0/BsLHYkzQG kvSZxCIBZcB2biWQBVEcexPsHKliPgzu01FUdHb5uTCncxfjEwRiWO3QAKuZ0eca LXFWdyr2YVZH9NMWY2rxVhV9Lrf1ldwBWcTa4BzbBY3HbOrfxStyZ1PMmG8cVlc4 IkjOdMGhBiCyuE5TYqMEZyCsl/+Z3juWsjzt6/GLjwPUv6QgEDw= =1EkQ -END PGP SIGNATURE-
Bug#1069246: dh-make-perl: test failure in t/AptContents.t
Source: dh-make-perl
Version: 0.124
Severity: serious
Tags: ftbfs help
Justification: fails to build from source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As noticed on ci.debian.net, dh-make-perl has a test failure in
t/AptContents.t:
https://ci.debian.net/packages/d/dh-make-perl/unstable/amd64/45274464/
This also happens locally, and also during the build tests:
t/AptContents.t .
ok 1 - use Debian::AptContents;
ok 2 - AptContents->new with no cache_dir dies
ok 3 - should say why it died
ok 4 - Distributing files on more CPUs results in no empty slots
ok 5 - should create
ok 6 - contents in a dir
ok 7 - Contents.cache created
ok 8 - cache was used
ok 9 - cache updated
ok 10 - Moose found by find_file_packages
ok 11 - Moose found by module name
ok 12 - get_contents_files
ok 13 - GD.pm is in libdg-gd2[-noxpm]-perl
ok 14 - Alternative dependency for module found in multiple packages
ok 15 - Image/Magick.pm in perlmagick and graphicsmagick-libmagick-dev-compat,
but different paths
ok 16 - Alternative dependency for Image::Magick module found in multiple
packages
ok 17 - Test::More is in perl core and libtest-simple-perl but we only get the
latter
ok 18 - use Debian::Control::FromCPAN;
ok 19 - Test::More is in libtest-simple-perl
ok 20
1..20
Failed 1/20 subtests
Test Summary Report
- ---
t/AptContents.t (Wstat: 0 Tests: 19 Failed: 0)
Parse errors: Tests out of sequence. Found (20) but expected (19)
Bad plan. You planned 20 tests but ran 19.
Files=24, Tests=409, 20 wallclock secs ( 0.07 usr 0.04 sys + 15.74 cusr 2.40
csys = 18.25 CPU)
Result: FAIL
And I don't understand the issue … Looking at the code:
112 is( ( $ctl->find_debs_for_modules( { 'Test::More' => '0' },
$apt_contents ) )[0] . '',
113 'libtest-simple-perl',
114 'Test::More is in libtest-simple-perl'
115 );
116
117 ok( unlink "$Bin/Contents.cache", 'Contents.cache unlinked' );
118
Line 112 is test 19, succeeding and outputting "Test::More is in
libtest-simple-perl".
Test 20 is the unlink in line 117; no output (but the file is
removed).
Changing line 117 to
is( unlink( "$Bin/Contents.cache" ), 1, '20 Contents.cache unlinked' );
leads to basically the same:
ok 20 - Contents.cache unlnked
1..20
Failed 1/20 subtests
Test Summary Report
- ---
t/AptContents.t (Wstat: 0 Tests: 19 Failed: 0)
Parse errors: Tests out of sequence. Found (20) but expected (19)
Bad plan. You planned 20 tests but ran 19.
Now the test name/message is printed, but still there's this "Tests
out of sequence" error message.
No idea if this is a problem in dh-make-perl (I think not, we see
something very similar in libconfig-model-dpkg-perl), or in
Test::More or somewhere else …
Cheers,
gregor
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmYhU41fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZrqQ/9Gnom3gRNYvgPGBmba3r1O1xP+8ODIKxlsMgdSsRUsBV+XVZNSPSZcMdC
iH4RqZf5kYvt0rpHXzIgz88lxky3ERLnoKrlmaI2A0gS4D6VtrjIdHdn6lRjmobR
PAU0K4BI5GDEFugZZnDxLKOlF2ClcGtqYVz91qDhLWoVjjzZQGvC3Er1tqTk4Ze9
uztJd3gg8J9f3wjcMYZCQwUZcALz6flnK7Eef4IMs0PRV45SRSMTQ6wS7Kp31amL
KQDqzPrQqbXJ2u6u4Ax04MeJrDW9y/p1Tw9Xt/2yYa1VXtyLPS+PcBWA3jEmjaXK
SgTeuvSf1cMk4PS75AT+Y3oZxYLDuP4QvdgjZCPG4Zxi3W1pt6bOV011t6kB0Oiz
aP8S/c4HbfNwhVjgrJRhBOizs2GioALV1/iA7LC0OFyVZbe3OWj/4x3i86FzgVqB
MzVcABTRCnKBHFUhZGMtPMXzm8l8COZkHgFkos43Z09nAZwcB5n8MLPPW4F3X1wd
HFoMQd1JcyAjWlwMohoyPRtM+qKbLdhDJc3NJoE7QG4WxQT5zT8TJXkEniLQplsJ
tCezQyDN7XSuJbILdIZTXG4T32m1MhOCq4GnR9d1pGMar9evM0UsRScrEKMs9ANa
8lY1WMbr3q61RyzNGOT7HmIp37fpEPOBc3OBw4uGhmvCYfF9GyY=
=+yiH
-END PGP SIGNATURE-
Bug#1065768: libauthen-krb5-perl: FTBFS on arm{el,hf}: Krb5.xs:1040:17: error: implicit declaration of function ‘krb5_free_address’; did you mean ‘krb5_free_addresses’? [-Werror=implicit-function-dec
On Sun, 31 Mar 2024 18:41:02 -0700, Russ Allbery wrote: > In theory, one could delete the pieces of the module that try to do things > that no one should really be doing from Perl and the rest of it remains > somewhat useful, but given that upstream has archived the project, I would > go ahead and remove it. Thanks, Russ, for the explanations and the recommendation. And thanks, Sebastian, for filing #1068258. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- BOFH excuse #183: filesystem not big enough for Jumbo Kernel Patch
Bug#1065768: libauthen-krb5-perl: FTBFS on arm{el,hf}: Krb5.xs:1040:17: error: implicit declaration of function ‘krb5_free_address’; did you mean ‘krb5_free_addresses’? [-Werror=implicit-function-dec
On Fri, 29 Mar 2024 13:08:43 +0100, Sebastian Ramacher wrote: > > Not sure there are many chances to fix this (short of disabling > > -Werror=implicit-function-declaration). Cf. also in Fedora: > > https://src.fedoraproject.org/rpms/perl-Authen-Krb5/commits/rawhide > > https://bugzilla.redhat.com/show_bug.cgi?id=2172836 > > So should it be removed? I'm by far not any expert on C code and gcc flags; but yes, given the above findings and unless someone more knowledgeable steps up in the next couple of week, I think we have to remove libauthen-krb5-perl (and libauthen-krb5-admin-perl). Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe signature.asc Description: Digital Signature
Bug#1067305: marked as pending in libjson-schema-modern-perl
Control: tag -1 pending Hello, Bug #1067305 in libjson-schema-modern-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libjson-schema-modern-perl/-/commit/419bb3c7a0a9a31029cd364d4a76177c628c325e Add test and runtime dependency on libcpanel-json-xs-perl. This was pulled in by libtest-json-schema-acceptance-perl via libjson-maybexs-perl before. Thanks: Niko Tyni for finding the missing piece. Closes: #1067305 (this message was generated automatically) -- Greetings https://bugs.debian.org/1067305
Bug#1067305: libjson-schema-modern-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 3
On Thu, 21 Mar 2024 00:46:45 +0200, Niko Tyni wrote: > Indeed. It seems to have regressed with > libtest-json-schema-acceptance-perl_1.022-1, and specifically > by the removal of some of its dependencies. Just installing > libcpanel-json-xs-perl makes it pass again. D'oh! Thanks, nice find :) Cheers, gregor, preparing the upload -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1067305: libjson-schema-modern-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 3
Control: tag -1 + confirmed
On Wed, 20 Mar 2024 22:00:40 +0100, Lucas Nussbaum wrote:
> Source: libjson-schema-modern-perl
> Version: 0.582-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240319 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > Test Summary Report
> > ---
> > t/additional-tests-draft2019-09.t (Wstat: 256 (exited 1) Tests: 983
> > Failed: 1)
> > Failed test: 79
> > Non-zero exit status: 1
> > t/additional-tests-draft2020-12.t (Wstat: 256 (exited 1) Tests: 1066
> > Failed: 1)
> > Failed test: 86
> > Non-zero exit status: 1
> > t/additional-tests-draft7.t (Wstat: 256 (exited 1) Tests: 762
> > Failed: 1)
> > Failed test: 40
> > Non-zero exit status: 1
Same failure in all 3 tests:
#v+
# prove --blib t/additional-tests-draft2019-09.t
t/additional-tests-draft2020-12.t t/additional-tests-draft7.t
t/additional-tests-draft2019-09.t .. 1/? # Failed test 'evaluation result
is incorrect'
# at t/additional-tests-draft2019-09.t line 36.
# expected false; got true
# {
# "valid": true
# }
# Failed test 'integers.json: "int64 range checks" - "beyond lower boundary"'
# at t/additional-tests-draft2019-09.t line 36.
t/additional-tests-draft2019-09.t .. 865/? #
#
# Results using Test::JSON::Schema::Acceptance 1.022
# specification version: draft2019-09
# using custom test directory: t/additional-tests-draft2019-09
# optional tests included: yes
#
# filename pass todo-fail fail
# ---
# anchor.json 2 0 0
# annotation-collection.json 10 0 0
# badRef.json 3 0 0
# faux-buggy-schemas.json 2 0 0
# format-duration.json 9 0 0
# format-ipv4.json 4 0 0
# format-ipv6.json17 0 0
# format-relative-json-pointer.json7 0 0
# formats.json 4 0 0
# id.json 6 0 0
# integers.json 28 0 1
# keyword-independence.json 812 0 0
# loose-types-const-enum.json 8 0 0
# recursive-dynamic.json 4 0 0
# ref-and-id.json 6 0 0
# ref.json10 0 0
# short-circuit.json 20 0 0
# unknownKeyword.json 4 0 0
# vocabulary.json 5 0 0
# optional/format-date-time.json 4 0 0
# optional/format-date.json1 0 0
# optional/format-time.json 13 0 0
# ---
# TOTAL 979 0 1
#
# WARNING: some non-optional tests are failing! This implementation is not
fully compliant with the specification!
#
# Looks like you failed 1 test of 983.
t/additional-tests-draft2019-09.t .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/983 subtests
t/additional-tests-draft2020-12.t .. 1/? # Failed test 'evaluation result
is incorrect'
# at t/additional-tests-draft2020-12.t line 36.
# expected false; got true
# {
# "valid": true
# }
# Failed test 'integers.json: "int64 range checks" - "beyond lower boundary"'
# at t/additional-tests-draft2020-12.t line 36.
t/additional-tests-draft2020-12.t .. 930/? #
#
# Results using Test::JSON::Schema::Acceptance 1.022
# specification version: draft2020-12
# using custom test directory: t/additional-tests-draft2020-12
# optional tests included: yes
#
# filename pass todo-fail fail
# ---
# anchor.json 2 0 0
# annotation-collection.json 10 0 0
# badRef.json 3 0 0
# dynamicRef.json 7 0 0
# faux-buggy-schemas.json 2 0 0
# format-duration.json 9 0 0
# format-ipv4.json 4 0 0
# format-ipv6.json17 0 0
# format-relative-json-pointer.json7 0 0
# formats.json 4 0 0
# id.json
Bug#1067341: marked as pending in libdevel-mat-dumper-perl
Control: tag -1 pending Hello, Bug #1067341 in libdevel-mat-dumper-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libdevel-mat-dumper-perl/-/commit/7d2b0b41347a219ee5ac9d1d8d1691dd1e9f261c Add a Breaks on libdevel-mat-perl < 0.53. Closes: #1067341 (this message was generated automatically) -- Greetings https://bugs.debian.org/1067341
Bug#1066249: libmediascan: FTBFS: api_test.c:80:3: error: implicit declaration of function ‘gettimeofday’ [-Werror=implicit-function-declaration]
On Thu, 14 Mar 2024 21:16:51 +0200, Niko Tyni wrote:
> > Not going to upload as-is, as I hardly speak any C and don't really
> > know what I'm doing and this is more than adding a missing #include
> > or prototype and I don't understand the code.
> I assume you mean the '#define _mkdir mkdir' part? The rest
> seems straightforward.
Right, this _mkdir was the part I was mostly unsure about.
> AFAICS the code used to call mkdir(2) without the mode argument.
> A simple test [1] indicates that will just put random garbage there,
> so the resulting directory will have a different mode every time. Surely
> that was always buggy.
That was my assumption as well that this is all a bit, hm, broken.
> I'm not convinced that affected functions in test/test_defects.c
> or test/test_background.c ever get executed for us though?
I think they don't get executed but they lead to compile errors.
> In any case, your change
>
> +int _mkdir(const char *pathname)
> +{
> +mkdir(*pathname, 0775);
> +}
>
> is not quite correct: I think it should read something like
>
> int _mkdir(const char *pathname)
> {
> return mkdir(pathname, 0775)
> }
>
> to work properly.
Ha! Thanks, that's what I meant by "I don't really speak C", and
indeed I was wondering how exactly to express this :)
> But I think it would be easier to stick with the preprocessor and do
>
> -#define _mkdir mkdir
> +#include
> +#define _mkdir(x) mkdir((x), 0755)
>
> instead.
Great.
> Hope this helps :)
It does, thank you!
Patch updated, package uploaded.
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
signature.asc
Description: Digital Signature
Bug#1066498: dh-make-perl: autopkgtest regression due to time_t transition
On Thu, 14 Mar 2024 18:40:27 +0200, Niko Tyni wrote: > Sure we need to allow for libperl5.XX to stay future-proof. I was just > thinking of hardcoding libperl5.38t64 as the (temporary) other option > rather than using a generic libperl5.XXt64 name. > But no worries :) There were already for variables for getting the perl API version in the script :) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1066249: libmediascan: FTBFS: api_test.c:80:3: error: implicit declaration of function ‘gettimeofday’ [-Werror=implicit-function-declaration]
On Wed, 13 Mar 2024 12:41:10 +0100, Lucas Nussbaum wrote: > > api_test.c: In function ‘check_mimetypes’: > > api_test.c:80:3: error: implicit declaration of function ‘gettimeofday’ > > [-Werror=implicit-function-declaration] > >80 | gettimeofday(&now, NULL); > > api_test.c: In function ‘main’: > > api_test.c:198:3: error: implicit declaration of function ‘run_unit_tests’ > > [-Werror=implicit-function-declaration] > > 198 | run_unit_tests(); > > test_background.c: In function ‘test_background_api’: > > test_background.c:12:16: error: implicit declaration of function ‘mkdir’; > > did you mean ‘_mkdir’? [-Werror=implicit-function-declaration] > >12 | #define _mkdir mkdir > > test_background.c: In function ‘test_async_api’: > > test_background.c:822:3: error: implicit declaration of function > > ‘gettimeofday’ [-Werror=implicit-function-declaration] > > 822 | gettimeofday(&now, NULL); > > test.c: In function ‘TouchFile’: > > test.c:512:3: error: implicit declaration of function ‘gettimeofday’ > > [-Werror=implicit-function-declaration] > > 512 | gettimeofday(&now, NULL); > > test.c:513:3: error: implicit declaration of function ‘utimes’; did you > > mean ‘ctime’? [-Werror=implicit-function-declaration] > > 513 | utimes(filename , &now); I've pushed a patch to git which make the package compile without errors. Not going to upload as-is, as I hardly speak any C and don't really know what I'm doing and this is more than adding a missing #include or prototype and I don't understand the code. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1066249: marked as pending in libmediascan
Control: tag -1 pending Hello, Bug #1066249 in libmediascan reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libmediascan/-/commit/0c920fa2741e966e16ca782a84646a90a02156bf Add implicit-function-declaration.patch. Closes: #1066249 (this message was generated automatically) -- Greetings https://bugs.debian.org/1066249
Bug#1065768: libauthen-krb5-perl: FTBFS on arm{el,hf}: Krb5.xs:1040:17: error: implicit declaration of function ‘krb5_free_address’; did you mean ‘krb5_free_addresses’? [-Werror=implicit-function-dec
On Sat, 09 Mar 2024 21:29:26 +0100, Sebastian Ramacher wrote: > Source: libauthen-krb5-perl > Version: 1.9-6 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org > > https://buildd.debian.org/status/fetch.php?pkg=libauthen-krb5-perl&arch=armhf&ver=1.9-6%2Bb3&stamp=1709893977&raw=0 > > Krb5.xs:1040:17: error: implicit declaration of function ‘krb5_free_address’; > did you mean ‘krb5_free_addresses’? [-Werror=implicit-function-declaration] > 1040 | krb5_free_address(context,addr); > | ^ > | krb5_free_addresses Not sure there are many chances to fix this (short of disabling -Werror=implicit-function-declaration). Cf. also in Fedora: https://src.fedoraproject.org/rpms/perl-Authen-Krb5/commits/rawhide https://bugzilla.redhat.com/show_bug.cgi?id=2172836 Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1066498: dh-make-perl: autopkgtest regression due to time_t transition
On Wed, 13 Mar 2024 23:12:57 +0200, Niko Tyni wrote: > > Reviews welcome; I'm not sure it's the most elegant and safe solution, > > and also if this libperl5.38t64 naming has other effects. > Thanks for fixing this. Thanks for checking. > Didn't dig deeply into what the test is actually doing, but I think it'd > be fine to just hardcode libperl5.38t64 FWIW. After some thinking, I think I makes to (temporarily) allow both libperl5.XXt64 and libperl5.XX, otherwise we'll have a mess during the 5.40 transition. (After that we can get rid of the option with the suffix again.) > But whatever works is good of course. :) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1065995: marked as pending in libauthen-smb-perl
Control: tag -1 pending Hello, Bug #1065995 in libauthen-smb-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libauthen-smb-perl/-/commit/4d5c752a546cd7fd9b2d0a4b62a1babd263ca7c1 Add implicit-function-declaration.patch. Declare functions before use. Closes: #1065995 (this message was generated automatically) -- Greetings https://bugs.debian.org/1065995
Bug#1066498: dh-make-perl: autopkgtest regression due to time_t transition
On Wed, 13 Mar 2024 13:34:57 +0100, gregor herrmann wrote: > > 80s not ok 5 - Errno is in libperl5.38 or perl-base (or only perl-base > > for perl < 5.22) > libperl5.38 or as it's called nowadays: libperl5.38t64, that's the > point probably … Fix committed in git. Reviews welcome; I'm not sure it's the most elegant and safe solution, and also if this libperl5.38t64 naming has other effects. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1066786: marked as pending in dh-make-perl
Control: tag -1 pending Hello, Bug #1066786 in dh-make-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/dh-make-perl/-/commit/9877efe593292b17819005919785ea9525f05f9f t/DpkgLists.t: use Test::Deep's subsetof test to check for libperl5.xt64. Closes: #1066786 (this message was generated automatically) -- Greetings https://bugs.debian.org/1066786
Bug#1066498: dh-make-perl: autopkgtest regression due to time_t transition
On Wed, 13 Mar 2024 11:20:06 -0100, Graham Inggs wrote: > dh-make-perl's autopkgtest regress when tested with perl/5.38.2-3.2 > [1]. I've copied what I hope is the relevant part of the log below. Huh, thanks for the bug report; the autopkgtests still worked a week ago on my laptop, when I did the last upload. > From what I can see on the excuses page for perl [2], dh-make-perl's > autopkgtests are the only ones failing on all architectures, besides > perl's own. Do these test cases need updating to handle the 't64'? Let's have a look: > 80s not ok 5 - Errno is in libperl5.38 or perl-base (or only perl-base > for perl < 5.22) *sigh* libperl5.38 or as it's called nowadays: libperl5.38t64, that's the point probably … Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- BOFH excuse #233: TCP/IP UDP alarm threshold is set too low.
Bug#1065975: marked as pending in libnet-nis-perl
Control: tag -1 pending Hello, Bug #1065975 in libnet-nis-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libnet-nis-perl/-/commit/a7a6e87c5cddc4c4a0e3943aadea64c9d47a1761 Add patch to declare function before use. Closes: #1065975 (this message was generated automatically) -- Greetings https://bugs.debian.org/1065975
Bug#1065788: marked as pending in liblocale-hebrew-perl
Control: tag -1 pending Hello, Bug #1065788 in liblocale-hebrew-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/liblocale-hebrew-perl/-/commit/de1692a5e4467ab6a9855aa2d70b22539dce5391 Add patch to declare function before use. Closes: #1065788 (this message was generated automatically) -- Greetings https://bugs.debian.org/1065788
