Okay.
Given the severely constrained manpower from all involved sides, I think
the best path forward to make some progress is to continue the review (and
eventual merge, hopefully) of my proposed patch in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859867#105. If we want to
expand scope, we
On Fri, 05 Jan 2018, Michael Stapelberg wrote:
> Raphaël, Benjamin, what’s the current status? It’s been quite a number
> of months since https://bugs.debian.org/859867#122, and I’m still very
> interested in having sbuild easily installable.
Benjamin never answered on the willingness to host
Hi,
Johannes Schauer writes:
> Quoting Simon McVittie (2017-08-20 01:16:12)
>> On Sun, 20 Aug 2017 at 00:26:26 +0900, Johannes Schauer wrote:
>> > since sbuild already supports autopkgtest as a backend (and thus also
>> > autopkgtest-virt-qemu which vectis seems to be using)
Quoting Simon McVittie (2017-08-20 01:16:12)
> On Sun, 20 Aug 2017 at 00:26:26 +0900, Johannes Schauer wrote:
> > since sbuild already supports autopkgtest as a backend (and thus also
> > autopkgtest-virt-qemu which vectis seems to be using) I'd be especially
> > interested in hearing which
On Fri, 11 Aug 2017 at 22:26:20 +0200, Raphael Hertzog wrote:
> Simon, you might want to review the history of #859867 and share
> your thoughts about this topic and let us know whether vectis
> is going to handle all this too. :)
Part of the purpose of vectis is to set up and run sbuild in an
Hi Simon,
Quoting Raphael Hertzog (2017-08-12 05:26:20)
> FYI, while watching the autopkgtest BoF at debconf, I discovered
> vectis by Simon McVittie:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843486
>
> Arguably it covers some common grounds since it does setup
> sbuild in a VM. Maybe
Hello,
FYI, while watching the autopkgtest BoF at debconf, I discovered
vectis by Simon McVittie:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843486
Arguably it covers some common grounds since it does setup
sbuild in a VM. Maybe there's room for collaboration here
as well?
Simon, you
On Thu, 10 Aug 2017, Michael Stapelberg wrote:
> Sounds good. Are you willing to contribute to this? I have no experience
> with autopkgtest at all.
Yes, I'm willing to help.
As for the proper umbrella for this work, maybe it can be part of the
"packaging-dev" source package ? Benjamin, have a
Hello guys,
On Sat, 05 Aug 2017, Michael Stapelberg wrote:
> Thanks for the thorough review. It took me quite a bit to address all these
> comments :).
Great to see progress being made here but I have a few ideas that might
impact how you implement all this.
I really like the idea to make it
Sounds good. Are you willing to contribute to this? I have no experience
with autopkgtest at all.
On Thu, Aug 10, 2017 at 6:41 AM, Raphael Hertzog wrote:
> Hello guys,
>
> On Sat, 05 Aug 2017, Michael Stapelberg wrote:
> > Thanks for the thorough review. It took me quite a
control: block -1 by 870260
Thanks for the thorough review. It took me quite a bit to address all these
comments :).
Find the updated patch attached, and answers inline:
On Wed, Aug 2, 2017 at 8:11 AM, Johannes Schauer wrote:
> Quoting Michael Stapelberg (2017-08-01
Quoting Michael Stapelberg (2017-08-01 23:15:04)
> Alright! Patch attached and provided inline, for your convenience:
Cool!
> +if (!defined($ENV{SUDO_USER})) {
> +die "Please run sudo $0";
> +}
Should you not rather check the UID instead?
> +system("adduser", "--quiet", "--",
Alright! Patch attached and provided inline, for your convenience:
>From b29b1faf6bafb4b6e51b4e99d0febc81abbb543c Mon Sep 17 00:00:00 2001
From: Michael Stapelberg
Date: Tue, 1 Aug 2017 23:13:36 +0200
Subject: [PATCH] add sbuild-debian-developer-setup package
---
That works for me :).
How shall we proceed? Should I prepare a patch against the sbuild package?
On Tue, Aug 1, 2017 at 11:00 AM, Johannes Schauer wrote:
> Quoting Michael Stapelberg (2017-08-01 10:51:41)
> > I think the following suggestion takes care of all the concerns you
Quoting Michael Stapelberg (2017-08-01 11:04:16)
> That works for me :).
>
> How shall we proceed? Should I prepare a patch against the sbuild package?
Yes please!
Put the patch into this bug and then we can talk about it. :)
signature.asc
Description: signature
Quoting Michael Stapelberg (2017-08-01 10:51:41)
> I think the following suggestion takes care of all the concerns you brought
> up: Let’s name it sbuild-debian-developer-setup, describe that the goal is to
> provide an sbuild setup which can build packages for Debian unstable,
> automates
On Mon, Jul 31, 2017 at 4:24 PM, Johannes Schauer wrote:
> Quoting Michael Stapelberg (2017-07-31 14:19:16)
> > Unless I’m mistaken, the following is what we’d need to recommend to new
> > users:
> >
> > % sudo apt install sbuild apt-cacher-ng lintian
>
> Why install lintian?
>
Quoting Michael Stapelberg (2017-07-31 14:19:16)
> Unless I’m mistaken, the following is what we’d need to recommend to new
> users:
>
> % sudo apt install sbuild apt-cacher-ng lintian
Why install lintian?
> % sudo adduser --quiet -- "$USER" sbuild
Better:
sudo sbuild-adduser $USER
> % sudo
On Sun, Jul 30, 2017 at 7:53 PM, Johannes Schauer wrote:
> Hi,
>
> Quoting Michael Stapelberg (2017-06-02 18:23:02)
> > Thanks for the review. Answers inline:
>
> sorry for the delay. I'm under a pile of work and this wasn't on the top
> of my
> todo list. But let me not stall
Hi,
Quoting Michael Stapelberg (2017-06-02 18:23:02)
> Thanks for the review. Answers inline:
sorry for the delay. I'm under a pile of work and this wasn't on the top of my
todo list. But let me not stall your work:
> > > # Enable eatmydata: occasionally losing a test build is preferable over
>
josch, friendly ping? :)
On Fri, Jun 2, 2017 at 6:23 PM, Michael Stapelberg
wrote:
> Thanks for the review. Answers inline:
>
> On Wed, May 24, 2017 at 11:03 AM, Johannes Schauer
> wrote:
>
>> Hi,
>>
>> Quoting Geert Stappers (2017-05-21 08:43:31)
>> >
Thanks for the review. Answers inline:
On Wed, May 24, 2017 at 11:03 AM, Johannes Schauer wrote:
> Hi,
>
> Quoting Geert Stappers (2017-05-21 08:43:31)
> > the debian/postinst now here inline
>
> thanks, that allows me to comment easily.
>
> > # Add to group sbuild all
On Wed, 24 May 2017, Michael Stapelberg wrote:
> Thanks for the feedback. Any suggestions as to how the script should be
> called, and which options it should have, if any?
In my case, I believe that we should have a cron job/systemd timer that
updates the chroot each week and that cron job could
Hi,
Quoting Geert Stappers (2017-05-21 08:43:31)
> the debian/postinst now here inline
thanks, that allows me to comment easily.
> # Add to group sbuild all âdynamically allocated user accountsâ; see
> # https://www.debian.org/doc/debian-policy/ch-opersys.html
> for user in $(getent passwd
Thanks for the feedback. Any suggestions as to how the script should be
called, and which options it should have, if any?
On Wed, May 24, 2017 at 1:17 AM, Johannes Schauer wrote:
> Hello all,
>
> Quoting Ansgar Burchardt (2017-05-24 08:42:37)
> > Michael Stapelberg
Hello all,
Quoting Ansgar Burchardt (2017-05-24 08:42:37)
> Michael Stapelberg writes:
> > Doing it in a script is one more step. The point of this endavour is to
> > make the setup as simple as possible.
>
> I think creating a chroot in postinst is not good. Mostly
Hi,
Michael Stapelberg writes:
> Doing it in a script is one more step. The point of this endavour is to
> make the setup as simple as possible.
I think creating a chroot in postinst is not good. Mostly because
maintainer scripts should never fail, but this is too likely
Doing it in a script is one more step. The point of this endavour is to
make the setup as simple as possible.
On that note, the awkward newgrp step afterwards still irks me.
On Sun, May 21, 2017 at 8:43 AM, Geert Stappers
wrote:
> On Sat, May 20, 2017 at 11:34:37PM +0200,
On Sat, May 20, 2017 at 11:34:37PM +0200, Michael Stapelberg wrote:
>
> Find attached the first draft of my suggestion. I implemented it as a
> separate package purely so that I can build it more quickly, but I assume
> we???d want to fold this into src:sbuild eventually.
>
> The resulting
On Thu, May 18, 2017 at 11:39 PM, Michael Stapelberg
wrote:
> Sorry for the late reply.
>
> On Tue, Apr 11, 2017 at 10:39 AM, Johannes Schauer
> wrote:
>
>> Hi,
>>
>> Quoting Michael Stapelberg (2017-04-08 11:28:12)
>> > One area where sbuild sorely
Sorry for the late reply.
On Tue, Apr 11, 2017 at 10:39 AM, Johannes Schauer wrote:
> Hi,
>
> Quoting Michael Stapelberg (2017-04-08 11:28:12)
> > One area where sbuild sorely lacks is configuration, though: pbuilder is
> very
> > easy to set up, whereas sbuild requires
Hi,
Quoting Michael Stapelberg (2017-04-08 11:28:12)
> One area where sbuild sorely lacks is configuration, though: pbuilder is very
> easy to set up, whereas sbuild requires reading through
> https://wiki.debian.org/sbuild, performing a bunch of steps, only to end up
> with a setup which works
Package: sbuild
Version: 0.73.0-4
Severity: wishlist
I’ve been using sbuild instead of pbuilder for a few years now, and I
generally like it: it seems almost universally better than pbuilder.
One area where sbuild sorely lacks is configuration, though: pbuilder
is very easy to set up, whereas
33 matches
Mail list logo