Your message dated Wed, 20 May 2020 21:15:10 +0200
with message-id <[email protected]>
and subject line Re: bacula: autopkgtest regressed in buster
has caused the Debian Bug report #923444,
regarding bacula: autopkgtest regressed in buster
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.)
--
923444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923444
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: bacula
Version: 9.4.2-1
Severity: important
User: [email protected]
Usertags: regression
[X-Debbugs-CC: [email protected], [email protected],
[email protected]]
Dear bacula maintainers,
Somewhere on 2019-02-26 your package bacula started to fail its
autopkgtest in testing/buster (it started failing in unstable somewhere
between 23 and 25 February). Because this regression wasn't caught by
the migration software, I can only assume that one of your indirect
dependencies, I heavily suspect dpkg causes the regression. (dpkg was
aged to 2 days, hence the regression in testing showed up only 2 days
after it showed up in buster).
I copied the error below. I have also diffed the installed packages
during the test between the first one failing and the last one
succeeding (items marked with * are NOT present in the diff between the
last overall successful run and the first overall failing run:
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bacula/2021354/log.gz
and
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bacula/2021354/artifacts.tar.gz
- dpkg 1.19.2
- dpkg-dev 1.19.2
+ dpkg 1.19.5
+ dpkg-dev 1.19.5
- findutils * 4.6.0+git+20190105-2
+ findutils * 4.6.0+git+20190209-2
- libacl1 * 2.2.52-3+b1
+ libacl1 * 2.2.52-5
- libattr1 * 1:2.4.47-2+b2
+ libattr1 * 1:2.4.47-4
- libdpkg-perl 1.19.2
+ libdpkg-perl 1.19.5
- libelf1 * 0.175-2
+ libelf1 * 0.176-1
- libp11-kit0 * 0.23.14-2
+ libp11-kit0 * 0.23.15-2
Don't hesitate to raise the severity further if this is RC for your package.
Paul
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bacula/2021354/log.gz
autopkgtest [20:46:39]: test backup-test: [-----------------------
+ echo 'start testing ... '
start testing ...
+ echo 'USER: root'
USER: root
+ echo '--------- configuring Bacula daemons -----------'
--------- configuring Bacula daemons -----------
+
FILECHGRDIR=/tmp/autopkgtest-lxc.xp_s9uxq/downtmp/autopkgtest_tmp/bacula-sd/filechgr
+
RESTOREDIR=/tmp/autopkgtest-lxc.xp_s9uxq/downtmp/autopkgtest_tmp/bacula-restores
+ mkdir -p
/tmp/autopkgtest-lxc.xp_s9uxq/downtmp/autopkgtest_tmp/bacula-sd/filechgr
+ chown -R bacula:tape
/tmp/autopkgtest-lxc.xp_s9uxq/downtmp/autopkgtest_tmp/bacula-sd/filechgr
+ sed -i
s%/nonexistant/path/to/file/archive/dir%/tmp/autopkgtest-lxc.xp_s9uxq/downtmp/autopkgtest_tmp/bacula-sd/filechgr%
/etc/bacula/bacula-sd.conf
+ sed -i 's%Where =
/nonexistant/path/to/file/archive/dir/bacula-restores%Where =
/tmp/autopkgtest-lxc.xp_s9uxq/downtmp/autopkgtest_tmp/bacula-restores%'
/etc/bacula/bacula-dir.conf
+ sed -i 's/signature = MD5/signature = SHA1/' /etc/bacula/bacula-dir.conf
+ sed -i 's/signature = MD5/signature = SHA1\naclsupport = yes/'
/etc/bacula/bacula-dir.conf
+ echo '--------- restarting services ----------- '
--------- restarting services -----------
+ service bacula-director restart
Job for bacula-director.service failed because the control process
exited with error code.
See "systemctl status bacula-director.service" and "journalctl -xe" for
details.
autopkgtest [20:47:09]: test backup-test: -----------------------]
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 9.6.3-1
Hi,
On 28-02-2019 11:12, Paul Gevers wrote:
> Somewhere on 2019-02-26 your package bacula started to fail its
> autopkgtest in testing/buster (it started failing in unstable somewhere
> between 23 and 25 February). Because this regression wasn't caught by
> the migration software, I can only assume that one of your indirect
> dependencies, I heavily suspect dpkg causes the regression. (dpkg was
> aged to 2 days, hence the regression in testing showed up only 2 days
> after it showed up in buster).
This bug got fixed in the latest version. It's good, as it caught
something in ufc today, but this bug can be closed.
Paul
signature.asc
Description: OpenPGP digital signature
--- End Message ---
