** No longer affects: gnupg (Ubuntu)
** No longer affects: gnupg (Ubuntu Bionic)
** No longer affects: gnupg2 (Ubuntu Bionic)
** No longer affects: gnupg2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in
** Changed in: apt-setup (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1754075
Title:
apt-setup uses apt-key but probably
** Changed in: apt-setup (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1754075
Title:
apt-setup uses apt-key but probably should not
** Bug watch removed: Debian Bug tracker #886473
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886473
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1754075
Title:
** Also affects: apt-setup (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851774
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnupg (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt-setup (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnupg2 (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
>From the apt side: The patch in #12 looks correct - we want people to
put the keys in trusted.gpg.d like this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1754075
Title:
** Also affects: gnupg (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gnupg2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: apt-setup (Ubuntu Bionic)
Importance: Undecided
Status: New
** Tags removed: rls-bb-incoming
--
You
** Tags added: id-5c4b9a39fe71d33a8db94ec3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1754075
Title:
apt-setup uses apt-key but probably should not anymore
Status in
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1754075
Title:
apt-setup uses apt-key but probably should not anymore
Status in apt-setup
I too used the workaround:
d-i preseed/late_command string \
in-target wget -q -O /etc/apt/trusted.gpg.d/repo_key.asc
http://our.repo/repo_key.asc ; \
We mirror the repositories we offer to our clients, so they can keep doing
their stuff in case the intarwebz is inaccessible. None of those
I've just been bitten by this bug while upgrading our business
PXE/preseed installations from Xenial to Bionic. We use an internal
private repository for company specific packages. I'm unable to get the
apt key installed with the preseed, so nothing works.
I'm going to attempt the workaround
Easy workaround which does not require another apt-setup.udeb:
d-i preseed/late_commandstring \
in-target wget -q -O /etc/apt/trusted.gpg.d/bla.asc
http://bla.de/bla.asc ; \
in-target sed -i '/keyword to uncomment specific line in file/s/^# *//'
/etc/apt/sources.list ;
I guess every sysadmin installing an agent-based configuration
management system via di will experience this problem, too. Funny how
there was no progress on this in half a year.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Any progress on this? This is a serious regression for us which makes
preseed substantially less functional in bionic...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
Of course only if they're inheriting special repositories this way. But
the bugs referenced here IMHO are showing lot's of examples representing
different reasons and ways to do this. ;-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hello again,
I don't really have an opinion if this should be solved by
- changing the priority of gnupg or gnupg2 (if that wasn't only another
unrelated side effect of the change described in Comment #7)
- adding a dependency to gnupg2 | gnupg to apt-setup-udeb if that would be
possible.
Hello,
Bug #1761030 indeed describes the same issues.
I've also a modified udeb in use, now. And it's working for me, but the
setup is almost the same.
d-i apt-setup/local0/source boolean false
d-i apt-setup/local0/key string
http://software.ubuntu.man-da.de/software/key.gpg
d-i
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnupg2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnupg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
Hello,
I have build locally an updated apt-setup.udeb with the patch from #12
and it works for me.
Installation of the rebuild udeb is a bit hacky via early_command:
d-i preseed/early_command string wget -q -O /tmp/apt-setup.udeb
http:///apt-setup-udeb_0.104ubuntu5_amd64.udeb; udpkg
-i
The attachment "replace_apt_key_add.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
On Monday, 9 April 2018 12:56:12 CEST Lars Kollstedt wrote:
[...]
> This patch should IMHO work, but I have no opportunity to test it without
> your help, since we're in udeb and testing preseed issues. ;-)
Hi again,
20 times looked at it and still overlooked one detail.
This must of course be
Hi,
by the way apt-key belongs to the package apt:
root@bionic-test:/home/kollstedt# apt-file search apt-key
[...]
apt: /usr/bin/apt-key
[...]
It is installed when the error occurs and is exitting with the error mentioned
above.
But
In apt-setup-0.104ubuntu5/generators/60local there is an call
$chroot $ROOT apt-key add "/tmp/key$i.pub"
which would be the origin of this message.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
Hi again,
switching to installation shell, and doing a
chroot /target
apt install gnupg2
exit
exit
allows me to complete the installation, when continuing with the
installation step preparing installation sources after this.
The /var/log/syslog from the installation system shows the following
Hi again,
on March 2nd we were already on 2.2.4-1ubuntu1 so there obviously was
something fixing this. Since the package already wasn't marked as
important this time.
On this time adding the keys still worked fine.
The last days it didn't on bionic.
Kind regards,
Lars
--
You received this
Hi,
looks like this has happened when changing the source of gnupg to gnupg2
with 2.2.4-1ubuntu1.
The old source
svn://anonscm.debian.org/pkg-gnupg/gnupg/trunk/
contains the Package as important.
The new source
https://anonscm.debian.org/git/pkg-gnupg/gnupg2.git
contains the Package as
Didn't want to throw out apt-setup.
** Package changed: gnupg (Ubuntu) => apt-setup (Ubuntu)
** Also affects: gnupg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg
apt-key complains about missing necessary gnupg or gnupg2 package.
** Package changed: apt-setup (Ubuntu) => gnupg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
32 matches
Mail list logo