Re: [Pkg-javascript-devel] Using clean build scripts from pkg-ruby-extras repo

2016-12-31 Thread Ross Gammon
Hi all,

On 29/11/16 12:20, Antonio Terceiro wrote:
> On Mon, Nov 28, 2016 at 10:44:08PM +0530, Pirate Praveen wrote:
>> On 2016, നവംബർ 28 10:27:15 PM IST, Paolo Greppi  
>> wrote:
>>> Hi this is opinionated but very useful. I have a couple of newbie
>>> questions.
>>>
>>> Did you try these scripts on Debian stable as host ?
>> No, I have not tried.
> Neither did I, but I will be happy to merge patches if anything does not
> work.

I run Jessie on my laptop, and thought I would give pkg-ruby-extras a
go. I ran into problems running the setup script due to a lack of space
under /root (too many chroots & containers!). This is my fault and a
problem I had been meaning to fix for a while.

So after fixing that, the next problem is that you run into #843137 with
sbuild (there have been a lot of changes in unstable/stretch with apt &
gpg). You have to install sbuild from jessie-backports to fix that.

Then the build command works fine up until the debci bit:
Run the test suite now? [Y/n]y
adt-run [16:44:30]: version 3.6jessie1
Error: container adt-sid-amd64 is not defined
: failure: ['sudo', 'lxc-clone', '--new',
'adt-virt-lxc-tbsmsn', '--orig', 'adt-sid-amd64'] failed (exit status 1)
adt-run [16:44:30]: ERROR: testbed failed: cannot send to testbed:
['BrokenPipeError: [Errno 32] Broken pipe\n']

WARNING: Test suite failed! Please verify before uploading

Now edit /home/ross/.chdist/unstable/etc/apt/sources.list
Run chdist apt-get unstable update
And enjoy.

I suppose I will have to create the adt-sid-amd64 manually, and then run
into the same gpg/apt issue. But it is Christmas Eve now, and that will
have to wait.

All the best!

Ross
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Using clean build scripts from pkg-ruby-extras repo

2016-11-29 Thread Antonio Terceiro
On Mon, Nov 28, 2016 at 10:44:08PM +0530, Pirate Praveen wrote:
> 
> 
> On 2016, നവംബർ 28 10:27:15 PM IST, Paolo Greppi  
> wrote:
> >Hi this is opinionated but very useful. I have a couple of newbie
> >questions.
> >
> >Did you try these scripts on Debian stable as host ?
> 
> No, I have not tried.

Neither did I, but I will be happy to merge patches if anything does not
work.

> >Why do we need two virtualization systems (schroot for sbuild & lxc for
> >autopkgtest) ?
> 
> I did not write these, my intention was to share the usefulness of the
> tool. I hope Antonio, who wrote this, will clarify.
> 
> I guess its because lxc has better isolation and can offer a closer
> environment to real world so that is used for autopkgtest while a
> chroot is lighter and is enough for build environment.

that, and also

- chroot is what sbuild uses by default, and it's what is used on the
  debian build daemons
- lxc is what is used in Debian CI


signature.asc
Description: PGP signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Using clean build scripts from pkg-ruby-extras repo

2016-11-28 Thread Pirate Praveen


On 2016, നവംബർ 28 10:27:15 PM IST, Paolo Greppi  wrote:
>Hi this is opinionated but very useful. I have a couple of newbie
>questions.
>
>Did you try these scripts on Debian stable as host ?

No, I have not tried.

>Why do we need two virtualization systems (schroot for sbuild & lxc for
>autopkgtest) ?

I did not write these, my intention was to share the usefulness of the tool. I 
hope Antonio, who wrote this, will clarify.

I guess its because lxc has better isolation and can offer a closer environment 
to real world so that is used for autopkgtest while a chroot is lighter and is 
enough for build environment.

>Would it be possible to use only one (for example lxc) ?

It could be done, but then it would diverge from the buildd configuration, so 
successful builds in lxc may not succeed in debian auto builders.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Using clean build scripts from pkg-ruby-extras repo

2016-11-28 Thread Paolo Greppi
Hi this is opinionated but very useful. I have a couple of newbie questions.

Did you try these scripts on Debian stable as host ?

Why do we need two virtualization systems (schroot for sbuild & lxc for
autopkgtest) ?

Would it be possible to use only one (for example lxc) ?

Paolo

On 28/11/2016 08:27, Pirate Praveen wrote:
> Hi,
> 
> I find these scripts very useful so I thought of sharing it more widely.
> I use it for ruby, go and nodejs packages.
> 
> Scripts are here
> https://anonscm.debian.org/cgit/pkg-ruby-extras/pkg-ruby-extras.git
> 
> 1. git clone
> 2. add cloned location to PATH,
> 3. and run `setup`, (this will create sbuild chroot and lxc-container)
> 4. then run `build` when you want to build a package from its source
> tree (those who have upload access can use build-and-upload).
> 
> Features:
> 1. It will build in a clean chroot using sbuild,
> 2. it will run autopkgtest in an lxc container,
> 3. it will offer to run autopkgtest of any or all reverse dependencies,
> 4. it will also offer to rebuild all or any reverse build dependencies.
> 
> It is very convenient when updating packages, especially for major
> updates that may break reverse dependencies.
> 
> It could end up in a package some time in the future when it is made
> more generic https://lists.debian.org/debian-ruby/2016/11/msg00011.html
> 
> Thanks
> Praveen




signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel