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