Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #207475 > unrolled thread

[sbuild] how to create chroot environment

Started byAlexei Fedotov <alexei.fedotov@gmail.com>
First post2019-04-15 13:10 +0200
Last post2019-04-15 17:30 +0200
Articles 8 — 5 participants

Back to article view | Back to linux.debian.user

Contents

  [sbuild] how to create chroot environment Alexei Fedotov <alexei.fedotov@gmail.com> - 2019-04-15 13:10 +0200
    Re: [sbuild] how to create chroot environment Georgi Naplatanov <gosho@oles.biz> - 2019-04-15 13:30 +0200
      Re: [sbuild] how to create chroot environment Alexei Fedotov <alexei.fedotov@gmail.com> - 2019-04-15 13:40 +0200
        Re: [sbuild] how to create chroot environment Alexei Fedotov <alexei.fedotov@gmail.com> - 2019-04-15 13:50 +0200
        Re: [sbuild] how to create chroot environment Jonathan Dowland <jmtd@debian.org> - 2019-04-15 16:30 +0200
          Re: [sbuild] how to create chroot environment <tomas@tuxteam.de> - 2019-04-15 16:40 +0200
            Re: [sbuild] how to create chroot environment Markus Schönhaber <debian-user@list-post.mks-mail.de> - 2019-04-15 17:10 +0200
              Re: [sbuild] how to create chroot environment <tomas@tuxteam.de> - 2019-04-15 17:30 +0200

#207475 — [sbuild] how to create chroot environment

FromAlexei Fedotov <alexei.fedotov@gmail.com>
Date2019-04-15 13:10 +0200
Subject[sbuild] how to create chroot environment
Message-ID<xN7ES-2Yr-9@gated-at.bofh.it>
Hello,
I've installed sbuild ver 0.73.0-4 and tried creating chroot environment

I used the following command and get an error.

devops@devops:~/git/docker.io$ sudo sbuild-createchroot
--include=eatmydata,ccache,gnupg unstable
/srv/chroot/unstable-amd64-sbuild http://deb.debian.org/debian
open3: exec of schroot -l --all-source-chroots failed: No such file or
directory at /usr/sbin/sbuild-createchroot line 217.

It seems "schroot" chommand is called, and it is nowhere to be found.
How could I create the chroot env?

--
Carry a towel
http://dataved.ru/
+7 916 562 8095

