Hi,
Quick followup given new insights.
On Sun, Sep 24, 2023 at 05:51:47PM +0200, Helmut Grohne wrote:
> Hi Johannes,
>
> On Sun, Sep 24, 2023 at 10:27:37AM +0200, Johannes Schauer Marin Rodrigues
> wrote:
> > There is really not much magic. The core of it is to pass this to your
> > mmdebstrap
Hi Johannes,
On Sun, Sep 24, 2023 at 10:27:37AM +0200, Johannes Schauer Marin Rodrigues
wrote:
> There is really not much magic. The core of it is to pass this to your
> mmdebstrap or debvm-create invocation:
>
> --setup-hook='for f in /etc/apt/sources.list /etc/apt/sources.list.d/*
>
Hi,
On 24-09-2023 10:27, Johannes Schauer Marin Rodrigues wrote:
Is the apt configuration on
those systems set to something that is not the default and should be considered
as well?
How the unstable to testing migration runs work is that they have a
testing testbed (with apt pinning making
Hi,
Quoting Helmut Grohne (2023-09-23 20:18:21)
> Quoting Ian Jackson (2023-09-23 12:19:27)
> > To summarise that discussion: at that time the best available solution that
> > worked in ci.d.n seemed to be to write an ad-hoc script to run the tests in
> > qemu; three packes had done that, each
Hi Ian,
On Sat, Sep 23, 2023 at 11:19:27AM +0100, Ian Jackson wrote:
> To summarise that discussion: at that time the best available solution
> that worked in ci.d.n seemed to be to write an ad-hoc script to run
> the tests in qemu; three packes had done that, each separately, with
> complex
Hi Helmut and others.
Some time ago we had a conversation on debian-devel about how to make
autopkgtests that spawn multiple nodes and communicate between them,
eg for testing network protocols[1].
To summarise that discussion: at that time the best available solution
that worked in ci.d.n
6 matches
Mail list logo
