Re: How do you delete a sbuild an sbuild chroot and start over?

[Johannes Schauer]

Hi Paul,

Quoting Paul Elliott (2016-08-05 21:28:25)
> 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.

note that purging sbuild and schroot will not remove the chroots. But it will
get you a clean initual configuration.

> I then recreated th chroot using steps 1-6 of "Create the chroot" from the
> wiki page.

Which sbuild version are you using? Since fixing of bug #801798 (so since
sbuild version 0.67.0) steps 2 and 3 from that wiki page are not useful
anymore, unless you want to build packages for Debian squeeze.

Also, step 4 has only to be done once after you installed sbuild and not every
time you create a new chroot.

> 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
> '/<>/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)

Please file a bug report against sbuild. Even if the problem is on your side,
the above error message is very cryptic and not helpful at all. In your bug
report, please include the following:

 - which sbuild version are you using?
 - which Debian release are you using?
 - list precisely which commands you are executing

Thanks!

cheers, josch


signature.asc
Description: signature

Re: How do you delete a sbuild an sbuild chroot and start over?

[Adam Borowski]

On Fri, Aug 05, 2016 at 10:07:23PM +0200, Jakub Wilk wrote:
> * Wookey , 2016-08-05, 20:56:
> >I think there is a way to stop it putting i the <>
> >substitutions, but I can't find that now.
> 
> In /etc/sbuild/sbuild.conf set:
> $log_filter = 0;
> 
> (It's beyond me why this is enabled by default.)

It makes build logs significantly more readble, and in the rare case you
actually need that information, it's right there near the start.

-- 
An imaginary friend squared is a real enemy.

Re: How do you delete a sbuild an sbuild chroot and start over?

[Jakub Wilk]

* Jakub Wilk , 2016-08-05, 22:07:

* Wookey , 2016-08-05, 20:56:
I think there is a way to stop it putting i the <> 
substitutions, but I can't find that now.


In /etc/sbuild/sbuild.conf set:
$log_filter = 0;


You can also use this tool to (hopefully) reverse filtering:
https://github.com/jwilk/deb-toolbox/blob/master/unfudge-build-log

--
Jakub Wilk

Re: How do you delete a sbuild an sbuild chroot and start over?

[Jakub Wilk]

* Wookey , 2016-08-05, 20:56:
I think there is a way to stop it putting i the <> 
substitutions, but I can't find that now.


In /etc/sbuild/sbuild.conf set:
$log_filter = 0;


(It's beyond me why this is enabled by default.)

--
Jakub Wilk

Re: How do you delete a sbuild an sbuild chroot and start over?

[Wookey]

On 2016-08-05 14:28 -0500, Paul Elliott wrote:

> dpkg-deb: building package 'sbuild-build-depends-core-dummy' in 
> '/<>/
> 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

> Is there any way to figure out what directory does not exist? (control member)

<> tells you what it is at the top of the log: 
e.g.
I: NOTICE: Log filtering will replace 'build/most-Ru6goH/most-5.0.0a' with 
'«PKGBUILDDIR»'
I: NOTICE: Log filtering will replace 'build/most-Ru6goH' with '«BUILDDIR»'
I: NOTICE: Log filtering will replace 
'var/lib/schroot/mount/sid-arm64-sbuild-9ba727aa-c9d7-4d64-9d2a-679b6ad14a8e' 
with '«CHROOT»'

So you can find out what directory it is trying to use. I guess maybe
you have a permissions problem?
 

You may also find that --log-external-command-output and 
--log-external-command-error
will help. 

--debug will give you buckloads of output, which again may help clarify the 
issue.

I think there is a way to stop it putting i the <>
substitutions, but I can't find that now.



Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: Digital signature

Re: How do you delete a sbuild an sbuild chroot and start over?

[Paul Elliott]

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
'/<>/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 
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
> '/<>/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
>>
>
>

Re: How do you delete a sbuild an sbuild chroot and start over?

[Johannes Schauer]

Hi,

Quoting Andrey Rahmatullin (2016-08-05 09:49:11)
> On Fri, Aug 05, 2016 at 02:42:27AM -0500, Paul Elliott wrote:
> > Before I was getting a different error complaining
> > that debfoster does not exist under "testing". BTW why does debfoster fail
> > to exist under testing?
> Because it was removed from testing and the new version hasn't entered
> testing yet.

note, that version 0.70.0 of sbuild in unstable (also didn't migrate to testing
yet) doesn't add debfoster to the chroot by default anymore.

So your problem shouldn't exist anymore with the most recent sbuild release.

Thanks!

cheers, josch


signature.asc
Description: signature

Re: How do you delete a sbuild an sbuild chroot and start over?

[Andrey Rahmatullin]

On Fri, Aug 05, 2016 at 02:42:27AM -0500, Paul Elliott wrote:
> Before I was getting a different error complaining
> that debfoster does not exist under "testing". BTW why does debfoster fail
> to exist under testing?
Because it was removed from testing and the new version hasn't entered
testing yet.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: How do you delete a sbuild an sbuild chroot and start over?

[Paul Elliott]

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
'/<>/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 
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
>

Re: How do you delete a sbuild an sbuild chroot and start over?

[Sean Whitton]

Hello,

On Wed, Aug 03, 2016 at 10:21:46AM +0200, Jonas Meurer wrote:
> Please note that this will delete *all* chroots and their configuration.
> I woud prefer something like:

That's what he said he wanted to do :)

-- 
Sean Whitton


signature.asc
Description: PGP signature

Re: How do you delete a sbuild an sbuild chroot and start over?

[Wookey]

On 2016-08-03 13:12 +0200, Johannes Schauer wrote:
> Hi,
> 
> Quoting Paul Wise (2016-08-03 12:41:28)
> > > As far as I know, schroot still doesn't
> > > document how to delete a chroot.
> > 
> > Seems to me like sbuild should have an sbuild-deletechroot command
> > that should call the relevant tool for the chroot in question and
> > schroot should have a corresponding command that would DTRT.
> 
> it is unlikely, that there will be a schroot command that does the right thing
> because schroot also leaves it up to the user to create the chroot in the 
> first
> place. This is also why sbuild-createchroot is doing everything manually
> including assembling the right schroot configuration file.

schroot does have the info it needs though - to lok up where the chroot is 
stored and remove it, so it could...
 
> My last attempt at implementing a command that does this was stopped early on
> by the question how this tool should best be called:
> 
>  - sbuild-deletechroot
>  - sbuild-removechroot
>  - sbuild-destroychroot
> 
> Maybe a native English speaker could tell me the most natural choice for a 
> tool
> that does the opposite of what sbuild-createchroot does.

'destroy' is closest to the opposite of 'create'. But 'remove' sounds
a bit less cataclysmic :-) Either will do fine.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: Digital signature

Re: How do you delete a sbuild an sbuild chroot and start over?

[Johannes Schauer]

Hi,

Quoting Paul Wise (2016-08-03 12:41:28)
> On Wed, Aug 3, 2016 at 1:06 PM, Johannes Schauer wrote:
> 
> > The main issue here is, that it is not clear *where* the bug should be 
> > filed.
> > Sbuild supports multiple backends. The probably most used one is the schroot
> > backend because that is used by sbuild-createchroot and the default of the
> > CHROOT_MODE configuration variable.
> >
> > Indeed I do remember having had a similar question when I started using 
> > sbuild
> > but never got around filing a bug. As far as I know, schroot still doesn't
> > document how to delete a chroot.
> 
> Seems to me like sbuild should have an sbuild-deletechroot command
> that should call the relevant tool for the chroot in question and
> schroot should have a corresponding command that would DTRT.

it is unlikely, that there will be a schroot command that does the right thing
because schroot also leaves it up to the user to create the chroot in the first
place. This is also why sbuild-createchroot is doing everything manually
including assembling the right schroot configuration file.

My last attempt at implementing a command that does this was stopped early on
by the question how this tool should best be called:

 - sbuild-deletechroot
 - sbuild-removechroot
 - sbuild-destroychroot

Maybe a native English speaker could tell me the most natural choice for a tool
that does the opposite of what sbuild-createchroot does.

Thanks!

cheers, josch


signature.asc
Description: signature

Re: How do you delete a sbuild an sbuild chroot and start over?

[Paul Wise]

On Wed, Aug 3, 2016 at 1:06 PM, Johannes Schauer wrote:

> The main issue here is, that it is not clear *where* the bug should be filed.
> Sbuild supports multiple backends. The probably most used one is the schroot
> backend because that is used by sbuild-createchroot and the default of the
> CHROOT_MODE configuration variable.
>
> Indeed I do remember having had a similar question when I started using sbuild
> but never got around filing a bug. As far as I know, schroot still doesn't
> document how to delete a chroot.

Seems to me like sbuild should have an sbuild-deletechroot command
that should call the relevant tool for the chroot in question and
schroot should have a corresponding command that would DTRT.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Re: How do you delete a sbuild an sbuild chroot and start over?

[Jonas Meurer]

Am 03.08.2016 um 06:20 schrieb Sean Whitton:
> On Tue, Aug 02, 2016 at 11:06:31PM -0500, Paul Elliott 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?
> 
> Asking for a friend? ;)
> 
> Assuming you used the suggestions for making the chroot on the sbuild
> wiki page, this should do it:
> 
> # rm -rf /srv/chroot/* /etc/sbuild/chroot/*-sbuild 
> /etc/schroot/chroot.d/*-sbuild

Please note that this will delete *all* chroots and their configuration.
I woud prefer something like:

SCHROOT=unstable-amd64-sbuild
SCHROOT_DIR=$(readlink -e /etc/sbuild/${SCHROOT})
rm -r ${SCHROOT_DIR} /etc/sbuild/${SCHROOT} \
/etc/schroot/chroot.d/$[SCHROOT}-*

Afterwards you can start over by creating a fresh version of the schroot
with sbuild-createchroot as documented on the wiki page[1].

Cheers,
 jonas

[1] https://wiki.debian.org/sbuild

> If you didn't use the suggestions on the wiki page, just start nuking
> stuff in those three directories.
> 




signature.asc
Description: OpenPGP digital signature

Re: How do you delete a sbuild an sbuild chroot and start over?

[Johannes Schauer]

Hi Paul,

Quoting Sean Whitton (2016-08-03 06:20:26)
> On Tue, Aug 02, 2016 at 11:06:31PM -0500, Paul Elliott 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.

if it's not documented, you should file a bug about that. ;)

The main issue here is, that it is not clear *where* the bug should be filed.
Sbuild supports multiple backends. The probably most used one is the schroot
backend because that is used by sbuild-createchroot and the default of the
CHROOT_MODE configuration variable.

Indeed I do remember having had a similar question when I started using sbuild
but never got around filing a bug. As far as I know, schroot still doesn't
document how to delete a chroot.

> > What is the proper way to do that?
> 
> Asking for a friend? ;)
> 
> Assuming you used the suggestions for making the chroot on the sbuild
> wiki page, this should do it:
> 
> # rm -rf /srv/chroot/* /etc/sbuild/chroot/*-sbuild 
> /etc/schroot/chroot.d/*-sbuild
> 
> If you didn't use the suggestions on the wiki page, just start nuking
> stuff in those three directories.

Paul was talking about "a chroot" (singular). The above advice kills all
chroots including those that are not related to sbuild. Assuming that you are
using the schroot backend, you can do the following:

 1. figure out which schroot you were using with sbuild. If you used an
unstable chroot on amd64, then look out for a file that is called like
/etc/schroot/chroot.d/unstable-amd64-sbuild-XX where XX is a random
ASCII string
 2. look inside that file to figure out where the chroot data lives in your
file system by looking at the directory= or the file= options
 3. if you want to delete the schroot, just delete the configuration file under
/etc/schroot/chroot.d/unstable-amd64-sbuild-XX together with the actual
chroot the configuration file pointed to

I never heard about /etc/sbuild/chroot/ but it seems it's used for the sudo
backend. I don't even know where the code is that creates this. But if you
don't care, then you can leave that directory alone.

Thanks!

cheers, josch


signature.asc
Description: signature

Re: How do you delete a sbuild an sbuild chroot and start over?

[Sean Whitton]

On Tue, Aug 02, 2016 at 11:06:31PM -0500, Paul Elliott 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?

Asking for a friend? ;)

Assuming you used the suggestions for making the chroot on the sbuild
wiki page, this should do it:

# rm -rf /srv/chroot/* /etc/sbuild/chroot/*-sbuild 
/etc/schroot/chroot.d/*-sbuild

If you didn't use the suggestions on the wiki page, just start nuking
stuff in those three directories.

-- 
Sean Whitton


signature.asc
Description: PGP signature