=== not_phunyguy is now known as phunyguy === vicamo_ is now known as vicamo [07:35] rbasak: hi, is there any progress on fixing systemd -> udisk2 post install failure in armhf lxd autopkgtest runners? now seeing this impact tests on latest KDE framewworks [07:35] rbalint ^^^ I mean! [09:48] RikMills, i'm bisecting the regressions and will upload a package in much better shape today/tomorrow [10:12] rbalint: thank you === ricab is now known as ricab|lunch [12:27] doko, hi, are there built gcc-7 packages which are working on there own? it seems packages from ubuntu-toolchain-r/test are relying on later uploads [12:27] ah sorry, for 16.04/Xenial === Wryhder is now known as Lucas_Gray === ricab|lunch is now known as ricab [13:46] ricotz: no, but you edit debian/rules.defs and regenerate the control file [13:49] doko, I assume with_common_libs and with_common_pkgs are the important vars in this case? [13:49] yes [13:50] ricotz: but why would you need that? [13:51] doko, I am trying to build libreoffice (6.3 requires gcc 7) on xenial [13:52] and avoid interferences with newer commons libs [13:53] or is there still a chance that xenial will receive such a toolchain update? [13:53] like bionic getting gcc-8 [13:56] no, bionic was already released with gcc-8 [13:58] hmm I see [14:49] Hi mapreri, did you see my latest mail last night? [15:02] GunnarHj: I did, but I'm caught up in something else today [15:02] so it's there, in my inbox [15:10] mapreri: Ok, good. Let's talk when you have a minute. [15:20] I have a minute right now, but not much more [15:20] GunnarHj: i.e., bring your query ;) [15:22] mapreri: Not much of a query, really. Just hoping that you'll find the time to upload the backports based on current eoan. The reasoning is in the mail. [15:23] GunnarHj: aye, I think I will. Maybe tonight or tomorrow. [15:23] mapreri: Sounds great! See ya. [15:23] o/ [15:29] Laney: That black thing looks really interesting, I'm about to run it on python-apt [15:29] It's a shame there's no git-black which only formats the hunks you are changing [15:30] (Like clang-format does for C(++); what we use in apt to progressively fix formatting) [15:36] juliank: why you highlight me? [15:36] but thanks for pointing me to it, TIL :P [15:36] Laney: Wasn't it you who pointed me to it? [15:36] nope [15:36] then it was ahasenack? [15:37] * juliank is confused [15:37] what did I break? [15:37] * ahasenack reads [15:37] haha [15:37] _someone_ mentioned black to me at debconf in hacklab [15:38] tsimonq2: please could you change all the kde-l10n-* packages to b-d on python3 instead of python? [15:38] but who? [16:03] I tidied up a package's debian/patches/ directory and added a few other patches to resolve build issues. However, creating a debdiff from the *.dsc files that resulted from `debuild -S -d` is only creating a debdiff that sees my changes to the changelog, but none of my other patches. The only notable difference from my usual workflow that produces "correct" debdiffs is that I renamed some of the patches in debian/patches [16:03] and updated the series file accordingly. Does anyone have a suggestion for where I could begin troubleshooting this? [16:25] connor_k: did you make sure that quilt was fully popped before changing the patches in debian/patches/ and the series file? [16:26] I'm not quite sure how not doing so would give you exactly the behaviour you describe, but if you didn't do that then you'd certainly end up in trouble. [16:31] rbasak, aha! Thank you! I "started over" after backing up my changelog and debian/patches directory, did a quilt pop -a, and copied in my backed up changes and the debdiff certainly looks more correct [16:31] thank you very much :-) [16:31] connor_k: you're welcome! [17:09] rafaeldtinoco: Could you answer rbasak in bug 1810857? [17:09] bug 1810857 in cloud-utils (Ubuntu Disco) "Typo in cloud-guest-utils: "reserveration-id"" [Low,In progress] https://launchpad.net/bugs/1810857 [17:10] bdmurray: sure [19:01] infinity, stgraber, kees: TB meeting? [19:14] GunnarHj: looks like I also had to add -backports to the package, I didn't realize u.U [19:17] mapreri: Do you mean the first line in d/changelog? In that case I follow you. [19:38] mapreri: Ok, I see that it's in both the -proposed and -backports new queues. Then we have spread our bets, so to say. ;) [19:39] mapreri: Anyway, thanks! That will be easy to sort out. [19:41] bdmurray: Do you have time to remove a couple of uploads which ended up in the wrong pocket? [19:56] GunnarHj: Depending on what you mean, I'm not an AA. [20:01] bdmurray: Ah, I thought you were. It's ibus-avro, which was just uploaded to the xenial/bionic/disco new queues. It's intended for the -backports pocket, but was first uploaded by mistake to -proposed too. So if you have the necessary access, it would be great if you could delete them from -proposed. [20:01] GunnarHj, I can do that [20:01] seb128: Ah, nice! [20:03] GunnarHj, mapreri, bdmurray, done [20:03] seb128: Thanks! [20:06] seb128: well, you rejected everything :D [20:06] guess I'll re-upload the -bpo ones [20:07] I think seb128 needs some sleep. :) [20:08] alright, back afk! o/ [20:09] GunnarHj, mapreri, sorry, I didn't know backport was in the same queue, I though those were 2 buggy uploads [20:09] I see it's reupload so we should be good :) [20:10] seb128, mapreri: Right, now all is as it should be. Thanks!4 [23:39] doko: Don't quote me on this, but those are KDE 4 and should be nuked anyway. [23:40] * sarnold runs to wikiquote [23:44] sarnold: Why there when you can just remove them with 'tsimonq2 says these can be removed'? [23:44] Unit193: so it can be mirrored everywhere! [23:46] XD [23:46] Might as well send something to ubuntu-devel-discuss while we're at it. [23:49] My personal opinion is that we should have nuked all of Qt 4 anyway cycles ago. [23:56] But that kills so much stuff! [23:57] Like...Uh...Synergy? [23:59] Bah. :P [23:59] I'm kidding, barrier is a good replacement.