[buildd-tools-devel] Bug#859866: Bug#859866: sbuild transiently fails stating apt-get update failed

[Johannes Schauer]

Hi,

Quoting Michael Stapelberg (2017-04-11 12:41:03)
> On Tue, Apr 11, 2017 at 10:43 AM, Johannes Schauer <josch at debian.org> wrote:
> > Quoting Michael Stapelberg (2017-04-08 11:21:46)
> > > I may very well be doing something wrong, but I repeatedly run into
> > > the following problem and have no clue as to how to approach fixing
> > > it.
> > >
> > > Every once in a while, an sbuild invocation will fail with the
> > > following message:
> > >
> > >     Reading package lists...
> > >     E: Could not open file /var/lib/apt/lists/deb.debian.
> > org_debian_dists_sid_main_source_Sources.diff_Index - open (2: No such
> > file or directory)
> > >     E: apt-get update failed
> > >
> > > I can fix this issue by running “sbuild-update -u unstable” twice
> > > (!). The first run fails with the same error message (but stores the
> > > updated package lists), the second run will do the actual update.
> > >
> > > Is this a misconfiguration on my end, or a bug in sbuild/schroot/apt?
> > >
> > > Find a full session transcript attached.
> >
> > I never encountered this error message. Neither from running sbuild nor
> > from
> > running apt-get update.
> >
> > Maybe apt people have a clue about what this means? I CC-ed their list.
> >
> > Michael, is it possible for you to create a chroot from scratch using
> > sbuild-createchroot and then reliably reproduce the problem from there?
> > Then I
> > could have a look at the problem myself.
> >
> 
> I’d be happy to wipe my sbuild setup and start from scratch. Which commands
> specifically do you recommend I use?

If you start completely from scratch, setting up sbuild with a schroot backend
works like this (since Debian Stretch):

$ sudo apt-get install sbuild
$ sudo sbuild-adduser $LOGNAME
$ ... *logout* and *re-login* or use `newgrp sbuild` in your current shell
$ sudo sbuild-createchroot unstable /srv/chroot/unstable-amd64-sbuild http://httpredir.debian.org/debian

So nearly what it currently says on the sbuild wiki page but minus several
workarounds that are not needed anymore since Stretch. These instructions can
also be taken from the sbuild man page (the EXAMPLES section) which also links
to the sbuild-createchroot man page with more examples in the respective
section.

But you will probably not completely start from scratch because you probably
populated /var/lib/sbuild/apt-keys for example but that shouldn't influence the
effect you see. Also make sure that you are using the default config either by
moving your ~/.sbuildrc or by passing a custom configuration via the
SBUILD_CONFIG environment variable.

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/20170411/1759445b/attachment.sig>