Hi all, Quoting Ross Gammon (2017-06-25 12:18:53) > Bringing query about the pkg-ruby-extras scripts on mentors list to > debian-ruby. I would like to finally get sbuild & lxc set up on my > Jessie machine so I can use the pkg-ruby-extras script, and I hope that > Josch can help with some improvements to the script for sbuild.
I'm dropping debian-mentors from the recipients of this thread as this problem
seems to be related to sbuild (where I can help) and the pkg-ruby-extras team
(now part of the recipients).
> >> W: Not creating symlink /srv/chroots/unstable-amd64-sbuild to
> >> /etc/sbuild/chroot/unstable-amd64-sbuild: file already exists
> > This is troublesome. It appears you already had a chroot set up?
> Yes - probably - I have had many unsuccessful goes at it in the past on
> different machines, and I can never remember where I got to.
What is your output of $(schroot --all-source-chroots --list)?
sbuild-createchroot will create schroot configuration files in
/etc/schroot/chroot.d in *.ini format. You can investigate these config files
to easily see which chroots schroot knows about (they should be listed above)
and where in your filesystem the chroot is located. You can do the latter by
either looking at the file option (in case of tarball based chroots) or the
directory option (in case of directory based chroots).
> $ schroot -l
> E: /etc/schroot/chroot.d/unstable-amd64-sbuild-GlcVID: line 1
> [unstable-amd64-sbuild]: A chroot or alias
> ‘chroot:unstable-amd64-sbuild’ already exists with this name
> I: Duplicate names are not allowed
Look at the files in /etc/schroot/chroot.d/. There should be another config
file with the string "[unstable-amd64-sbuild]" in the first line. Investigate
which chroot they are each pointing to (maybe the same) and then maybe rename
one of them for now.
> > Yup, this looks like the chroot you want to create already exists.
> What is the best way to clear it all out and start again?
In case you are only using schroot for sbuild, then you can safely delete the
config files in /etc/schroot/chroot.d together with the chroot locations they
reference. If those config files were created by sbuild-createchroot, then
their name should follow the format:
${dist}-${arch}-sbuild-${random}
The pkg-ruby-extras script seems to put the chroots into /srv/chroots/ while
the sbuild-createchroot man page suggests /srv/chroot/.
Since recently there is also the command sbuild-destroychroot which will give
you advice on how to remove a chroot.
> > Everything you did so far didn't use lxc at all. Instead, schroot was used
> > as a build environment.
> I think the intention of the setup script is to set up sbuild for building,
> and lxc for autopkgtest. Maybe I have a half-setup lxc, and debci tries to
> fallback to sbuild. I should debug the setup script some more.
Yes, that's likely. Though it's also possible to build packages using sbuild
with an lxc backend. In that case, only lxc would be needed and not schroot as
well.
> > If I understand it correctly, then you are using this script:
> >
> > https://anonscm.debian.org/cgit/pkg-ruby-extras/pkg-ruby-extras.git/tree/setup
> >
> > Unfortunately, there is much to be improved about this script. If you want
> > to
> > help improve it, just contact the authors of the script with your problems
> > and
> > CC me. :)
> You are correct. I used debomatic online (http://debomatic-amd64.debian.net/)
> to test my new autopkgtests in the end. But I would rather debug them
> locally. And I would like to begin using pkg-ruby-extras for all of the
> little transitions we have to do in pkg-javascript (like Pirate & others do).
>
> I have just subscribed to debian-ruby (as I have some ruby stuff that I
> use locally and would like to package one day), and added them to this
> mail. We can probably drop mentors from cc. I will report back on any
> resolutions.
If the pkg-ruby-extras team is interested in a review of the setup script, then
I can put that into a separate mail.
Thanks!
cheers, josch
signature.asc
Description: signature
