Thank YouAny ideas what the problem is with the above error? As far as I can figure out sbuild-build-depends-core-that debfoster does not exist under "testing". BTW why does debfoster fail to exist under testing?I am not sure if this error is because of the way I deleted the old chroot. Before I was getting a different error complainingI always get the following error:I have then tried to build 2 different packages, on the different chroots.For testing, and for unstable.Ok, I deleted my old sbuild chroot for debian testing.I then created two sbuild chroot according to the wiki instructions.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
+----------------------------------------------------------- -------------------+
| Cleanupdummy does not even exist.
--
Paul Elliott1(512)837-1096
pelliott@BlackPatchPanel.com3300 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 <pelliott@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
pelliott@BlackPatchPanel.com 3300 Plaza Drive, apt 1
http://www.free.blackpatchpanel.com/pme/ New Albany, IN 47150