Your message dated Tue, 21 Jan 2025 21:49:54 +0000
with message-id <[email protected]>
and subject line Bug#1089242: fixed in guile-zlib 0.2.2-1
has caused the Debian Bug report #1089242,
regarding guile-zlib: FTBFS with zlib-ng.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1089242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089242
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: guile-zlib
Version: 0.2.1-1
Severity: important
Tags: sid patch
control: affects -1 src:zlib-ng
User: [email protected]
Usertags: zlib-ng-ftbfs
The "gzip output port, error" test writes 65536 of likely uncompressible
bytes and expects that the zlib library writes it immediately to the
fd. This happens with zlib but does not happen with zlib-ng as it caches
this amount and does not write (yet). The test fails as the error is
not observed. Once the fd is "dropped" the fd is closed by the garbage
collector and the error is thrown but not caught by the test.
This is my understanding and I just learned that guile exists.
The patch attached increases the number of written bytes so that zlib-ng
als writes immediately to the fd and throws the error.
Sebastian
From: Sebastian Andrzej Siewior <[email protected]>
Date: Sat, 7 Dec 2024 17:15:26 +0100
Subject: [PATCH] test: Increase write size for write test.
The "gzip output port, error" test writes 65536 of likely uncompressible
bytes and expects that the zlib library writes it immediately to the
fd. This happens with zlib but does not happen with zlib-ng as it caches
this amount and does not write (yet). The test fails as the error is
not observed. Once the fd is "dropped" the fd is closed by the garbage
collector and the error is thrown but not caught by the test.
This is my understanding and I just learned that guile exists.
Increase the number of written bytes so that zlib-ng als writes
immediately to the fd and throws the error.
Signed-off-by: Sebastian Andrzej Siewior <[email protected]>
---
tests/zlib.scm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/zlib.scm b/tests/zlib.scm
index b33bc9dbd288..ec7b0fe9fc13 100644
--- a/tests/zlib.scm
+++ b/tests/zlib.scm
@@ -57,7 +57,7 @@
(call-with-output-file "/dev/full"
(lambda (p)
(let ((p (make-gzip-output-port p)))
- (put-bytevector p (random-bytevector 65536))
+ (put-bytevector p (random-bytevector 262140))
(force-output p)
(close-port p))))
#f)
--- End Message ---
--- Begin Message ---
Source: guile-zlib
Source-Version: 0.2.2-1
Done: Vagrant Cascadian <[email protected]>
We believe that the bug you reported is fixed in the latest version of
guile-zlib, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vagrant Cascadian <[email protected]> (supplier of updated guile-zlib package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 21 Jan 2025 13:34:24 -0800
Source: guile-zlib
Architecture: source
Version: 0.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian <[email protected]>
Changed-By: Vagrant Cascadian <[email protected]>
Closes: 1089242
Changes:
guile-zlib (0.2.2-1) unstable; urgency=medium
.
* New upstream release. (Closes: #1089242)
* debian/copyright: Update for 0.2.2.
Checksums-Sha1:
5fa8b89e946b34634f38510a32750efc5aa8e9c7 1340 guile-zlib_0.2.2-1.dsc
17ef5423a9a1f49fa6c29f1bddc67a421af08e15 17433 guile-zlib_0.2.2.orig.tar.gz
5f42e2cb6a8a16bb48476a41d61face177a94b95 2572 guile-zlib_0.2.2-1.debian.tar.xz
14a02a25f9db44e2a79be374d374b527a70ad308 6154
guile-zlib_0.2.2-1_amd64.buildinfo
Checksums-Sha256:
a42ff255c71d78efa089e6629151d27ccce3b9412d235fd7f82018d87f5a2699 1340
guile-zlib_0.2.2-1.dsc
6f6cca4b32ca79f3f4627cdb7ea68569a3cc38be60468991e2b5c085783e38c1 17433
guile-zlib_0.2.2.orig.tar.gz
16500ceeb3bf0fb61bd711a8bb3ea0a9d1ca30f9d0e6598b727aeb45c4361b11 2572
guile-zlib_0.2.2-1.debian.tar.xz
0c03f8940345245db8d2f2f59bb1126f2475c21ceefee3e2031a0da306912dbc 6154
guile-zlib_0.2.2-1_amd64.buildinfo
Files:
63f7984166f350a966fe44bc8573342b 1340 lisp optional guile-zlib_0.2.2-1.dsc
86376f180672cd3972e9efea8a9f5f3c 17433 lisp optional
guile-zlib_0.2.2.orig.tar.gz
640ba1365cb1a3ab54ed2988cf35f71e 2572 lisp optional
guile-zlib_0.2.2-1.debian.tar.xz
f2a61c702ae8e8a58ad07b3a8d45e03c 6154 lisp optional
guile-zlib_0.2.2-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iIkEARYKADEWIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCZ5AT1xMcdmFncmFudEBk
ZWJpYW4ub3JnAAoJENxRj8h/lxaqZ+gA/0kyvEvCPC4pkWvkE8FBNmYBrApOwjfh
s0MXWwL35B44AQDopt4hG2nHy99LQhsQEA1GtpeqYTc6rwh0WpyIgehfBw==
=tgXl
-----END PGP SIGNATURE-----
pgpW5hcbmbcUQ.pgp
Description: PGP signature
--- End Message ---
