[11:35] <Skuggen> vorlon: Thanks :)
[12:22] <ahasenack> Skuggen: heh, net-snmp upstream decided to replace my_bool with a char, have you seen this before? https://sourceforge.net/p/net-snmp/code/ci/9f4af8c42d515e6b214738cc97212dfbe7f749cf
[12:22] <ahasenack> what was my_bool before, in terms of size?
[12:22] <ahasenack> I guess they want a byte
[13:24] <Skuggen> ahasenack: Originally, my_bool was just a char
[13:25] <ahasenack> ok
[13:25] <Skuggen> Well, I'm not 100% sure about "originally" since it's old, but it was a char before :)
[15:21] <doko> ahasenack, cpaelzer: do you plan with samba 4.10 for disco? looks like Python3 is making some progress there
[15:24] <ricotz> doko, would you have time to put together a gcc-mozilla based on 8.2 in bionic?
[15:26] <ahasenack> doko: yeah, it's the first one with py3 and py2
[15:26] <ahasenack> doko: I wasn't planning on going ahead of debian
[15:26] <doko> ricotz: there is a proper gcc-8.x in bionic, you don't need another build
[15:26] <ricotz> doko, for xenial, trusty isn't worth it anymore, I guess
[15:27] <ricotz> I meant to backport from bionic
[15:28] <doko> ricotz: it's easy. just rename the package from gcc-8 and look what changes the existing gcc-mozilla has
[15:28] <doko> wasn't chris ccoulson doing that?
[15:30] <ricotz> doko, I know, I did so with 6.5.0 which is already required for the current firefox to fix armhf/arm64 -- but I ran into failures on trusty
[15:30] <ricotz> I can try with 8.2 again though
[15:31] <ricotz> doko, not sure what chris is doing these days
[15:31] <ricotz> basically osomon has taken over the mozilla stuff
[15:33] <doko> including the b-d's? ;p
[15:34] <ricotz> mw_hudson is doing rustc/cargo
[17:19] <ejat> hi .. is there ppa for gnome 3.32 available for testing?
[18:11] <ricotz> doko, this is something which came up https://paste.debian.net/plain/1065702
[18:24] <jbicha> ejat: GNOME 3.32 has not been released yet, but there (probably) won't be a PPA either
[18:26] <ahasenack> has anybody written a sort of recursive check-mir script? To chase down all non-main deps and run it again on each, until there is none left?
[18:33] <ejat> jbicha: ok thanks
[18:34] <ejat> jbicha: can u advise on this => https://paste.ubuntu.com/p/sWqW2hWQZp/
[18:34] <jbicha> that doesn't mean anything to me
[18:34] <ejat> gnome-control-center crashed
[18:35] <ejat> in disco -proposed
[18:37] <jbicha> could you file a bug with apport
[18:42] <jbicha> also: https://askubuntu.com/questions/785414/is-it-ok-to-enable-proposed-updates-during-ubuntus-development-cycle
[18:44] <ejat> jbicha: bug 1814947
[18:59] <jbicha> ejat: that still provides almost no info. I meant can you use Ubuntu's error reporter thing to report the crash with the debug info
[19:00] <jbicha> but I'm too busy working on other stuff this week to be able to help you really. Sorry
[19:01] <ejat> jbicha: okay ill try .. no worries .. sorry to take ya time
[19:14] <ahasenack> is it possible to disable the universe component in a ppa, when building a source package there?
[19:15] <tumbleweed> IIRC it's encforcing component separation is PPA configuration option
[19:15] <ahasenack> I have "￼ Default (security dependencies and recommended updates)."
[19:15] <ahasenack> and
[19:16] <ahasenack> "Use the same components used for each source in the Ubuntu primary archive."
[19:16] <ahasenack> the other option is " Use all Ubuntu components available.", which doesn't seem to be what I want
[19:17] <infinity> ahasenack: What are you trying to accomplish, exactly?
[19:17] <infinity> ahasenack: main can build-dep on universe (even in the primary archive) now.
[19:17] <ahasenack> testing a mir
[19:17] <ahasenack> it's a universe package, for which I'm listing all non-main build-deps
[19:17] <infinity> ahasenack: main can't have runtime deps on universe, but PPAs don't have components, so everything in a PPA is in main.
[19:18] <ahasenack> my plan was to upload said source package, have the build fail because of missing deps (which are in universe), and then start uploading the universe deps one by one
[19:19] <infinity> Yeah, that's not going to work.
[19:19] <ahasenack> ok, local lxd it is then
[19:22] <ejat> seb128:  updated as your advise in bug 1814949
[19:23] <seb128> ejat, thx
[19:23] <ejat> thanks to you for the guide ..
[19:43] <seb128> ejat, do you remember what panel you opened last?
[19:44] <seb128> ejat, and do you have special discuss connected or specifc fs? (like zfs)
[19:58] <jbicha> seb128: yeah the zfs in the original bug was the one thing that looked interesting :)