On Wed, Oct 27, 2021 at 05:32:21PM +0300, Uladzimir Bely wrote:
> When sbuild is used to compile a package from sources, some packages (package
> dependencies) are internally downloaded and installed in schroot.
>
> I'm looking for a way to cache the dependencies in form of .
On 10/27/21 7:32 AM, Uladzimir Bely wrote:
When sbuild is used to compile a package from sources, some packages (package
dependencies) are internally downloaded and installed in schroot.
I'm looking for a way to cache the dependencies in form of .deb files outside
the schroot. So that I
On Wed, 27 Oct 2021 17:32:21 +0300
Uladzimir Bely wrote:
> I'm looking for a way to cache the dependencies in form of .deb files
> outside the schroot. So that I could later create a local partial
> debian repo from these .deb files and run sbuild for a second time
> using the
When sbuild is used to compile a package from sources, some packages (package
dependencies) are internally downloaded and installed in schroot.
I'm looking for a way to cache the dependencies in form of .deb files outside
the schroot. So that I could later create a local partial debian
Hi,
after some sbuild breaks which came from experimenting with setting up
ccache with sbuild (https://wiki.debian.org/sbuild) I've now discovered
that there are several schroot sessions permanently running at the same
time on my system, which I can't close because it says &quo
Addition, that's what happens trying to close any of the open sessions:
$ schroot -c
session:sid-amd64-sbuild-d6d9a259-3c44-46b1-9814-8b404cac5c6b -e -f
E: 15binfmt: update-binfmts: unable to open
/var/lib/schroot/mount/sid-amd64-sbuild-d6d9a259-3c44-46b1-9814-8b404cac5c6b/bin/sh:
No
Hi,
I've got a situation whereby there is a shared server that I need to
give an organization access to particular directories.
What I've devised, but it isn't working for the other side..., is the
following:
Debian Squeeze with schroot installed and a special schroot called
&quo
ot;
>> . "$SETUP_DATA_DIR/common-config"
>>
>> Where is this being sourced from (ie, where is the 'common-data'
>> file?) and (more important) where is this documented?
>
> It's set in the environment which the setup scripts run in. It
> sh
;
>
> Where is this being sourced from (ie, where is the 'common-data'
> file?) and (more important) where is this documented?
It's set in the environment which the setup scripts run in. It
should be documented in schroot-setup(5), but appears to be missing.
Mea culpa. T
On Fri, Sep 06, 2013 at 09:35:58AM +0200, Khaled Blah wrote:
> On 04.09.2013 17:16, Chris Bannister wrote:
> > On Wed, Sep 04, 2013 at 02:42:44PM +0200, Khaled Blah wrote:
> >> Hi all,
> >>
> >> I'd like to mount an NFS mount point into a schroot sessi
plete (so that maybe this shows up on google when the
next person has issues finding undocumented stuff in schroot - it's
not in the man page as my search implies btw):
/usr/share # find -iname "*.bz2" | while read f; do t=$(bzcat $f |
grep SETUP_DATA_DIR); test -n "$
eing sourced from (ie, where is the 'common-data'
file?) and (more important) where is this documented?
Doing "echo $SETUP_DATA_DIR" should help you, I think. And for
documentation, reading about shell will also help you.
I'm guessing this means it's exported by some
you.
I'm guessing this means it's exported by some schroot internal
mechanism inside the schroot? I'm not sure what I don't know about
bash that would help here? This doesn't seem to be an export bash
knows about?
I have no idea about what are the files you are sp
ctions"
>> . "$SETUP_DATA_DIR/common-config"
>>
>> Where is this being sourced from (ie, where is the 'common-data'
>> file?) and (more important) where is this documented?
>
>Doing "echo $SETUP_DATA_DIR" should help you, I think
Le 07.10.2013 18:38, shawn wilson a écrit :
This is at the top of every config file, but I can't find it
documented:
. "$SETUP_DATA_DIR/common-data"
. "$SETUP_DATA_DIR/common-functions"
. "$SETUP_DATA_DIR/common-config"
Where is this being sourced from (ie, where is the 'common-data'
file?)
This is at the top of every config file, but I can't find it documented:
. "$SETUP_DATA_DIR/common-data"
. "$SETUP_DATA_DIR/common-functions"
. "$SETUP_DATA_DIR/common-config"
Where is this being sourced from (ie, where is the 'common-data'
file?) and (more important) where is this documented?
On 04.09.2013 17:16, Chris Bannister wrote:
> On Wed, Sep 04, 2013 at 02:42:44PM +0200, Khaled Blah wrote:
>> Hi all,
>>
>> I'd like to mount an NFS mount point into a schroot session. I
>> understand I need to edit /etc/schroot/sbuild/fstab on the host to do
On Wed, Sep 04, 2013 at 02:42:44PM +0200, Khaled Blah wrote:
> Hi all,
>
> I'd like to mount an NFS mount point into a schroot session. I
> understand I need to edit /etc/schroot/sbuild/fstab on the host to do so
> but all my attempts so far failed. Does anyone here know how i
Hi all,
I'd like to mount an NFS mount point into a schroot session. I
understand I need to edit /etc/schroot/sbuild/fstab on the host to do so
but all my attempts so far failed. Does anyone here know how it can be done?
Regards,
--
Khaled Blah
System Administrator, Mara Sy
Roger Leigh wrote:
> Bob Proulx wrote:
> > There are two issues. ...
>
> So one key question here: do you have /proc mounted inside the
> chroot?
No. I only do that if the task and applications I am running in the
chroot require it. But for my typical chroot these are rarely
required. Sure they
root on the host system unintentionally. "Unlikely" isn't
a good enough guarantee here--we need to be absolutely certain.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/
`. `' schroot and sbuild http:/
Roger Leigh wrote:
> Bob Proulx wrote:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665827
>
> Note that this is a bug against initscripts, not debianutils.
Yes. But both are buggy! I also filed a bug against ischroot.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685034
> Is t
ack,
otherwise we run the standard codepath for a base system. I'm
not sure that there's a more reasonable solution here--we don't
have the information to make a better choice if it's 2. So it
would be useful to know exactly what the return value of
ischroot is (it must be run
Roger Leigh wrote:
> Bob Proulx wrote:
> > I haven't submitted a bug yet but I always have problems with sysvinit
> > postinst depending upon ischroot and ischroot getting it wrong and
> > that leaving a broken /run - /var/run behind. You might hit that too.
>
> If this is still happening, please
; > if [ -f /var/lib/schroot/session/sid-sab ]; then
> > schroot -rq -c $NAME /etc/init.d/sabnzbdplus stop
> > schroot -eq -c $NAME
> > else
> > echo "SABnzbd+ not running, not stooped" 2>&1
> > fi
> > }
> >
On Mon, Jul 23, 2012 at 06:27:22PM +0200, Ramon Hofer wrote:
> I now changed the stop function to (added the if test) to get rid of
> error messages when running `sid-sabnzbdplus stop` twice:
> stop_sab() {
> if [ -f /var/lib/schroot/session/sid-sab ]; then
> schroot -r
21 at 22:05 +0100, Roger Leigh wrote:
> > > > > I would also check the return status of schroot. If sid-sab
> > > > > already exists, then session creation will fail, and you'll
> > > > > reuse the old session. That might not be incorrect, but
> &
Is there another one which I can use to set specific mounts?
> > > > Like in my case the config dir in my home for sabnzbd?
> > >
> > > Not provided with the package. You could just
> > > sudo cp -r /etc/schroot/default /etc/schroot/sabnzbd
> > > an
e in my case the config dir in my home for sabnzbd?
> >
> > Not provided with the package. You could just
> > sudo cp -r /etc/schroot/default /etc/schroot/sabnzbd
> > and then set
> > script-config=/etc/schroot/sabnzdb/config
> > (you'll need to edit
On Sun, Jul 22, 2012 at 05:27:14PM +0200, Ramon Hofer wrote:
> On Son, 2012-07-22 at 15:58 +0100, Roger Leigh wrote:
> > On Sun, Jul 22, 2012 at 03:25:49PM +0200, Ramon Hofer wrote:
> > > On Sam, 2012-07-21 at 22:05 +0100, Roger Leigh wrote:
> > > > I would also chec
i, 20 Jul 2012 10:42:58 +0100, Roger Leigh wrote:
> > >>
> > >> > On Thu, Jul 19, 2012 at 12:34:26PM +, Ramon Hofer wrote:
> > >> >> I have some questions about starting daemons in a chroot environment
> > >> >> or rather about
On Son, 2012-07-22 at 15:58 +0100, Roger Leigh wrote:
> On Sun, Jul 22, 2012 at 03:25:49PM +0200, Ramon Hofer wrote:
> > On Sam, 2012-07-21 at 22:05 +0100, Roger Leigh wrote:
> > >
> > > Firstly, add schroot to Required-(Start|Stop), since you do
> > > need i
On Sun, Jul 22, 2012 at 03:25:49PM +0200, Ramon Hofer wrote:
> On Sam, 2012-07-21 at 22:05 +0100, Roger Leigh wrote:
> >
> > Firstly, add schroot to Required-(Start|Stop), since you do
> > need it to be set up prior to starting new sessions.
>
> Thanks for the hint!
&g
On Sam, 2012-07-21 at 22:05 +0100, Roger Leigh wrote:
> On Sat, Jul 21, 2012 at 04:52:24PM +, Ramon Hofer wrote:
> > On Sat, 21 Jul 2012 11:54:58 +, Ramon Hofer wrote:
> >
> > > I found what I did wrong: In the init.d script I used chroot instead of
&
t; > On Thu, Jul 19, 2012 at 12:34:26PM +, Ramon Hofer wrote:
> >> >> I have some questions about starting daemons in a chroot environment
> >> >> or rather about starting schroot on bootup.
> >> >> The reason I want to do this is to clean up my ser
On Sat, Jul 21, 2012 at 04:52:24PM +, Ramon Hofer wrote:
> On Sat, 21 Jul 2012 11:54:58 +, Ramon Hofer wrote:
>
> > I found what I did wrong: In the init.d script I used chroot instead of
> > schroot:
> > http://pastebin.com/raw.php?i=Lamy4K4a
> >
> &g
On Sat, 21 Jul 2012 11:54:58 +, Ramon Hofer wrote:
> I found what I did wrong: In the init.d script I used chroot instead of
> schroot:
> http://pastebin.com/raw.php?i=Lamy4K4a
>
> Could you please help me with the correct command?
> Instead of `chroot /srv/chroot/sid /etc/
ome questions about starting daemons in a chroot environment
>> >> or rather about starting schroot on bootup.
>> >> The reason I want to do this is to clean up my server. It's a
>> >> Squeeze with an AMD64 kernel from backports. Some packages are from
>
On Fri, 20 Jul 2012 14:24:11 -0600, Bob Proulx wrote:
> First I should say that schroot appears to have a lot more functionality
> than I previously realized. I had thought it was just a fancy suid
> chroot similar to 'dchroot' adding a security layer around chroot(2).
>
First I should say that schroot appears to have a lot more
functionality than I previously realized. I had thought it was just a
fancy suid chroot similar to 'dchroot' adding a security layer around
chroot(2). But it looks like it can do much more including building
chroots on the fly
On Fri, Jul 20, 2012 at 12:48:49PM +, Ramon Hofer wrote:
> On Fri, 20 Jul 2012 10:42:58 +0100, Roger Leigh wrote:
>
> > On Thu, Jul 19, 2012 at 12:34:26PM +, Ramon Hofer wrote:
> >> I have some questions about starting daemons in a chroot environment or
> >>
On Fri, 20 Jul 2012 10:42:58 +0100, Roger Leigh wrote:
> On Thu, Jul 19, 2012 at 12:34:26PM +, Ramon Hofer wrote:
>> I have some questions about starting daemons in a chroot environment or
>> rather about starting schroot on bootup.
>> The reason I want to do this is
local system administrator to control the behaviour of
invoke-rc.d for every initscript id and action"
http://people.debian.org/~hmh/invokerc.d-policyrc.d-specification.txt
So this script controls the way and order the daemons are started?
Is it correct that without it I wouldn't be
On Thu, Jul 19, 2012 at 12:34:26PM +, Ramon Hofer wrote:
> I have some questions about starting daemons in a chroot environment or
> rather about starting schroot on bootup.
> The reason I want to do this is to clean up my server. It's a Squeeze
> with an AMD64 kernel fro
imple case of a
chroot.
Thanks,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083
t; Entered the chroot with
> $ sudo schroot -p -c sid
>
> Installed locales and reconfigured them. I also installed vim.
Seems reasonable so far. Some packages will require /proc. Some will
also require /dev. Some will require other things.
> I noticed that auto-completion isn't wo
Hi all
I have some questions about starting daemons in a chroot environment or
rather about starting schroot on bootup.
The reason I want to do this is to clean up my server. It's a Squeeze
with an AMD64 kernel from backports. Some packages are from testing which
gives me problems becau
th 32 and 64 bits.
>
> I've already used schroot before, and I'm quite familiar with it, but
> I do not fully understand how
> programs from the chroot can open X windows on the host. It always
> seemed magical to me.
All you need is to be able to connect to the X server. So havin
Hello all,
I'd like to use schroots to build and use openGL programs
(openscenegraph, ogre, and some
proprietary scientific software which use these libs) under different releases
of debian/ubuntu, for both 32 and 64 bits.
I've already used schroot before, and I'm quite familiar
and:
> > >
> > > apt-get upgrade
> > > [...]
> > > Setting up schroot (1.4.19-1+squeeze1) ...
> > > dpkg: warning: schroot: config file
> > > '/etc/schroot/default/nssdatabases' is a circular link (=
> > > '/etc/sc
> On Mon, 6 Jun 2011 10:15:01 +0100
> Roger Leigh wrote:
> On Mon, Jun 06, 2011 at 09:45:59AM +0300, Mihamina Rakotomandimby
> wrote:
> > This morning, I upgraded my system and:
> >
> > apt-get upgrade
> > [...]
> > Setting up schroot (1.4.19-1+
On Mon, Jun 06, 2011 at 09:45:59AM +0300, Mihamina Rakotomandimby wrote:
> This morning, I upgraded my system and:
>
> apt-get upgrade
> [...]
> Setting up schroot (1.4.19-1+squeeze1) ...
> dpkg: warning: schroot: config file '/etc/schroot/default/nssdatabases
Hi all,
This morning, I upgraded my system and:
apt-get upgrade
[...]
Setting up schroot (1.4.19-1+squeeze1) ...
dpkg: warning: schroot: config file '/etc/schroot/default/nssdatabases' is a
circular link
(= '/etc/schroot/default/nssdatabases')
dpkg: warning:
>
> actually, location seems to be deprecated, while directory does not print
> warnings.
>
> 09:26 ~ % LANG=C schroot -c ia32
> W: line 15 [ia32]: Deprecated key 'location' used
> I: This option will be removed in the future; please update your configuration
'lo
probably want "type=directory".
Thanks a lot, I missed that one :)
> Also, I think your 'directory'
> setting should be 'location', i.e. 'location=/srv/chroot/ia32'. See
> man schroot.conf for details.
actually, location seems to be deprecated, w
On Mon, Feb 15, 2010 at 8:15 AM, wrote:
>
> Here is my schroot.conf
>
> [ia32]
> description=Debian testing 32bits
> directory=/srv/chroot/ia32
> users=arno
> root-groups=root
> root-users=arno
> run-exec-scripts=true
>
You've omitted the 'type=' setting which causes the type to default to
'plai
Hi,
I'm using a 64bits debian unstable, and using schroot to be able to easily
(eliminating the need to become root) chroot to a 32bits environment.
I want to have /tmp, /dev, /proc, and /dev/pts shared between host system and
chroot. So, I used to have lines such as
/tmp/srv/chroot
On Sat, Aug 23, 2008 at 08:12:11PM +0200, Aniruddha wrote:
> On Fri, 2008-08-22 at 11:17 -0700, Bob McGowan wrote:
> > I'd guess "libgnomebreakpad.so" is not accessible from within the
> > schroot environment.
> >
> > And without it, GTK and ne
On Fri, 2008-08-22 at 11:17 -0700, Bob McGowan wrote:
> I'd guess "libgnomebreakpad.so" is not accessible from within the
> schroot environment.
>
> And without it, GTK and nero can't do anything affecting the display.
>
> *However*, this is all guesswo
Aniruddha wrote:
On Fri, 2008-08-22 at 09:43 -0700, Bob McGowan wrote:
What does 'xhost' say when you run it as the "normal" user (before you
do the schroot)?
You may need to do an 'xhost local:' to allow any local (only your host
system logins) user to con
On Fri, 2008-08-22 at 09:43 -0700, Bob McGowan wrote:
> What does 'xhost' say when you run it as the "normal" user (before you
> do the schroot)?
>
> You may need to do an 'xhost local:' to allow any local (only your host
> system logins) user
Aniruddha wrote:
I have set up a schroot using this guide:
http://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html#id292205 , but for some reason when I try to run a program I get the following error:
~$ schroot -p nero
W: Group ‘sbuild’ not found
I: [sid chroot] Running
I have set up a schroot using this guide:
http://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html#id292205
, but for some reason when I try to run a program I get the following error:
> ~$ schroot -p nero
> W: Group ‘sbuild’ not found
> I: [sid chroot] Running comma
shame <[EMAIL PROTECTED]> writes:
> Did you find a satisfactory solution to this problem?
> I also have the nasty build up of sessions using schroot.
>
> Using schroot -e --all-sessions does clear out the sessions but I
> can't find a way to automate this.
It's w
Did you find a satisfactory solution to this problem?
I also have the nasty build up of sessions using schroot.
Using schroot -e --all-sessions does clear out the sessions but I can't find a
way to automate this.
I tried adding this to a launcher on my panel ([i]schroot -e --all-ses
Anton Piatek wrote:
Wackojacko wrote:
Anton Piatek wrote:
Wackojacko wrote:
Anton Piatek wrote:
It may help if you could give us more information on what myprogram
does, and how it is launched, in the chroot?
In any case you could try
#schroot -e --all-sessions
to kill the existing
Wackojacko wrote:
> Anton Piatek wrote:
>> Wackojacko wrote:
>>> Anton Piatek wrote:
>>>> Hi, I set up a basic schroot environment to run a couple of 32 bit
>>>> apps on my amd64 box. The problem is that when the program exits
>>>> schroot le
Anton Piatek wrote:
Wackojacko wrote:
Anton Piatek wrote:
Hi, I set up a basic schroot environment to run a couple of 32 bit
apps on my amd64 box. The problem is that when the program exits
schroot leaves all its session data behind, mount points and all (so
`mount` returns a hell of a lot of
Wackojacko wrote:
> Anton Piatek wrote:
>> Hi, I set up a basic schroot environment to run a couple of 32 bit
>> apps on my amd64 box. The problem is that when the program exits
>> schroot leaves all its session data behind, mount points and all (so
>> `mount` returns
Anton Piatek wrote:
Hi,
I set up a basic schroot environment to run a couple of 32 bit apps on my
amd64 box. The problem is that when the program exits schroot leaves all its
session data behind, mount points and all (so `mount` returns a hell of a lot
of entries)
schroot is being called as
Hi,
I set up a basic schroot environment to run a couple of 32 bit apps on my
amd64 box. The problem is that when the program exits schroot leaves all its
session data behind, mount points and all (so `mount` returns a hell of a lot
of entries)
schroot is being called as follows
`ls -l
at if you are using schroot there are chances you can
avoid binding directories and copying or hard linking files. Check
schroot manpage and modify /etc/schroot/setup.d/10mount to match your
needs.
this is what i would like to do - there should be some possibility to
let schroot manage bind mou
On (10/11/06 09:53), Lubos Vrbka wrote:
> could anybody please show me how to setup schroot so, that it
> automatically bindmounts the /dev, /tmp and /home directories inside the
> chroot when it is entered? until now i was using permanent bind mount in
> my fstab. however
hi guys,
could anybody please show me how to setup schroot so, that it
automatically bindmounts the /dev, /tmp and /home directories inside the
chroot when it is entered? until now i was using permanent bind mount in
my fstab. however, having the directories bindmounted only when the
chroot
Þann 2006-10-12, 21:03:03 (-0400) skrifaði T:
> Hi
>
> I have both dchroot & schroot installed on my box, but I want to just keep
> one. On seeing:
>
> schroot shares most of its options with dchroot, but offers vastly
> more functionality.
>
> I decided to remo
Hi
I have both dchroot & schroot installed on my box, but I want to just keep
one. On seeing:
schroot shares most of its options with dchroot, but offers vastly
more functionality.
I decided to remove schroot because I don't need those fancy functionality.
but I can't because:
76 matches
Mail list logo
