=== jamesh_ is now known as jamesh === stokachu_ is now known as stokachu === michagogo_ is now known as michagogo === Elimin8r is now known as Elimin8er [07:52] Laney, can you please update src:agda? it can't build with new haskell stack [07:52] should be trivial to do [07:57] otherwise I can do it, with some permission [08:17] I think I did the work [08:24] Hallo zusammen === maclin1 is now known as maclin === doko_ is now known as doko === NCommander is now known as mcasadevall === mcasadevall is now known as NCommander [12:25] infinity: now tracking as https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1702679, and reported upstream binutils for now [12:25] Launchpad bug 1702679 in binutils (Ubuntu) "binutils fails to build glibc-2.24 on aarch64-linux-gnu and arm-linux-gnueabihf" [High,Confirmed] [12:41] jbicha, cyphermox_ looks like there is a genuine netplan regression with 1.8 network manager [12:42] i will try to look into that, as I want 1.8 network manager to migrate [12:42] it's tasty [12:42] xnox, slangasek was looking at it a bit, unsure if you synced up with him (just mentioning to avoid work duplication) [12:42] seb128, oh ok. nope, i'm in parallel to slangasek. [12:42] k [12:43] well he said he was having issues to set up an env to work on the problem but that he would try a bit more [12:43] that was yesterday [12:43] so unsure how much he did [12:44] ack. [12:45] cause i have resolved+nm+vpn bug to fix, and i think it would be nicer to fix it on top of v1.8 /after/ that migrates. [12:45] to not coflate the upgrade. [12:45] right, we would like n-m to migrate as well [12:46] I discussed the issue with cyphermox before he was off, he said he would look at it but didn't manage to do that before being on vac [13:05] dh: unable to load addon systemd: Can't locate Debian/Debhelper/Sequence/systemd.pm in @INC (you may need to install the Debian::Debhelper::Sequence::systemd module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl [13:05] /usr/lib/x86_64-linux-gnu/perl-base .) at (eval 15) line 2. [13:05] Something changed from Xenial to Yakkety that makes this go away. ISTR something about this, but I don't see any different rdeps on dh-systemd. [13:05] Any pointers please? [13:20] Ah. [13:20] /usr/share/perl5/Debian/Debhelper/Sequence/systemd.pm moved to the debhelper package itself, and dh-systemd is now transitional. [13:22] So for a backportable package, I guess I want "Build-Depends: debhelper (>= 9.20160709) | dh-systemd". [13:23] Of course I need debhelper anyway, so would something like "Build-Depends: debhelper (>= 9.20160709) | [13:23] dh-systemd, debhelper (>= 9)" be acceptable? [13:26] That sounds about right to me [13:27] Thanks! [13:28] Of course, if you don't need backportability to older debhelpers, you could just use debhelper (>= 9.20160709) [13:28] I need backportability to Xenial, which only has debhelper 9.20160115ubuntu3 [13:29] OK. I wonder if the Depends should include a ~ in the version for backporting needs, not sure why there is none in dh-systemd [13:30] If you mean "Build-Depends: debhelper (>= 9.20160709~) | dh-systemd, debhelper (>= 9~)" then yeah I could do that. [13:31] I don't think the ~ in 9.20160709~ is really needed because falling back to dh-systemd in that case should always work, but might as well use debhelper in that case then I guess. [13:34] I guess it's no problem anymore because dh backports are now higher-versioned anyway [14:53] xnox: I have not had much success reproducing that nplan failure however, because it's masked for me by lots of other failures [14:53] slangasek, ack, ok. I assume i can take a stab at that. [14:54] slangasek, btw the "split-dns-networkmanager-bug-not-work-right-with-vpn" is a bug in NM which missconfigures all of its dns backends. === NCommander is now known as mcasadevall [15:59] infinity: https://sourceware.org/bugzilla/show_bug.cgi?id=21725 now has one additional update. could you have a look? but this one is for arm64 only [15:59] sourceware.org bug 21725 in binutils "[2.29 Regression] binutils fails to build glibc-2.24 on aarch64-linux-gnu and arm-linux-gnueabihf" [Normal,New] [16:03] doko: That will certainly be an issue on arm64 (and maybe the only one there), but definitely not the same bit in the armhf log. :/ [17:03] infinity: please backport e9177fba13549a8e2a6232f46080e5c6d3e467b1 as well, fixes the build on arm64. I cannot see in the build log, if something else fails before [17:03] doko: Already done (it's haflway through the testsuite on rugby right now) [17:05] doko: If that turns out happy, I'll look into armhf after I get some more point release HWE stuff sorted. [17:40] doko: Confirmed arm64 happy, moving on to an armhf test build. === NCommander is now known as mcasadevall === NCommander is now known as mcasadevall [19:06] hm, do-release-upgrade is upgrading a xenial desktop to yakkety instead of zesty [19:06] I have "Prompt=normal" in /etc/update-manager/release-upgrades, not "lts" [19:07] ah [19:07] ok [19:07] have to go step by step [19:14] ahasenack: yeah, i think until yakkety goes eol (at least) [19:14] so once Y is eol, xenial can't be upgraded anymore until the next lts is out? [19:15] that thought never occurred to me before [19:15] ahasenack: no, i think X -> Z will be possible (iirc) [19:15] ahasenack: istr bdmurray mentioning this [19:15] there's old-releases too [19:16] sarnold: true === JanC is now known as Guest56451 === JanC_ is now known as JanC [20:08] jbicha, are you uploading qtbase yourself? I have already prepared my own upload to push… [20:09] oh, you already uploaded it :) [20:10] fine then [20:10] mitya57: were you planning to fix other stuff in your upload? [20:10] I saw your bug and prepared a merge with Debian unstable. [20:10] Anyway we have the large Qt 5.9 transition in progress, so all fixes from Debian will sooner or later get into Artful. [20:11] did you want to backport those other patches for zesty? the only issue that bothered me was the one gtk filechooser crash [20:13] For zesty, no. [20:13] mitya57: ok, I'll do the zesty SRU once I verify the artful package works for me [20:13] Ok, thanks for taking care of it! [20:14] I guess it's up to you whether you want to push the 5.7 merge or just wait for 5.9 [20:15] I originally was going to ask you to do the upload but then I thought I've been annoyed by this bug for 6 months so maybe I can take care of it myself now :) [20:17] I will focus on 5.9 then. [20:17] * mitya57 still waits for reply to his message on ubuntu-devel@... [20:18] mitya57: thanks for pushing my change to git, I think next time I'll just ask you to do the upload then :) [20:18] Ok, no problem :) [20:18] I forgot about the vcs [20:18] I wonder how you noticed that I pushed it so quickly. [20:18] I was just looking now for a vcs so lucky timing