[buildd-tools-devel] Bug#870102: Bug#870102: automatically update schroots

Antoine Beaupré anarcat at debian.org
Sun Jul 30 14:05:08 UTC 2017


On 2017-07-30 08:31:08, Johannes Schauer wrote:
> Quoting Antoine Beaupre (2017-07-29 22:15:29)
>> It would be nice if sbuild automatically updated the configured
>> schroots. As things stand now, a configured schroot will slowly rot
>> down to a point where new builds will have to download a bunch of base
>> packages at each run, if sbuild is configured to automatically update
>> the schroot at build time. And if it's not, the resulting build will
>> be based on bit-rotten code as well.
>> 
>> I have used the following simple script in /etc/cron.weekly/sbuild:
>> 
>> #!/bin/sh -e
>> 
>> cd /etc/sbuild/chroot/
>> for chroot in *; do
>>     sbuild-update --update --upgrade --clean --autoclean --autoremove $chroot >/dev/null
>> done
>> 
>> I don't like it so much: "> /dev/null" is a crude hack, and it should
>> be possible to silence apt more carefully. But it works and is good
>> enough for my purpose.
>> 
>> Could that be considered upstream?
>
> Do you not find the script in /usr/share/doc/sbuild/examples/sbuild-update-all
> sufficient?

s/sufficient// :) I didn't notice that one at all.

How about hooking it straight into cron in some way, or documenting it
somewhere?

Maybe all I need to do is to hook that in the sbuild wiki page?

a.

-- 
If it's important for you, you'll find a way.
If it's not, you'll find an excuse.
                        - Unknown



More information about the Buildd-tools-devel mailing list