Your message dated Thu, 09 Oct 2025 18:00:18 +0000
with message-id <[email protected]>
and subject line Bug#1117274: fixed in pg-crash 0.3-2
has caused the Debian Bug report #1117274,
regarding pg-crash: FTBFS: dpkg-buildpackage: error: debian/rules clean
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.)
--
1117274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1117274
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:pg-crash
Version: 0.3-1
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/202510/
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:pg-crash, so that this is still
visible in the BTS web page for this package.
Thanks.
--------------------------------------------------------------------------------
[...]
debian/rules clean
dh clean --with pgxs
dh_auto_clean --buildsystem=pgxs
pg_buildext clean build-%v postgresql-%v-pg-crash
rm -rf build-*/
rm -rf debian/postgresql-*-pg-crash/ debian/postgresql-*-pg-crash.substvars
make[1]: Entering directory '/<<PKGBUILDDIR>>'
rm -f pg_crash.so libpg_crash.a libpg_crash.pc
rm -f pg_crash.o pg_crash.bc
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_clean
pg_buildext checkcontrol
--- debian/control 2025-06-12 15:47:04.000000000 +0000
+++ debian/control.tOvESG 2025-10-04 10:08:40.902372400 +0000
@@ -15,7 +15,7 @@
Vcs-Browser: https://salsa.debian.org/postgresql/pg-crash
Vcs-Git: https://salsa.debian.org/postgresql/pg-crash.git
-Package: postgresql-17-pg-crash
+Package: postgresql-18-pg-crash
Architecture: any
Depends:
${misc:Depends},
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
make: *** [debian/rules:4: clean] Error 1
dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Source: pg-crash
Source-Version: 0.3-2
Done: Christoph Berg <[email protected]>
We believe that the bug you reported is fixed in the latest version of
pg-crash, 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.
Christoph Berg <[email protected]> (supplier of updated pg-crash 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: Wed, 08 Oct 2025 16:02:20 +0200
Source: pg-crash
Binary: postgresql-18-pg-crash postgresql-18-pg-crash-dbgsym
Architecture: source amd64
Version: 0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers <[email protected]>
Changed-By: Christoph Berg <[email protected]>
Description:
postgresql-18-pg-crash - Periodically crash your PostgreSQL database
Closes: 1117274
Changes:
pg-crash (0.3-2) unstable; urgency=medium
.
* Upload for PostgreSQL 18. (Closes: #1117274)
* Add ${postgresql:Breaks}.
* Fix Vcs-Git, repo is on github.
Checksums-Sha1:
056306435e81ddb5ae0d0bdc7d8626aab795247d 2117 pg-crash_0.3-2.dsc
d2f1db49e4140d6f418c17e4e9b3a728925af349 2448 pg-crash_0.3-2.debian.tar.xz
93cfd101139109f9c10f5b86c6bba75a02989578 11931 pg-crash_0.3-2_amd64.buildinfo
4b82e48c5c3e67cc77abaa6594da0b53143fcaac 15920
postgresql-18-pg-crash-dbgsym_0.3-2_amd64.deb
42ec05e39cf74cc89c42eb9563491acb6c87fd52 13660
postgresql-18-pg-crash_0.3-2_amd64.deb
Checksums-Sha256:
1d4337d5d47b47277647c1b4a96000f1b1e67e457fc9032a4258c17310f050b7 2117
pg-crash_0.3-2.dsc
aa4aef5f9951b6f51954855d0df3070313d0a880e8df7bc027f566425fc67c6b 2448
pg-crash_0.3-2.debian.tar.xz
2f72302d162b3120aed707fd4b44cecf07af1369091297e966eae27acb2a734e 11931
pg-crash_0.3-2_amd64.buildinfo
b1d93f5ba1f61acf4053cd11e9d182055bf1fe091a07c8fdc6a8dcbc521f54f8 15920
postgresql-18-pg-crash-dbgsym_0.3-2_amd64.deb
b328d7414a040ed7bacfd214c5afe4147d47806382c01374770ab7b5dd412953 13660
postgresql-18-pg-crash_0.3-2_amd64.deb
Files:
8baeebb9dc2672a50fc6b2a4ac38a540 2117 database optional pg-crash_0.3-2.dsc
68c5d0007db5fd2d9c1f9ea47ee52456 2448 database optional
pg-crash_0.3-2.debian.tar.xz
e504fc0254de38daf0b2f8a3adbd77c2 11931 database optional
pg-crash_0.3-2_amd64.buildinfo
fd68e7ccb6b578e624ee603b26155ab7 15920 debug optional
postgresql-18-pg-crash-dbgsym_0.3-2_amd64.deb
30069e030e6263e2c1a8b531b8250ccb 13660 database optional
postgresql-18-pg-crash_0.3-2_amd64.deb
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmjmcQwACgkQTFprqxLS
p66a9RAApkckNil3HIVnRTVocwq+ObCxQO35M2lfNEZRaO9B+0IxdZOKEJfd7YQL
42B/4dE6Ri6tEvfLM8G/YMKCMZIyBke8dpN+c/LlNL1a8b6AkBdACJxstSTL26tM
SsLYsp4cy8zlfwSJYYXrLSC1JaGEjqaowcShA/+10QGJWeRNMv4rXI0MLlqRwj4V
NWbfffnoDbwcfZxmf1NoevsJf01Ef/EFmWxiR+F5yxMGh1ax6LA0uhmancQLowV3
WZsVnLwxrxXNhyaQIWmVW8ggmBghigUd7b8mBpiAP6mHL1Rea5E0VbiOxo2KTPVA
yOlZrcyh66mHcsjb0HzZw5GuYPY34OymhQC2dpV9zQctzPBkztzst8jIk4Fcy1J4
QRJW1u039rAMVwHKuPolMQvqCa6MIWBwV+Mt4f9bssb8BeqpZUjx8nnxcjoCLLbZ
S95GrT73SvWW0wzUqS4gDS4LQCGo+uNFg/XZ0+F6qExHMUb8uXFgGY0xTrgK8o10
hYMwyX5NonHyi7aKVKU0TEVO+YgaHEAr79L8J4LDb07zG9ZT4usaCWlWRN37O/0U
YVVWwtvfJQ62ER6Qpn+wGpbV7MLsf1Y8DthwinQ4GVlW4/JKSDd/ALv2E6r2K0Ys
lgFt8n5OBOo0/3bLRLrCWW7xruFjVNZ++USWEkIVA2rRfzmryJo=
=6SQY
-----END PGP SIGNATURE-----
pgpnnbBs8Sve5.pgp
Description: PGP signature
--- End Message ---
