Your message dated Fri, 07 Nov 2025 07:04:31 +0000
with message-id <[email protected]>
and subject line Bug#1120215: fixed in php-lorenzo-pinky 1.1.0-4
has caused the Debian Bug report #1120215,
regarding php-lorenzo-pinky: FTBFS: dpkg-buildpackage: error: debian/rules 
binary subprocess returned exit status 2
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.)


-- 
1120215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120215
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:php-lorenzo-pinky
Version: 1.1.0-3
Severity: serious
Tags: ftbfs forky sid

Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

https://people.debian.org/~sanvila/build-logs/202511/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:php-lorenzo-pinky, so that this is still
visible in the BTS web page for this package.

Thanks.

--------------------------------------------------------------------------------
[...]
 debian/rules clean
dh clean
   dh_clean
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<<PKGBUILDDIR>>'
cp -f debian/autoload.php src/
# Mimic install path for tests
mkdir --parent data
ln -sf ../src data/Pinky
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
phpunit --do-not-cache-result --bootstrap src/autoload.php tests/
PHPUnit 12.4.2 by Sebastian Bergmann and contributors.

Runtime:       PHP 8.4.11
Configuration: /<<PKGBUILDDIR>>/phpunit.xml.dist

........................FF..............                          40 / 40 (100%)

Time: 00:00.030, Memory: 8.00 MB

There were 2 failures:

1) EncodingTest::testMultiByteContent#1 with data ('<html><body><p>Twoje 
zam&oacu.../html>', '<p>Twoje zamówienie oczekuje ...🇳🇱</p>')
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'<html><body><p>Twoje zam&oacute;wienie oczekuje na wp&#322;at&#281; zadatku 
&#127475;&#127473;</p></body></html>'
+'<html><body><p>Twoje zamówienie oczekuje na wpłatę zadatku 
🇳🇱</p></body></html>'

/<<PKGBUILDDIR>>/tests/EncodingTest.php:16

2) EncodingTest::testMultiByteContent#2 with data 
('<html><body><p>&#1055;&#1088;.../html>', '<p>Привет мир!</p>')
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'<html><body><p>&#1055;&#1088;&#1080;&#1074;&#1077;&#1090; 
&#1084;&#1080;&#1088;!</p></body></html>'
+'<html><body><p>Привет мир!</p></body></html>'

/<<PKGBUILDDIR>>/tests/EncodingTest.php:16

FAILURES!
Tests: 40, Assertions: 45, Failures: 2, PHPUnit Deprecations: 1.
make[1]: *** [debian/rules:12: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:3: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------

--- End Message ---
--- Begin Message ---
Source: php-lorenzo-pinky
Source-Version: 1.1.0-4
Done: David Prévot <[email protected]>

We believe that the bug you reported is fixed in the latest version of
php-lorenzo-pinky, 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.
David Prévot <[email protected]> (supplier of updated php-lorenzo-pinky 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: Thu, 06 Nov 2025 18:55:26 +0100
Source: php-lorenzo-pinky
Architecture: source
Version: 1.1.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers <[email protected]>
Changed-By: David Prévot <[email protected]>
Closes: 1120215
Changes:
 php-lorenzo-pinky (1.1.0-4) unstable; urgency=medium
 .
   * Update expected output, again (Closes: #1120215)
   * debian/control: Document nocheck flag
Checksums-Sha1:
 91f0d45c8abf812aeb50dac47541e82b67b03382 1778 php-lorenzo-pinky_1.1.0-4.dsc
 25e99abe7014ae2b8b0b17ab68182e26c2d30095 5012 
php-lorenzo-pinky_1.1.0-4.debian.tar.xz
 4cab5211f668bf617506e941bf530abc9de6857b 7036 
php-lorenzo-pinky_1.1.0-4_amd64.buildinfo
Checksums-Sha256:
 6528211a9fab9212c1c9bc2459c039e40050966508191674ffdf02b5820c2145 1778 
php-lorenzo-pinky_1.1.0-4.dsc
 6f5e12fdcabd2d4e4347f1e878f60f57afeaa2e47ce67e68ae8b3ad03af7e5ce 5012 
php-lorenzo-pinky_1.1.0-4.debian.tar.xz
 aca640661b5f537201da2697dd7f2fe63f1c881fa9e75da1579e60e4d2036d94 7036 
php-lorenzo-pinky_1.1.0-4_amd64.buildinfo
Files:
 48c4a6d47e1451496f7346435a0e32ca 1778 php optional 
php-lorenzo-pinky_1.1.0-4.dsc
 3e85a29d4ab6deb9b775efcaf585d642 5012 php optional 
php-lorenzo-pinky_1.1.0-4.debian.tar.xz
 41e1f20e990feeeb673a225bbeed9b6c 7036 php optional 
php-lorenzo-pinky_1.1.0-4_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQFGBAEBCgAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAmkNlFESHHRhZmZpdEBk
ZWJpYW4ub3JnAAoJEAWMHPlE9r08PQgH/14MN2KzKeSnrvIQzxBwBQLwuILOcP/V
CboHy7WFGfGipTYBIzNUz2mrGXAAaac3tJ9TaLwbVYI170e4yn0CEQMpLTmgreYN
rjt1td24BVpS0UE9kmbafKkxXsuDkVYXAFrcxiiWQJYdT+3K6C/cSNRnvUfXPj99
V4ga9Z8mQ/FfKW3tBw7W+bEchvvMQM7UTzxtl2aIq3zXLtwLkYl86W8Lqgra00B8
qs0IRMR0yBNzbLhp8dWUDj0H9/hO3HWwt0jQSf4gaVFQA8s5VWv6HcR+rb6j8fJ5
ZEuGvIoOb1peHB5AxafNR3pjCj0smbU2Io6/f8u9A1NZgvaUev4aDCA=
=Xsjk
-----END PGP SIGNATURE-----

Attachment: pgpoGaAJ4weYw.pgp
Description: PGP signature


--- End Message ---

Reply via email to