[buildd-tools-devel] Bug#893577: sbuild-debian-developer-setup: Should not rely on files in /usr/share/doc

[Johannes Schauer]

Hi all,

> At the end of the script, it runs
> 
>     symlink("/usr/share/doc/sbuild/examples/sbuild-update-all", "/etc/cron.daily/sbuild-debian-developer-setup-update-all");
> 
> which requires the file in /usr/share/doc to be present. Policy 12.3 says that
> packages can't do that and says that such files should be in
> /usr/share/package with a symlink into /usr/share/doc/package/ as
> appropriate.

probably the right thing to do would be to let the
sbuild-debian-developer-setup package directly install sbuild-update-all into
/etc/cron.daily/sbuild-debian-developer-setup-update-all. If necessary,
sbuild-update-all has to be adapted such that it will not barf if the user has
not yet run sbuild-debian-developer-setup.

This would mean that the same copy of sbuild-update-all would potentially exist
twice on a system, but I don't think that's much of a problem.

Michael, can you take care of this?

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20180327/21323da5/attachment.sig>