slangasekxnox: I feel like you might be the person to ask about stray dirmngr processes left hanging around in an image chroot after apt has been run00:14
xnoxslangasek, yeah....00:16
slangasekxnox: how can I fix this?00:16
xnoxpkill ?00:16
slangasekmmhmm :)00:16
xnoxon a more serious note, things should not be hitting the network, or trying to retrieve gpg keys.00:17
xnoxsoemthing somewhere calls gnupg and doesn't clean up. You don't mean that a simple "apt update" results in stray dirmngr?00:17
slangasekxnox: probably the apt-key call00:18
xnoxyes, apt-key would do it. one should not call apt-key.... and just ship key snippets (like ubuntu-keyring does)00:18
xnoxor are you adding/enabling PPAs with apt-key?00:18
xnox... and not using add-apt-repository?00:19
slangasekthis script *also* uses add-apt-repository00:19
slangaseklet me see if the apt-key stuff is superfluous00:19
xnoxif add-apt-repository results in stray dirmngr, i should fix that.00:19
-queuebot:#ubuntu-release- New: accepted qbs [amd64] (zesty-proposed) [1.7.0+dfsg-3]00:19
-queuebot:#ubuntu-release- New: accepted qbs [armhf] (zesty-proposed) [1.7.0+dfsg-3]00:19
-queuebot:#ubuntu-release- New: accepted qbs [powerpc] (zesty-proposed) [1.7.0+dfsg-3]00:19
-queuebot:#ubuntu-release- New: accepted qbs [s390x] (zesty-proposed) [1.7.0+dfsg-3]00:19
-queuebot:#ubuntu-release- New: accepted qbs [arm64] (zesty-proposed) [1.7.0+dfsg-3]00:19
-queuebot:#ubuntu-release- New: accepted qbs [ppc64el] (zesty-proposed) [1.7.0+dfsg-3]00:19
-queuebot:#ubuntu-release- New: accepted qbs [i386] (zesty-proposed) [1.7.0+dfsg-3]00:19
slangasekhowever, there's also a cleanup phase here of 'sudo apt-key del ${ppa_key}'00:19
slangasekis that going to provoke dirmngr?00:19
xnoxthat should be safe.00:20
xnoxapt-key adv is not.00:20
slangasekthat does seem like a bug in apt-key, anyway00:21
xnoxthat it doesn't clean up dirmngr (or any other spawned agents) post-adv command? (which are actually passthrough to gpg command, which now started to spawn garbage)00:22
slangasekapt-key appears to run with a temporary GNUPGHOME dir00:23
slangasekand anything spawned that references that dir is lost00:23
slangasekand add-apt-repository adds the ppa, but packages from that ppa are listed as unauthenticated00:24
xnoxslangasek, $ gpgconf --list-components | sed 's/:.*//' | xargs -L1 gpgconf --kill00:24
xnoxprobably slightly better (e.g. don't try to kill gpg "component") is needed.00:25
xnoxadd-apt-repository should have been fetching a key =/ iff it can access things (do you need proxy to access ubuntu keyserver?!)00:25
slangasekxnox: but doesn't that require the matching GNUPGHOME, so gpgconf can see which of the running processes is its?00:26
xnoxsure it does, hence it should be in the apt-key cleanup.00:26
xnox(as in apt-key itself should be doing that)00:26
xnoxwhich btw is just a fancy pkill00:27
slangasekso we agree it's an apt-key bug00:27
xnoxbut i thought that add-apt-repository did the right thing (tm)00:27
xnoxso possibly two bugs.00:27
* slangasek nods00:27
slangasekxnox: add-apt-repository doesn't know to fetch ppa keys for a private ppa :P00:33
xnoxoh, you want that00:34
slangasekwell, all things considered, I really do not00:34
slangasekbut I currently have00:34
xnoxslangasek, use curl to fetch private ppa key off keyserver and pipe it into a file.00:34
slangasekalternatively, I can batch-copy things out of the private to a public one because thbt00:35
xnoxslangasek, or you can specify [trusted=yes] on the ppa entry you are using.00:37
xnoxgiven you delete the key afterwards anyway... and building in secure environment anyway....00:37
xnoxand forget about keys.00:37
slangasekxnox: same problem with add-apt-repository00:53
-queuebot:#ubuntu-release- Unapproved: lxc (xenial-proposed/main) [2.0.6-0ubuntu1~ubuntu16.04.1 => 2.0.6-0ubuntu1~ubuntu16.04.2] (ubuntu-server)00:54
xnoxkillall dirmngr sounds appropriate size of ikea hammer.00:54
slangasekExecuting: /tmp/tmp.DaevBURr1s/gpg.1.sh --keyserver keyserver.ubuntu.com --recv00:55
slangasekgpg: keybox '/tmp/tmp0_lqr33e/pubring.gpg' created00:55
slangasekroot      2600  0.0  0.0 175736  4088 ?        Ssl  16:51   0:00  \_ dirmngr --daemon --homedir /tmp/tmp0_lqr33e00:55
-queuebot:#ubuntu-release- Unapproved: lxc (yakkety-proposed/main) [2.0.6-0ubuntu1~ubuntu16.10.1 => 2.0.6-0ubuntu1~ubuntu16.10.2] (ubuntu-server)00:55
xnoxalso, i'm confused why gpg doesn't just kill dirmngr at the end of execution....00:55
slangasek                     root       4891 .rce. gpg-agent00:57
xnoxyeah that too00:57
xnoxapperantly gpg-agent is needed to store keys....00:58
stgraberwhy did they make such a mess with gpg2...00:58
* xnox was not kidding when i said pipe curl from keyserver into /etc/apt/trusted.gpg.d/foo.gpg file00:58
xnoxgpg2.1, i think gpg2.0 was still sane.00:58
stgraberit's really tempting to distro patch gpg to record what it auto-spawns and kill them all on exit, basically re-introducing good old gpg1 behavior (except it used to do everything in-process)00:59
stgrabernot if you have them listen on a per-process temp path :)01:00
xnoxone can spawn to /usr/bin/gpg which are waiting on results from e.g. the same dirmgr01:00
xnoxi think upstream rejected systemd socket activation =)01:00
-queuebot:#ubuntu-release- Unapproved: systemd (trusty-proposed/main) [204-5ubuntu20.20 => 204-5ubuntu20.21] (core)06:46
LocutusOfBorgnovaclient.exceptions.OverLimit: Quota exceeded for ram: Requested 8192, but already used 48640 of 51200 ram (HTTP 413) (Request-ID: req-ecaa7c79-5e1f-4106-8b3f-7664a086b1cf)10:00
LocutusOfBorgERROR (OverLimit): Quota exceeded for ram: Requested 8192, but already used 48640 of 51200 ram (HTTP 413) (Request-ID: req-ecaa7c79-5e1f-4106-8b3f-7664a086b1cf)10:00
LocutusOfBorgLaney, ^^ seems that retrying poppler autopkgtestsuite against libreoffice fails on i38610:00
LocutusOfBorgI would like to finish that poppler stuff :/10:00
* LocutusOfBorg leaves10:03
LocutusOfBorgrmadison -u ubuntu cups-ipp-utils10:05
LocutusOfBorguniverse ^^10:05
LocutusOfBorgdoko, promote to main and unblock cups?10:05
LaneyIt'll retry itself10:05
LocutusOfBorgcups-filters-core-drivers/* unsatisfiable Depends: cups-ipp-utils10:06
Laneylibreoffice wants a large instance10:06
LocutusOfBorgthanks Laney :)10:06
LocutusOfBorgI'm already trying the reverse-dependencies10:06
LocutusOfBorgif the laptop battery resists, I'll also set up a ben file10:06
LocutusOfBorgcups needs a move to main of cups-ipp-utils anyway I guess10:07
LocutusOfBorgpoppler is already on ben10:09
-queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (yakkety-proposed) [2.0.6-0ubuntu1~ubuntu16.10.2]10:35
-queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (xenial-proposed) [2.0.6-0ubuntu1~ubuntu16.04.2]10:36
=== mardy_ is now known as mardy
-queuebot:#ubuntu-release- Unapproved: accepted sbuild-launchpad-chroot [source] (yakkety-proposed) [0.13.1ubuntu16.10.1]10:42
-queuebot:#ubuntu-release- Unapproved: accepted util-linux [sync] (yakkety-proposed) [2.28.2-1ubuntu1.1]10:58
-queuebot:#ubuntu-release- Unapproved: accepted util-linux [sync] (xenial-proposed) [2.27.1-6ubuntu3.2]11:02
ginggswould an ubuntu-archive admin remove python-sunpy and python3-sunpy 0.7.3-1 on armhf and arm64 from -proposed please? LP: #164315111:02
ubot5`Launchpad bug 1643151 in sunpy (Ubuntu) "Please remove sad pandas and friends" [Undecided,New] https://launchpad.net/bugs/164315111:02
-queuebot:#ubuntu-release- New source: bubblewrap (xenial-proposed/primary) [0.1.5-1~ubuntu16.04.1]14:54
barrytsimonq2: how did your revert test go?16:16
apwginggs, looking16:25
apwginggs, done16:27
mvocan someone please release snapd 2.20.1ubuntu1 for xenial and 2.20.1+16.10ubuntu2 for yakkety? verification is done. there is an autopkgtest failure on ppc64el but despite what the tracker says this is not a real regression because there was a hickup in a previous upload and that was responsible for this "passed on ppc64el" result16:56
-queuebot:#ubuntu-release- New binary: yaz [ppc64el] (zesty-proposed/universe) [5.19.2-0ubuntu1] (no packageset)17:02
-queuebot:#ubuntu-release- New binary: yaz [s390x] (zesty-proposed/universe) [5.19.2-0ubuntu1] (no packageset)17:04
-queuebot:#ubuntu-release- New binary: yaz [amd64] (zesty-proposed/universe) [5.19.2-0ubuntu1] (no packageset)17:05
-queuebot:#ubuntu-release- New binary: yaz [powerpc] (zesty-proposed/universe) [5.19.2-0ubuntu1] (no packageset)17:05
-queuebot:#ubuntu-release- New binary: yaz [arm64] (zesty-proposed/universe) [5.19.2-0ubuntu1] (no packageset)17:06
-queuebot:#ubuntu-release- New binary: yaz [armhf] (zesty-proposed/universe) [5.19.2-0ubuntu1] (no packageset)17:06
-queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (xenial-proposed) [1:16.04.5]17:08
-queuebot:#ubuntu-release- New binary: yaz [i386] (zesty-proposed/universe) [5.19.2-0ubuntu1] (no packageset)17:11
-queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (xenial-proposed) [1:16.04.21]18:08
-queuebot:#ubuntu-release- Unapproved: ubuntu-gnome-meta (xenial-proposed/universe) [0.58.1 => 0.58.2] (ubuntugnome)18:17
dmj_s76When are we expecting kernel 4.8 to land in the daily iso for 16.04.2?18:19
jbichabdmurray: if you can, please look at accepting ubuntu-gnome-meta 0.58.2 in to xenial-proposed so it's ready in time for 16.04.218:21
-queuebot:#ubuntu-release- Unapproved: accepted ubuntu-gnome-meta [source] (xenial-proposed) [0.58.2]18:39
jbichathank you!18:40
slangasekinfinity: ^^ 4.8 in xenial dailies? done?19:22
tkamppeterHi, I have synced cups-filters 1.13.2 from Debian to Zesty some days ago, why did it not make it from -proposed to the release?20:10
nacctkamppeter: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html says unsatisfiable depends cups-ipp-utils20:33
tkamppeternacc, why unsatisfiable depends on cups-ipp-utils? cups-ipp-utils is part of the cups source package which is in main.20:34
slangasekwhich means the binary needs promoting to main20:34
slangasek(done now)20:34
nacctkamppeter: yeah it was a mismatch http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed20:35
tkamppeterslangasek, thanks.20:35
tkamppeternacc, also thanks.20:35
nacctkamppeter: np20:36
-queuebot:#ubuntu-release- Unapproved: accepted graphviz [source] (xenial-proposed) [2.38.0-12ubuntu2.1]21:12
-queuebot:#ubuntu-release- Unapproved: accepted graphviz [source] (yakkety-proposed) [2.38.0-15ubuntu1.1]21:15
juliankI feel like we should let apt 1.2.18 enter xenial-updates now. While nobody verified 1592817 as fixed, there seem to be no new reports in it for -proposed (bdmurray). There's a ton of other bugs verified fixed, and it's really important to get this done now, as it apparently breaks upgrades to yakkety for some people. Most of this has been waiting since November's 1.2.16 upload, so it really is a bit older than overviews make you think :)21:17
juliankThere were some autopkgtest failures, but those are not regressions caused by apt since the last apt upload21:18
-queuebot:#ubuntu-release- Unapproved: accepted overlay-scrollbar [source] (xenial-proposed) []21:21
bdmurrayHow are the autopkgtest failures not regressions?21:21
-queuebot:#ubuntu-release- Unapproved: accepted overlay-scrollbar [source] (yakkety-proposed) []21:23
-queuebot:#ubuntu-release- Unapproved: accepted fcitx [source] (xenial-proposed) [1:]21:29
-queuebot:#ubuntu-release- Unapproved: accepted fcitx [source] (yakkety-proposed) [1:]21:32
-queuebot:#ubuntu-release- Unapproved: libseccomp (trusty-proposed/main) [2.2.3-2ubuntu1~ubuntu14.04.1 => 2.1.1-1ubuntu1~trusty3] (core)21:33
-queuebot:#ubuntu-release- Unapproved: accepted maas [source] (xenial-proposed) [2.1.3+bzr5573-0ubuntu1~16.04.1]21:35
juliankbdmurray: They happen in apport, autopkgtest, and sbuild; and if you look at the logs, already earlier (even with 1.2.15). I think all of them started as soon as yakkety opened.21:35
juliankIt would be a wise thing to fix them at some point, but I have not gotten around to that, and apparently nobody else either :/21:38
juliankapport actually started failing in August, at that point, the wily ddeb archive started showing signature errors in apt - without a change in apt.21:42
juliankThese tests will stop working even more once wily is dropped from the archive.21:42
juliankor well, that was the issue21:43
juliankthe ddebs were dropped at that time21:43
-queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (xenial-proposed) [0.122ubuntu8.8]21:45
jdstrandbdmurray: happy new year! I could you take a look at libseccomp on trusty in the unapproved queue?22:13
jdstrands/I could/could/22:13
jdstrandbdmurray: this is to address bug 165348722:13
ubot5`bug 1653487 in libseccomp (Ubuntu) "seccomp argument filtering not working on trusty" [High,In progress] https://launchpad.net/bugs/165348722:13
bdmurrayjdstrand: I was on a call, looking now23:03
bdmurrayjdstrand: its meant to supersede the existing upload?23:05
jdstrandbdmurray: yes. it includes everything that was in it23:06
bdmurrayjdstrand: I guess I meant you don't care if the other doesn't get released first?23:06
jdstrandbdmurray: do not release the other first (there is no point since this SRU is for snappy and the previous upload doesn't work with snappy amd64)23:08
jdstrandbdmurray: basically, this fixes the verification-failed of Tyler's upload23:08
bdmurrayjdstrand: got it23:09
jdstrandbdmurray: so reject Tyler's, and accept this one (which is Tyler's plus patches to fix the failure)23:09
bdmurrayfyi bug 1653487 has no trusty task23:11
ubot5`bug 1653487 in libseccomp (Ubuntu) "seccomp argument filtering not working on trusty amd64" [High,In progress] https://launchpad.net/bugs/165348723:11
jdstrandbdmurray: fixed23:12
-queuebot:#ubuntu-release- Unapproved: accepted libseccomp [source] (trusty-proposed) [2.1.1-1ubuntu1~trusty3]23:15
jdstrandbdmurray: thanks!23:15
bdmurrayjdstrand: I think there's something wrong with your "Send" button23:16
-queuebot:#ubuntu-release- Unapproved: accepted os-prober [source] (xenial-proposed) [1.70ubuntu3.2]23:23
-queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (xenial-proposed) [229-4ubuntu14]23:54

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!