Hi,
Quoting Dima Kogan (2023-03-02 07:00:13)
> >> Since apt only supports a single keyring file and directory, respectively,
> >> you can not use this option to pass multiple files and/or directories.
>
> I did see that note. But for most other stuff in /etc the main config
> lives in /etc/thing,
Hi.
Johannes Schauer Marin Rodrigues writes:
> It seems that /etc/apt/trusted.gpg is a historic relic and keys from it are
> removed by the postinst of debian-archive-keyring with the following code
> comment next to it:
>
> # remove keys from the trusted.gpg file as they are now shipped in frag
Hi,
Quoting Dima Kogan (2023-02-28 22:56:26)
> It's not actually that weird; I just wasn't looking at the error messages
> closely enough. The /etc/apt/sources.list has two repos:
>
> - main bookworm repo. Signed with the Debian keys
> - my repo. Signed with its own key
>
> If I "mmdebstrap --ke
Johannes Schauer Marin Rodrigues writes:
> The weirdest thing about your bug is that copying your key to
> /etc/apt/trusted.gpg.d/ makes it work for you because when you changed the
> location of Dir::Etc::TrustedParts it just pointed to a different directory.
> Apt should not treat keys differen
Hi,
Quoting Dima Kogan (2023-02-24 06:31:03)
> > I also think I found the source of your problem. I reproduced your issue
> > locally like this:
> >
> > sq key generate --userid "" --export juliet.key.pgp
> > sq key extract-cert --output juliet.cert.pgp juliet.key.pgp
> > apt-ftparchive release .
Johannes Schauer Marin Rodrigues writes:
> you were now able to reproduce the problem without mmdebstrap but with
> plain apt. This suggests that your problem is not an mmdebstrap
> problem.
OK. Good to know.
>> And I have another related question. I can workaround this by copying my keys
>> t
Hi,
Quoting Dima Kogan (2023-02-23 18:55:01)
> I just ran your script up to the "apt update", having the shell substitute $1
> <- "bookworm" and $2 <- "DIRECTORY_FOR_CHROOT", and adding my new repo:
>
> mkdir -p "$2/etc/apt" "$2/var/cache" "$2/var/lib"
> cat << END > "$2/apt.conf"
> Apt::Ar
Hi josch. Thanks for replying!
I just ran your script up to the "apt update", having the shell
substitute $1 <- "bookworm" and $2 <- "DIRECTORY_FOR_CHROOT", and adding
my new repo:
mkdir -p "$2/etc/apt" "$2/var/cache" "$2/var/lib"
cat << END > "$2/apt.conf"
Apt::Architecture "$(dpkg --print
Hi,
Quoting Dima Kogan (2023-02-23 00:45:37)
> This should work, but it doesn't. I used sysdig to confirm that
> something is indeed looking in $PWD/keys/ and something is indeed
> calling read() on the relevant key. I have also confirmed that if I copy
> my keys to /etc/apt/trusted.gpg.d/ then it
Package: mmdebstrap
Version: 1.3.1-2
Severity: normal
X-Debbugs-Cc: none, Dima Kogan
Hi. I'm using mmdebstrap to bootstrap an install that uses the normal
Debian repos AND my own repo. My repo is signed with a key that lives in
$PWD/keys/something.gpg. I pass --keyring=$PWD/keys as suggested in
10 matches
Mail list logo
