[09:36] doko is #913626 only with s390x ? [09:41] ginggs: apparently yes [09:44] doko: thanks, i'll have a look [11:06] doko: i find it weird that r-cran-stringi and r-base are both in dependecy level 1 in the ubuntu tracker [12:24] didrocks, Could not open desktop-minimal from checkout of (any of): [12:24] destkop-minimal [12:24] desktop [12:24] didrocks, you need a faster keyboard =) [12:25] fixed [13:01] xnox, thanks [13:02] (for fixing the typo) [13:45] grrrrr, I will never be able to type desktop properly! [13:45] thx for fixing! [13:48] didrocks, time that we rename it to "bureau" ? [13:50] ogra: ofc! that's my followup commit [13:50] :) [13:50] ! [15:47] coreycb: so bug 1795424 is v-done correct? [15:47] bug 1795424 in nova (Ubuntu Bionic) "[SRU] queens stable releases" [High,Fix committed] https://launchpad.net/bugs/1795424 [15:54] bdmurray: yep, finally! [16:00] coreycb: Do you mind modifying the tags? === cshep is now known as platonical [16:29] bdmurray: done [17:09] coreycb: Any plans to fix cinder in disco? (see the autopkgtest failures) [17:09] infinity: taking a look [17:10] coreycb: Ta. [17:22] is this something that can be easily fixed in bileto, or should we really stop using it for disco onwards? [17:22] E: The repository 'http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu disco Release' does not have a Release file. [17:22] looks like all we need is one package in that ppa built for disco [17:23] ahasenack, that is fixable. [17:23] ahasenack, not built =) _copied_ [17:23] * xnox does that [17:23] yep, copied [17:25] are we both doing it? [17:25] I'm not [17:25] i have [17:25] =) [17:25] good [17:25] good [17:25] thanks [17:26] will be published eventually. [17:32] Better idea, the stable-phone-overlay stuff should all be torn out of bileto. [17:40] infinity, we thought we did. [17:41] infinity, i think it still is wired up to britney triggers, cause bileto triggers britney with that --extra-ppa or some such. [17:41] infinity, and sil is away to fix it =/ [17:55] stupid question I know, but what's the suggested/proposed timeline for a Py2 removal? [17:55] if there even is one (since that has a huge number of rdeps too) [18:32] Rejected: [18:32] libecpg-compat3-dbgsym_10.5-1build3_s390x.ddeb: Version older than that in the archive. 10.5-1build3 <= 11.1-1 [18:32] libecpg-compat3_10.5-1build3_s390x.deb: Version older than that in the archive. 10.5-1build3 <= 11.1-1 [18:32] libecpg-dev-dbgsym_10.5-1build3_s390x.ddeb: Version older than that in the archive. 10.5-1build3 <= 11.1-1 [18:32] [...] [18:32] so postres 10 and 11 are not co-buildable? [18:33] postgres even [18:34] there should be like an upload of 10 which drops the transitional packages, no? [19:12] doko: Once the transition is complete, it should just be removed. [19:12] doko: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913353 [19:12] Debian bug 913353 in ftp.debian.org "RM: postgresql-10 -- ROM; superseded by postgresql-11" [Normal,Open] [19:13] doko: Unfortunately, entangling psql and icu might make that fiddly. [20:17] bdmurray, thanks for fixing update-notifier, we (desktop) were looking at that earlier since we did the previous update that was blocked in proposed and we were about to upload https://www.irccloud.com/pastebin/WsNmykoB/ ... do you prefer your solution? L_aney also pointed out that update-manager went for ignore W503 and that it would be good to be using a consistent style between those projects [20:22] seb128: I don't really have a preference and being consistent would be sensible. [20:32] bdmurray, you are ok if I do the change from the pastebin then? [20:38] seb128: Yeah, that's fine by me. Maybe sending an email about 503 vs 504 would be good too. [20:44] bdmurray, where do you suggest sending it? [20:45] seb128: ubuntu-devel? [20:46] just to ask if as a project we have an opinion/preference? [20:47] If the goal is consistency then saying this one is preferred [20:49] k [21:03] doko: do you have any idea why calamares would be looking for a liboost-python tied to python 3.6? [21:03] (i ask you because you recently did a no change rebuilt of calamares, assumedly for that reason) [21:09] fwiw this is true also with the version in proposed, though i had no hope of that fixing things [21:21] wxl: i don't know about this package at all but a lot of packages have bad code to find the libboost_python soname :( [21:22] mwhudson: well it's been working. fwiw https://github.com/calamares/calamares [21:23] searching that for libboost i only return a cmake module which is i doubt what we're looking for [21:29] yeah the naming stucture of the soname at least hasn't changed since cosmic.. this couldn't in some way be a result of merged-usr could it? [21:30] doesn't seem like it would... [21:32] and i DO have libboost_python37.so.1.67.0. this does indeed suggest something amiss with calamares...... but then we did a no change rebuild already so color me confused [22:08] wxl: Try grabbing these packages locally real quick: https://launchpad.net/ubuntu/+source/boost1.67/1.67.0-10 [22:08] It could very well be an outdated boost1.67. [22:29] @tsimonq2: even though the same version's in proposed which i pulled down? [22:29] Error: "tsimonq2:" is not a valid command. [22:31] @@@@@@@wxl: Oh really? [22:31] Error: "@@@@@@wxl:" is not a valid command. [22:31] * tsimonq2 runs