[01:58] bkerensa: ok, turns out that even though update-manager -d didn't give me any errors, it also didn't actually upgrade me to trusty; found the issue in ubuntu-release-upgrader and fixing now [02:35] slangasek: \o/ pff [02:35] slangasek: should have told me what it was so I could fix it :) [02:35] where is the mentoring love [02:41] slangasek: so wait is the bug in saucy too? [02:42] slangasek: or does update-manager -d grab a new copy of ubuntu-release-upgrader when -d is dropped [02:53] bkerensa: ubuntu-release-upgrader is always downloaded from the server for the target release. [02:53] slangasek: oh ok well when its fixed ping me so I can unleash the trusty testing [02:53] :D [02:54] as for mentoring, the changes are in the bzr branch and are self-explanatory? [02:54] the fix is uploaded, should be visible to the world in ~15minutes [02:56] slangasek: Do you have any tasks this cycle you might be interested in working with the loco on? [04:02] slangasek: hmm still says no upgrades available [04:02] slangasek: do I need to purge something? === c_smith is now known as c_smith-afk [05:41] bkerensa: was apparently a timing issue; I don't know why it took so long to publish to the archive server, but the right tarball is there now and works [05:43] bkerensa: tasks this cycle> none off the top of my head, but I can think on it. Are there any events planned for this cycle? [06:33] slangasek: not events planned ideally I had announced stepping down as lead but I am a bit concerned nobody stepped up to take over so maybe I will try for a jam at some point [06:33] slangasek: I am also very interested in helping out with debconf planning and need to get in the loop [06:37] * slangasek gestures in the direction of the debconf14-team list :) [07:06] slangasek: dear god whoopsie is filling my syslog [07:06] like [07:06] a line a second [07:07] :s [07:14] slangasek: so it seems software-properties-gtk is missing some info about trusty so it crashes i [07:14] aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Ubuntu/trusty [07:17] right, seems to be python-apt needing an update [07:20] slangasek: I will have a look [07:20] the issue is in data/templates/Ubuntu.info.in [07:21] ah [07:21] ok [07:21] fixing it [07:34] slangasek: https://code.launchpad.net/~bkerensa/ubuntu/trusty/python-apt/add-trusty-template/+merge/192297 [07:35] if you dont mind otherwise it can patch pilot [07:35] :D [07:47] slangasek: looks like it was already fixed but is just in proposed [15:37] bkerensa: oh? let me see [15:39] yep, looks like it's landed in trusty now [17:26] slangasek: can you remind me how to do merges from debian [17:26] slangasek: I believe it was bzr branch debianlp:package [17:26] then there was a way to bring in the Ubuntu changes [17:36] bkerensa: http://developer.ubuntu.com/packaging/html/udd-merging.html [17:36] thx [17:38] slangasek: seems to leave out the step of first bzr branch ubuntu:package but wfm [17:38] :D [17:44] slangasek: whats the way to list a debian bug # in changelog? [17:44] like [17:44] * Merged from Debian ( ) [17:45] why would you be listing Debian bug #s in the changelog for an Ubuntu upload? [17:46] slangasek: idk I guess I wouldnt [17:47] ok then :) [17:50] slangasek: what does this output mean "bad-distribution-in-changes-file trusty" [17:51] that you don't have up-to-date tooling that fully understands trusty, so you're getting a warning about an unknown upload target [17:51] also, 'lintian -i' [17:53] slangasek: makes sense so because I merged from Debian when its building out it worries [17:54] it shouldnt affect things though? [17:54] no, it has nothing to do with merging from Debian [17:54] it has to do with you not having up-to-date tooling installed that understands trusty [17:55] slangasek: how can I install the up-to-date tooling? [17:55] is this possible [17:55] 'apt-get dist-upgrade' on trusty? [17:56] ah, actually it looks like lintian hasn't been fixed yet to know trusty [17:56] so just ignore the warning, since you know 'trusty' is a real target [17:57] slangasek: do you know if patch pilots have started or should I bug someone at some point to sponsor my pending MP's? [17:57] one is security related [17:57] the patch pilot schedule runs continuously [17:58] oh [17:58] no breaks between release? [17:58] sheesh [18:07] slangasek: I came across a package in Ubuntu that has a control file with upstreams info still intact in the maintainer field [18:07] can that be accurate? [18:08] surely Debian Maintainers are not also maintaining packages we merge into Ubuntu [18:08] what package? [18:08] tuxguitar [18:09] also does not use Ubuntu versioning [18:09] o.o [18:09] tony mancil [18:09] ;p [18:09] If it needs to be changed I can do so since I am merging in the latest [18:10] if it doesn't use Ubuntu versioning, why do you think it's being maintained in Ubuntu at all, instead of being a synced package? [18:12] slangasek: ok so synced but we still dont add anything? [18:12] if we added something it wouldn't be in sync [18:13] can I merge it without adding a changelog entry or changing anything? [18:13] so its like a manual sync [18:13] no, you can't merge something that doesn't have anything on our side needing merged [18:13] meh [18:13] its outdated in Ubuntu [18:13] :) [18:13] outdated compared to what? [18:13] to upstream [18:13] its not been synced recently [18:14] we have 1.2-15 [18:14] 1.2-16 is available [18:14] so outdated compared to unstable [18:14] yes [18:14] which means it will be autosynced for trusty [18:14] ok [18:14] * bkerensa notes to leave synced packages alone [18:15] slangasek: how often does autosyncing occur generally? [18:15] more or less constantly. I don't know if autosyncs have been turned on yet, I guess it will happen in a day or two at the latest [18:17] * sbeattie guesses so, based on the 8GB+ of updates debmirror has been trying to sync for him since yesterday === i2p is now known as i2p` === i2p` is now known as i2p [22:10] slangasek: https://code.launchpad.net/~bkerensa/ubuntu/trusty/xubuntu-meta/refresh-all-the-things/+merge/192300 [22:10] could you sponsor that [22:10] its so xubuntu is good to start being usable for trusty