Seems like this is the result of your commit https://salsa.debian.org/debian/sbuild/commit/eed23f5b70449b60f91764e3ab23196d8ec76dff :)
I don’t have the time to do any fixes at the moment, sorry. On Tue, Feb 12, 2019 at 7:51 PM Johannes Schauer <jo...@debian.org> wrote: > Hi Michael, > > could you look into this bug? > > Thanks! > > Quoting Antoine Beaupre (2019-02-12 18:11:45) > > Package: sbuild > > Version: 0.78.1-1 > > Severity: minor > > File: > /usr/share/doc/sbuild/examples/sbuild-debian-developer-setup-update-all > > > > It looks like that file was renamed in a recent upload, which broke my > > wrapper scripts. That's not too bad: it's an example script so that > > may be expected (even though I would prefer if that script would be > > publicly available in sbin or something). > > > > The problem though is that the script itself documents how to add > > itself to cron jobs, like this: > > > > # 1. Update all sbuild chroots four times a day (at > 00:15/06:15/12:15/18:15): > > # > > # 15 */6 * * * root /usr/share/doc/sbuild/examples/sbuild-update-all > > > > That path doesn't exist anymore, as the script was renamed.. It would > > be nice to complete the process and fix the example code as well... > > > > Ideally, this should be handled automatically by the package, which > > could deploy a cronjob itself, which might be tweakable with (say) > > /etc/default/sbuild or something... > > > > A. > -- Best regards, Michael
