[04:30] Hello, can someone help me with what are the high level steps on how you build ubuntu for a different arch. eg. https://wiki.ubuntu.com/S390X For now, I just want to build ubuntu for x86 in my laptop. [04:31] when i lookup "build ubuntu" i get https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel does this mean building the latest ubuntu that i can boostrap on my machine? [05:53] geekodour08: I'm not sure exactly what you're trying to do, but https://wiki.debian.org/DebianBootstrap is a pretty decent overview. [05:53] geekodour08: We do some things a bit differently, but it's basically the same as bootstrapping a new Debian architecture. [06:17] geekodour08: Why would you need to bootstrap to build for x86 when Ubuntu it already built for x86...? [06:17] s/it/is/ [06:25] RAOF: thanks a lot! and infinity: just for educational purpose, i just wanted to know what is done. the debian bootstrap guide looks like a nice resource. === zyga|afk is now known as zyga [10:27] hm, so I was planning on maintaining mesa on lp git, but I see that it's owned by the "server dev import team" and I can't push there (as a core dev), so where should I put these then, under some team? [10:27] https://code.launchpad.net/ubuntu/+source/mesa [10:29] not that importing that repo would be sane either :) [10:31] yeah, I'll use ubuntu-x-swat instead [11:04] tjaalton: core-dev? [11:04] it would be good if all uploaders could push to it [11:05] would be [11:05] oh you mean core-dev team? [11:07] Or add core-dev to that team I guess [11:07] that'd be nasty, since it'd get all the bugmail [11:08] should go to https://lists.launchpad.net/ubuntu-x-swat/, since the team has an email address set [11:08] (AIUI) [11:09] hmm right [11:10] I think there might be a way to point https://code.launchpad.net/ubuntu/+source/mesa at something else though [11:11] hmm, though I'm not sure if that would get the distro ACLs === cpaelzer_ is now known as cpaelzer [11:17] doesn't matter [13:12] bdmurray: do you know where https://git.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/diff/DistUpgrade/apt_btrfs_snapshot.py?h=ubuntu/xenial-proposed&id=7c0245c13bdeb92fb005aa7073c50bd78db99693 came from in your 1:16.04.26 upload of ubuntu-release-upgrader? Was that intentional? [13:42] xnox: please consider adding ~ubuntu-core-dev to https://launchpad.net/~timezonemap-team/+members [13:43] jbicha, no.... [13:43] jbicha, not everyone in core-dev is allowed to commit to that. [13:44] why? [13:44] CLA [13:44] ok, I'll send you a merge proposal then :) [13:50] xnox: maybe it needs to be added to https://www.canonical.com/projects/directory & https://github.com/canonical-websites/www.canonical.com/blob/master/templates/projects/directory.html [13:50] and maybe a note about the CLA added to the source code somewhere? [13:52] not sure about it being under the CLA [13:52] IIRC its origins are external [13:53] Laney, jbicha - it was confusing last time i tried to check all that. [13:54] as in, eternal origins, are/were/maybe based on our stuff [13:54] I did update debian/copyright a bit in my merge proposal [13:54] anyway Laney is also a committer ;-) [13:55] there are some parts that are clearly not owned by Canonical (tzdata & geonames) [13:56] xnox: Make me an adminstrator then and I'll add core-dev [14:33] rbasak, hey, if you do SRU could you look at moving the fwupd/bionic one to -updates? bug #1719797 is listed as not verified but it was verified, it's just that a gnome-software SRU (ab)used the same bug number and that did lead to have the tags reset to verification-needed. Those don't need to go together and I checked with Mario, the fwupd is good to migrate [14:33] bug 1719797 in gnome-software (Fedora) "Firmware update seemingly not working" [Undecided,Confirmed] https://launchpad.net/bugs/1719797 [15:03] rbasak: it's updated as a part of the pre-build.sh script so it was somewhat intentional. [15:04] OK [15:26] anyone else seen this or know how to fix? i'm sure i'im just missing something. [15:26] this is a disco client trying to ssh with password auth to a 18.04 server [15:26] the server *does* have PasswordAuthentication enabled [15:27] and a fresh lxc container for bionic can connect with just 'ssh host' [15:28] but disco doesn't like it [15:28] smoser: the specific error messages and logs might be useful? [15:28] (not sure if you already got help on this or not) [15:29] teward: yeah, i'm getting them [15:30] i'm spinning a disco lxd up to try and SSH to the host computer it's on (this laptop, which also has OpenSSH on it for reasons) [15:30] to see if I can replicate. [15:30] (slow net is slow >.<) [15:32] http://paste.ubuntu.com/p/DHF82dGkqw/ [15:32] ^-- cosmic [15:33] smoser: confirm /etc/ssh/sshd_config has 'PasswordAuthentication yes' on the server [15:33] because it's not offering password auth as an option [15:33] at least according to your logs [15:35] smoser: E:NOREPRO with 'PassswordAuthentication yes' and no special AuthenticationMethods definitions on an 18.04 server with a Disco client [15:35] gah. [15:36] also important is to type the ip address correctly [15:36] that'd help :P [15:36] so that you attempt to connect to the system that you enabled password auth on [15:36] heheheh [15:36] rather than a different system [15:36] smoser: so it's working then :) [15:36] pebkac [15:36] YAY, crisis averted. *goes to find more coffee* [15:37] thank you [15:37] yep [16:02] bdmurray: I was reviewing ceph in Trusty :-/ [16:08] rbasak: The task was Incomplete and I'd subscribed to it [16:09] I had assumed that since your question was answered (clearly satisfactorily) that it was expected to be picked up by the next person on rota. [16:10] I try and subscribe to ones I set to Incomplete so I can follow up as I already have context and as next person might not get to that SRU. [16:11] That's a good thing to do. But we should have a method to avoid collisions. [16:43] tkamppeter: about hplip. I think that hplip installs something from the network in a system location, when downloading drivers ... [16:44] so better ask about which files do *not* belong to a package [17:46] cyphermox: are you taking care of n-m vs. dnsmasq autopkgtest? Wondering what to do with my Trello card on it. [17:46] cyphermox: I do have https://git.launchpad.net/~racb/ubuntu/+source/network-manager/commit/?h=python-dep8-improvements which I think would be useful to land in n-m in Disco for the future. Want a proper MP for it? [17:48] cpaelzer: I'm going to continue looking at the qemu/libvirt SRUs tomorrow morning. [17:51] rbasak: desktop team owns network-manager [17:51] rbasak: I'll have a look, but please feel free to push your code. [17:52] cyphermox: thanks. Was your first statement in relation to my n-m vs. dnsmasq or my branch? If the latter, I guess I need to coordinate with the desktop team for the n-m issue then? Is that seb128? [17:54] * rbasak EODs [17:58] rbasak: my point was for the code, you should feel free to push to the right NM branch (which used to be https://code.launchpad.net/~network-manager/network-manager/+git/ubuntu/+ref/master, but it appears out of date), and I'll have a look at the dnsmasq issues later [18:11] OK, thanks! [20:50] rbasak, hey, feel free to create a mp for those changes, we can review them. Or just ping me tomorrow if we want to get them commited without going through submitted a proper merge request [20:52] rbasak, cyphermox, the current vcs is https://git.launchpad.net/network-manager/log/?h=cosmic and it's almost uptodate, just mdeslaur didn't commit his CVE fix there === cshep is now known as platonical