[1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
[2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
[3] Start using Apache Openmeetings today, http://openmeetings.apache.org/

[toc] | [next] | [standalone]

#207477

FromGeorgi Naplatanov <gosho@oles.biz>
Date2019-04-15 13:30 +0200
Message-ID<xN7Yd-35a-3@gated-at.bofh.it>
In reply to#207475
On 4/15/19 2:02 PM, Alexei Fedotov wrote:
> Hello,
> I've installed sbuild ver 0.73.0-4 and tried creating chroot environment
> 
> I used the following command and get an error.
> 
> devops@devops:~/git/docker.io$ sudo sbuild-createchroot
> --include=eatmydata,ccache,gnupg unstable
> /srv/chroot/unstable-amd64-sbuild http://deb.debian.org/debian
> open3: exec of schroot -l --all-source-chroots failed: No such file or
> directory at /usr/sbin/sbuild-createchroot line 217.
> 
> It seems "schroot" chommand is called, and it is nowhere to be found.

"schroot" is a Debian package and you can install it easily.

> How could I create the chroot env?

There are other ways (debootstrap for example) but if you want to use
"sbuild" then "schroot" is the preferred way I think.

Kind regards
Georgi

[toc] | [prev] | [next] | [standalone]

#207480

FromAlexei Fedotov <alexei.fedotov@gmail.com>
Date2019-04-15 13:40 +0200
Message-ID<xN87U-38n-7@gated-at.bofh.it>
In reply to#207477
Georgi, thanks!
it seems schroot package is somehow missed in my repository, I will
look into it.

--
Carry a towel
http://dataved.ru/
+7 916 562 8095

[1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
[2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
[3] Start using Apache Openmeetings today, http://openmeetings.apache.org/

On Mon, Apr 15, 2019 at 2:23 PM Georgi Naplatanov <gosho@oles.biz> wrote:
>
> On 4/15/19 2:02 PM, Alexei Fedotov wrote:
> > Hello,
> > I've installed sbuild ver 0.73.0-4 and tried creating chroot environment
> >
> > I used the following command and get an error.
> >
> > devops@devops:~/git/docker.io$ sudo sbuild-createchroot
> > --include=eatmydata,ccache,gnupg unstable
> > /srv/chroot/unstable-amd64-sbuild http://deb.debian.org/debian
> > open3: exec of schroot -l --all-source-chroots failed: No such file or
> > directory at /usr/sbin/sbuild-createchroot line 217.
> >
> > It seems "schroot" chommand is called, and it is nowhere to be found.
>
> "schroot" is a Debian package and you can install it easily.
>
> > How could I create the chroot env?
>
> There are other ways (debootstrap for example) but if you want to use
> "sbuild" then "schroot" is the preferred way I think.
>
> Kind regards
> Georgi
>

[toc] | [prev] | [next] | [standalone]

#207482

FromAlexei Fedotov <alexei.fedotov@gmail.com>
Date2019-04-15 13:50 +0200
Message-ID<xN8hz-3bU-3@gated-at.bofh.it>
In reply to#207480
I've installed schroot from http://deb.debian.org/debian and it
worked. Thanks again for your help.
--
Carry a towel
http://dataved.ru/
+7 916 562 8095

[1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
[2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
[3] Start using Apache Openmeetings today, http://openmeetings.apache.org/

On Mon, Apr 15, 2019 at 2:30 PM Alexei Fedotov <alexei.fedotov@gmail.com> wrote:
>
> Georgi, thanks!
> it seems schroot package is somehow missed in my repository, I will
> look into it.
>
> --
> Carry a towel
> http://dataved.ru/
> +7 916 562 8095
>
> [1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
> [2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
> [3] Start using Apache Openmeetings today, http://openmeetings.apache.org/
>
> On Mon, Apr 15, 2019 at 2:23 PM Georgi Naplatanov <gosho@oles.biz> wrote:
> >
> > On 4/15/19 2:02 PM, Alexei Fedotov wrote:
> > > Hello,
> > > I've installed sbuild ver 0.73.0-4 and tried creating chroot environment
> > >
> > > I used the following command and get an error.
> > >
> > > devops@devops:~/git/docker.io$ sudo sbuild-createchroot
> > > --include=eatmydata,ccache,gnupg unstable
> > > /srv/chroot/unstable-amd64-sbuild http://deb.debian.org/debian
> > > open3: exec of schroot -l --all-source-chroots failed: No such file or
> > > directory at /usr/sbin/sbuild-createchroot line 217.
> > >
> > > It seems "schroot" chommand is called, and it is nowhere to be found.
> >
> > "schroot" is a Debian package and you can install it easily.
> >
> > > How could I create the chroot env?
> >
> > There are other ways (debootstrap for example) but if you want to use
> > "sbuild" then "schroot" is the preferred way I think.
> >
> > Kind regards
> > Georgi
> >

[toc] | [prev] | [next] | [standalone]

#207495

FromJonathan Dowland <jmtd@debian.org>
Date2019-04-15 16:30 +0200
Message-ID<xNaMp-4Og-1@gated-at.bofh.it>
In reply to#207480
On Mon, Apr 15, 2019 at 02:30:33PM +0300, Alexei Fedotov wrote:
>it seems schroot package is somehow missed in my repository, I will
>look into it.

schroot is merely recommended by sbuild, and not depended upon by it:
presumably sbuild can be used in some other way without schroot. When
you installed sbuild your package manager must have been configured
not to install Recommends; the default behaviour (for apt, at least)
is to install Recommends.

-- 

Jonathan Dowland

[toc] | [prev] | [next] | [standalone]

#207499

From<tomas@tuxteam.de>
Date2019-04-15 16:40 +0200
Message-ID<xNaW6-4RD-9@gated-at.bofh.it>
In reply to#207495

[Multipart message — attachments visible in raw view] — view raw

On Mon, Apr 15, 2019 at 03:26:04PM +0100, Jonathan Dowland wrote:
> On Mon, Apr 15, 2019 at 02:30:33PM +0300, Alexei Fedotov wrote:
> >it seems schroot package is somehow missed in my repository, I will
> >look into it.
> 
> schroot is merely recommended by sbuild, and not depended upon by it:
> presumably sbuild can be used in some other way without schroot. When
> you installed sbuild your package manager must have been configured
> not to install Recommends; the default behaviour (for apt, at least)
> is to install Recommends.

Yes, sbuild defaults to schroot, but can use other methods. From
sbuild's man page:

  --chroot-mode=schroot|sudo|autopkgtest
    Select the desired chroot mode. Four values are possible:
    schroot (the default), sudo (which uses sudo to execute
    chroot in a directory from  /etc/sbuild/chroot or ./chroot)
    and autopkgtest which uses the autopkgtest-virt-* binaries
    (selectable via the --autopkgtest-virt-server option). 
    This command line option sets the CHROOT_MODE configuration
    variable. See sbuild.conf(5) for more information.

So at first sight it seems that sbuild doesn't check whether schroot
is available, and if not, it runs aground by trying to use it, as
it is its default.

OP has installed schroot already, which is generally a Good Thing
anyway -- but whenever there are reasons not to use it, perhaps
the command-line option "--chroot-mode=sudo" (or its equivalent
config item) might be of help.

Cheers
-- tomás

[toc] | [prev] | [next] | [standalone]

#207504

FromMarkus Schönhaber <debian-user@list-post.mks-mail.de>
Date2019-04-15 17:10 +0200
Message-ID<xNbp9-5hx-35@gated-at.bofh.it>
In reply to#207499
Tomas, 15.4.2019 16:38 +0200:

>   --chroot-mode=schroot|sudo|autopkgtest
>     Select the desired chroot mode. Four values are possible:
>     schroot [...], sudo [...] and autopkgtest [...]

Out of curiosity: am I missing something or are there only three of the
"Four values" which "are possible" documented? What might be the fourth?

-- 
Regards
  mks

[toc] | [prev] | [next] | [standalone]

#207506

From<tomas@tuxteam.de>
Date2019-04-15 17:30 +0200
Message-ID<xNbIv-5om-9@gated-at.bofh.it>
In reply to#207504

[Multipart message — attachments visible in raw view] — view raw

On Mon, Apr 15, 2019 at 05:05:53PM +0200, Markus Schönhaber wrote:
> Tomas, 15.4.2019 16:38 +0200:
> 
> >   --chroot-mode=schroot|sudo|autopkgtest
> >     Select the desired chroot mode. Four values are possible:
> >     schroot [...], sudo [...] and autopkgtest [...]
> 
> Out of curiosity: am I missing something or are there only three of the
> "Four values" which "are possible" documented? What might be the fourth?

Yes, this looks like an error. I'd venture that there are just three
values.

Cheers
-- t

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web