This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
As an 'fyi', newer versions of curtin now have dropped the specific hack for
dirmngr and gpg.
Instead they now use a pid namespace for all processes in the chroot.
This allows us to let the kernel kill off the delinquent processes when their
parent exits.
--
You received this bug notification
** Branch linked: lp:~raharper/curtin/merge-unshare-chroot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645680
Title:
apt feature broken on >=Yakkety due to new gpg agent
To manage notifications
** Branch linked: lp:~smoser/maas-images/trunk.use-unshare
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645680
Title:
apt feature broken on >=Yakkety due to new gpg agent
To manage notifications
** Branch linked: lp:~curtin-dev/curtin/yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645680
Title:
apt feature broken on >=Yakkety due to new gpg agent
To manage notifications about this
** Branch linked: lp:~curtin-dev/curtin/zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645680
Title:
apt feature broken on >=Yakkety due to new gpg agent
To manage notifications about this
This bug was fixed in the package curtin - 0.1.0~bzr437-0ubuntu1~16.10.1
---
curtin (0.1.0~bzr437-0ubuntu1~16.10.1) yakkety-proposed; urgency=medium
* debian/new-upstream-snapshot: change to not use bzr merge-upstream.
* New upstream snapshot.
- revert: Test Workaround: skip
This bug was fixed in the package curtin - 0.1.0~bzr437-0ubuntu1~16.04.1
---
curtin (0.1.0~bzr437-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
* debian/new-upstream-snapshot: change to not use bzr merge-upstream.
* New upstream snapshot.
- pep8: fix pep8 errors found
Hi,
I've verified this in yakkety using vmtest from curtin and some tools at
https://gist.github.com/smoser/4e25b5a9e6245692be90098464990d00
$ git clone https://gist.github.com/4e25b5a9e6245692be90098464990d00.git vtools
$ export PATH=$PWD/vtools:$PATH
$ bzr branch curtin trunk
$ cd trunk
$ bzr
previous comment should have said :
I've verified this in XENIAL using vmtest
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I've verified this in yakkety using vmtest from curtin and some tools at
https://gist.github.com/smoser/4e25b5a9e6245692be90098464990d00
$ git clone https://gist.github.com/4e25b5a9e6245692be90098464990d00.git vtools
$ export PATH=$PWD/vtools:$PATH
$ bzr branch curtin trunk
$ cd trunk
$ bzr
** Changed in: curtin
Status: Confirmed => Fix Committed
** Changed in: curtin (Ubuntu Xenial)
Status: Triaged => Fix Committed
** Tags removed: verification-needed
** Tags added: verification-needed-xenial verification-needed-yakkety
--
You received this bug notification because
Hello ChristianEhrhardt, or anyone else affected,
Accepted curtin into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr437-0ubuntu1~16.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this
** Description changed:
+ - Begin SRU Template -
+ [Impact]
+ The mechanism for adding PPAs during was prone to failure when installing
+ 16.10 (yakkety) or newer systems.
+
+ A curtin install of yakkety with the following configuration would
+ fail:
+ apt:
+ sources:
+ ignored1:
** Also affects: curtin (Ubuntu Zesty)
Importance: Undecided
Status: Fix Released
** Also affects: curtin (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: curtin (Ubuntu Xenial)
** Branch linked: lp:~smoser/ubuntu/xenial/curtin/pkg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645680
Title:
apt feature broken on >=Yakkety due to new gpg agent
To manage notifications
** Branch linked: lp:~smoser/ubuntu/xenial/curtin/pkg-sru-r437
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645680
Title:
apt feature broken on >=Yakkety due to new gpg agent
To manage
This bug was fixed in the package curtin - 0.1.0~bzr435-0ubuntu1
---
curtin (0.1.0~bzr435-0ubuntu1) zesty; urgency=medium
* New upstream snapshot.
- pep8: fix pep8 errors found with 'make pep8' on zesty.
- Workaround failures caused by gpg2 daemons left running in chroot.
** Branch linked: lp:curtin
** Branch linked: lp:~smoser/ubuntu/zesty/curtin/pkg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645680
Title:
apt feature broken on >=Yakkety due to new gpg agent
** Changed in: gnupg
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645680
Title:
apt feature broken on >=Yakkety due to new gpg agent
To manage notifications
** Branch linked: lp:~paelzer/curtin/curtin-bug-1645680-gpgagent
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645680
Title:
apt feature broken on >=Yakkety due to new gpg agent
To manage
** Changed in: gnupg
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645680
Title:
apt feature broken on >=Yakkety due to new gpg agent
To manage notifications about
I was able to track the spawning down to calls to gpg done from add-apt-
repository.
Simplified - that spawns one:
gpg --keyserver hkp://keyserver.ubuntu.com:80/ --recv
04450970750A7228C042CD4442C3EB37B6832E30
There already is our "oneshot" in the form of "--no-use-agent"
So that does not
We discussed alternatives and options and agreed that we first have to
file an upstream bug.
We should file a bug upstream and link it here.
Target is to understand if there is - or ever will be - something like a
--oneshot option to exit it immediately. Preferably also controlled by an
24 matches
Mail list logo
