[00:33] fossfreedom: did you inspect the filesystem to make sure the appropriate binary was included, if it needs feh or something like that? [01:10] Unit193, tsimonq2: thanks! [01:10] Now I can harass you for uploads! (Nah, just kidding.) [01:14] heh heh [01:22] niedbalski: Bug 1708305 hasn't had its traditional 7-day aging in xenial-proposed; is there a particular reason to release it early? [01:22] bug 1708305 in Ubuntu Cloud Archive ocata "Realtime feature mlockall: Cannot allocate memory" [Medium,In progress] https://launchpad.net/bugs/1708305 === JanC is now known as Guest61806 === JanC_ is now known as JanC [07:24] cyphermox, re ubiquity. Yes budgie-wm is there and the process list indicates budgie-wm --sm-disable is running. For fun, I commented out gnome-settings-daemon & budgie-wm process start code, installed metacity and feh with a hard-coded background_image and the wallpaper was displayed. Title bar looks odd though. [07:26] I do note there is two gnome-settings-daemon binaries listed in ubiquity-dm that no longer exists with the recent gnome-settings-daemon upload but deleting those two from the array doesnt do anything. more of a tiny code cleanup in that area [07:44] cyphermox, brain-wave! Ubuntu Budgie has the new per-desktop override for the gsettings background schema so that we don't trample over other desktops overriding that key. We need now to set the environment variable "XDG_CURRENT_DESKTOP=Budgie". Would you be ok with a PR for that? === maclin1 is now known as maclin [08:30] @pilot in === udevbot changed the topic of #ubuntu-devel to: Zesty Released | Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-zesty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | Patch Pilots: sil2100 [08:34] Patch pilot <3 [08:38] tsimonq2: you don't need patch pilots that much anymore though! Just for main packages ;) [08:46] sil2100: I know, I just love the concept ;) [08:47] I like it as a day to have a reason to ignore all else [08:47] and actually focus on creating/reviewing/sponsoring fixes [08:49] cpaelzer: <3 [08:50] I liked it as someone without upload access and I'm guessing I wasn't the only one === led2 is now known as led1 [11:03] fossfreedom: oh [11:11] cjwatson, thank you for env --chdir. It did occur to me for ages that make -C is amazing, but i never thought of porting it elsewhere. [11:12] yeah, been annoying me for a long time now! [11:13] https://code.launchpad.net/~jbicha/ubiquity/adapt-to-gsd325/+merge/329902 [11:13] jbicha: libdazzle ftbfs on ppc64el, accepting anyway, new package [11:13] bdmurray: Can I please be approved to ~ubuntu-reviewers? :) [11:14] doko: thanks [11:28] @pilot out === udevbot changed the topic of #ubuntu-devel to: Zesty Released | Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-zesty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | Patch Pilots: [11:28] (lunch time) [11:46] tsimonq2: around? About bug 1327002. Your uploaded changes file is missing bug references even though the changelog entry has them. Did you use an Ubuntu system to build the changes file? The Ubuntu delta in dpkg-genchanges matters. [11:46] bug 1327002 in gthumb (Ubuntu Trusty) "Mint 17/Ubuntu 14.04 - can only launch one instance of gthumb" [Low,Triaged] https://launchpad.net/bugs/1327002 [11:47] rbasak: Hey :) [11:47] rbasak: That's...weird [11:47] It's pretty common when people upload SRUs from Debian. [11:47] rbasak: I *am* on a Buster system at the moment [11:47] (Ubuntu SRUs) [11:47] So yeah [11:48] tsimonq2: can you fix up? If not I can. [11:48] Sorry, my mistake. I didn't know there was much of a difference and this is the first time I'm using a Buster system for this sort of thing... [11:48] rbasak: How would I go about fixing it? [11:49] tsimonq2: I'm not sure how to do it on Debian. But you can check before upload: the changes files should have a X-Launchpad-Bugs-Fixed (IIRC, similar at least) line if correct. [11:49] tsimonq2: on Ubuntu, it happens by magic. [11:49] rbasak: Alright. [11:50] rbasak: So should I upload a new upload with that line in changes, or is it easier to do it on your end? [11:50] tsimonq2: new upload please. One of us has to do it. You already have the source :-) [11:50] Ok. :) [11:50] I can fetch it from the reject queue and do it myself if it's awkward for you. [11:50] No, I can try ;) [11:51] On Debian you should be able to make it work by setting DEB_VENDOR=ubuntu in the environment when running debuild. [11:51] cjwatson: ack, thanks! [11:52] I run Testing on my laptop (which I use less often but happen to be using today) and Artful on my desktop... weird little quirk you wouldn't expect :) [11:54] I've been meaning to write a "so you're now an uploader!" page with a list of quirks for a while :-/ [11:55] * rbasak JFDI [11:57] rbasak: better? [11:59] rbasak: I have a feeling doomsday and any other package that I uploaded to the SRU queue within the past few hours might have the same problem :( [12:00] tsimonq2: do you mind checking for me please? If you click on the entry in the queue you'll see the changes file. If you can give me a list of uploads I need to reject, that's the easiest way. [12:03] rbasak: libva/xenial libqapt/xenial doomsday/zesty [12:03] rbasak: I've been busy :P [12:03] OK, I'll reject those, thanks. [12:03] I've just written an initial revision of https://wiki.ubuntu.com/DeveloperMembershipBoard/NewUploader [12:04] Not linked to it from anywhere yet. [12:04] Everyone: feel free to contribute and edit. [12:04] The DMB could refer successful applicants to this page so they know what to do. I remember that I certainly didn't know how to upload when my application was approved :) [12:05] rbasak: Have you seen https://wiki.ubuntu.com/MOTU/New ? [12:05] rbasak: The only reason I knew how to upload when I got approved is because when working with acheronuk on some Kubuntu stuff, he remote signed some packages and I got to dput ubuntu them from the VPS we were working on :P [12:06] But yeah, I pretty much had to figure out everything on there :) [12:06] Laney: ah. Thanks! [12:07] Most of that isn't MOTU specific. We should have a single page and make sure the DMB points successful applicants to it. [12:08] One thing that I had to learn once I got MOTU was how to use the autopkgtest infra from the point of view of someone who has upload permissions to the archive [12:09] In this specific example, nodejs wouldn't migrate because node-something-or-other failed tests, I uploaded a new version fixing it and it didn't automatically retry... turns out my sponsors have always been smart enough to retry that stuff for me :) [12:10] Unit193: tseliot looks after the nvidia drivers, I don't have upload rights for those packages [12:13] tsimonq2: there is: https://wiki.ubuntu.com/UbuntuDevelopment/Uploading [12:14] Oh [12:14] Ok [12:14] Cool [12:15] And then there were three :-/ [12:17] * tsimonq2 scratches head: [12:17] E: libqapt source: maintainer-address-causes-mail-loops-or-bounces Ubuntu Developers [12:18] Hmmm, is that a bug in Lintian or a Won't Fix? O_o [12:18] Does it do that on Ubuntu also? [12:19] IIRC, Debian's policy is that maintainer addresses must not be behind a moderation wall. [12:20] I'll check later on my Artful machine [12:20] But there doesn't seem to be a relevant delta so my guess is Yes [12:20] Perhaps we need to suppress that on Ubuntu as it's acceptable to us. [12:21] Ok [12:24] rbasak: All of those packages should be fixed now with a proper header, fwiw [12:25] Thanks! [12:25] Thanks for catching that ;) [12:47] Wooo, sponsorship queue down to 34 [12:48] tsimonq2, \o/ [12:49] Oh hey mitya57 :D [12:49] (a good chunk of the things in the sponsorship queue just needed triage [12:49] ) [13:11] @pilot in === udevbot changed the topic of #ubuntu-devel to: Zesty Released | Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-zesty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | Patch Pilots: sil2100 [13:11] o/ sil2100 [13:11] o/ [13:12] rbasak: Since it's your SRU day, could I please get this accepted into xenial-proposed? bug 1710993 [13:12] bug 1710993 in lubuntu-meta (Ubuntu Xenial) "PulseAudio requirement breaks Firefox on ALSA-only systems after 55.0.1 update" [Critical,In progress] https://launchpad.net/bugs/1710993 [13:12] fossfreedom: that doesn't sound like something that ubiquity should do? [13:13] rbasak: With my Lubuntu Release Manager hat on, I think it's a fairly important update that should be rolled out... what's the process for shortening and/or bypassing the 7 day limit? i.e. do I just justify it to you or do I say something in the bug report? [13:15] Looking [13:17] tsimonq2: that's a pretty radical change given what Lubuntu is supposed to be. [13:18] tsimonq2: I suppose I'd like an ack from the Lubuntu release managers :-P [13:18] rbasak: I also agree that it's a pretty radical change from upstream Firefox [13:18] tsimonq2: so ultimately I guess you can decide, but would it be worth getting some wider discussion first? [13:19] rbasak: We did have this discussion back in February or March [13:19] Oh, OK. Did that include stable release changes? [13:19] rbasak: Upstream Firefox isn't going to budge, and we already ship with pulse in 16.10 and on [13:19] Yep [13:19] As I say I think it's not really for me to say if that's what you all want to do. [13:20] I just want to make sure that you're sure :-) [13:20] I'm sure :) [13:20] you :-) [13:20] We're sure :P [13:20] OK :) [13:21] Technically, will this dtrt and pull in pulseaudio in all cases? [13:22] Is there any case where apt will attempt to remove lubuntu-meta instead? [13:22] Well, I'd also like a merge on my lubuntu.xenial MP :P [13:22] Link? [13:22] ...why would apt try to remove lubuntu-desktop? :P [13:22] https://code.launchpad.net/~tsimonq2/ubuntu-seeds/add-pulseaudio-to-lubuntu-xenial/+merge/329783 [13:22] Well for example something could conflict with pulseaudio. [13:23] Well like I said, this change is implemented in 16.10 and on [13:23] While I know that's not 100% justification, the seed hasn't changed that much from 16.04 to 16.10 [13:23] Yeah but package disruption is expected during release upgrades. [13:24] Well, it'll just install some new packages. [13:24] I wouldn't describe it as "disruption" [13:24] I'm not sure (technically) about a seed change after release. I suppose it'll affect only future point releases? I don't know, so I'd like to defer to someone who knows for the MP. [13:24] Ok. [13:24] If that's all it does, then I agree it's not disruption. [13:24] The risk is that it doesn't do that for some unknown reason. [13:24] rbasak: We have a daily ISO that runs germinate [13:24] I see [13:25] One reason might be that if I have lubuntu-desktop and something installed that conflicts with pulseaudio for example. [13:25] ic [13:25] I don't know if there are other cases that might cause a problem. [13:25] I'm not saying there is a problem. I'm just trying to explore possibilities to try and discover any problems now rather than later. [13:25] I understand :) [13:26] Worst case scenario, not saying this *will* happen, but lubuntu-desktop gets removed. It's a metapackage, it shouldn't really matter. [13:26] It impacts a future release upgrade. [13:26] i.e. iirc it *shouldn't* autoremove the deps [13:26] Oh [13:26] Well true [13:27] This might all be considered acceptable of course. [13:27] Another thing is that "apt upgrade" may not want to install pulseaudio; only "apt full-upgrade". What will the GUI do? [13:27] This may not be so bad; it's no worse. [13:27] Actually kernel upgrades work that way. [13:27] So it must be fine. [13:27] Good point [13:36] But yeah, we're pretty sure about doing this :) [13:36] OK [13:36] +1 [13:36] I'm just writing this up in the bug. [13:37] Ok :) [13:43] rbasak: My thoughts on Firefox not sticking to the ESR releases for stable releases because of the regression potential is another issue, but it could have made this easier to deal with [13:43] It's difficult. I'm not sure general Ubuntu users want to stick to ESR for the lifetime of Xenial for example. [13:43] (I'm not a Firefox expert (that's... the point with this...) but I think that's how Debian does it) [13:44] No I get it [13:44] But [13:44] snaps better suit Firefox's model IMHO. [13:44] rbasak: For once irt snaps I agree :P [13:44] Another way might be to package ESR also (as firefox-esr or something). Then flavours could choose to use that. [13:45] I wouldn't mind doing that [13:45] But as always there's the question of who would provide the developer time. [13:45] Exactly... [13:46] I don't think Ubuntu would object to a firefox-esr being maintained in universe. [13:46] But, hindsight is 20/20, some users have complained already that they have to install pulse (to Mozilla) and there will be more... but as Chris said in the changelog entry, if nobody will step up to fix it, it goes unfixed. [13:46] And we have to adapt. [13:47] Unfortunately... [13:47] rbasak: Maybe at the start of b-cycle I'll consider bringing that up to the MOTU list [13:47] But we'll have to see [13:48] Any reason to delay the discussion? You can talk about B plans now :) [13:49] I don't have a good answer :P [13:50] Sometime between today and B Alpha 1 then :P [13:50] Does lubuntu-meta autogenerate its dependencies like ubuntu-meta? [13:50] Yep. [13:50] Well, it does the thing with ./update [13:50] So for this upload you did that manually against your local change to the seed for which the MP is still outstanding? [13:50] Yep, then discarded the config change. [13:51] That's why I think they should land closely timed :P [13:52] OK. You have my +1 for both the upload and the MP, but I'd like someone who knows more to confirm that this approach is OK please. [13:52] Sure. [13:53] cyphermox: ping :) ^ [13:53] slangasek perhaps? ^ and https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1710993 and https://code.launchpad.net/~tsimonq2/ubuntu-seeds/add-pulseaudio-to-lubuntu-xenial/+merge/329783 [13:53] Launchpad bug 1710993 in lubuntu-meta (Ubuntu Xenial) "PulseAudio requirement breaks Firefox on ALSA-only systems after 55.0.1 update" [Critical,In progress] [13:54] Fair ;) [14:00] hey, any network-manager modem-manager experts around? I updated my xenial x250 to zesty and my modem connection can no longer be established. I see the modem (modem-manager-gui) and network-manager sees the modem but any attempts to connect fail with ""No suitable device found for this connection." -- indeed any attempt to create a new 3G connection shows no devices on the "applicable to this [14:00] device" page [14:11] tsimonq2: rbasak: looks sane to me, but you'll want to test what the effect is of adding pulseaudio in general [14:11] ie is that going to pull in other things too? [14:11] does that work fine with volume controls or is there config to change as well? (I don't think so, but better be safe) [14:12] I think it would be best to further flesh out the test cases even if it looks liek a pretty straightforward change [14:14] zyga-ubuntu: you should check if your modem is listed by 'mmcli -L', and if not, you should check whether usb-modeswitch and usb-modeswitch-data were updated [14:17] @pilot out === udevbot changed the topic of #ubuntu-devel to: Zesty Released | Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-zesty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | Patch Pilots: [14:17] * sil2100 switches to his SRU hat === jeblair_ is now known as jeblair [14:19] cyphermox: it is listed by mmcli -L [14:19] cyphermox: /org/freedesktop/ModemManager1/Modem/0 [Sierra] MBIM [1199:A001] [14:20] jbicha, any guess on when the hidpi scaling issue will get resolved in artful? is there a bug i can track the progress of? [14:21] bjf: wait for gnome-shell 3.25.90, we're working on it this week [14:21] jbicha, ack, thanks [14:21] I guess you could subscribe to LP: #1712800 [14:21] Launchpad bug 1712800 in mutter (Ubuntu) "FFe: gnome-shell 3.26" [Undecided,Confirmed] https://launchpad.net/bugs/1712800 [14:22] zyga-ubuntu: do you have ofono installed? [14:23] I think there was a case where it might be pulled in or remain installed when it really shouldn't [14:24] sforshee: I did see he uploaded, but for the past several changes you were the one submitting them so figured I'd poke you. [14:25] cyphermox (cc rbasak): ack, I'll spin up a Lubuntu VM and test it out, report back soon [14:27] cyphermox: partially [14:27] libqofono-qt5-0:amd64 install [14:27] qml-module-ofono:amd64 install [14:27] cyphermox: ^ just those two [14:27] should I remove them? [14:27] I don't think that would be it [14:27] you shouldn't just remove random things if unsure ;) [14:27] ok [14:27] any more hints on what to try? [14:28] zyga-ubuntu: sorry, I do not know, the best I can offer is that you delete the connection in NM and re-create it after a reboot [14:28] cyphermox: tried that [14:28] ok [14:28] cyphermox: when I create the connection I don't see my modem listed as a choice [14:28] cyphermox: it's a roaming connection, not sure if that's a factor [14:28] if the modem is listed in ModemManager (mmcli), but not found in NM, I don't know what to do with that [14:29] ah, well you should check if the connection allows roaming [14:29] there's a checkbox when you edit it [14:29] Unit193: I supplied patches yes, however it sounds like there's a patch already and I'm not able to upload that pacakge [14:34] Somewhat, yes. No idea how the internal Canonical stuff works though. Thanks. [14:35] cyphermox: checked that as well, it does [14:35] * zyga-ubuntu moves out of range [14:37] tseliot: Have you seen LP 1711758 by chance? [14:37] Launchpad bug 1711758 in nvidia-graphics-drivers-304 (Ubuntu) "artful: nvidia-304 unknown symbol init_mm" [Undecided,Confirmed] https://launchpad.net/bugs/1711758 [14:38] Unit193: not yet, but I'll have a look at it, and I'll fix it. Thanks [14:38] Thanks a lot! [14:47] cpaelzer: looking at nut in Xenial unapproved. Is it intentional that it has no bug link? [14:48] cpaelzer: yes and no [14:48] grr [14:48] rbasak: ^^ [14:48] rbasak: that is the lack of -v on that build [14:48] on the bug we talked in regard to the importer [14:49] I see. And the latest version bump is supposed to not have a bug link, right? [14:49] rbasak: the former upload had both buglinks, and the new one is reverting one of them [14:49] so with -v I'd close "both" which would be also wrong [14:49] Could you re-upload with a -v please? Otherwise I think it'll cause issues in the pending-sru report. [14:49] Oh. [14:49] I see. [14:49] rbasak: well I can, but then both which is wrong [14:49] and changing old changelog history isn't good either [14:49] which is why I uploaded the way it is now [14:50] I think we need a bug link for the bug that is still being fixed. Otherwise pending-sru will be broken. [14:50] I wonder if we need to hack the changes file to have one bug but not the other. [14:50] rbasak: TL;DR tell me which way we need it for the process to work and I'll do so [14:51] cpaelzer: unless someone says otherwise, I'd rebuild the source with -us -uc -v..., then modify the changes file manually, then debsign on the changes file. Ugly, but I can't think of anything better. [14:51] tsimonq2: Also, in regards to your lintian warning. Yes there isn't delta, but that's because lintian uses profiles. That specific check is disabled in Ubuntu. [14:52] Unit193: aha [14:52] Try --profile ubuntu [14:52] rbasak: https://code.launchpad.net/~paelzer/ubuntu/+source/nut/+git/nut/+ref/bug-1540008-1099947-xenial https://code.launchpad.net/~paelzer/ubuntu/+source/nut/+git/nut/+ref/bug-1540008-1099947-trusty [14:52] rbasak: do you want to do that hacking to fix it up or shall I try and you reject from unapproved so I can re-upload? [14:53] cpaelzer: I'd prefer if you could hack it please, then I can independently check. Less chance of a mistake slipping through - especially because it's a hack. [14:53] rbasak: ok, then reject now and I'll send you something into -unapproved [14:53] rbasak: will ping you then === led2 is now known as led1 === led2 is now known as led1 [15:03] rbasak: you rejected the xenial one but the case is the same for xenial and trusty [15:04] rbasak: I have the modified changes file ready [15:04] rbasak: would you reject the nut in trusty as well so we can halde both at once? [15:05] cpaelzer: sorry, done. [15:06] rbasak: what part of this approach were you looking for confirmation on? The mechanics of how to add a package to a seed post-release, or the idea of doing so? [15:06] rbasak: bot nut uploads are in unapproved again, please take a look if you think the +v+changesmod worked the way [15:11] cpaelzer: will do, thanks! [15:11] slangasek: mainly the changing of the seed post-release. [15:11] slangasek: well, both parts of your question I guess. [15:11] slangasek: I don't know what I don't know, so I'm asking :) [15:13] slangasek: I don't see what would go wrong with changing both the seed and accepting the upload. But as it's unusual, I'm asking. [15:14] cpaelzer: https://launchpadlibrarian.net/335184706/nut_2.7.1-1ubuntu1.2_source.changes [15:15] cpaelzer: that's not quite what I was expecting. But I don't particularly mind 99947 ending up auto-closing. That can easily be fixed. [15:15] rbasak: yes, we've had to do this sort of thing before, and this is the right mechanism; update-manager will honor new dependencies on upgrade, so if Lubuntu is using that, we're ok [15:16] rbasak: oh hey, another Lubuntu Release Manager who has access approved my MP ;) [15:17] rbasak: I tohught the regex is on LP: # [15:17] rbasak: odd [15:17] rbasak: do you want another new changes file? [15:17] rbasak: or do you handle the remaining mistake in that? [15:24] cyphermox: http://paste.ubuntu.com/25432469/ [15:24] cyphermox: n-m crashes, I'm trying to fetch sources to see what's going on there [15:24] specifically on sie 30 16:59:44 fyke NetworkManager[1442]: ((nm-manager.c:2863)): assertion '' failed sie 30 16:59:44 fyke NetworkManager[1442]: ((devices/nm-device.c:8235)): assertion '' failed [15:27] rbasak: Well, he approved it, just didn't actually merge it. [15:28] g_return_if_fail (nm_device_get_managed (device, FALSE)); |> [15:28] also on g_return_val_if_fail (nm_device_get_managed (self, FALSE), FALSE); [15:29] cyphermox: so nmcli gives me this: cdc-wdm0: unmanaged gsm (cdc_mbim, cdc_acm), hw [15:30] cyphermox, rbasak: Ok, to report back, it installs 9 additional dependencies with 7,528 KB taken up. It installs correctly and Firefox can now play audio. [15:30] Not too many extra things [15:30] I think it'll be fine. [15:31] tsimonq2, slangasek, cyphermox: thanks. I'll process this today. Just otp right now. [15:31] Ok [15:40] Sponsorship queue down to 30 \o/ [15:42] * zyga updates to artful [15:42] mvo: fingers crossed :) [15:44] hmm [15:44] freenode's web irc is pretty neat [15:44] if it only did offline / background I'd never look back [15:45] tsimonq2: hopefully not as a result of freeze-violating uploads? :) [15:47] slangasek: Nope [15:47] slangasek: Most are triaging things, asking for updates on packages, ~ubuntu-sponsors falsely subscribed, etc. [15:47] slangasek: If anything I've done a lot of SRUs :P [15:47] Mm, not convinced most of lgw01 is going to wake back up trivially ... [15:48] slangasek: One thing I want to know is how to get things like the top entry (a Bazaar branch) which I already left a comment on out of the queue :P [15:49] hmm, good question [15:51] bdmurray: hey [15:52] seems like that the pep8 tests were failing before too [15:52] do you want me to fix them all or just the parts that I edited? [15:54] slangasek: In general I'm wondering how some of these Bazaar branches are getting on here, take that MP against lp:ubuntu-cve-tracker for example, that's on the MOTU page, not the security one, which is inaccurate because the MOTU page should be things the MOTUs can sponsor, no? :) [15:55] bdmurray: nevermind [15:55] they're not failing on trunk [15:56] tsimonq2: I don't have the url in front of me, can you point me the page you're seeing this on/ [15:56] tsimonq2: http://reqorts.qa.ubuntu.com/reports/sponsoring/index.html ? [15:57] slangasek: General overview: http://reqorts.qa.ubuntu.com/reports/sponsoring/ - MOTU page: http://reqorts.qa.ubuntu.com/reports/sponsoring/motu.html - Security page: http://reqorts.qa.ubuntu.com/reports/sponsoring/security.html [15:57] jbicha: do you have a recommendation of who would be appropriate to help review a SRU for vim? specifically related to gvim on unity and segfaults in xenial? it was done via the git workflow and I can review the code content, but I don't know what is considered 'correct' for desktop [15:58] tsimonq2: ok, completely unclear to me as well; UTSL https://launchpad.net/ubuntu-sponsoring [16:00] Someone needs to indent their CSS ;) [16:00] (not pointing fingers at anyone :P) [16:01] heh [16:02] nacc: IMO gvim isn't "desktop" so any Ubuntu developer should be fine [16:02] jbicha: well the question in particular is what to do about some desktop-related hook/variable [16:02] jbicha: specifically the last comment from the submitter in https://code.launchpad.net/~jbenden/ubuntu/+source/vim/+git/vim/+merge/329613 [16:02] vim is Foundations [16:02] slangasek: So is ~ubuntu-branches still relevant? [16:02] slangasek: --^ :) [16:03] tsimonq2: we're going to reuse it for git, i think (or something similar, at least). but the bzr branches are generally dead. [16:03] Ok [16:04] I'll whip up an MP working with that... [16:04] tsimonq2: that's my understanding at least. I'd wait to be sure from slangasek :) [16:04] yeah the remaining ~ubuntu-branches bzr branches are a bucket of fail [16:05] Ok [16:05] (the fail was left out in the sun too long and melted) [16:06] heh [16:07] nacc: I left a couple drive-by comments, you can ask in #ubuntu-desktop [16:07] jbicha: thank you [16:39] zyga-ubuntu: If you like webchat, perhaps check out 'thelounge' [16:46] Unit193: thanks, I'll check that out [16:47] Can be configured to have scrollback. [17:16] rbasak: Is git ubuntu something I can install yet? [17:18] Mhhh, it would be great to have it as just a regular deb package, I don't like having snapd installed as it hogs my disk space :/ [17:18] tsimonq2: it's only a snap [17:19] tsimonq2: making it a deb is not in our plans [17:19] tsimonq2: because we depend on functionality from debs only available in artful (or potentially outside of debs, in the case of somethjing i'm hitting now) [17:19] tsimonq2: and i'm not willing to sign up to backport git, gbp, etc. to older releases :) [17:20] I guess I'm installing from source :P [17:20] tsimonq2: what release are you on? [17:20] Artful :P [17:20] tsimonq2: ok, that should be fine :) [17:20] tsimonq2: and 'installing' from source, is just clone and add repo/bin to PATH [17:20] (for now) [17:20] Fair ok [17:21] as it's a degenerate case currently (only used by developers) [17:21] tsimonq2: if that doesn't work, let me know [17:21] Ok [17:24] nacc: Let's just say that I might be hacking on the packaging guide, if I was, is git ubuntu something production ready enough to put there? ;) [17:25] (probably not, right?) [17:25] I mean, it can always be edited in the future, but I'd like a working packaging guide... [17:27] tsimonq2: we're not yet importing the world, so i'd wait [17:28] tsimonq2: it's on our roadmap for 1.0 to hit that switch [17:28] but we need to coordinate with LP team, etc. [17:28] Ok [17:28] tsimonq2: so yeah, i'd not mention it in the hacking guide (yet). I don't think. But I woudl drop any mention of UDD or bzr :) [17:28] I'm working on that right now ;) [17:29] tsimonq2: nice, can check that off my list then :) [17:29] nacc: That was a major part of my MOTU application, I would have been around and probably had MOTU a year before I did had that thing been up-to-date. [17:29] I know I'm not the only one who is discouraged by that. [17:30] So since the sponsorship queue doesn't hurt my eyes as much, this is my next step ;) [17:30] tsimonq2: nice! [17:31] tsimonq2: yeah, tbh, the tooling is probably stable enough for most people to use it, but the first thing many will try to do is clone some srcpkg which we haven't imported yet and complain (we have a clear error message to request the import). So rather than throw up that roadblock, my plan was to transition the guide at the same time as we hit the switch to import the world (which is going to take a [17:31] while anyways) [17:32] nacc: Ok [17:32] nacc: Do you generally have an ETA on that? [17:32] (i.e. days, weeks, months, years?) [17:34] tsimonq2: heh [17:35] I guess I'm sort of asking because if it's a matter of a month or two, I might not want to pour my heart and soul into that part of it [17:35] tsimonq2: we are hopefully going to have a trello board up soon which has the plan laid out (and public) [17:35] ooooooh ok [17:35] tsimonq2: we're hopefully going to be at alpha in the next month or two, but that's not a hard requirement [17:35] Ok [17:35] Fair [17:35] tsimonq2: major feature wise, we're mostly done. but we have a bunch of refactoring going on now and a huge testing spike that rbasak is working on [17:36] nacc: Ok. [17:37] nacc: Btw, I've been meaning to ask... how will that deal with packages that are already imported in Git? [17:37] nacc: i.e. the Kubuntu packages use a totally separate Git workflow [17:37] tsimonq2: i'll make sure to loop you in when we get all that documented out (our plan is to sit down and do that by eow next week, but again, no guarantees :) [17:37] Will git merge be expected or how will that work? [17:37] nacc: Ok :) [17:37] tsimonq2: the importer doesn't really care (currently) [17:38] Alright [17:38] tsimonq2: we have discussed telling the importer about some upstream sources of information (where upstream is up to the developer) [17:38] Ok [17:38] tsimonq2: the distinction is that the importer only trusts launchpad publishing data [17:38] tsimonq2: and we want it to always be 'correct' relative to the archive [17:38] I see [17:38] Publishing data in respect to what? [17:39] e.g.: https://launchpad.net/ubuntu/+source/freeradius/+publishinghistory [17:39] what was published when, and to where and with what contents [17:39] basically, the git import is a git view of that page for every srcpkg [17:39] oic [17:40] nacc: Let's say someone really really hates Git and doesn't want to do their changes in Git, it'll automatically import the changes, right? [17:40] the other issue we'll run into with adding 'other' sources (if we do it automatically) is that we have to translate version strings correctly (as each git project could do versioning however they want, with namespaces etc.) [17:40] tsimonq2: yep [17:40] tsimonq2: as long as they are published [17:40] And what if there's (unfortunately) build conflicts? [17:40] tsimonq2: build where? [17:40] s/build/merge/ [17:40] tsimonq2: algorithmically, there won't be :) [17:41]