Processed: Re: silkaj: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12 returned exit code 13
Processing control commands:
> reassign -1 python3-pendulum
Bug #1078378 [src:silkaj] silkaj: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.12 returned exit code 13
Bug reassigned from package 'src:silkaj' to 'python3-pendulum'.
No longer marked as found in versions silkaj/0.11.0-2.
Ignoring request to alter fixed versions of bug #1078378 to the same values
previously set
--
1078378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1078371: Type missmatch, does not work on all architectures
Hi On Sun, Aug 11, 2024 at 08:43:23AM +0200, Petter Reinholdtsen wrote: > but alas, did not really solve much. This is unsurprising, as the tests in 3.2-3 are just broken. At least both the bind and bind-broken directory are identical and the "validate-bind-zones" test fails. | ~/nslint-3.2/debian/tests$ ./validate-bind-zones | success: no error in zone detected | error: no error in supposed incorrect zone detected. | ~/nslint-3.2/debian/tests$ diff -urN bind bind-broken/ && echo none || echo diff | none So first step is to get working tests. Second is to actually test what you are trying to see. Bastian -- Change is the essential process of all existence. -- Spock, "Let That Be Your Last Battlefield", stardate 5730.2
Bug#1078371: Type missmatch, does not work on all architectures
On Sun, Aug 11, 2024 at 09:32:10PM +0200, Bastian Blank wrote: > On Sun, Aug 11, 2024 at 08:43:23AM +0200, Petter Reinholdtsen wrote: > > but alas, did not really solve much. > > This is unsurprising, as the tests in 3.2-3 are just broken. Also gcc shows buffer overflows: | ./nslint.c: In function ‘checkwks’: | ./nslint.c:567:39: warning: ‘%s’ directive writing up to 1023 bytes into a region of size 512 [-Wformat-overflow=] | 567 | (void)sprintf(psbuf, "%s/%s", serv, proto); | | ^~ | ./nslint.c:567:23: note: ‘sprintf’ output 2 or more bytes (assuming 1025) into a destination of size 512 | 567 | (void)sprintf(psbuf, "%s/%s", serv, proto); | | ^~~~ | ./nslint.c:577:42: warning: ‘%s’ directive writing up to 511 bytes into a region of size 132 [-Wformat-overflow=] | 577 | sprintf(errstr, "%s unknown", psbuf); | | ^~ ~ | ./nslint.c:577:25: note: ‘sprintf’ output between 9 and 520 bytes into a destination of size 132 | 577 | sprintf(errstr, "%s unknown", psbuf); | | ^~~~ And an instrumented cmpaddr function shows the condition that reaches abort(): | $ nslint -d -c named.conf | got family: 2, 2 | got family: 2, 2 | got family: -520095920, -517846240 | got family: 0, 2 | got family: 2, 2 | nslint: 19/131072 items used, 0 errors Fixing the first error, aka replace with cmpitemaddr does not work either, because the qsort calls it with "struct item **", not "struct item *". The cmpitemaddr function is unused otherwise. Now I have to ask you, if you really are capable to maintain a package in this state? Bastian -- Vulcans worship peace above all. -- McCoy, "Return to Tomorrow", stardate 4768.3
geotranz is marked for autoremoval from testing
geotranz 3.7-3 is marked for autoremoval from testing on 2024-08-25 It is affected by these RC bugs: 1052574: geotranz: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7 https://bugs.debian.org/1052574 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
Bug#1078371: Type missmatch, does not work on all architectures
[Bastian Blank]
> Also gcc shows buffer overflows:
As far as I can tell, this seem to be mostly theoretical. To reduce the
chance of this affecting anything, I added a patch to git to get rid of
it.
> And an instrumented cmpaddr function shows the condition that reaches
> abort():
Good idea. I did the same applying this patch the git source, where the
autopkgtest has been fixed:
--- nslint-3.2.orig/nslint.c
+++ nslint-3.2/nslint.c
@@ -592,6 +592,7 @@ cmpaddr(const void *arg1, const void *ar
n1 = (const struct network *)arg1;
n2 = (const struct network *)arg2;
+ printf("got family: %d, %d\n", n1->family, n2->family);
/* IPv4 before IPv6 */
if (n1->family != n2->family)
return ((n1->family == AF_INET) ? -1 : 1);
With this patch I place, I get the following on amd64:
% NSLINT="`pwd`/nslint" debian/tests/validate-bind-zones
got family: 2, 2
got family: 2, 2
got family: 396612976, 398862656
got family: 0, 2
got family: 2, 2
success: no error in zone detected
got family: 2, 2
got family: 2, 2
nslint: Missing "a": tjener.intern. -> 10.0.0.2
nslint: Missing "ptr": tjener.intern. -> 10.0.2.2
got family: -1350817472, -1350817432
got family: -1353067152, -1350817432
got family: -1353067152, -1350817472
got family: 0, 2
got family: 2, 2
got family: 2, 2
success: error in zone detected.
%
> Fixing the first error, aka replace with cmpitemaddr does not work
> either, because the qsort calls it with "struct item **", not "struct
> item *". The cmpitemaddr function is unused otherwise.
As far as I can tell, the qsort code in question try to sort a list of
addresses, not a list of struct item, so struct item ** seem correct.
> Now I have to ask you, if you really are capable to maintain a package
> in this state?
I absolutely do not plan to stand in the way of anyone willing to adapt
this package.
--
Happy hacking
Petter Reinholdtsen
