[01:57] juliank: Downside to Ubuntu's command-not-found is that it doesn't have update-command-not-found. :/ [05:11] rbasak: infinity: did we ever figure out the issue? (Yesterday was a crazy hellish day, I apparently was not straight-thinking on a regular basis...) [08:00] niedbalski: see question by bdmurray above - and if possible ack in the bug so the SRU Team sees it [08:38] teward: I think LocutusOfBorg pointed out what to cherry-pick from a different package to you or something? [08:39] yes === mardy_ is now known as mardy [08:39] on the bug report, I uploaded the patch in my ppa [08:40] btw completely not a luajit fault [08:40] and please don't force me to look at that hell again [08:52] cpaelzer: rbasak: hey! I have a small question for you: how do we request some packages to get autoimported in your git machinery? and how long will it take to get the first import done? I have 3 potential packages which can help us on our new community theme effort (only autoimport, we won't push to them yet as we discussed during the Rally) [09:11] didrocks: https://git.launchpad.net/usd-importer/tree/gitubuntu/source-package-whitelist.txt [09:12] didrocks: this should mostly be it for the sense of auto-importing [09:12] cpaelzer: excellent, let me do a MP against it [09:12] didrocks: but nacc / rbasak work on getting everything imported so a lot of things might (have) change [09:12] for now that should be it AFAIK [09:13] yeah worst case it is a simple MP and you'll get told in the review of it [09:13] how long is the first import taking approx, once this is merged? (so that I can give some timeline for the community) [09:13] didrocks: would a single manual import help you? [09:13] doing immediately :) [09:13] yes! [09:13] just to get them started [09:13] let me take a look then at a manual import [09:13] ah, excellent :) [09:13] didrocks: list of packages? [09:14] cpaelzer: gnome-shell, gtk+3.0, gnome-themes-standard [09:17] didrocks: all three imports are running - no commit ment on duration or success chance [09:17] didrocks: will let you know [09:17] cpaelzer: haha, no worry, thanks a lot! :) [09:22] didrocks: gz to your spotlight btw! [09:25] cpaelzer: thanks ;) [09:46] didrocks: sorry - had to abort for a shrotage on storage, but looked good so far - rerun after some cleanup [09:47] cpaelzer: thx for keeping me posted (and good luck!) [09:48] cpaelzer: thanks :) [09:49] didrocks: please note that we expect to rebase the world still. [09:50] rbasak: yeah, not a biggie, I just need a way for the community to git clone and get easily the current content from ubuntu, they won't branch from it [09:56] OK great. The whitelist should be sufficient for that I think. [10:33] Unit193: Well, if we merge it would have both the static db and update-command-not-found :D [10:35] I'm not sure if the local one should take precedent or if they should be merged somehow [10:35] u-c-n-f is far less effective than the ones shipped in the package. [10:36] like, no alternatives === led_ir23 is now known as led_ir22 [10:50] ginggs: the autopkg test are far by complete, but could you have a look at the ones triggered by gdal? [11:00] cpaelzer, rbasak: rdma-core now builds libibverbs*, which wants to promote to main. server team was subcribed to it. please can you file a MIR for that? [11:03] I was following rdma-core for dpdk reasons [11:03] yes I can file the MIR [11:04] did id now complete in Debian? [11:04] rdma-core is in universe though? [11:04] IIRC on wednesday it wasn't [11:04] rbasak: it is meant to replace libibverbs1 (and many more) [11:04] which is in main [11:04] Ah [11:04] transition from many (MANY++) sources to one source [11:05] which means many source pkg -> rdma-core [11:05] I see [11:05] doko: let me just infishe the debdiff here and then I'll file one [11:06] doko: i will look [11:07] Looks like it's pulled in by libvirt, ceph and boost. [11:08] Also tgt [11:26] doko: rbasak: filed 1732892 [11:26] doko: it is a bit of a special case as it is a reorg of the source packages - so for all in main before this is kind of clear but as the source now contains more ... [11:26] e.g. the security POV on the case might be different now [11:26] anyway the bug to process it now exists - thanks for the ping doko [11:28] didrocks: gnome-themes-standard complete (https://code.launchpad.net/~usd-import-team/ubuntu/+source/gnome-themes-standard/+git/gnome-themes-standard), others still running [12:34] rbasak: one more thing ... who could look at the postgresql-10 triggered autopkg test failures? [12:35] citus, postgresql-plproxy, psqlodbc [12:37] doko, some of these were due to out-of-date postgresql-common and just need retry with like all-proposed. let me double check things. [12:38] doko, the thing to grep is "supported-versions: WARNING: Unknown Ubuntu release: 18.04" [12:38] you can trigger with just pg-common from proposed if it's that [12:39] citrus pg-repack postgresql-plproxy psqlodbc look retriable [12:40] pglogical looks like a perl/postgresql regression? [12:43] Laney, hmmmm imho pglogical/armhf should be bad tested.... it is always failed everywhere else. [12:43] didrocks: gnome-shell complete as well, one more to go ... [13:42] doko: these look good now http://autopkgtest.ubuntu.com/packages/p/pdal/bionic/armhf http://autopkgtest.ubuntu.com/packages/o/otb/bionic/armhf [13:55] ginggs: nice, thanks [13:55] sil2100, hey, I've noticed that ubuntu-image is pulled when installing livecd-rootfs now, why is that? It clobbers ubuntu-image from the snap [15:37] cpaelzer: which version of the snap did you use to import (thi sis important) [15:42] cpaelzer: seems gtk+3.0 is taking a lot more time (just checked and not here yet), thanks a lot for the 2 others! I will use that opportunity to get familiar with the repo layout as well === zyga-ubuntu is now known as zyga-afk [17:08] cpaelzer: did you a skip-applied import? [17:08] cpaelzer: also, i guess i didn't tell you this before, but please update the whitelist ifyou manually import packages [17:08] cpaelzer: otherwiset the repo will immediately fall out of date [17:41] is AWS image naming convention ducumented anywhere? [17:54] There's https://bugs.launchpad.net/cloud-images/+bug/1458825 (opened by me, over two years ago). [17:54] Launchpad bug 1458825 in cloud-images "Please explain "root store" terms (hvm-io1, hvm, ...)" [Undecided,New] [17:58] BlessJah: Faux: wrong channel? [17:58] probably want #ubuntu-server [17:59] I was replying to BlessJah. [17:59] Oh my, you saw that. [17:59] * Faux -> coffee. [17:59] Faux: :) [18:07] juliank: But if someone adds an external repo with working contents, Debian gets them whereas Ubuntu won't. [18:14] nacc: you're right, thanks [18:15] Unit193: Yes, that's why I'd want to merge that stuff [18:16] Faux: I'll try to get answer on #ubuntu-server [18:18] Thanks for that. [18:43] mardy: Hi, do you know if cordova-ubuntu is still a living thing, or can be removed from archive? The latest commit in https://github.com/apache/cordova-ubuntu was >1 year ago. [18:43] I am asking because it is the only reverse dependency of qtsystems-opensource-src, which I would like to remove. [18:44] mitya57: there are repos in github, let me check if they have seen some activity lately... [18:47] mitya57: yep, last commit is from 1 year ago there too, so my guess is that you can remove them; I didn't contribute much to them so I'm not 100% sure whether anyone is still using them, but given that they are unmaintained... [18:49] mardy: thanks for confirmation! You were the only one of last committers whom I found on IRC ;) [18:50] mitya57: yep. BTW, any plans for QtPim? I recently updated it to the latest git, the patch delta is considerably smaller now: https://github.com/ubports/qtpim-opensource-src-packaging/pull/1/commits/c41708bcde351ebbdd7d3e4fedbc4d48c399d24b [18:56] mardy: its rdeps are cordova-ubuntu-3.4 and messaging-framework. If the former is removed and the latter is compatible with the new version, then it makes sense to update it to Ubuntu. [18:56] mitya57: kde is not using it? [18:56] they are probably using some stuff of their own [18:57] According to reverse-depends, they are not using it. [18:57] ok [18:57] mardy: Let's wait for the current Qt transition to migrate, then I'll maybe take your packaging and upload it. [19:48] Faux: could you join #ubuntu-server to discuss you bug report? [20:04] cyphermox: doko: i'm about to be out on vacatio, and am a bit hesitant anyways to process a MIR I filed; LP: #1687454. Is it possible one of you can look so we can get that in this cycle? I think based upon c#2, it should be approved since we have the security ack? [20:04] Launchpad bug 1687454 in nghttp2 (Ubuntu) "[MIR] nghttp2" [Undecided,New] https://launchpad.net/bugs/1687454 [20:05] dpb1: --^ if you could help keep track of that [20:06] nacc: yes I'll review it [20:07] cyphermox: thanks! [20:11] nacc: will do. [20:11] dpb1: thanks [20:12] dpb1: anyone on the squad should be able to cherry-pick the necessary change from the history (as I uploaded a version with the depenency changed during the last cycle) and upload it (or request it be sponsored) [20:13] dpb1: necessary change = build mod_http2 for apache2, if MIR is approved [20:15] cpaelzer: fwiw, i would really rather folks not use skip-applied except when testing the importer (purely for speed of import). If you are pushing to the repo, no special options should be passed (unless there is a very good reason, e.g. patches-applied fails) === zyga-afk is now known as zyga [21:13] cpaelzer, bdmurray I think you can proceed with the SRU. [21:14] niedbalski: which one was that again? [21:15] niedbalski: And how much confidence do you have in "I think" [21:15] bdmurray, cpaelzer I am seeing a problem on the upgrade with virtlogd not being properly started after upgrade, but the problem isn't reproducible with exception of this particular environment. [21:15] so I can't hold this because of a single case. === wendar_ is now known as wendar