Source: accountsservice
Version: 22.08.8-6
Severity: serious
Dear maintainers,
I recently started to upgrade hosts that are used by ci.debian.net to
bookworm. I do that architecture by architecture (i386, ppc64el and
s390x by now; riscv64 isn't a release architecture so it runs bookworm
since the
On Mon, 05 Aug 2024 at 00:43:06 +0100, Simon McVittie wrote:
> A sid lxc container in a bookworm VM (built with a-b-lxc from bookworm)
> doesn't currently start up at all for me
I reported that separately, as #1078165.
After resolving that by using autopkgtest(-virt-lxc) from
bookworm-backports,
Hi Simon,
On 07-08-2024 16:34, Simon McVittie wrote:
So I think that theory is consistent with why sid's accountsservice now
passes its autopkgtest when run in lxc on bookworm.
I confirm that on ci.d.n the test in unstable now passes on a bookworm
kernel on amd64, armel, armhf, i386 and ppc64
On Thu, 08 Aug 2024 at 08:28:04 +0200, Paul Gevers wrote:
> Hi Simon,
> > The test failure I saw under a-v-podman is concerning, but probably
> > ought to be a separate bug report - and probably non-RC, since Debian's
> > production infrastructure is currently based on a-v-lxc (and ideally
> > a-v-
Hi,
On 08-08-2024 09:16, Simon McVittie wrote:
Or qemu, now that that's fixed (although not in a released autopkgtest yet).
I also started to write that, but qemu we only have on amd64, because
most of our other host don't support hardware accelerated KVM. And the
per package preference is n
On Sat, 18 Mar 2023 at 07:17:34 +0100, Paul Gevers wrote:
> I ran the [accountsservice autopkgtest] (lxc backend, just
> like on ci.d.n) on my own laptop running bookworm and the test hangs
> like on the other architectures.
Some potentially interesting data points:
I can reproduce this (or somet
6 matches
Mail list logo
