On Wed, Feb 9, 2022 at 5:09 PM Adam D. Barratt wrote:
>
> On Wed, 2022-02-09 at 17:02 -0500, Jeffrey Walton wrote:
> > On Wed, Feb 9, 2022 at 4:48 PM Adam D. Barratt <
> > a...@adam-barratt.org.uk> wrote:
> > > ...
> > > I have to admit that I'm slightly confused as to why you're
> > > attempting
On Wed, 2022-02-09 at 17:02 -0500, Jeffrey Walton wrote:
> On Wed, Feb 9, 2022 at 4:48 PM Adam D. Barratt <
> a...@adam-barratt.org.uk> wrote:
> > ...
> > I have to admit that I'm slightly confused as to why you're
> > attempting
> > to use the ports archive to build an armhf chroot in any case, wh
On Wed, Feb 9, 2022 at 4:48 PM Adam D. Barratt wrote:
> ...
> I have to admit that I'm slightly confused as to why you're attempting
> to use the ports archive to build an armhf chroot in any case, when
> it's been in the main archive for over a decade now.
I'm trying to reproduce a bug from Debi
On Wed, 2022-02-09 at 16:26 -0500, Jeffrey Walton wrote:
> On Wed, Feb 9, 2022 at 4:00 PM Adam D. Barratt <
> a...@adam-barratt.org.uk> wrote:
> > On Wed, 2022-02-09 at 15:30 -0500, Jeffrey Walton wrote:
> > > Ah, the never ending problem of Debian keys... I'm trying to
> > > setup a
> > > Qemu Chr
Package: debian-archive-keyring
Version: 2021.1.1
X-Debbugs-CC: g...@debian.org
Tags: sid
Ah, the never ending problem of Debian keys... I'm trying to setup a
Qemu Chroot for testing Debian bug 1001995.
Key id E852514F5DF312F6 cannot be found in debian-archive-keyring, and
it cannot be found at h
5 matches
Mail list logo
