I've noticed for a long time (maybe years) that most of the packages in DDPO have Piuparts tests failing because of long-standing errors of other packages and then consequently also block many more dependent on them making difficult to find real problems related to the selected package.

Here's an example:

0m52.0s INFO: Warning: Package purging left files on system:
  /etc/X11/Xsession.d/     owned by: dbus-user-session
  /etc/default/locale -> ../locale.conf     not owned
  /etc/vconsole.conf -> default/keyboard     not owned
  /root/.ssh/     not owned
  /var/cache/private/     not owned
  /var/lib/private/     not owned
  /var/lib/systemd/coredump/     not owned
  /var/lib/systemd/ephemeral-trees/     not owned
  /var/lib/systemd/network/     not owned
  /var/lib/systemd/pstore/     not owned
  /var/log/private/     not owned

0m52.0s ERROR: FAIL: After purging files have disappeared:
  /etc/systemd/system/multi-user.target.wants/     not owned
  /etc/systemd/system/multi-user.target.wants/e2scrub_reap.service -> /lib/systemd/system/e2scrub_reap.service     not owned

0m52.0s ERROR: FAIL: After purging files have been modified:
  /etc/systemd/system/timers.target.wants/dpkg-db-backup.timer -> /lib/systemd/system/dpkg-db-backup.timer     not owned

(taken from https://piuparts.debian.org/stable2sid/fail/xapps-common_2.8.5-1.log)


Has anyone else noticed this?

Is there a way to avoid this and finally be able to use piuparts.debian.org to find any rare issues that escape Salsa CI and manual tests?

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to