Bug#964645: isakmpd: FTBFS: cc: error: Entering: No such file or directory
Source: isakmpd Version: 20041012-9 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200709 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -O2 -g -Wall -DNEED_SYSDEP_APP > -I/<> -I/<>/sysdep/linux -I. -DHAVE_GETNAMEINFO > -DUSE_OLD_SOCKADDR -DHAVE_PCAP -DNEED_SYSDEP_APP -DMP_FLAVOUR=MP_FLAVOUR_GMP > -DUSE_AES -I/<>/sysdep/linux/include > -I/<>/sysdep/common -I/usr/include/openssl -DUSE_DEBUG > -DUSE_TRIPLEDES -DUSE_BLOWFISH -DUSE_CAST -DUSE_EC -DUSE_AGGRESSIVE > -DUSE_X509 -DUSE_DPD -DUSE_NAT_TRAVERSAL -DUSE_ISAKMP_CFG -DUSE_AES > -DUSE_PF_KEY_V2 -I/<>/apps/certpatch/../.. > -I/<>/apps/certpatch/../../sysdep/linux -Imake[2]: Entering > directory '/<>' /<> make[2]: Leaving directory > '/<>' -Wall -DMP_FLAVOUR=MP_FLAVOUR_GMP -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro certpatch.c -lcrypto -lssl -lgmp -o > certpatch > cc: error: Entering: No such file or directory > cc: error: directory: No such file or directory > cc: error: make[2]:: No such file or directory > cc: error: Leaving: No such file or directory > cc: error: directory: No such file or directory > make[2]: *** [: certpatch] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/07/09/isakmpd_20041012-9_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Processing of python-bayespy_0.5.18-3_source.changes
python-bayespy_0.5.18-3_source.changes uploaded successfully to localhost along with the files: python-bayespy_0.5.18-3.dsc python-bayespy_0.5.18-3.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
python-bayespy_0.5.18-3_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 Jul 2020 14:34:54 + Source: python-bayespy Architecture: source Version: 0.5.18-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Graham Inggs Closes: 954590 Changes: python-bayespy (0.5.18-3) unstable; urgency=medium . * QA Upload * Fix FTBFS with recent matplotlib (Closes: #954590) - Add build and test dependencies on python3-pytest - Adjust absolute tolerance for some tests * Switch to debhelper 13 * Set Rules-Requires-Root: no * Bump Standards-Version to 4.5.0, no changes Checksums-Sha1: 33745c2fc9adaee90fd41dbd8b5c4ae1079de29f 2298 python-bayespy_0.5.18-3.dsc 8fed5bd8b16d9f52f2a1b854ed1de1af91c48463 6084 python-bayespy_0.5.18-3.debian.tar.xz Checksums-Sha256: 8610093f0663d6ca990e17f7d17225f5d81c1b841d80daca7e7f50b0e30aebcd 2298 python-bayespy_0.5.18-3.dsc e8fa5386e8d862d4f7d14bdea579419360e37e720fd77015fb957e973f7f22ac 6084 python-bayespy_0.5.18-3.debian.tar.xz Files: 2884dc176966b7057d4abd1a33a8c241 2298 python optional python-bayespy_0.5.18-3.dsc 8e538eb54f70d7334bd93f3381d3b78b 6084 python optional python-bayespy_0.5.18-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl8HN1cACgkQr8/sjmac 4cIW9hAAimy1K45u4CKE/4XqQGnZL5cYoaOP2BrnzEzIy0JqlPYkAzmxCtcBqpq3 EKqc4FK41nkKufp5mr1WWAsMg4jkeOFKdFruNzq2itT6qxg4IcZPdBR/4X9enjtM 73NwoxAQ4JXweq4LEKuPBYOU4JlN5lFDZFXiagFyYqhFoDDn+siki9aHjPHvFO4s GDRUnzUUGxWK3rFGNlnNxV6To9lD7P40Fty73zfvqaZ7zEGSSw+RrSkZl9C0SII5 1uU5ZPh/68vbNwRjYa9BDIdH5shlwTbM9XR6z7HAamJNGbZYGLLlBJr0nknixP+i /HTs/1yb1vPMjMgXyeZJFswz7qCV8cLTn+x3r1L/nJGGMeRVTGYXIdNwqUhVWIM2 r+5c4crStVrfZwr/8zyvW7RtauIML7fyDYbnU23R3UHjTbZ7g9+L2jrYKSvTV5Zy cwRL8xqgYR68NPdkM9hBRYsKGp43F28bDsli3enNaYx9whMRrccH2O80LnSXR5S+ pHp/lb1ie3XM/RfnTMkp6cDayIVWdEWXfTsdD8DpSbYISESA7RIp0ErjO+cKW86X T3DOSXZSR9XwcVkbTWoJn784lKVgrFVcvXHdjYUwFEpK9/5ngIOILzqYIX7bPNIY 0AGlHAmCR5us//BbFJ6GyX79a5SXSc5dZ8wrDOkFmTGoCUiGzGQ= =EHzD -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#954590: marked as done (python-bayespy: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.7 3.8" returned exit code 13)
Your message dated Thu, 09 Jul 2020 16:04:50 +
with message-id
and subject line Bug#954590: fixed in python-bayespy 0.5.18-3
has caused the Debian Bug report #954590,
regarding python-bayespy: FTBFS: dh_auto_test: error: pybuild --test
--test-nose -i python{version} -p "3.7 3.8" returned exit code 13
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.)
--
954590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-bayespy
Version: 0.5.18-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> xvfb-run -a dh_auto_test
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.7_bayespy/build;
> python3.7 -m nose -v
> Test the creation of Bernoulli nodes. ... ok
> Test mixture of Bernoulli ...
> /<>/.pybuild/cpython3_3.7_bayespy/build/bayespy/inference/vmp/nodes/categorical.py:43:
> FutureWarning: Using a non-tuple sequence for multidimensional indexing is
> deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this
> will be interpreted as an array index, `arr[np.array(seq)]`, which will
> result either in an error or a different result.
> u0[[np.arange(np.size(x)), np.ravel(x)]] = 1
> ok
> Test the moments of Bernoulli nodes. ... ok
> Test observation of Bernoulli node ... ok
> Test random sampling in Bernoulli node ... ok
> Test the creation of beta nodes. ... ok
> Test the moments of beta nodes. ... ok
> Test random sampling of beta nodes. ... ok
> Test the creation of binomial nodes. ... ok
> Test binomial mixture ... ok
> Test the moments of binomial nodes. ... ok
> Test observation of Bernoulli node ... ok
> Test random sampling in Binomial node ... ok
> Test constant categorical nodes ... ok
> Check the Euclidean gradient of the categorical node ... ok
> Test the creation of categorical nodes. ... ok
> Test initialization of categorical nodes ...
> /<>/.pybuild/cpython3_3.7_bayespy/build/bayespy/inference/vmp/nodes/categorical.py:43:
> FutureWarning: Using a non-tuple sequence for multidimensional indexing is
> deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this
> will be interpreted as an array index, `arr[np.array(seq)]`, which will
> result either in an error or a different result.
> u0[[np.arange(np.size(x)), np.ravel(x)]] = 1
> ok
> Test the moments of categorical nodes. ... ok
> Test observed categorical nodes ...
> /<>/.pybuild/cpython3_3.7_bayespy/build/bayespy/inference/vmp/nodes/categorical.py:107:
> FutureWarning: Using a non-tuple sequence for multidimensional indexing is
> deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this
> will be interpreted as an array index, `arr[np.array(seq)]`, which will
> result either in an error or a different result.
> u0[[np.arange(np.size(x)), np.ravel(x)]] = 1
> ok
> Test the creation of CategoricalMarkovChain object ... ok
> Test the message of CategoricalMarkovChain to child ... ok
> Test random sampling of categorical Markov chain ... ok
> Test the creation of Concatenate node ... ok
> Test the mask handling in Concatenate node ... ok
> Test the message to child of Concatenate node. ... ok
> Test the message to parents of Concatenate node. ... ok
> Test the mask message to parent of Tile node. ... ok
> Test the moments of Tile node. ... ok
> Test the parent message of Tile node. ... ok
> Test the constant moments of Dirichlet nodes. ... ok
> Test the creation of Dirichlet nodes. ... ok
> Test the moments of Dirichlet nodes. ... ok
> Test the message from SumMultiply to its children. ... ok
> Test the message from SumMultiply node to its parents. ... ok
> Test that the parent nodes are validated properly in SumMultiply ... ok
> test_lower_bound_contribution
> (bayespy.inference.vmp.nodes.tests.test_gamma.TestGamma) ... ok
> Test standard gradient of a Gamma node. ... ok
> Test Riemannian gradient of a Gamma node. ... ok
> Test the creation of Gate node ...
> /<>/.pybuild/cpython3_3.7_bayespy/build/bayespy/inference/vmp/nodes/categorical.py:43:
> FutureWarning: Using a non-tuple sequence for multidimensional indexing is
> deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this
> will be interpreted as an array index, `arr[np.array(seq)]`, which will
> result either in an error or a different result.
> u0[[np.arange(np.size(x)), np.ravel(x)]] = 1
> ok
> Test
Bug#873978: marked as done (sendmail-base: Please check for /usr/share/sendmail/dynamic before sourcing it)
Your message dated Thu, 09 Jul 2020 18:32:26 + with message-id and subject line Bug#873978: fixed in sendmail 8.15.2-8+deb9u1 has caused the Debian Bug report #873978, regarding sendmail-base: Please check for /usr/share/sendmail/dynamic before sourcing it 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.) -- 873978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sendmail-base Version: 8.15.2-8 Severity: serious I had sendmail installed. Then I removed it including sendmail-base. I used "apt-get remove" instead of "purge" and this did not end well. The log was quickly filled with this: |Sep 1 21:28:02 debbuildd dhclient[3221]: DHCPREQUEST of 172.123.10.83 on eth0 to 255.255.255.255 port 67 |Sep 1 21:28:02 debbuildd dhclient[3221]: DHCPOFFER of 172.123.10.83 from 172.123.10.1 |Sep 1 21:28:03 debbuildd dhclient[3221]: DHCPACK of 172.123.10.83 from 172.123.10.1 |Sep 1 21:28:03 debbuildd dhclient[3221]: DHCPDECLINE on eth0 to 255.255.255.255 port 67 |Sep 1 21:28:03 debbuildd dhclient[3221]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 |Sep 1 21:28:03 debbuildd dhclient[3221]: DHCPREQUEST of 172.123.10.83 on eth0 to 255.255.255.255 port 67 |Sep 1 21:28:03 debbuildd dhclient[3221]: DHCPOFFER of 172.123.10.83 from 172.123.10.1 |Sep 1 21:28:03 debbuildd dhclient[3221]: DHCPACK of 172.123.10.83 from 172.123.10.1 |Sep 1 21:28:03 debbuildd dhclient[3221]: DHCPDECLINE on eth0 to 255.255.255.255 port 67 The reason for the DHCPCELINE was: |/sbin/dhclient-script: 28: . :Can't open /usr/share/sendmail/dynamic Which could have been caused by |/etc/network/if-up.d/sendmail:. /usr/share/sendmail/dynamic; |/etc/network/if-post-down.d/sendmail:. /usr/share/sendmail/dynamic; |/etc/network/if-down.d/sendmail:. /usr/share/sendmail/dynamic; |/etc/dhcp/dhclient-exit-hooks.d/sendmail:. /usr/share/sendmail/dynamic; |/etc/ppp/ip-up.d/sendmail:. /usr/share/sendmail/dynamic; |/etc/ppp/ip-down.d/sendmail:. /usr/share/sendmail/dynamic; |/etc/resolvconf/update-libc.d/sendmail:. /usr/share/sendmail/dynamic; but in my case it was /etc/dhcp/dhclient-exit-hooks.d/sendmail. Please either remove those files on remove or test for "/usr/share/sendmail/dynamic" before the script sources the file. This was a headless box so it took while to notice… Sebastian --- End Message --- --- Begin Message --- Source: sendmail Source-Version: 8.15.2-8+deb9u1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of sendmail, 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 873...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated sendmail 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: SHA256 Format: 1.8 Date: Sun, 25 Aug 2019 20:07:11 +0200 Source: sendmail Binary: sendmail-bin rmail sensible-mda libmilter1.0.1 libmilter-dev sendmail-doc sendmail sendmail-base sendmail-cf Architecture: source Version: 8.15.2-8+deb9u1 Distribution: stretch Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Description: libmilter-dev - Sendmail Mail Filter API (Milter) (development files) libmilter1.0.1 - Sendmail Mail Filter API (Milter) rmail - MTA->UUCP remote mail handler sendmail - powerful, efficient, and scalable Mail Transport Agent (metapacka sendmail-base - powerful, efficient, and scalable Mail Transport Agent (arch inde sendmail-bin - powerful, efficient, and scalable Mail Transport Agent sendmail-cf - powerful, efficient, and scalable Mail Transport Agent (config ma sendmail-doc - powerful, efficient, and scalable Mail Transport Agent (documenta sensible-mda - Mail Delivery Agent wrapper Closes: 863567 873978 887064 893424 894535 Changes: sendmail (8.15.2-8+deb9u1) stretch; urgency=medium . * QA upload. * rmail: Add exim4 to the list of conflicting MTAs. (Closes: #863567) * Skip hook execution if /usr/share/sendmail/dynamic does not exist. (Closes: #873978) * debian/examples/network/if-post-down.d/sendmail: Generate during build. * c
Bug#863567: marked as done (rmail: unable to install because of unmet dependency)
Your message dated Thu, 09 Jul 2020 18:32:26 + with message-id and subject line Bug#863567: fixed in sendmail 8.15.2-8+deb9u1 has caused the Debian Bug report #863567, regarding rmail: unable to install because of unmet dependency 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.) -- 863567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rmail Severity: normal rmail is currently uninstallable on Stretch: # apt-get -o Debug::pkgProblemResolver=1 install rmail Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 2 Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) rmail:amd64 < none -> 8.15.2-8 @un puN Ib > Broken rmail:amd64 Depends on sendmail-bin:amd64 < none | 8.15.2-8 @un uH > Considering sendmail-bin:amd64 0 as a solution to rmail:amd64 9998 Re-Instated liblockfile-bin:amd64 Re-Instated liblockfile1:amd64 Re-Instated lockfile-progs:amd64 Re-Instated sendmail-base:amd64 Re-Instated sendmail-cf:amd64 Re-Instated sendmail-bin:amd64 Investigating (0) exim4:amd64 < 4.89-2 @ii mK Ib > Broken exim4:amd64 Depends on exim4-daemon-light:amd64 < 4.89-2 @ii mR > Considering exim4-daemon-light:amd64 0 as a solution to exim4:amd64 7 Added exim4-daemon-light:amd64 to the remove list Broken exim4:amd64 Depends on exim4-daemon-heavy:amd64 < none | 4.89-2 @un uH > Considering exim4-daemon-heavy:amd64 0 as a solution to exim4:amd64 7 Try Installing exim4-daemon-heavy:amd64 < none | 4.89-2 @un uH > before changing exim4:amd64 Fixing exim4:amd64 via keep of exim4-daemon-light:amd64 Investigating (0) exim4-daemon-heavy:amd64 < none -> 4.89-2 @un uN Ib > Broken exim4-daemon-heavy:amd64 Conflicts on mail-transport-agent:amd64 < none @un H > Conflicts//Breaks against version 2.64-8+b2 for ssmtp but that is not InstVer, ignoring Conflicts//Breaks against version 8.15.2-8 for sendmail-bin but that is not InstVer, ignoring Conflicts//Breaks against version 2.0.2+nmu1 for qmail-run but that is not InstVer, ignoring Conflicts//Breaks against version 3.1.4-7 for postfix but that is not InstVer, ignoring Conflicts//Breaks against version 6.0.2p1-2 for opensmtpd but that is not InstVer, ignoring Conflicts//Breaks against version 1:1.13-1.2 for nullmailer but that is not InstVer, ignoring Conflicts//Breaks against version 1.6.6-1 for msmtp-mta but that is not InstVer, ignoring Considering exim4-daemon-light:amd64 0 as a solution to exim4-daemon-heavy:amd64 0 Holding Back exim4-daemon-heavy:amd64 rather than change mail-transport-agent:amd64 Investigating (1) rmail:amd64 < none -> 8.15.2-8 @un puN Ib > Broken rmail:amd64 Conflicts on exim4-daemon-light:amd64 < 4.89-2 @ii mK > Considering exim4-daemon-light:amd64 0 as a solution to rmail:amd64 9998 Added exim4-daemon-light:amd64 to the remove list Fixing rmail:amd64 via remove of exim4-daemon-light:amd64 Investigating (1) exim4:amd64 < 4.89-2 @ii mK Ib > Broken exim4:amd64 Depends on exim4-daemon-light:amd64 < 4.89-2 @ii mR > Considering exim4-daemon-light:amd64 0 as a solution to exim4:amd64 7 Added exim4-daemon-light:amd64 to the remove list Broken exim4:amd64 Depends on exim4-daemon-heavy:amd64 < none | 4.89-2 @un uH > Considering exim4-daemon-heavy:amd64 0 as a solution to exim4:amd64 7 Try Installing exim4-daemon-heavy:amd64 < none | 4.89-2 @un uH > before changing exim4:amd64 Fixing exim4:amd64 via keep of exim4-daemon-light:amd64 Investigating (1) exim4-daemon-heavy:amd64 < none -> 4.89-2 @un uN Ib > Broken exim4-daemon-heavy:amd64 Conflicts on mail-transport-agent:amd64 < none @un H > Conflicts//Breaks against version 2.64-8+b2 for ssmtp but that is not InstVer, ignoring Conflicts//Breaks against version 8.15.2-8 for sendmail-bin but that is not InstVer, ignoring Conflicts//Breaks against version 2.0.2+nmu1 for qmail-run but that is not InstVer, ignoring Conflicts//Breaks against version 3.1.4-7 for postfix but that is not InstVer, ignoring Conflicts//Breaks against version 6.0.2p1-2 for opensmtpd but that is not InstVer, ignoring Conflicts//Breaks against version 1:1.13-1.2 for nullmailer but that is not InstVer, ignoring Conflicts//Breaks against version 1.6.6-1 for msmtp-mta but that is not InstVer, ignoring Considering exim4-daemon-light:amd64 0 as a solution to exim4-daemon-heavy:amd64 0 Holding Back exim4-daemon-heavy:amd64 rather than change mail-transport-agent:amd64 Investigating (2) rmail:amd64 <
Bug#887064: marked as done ([sendmail] persistent queue runners in split daemon mode missed by /etc/init.d/sendmail)
Your message dated Thu, 09 Jul 2020 18:32:26 +
with message-id
and subject line Bug#887064: fixed in sendmail 8.15.2-8+deb9u1
has caused the Debian Bug report #887064,
regarding [sendmail] persistent queue runners in split daemon mode missed by
/etc/init.d/sendmail
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.)
--
887064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sendmail-bin
Version: 8.15.2-8
Tags: patch
When sendmail is configured with persistent queue runners *and* the
queue runner control process is separate from the main MTA daemon,
/etc/init.d/sendmail fails to find the queue runner control process and
deletes the pid file after startup. This results in the queue runners
not being terminated at shutdown or restart.
Here's how to reproduce this behaviour:
Activate persistent queue runners e.g. by setting
QUEUE_INTERVAL="p1m";
in /etc/mail/sendmail.conf
Make sure that "split daemon" mode is active, i.e. that the MTA listener
daemon is a separate process from queue runner control (otherwise the
bug does not show). Among other situations, this is the case when
QUEUE_PARMS is different from DAEMON_PARMS. For debugging purposes,
just set some option such as
QUEUE_PARMS="-O QueueFactor=60";
in /etc/mail/sendmail.conf
Run sendmailconfig; /etc/init.d/sendmail restart
At this point, the MTA listener daemon and queue control
pids should be recorded in /run/sendmail/mta/sendmail.pid and
/run/sendmail/mta/queue.pid, respectively. However, /etc/init.d/sendmail
has checked for the queue control process after startup, was unable to
find it, and has deleted /run/sendmail/mta/queue.pid.
Run /etc/init.d/sendmail stop
At this point, there should be no more sendmail processes; in fact,
both the queue runner control process and all configured queue runners
are still present.
I believe the problem results from Debian calling the sendmail binary
as "sendmail-mta" while /etc/init.d/sendmail checks for a process with
an executable called "sendmail". Patching /etc/init.d/sendmail to
check for sendmail-mta in this particular case (split-daemon mode and
persistent queue runners) seems to fix the problem for me. Other ps
invocations in /etc/init.d/sendmail do not select by binary names and
are thus not affected.
Here's a patch:
--- etc/init.d/sendmail.orig2016-12-08 17:43:49.0 +
+++ etc/init.d/sendmail 2018-01-13 08:06:45.350670214 +
@@ -289,7 +289,7 @@
if [ -z "$qp" ]; then
chmod 0664 $MTAQ_PIDFILE;
else
- qc=`ps --no-headers -fCsendmail \
+ qc=`ps --no-headers -fCsendmail-mta \
| egrep -e 'Queue control' \
| awk '{print $2}'`;
if [ -z "$qc" ]; then
--- End Message ---
--- Begin Message ---
Source: sendmail
Source-Version: 8.15.2-8+deb9u1
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
sendmail, 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 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated sendmail 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: SHA256
Format: 1.8
Date: Sun, 25 Aug 2019 20:07:11 +0200
Source: sendmail
Binary: sendmail-bin rmail sensible-mda libmilter1.0.1 libmilter-dev
sendmail-doc sendmail sendmail-base sendmail-cf
Architecture: source
Version: 8.15.2-8+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andreas Beckmann
Description:
libmilter-dev - Sendmail Mail Filter API (Milter) (development files)
libmilter1.0.1 - Sendmail Mail Filter API (Milter)
rmail - MTA->UUCP remote mail handler
sendmail - powerful, efficient, and scalable Mail Transport Agent (metapacka
sendmail-base - powerful, efficient, and scalable Mail Transport Agent (arch
inde
sendmail-bin - powerful, efficient, and scalable Mail Transport Agent
sendmail-cf - powerful, efficient, and scalable M
Bug#894535: marked as done (sendmail: Typo in apt show sendmail)
Your message dated Thu, 09 Jul 2020 18:32:26 +
with message-id
and subject line Bug#894535: fixed in sendmail 8.15.2-8+deb9u1
has caused the Debian Bug report #894535,
regarding sendmail: Typo in apt show sendmail
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.)
--
894535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sendmail
Version: 8.15.2-8
Severity: minor
Dear Maintainer,
Paragraph "Fortunately, simple thing can be done easily, and complex things
are possible, even if not easily understood ;) Sendmail is the *ONLY*
MTA with a Turing complete language to control *ALL* aspects of delivery!"
"Thing" should read "things"
-- Package-specific info:
Output of /usr/share/bug/sendmail/script:
ls -alR /etc/mail:
/etc/mail:
total 236
drwxr-sr-x 7 smmta smmsp 4096 Mar 29 12:27 .
drwxr-xr-x 128 root root 12288 Mar 31 23:22 ..
-rwxr-xr-- 1 root smmsp 10019 Mar 29 12:26 Makefile
-rw--- 1 root root 4265 Mar 29 12:26 access
-rw-r- 1 smmta smmsp 12288 Mar 29 12:26 access.db
-rw-r--r-- 1 root root281 Dec 8 2016 address.resolve
lrwxrwxrwx 1 root smmsp10 Mar 29 12:26 aliases -> ../aliases
-rw-r- 1 smmta smmsp 12288 Mar 29 12:27 aliases.db
-rw-r--r-- 1 root root 3219 Mar 29 12:26 databases
-rw-r--r-- 1 root root 5659 Dec 8 2016 helpfile
-rw-r--r-- 1 root smmsp17 Mar 29 12:26 local-host-names
drwxr-sr-x 2 smmta smmsp 4096 Mar 29 12:26 m4
drwxr-xr-x 2 root root 4096 Mar 29 12:26 peers
drwxr-xr-x 2 root smmsp 4096 Dec 8 2016 sasl
-rw-r--r-- 1 root smmsp 64154 Mar 29 12:26 sendmail.cf
-rw-r--r-- 1 root root 12236 Mar 29 12:26 sendmail.conf
-rw-r--r-- 1 root smmsp 4058 Mar 29 12:26 sendmail.mc
-rw-r--r-- 1 root root149 Dec 8 2016 service.switch
-rw-r--r-- 1 root root180 Dec 8 2016 service.switch-nodns
drwxr-sr-x 2 smmta smmsp 4096 Mar 29 12:26 smrsh
-rw-r--r-- 1 root smmsp 44594 Mar 29 12:26 submit.cf
-rw-r--r-- 1 root smmsp 2374 Mar 29 12:26 submit.mc
drwxr-xr-x 2 smmta smmsp 4096 Mar 29 12:26 tls
-rw-r--r-- 1 root smmsp 0 Mar 29 12:26 trusted-users
/etc/mail/m4:
total 8
drwxr-sr-x 2 smmta smmsp 4096 Mar 29 12:26 .
drwxr-sr-x 7 smmta smmsp 4096 Mar 29 12:27 ..
-rw-r- 1 root smmsp0 Mar 29 12:26 dialup.m4
-rw-r- 1 root smmsp0 Mar 29 12:26 provider.m4
/etc/mail/peers:
total 12
drwxr-xr-x 2 root root 4096 Mar 29 12:26 .
drwxr-sr-x 7 smmta smmsp 4096 Mar 29 12:27 ..
-rw-r--r-- 1 root root 328 Dec 8 2016 provider
/etc/mail/sasl:
total 8
drwxr-xr-x 2 root smmsp 4096 Dec 8 2016 .
drwxr-sr-x 7 smmta smmsp 4096 Mar 29 12:27 ..
/etc/mail/smrsh:
total 8
drwxr-sr-x 2 smmta smmsp 4096 Mar 29 12:26 .
drwxr-sr-x 7 smmta smmsp 4096 Mar 29 12:27 ..
lrwxrwxrwx 1 root smmsp 26 Mar 29 12:26 mail.local ->
/usr/lib/sm.bin/mail.local
lrwxrwxrwx 1 root smmsp 17 Mar 29 12:26 procmail -> /usr/bin/procmail
/etc/mail/tls:
total 48
drwxr-xr-x 2 smmta smmsp 4096 Mar 29 12:26 .
drwxr-sr-x 7 smmta smmsp 4096 Mar 29 12:27 ..
-rw-r--r-- 1 root root 7 Mar 29 12:26 no_prompt
-rw--- 1 root root 1191 Mar 29 12:26 sendmail-client.cfg
-rw-r--r-- 1 root smmsp 1176 Mar 29 12:26 sendmail-client.crt
-rw--- 1 root root 989 Mar 29 12:26 sendmail-client.csr
-rw-r- 1 root smmsp 1675 Mar 29 12:26 sendmail-common.key
-rw-r- 1 root smmsp 1650 Mar 29 12:26 sendmail-common.prm
-rw--- 1 root root 1191 Mar 29 12:26 sendmail-server.cfg
-rw-r--r-- 1 root smmsp 1176 Mar 29 12:26 sendmail-server.crt
-rw--- 1 root root 989 Mar 29 12:26 sendmail-server.csr
-rwxr--r-- 1 root root 3248 Mar 29 12:26 starttls.m4
sendmail.conf:
DAEMON_NETMODE="Static";
DAEMON_NETIF="eth0";
DAEMON_MODE="Daemon";
DAEMON_PARMS="";
DAEMON_HOSTSTATS="No";
DAEMON_MAILSTATS="No";
QUEUE_MODE="${DAEMON_MODE}";
QUEUE_INTERVAL="10m";
QUEUE_PARMS="";
MSP_MODE="Cron";
MSP_INTERVAL="20m";
MSP_PARMS="";
MSP_MAILSTATS="${DAEMON_MAILSTATS}";
MISC_PARMS="";
CRON_MAILTO="root";
CRON_PARMS="";
LOG_CMDS="No";
HANDS_OFF="No";
AGE_DATA="";
DAEMON_RUNASUSER="No";
DAEMON_STATS="${DAEMON_MAILSTATS}";
MSP_STATS="${MSP_MAILSTATS}";
sendmail.mc:
divert(-1)dnl
divert(0)dnl
define(`_USE_ETC_MAIL_')dnl
include(`/usr/share/sendmail/cf/m4/cf.m4')dnl
VERSIONID(`$Id: sendmail.mc, v 8.15.2-8 2016-12-08 18:43:49 cowboy Exp $')
OSTYPE(`debian')dnl
DOMAIN(`debian-mta')dnl
undefine(`confHOST_STATUS_DIRECTORY')dnl#DAEMON_HOSTSTATS=
FEATURE(`no_default_msa')dnl
DAEMON_OPTIONS(`Family=inet, Name=MTA-v4, Port=smtp, Addr=127.0.0.1')dnl
DA
Bug#952009: marked as done (c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant)
Your message dated Thu, 09 Jul 2020 18:32:23 + with message-id and subject line Bug#952009: fixed in c-icap-modules 1:0.4.4-1+deb9u2 has caused the Debian Bug report #952009, regarding c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant 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.) -- 952009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: c-icap-modules Version: 1:0.5.3-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -fvisibility=hidden -DCI_BUILD_MODULE > -D_REENTRANT -g -O2 -fdebug-prefix-map=/build/c-icap-FHVm1G/c-icap-0.5.3=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall > -D_FILE_OFFSET_BITS=64 -I/usr/include -I/usr/include/c_icap -module > -avoid-version -Wl,-z,relro -Wl,-z,now -o clamd_mod.la -rpath > /usr/lib/x86_64-linux-gnu/c_icap/ clamd_mod_la-clamd_mod.lo > libtool: link: gcc -shared -fPIC -DPIC .libs/clamd_mod_la-clamd_mod.o-g > -O2 -fstack-protector-strong -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro > -Wl,-z -Wl,now -Wl,-soname -Wl,clamd_mod.so -o .libs/clamd_mod.so > In file included from /usr/include/clamav.h:69, > from clamav_mod.c:27: > clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant > 108 | static char CLAMAV_VERSION[CLAMAV_VERSION_SIZE]; > | ^~ > clamav_mod.c: In function ‘clamav_set_versions’: > clamav_mod.c:645:6: warning: assignment of read-only location ‘"0.102.2"[63]’ > 645 | CLAMAV_VERSION[CLAMAV_VERSION_SIZE - 1] = '\0'; > | ^~ > make[4]: *** [Makefile:512: clamav_mod_la-clamav_mod.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/c-icap-modules_0.5.3-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: c-icap-modules Source-Version: 1:0.4.4-1+deb9u2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of c-icap-modules, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated c-icap-modules 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: Mon, 06 Jul 2020 23:32:58 +0300 Source: c-icap-modules Binary: libc-icap-mod-virus-scan libc-icap-mod-clamav libc-icap-mod-urlcheck libc-icap-mod-contentfiltering Architecture: source Version: 1:0.4.4-1+deb9u2 Distribution: stretch Urgency: medium Maintainer: Mathieu Parent Changed-By: Adrian Bunk Description: libc-icap-mod-clamav - transitional dummy package libc-icap-mod-contentfiltering - Content filtering Service for c-icap libc-icap-mod-urlcheck - URL Check Service for c-icap libc-icap-mod-virus-scan - Antivirus Service for c-icap Closes: 952009 Changes: c-icap-modules (1:0.4.4-1+deb9u2) stretch; urgency=medium . * Non-maintainer upload. * Backport support for ClamAV 0.102. (Closes: #952009) Checksums-Sha1: c64331eab9c1345d1778a89af97ece38f7ce2ff2 2371 c-icap-modules_0.4.4-1+deb9u2.dsc a58bbaa92c46b45b576930bbec344c263788ef75 7228 c-icap-modules_0.4.4-1+deb9u2.debian.tar.xz Checksums-Sha256: aa0d196f25dfb7d61e97f5d172e0fb781ff5547758cc41d48332615e46015b3c 2371 c-icap-modules_0.4.4-1+deb9u2.dsc 8b65559eaf8dbf0106f3605068ac156e98233b53be5bfef7af2506c0fddeb1e6 7228 c-icap-modules_0.4.4-1+deb9u2.debian
Bug#893424: marked as done (Cannot uninstall package)
Your message dated Thu, 09 Jul 2020 18:32:26 +
with message-id
and subject line Bug#893424: fixed in sendmail 8.15.2-8+deb9u1
has caused the Debian Bug report #893424,
regarding Cannot uninstall package
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.)
--
893424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sendmail-base
Version: 8.15.2-10
Severity: serious
Due to a bug in the maintainer script, sendmail-base cannot be uninstalled:
rak@zeta:~$ sudo apt-get remove sendmail-base
[sudo] password for rak:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
lockfile-progs
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
sendmail-base
0 upgraded, 0 newly installed, 1 to remove and 52 not upgraded.
After this operation, 867 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 388617 files and directories currently installed.)
Removing sendmail-base (8.15.2-10) ...
rm: cannot remove '/etc/mail/m4': Is a directory
dpkg: error processing package sendmail-base (--remove):
installed sendmail-base package pre-removal script subprocess returned error
exit status 123
Errors were encountered while processing:
sendmail-base
E: Sub-process /usr/bin/dpkg returned an error code (1)
rak@zeta:~$ sudo apt-get purge sendmail-base
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
lockfile-progs
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
sendmail-base*
0 upgraded, 0 newly installed, 1 to remove and 52 not upgraded.
After this operation, 867 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 388617 files and directories currently installed.)
Removing sendmail-base (8.15.2-10) ...
rm: cannot remove '/etc/mail/m4': Is a directory
dpkg: error processing package sendmail-base (--remove):
installed sendmail-base package pre-removal script subprocess returned error
exit status 123
Errors were encountered while processing:
sendmail-base
E: Sub-process /usr/bin/dpkg returned an error code (1)
-- Package-specific info:
Output of /usr/share/bug/sendmail-base/script:
ls -alR /etc/mail:
/etc/mail:
total 24
drwxr-xr-x 1 root root 138 Mar 18 14:32 .
drwxr-xr-x 1 root root 5364 Mar 18 13:50 ..
-rw-r--r-- 1 root root 281 Jan 13 17:43 address.resolve
drwxr-xr-x 1 root root 0 Jan 13 17:43 m4
drwxr-xr-x 1 root root16 Mar 18 13:30 peers
-rw-r--r-- 1 root root 12235 Mar 18 13:33 sendmail.conf
-rw-r--r-- 1 root root 148 Jan 13 17:43 service.switch
-rw-r--r-- 1 root root 179 Jan 13 17:43 service.switch-nodns
/etc/mail/m4:
total 0
drwxr-xr-x 1 root root 0 Jan 13 17:43 .
drwxr-xr-x 1 root root 138 Mar 18 14:32 ..
/etc/mail/peers:
total 4
drwxr-xr-x 1 root root 16 Mar 18 13:30 .
drwxr-xr-x 1 root root 138 Mar 18 14:32 ..
-rw-r--r-- 1 root root 328 Jan 13 17:43 provider
sendmail.conf:
DAEMON_NETMODE="Static";
DAEMON_NETIF="eth0";
DAEMON_MODE="Daemon";
DAEMON_PARMS="";
DAEMON_HOSTSTATS="No";
DAEMON_MAILSTATS="No";
QUEUE_MODE="${DAEMON_MODE}";
QUEUE_INTERVAL="10m";
QUEUE_PARMS="";
MSP_MODE="Cron";
MSP_INTERVAL="20m";
MSP_PARMS="";
MSP_MAILSTATS="${DAEMON_MAILSTATS}";
MISC_PARMS="";
CRON_MAILTO="root";
CRON_PARMS="";
LOG_CMDS="No";
HANDS_OFF="No";
AGE_DATA="";
DAEMON_RUNASUSER="No";
DAEMON_STATS="${DAEMON_MAILSTATS}";
MSP_STATS="${MSP_MAILSTATS}";
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_CA.UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set
to en_CA.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sendmail-base depends on:
ii adduser 3.117
ii lockfile-progs 0.1.17+b1
ii m4 1.4.18-1
ii make4.2.1-1
ii netbase 5.4
ii perl5.26.1-5
sendmail-base recommends no packages.
Versions of packages sendmail-base suggests:
ii ca-certificates 20170717
pn logcheck
ii logrotate3.11.0-0.1
sendmail_8.15.2-8+deb9u1_source.changes ACCEPTED into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Aug 2019 20:07:11 +0200 Source: sendmail Binary: sendmail-bin rmail sensible-mda libmilter1.0.1 libmilter-dev sendmail-doc sendmail sendmail-base sendmail-cf Architecture: source Version: 8.15.2-8+deb9u1 Distribution: stretch Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Description: libmilter-dev - Sendmail Mail Filter API (Milter) (development files) libmilter1.0.1 - Sendmail Mail Filter API (Milter) rmail - MTA->UUCP remote mail handler sendmail - powerful, efficient, and scalable Mail Transport Agent (metapacka sendmail-base - powerful, efficient, and scalable Mail Transport Agent (arch inde sendmail-bin - powerful, efficient, and scalable Mail Transport Agent sendmail-cf - powerful, efficient, and scalable Mail Transport Agent (config ma sendmail-doc - powerful, efficient, and scalable Mail Transport Agent (documenta sensible-mda - Mail Delivery Agent wrapper Closes: 863567 873978 887064 893424 894535 Changes: sendmail (8.15.2-8+deb9u1) stretch; urgency=medium . * QA upload. * rmail: Add exim4 to the list of conflicting MTAs. (Closes: #863567) * Skip hook execution if /usr/share/sendmail/dynamic does not exist. (Closes: #873978) * debian/examples/network/if-post-down.d/sendmail: Generate during build. * connect-from-null.patch: New, fix "NOQUEUE: connect from (null)", thanks to Michael Grant and Claus Assmann. * Fix finding the queue runner control process in "split daemon" mode, thanks to Marc Andre Selig. (Closes: #887064) * Fix prerm failure on btrfs. (Closes: #893424) * Switch Vcs-* URLs to salsa.debian.org. * Fix typos in descriptions. (Closes: #894535) * sendmail-bin.prerm: Stop sendmail before removing the alternatives. Checksums-Sha1: 75284ae33b217bb4dfa92b4fea0df445231ac28d 2561 sendmail_8.15.2-8+deb9u1.dsc e7485d43f311b18a40caab5ae6b7a6c9bd88c097 407432 sendmail_8.15.2-8+deb9u1.debian.tar.xz fd7405279fb1fdb45db5e1d21a8586c131c97af5 6528 sendmail_8.15.2-8+deb9u1_source.buildinfo Checksums-Sha256: 5fd23723c263b9319f0d4343ad5b1b540f51ca15c778a9a5e7c1add63a1296eb 2561 sendmail_8.15.2-8+deb9u1.dsc 05a88a7ec27566be71b493c576e93018f3004ef36d766b545fb05d27b5264471 407432 sendmail_8.15.2-8+deb9u1.debian.tar.xz cd941313c5805966bae94dfcd8d479a622c6b205f94f17fa903f30f15356ccbe 6528 sendmail_8.15.2-8+deb9u1_source.buildinfo Files: f86d1916ac4ccea2792f4dbf2691c447 2561 mail extra sendmail_8.15.2-8+deb9u1.dsc 498fb31428ca2adefd5eb51510419950 407432 mail extra sendmail_8.15.2-8+deb9u1.debian.tar.xz 4fc0bd65e7251ea5fc5b7114f4f741b0 6528 mail extra sendmail_8.15.2-8+deb9u1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl8DMSUQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCL+nD/9662kywkfDi+ICEIvqnTqlM9ySSJRPIPIX ibDM8qDkzit4O2U0ZtermmFHsOBYN+y/Mz57A4gWiQhXmS69+TTQztQYRqJcWTaL GISR/3AW6NGnQCyNAf7UuJ3hW2qhRxhKWVJouEQ3HSXqSFFx2/HRLWrEdI/ihi2F DAQhCKYN64GDT4YUDpTdOehCHetvK1omXJCLsDhieJ3bui3dyWEU/kVlM27M577l qpTtXc2d2Az/lvhuigX5MQqGN7Ev4xobnPHMXynIVOLRr7CdifFJyVCR1gNK7adX 62TmqABHu7q86s1OP5CMT6wx82cHnQ6Waijge+2U6T96mGnr3mETsii3C5kSS/Kk R6ITEoPNz1okq/ogVXPLcdnfKAQX1pydn/I1UWgnDSQ7dp6o2b/e7dtQbQGMF9/p LR/4mooG3YZcOmXSaIFvnYzffZEVzVIUOYNQIatusjCXgmwOJaTBdS322oeWM0Dk N8AgcFx/4hZFwHPQx5ab2kdV1DaRJAYaTDugpfaVdal6iNelNlapDAFe0AYlOPPP 8ew2FN7CYi3mtgLCmUmWRb9LzICVfU/qpqkUvQ0jFjHTD+d87s55lZm6R6rhXqma 3tKs7ogE14uiSf6AFk5jJNnFcJnftiAR+Dk4MBxcgIcfq85621ZhIahYJ/Cz+s6e x+aBz1MQ7g== =bu4G -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#952009: marked as done (c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant)
Your message dated Thu, 09 Jul 2020 19:17:08 + with message-id and subject line Bug#952009: fixed in c-icap-modules 1:0.5.3-1+deb10u1 has caused the Debian Bug report #952009, regarding c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant 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.) -- 952009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: c-icap-modules Version: 1:0.5.3-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -fvisibility=hidden -DCI_BUILD_MODULE > -D_REENTRANT -g -O2 -fdebug-prefix-map=/build/c-icap-FHVm1G/c-icap-0.5.3=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall > -D_FILE_OFFSET_BITS=64 -I/usr/include -I/usr/include/c_icap -module > -avoid-version -Wl,-z,relro -Wl,-z,now -o clamd_mod.la -rpath > /usr/lib/x86_64-linux-gnu/c_icap/ clamd_mod_la-clamd_mod.lo > libtool: link: gcc -shared -fPIC -DPIC .libs/clamd_mod_la-clamd_mod.o-g > -O2 -fstack-protector-strong -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro > -Wl,-z -Wl,now -Wl,-soname -Wl,clamd_mod.so -o .libs/clamd_mod.so > In file included from /usr/include/clamav.h:69, > from clamav_mod.c:27: > clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant > 108 | static char CLAMAV_VERSION[CLAMAV_VERSION_SIZE]; > | ^~ > clamav_mod.c: In function ‘clamav_set_versions’: > clamav_mod.c:645:6: warning: assignment of read-only location ‘"0.102.2"[63]’ > 645 | CLAMAV_VERSION[CLAMAV_VERSION_SIZE - 1] = '\0'; > | ^~ > make[4]: *** [Makefile:512: clamav_mod_la-clamav_mod.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/c-icap-modules_0.5.3-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: c-icap-modules Source-Version: 1:0.5.3-1+deb10u1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of c-icap-modules, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated c-icap-modules 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: Mon, 06 Jul 2020 23:40:47 +0300 Source: c-icap-modules Architecture: source Version: 1:0.5.3-1+deb10u1 Distribution: buster Urgency: medium Maintainer: Mathieu Parent Changed-By: Adrian Bunk Closes: 952009 Changes: c-icap-modules (1:0.5.3-1+deb10u1) buster; urgency=medium . * Non-maintainer upload. * Backport support for ClamAV 0.102. (Closes: #952009) Checksums-Sha1: b3ac62d7618d0808b4543badde42fd81afdfec38 2238 c-icap-modules_0.5.3-1+deb10u1.dsc 2bcc1dc66435a673b675b010f062a480da56038d 6340 c-icap-modules_0.5.3-1+deb10u1.debian.tar.xz Checksums-Sha256: f1132600b2e6160707ffd5e9cd02794f155d5b157009f1a992cd0ec731e25adf 2238 c-icap-modules_0.5.3-1+deb10u1.dsc fb4c54c1d95048abbceaab4761625c0cc91490dc4f42492b44ac8745c9901f62 6340 c-icap-modules_0.5.3-1+deb10u1.debian.tar.xz Files: 3d8055f537a02ffd1edff17b78b19629 2238 net optional c-icap-modules_0.5.3-1+deb10u1.dsc 6175fb3b3233e573b60e3f7376485dbc 6340 net optional c-icap-modules_0.5.3-1+deb10u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8Dji4ACgkQiNJCh6LY mLEebg//bXQCB0k4CM9IkRELnh0WZU8/otkm+g45Na1vkaaR9ia
Bug#956927: marked as done (wav2cdr is broken on 64bit architectures other than amd64 and alpha)
Your message dated Thu, 09 Jul 2020 19:32:15 + with message-id and subject line Bug#956927: fixed in wav2cdr 2.3.4-2+deb10u1 has caused the Debian Bug report #956927, regarding wav2cdr is broken on 64bit architectures other than amd64 and alpha 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.) -- 956927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wav2cdr Version: 2.3.4-3 Severity: important The new and first CI test[1] for wav2cdr fails in arm64[2]. Consequently, the revision 2.3.4-3 will not migrate to testing. [1] https://salsa.debian.org/debian/wav2cdr/-/blob/debian/master/debian/tests/control [2] https://ci.debian.net/data/autopkgtest/testing/arm64/w/wav2cdr/4822988/log.gz The significative output is: autopkgtest [19:42:07]: test command1: wav2cdr -V | grep Version autopkgtest [19:42:07]: test command1: [--- wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed. autopkgtest [19:42:07]: test command1: ---] autopkgtest [19:42:07]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL non-zero exit status 1 autopkgtest [19:42:07]: test command1: - - - - - - - - - - stderr - - - - - - - - - - wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed. [...] autopkgtest [19:42:16]: test command2: wav2cdr --help | grep describes autopkgtest [19:42:16]: test command2: [--- wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed. autopkgtest [19:42:16]: test command2: ---] autopkgtest [19:42:16]: test command2: - - - - - - - - - - results - - - - - - - - - - command2 FAIL non-zero exit status 1 autopkgtest [19:42:17]: test command2: - - - - - - - - - - stderr - - - - - - - - - - wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed. [...] autopkgtest [19:42:21]: test command3: wav2cdr debian/tests/silence.wav $AUTOPKGTEST_TMP/silence.mp3 autopkgtest [19:42:21]: test command3: [--- wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed. bash: line 1: 837 Aborted bash -ec 'wav2cdr debian/tests/silence.wav $AUTOPKGTEST_TMP/silence.mp3' 2> >(tee -a /tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stdout) autopkgtest [19:42:21]: test command3: ---] autopkgtest [19:42:21]: test command3: - - - - - - - - - - results - - - - - - - - - - command3 FAIL non-zero exit status 134 autopkgtest [19:42:22]: test command3: - - - - - - - - - - stderr - - - - - - - - - - wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed. autopkgtest [19:42:22]: summary command1 FAIL non-zero exit status 1 command2 FAIL non-zero exit status 1 command3 FAIL non-zero exit status 134 Eriberto --- End Message --- --- Begin Message --- Source: wav2cdr Source-Version: 2.3.4-2+deb10u1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of wav2cdr, 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 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated wav2cdr 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: Sun, 05 Jul 2020 23:09:10 +0300 Source: wav2cdr Architecture: source Version: 2.3.4-2+deb10u1 Distribution: buster Urgency: medium Maintainer: Debian QA Group Changed-By: Adrian Bunk Closes: 956927 Changes: wav2cdr (2.3.4-2+deb10u1) buster; urgency=medium . * QA upload. * Use C99 fixed-size integer types to fix runtime assertion on 64bit architectures other than amd64 and alpha. (Closes: #956927) * Stop linking to the dead Homepage. Checksums-Sha1: 7af5ece544e8f7c9b55823ab52037b5cbf50b58a 1716 wav2cdr_2.3.4-2+deb10u1.dsc 79596e42f7831c6408db75c6ac92b90765b5442c 10608 wav2cdr_2.3.4-2+deb10u1.debian.tar.xz Checksums-Sha256: a1386c934afd54947296d25d6a10d9829dfb
Bug#958578: marked as done (wav2cdr is broken on 64bit architectures other than amd64 and alpha)
Your message dated Thu, 09 Jul 2020 19:32:15 + with message-id and subject line Bug#956927: fixed in wav2cdr 2.3.4-2+deb10u1 has caused the Debian Bug report #956927, regarding wav2cdr is broken on 64bit architectures other than amd64 and alpha 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.) -- 956927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wav2cdr Version: 2.3.4-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), With a recent upload of wav2cdr you added an autopkgtest, great. However it fails on arm64. I copied some of the output at the bottom of this report. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=wav2cdr https://ci.debian.net/data/autopkgtest/testing/arm64/w/wav2cdr/4822988/log.gz autopkgtest [19:42:21]: test command3: wav2cdr debian/tests/silence.wav $AUTOPKGTEST_TMP/silence.mp3 autopkgtest [19:42:21]: test command3: [--- wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed. bash: line 1: 837 Aborted bash -ec 'wav2cdr debian/tests/silence.wav $AUTOPKGTEST_TMP/silence.mp3' 2> >(tee -a /tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stdout) autopkgtest [19:42:21]: test command3: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: wav2cdr Source-Version: 2.3.4-2+deb10u1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of wav2cdr, 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 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated wav2cdr 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: Sun, 05 Jul 2020 23:09:10 +0300 Source: wav2cdr Architecture: source Version: 2.3.4-2+deb10u1 Distribution: buster Urgency: medium Maintainer: Debian QA Group Changed-By: Adrian Bunk Closes: 956927 Changes: wav2cdr (2.3.4-2+deb10u1) buster; urgency=medium . * QA upload. * Use C99 fixed-size integer types to fix runtime assertion on 64bit architectures other than amd64 and alpha. (Closes: #956927) * Stop linking to the dead Homepage. Checksums-Sha1: 7af5ece544e8f7c9b55823ab52037b5cbf50b58a 1716 wav2cdr_2.3.4-2+deb10u1.dsc 79596e42f7831c6408db75c6ac92b90765b5442c 10608 wav2cdr_2.3.4-2+deb10u1.debian.tar.xz Checksums-Sha256: a1386c934afd54947296d25d6a10d9829dfb86b934e524d19d4b472e2ef97446 1716 wav2cdr_2.3.4-2+deb10u1.dsc dcfd6fd4b270e15a8df49aa83b8623b02668b9b602a9da67f4a6d88e36e06e8f 10608 wav2cdr_2.3.4-2+deb10u1.debian.tar.xz Files: 3ad4b96aab5b0b9578f5db5bdbf3563d 1716 sound optional wav2cdr_2.3.4-2+deb10u1.dsc 374a0c4fa5973968ddf84c3edc7b1ce1 10608 sound optional wav2cdr_2.3.4-2+deb10u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8CNbUACgkQiNJCh6LY mLFetg/8CWaBqU6z+TcEykJbr2jgyRr5MvNM9Ejw7Jdcri4jDoGpN4XNeCy8bnmG DOUZ+MWgpg48efDHFuDWo1n57HlACFgfl3gmdhAogGt4Ez8HrxcMFswQVKxwmvET uoLbyhFZQcZrwhr67t283lNJWggZMDbQEIufY2ofzB1a4glcxpvec1ogx0BtyZ9A U7hoPXUdOPxNKV3pOaohLOgC866txmljXmWIaTGkdr/Is1j+Q4V9OBIbqPdtLH32 4ZY7OKhx+CocM1oQ9yMOVHqjLrb9LjetDxqQW7/D4bQnNpKj2m1vflGAook9Y/Ky a9ZXy/bUPF+EnG/85MGNtefkTxbiE1kxYglQyM4F4XvqYElMfOjTBFT5zTMgu3yc EH4D9qwSxkSzbKhNUv+dgGBTvzSZHV7jnnrb2rJaIVbA4ey384VA/o/ENh69Syag vqG/sr75VFyzpQJehJXrT1liTtPLHh8VgmQ3Tyi3nOz4MGJvja1RYx7cUOvOlzjf BAlxcix4W0UkM98AWwaz0v4gzYDZT3VbAw1zHOuf3wPlpyoGeX9r84v4BP4Or9nQ scEcEF+mAcKlwFACw8WotYcTx6FjqzQr5eJGBKbDygQFypnR1wb0eUspFM/l68Jv Vj/4pN6CTYKsemgE5dtPiyjrLzOUkg95O4WYCLIdHBmaJuoZvuI= =MJWC -END PGP SIGNATURE End Message ---
wav2cdr_2.3.4-2+deb10u1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Jul 2020 23:09:10 +0300 Source: wav2cdr Architecture: source Version: 2.3.4-2+deb10u1 Distribution: buster Urgency: medium Maintainer: Debian QA Group Changed-By: Adrian Bunk Closes: 956927 Changes: wav2cdr (2.3.4-2+deb10u1) buster; urgency=medium . * QA upload. * Use C99 fixed-size integer types to fix runtime assertion on 64bit architectures other than amd64 and alpha. (Closes: #956927) * Stop linking to the dead Homepage. Checksums-Sha1: 7af5ece544e8f7c9b55823ab52037b5cbf50b58a 1716 wav2cdr_2.3.4-2+deb10u1.dsc 79596e42f7831c6408db75c6ac92b90765b5442c 10608 wav2cdr_2.3.4-2+deb10u1.debian.tar.xz Checksums-Sha256: a1386c934afd54947296d25d6a10d9829dfb86b934e524d19d4b472e2ef97446 1716 wav2cdr_2.3.4-2+deb10u1.dsc dcfd6fd4b270e15a8df49aa83b8623b02668b9b602a9da67f4a6d88e36e06e8f 10608 wav2cdr_2.3.4-2+deb10u1.debian.tar.xz Files: 3ad4b96aab5b0b9578f5db5bdbf3563d 1716 sound optional wav2cdr_2.3.4-2+deb10u1.dsc 374a0c4fa5973968ddf84c3edc7b1ce1 10608 sound optional wav2cdr_2.3.4-2+deb10u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8CNbUACgkQiNJCh6LY mLFetg/8CWaBqU6z+TcEykJbr2jgyRr5MvNM9Ejw7Jdcri4jDoGpN4XNeCy8bnmG DOUZ+MWgpg48efDHFuDWo1n57HlACFgfl3gmdhAogGt4Ez8HrxcMFswQVKxwmvET uoLbyhFZQcZrwhr67t283lNJWggZMDbQEIufY2ofzB1a4glcxpvec1ogx0BtyZ9A U7hoPXUdOPxNKV3pOaohLOgC866txmljXmWIaTGkdr/Is1j+Q4V9OBIbqPdtLH32 4ZY7OKhx+CocM1oQ9yMOVHqjLrb9LjetDxqQW7/D4bQnNpKj2m1vflGAook9Y/Ky a9ZXy/bUPF+EnG/85MGNtefkTxbiE1kxYglQyM4F4XvqYElMfOjTBFT5zTMgu3yc EH4D9qwSxkSzbKhNUv+dgGBTvzSZHV7jnnrb2rJaIVbA4ey384VA/o/ENh69Syag vqG/sr75VFyzpQJehJXrT1liTtPLHh8VgmQ3Tyi3nOz4MGJvja1RYx7cUOvOlzjf BAlxcix4W0UkM98AWwaz0v4gzYDZT3VbAw1zHOuf3wPlpyoGeX9r84v4BP4Or9nQ scEcEF+mAcKlwFACw8WotYcTx6FjqzQr5eJGBKbDygQFypnR1wb0eUspFM/l68Jv Vj/4pN6CTYKsemgE5dtPiyjrLzOUkg95O4WYCLIdHBmaJuoZvuI= =MJWC -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of storebackup_3.2.1-2~deb10u1_source.changes
storebackup_3.2.1-2~deb10u1_source.changes uploaded successfully to localhost along with the files: storebackup_3.2.1-2~deb10u1.dsc storebackup_3.2.1-2~deb10u1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processing of storebackup_3.2.1-2~deb9u1_source.changes
storebackup_3.2.1-2~deb9u1_source.changes uploaded successfully to localhost along with the files: storebackup_3.2.1-2~deb9u1.dsc storebackup_3.2.1-2~deb9u1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
storebackup_3.2.1-2~deb9u1_source.changes ACCEPTED into oldstable-proposed-updates->oldstable-new
Mapping stretch to oldstable. Mapping oldstable to oldstable-proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 Jul 2020 14:54:23 +0300 Source: storebackup Binary: storebackup Architecture: source Version: 3.2.1-2~deb9u1 Distribution: stretch Urgency: medium Maintainer: Debian QA Group Changed-By: Adrian Bunk Description: storebackup - fancy compressing managing checksumming deduplicating hard-linkin Closes: 949393 Changes: storebackup (3.2.1-2~deb9u1) stretch; urgency=medium . * QA upload. * Rebuild for stretch. . storebackup (3.2.1-2) unstable; urgency=medium . * QA upload. * Set maintainer to Debian QA Group. (see #856299) * Add patch to change the way the lockfile is opened in the Perl code. (Fixes: CVE-2020-7040) (Closes: #949393) Checksums-Sha1: dae8a3ec72893cb4de688e0063276c8dda51cfb3 1912 storebackup_3.2.1-2~deb9u1.dsc f2ec33d5ef6d5ff57d3591e3c6f425dd23ce8ec9 8924 storebackup_3.2.1-2~deb9u1.debian.tar.xz Checksums-Sha256: bd959ebab6f454fcd9ee0ea8d9dbe71f6fadcadee700334456c13f8bc6b2d5b5 1912 storebackup_3.2.1-2~deb9u1.dsc c9a98527d0c1fbb2cdc95c39df297420ae00a3b10670ab83032bb86475260f9c 8924 storebackup_3.2.1-2~deb9u1.debian.tar.xz Files: 068a7551d3a2bccfd0b9933b4349c476 1912 utils optional storebackup_3.2.1-2~deb9u1.dsc 4c1d579c6f40f320c8e48e40f21cca81 8924 utils optional storebackup_3.2.1-2~deb9u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8HBlgACgkQiNJCh6LY mLHjbw//Z0OwqqXWC+YtAsOQj+sTCRZkbPx7BMo8jKytO83T25MKSy0J/5kTnDDa 2wyUxKiLZyTIkhkZugcqTnDeuDG/MLBL2JtoSJuWIfLHZi4mfgTkUegVfVBuauXR nAGnWokOPJY4NcaLaxgRGuRcWvFQEXJ4+erXzv5xuTAfVBfGUuCQntO1FIacrYp7 MVSwKny/J3hy7oskGLHpINZSGgsZZ5lI7cEPNaXnvKYdDnU9i4/8h0DY0gLAy3Jn /OXm6v4p9BipcfCwPDlmwhsoVQiO3QGRsBx1dar5LancsagxxC57tsVbnCftyOdl 7wAO7YV3OIukurYWHazT84OHgtrrfsjquGxFwLit2R2vk009OS3G5qlwCXhgwhDi RDoo50P/0sOC0kAxbonWQyo91hTaWCDEwwZ7mE5b+uUkYoiDxSKi7LC9pO+UCb39 ew/vPdNNIe/bNJ5DK/0QBXfFBC8M2uEc3PPjsOR8ATyUixk9BM7DRTBeRMeUW9uh SI7FYBntkIt0wYA6UBOZsL6Tnk1DZO2MvPWaIVsuTluaQ36JkMDjEv25h9rQI1Kh Dr5/z5dPE6hsRSl01dJdH0oQ9OXuEW/S8gMiB4M+aN7qPt44uS0mHjpDnwF7osN5 BPZiCcKmo7MIscYk41jPAgmWJBAOvxo8BB1pGWMpv4f0p3esapY= =l9/x -END PGP SIGNATURE- Thank you for your contribution to Debian.
storebackup_3.2.1-2~deb10u1_source.changes ACCEPTED into proposed-updates->stable-new
Mapping buster to stable. Mapping stable to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 Jul 2020 14:59:51 +0300 Source: storebackup Architecture: source Version: 3.2.1-2~deb10u1 Distribution: buster Urgency: medium Maintainer: Debian QA Group Changed-By: Adrian Bunk Closes: 949393 Changes: storebackup (3.2.1-2~deb10u1) buster; urgency=medium . * QA upload. * Rebuild for buster. . storebackup (3.2.1-2) unstable; urgency=medium . * QA upload. * Set maintainer to Debian QA Group. (see #856299) * Add patch to change the way the lockfile is opened in the Perl code. (Fixes: CVE-2020-7040) (Closes: #949393) Checksums-Sha1: df336890c1d9d6e90c58fc9a39ba2a682956bbdc 1916 storebackup_3.2.1-2~deb10u1.dsc faf60740a718a2ad339978e01b015bc9ca350659 8920 storebackup_3.2.1-2~deb10u1.debian.tar.xz Checksums-Sha256: a156fbed669820fd705074b8730cbf1090eb4d21c05a6976b460296eec9462e6 1916 storebackup_3.2.1-2~deb10u1.dsc 45691f54126d53aca02338453a761c2dfbe22c21bf642c6e217f74ff530af339 8920 storebackup_3.2.1-2~deb10u1.debian.tar.xz Files: afdc74a765f782581dbf156880abea0e 1916 utils optional storebackup_3.2.1-2~deb10u1.dsc 7c5a6d4b803350bca130dc898eea4571 8920 utils optional storebackup_3.2.1-2~deb10u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8HCj0ACgkQiNJCh6LY mLF29A//air5pKkMUsXQ7+Sc6qErPc/5i8fNTxZbJkYFFcOid103+xBt6gaSw/4j cSQqJqlgN1gdgKHzbSwpBckp4F/5z5e2ejiEh2Jdk7pg2kpUR9tZHz41kaAlBOBq SvXL9JowEzN1y1R4LftN3QAD8+xb9Fyht6JLRvz6rFY5m7QLaqyM6vB2WvqP2pO2 EsVp2wuw+IUveTNxTvRk6FjwwAGobDFZmMGbWTLQS3OzxG8cFwqUh10WvGXsppC0 DebrEvUwyQs/60KvwKFjIT4nJRyQHVTqAB2vtq1F0ofS16Icq9pjVOxGO2meTGZH y5351dbLf9jKxknB3qNDoGxURy8SC4pIMTKZQsLiWZq87vvoM/Q577X9CvF3jgaI gKcCC/lVbgRVVRw/CWbkoOxkJnBH/h9a0pS+JkVDR9vHKHPIG5Atu4CV71CiD+Mr gogjwZnVubMgNdE/sYinydLUjUR9OtIXU3xsjCXNyJbmWiJ6am46BcOB0R1ZUMiW ZmvvLkKOYjIhsMBCSNkQLmMmxGbp3b46Kh2oANCVFo2loOvhh/H2vbxifF45pFPD 5fkonOJJfGfWO4e8Ig5vlao2AKZAsQMiQdUULLrKY6hBhsaPPN3DW3fucKCrGjPS 6zhmkbRT/DnkBcMVS4TYid9X4vm0hgaeQU+waA5rowbwhDjhg64= =gB2y -END PGP SIGNATURE- Thank you for your contribution to Debian.
mercurial switch to python3 in debian unstable - July 16th, 2020
Hello, this email is to inform the maintainers of the reverse dependencies of mercurial of the plan to upload to unstable the python3 version next Thursday. We want to be extra-safe with the switch, hence this email. In To: to this email the maintainers mailing list + key other MLs and addresses, in Bcc: the real people listed in Maintainer/Uploaders of the involved packages, apologies if you received more than 1 copy of it. The full list of the packages, as produced by dak, is available at the bottom of this email. There has been a test rebuilt, via ratt, as part of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937009#142 and it doesnt look like there's any failure in the build process due to the switch (except for meson, which indirectly build-depends on python2 without listing it). Mercurial is also used as part of the normal operation of a program, and that cannot be tested automatically, nor via a rebuild. The python3 version of mercurial is available in experimental (5.4.1-1+exp1); if you could test it against your package to make sure it works as you intended, that would help the transition. Mercurial has an extensive test suite, which passes 100% with python3, so we dont expect any failure while using the `mercurial` command, but some interfaces/operations may have changed. If we dont hear otherwise, we plan to upload the python3 version of mercurial in unstable on or around next Thursday, July 16th. This effort will greatly benefit the broader effort of py2removal, by allowing the chain removal of several other packages. Regards, Sandro $ dak rm -Rn mercurial Will remove the following packages from unstable: mercurial |5.4.1-1 | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x mercurial-common |5.4.1-1 | all Maintainer: Python Applications Packaging Team --- Reason --- -- Checking reverse dependencies... # Broken Depends: git-remote-hg: git-remote-hg hg-git: mercurial-git hgsubversion: hgsubversion mercurial-buildpackage: mercurial-buildpackage mercurial-crecord: mercurial-crecord mercurial-extension-utils: mercurial-extension-utils mercurial-keyring: mercurial-keyring python-hgapi: python3-hgapi python-hglib: python3-hglib sphinx-patchqueue: python-sphinx-patchqueue # Broken Build-Depends: check-manifest: mercurial composer: mercurial devpi-common: mercurial git-remote-hg: mercurial golang-github-masterminds-vcs-dev: mercurial haskell-filestore: mercurial hg-git: mercurial (>= 4.8~) hgsubversion: mercurial (>= 5.2-1~) jags: mercurial meson: mercurial pepper: mercurial python-hgapi: mercurial python-hglib: mercurial (>= 1.9) reposurgeon: mercurial ros-rosinstall: mercurial ros-vcstools: mercurial ros-wstool: mercurial setuptools-scm: mercurial Dependency problem found.
pev is marked for autoremoval from testing
pev 0.80-5 is marked for autoremoval from testing on 2020-07-15 It is affected by these RC bugs: 960880: pev: autopkgtest failure: pehash did not report ASLR status
