Your message dated Fri, 04 Jul 2025 17:34:11 +0000
with message-id <e1uxkid-006brb...@fasolo.debian.org>
and subject line Bug#1033711: fixed in kore 4.2.3-1
has caused the Debian Bug report #1033711,
regarding kore: autopkgtest regression: Killing leaked background processes
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 ow...@bugs.debian.org
immediately.)
--
1033711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kore
Version: 4.1.0-6
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails since May
2022. Can you please investigate the situation and fix it? I copied some
of the output at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. [Release Team member hat on] Because
we're currently in the hard freeze for bookworm, I have marked this bug
as bookworm-ignore, although from the log I'm not sure this doesn't hint
at serious issues. Targeted fixes are still welcome.
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html
https://ci.debian.net/data/autopkgtest/testing/amd64/k/kore/32029176/log.gz
autopkgtest [09:24:03]: test myapp-clang: [-----------------------
created myapp/src/myapp.c
created myapp/conf/myapp.conf
created myapp/conf/build.conf
created myapp/.gitignore
created dh2048.pem
myapp created successfully!
WARNING: DO NOT USE THE GENERATED DH PARAMETERS AND CERTIFICATES IN
PRODUCTION
active flavor dev
output type dso
kore binary /usr/bin/kore
kore features -DKORE_USE_PGSQL -DKORE_USE_TASKS -I/usr/include/postgresql
/tmp/autopkgtest-lxc.5m5g54p3/downtmp/wrapper.sh: Killing leaked
background processes: 1562 1566 1572 1573 1574
PID TTY STAT TIME COMMAND
1562 ? S 0:00 timeout --preserve-status -k 60s -s
SIGQUIT 60s kodev run
1566 ? S 0:00 kore [parent]
1572 ? S 0:00 kore [wrk 1]
1573 ? S 0:00 kore [wrk 2]
1574 ? S 0:00 kore [keymgr]
autopkgtest [09:24:15]: test myapp-clang: -----------------------]
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: kore
Source-Version: 4.2.3-1
Done: Shih-Yuan Lee (FourDollars) <fourdoll...@debian.org>
We believe that the bug you reported is fixed in the latest version of
kore, 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 1033...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Shih-Yuan Lee (FourDollars) <fourdoll...@debian.org> (supplier of updated kore
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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 04 Jul 2025 16:47:25 +0000
Source: kore
Built-For-Profiles: noudeb
Architecture: source
Version: 4.2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Shih-Yuan Lee (FourDollars) <fourdoll...@debian.org>
Changed-By: Shih-Yuan Lee (FourDollars) <fourdoll...@debian.org>
Closes: 1033711 1081081
Changes:
kore (4.2.3-1) unstable; urgency=medium
.
* Bump to 4.2.3.
* d/p/0*.patch: Drop all patches from the upstream.
* d/p/debian.patch: Refresh debian.patch.
* d/p/0002-pgsql-Handle-PGRES_TUPLES_CHUNK-for-PostgreSQL-17.patch:
Fix the problem for PostgreSQL 17+. (Closes: #1081081)
* d/p/0003-conf-Correct-TLS-certificate-filenames-in-example-co.patch:
Correct TLS certificate filenames in example config (Closes: #1033711)
* debian/patches/0004-Disable-deprecated-warnings-for-OpenSSL-3.patch,
debian/patches/0005-Change-how-we-handle-EVP_PKEY-for-privsep.patch:
Cherry-pick upstream OpenSSL 3.x compatibility patches (Closes: #1033711)
* debian: Correctly wait for Kore parent process in autopkgtests
* debian: Improve Seccomp verification in myapp tests
* debian: Improve service readiness check in myapp tests
* debian: Bump debhelper compat level and standards version
Checksums-Sha1:
e18dd1866682d55c695181c88ba73fd2d9ee8492 1948 kore_4.2.3-1.dsc
48076eda5771f32815675aef961a403f98f77c33 1085717 kore_4.2.3.orig.tar.gz
af118b8752f5d13b417792b820a62232af759c2d 13652 kore_4.2.3-1.debian.tar.xz
2e6647ffad89efcabc7294648e87cca147405795 7900 kore_4.2.3-1_source.buildinfo
Checksums-Sha256:
b73b7acbd438b8dd255212c59a06e1a6e045c7f6bdd82497906f6fad720e87b3 1948
kore_4.2.3-1.dsc
f9a9727af97441ae87ff9250e374b9fe3a32a3348b25cb50bd2b7de5ec7f5d82 1085717
kore_4.2.3.orig.tar.gz
996baa55fedd661873fa11016d42db465efafbb7a68668bdcc3b58aec238fa4e 13652
kore_4.2.3-1.debian.tar.xz
0ad1ce9227e63f3883b0986bb133e2f7474741222ce2823f115b5292c1c3f67e 7900
kore_4.2.3-1_source.buildinfo
Files:
0e202df13da530251f4025b235de990b 1948 httpd optional kore_4.2.3-1.dsc
05582349a626603189e04c8c6bb4231b 1085717 httpd optional kore_4.2.3.orig.tar.gz
ef102b845b2cc34c62585f6b886333b2 13652 httpd optional
kore_4.2.3-1.debian.tar.xz
a49e12db2b045146855187c8c70db859 7900 httpd optional
kore_4.2.3-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJLBAEBCgA1FiEEqLZfH4yXKLbSNdjT6exG9aVH8x4FAmhoCrcXHGZvdXJkb2xs
YXJzQGRlYmlhbi5vcmcACgkQ6exG9aVH8x6SEg//VsztLJF9kITCqi6jQELZ2mTh
JCvsUiYhAMF/g6AutGfOyDG10FJeo+oyI5URgidMmm1ZMxwMvqd4i58GPeE/O7eE
6ajxcWcVEpLLsg63ifXmONorYhvdDBsEL/Yhd3Q6lnNuYkKao8lkc0Xu56+4AhAL
QaLujNr2Wz8fvT+c2kTJaPMmtg2/bno4p8gUXPgXu4rSdvZ7GmVBhJwSX8DXwVjZ
qm668T2iVXKUv1efxXr3M1omo3/gN5LXVEl2QomrLbhwiKIX8J/Z8HS/5Djjyux6
xtb2GfmoEBLQ/jA/Dls4LaxdnCPFNfstNIMHh1eQtuc7Vxdk68zZ23EMtxCYi8ZV
SxJ+RYsHqZ/qaic6yYbdtHM1j69mskygORB61sjQNL6mM/nh46cOseJNZOo8hv7s
KmvIU8O7fbhrtXSiug6wpr7iHg8b6MjjTvh3AGk8LoKrwioRG4b2HhJQyvKEog3h
kI2ZvxEDu6wCZTdpr7TQC6ALzvFDtle/Vk7sRLkvfNUAcUU+EiBnKkmYBxjsjMrx
9kyo2ob6OQBEQPwNQm6O8fVSN0bQscz8kxjE5nPJIZMsldU8hjlwvziJqKgm/vGP
/QeVq+HJ+swE+M+wt3QuEnTJHTcix56xX89AoeAe/Vz1X0gVunCRIjduePEuuTqt
0bioin+9l1sNL2wq3sY=
=b3Ii
-----END PGP SIGNATURE-----
pgpnlR8qIrlxy.pgp
Description: PGP signature
--- End Message ---
