[04:54] o/ can removed packages be SRU'd back into an already released ubuntu release? [04:54] cjwatson: ^ [04:55] https://launchpad.net/ubuntu/+source/openscad/+publishinghistory for context [07:46] anyone has anything to do with upstream mongodb? their ubuntu repo repo.mongodb.org makes very policy-outdated packages that don't work with systemd [07:47] (found out at work we were using that on a server, don't know why) [11:16] LtWorf: sorry, no, you'll have to report that with them. [11:16] LtWorf: they do have a public bug tracker (jira). [12:14] rbasak: was hoping someone had an account already [12:14] anyway i just wiped it and got the ubuntu one :) [12:16] LtWorf: I do have an account, but I won't put my name to a report without verifying it first, and that's much more work than for someone who already has confidence in a report to sign up. [12:17] ok [12:49] tsimonq2: if it's not too much effort, could you please rebase your add-lubuntu git-ubuntu branch onto current master? [12:49] That would include the CI fixes and we should be able to get CI passed then. [14:13] rbasak: Sure, but it wil end up being after you EOD. [14:14] tsimonq2: np, I can land it together. I've already started a one-off catchup from your list. [14:14] Uh [14:14] s/together/tomorrow/ [14:31] If I got to http://manpages.ubuntu.com/manpages/man1/systemd-resolve.1.html it automatically takes me to Xenial's man page. At somepoint will this change to bionic? [14:51] powersj: after 18.04.1 I'd suspect [14:58] powersj, i think the answer is never, unless you figure out the branch this thing is deployed from and make a merge proposal =/ [14:59] xnox: dpb1 and I found it [14:59] working through it [14:59] xnox: :) [15:11] tsimonq2: one thing I forgot to mention. We still consider the imported branches unstable - there will be a non-fast forwarding reimport/breakage of everything at some point in the future. [15:11] tsimonq2: currently we lose all MPs (landed or not) against the imported repositories when we do that. [15:19] Is that planned? [15:19] (Meaning, can you let me know when it happens?) [15:20] tsimonq2: yes it's planned, and we can pre-announce it [15:20] (not planned with a date yet, just planned) [15:20] We have a bunch of bugs we want to fix first [15:21] OK [15:21] Thanks. [15:22] https://bugs.launchpad.net/usd-importer/+bugs?field.tag=hash-abi-break [19:06] !dmb-ping [19:06] bdmurray, BenC, cyphermox, jbicha, micahg, rbasak, sil2100: DMB ping. [19:06] That needs updating :-/ [19:07] tsimonq2: ^ [19:12] Oh hi. [19:25] rbasak: I think you just need to do !dmb-ping is to update it [19:25] !dmb-ping is cyphermox, jbicha, micahg, rbasak, sil2100, slashd, tsimonq2: DMB ping. [19:25] "Your edit request has been forwarded to #ubuntu-ops" [19:26] Laney: thanks! [19:27] Normally I'd ping the others to let them know what I just did. I think I probably don't need to on this occasion :) [19:29] rbasak: just updated [19:29] Thanks! [19:29] Awesome, thanks! [19:29] (I did not do it, wxl did :-) [22:43] anyone know if it's possible to find out specific details from inside an autopkgtest run? [22:43] because nginx is failing for the searx autopkgtest, but the actual failing component is uwsgi [22:43] not nginx, and I can't see the uwsgi fail reason because the way systemctl handles it suppresses all error output unless you go and get it from `systemctl -l status uwsgi`