[buildd-tools-devel] Bug#727011: Bug#727011: sbuild insists on doing apt-get update

[Roger Leigh]

On Mon, Oct 21, 2013 at 03:10:58PM +0100, Ian Jackson wrote:
> Package: sbuild
> Version: 0.63.2-1.1
> 
> I'm trying to get sbuild to work without it insisting on an apt-get
> update and upgrade.  Encouraged by the manpage, I have tried to do
> this by editing sbuild.conf, and also tried .sbuildrc.
> 
> But it still does apt-get update.

I'll have to check in more detail, but I think that this is an
artifact of using the apt or aptitude resolver: after creating the
temporary archive with apt-ftparchive, we need to update apt.  By
default this does not (or at least should not) perform a full update.
If you set APT_UPDATE_ARCHIVE_ONLY ($apt_update_archive_only = 0)
then it should do a full update.

It may be the case that this setting is not being respected or the
logic is inverted.

Please could you retry with and without this setting enabled?  It
would be great to have debug logs for both cases as you provided here.

Note that with the removal of the "internal" resolver, we do need to
update at least the local archives on every sbuild run, so the older
$apt_update option is not as useful.  It's still used for a full
update, but the above partial update is independent of that setting,
and this is what's doing the full update in your case.  See
update_archive() in lib/Sbuild/ResolverBase.pm (vs plain update()
in the same file).


Thanks,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20131021/2da6f284/attachment.sig>