Your message dated Sun, 04 Sep 2016 22:30:32 +0000
with message-id <[email protected]>
and subject line Bug#810701: fixed in debci 1.4
has caused the Debian Bug report #810701,
regarding debci: unowned directory after purge: /var/log/debci/
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.)
--
810701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810701
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debci
Version: 1.0.1
Severity: important
User: [email protected]
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned
directories on the system after purge, which is a violation of
policy 6.8:
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails
Filing this as important as having a piuparts clean archive is a release
goal since lenny.
The maintainer scripts create (and later remove) a file in that
directory. Manual directory removal may be not appropriate as this
directory is shared between several packages.
If the package would ship this as an empty directory, dpkg would take
care of the creation and removal (if it's empty).
>From the attached log (scroll to the bottom...):
0m59.3s ERROR: FAIL: Package purging left files on system:
/var/log/debci/ not owned
cheers,
Andreas
debci_1.0.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: debci
Source-Version: 1.4
We believe that the bug you reported is fixed in the latest version of
debci, 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.
Antonio Terceiro <[email protected]> (supplier of updated debci 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: SHA256
Format: 1.8
Date: Sun, 04 Sep 2016 18:27:51 -0300
Source: debci
Binary: debci debci-worker debci-collector
Architecture: source
Version: 1.4
Distribution: unstable
Urgency: medium
Maintainer: Antonio Terceiro <[email protected]>
Changed-By: Antonio Terceiro <[email protected]>
Description:
debci - continuous integration system for Debian
debci-collector - continuous integration system for Debian (collector daemon)
debci-worker - continuous integration system for Debian (worker daemon)
Closes: 810701
Changes:
debci (1.4) unstable; urgency=medium
.
[ Antonio Terceiro ]
* bin/debci-migrate.d/002_compress_artifacts: also remove directories after
compressing artifacts
* Web UI:
- include version numbers almost everywhere.
* lib/debci/html/package.erb: avoid crashing when installing a fresh system
with no data, but with packages already blacklisted.
* debian/debci.postrm: remove /var/log/debci on purge (Closes: #810701)
* Add support for running tests for multiple suites (See: #831975).
.
Not that we couldn't do that already, but it would require specific
workers for each suite. With these changes, a worker node for a given
architecture can now run tests on any suite for that architecture.
.
- debci-worker will now expect the suite name as a second argument on test
jobs (defaulting to whatever is in $debci_suite).
- debci-enqueue will now send the suite name as a second argument on each
test job
- Added debci-update-worker as a wrapper for callling debci-setup for each
supported suite.
* backends/lxc:
- retry `apt-get update` until it works. Most of the time when the testbed
setup fails on production is during `apt-get update`.
* "Platform-Specific issues" will now not consider tmpfail as an issue.
Those are already being tracked by "Status alerts".
* test/test_shell_best_practices.sh: start checking scripts with shellcheck;
not failing on issues just yet.
.
[ Gordon Ball ]
* Add the concept of failure states, to distinguish between
* tests which have never passed
* tests which passed for a previous version, but never for the current
version
* tests which previously passed for the current version
Checksums-Sha1:
4bbfb6835c8d21c9fad402f54dbc30aeb1986b61 2044 debci_1.4.dsc
f9bf8533b4a4fbe82bf8c7de9791da63f3a6a2b5 69500 debci_1.4.tar.xz
Checksums-Sha256:
4d51fc223857bc339aea642311d2b09debbb6ba9fe827cc1cbcb553b166bb27a 2044
debci_1.4.dsc
cff217cdfafa7f3c599e6edcd97795b26db6b0269062897f6e168c34e5ea8d53 69500
debci_1.4.tar.xz
Files:
ef13062e008ddfb0bc63949edd9dc499 2044 devel optional debci_1.4.dsc
4811533d1eac254d2640b0abdd51ce4a 69500 devel optional debci_1.4.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCAAGBQJXzJXqAAoJEPwNsbvNRgvepHgQANV5KmdFkY3v/XrgjpEdToKJ
0OPapKvVEPrGOsmnjlnPgLlBsHtabelsewnB8RYaZm4ijoiwnDHBpIgvaYYT27M9
/aF/xMWs6Dz0XiAtFhnHsgC+pjfYn5K3VKj+Qfur3DPXt4BWXQLfW8Rv+EMv5I91
QtiGAoIF3HjN2Ux9m5qmXPHF52TavQBcuKwXBbPh94QQZ0km8Z8ZFICxmStukqox
wnyBKRN2ctS0ZzRcZ4j+0y61Q38aMFz0u2LKclb+LOs3jbM4nFCK4JnMDwEv71Zr
OnnGnBTIT3ywsysqI3pVZOphVEht2SGqVtMgbjTdNd8j/PMUEHcBeHUl7KJ/1gVp
T9jrwMH0UKIG2aPxRxKidpynGRCPNp7wNnP+nyXFnGia8aTXqeI3h2maKm7v4Aht
GqF5Z4d7Y2L3XeK6GQo2Pf4ZyDth1LHfcFxo9eqVM4FMJzXS0qcFxH+c+IfRB6JL
h3UV+GCVG7+wd6CaU/z+QFmvPd8v6KVqBiV2m8+LzzlxGuggPwUH2aft8OemQbhE
2l9rw6PlX0JPo5bY7fCWuZDSGR59MtIAA7Aq9EeDC1qdutFwNrv7hYa7fso1glC4
n6jgOwPBXdjUZwz3wfwu/4+JA53Ho/v/p9tl5hCdW4DtBqaKRX6lO1BMdy/i6PXx
zU/PCeVi8ejh8vfAo/5c
=j0kP
-----END PGP SIGNATURE-----
--- End Message ---
