[10:58] <cpaelzer> hi, I was wondering to land a lib and a dependent together what the right steps are
[10:59] <cpaelzer> in my case the lib is a sync from Debian and the dependent package would be a no-change rebuild to pick up the change
[10:59] <cpaelzer> I know bileto can be used for such transitions, but I was wondereing if syncpackage ... --no-lp and then into bileto ppa would be ok given the amount of warnings about --no-lp in man syncpackage
[11:03] <rbasak> cpaelzer: to copy straight into a PPA, you can use copypackage instead, from ubuntu-archive-tools.
[11:03] <Odd_Bloke> If a core dev has a minute to review https://code.launchpad.net/~tribaal/livecd-rootfs/fix-ova-manifest/+merge/314682 it would be much appreciated.
[11:03] <rbasak> cpaelzer: I've never used copypackage to source from Debian, but I presume that's possible.
[11:04] <rbasak> cpaelzer: you don't need to use bileto though unless you want to. It's fine to syncpackage, and then upload a no-change rebuild for the dependent once the sync has built. It'll be stuck in proposed until it's all done, but that's the point of proposed so it's fine.
[11:04] <Odd_Bloke> (There's also https://code.launchpad.net/~tribaal/livecd-rootfs/fix-ubuntu-ovf-attributes/+merge/314702 but the diff there is a bit chunkier.)
[11:04] <Tribaal> not *much* chunkier though :)
[11:05] <rbasak> cpaelzer: no point in uploading the no-change rebuild early though - it'll rebuild without the update, so that's pointless. Have to wait until the synced package is built and the binary published.
[11:05] <Tribaal> thanks Odd_Bloke
[11:05] <rbasak> cpaelzer: it's copy-package, sorry.
[11:09] <cpaelzer> rbasak: thanks
[11:11] <tumbleweed> `/win 35
[11:11] <cpaelzer> rbasak: and I just see - other than with dput these days for syncpackage you still have to call it $release-proposed instead of just the release name right?
[11:12] <rbasak> cpaelzer: I'm not sure. Doing so would do no harm. But why would you use copypackage to copy into a -proposed pocket in this case?
[11:16] <cpaelzer> rbasak: no syncpackage
[11:16] <cpaelzer> rbasak: like "syncpackage --release=zesty-proposed --debian-version=16.11-1 --bug=1539775 --force --verbose dpdk"
[11:21] <cpaelzer> tumbleweed: http://hpoussineau.free.fr/qemu/arc20081202-nt350-4.png that is :-)
[11:21] <rbasak> Ah.
[11:21] <rbasak> I believe zesty-proposed is implied.
[11:22] <rbasak> I've never used --release
[11:22] <cpaelzer> I think current-release is the default according to the doc
[11:22] <Laney> Yes, and it'll take the latest available version by default too
[11:22] <cpaelzer> let check if it implies -proposed, because with --release=zesty it told me that I don't have permissions to do so
[11:25] <cpaelzer> thanks everone, worked as it should now
[11:25] <rbasak> I'm pretty sure it must imply -proposed, because it's succeeded and done the right thing for me in the past.
[11:26] <tumbleweed> cpaelzer: :P
[12:54] <cpaelzer> rbasak: dpdk sync worked just fine and I waited till the build said pblished in proposed >30 minutes ago. Yet the subsequent rebuild of openvswitch still pulled in the older version :-/
[12:55] <rbasak> cpaelzer: are you sure it was the binaries that were published rather than just the source?
[12:55] <cpaelzer> rbasak: the solution is easy - upload another no-change, but I really want to avoid proliferating the numbers due to that - what is the hard check to go for if it is ready to pull the new package version
[12:55] <cpaelzer> hmm checking
[12:56] <rbasak> cpaelzer: the binaries aren't published - they're held in NEW.
[12:57] <cpaelzer> harr, that got me - thanks for helping me to find the reason
[12:57] <cpaelzer> yes it has a few new packages as the dpdk zoo of sublibraries grew
[12:58] <rbasak> cpaelzer: you're welcome. On https://launchpad.net/ubuntu/+source/dpdk/16.11-1, it says "(New)" against the builds. IIRC it also tells you there when they are pending publication, but I'm not sure.
[12:58] <cpaelzer> rbasak: it does tell me there, I was wrongly checking published and build on https://launchpad.net/ubuntu/+source/dpdk/16.11-1
[12:59] <cpaelzer> but that only was source + build as you assumed
[12:59] <cpaelzer> I can't see binary publsihed (or not) on that page
[13:00] <cpaelzer> https://launchpad.net/ubuntu/+source/dpdk when you flip open the release thing tells me pending publication
[13:01] <cpaelzer> well you can see it - by not seing anything - under the binaries list on https://launchpad.net/ubuntu/+source/dpdk/16.11-1
[13:02] <cpaelzer> That said the pending publication down there could be useful
[13:02] <cpaelzer> I might file an LP bug for that
[13:11] <cpaelzer> ok, I have abug for it now
[13:11] <cpaelzer> thanks rbasak to help my finding my misassumption
[13:27] <coreycb> infinity: hi, any chance you could upload 0.158 of ubuntu-dev-tools to debian?
[16:05] <Saviq> wgrant, hey, is there a bug# for the arm64 builders kernel issue? I'm afraid we're encountering the same in our CI, trying to enable arm64 there...
[16:37] <doko> tjaalton: when do you plan to build mesa with llvm 3.9 in the stable releases?
[16:41] <tjaalton> doko: only mesa 13 backport will
[16:41] <tjaalton> not the currently SRU'd 12.0.x
[16:42] <tjaalton> because there were some issues with it, though it was easy to get it build with 3.9
[16:42] <tjaalton> mesa 13 is the first one that properly supports 3.9
[17:12] <tjaalton> should requestbackport work on xenial?
[17:12] <tjaalton> lazr.restfulclient.errors.BadRequest: HTTP Error 400: Bad Request
[17:26] <dmj_s76> jbicha: So I want to fix a number of bugs by adding hidpi support to Humanity.  Should I branch from lp:humanity or lp:~ubuntu-art-pkg/humanity/release ?
[17:29] <dmj_s76> I'm assuming the latter since that's where commits have been lately.
[17:47] <dobey> i almost never say that anything needs "hidpi" support, but man, does the steam overlay stuff seriously need some improvement there
[18:06] <dmj_s76> dobey: hmm...details?
[18:12] <dobey> dmj_s76: i mean i like small icons/text normally. but when playing games at 4K and then i open the steam overlay, everything is even tinier than it normally is in the steam client. the notifications for achievements are especially annoying, because they're super tiny and stuck hard to the far upper right corner. those would be much better if they ended up like standard notifications in ubuntu
[18:13] <dmj_s76> dobey: Maybe this needs reporting to Valve.
[18:13] <dobey> probably yeah
[18:14] <dobey> i know you can't do anything about it. was just trolling a bit because everyone thinks my normal font size is tiny
[18:14] <dmj_s76> In this case Humanity icons not supporting @2x is a problem, causing the wrong icons to be shown and graphical bugs in Ubiquity.
[18:15] <dobey> @2x?
[18:15] <udevbot> Error: "2x?" is not a valid command.
[18:15] <dobey> err, thanks bot
[18:16] <dobey> i thought that was an apple thing
[18:17] <dmj_s76> How you signal GTK, etc to use the normal icon and scale up rather than picking the bigger one (which can be the wrong metaphor) eg, "scale up the 24 px icon, not use the 48px icon"
[18:18] <dmj_s76> It's a Linux thing too.
[18:19] <dobey> i know gtk+ has that scaling thing; i didn't realize it was doing dumb things with icons like appending @2x to the size
[18:20] <dmj_s76> well, you basically just need @2x symlinks to the correct folders
[18:20] <dmj_s76> and an update to the index.theme
[19:51] <jackpot51> Is there a maintainer for the wpa source package?
[19:51] <jackpot51> It just says "Ubuntu Developers"
[19:53] <sarnold> jackpot51: the changelog lists a wide variety of folks https://launchpad.net/ubuntu/+source/wpa/+changelog
[19:55] <jackpot51> That is unfortunate. pitti: Since you did a change for the wpa_supplicant.service, would you talk to me about my changes?
[19:56] <sarnold> pitti's moved to another employer in the meantime, it might be a while before he has time to review something not for new work
[19:56] <rbasak> jackpot51: all packages in Ubuntu are team maintained. There are no individual maintainers.
[19:57] <rbasak> jackpot51: if you need to talk to people about a proposed change, then you can do it here, on the mailing list, or in a bug. And any person (subject to appropriate permissions on that package) can upload any change.
[19:57] <jackpot51> the problem is that systemctl isolate kills wpa_supplicant.service
[19:58] <jackpot51> This is easily seen where it is used in the OEM installer - wifi connections are lost after oem-config finishes
[19:58] <sarnold> isn't that the intention of isolate?
[19:59] <jackpot51> systemctl isolate graphical.target is used
[19:59] <jackpot51> graphical.target should depend on wpa_supplicant.service
[19:59] <jackpot51> ethernet connections are not lost due to network manager not being killed
[19:59] <jackpot51> wifi is lost due to wpa_supplicant being killed
[20:01] <jackpot51> related bug: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024
[20:01] <rbasak> How does network manager avoid getting killed?
[20:01] <tsimonq2> *sits in*
[20:02] <tsimonq2> Had that bug before
[20:02] <tsimonq2> (didn't know it wasn't hardware-specific)
[20:02] <jackpot51> it is not hardware specific - system76 and dell laptops experience it on first boot
[20:02] <jackpot51> switching cards does not solve the issue
[20:03] <rbasak> jackpot51: it sounds like you've done a great job pinning down the root cause. Thanks! If nothing else, please could you write that up in the bug?
[20:03] <sarnold> jackpot51: nice :D
[20:03] <jackpot51> will do
[20:04] <rbasak> jackpot51: as for the correct fix, should it be done the same way that network manager avoids getting killed? How is that, and doesn't network manager spawn wpasupplicant as a child, or is it really using a separate systemd service?
[20:04] <sarnold> maybe NM systemd unit file needs adjusting to require wpa_supplicant..
[20:04] <jackpot51> it is a seperate service - as a side note, bluetoothd has the same issue
[20:04] <wgrant> Saviq: https://bugreports.qt.io/browse/QTBUG-54822
[20:05] <jackpot51> I fixed it the "wrong" way by adding IgnoreOnIsolate=true to [Unit] in wpa_supplicant.service
[20:05] <rbasak> jackpot51: and it'd be nice to have the relevant Debian maintainer's agreement if possible before fixing it in Ubuntu, so we can do it the same way and get additional review
[20:05] <rbasak> Assuming the same bug exists in Debian and that they want to use graphical.target in the same way.
[20:07] <rbasak> If urgent, we can always fix first of course. I'm just not confident enough in this area to confirm any fix is correct.
[20:08] <jackpot51> My fix would mean that going to a non-networking target would not kill wpa_supplicant
[20:08] <jackpot51> I don't think that happens in the real world often though
[20:13] <jackpot51> here is the most upstream service file: https://w1.fi/cgit/hostap/tree/wpa_supplicant/systemd/wpa_supplicant.service.in
[20:13] <sarnold> and does NM depend upon it properly?
[20:14] <jackpot51> I am not sure: https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/data/NetworkManager.service.in
[20:14] <jackpot51> It isn't in the upstream service file
[20:26] <jackpot51> by the way, it is possible to trigger the bug running on your own system. All you have to do is run `sudo systemctl isolate default.target` while connected to WiFi