OK this time I deleted the recommended files as before, but I noted there were no other chroots in use. So I purged both sbuild and schroot with apt-get and reinstalled.
I then recreated th chroot using steps 1-6 of "Create the chroot" from the wiki page. I get the same error! Setup apt archive ----------------- Merged Build-Depends: build-essential, fakeroot Filtered Build-Depends: build-essential, fakeroot dpkg-deb: building package 'sbuild-build-depends-core-dummy' in '/<<BUILDDIR>>/resolver-aIr7Ri/apt_archive/sbuild-build-depends-core-dummy.deb'. dpkg-deb: error: failed to make temporary file (control member): No such file or directory Dummy package creation failed E: Setting up apt archive failed +------------------------------------------------------------------------------+ | Cleanup Some how some bad data is being stored in some unknown place. Is there any way to figure out what directory does not exist? (control member) Thank You On Fri, Aug 5, 2016 at 2:42 AM, Paul Elliott <pelli...@blackpatchpanel.com> wrote: > Ok, I deleted my old sbuild chroot for debian testing. > > I then created two sbuild chroot according to the wiki instructions. > > For testing, and for unstable. > > I have then tried to build 2 different packages, on the different chroots. > > > I always get the following error: > Setup apt archive > ----------------- > > Merged Build-Depends: build-essential, fakeroot > Filtered Build-Depends: build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-core-dummy' in > '/<<BUILDDIR>>/resolver-mAdLP4/apt_archive/sbuild- > build-depends-core-dummy.deb'. > dpkg-deb: error: failed to make temporary file (control member): No such > file or directory > Dummy package creation failed > E: Setting up apt archive failed > +----------------------------------------------------------- > -------------------+ > | Cleanup > > I am not sure if this error is because of the way I deleted the old > chroot. Before I was getting a different error complaining > that debfoster does not exist under "testing". BTW why does debfoster fail > to exist under testing? > > Any ideas what the problem is with the above error? As far as I can figure > out sbuild-build-depends-core-dummy does not even exist. > > > Thank You > -- > Paul Elliott 1(512)837-1096 > pelli...@blackpatchpanel.com 3300 Plaza Drive, apt 1 > http://www.free.blackpatchpanel.com/pme/ New Albany, IN 47150 > > > On Tue, Aug 2, 2016 at 11:06 PM, Paul Elliott < > pelli...@blackpatchpanel.com> wrote: > >> >> >> Sometimes a user gets a sbuild chroot so screwed up that it does not >> work anymore, and the user has no idea how to fix it, because he does not >> know what he did wrong. >> >> He wants to start over from scratch. >> >> The problem is, it is not documented the correct way to delete >> the chroot and tar ball. The users want to put sbuild back to >> the way it was just after sbuild was installed. >> >> >> What is the proper way to do that? >> >> Thank You for your answers. >> >> >> -- >> Paul Elliott 1(512)837-1096 >> pelli...@blackpatchpanel.com 3300 Plaza Drive, apt 1 >> http://www.free.blackpatchpanel.com/pme/ New Albany, IN 47150 >> > >
