Devuan bug report logs - #450
autopkgtest: cannot build a testbed for LXC

version graph

Package: autopkgtest; Maintainer for autopkgtest is (unknown);

Reported by: Ryutaroh Matsumoto <>

Date: Sun, 10 May 2020 02:03:01 UTC

Severity: grave

Tags: debian

Found in version 5.10

Full log

Message #20 received at (full text, mbox, reply):

Received: (at 450) by; 10 May 2020 10:00:02 +0000
Return-Path: <>
Received: from []
	by with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Sun, 10 May 2020 10:00:02 +0000 (UTC)
Received: from ( [])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by (Postfix) with ESMTPS id 2BD01F60B9D
	for <>; Sun, 10 May 2020 11:56:03 +0200 (CEST)
Received: from apollo.hindleynet ([]
	by with smtp (Exim 4.84_2)
	(envelope-from <>)
	id 1jXigj-0006Ve-3F; Sun, 10 May 2020 10:56:01 +0100
Received: (nullmailer pid 32452 invoked by uid 1000);
	Sun, 10 May 2020 09:56:00 -0000
Date: Sun, 10 May 2020 10:56:00 +0100
From: Mark Hindley <>
To: Ryutaroh Matsumoto <>
Subject: Re: bug#450: autopkgtest: cannot build a testbed for LXC
Message-ID: <>
References: <>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
X-IMAPbase: 1220827534 0000000218
X-UID: 218
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=disabled
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
On Sun, May 10, 2020 at 06:23:10PM +0900, Ryutaroh Matsumoto wrote:
> Hi Mark, thanks again for your attention and response.
> >> If Devuan project has no intention/plan to deploy CI, then autpkgtest and debci can be simply banned...
> > I just think nobody has provided the necessary autopkgtest templates.
> > Are you able to prepare them? I am not aware that we have anybody on teh dev
> > team who actively uses lxc.
> I'm unsure, but at least I can try...


> Do you think someone in Devuan project has interest in CI and/or
> autopkgtest all packages?

We currently use for our package building. Sources
are in git. However, the vast majority of packages are used directly from Debian
by redirection. We only fork and compile sources that need modification. This is
significantly different from most (all?) other Debian derivatives.

> Automated continuous application of autopkgtest on all packages
> will sqeeze out unknown bugs in Devuan, but having a
> machine(s) running autopkgtest may be an obstacle.
> I am happily using Google Cloud Platform Compute Engine
> with 640MB RAM and 30GB storage costing absolutely no money,
> but I strongly doubt if 640MB RAM and 30GB storage are
> enough for continuous autopkgtest...

Yes, I doubt that too. I am certainly not aware of anybody looking at this, but
if you are interested in it and think that would benefit, do come and get
involved implementing it.



Send a report that this bug log contains spam.

Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

Devuan Bugs Owner <>.
Last modified: Wed May 5 22:14:07 2021;