[Pkg-systemd-maintainers] [Piuparts-devel] Need help with a particular piuparts run

Andreas Beckmann anbe at debian.org
Tue Jul 9 06:19:32 BST 2013


On 2013-07-04 08:12, Michael Stapelberg wrote:
> Hi Andreas,
> 
> Michael Stapelberg <stapelberg at debian.org> writes:
>>> I'd prefer to avoid pulling in perl by default into the minimal chroot
>>> as that makes it harder to detect packages that depend on perl-base, but
>>> actually need perl. Weird (heisen)bugs showing only in rare corner cases
>>> (postgresql-common recently).
>> I see. Given the circumstances, would you be willing to make
>> init-system-helpers pseudo-essential even though it pulls in perl?
> Friendly ping.

I tried it in my local instance ... seems to work, but now I get

0m22.5s ERROR: FAIL: Package purging left files on system:
  /etc/systemd/	 not owned
  /etc/systemd/system/	 not owned
  /etc/systemd/system/multi-user.target.wants/	 not owned
  /var/lib/systemd/deb-systemd-helper-enabled/	 not owned
  /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/	 not owned

Please ship these directories in a package (or more packages, as appropriate)
s.t. dpkg takes care of creation and removal. Manual rmdir is probably not
a good idea.


Andreas

PS: the corresponding piuparts bug template:

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:

http://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...):



cheers,




More information about the Pkg-systemd-maintainers mailing list