[01:07] <skynet1248> Hi I have question about kernel dynamic modules
[01:08] <skynet1248> if I execute modinfo parport_serial | grep 9835
[01:08] <skynet1248> I get somethink like this:
[01:08] <skynet1248> alias:          pci:v00009710d00009835sv*sd*bc*sc*i*
[01:08] <skynet1248> is any option to add my own alias to parport_serial module?
[05:11] <micahg> ScottK: pacakgekit is baffling, same build on maverick builds fine, it seems like the mozilla plugin isn't being built for some reason on natty
[05:47] <micahg> ScottK: packagekit solved (bug 692854 if you want to sponsor)
[07:17] <dholbach> good morning!
[07:31] <micahg> Riddell: I fixed the packagekit FTBFS if you want to sponsor it (bug 692854)
[08:36] <janimo> in case binary new requests are to be brought up here: lightspark{,-common,-dbg} and browser-plugin-lightspark on armel were just recently introduced. thanks
[08:44] <dholbach> @pilot in
[09:02] <janimo> Laney: hello, have you had the chance to look at the new way ghc6 fails on armel?
[10:37] <AnAnt> Hello, is this http://launchpadlibrarian.net/61007900/buildlog_ubuntu-natty-i386.git-buildpackage_0.5.12_FAILEDTOBUILD.txt.gz , actually a problem of pychecker with python2.7 ?
[10:39] <AnAnt> doko__: ^
[10:46] <dholbach> james_w, why can't I reject https://code.launchpad.net/~stefan-bader-canonical/ubuntu/natty/e2fsprogs/branch/+merge/43541?
[10:46] <dholbach> there's just "WIP", "Merged" and "Needs Review"
[10:51] <doko__> AnAnt: likely pychecker, we had issues getting it updated to 2.6 too ...
[12:05]  * Keybuk must stop winding Lennart up on lkml
[12:06] <Keybuk> but it's such fun!
[12:10] <dholbach> Public service announcement: we're down to 20 items on http://reqorts.qa.ubuntu.com/reports/sponsoring/ - YES!
[12:10] <Keybuk> dholbach: I'm looking forwards to having to get all my uploads sponsored ;-)
[12:11] <dholbach> Keybuk, because you'll lose your upload privileges? why?
[12:11] <maco> you're de-core-dev-ing like crimsun did?
[12:11] <Keybuk> because of a Launchpad bug
[12:11] <Keybuk> I can't transfer my GPG key to my new LP account
[12:12] <dholbach> Keybuk, seems like LP is not set up for schizophrenic personas :-P
[12:12] <Keybuk> indeed
[12:12] <Keybuk> I'm going to nag them about that once they've fixed the gaping hole in LP's brain where all my bzr branches used to be
[12:13] <Keybuk> but you know how it is, Ticket in RT, Out of Mind
[12:19] <dholbach> Daviey, do you know if bug 687971 is still blocked on bug 688522?
[12:19]  * dholbach attempts a test build
[12:21] <Laney> janimo: a bit, not so much though
[12:27] <Daviey> dholbach, I don't know if the openjdk fix has landed in natty yet..
[12:27]  * Daviey checks
[12:27] <Daviey> dholbach, looks like it's still blocked in natty awaiting the openjdk fix (either dropping of two patches, or a proper fix from upstream)
[12:28] <dholbach> Daviey, shall we get the bug out of the queue for now then?
[12:29] <Daviey> dholbach, Hmm.. can do; i'd like to hear doko's thoughts on porting the fix to openjdk from maverick to natty for the interim to get things moving
[12:29] <dholbach> hum, to me it looks like it's building alright in natty?
[12:29] <Daviey> that would unblock and allow us to close those bugs.
[12:30] <Daviey> dholbach, Interesting.... openjdk hasn't been touched since the 26th Nov... so it *should* fail.
[12:30] <dholbach> http://paste.ubuntu.com/546240/
[12:30] <dholbach> Daviey, ^
[12:31] <Daviey> hmm
[12:32] <Daviey> dholbach, lemme rebuild here
[12:32] <dholbach> Daviey, that was with James' branch
[12:36]  * Daviey regrets reinstalling natty... loosing his devel env.
[12:36] <Daviey> losing*
[12:39] <dholbach> Daviey, the old version still builds too
[12:39] <dholbach> (but with the wrong paths, I guess)
[12:40] <Daviey> dholbach, trying to re-digest https://bugs.launchpad.net/ubuntu/+source/eucalyptus-commons-ext/+bug/687971/comments/8
[12:41] <dholbach> Daviey, to me it looks like geronimo-jacc-1.1-spec should be uploaded, so eucalyptus-commons-ext can build again, then something done with openjdk, so libhibernate3-java can build
[12:41] <Daviey> That is my understanding. :)
[12:41] <dholbach> Daviey, if that's the case, I'd upload the geronimo-jacc-1.1-spec change now
[12:42] <dholbach> Daviey, go? :)
[12:45] <Daviey> dholbach, It sounds sensible, and i'm not too concerned if it has fall out TBH... :)
[12:46] <dholbach> haha
[12:46] <dholbach> ok
[12:46] <dholbach> I'm sure James will be in touch with me if it fails :)
[12:47] <Daviey> dholbach, No. i really think it will be ok
[12:47] <Daviey> and James probably won't be around until NEXT YEAR :)
[12:47] <Daviey> so you have a year to run, and hide. :)
[12:47] <dholbach> ha!
[12:49] <Daviey> dholbach, Can you give me a ping when it's uploaded please? :)
[12:50] <dholbach> Daviey,
[12:50] <dholbach>  ____ ___ _   _  ____ _
[12:50] <dholbach> |  _ \_ _| \ | |/ ___| |
[12:50] <dholbach> | |_) | ||  \| | |  _| |
[12:50] <dholbach> |  __/| || |\  | |_| |_|
[12:50] <dholbach> |_|  |___|_| \_|\____(_)
[12:50] <dholbach>                         
[12:50] <dholbach> @pilot out
[12:54] <Daviey> dholbach, thanks! :)
[12:59] <bdrung> dholbach: your ping was very small. it could easily overlooked. :P
[12:59] <bdrung> dholbach: and thanks for getting the main queue down to 15
[13:00] <dholbach> 15? I thought 19
[13:00] <bdrung> dholbach: _main_
[13:00] <dholbach> aha, yes :)
[13:00] <dholbach> next step: get the 2000+ bugs with patches fixed :-P
[13:01] <bdrung> dholbach: you were involved in edit-patch, weren't you?
[13:01] <dholbach> bdrung, mvo was
[13:01] <dholbach> I was part of the discussion when the idea was born - but that's as much credit as I'd be willing to take :)
[13:02] <bdrung> dholbach: this tool needs some love and needs an non-interactive mode for making sponsor-patch a useful tool for the 2000+ bugs with patches
[13:02] <dholbach> bdrung, I agree
[13:03] <bdrung> dholbach: why are you listed as author in edit-patch?
[13:03]  * bdrung tries to make you more responsible. :P
[13:03] <dholbach> bdrung, I don't know
[13:04] <dholbach> I started writing it in python and mvo took it from there and rewrote it in much better shell
[13:04] <bdrung> dholbach: having it in python would be nice - then sponsor-patch could use it without running a command
[13:05] <dholbach> the idea was to get it into devscripts at some stage
[13:05] <bdrung> dholbach: ok, valid point
[13:05] <dholbach> alrightie... I'll take the dog for a walk in the snow now - see you in a bit :)
[13:05] <bdrung> but devscripts doesn't seem to be well maintained
[13:06] <bdrung> dholbach: and i will build an iglu :)
[13:06] <dholbach> ha, excellent :)
[13:06] <dholbach> enjoy! :)
[13:08] <ScottK> micahg: Thank you.  I'll take it if no one else has.
[13:10] <Keybuk> Using distribution natty
[13:10] <Keybuk> bzr: ERROR: Unknown target distribution: natty
[13:10] <Keybuk> --
[13:10] <Keybuk> argh!
[13:14] <mvo> bdrung: yeah, I saw that there are a few open bugs on it, should be straightforward to add a non-interactive mode
[13:14] <bdrung> mvo: it would be nice if you could add it.
[13:16] <mvo> bdrung: ok, I have a look next
[13:32] <cdbs> Keybuk: That is fixed in latest upload to maverick
[13:32] <cdbs> s/maverick/natty
[13:33] <cdbs> Keybuk: and I am waiting for someone to test an SRU upload. Its already in maverick-proposed
[13:34] <Keybuk> cdbs: yeah, it's just annoying that it checks at all
[13:34] <Keybuk> since it doesn't actually put it anywhere
[13:38] <cdbs> Keybuk: I guess you are using bzr bd or something related to its plugins?
[13:38] <Keybuk> yup
[13:38] <Keybuk> bzr merge-upstream in this case
[13:41] <Keybuk> hmm, and now pbuilder isn't co-operating
[13:42] <ScottK> If it's not finding your pbuilderrc it's because sudo changed it's handling of the environment in Natty and it's looking in /root.
[13:42] <cdbs> Keybuk: Would be awesome if you tested that SRU upload
[13:42] <cdbs> g2g
[13:42] <Keybuk> no, it seems to be not installing one of the Build-Dependeices
[13:42] <Keybuk> so failing the build because the dep isn't satisfied
[13:42] <cdbs> upload of package bzr-builddeb
[13:42] <Keybuk> dpkg-checkbuilddeps: Unmet build dependencies: libselinux1-dev
[13:42] <Keybuk> dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting.
[13:42] <ScottK> That's on odd one then.
[13:43] <Keybuk> yeah
[13:43] <Keybuk> it looks like it's not parsing the libselinux1-dev [linux-any] properly
[13:43] <ScottK> Ah.
[13:44] <Keybuk> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=363193
[13:47] <Keybuk> jhunt: did we get a useful bash-completion file in the end?
[13:50] <jhunt> Keybuk: yes - in your inbox now.
[13:51] <Keybuk> who should be listed as the author?
[13:51] <jhunt> Keybuk: me
[13:52] <Keybuk> ok
[13:52] <jhunt> Keybuk: thx.
[13:54] <jhunt> Keybuk: it closes bug 672067.
[13:55] <Keybuk> ok, committed and pushed
[13:55] <Keybuk> you'll need to do some packaging changes - but we can do those on thursday together if london works out
[13:56] <maco> Keybuk: s/works out/defrosts/ ?
[13:56] <Keybuk> jhunt: if you wanted to have a go beforehand, you'd need to bzr merge -c 1258 lp:upstart to cherry pick the add, and then modify debian/upstart.install
[13:56] <Keybuk> (man dh_install is the appropriate manpage)
[13:58] <Keybuk> walters: howdy
[13:59] <walters> hi Keybuk
[13:59] <Keybuk> how goes it?
[13:59] <walters> good!  just getting back from doing some volunteer math tutoring at the local high school, it's fun actually =)
[14:00] <walters> how's sf treating you?
[14:00] <Keybuk> SF isn't yet treating me
[14:00] <Keybuk> I'm still in the USCIS queue
[14:01] <walters> ah hah, i had to look that up
[14:01] <maco> how many years is that expected to take?
[14:01] <walters> though i should know it since my girlfriend just became an American 2 months ago =)
[14:01] <Keybuk> I'm supposed to find out sometime between Dec 24 and Dec 28
[14:01] <Keybuk> depending how you interpret their "days"
[14:01] <Keybuk> and whether or not they miss the promised date and just do it later
[14:01] <walters> our days are 24.1 feet
[14:02] <james_w> dholbach, can you upload the package?
[14:02] <maco> did they just give some number of days and then youre supposed to subtract out weekends and holidays?
[14:02] <dholbach> james_w, I'm core-dev, so I'd expect so, yes
[14:02] <james_w> dholbach, yeah
[14:03] <james_w> dholbach, it's bug filing time I think
[14:03] <dholbach> james_w, is it lp.net/launchpad already?
[14:03] <james_w> yeah, I think so
[14:03] <dholbach> alrightie
[14:04] <Keybuk> maco: that's the depending on their intepretation bit ;-)
[14:05] <dholbach> james_w, bug 692998
[14:05] <james_w> thanks
[14:05] <dholbach> de rien
[14:06] <maco> Keybuk: remember, we dont have boxing day
[14:08] <jhunt> Keybuk: thx!
[15:01] <joaopinto> cjwatson, hi, regarding my installer crash yesterday, could you please look at http://pastebin.ubuntu.com/546280/ ?
[15:01] <joaopinto> I will file a bug it if it's unknown or unlikely to be fixed on a newer daily
[15:02] <Keybuk> kees: AYT?
[15:02] <cjwatson> joaopinto: please file a bug with the full logs attached
[15:02] <joaopinto> ok
[15:02] <cjwatson> I don't debug from partial logs
[15:03] <cjwatson> I assume you've already verified it on the current daily build
[15:03] <joaopinto> shouldn't the installer crash handler allow me to open the report bug directly  and upload the required files ?
[15:03] <cjwatson> (if that had been a full log I wouldn't have needed to ask)
[15:03] <joaopinto> not yet, I will need to refresh the iso
[15:04] <cjwatson> you should get an apport crash thingy if the installer crashes
[15:04] <cjwatson> if you don't, use 'ubuntu-bug ubiquity'
[15:05] <joaopinto> running ubuntu-bug ubiquity from my current installed system failed :P
[15:05] <joaopinto> I assume it's expected to be run from a livecd session
[15:05] <cjwatson> of course!
[15:05] <joaopinto> I will do the manual link bug reporting and attach the logs, otherwise I would need to reinstall & fail again
[15:05] <cjwatson> fine
[15:10] <joaopinto> done, bug 693027
[15:11] <joaopinto> which package should be used for the bug about the global menu not responding after the failure dialog ?
[15:17] <joaopinto> about refreshing to a newer daily, can I just dd the usb partition into an iso, update it and just dump it into the usb partition ?
[15:18] <cjwatson> I doubt it
[15:19] <joaopinto> ok, so I will only be able to test it after retunring from holidays :(
[15:21] <cjwatson> ev is looking at it now
[15:30] <joaopinto> the booting ubuntu logo looks bad, that is something being worked right ?
[15:31] <joaopinto> "bad" as in, the letters are not round, look "corrupted" on the edges
[15:33] <cjwatson> known, I'll work on it in the new year if nobody's dealt with it before then
[15:56] <pitti> cjwatson: unfortunately adding python2.7 to "minimal" didn't work :-/
[15:57] <pitti> I rebuilt alternates, still there (http://cdimage.ubuntu.com/daily/20101221.1/natty-alternate-i386.list)
[15:59] <cjwatson> alternates are a bad example
[15:59] <cjwatson> you need to ask me for those :)
[15:59] <cjwatson> how long ago did you add it?
[15:59] <pitti> cjwatson: oh, I do? what changed?
[16:00] <cjwatson> wait, maybe I'm misdiagnosing this
[16:00] <pitti> cjwatson: ubuntu-meta published 3 hours ago
[16:00] <cjwatson> it does have the right priority set
[16:00] <pitti> cjwatson: and I rebuilt the alternates about a hour ago
[16:00] <cjwatson> give me a minute to investigate, then.
[16:01] <pitti> cjwatson: it's not that urgent, no need to drop your brain state
[16:01] <cjwatson> too late
[16:01] <pitti> argh, sorry about that
[16:04] <doko> kenvandine: could you have a look at the libgda4 build failure? more gir transition stuff
[16:04] <kenvandine> sure
[16:05] <pitti> cjwatson, doko: OTOH it's just 16 packages to rebuild for getting everything to python2.7 | python2.6; I can do just that, ok for you?
[16:05] <cjwatson> wait please, this might be a genuine germinate bug and I'd like the opportunity to diagnose it
[16:05] <pitti> *nod*
[16:07] <cjwatson> it should definitely be using python2.7 already in minimal rather than pulling another package into standard
[16:10] <doko> only python2.7-minimal is in minimal, not python2.7
[16:11] <cjwatson> no, python2.7 is in minimal now as a workaround by pitti
[16:11] <cjwatson> that should have worked
[16:11] <doko> ahh
[16:29] <cjwatson> pitti: (still working on it, germinate slows down really dramatically under pdb :-/)
[16:36] <cjwatson> pitti: the short-term solution is going to be to rebuild those packages anyway, though - I'm not going to be able to get a new germinate deployed on archive and cdimage before I finish for the year
[16:36] <pitti> cjwatson: fine with me, I should be able to get this done today
[16:37] <pitti> cjwatson: is there a way how you can reproduce this situation with all packages fixed?
[16:37] <cjwatson> I can probably fake something up
[16:37] <cjwatson> hopefully I can fix it before the archive changes though :)
[16:37] <pitti> cjwatson: also, I'm only going to rebuild the packages which are on the CD for now
[16:37] <pitti> there are a few more in main
[16:38] <pitti> which we could then temporarily seed for testing
[16:38] <cjwatson> I can always just keep this debug directory - due to another bug, it won't refresh its local copies of the Packages/Sources files
[16:38] <cjwatson> so it should be fine
[16:38] <pitti> ah, good
[16:40] <cjwatson> ah, maybe it's not a germinate bug after all
[16:40] <cjwatson> Package: python-apt
[16:40] <cjwatson> Depends: python2.6 | python2.7, python (>= 2.6.5-11~), libapt-inst1.2, libapt-pkg4.10, libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.4.0), python-apt-common
[16:40] <cjwatson> Recommends: lsb-release, iso-codes, python2.6
[16:40] <pitti> argh
[16:40] <cjwatson> why that Recommends?
[16:40] <pitti> mvo: ^ could have been a temporary workaround for something?
[16:42] <cjwatson> fix that and python2.6 drops off the alternate CD
[16:42] <pitti> cool, will coordinate with mvo and do that
[16:42] <pitti> thank you!
[16:42] <mvo> pitti: uh, no idea, let me fix and upload
[16:42] <mvo> thanks cjwatson
[16:42] <cjwatson> according to germinate anyway
[16:42] <pitti> mvo: ah, you want to? ok, great
[16:42] <mvo> and bzr blame to figure out what is going on
[16:43] <mvo> pitti: yes, thats fine, I will merge the latest debian stuff along the way
[16:44] <pitti> mvo: danke
[16:46] <pitti> it's the only reverse-recommends in main, anyway
[16:46] <pitti> and in all other components, too
[16:54] <doko> kees, mterry: MIR ping (689766 and 692955), just to resolve component mismatches
[16:54] <mterry> doko, hiyo
[16:55] <mterry> doko, I can take the first, libasyncns
[16:56] <doko> mterry: the second too, please. I did submit these, can't review
[16:56] <mterry> doko, OK
[17:00] <lool> cjwatson: Hey, would you be able to ack and/or promote python-fixtures as per LP #692955?
[17:00] <lool> (I need a fix in a package which is dep-wait on python-fixtures)
[17:01] <cjwatson> I can't ack it, I'm not in ubuntu-mir
[17:02] <cjwatson> my understanding is that I only get to promote source packages that are either (a) trivially obvious (split-out, renamed, etc.) or (b) set to Fix Committed by an ubuntu-mir member
[17:05] <mterry> lool, I'm about to look at that MIR
[17:11] <lool> mterry: thanks
[17:12] <lool> cjwatson, james_w: Yeah, I thought you guys were historical ~ubuntu-mir members
[17:12] <tgardner> how does one find out _why_ a package has been rejected?
[17:13] <cjwatson> lool: nope, never me
[17:13] <cjwatson> tgardner: the archive admin who rejects iti is supposed to mail you
[17:13] <cjwatson> *it
[17:13] <cjwatson> if they didn't then they need a slap :)
[17:13] <tgardner> cjwatson, huh. and how do I find out who rejected it?
[17:14] <tgardner> the email says 'Rejected by archive administrator.'
[17:14] <cjwatson> unfortunately there isn't an easy way.  https://bugs.launchpad.net/launchpad/+bug/31750
[17:14] <cjwatson> tgardner: what package name?
[17:15] <tgardner> cjwatson, linux-meta_2.6.35.24.29
[17:15] <tgardner> I lookedin both of the bugs mentioned in the changelog, but there were no comments
[17:17] <cjwatson> irritatingly I can't find a record even on the archive master
[17:17] <cjwatson> stable processing is usually pitti, but I see he's left IRC
[17:17] <cjwatson> it may have been an accident
[17:17] <tgardner> cjwatson, well, this isn't an ABI bumper so it can wait.
[17:18] <cjwatson> I can resurrect it
[17:18] <tgardner> cjwatson, that would be fine with me.
[17:19] <doko> marjo: do you have any update on the upgrade failures?
[17:21] <mvo> doko: it looks like its not python releated, it appears there is a problem with the intel driver on the i945 chipset
[17:21] <mterry> lool, python-fixtures FTBFS due to test case issues.  If you're an interested party, maybe you can look at it?
[17:21] <mvo> doko: I added code to the release-upgrader to autopatch pycomile now
[17:22] <cjwatson> tgardner: resurrected and accepted.  if whoever it was didn't want me to reverse their decision then they should have mailed you a reason. :-)
[17:22] <doko> mvo: \o/  is this release-upgrader in maverick-updates too?
[17:22] <tgardner> cjwatson, :) thanks for your help
[17:24] <mvo> doko: everybody upgrading will get it, regardless of -update or not (its the default upgrade app, its always fetched from the distro that you upgrade to)
[17:24] <mvo> doko: diff -ed ftw ;)
[17:25] <mvo> cjwatson: new python-apt uploaded, took a bit longer as I fixed another debfile releated bug along the way
[17:25] <cjwatson> ta
[17:31] <apw> marjo, sure
[17:31] <marjo> apw: here
[17:31] <apw> marjo, can we get the /var/log/Xorg.0.log file for the 'black boot' on the bug please
[17:32] <marjo> fyi: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/693093
[17:36] <marjo> apw: done
[17:37] <doko> cdbs: about your liboauth upload. if your change is the only Ubuntu change, please don't make such changes. it increases the delta for no extra worth
[17:39] <apw> marjo, and you are unable to switch to VT1 ?  or you can now?
[17:42] <apw> marjo, can you login to the machine and do the following
[17:43] <apw> DISPLAY=:0.0 xwd -root >OUT
[17:43] <apw> and put the result somewhere i can look at it
[17:43] <apw> marjo, also can you confirm whether the backlight is on (a dark place can herlp here)
[17:45] <marjo> apw: still unable to switch to VT1
[17:47] <apw> marjo, actualy you may need to login to do the xwd thing, so when you hear the drums i think you need to hit return, then password, and see if you get the login sound
[17:47] <apw> then try it
[17:49] <cdbs> doko: okay, it was actually recommended by the upstream author. Moreover, I am the debian maintainer of liboauth, so I can manage delta effectively
[17:49] <cdbs> and I will drop the patch in Debian once gcc-4.5 becomes default there for wheezy
[17:50] <marjo> apw: didn't work
[17:50] <doko> cdbs: it is unlikely that debian will make --as-needed the default
[17:50] <marjo> apw: any other way to try?
[17:51] <cdbs> doko: hmm, will see then. will sync when I get the next upstream version uploaded
[17:51] <marjo> apw: no login sound heard
[17:52] <marjo> apw: backlight is on
[18:10] <lool> doko: Is it intentional that the python2.7 testsuite got disabled in 2.7.1-1ubuntu1?
[18:11] <doko> lool: yes, quick upload, no changes, will enable it again with the next upload
[19:17] <netadmin> hello
[20:22] <ari-tczew> @pilot in
[20:31] <ari-tczew> cyphermox: have you got tested your patch for cnetworkmanager?
[20:34] <cyphermox> ari-tczew, it was, though I didn't re-test it recently since uploading a new NM
[20:34] <ari-tczew> cyphermox: could you do it again?
[20:34] <cyphermox> of course
[20:35] <ari-tczew> cool!
[20:35] <cyphermox> sorry for harassing you about it, it's just pretty much the only way to use NM on the command-line, although I frankly don't touch it much
[20:36] <ebroder> ari-tczew: Hey, I noticed you've had the pinot merge assigned to you for a while now. Are you still working on it?
[20:36] <ari-tczew> ebroder: yes, I'll do it after sponsorship for cyphermox
[20:36] <ari-tczew> ebroder: I'm doing cnetworkmanager 1st as cyphermox is waiting since 8th Dec :)
[20:36] <ebroder> ari-tczew: Ok, just making sure you hadn't forgotten about it. I was going to look at it last night, but didn't want to yoink it from you
[20:37] <ari-tczew> ebroder: I'm pretty sure that you won't be out of work for Ubuntu :)
[20:39] <cyphermox> ari-tczew, still looks good to me.
[20:46] <ScottK> ari-tczew: Did you see clementine is out of binary New in maverick-backports?
[20:46] <ScottK> Should be all set now.
[20:47] <ari-tczew> ScottK: I see that clementine is still New :>
[20:48] <ScottK> ari-tczew: Sorry.  My mistake.
[20:48] <ari-tczew> kk
[20:48]  * ScottK was looking at a different package and didn't realize it.
[20:52] <ari-tczew> cyphermox: what do you think about forwarding your patch to debian/upstream?
[20:54] <cyphermox> yes, upstream
[20:54] <cyphermox> I should send it again, actually
[20:56] <ari-tczew> cyphermox: ok, uploading
[21:04]  * ari-tczew loves review patches by Bazaar, but hates sponsorship it! (very hard)
[21:05] <tumbleweed> ari-tczew: sponsor-patch :)
[21:05] <Laney> bzr bd -S ?
[21:05] <ari-tczew> tumbleweed: does it support Bazaar?
[21:05] <tumbleweed> ari-tczew: yes
[21:06] <ari-tczew> Laney: there are not only build source. now I have to set tags, set merge and 100 other commands...
[21:06] <tumbleweed> ari-tczew: bzr mark-uploaded && bzr push :parent (or sponsor-patch :P)
[21:07] <ari-tczew> tumbleweed: could you drive through sponsor-patch way?
[21:07] <tumbleweed> ari-tczew: sponsor-patch -u $bugnumber
[21:07] <tumbleweed> err -s
[21:08] <bdrung> ari-tczew: you could read the man page of sponsor-patch. it explains it very good.
[21:10] <ari-tczew> tumbleweed: okay, I have test built done, it's ready to upload. does sponsor-patch sets all tags and other data necessary for bzr sponsorship policy? (I'm just making sure)
[21:10] <tumbleweed> yes it does
[21:11] <bdrung> ari-tczew: you can run it with "-v" to see which commands are called
[21:11] <tumbleweed> only issue I can think of is that you can't push back when uploading SRUs because there is no $release-proposed branch yet, but that's not really sponsor-patch's problem.
[21:12] <ari-tczew> tumbleweed: I'm doing for natty.
[21:17] <ari-tczew> which package includes 'bd' command?
[21:17] <bdrung> ari-tczew: bzr-builddeb
[21:18] <bdrung> ari-tczew: does sponsor-patch fail?
[21:18] <tumbleweed> bdrung: that should probably go in reccomends
[21:18] <ari-tczew> bdrung: yes
[21:19] <bdrung> ari-tczew: show me the crash log
[21:19]  * bdrung nods to tumbleweed.
[21:29] <ari-tczew> bdrung: http://paste.ubuntu.com/546400/
[21:33] <bdrung> tumbleweed: does this work: "login(self, service=service)"?
[21:34] <tumbleweed> bdrung: that service comes from the default value in ubuntutools.lp
[21:38] <ari-tczew> bdrung, tumbleweed: failed :/ http://paste.ubuntu.com/546403/
[21:38] <bdrung> tumbleweed: shouldn't you mention which env variables are still supported, but deprecated
[21:39] <bdrung> ari-tczew: i'll fix it. which u-d-t version do you use?
[21:41] <tumbleweed> bdrung: ok
[21:41] <ari-tczew> bdrung: Zainstalowana: 0.107
[21:41] <ari-tczew> ups, I have to update :/
[21:43] <tumbleweed> bdrung: there's also the option of warning about deprecated configuration
[21:43] <bdrung> tumbleweed: ok, i prefer that.
[21:43] <bdrung> tumbleweed: then we don't need to document them
[21:43] <tumbleweed> oh, even better, yes :)
[21:44] <ari-tczew> cyphermox: sorry for my late, I'm testing sponsor-patch on your case :)
[21:44] <ari-tczew> but don't worry, it will be uploaded soon
[21:44] <bdrung> ari-tczew: your bug is still in trunk
[21:45] <ari-tczew> bdrung: could you qualify the time of fix? I have to know whether wait for fix or play with sponsorship another way.
[21:45] <bdrung> ari-tczew: gimme 5 mins.
[21:45] <ari-tczew> okay
[21:48] <ari-tczew> mterry: you merged bluez with Debian! wow you're my lord!
[21:48] <mterry> ari-tczew, :)  we hadn't done that in a long time
[21:48] <ari-tczew> mterry: I tried to do this 3 times but always I failed :P
[21:49] <mterry> ari-tczew, I only did half of it.  Rob Ancell started it, I just finished it.   Maybe that was the missing piece -- only do a small chunk.  :)
[21:50] <ari-tczew> mterry: mhm. I'm working with Robert on some merges. Your sentence makes me sure that it will be a success :)
[21:50] <bdrung> ari-tczew: pushed fix to trunk
[21:50] <cyphermox> ari-tczew, ah, no worries, I'm fighting a unity bug ;)
[21:50] <bdrung> ari-tczew: you can build it with "bzr bd"
[21:52] <ari-tczew> s/a/an unity bug - english typo ;)
[21:52] <ari-tczew> cyphermox: ^^
[21:52] <cyphermox> indeed. thanks ;)
[21:52] <ari-tczew> You're welcome.
[21:54] <bdrung> tumbleweed: should i call ubu_email() in sponsor-patch?
[21:55] <cjwatson> ari-tczew: actually, "a unity bug" is correct - it's the initial sound that matters, not the initial letter, and "unity" starts with a /y/ sound
[21:57] <ari-tczew> cjwatson: in Poland teach to write 'an' before vowels :>
[21:57] <bdrung> ari-tczew: "teach"?
[21:57] <RAOF> It's not a *bad* herustic :)
[21:57] <cjwatson> that's a reasonable rule of thumb but it fails in cases where the initial sound is consonantal anyway, like this
[21:57] <ari-tczew> bdrung: teachers say to write...
[21:58] <bdrung> RAOF: heuristic?
[21:58] <RAOF> bdrung: Fancy rule of thumb!
[21:59] <micahg> RAOF: I think he was referring to the fact that you said herustic
[21:59] <bdrung> RAOF: my heuristic translates your "herustic" to "heuristic"
[21:59] <RAOF> Ah.
[21:59] <RAOF> :P
[21:59] <RAOF> Spelling, as always, is for the week.
[22:00] <tumbleweed> bdrung: I doubt it, unles s you use the uploader's email address to locate a gpg key
[22:00] <bdrung> my brain to finger interface is broken too
[22:01] <bdrung> tumbleweed: but syncpackage should do it, right?
[22:02] <bdrung> "sponsor-patch 1" crashed. what does this tell us?
[22:03] <ari-tczew> bdrung: how can I use sponsor-patch from trunk? can I copy files manually or rather branch locally and run ??
[22:03] <tumbleweed> bdrung: same issue, you aren't editing a changelog.
[22:03] <tumbleweed> ari-tczew: check out trunk; ./sponsor-patch
[22:03] <bdrung> ari-tczew: or build the package with "bzr bd" and install it
[22:04] <ari-tczew> bdrung: I don't understand, bzr bd on cnetworkmanager?
[22:04] <kklimonda> ari-tczew: teachers don't really do that - your may, but it's not really fair to generalize like that.
[22:04] <bdrung> ari-tczew: in trunk
[22:15] <tumbleweed> bdrung: pushed up some deprecation stuff in config-681693 r913
[22:16] <ari-tczew> bdrung: okay fixed, thanks
[22:16] <ari-tczew> now I have a problem
[22:16] <ari-tczew> where are the files?
[22:16] <ari-tczew> I have to got .changes file to upload
[22:16] <tumbleweed> ari-tczew: in /tmp/sponsor-patch-SOMEHTING
[22:16] <bdrung> ari-tczew: what command did you call?
[22:17] <ari-tczew> $ ~/bin/sponsor-patch 677589 -u -v -kari-tczew@ubuntu.com
[22:17] <ari-tczew> bdrung: I branched u-d-t trunk and linked sponsor-patch into ~/bin
[22:18] <bdrung> ari-tczew: -u requires an upload target
[22:18] <ari-tczew> bdrung: hm?
[22:18] <bdrung> ari-tczew: for sponsoring -s should be used (which is "-u ubuntu -b")
[22:18] <ari-tczew> could you give an example?
[22:18] <bdrung> ari-tczew: example in man page :)
[22:19] <ari-tczew> bdrung: please, I'm not lying on the time...
[22:19] <bdrung> ari-tczew: and i don't want to type everything twice
[22:20] <bdrung> sponsor-patch 677589 -s -v -kari-tczew@ubuntu.com
[22:20] <ari-tczew> tumbleweed: dpkg-source: ostrzeżenie: błąd weryfikowania sygnatury w /tmp/sponsor-patch-PsgDvt/cnetworkmanager_0.21.1-1.1ubuntu1.dsc
[22:21] <tumbleweed> ari-tczew: you may want to configure your gpg with a default key to save you lots of -k typing. bdrung: Maybe we should guess -k parameters from ubu_emial in many places.
[22:21] <ari-tczew> tumbleweed: bash: cd: /tmp/sponsor-patch-PsgDvt: No such file or directory
[22:21]  * micahg just made a bash alias for key sponsoring
[22:21] <tumbleweed> it deletes it when it has finished running
[22:22] <ari-tczew> tumbleweed: are you kidding me? how can I get these files if this script is deleting at the end?
[22:22] <tumbleweed> ari-tczew: very recent change (a couple of revisions ago). You can tell it to work in a specific place, then it won't delete.
[22:22] <bdrung> tumbleweed: good idea
[22:22] <ebroder> ari-tczew: If you would just use -s like bdrung suggests, it will upload for you, but it will always ask you first
[22:22] <bdrung> ari-tczew: in most cases you want to do an upload
[22:24] <ari-tczew> tumbleweed: would be nice if sponsor-patch will create files in direcotry where I am ($ pwd)
[22:24] <bdrung> ari-tczew: sponsor-patch -w .
[22:24] <ebroder> Or set UBUNTUTOOLS_WORKDIR=. and it will always do that, right?
[22:24] <tumbleweed> bdrung: only danger of it is that people who've rotated keys will have multiple keys with the same email address.
[22:25] <bdrung> ebroder: yes
[22:25] <tumbleweed> ari-tczew: that's what it did previously, now you have to tell it to do that.
[22:25] <ari-tczew> tumbleweed: how can I set my gpg to use always my e-mail address?
[22:25] <bdrung> tumbleweed: i found a grave bug: if you use -u and set it to something else than "ubuntu" it wont upload it.
[22:25] <tumbleweed> ari-tczew: default-key in gpg.conf
[22:26] <tumbleweed> bdrung: oh yeah I forgot about that
[22:26] <bdrung> ari-tczew: i set DEBSIGN_KEYID is ~/.devscripts
[22:26] <bdrung> s/is/in/
[22:28] <bdrung> tumbleweed: that's why "sponsor-patch 677589 -u -v" didn't fail. it should fail with "can't upload to '-v'"
[22:29] <tumbleweed> ari-tczew: thanks for your bugfinding :)
[22:29] <ari-tczew> bdrung: can I specify e-mail address in DEBSIGN_KEYID?
[22:30] <bdrung> ari-tczew: i specified the key id
[22:30] <tumbleweed> I would assume so. gpg can generally take email addresses or ids
[22:30] <bdrung> which should lead to the same result
[22:33] <ari-tczew> bdrung, tumbleweed: if I'm stopping sponsor-patch by ctrl + c, then I'm getting an traceback. it should show only 'Aborted.' or something
[22:33] <ari-tczew> http://paste.ubuntu.com/546413/
[22:33] <tumbleweed> agreed (and that's an issue you'll see in many less-complex python scripts)
[22:34] <ebroder> ari-tczew: I don't agree with that
[22:34] <tumbleweed> ebroder: you want to know where it failed?
[22:34] <bdrung> ebroder: why?
[22:34] <ebroder> I see Ctrl-c as a more external failure than something like "dch failed". As soon as the program starts trying to be clever about those sorts of external failures, it becomes a lot harder to debug them when they occur
[22:35] <ebroder> Like, a program returning non-0 is an "expected" failure in some ways
[22:35] <ebroder> Whereas KeyboardInterrupt isn't
[22:36] <tumbleweed> on a slow connection, sponsoring a big package, keyboardinterrupt isn't that unexpected (but you don't know where to catch it, so you need to wrap main in try..except.
[22:36] <ebroder> I guess I might be OK with a KeyboardInterrupt handler, but I definitely don't want to see something like a try..except that catches all exceptions, or even all Exception subclasses
[22:37] <tumbleweed> ebroder: yeah, with you on that. (And personally I'd rather see th traceback most of the time, but it's probably scary for some)
[22:37] <bdrung> ebroder: would catching KeyboardInterrupt have any bad side effect?
[22:38] <bdrung> tumbleweed: is it possible to print "User abort in $command."?
[22:38] <ebroder> At the top-level? No, you'd just want to be sure to still exit non-0
[22:38] <ebroder> You just do if __name__ == '__main__': try: main() except KeyboardInterrupt: sys.stderr.write('User aborted\n'); sys.exit(1)
[22:39] <ebroder> Detecting where the abort happened is quite a bit more difficult
[22:39] <tumbleweed> bdrung: yes you can dig into the traceback in the handler
[22:39] <ebroder> Eww :)
[22:39] <tumbleweed> yes
[22:39] <ari-tczew> bdrung: your suggested command (sponsor-patch 677589 -s -v) wanted to build in pbuilder!
[22:40] <tumbleweed> ari-tczew: that's the default test-builder
[22:40] <ebroder> ari-tczew: Yes, read the manpage
[22:40] <bdrung> ari-tczew: then specify a other builder
[22:40] <ari-tczew> I don't want to build :
[22:40] <ari-tczew> :/
[22:40] <ebroder> Dude, all this stuff is well-documented in the manpage
[22:40] <bdrung> ari-tczew: reading the man page would really help
[22:40]  * ari-tczew hopes that will sponsor one patch today yet
[22:41] <bdrung> ari-tczew: you sponsor without building it before?
[22:41] <ari-tczew> bdrung: wrrrr... I wrote at the start, that I've reviewed and built this one!
[22:41] <ari-tczew> let me scroll up to copy log
[22:43] <ebroder> ari-tczew: So far you've asked us lots of workflow questions about sponsor-patch that are all documented in the manpage, and at this point you've taken more of our time for answering your questions than it would take you to read the manpage and figure out how to do what you're trying to do.
[22:43] <ari-tczew> ebroder: I'm a person on who manpages doesn't work. (not technically, just I can't get manpages on my mind)
[22:44] <ebroder> Did you try?
[22:46] <bdrung> tumbleweed: "Deprecated configuration variable", but which variable should be used?
[22:46] <ari-tczew> ebroder: when I'm reading a manpage, I got a feelling like wearing long johns
[22:46] <bdrung> tumbleweed: "print >> stderr" - should we use Logger instead?
[22:47] <tumbleweed> bdrung: yeah, that was my first impulse, but unless logger is configured (which is not ubuntutools.config's problem), its output isn't very pretty
[22:48] <tumbleweed> I suppose it could gain some logger-configuring features
[22:48] <tumbleweed> ari-tczew: seriously, you need to be able to read manpages. People get tired of helping people who don't help themselves.
[22:49] <bdrung> tumbleweed: really? logger only needs the verbose mode set correctly, but this doesn't matter for warnings
[22:55] <bdrung> tumbleweed: we should convert all python scripts to PEP8 (after merging your branch)
[22:55] <tumbleweed> yeah
[22:57] <tumbleweed> yes, setting a basicConfig should be enough. and it only applies the first time it's called, so scripts can still do what they want.
[22:58] <ari-tczew> bdrung: look at http://paste.ubuntu.com/546416/
[22:58] <ari-tczew> I know that I used option -w wrong but whether is it a bug?
[22:59] <bdrung> ari-tczew: lemme investigate
[23:01] <bdrung> ari-tczew: the error is that you set your working dir to: ='~/zainstalowane/paczki/ubuntu/cnetworkmanager'
[23:01] <bdrung> ari-tczew: correct would be sponsor-patch 677589 -s -v -b -w '~/zainstalowane/paczki/ubuntu/cnetworkmanager'
[23:03] <tumbleweed> bdrung: workdir might need to take package name substitutions
[23:03] <bdrung> tumbleweed: package name substitutions?
[23:04] <tumbleweed> ~/zainstalowane/paczki/ubuntu/cnetworkmanager -> ~/zainstalowane/paczki/ubuntu/%(source)s
[23:05] <bdrung> tumbleweed: you can implement and document it if you want that feature
[23:06]  * tumbleweed files a bug for now
[23:07] <ari-tczew> bdrung, tumbleweed, ebroder: I've readed 'man sponsor-patch' and I still don't know how can I drop building.
[23:08] <ari-tczew> It's like communist requirement.
[23:08] <tumbleweed> don't specify -b?
[23:08] <bdrung> ari-tczew: "-s" is equivalent to "-u ubuntu -b" and -b means building. so you can use "-u ubuntu" to upload, but not build it
[23:09] <ari-tczew> bdrung: well, can't I buld *.changes file without building and without uploading?
[23:09] <bdrung> ari-tczew: then drop any "-s" "-u" "-b"
[23:09] <bdrung> just specify a workdir
[23:14] <bdrung> tumbleweed: two things before merging: 1) what speaks against using Logging.warning instead of printf? 2) does the deprecation warning list all possible variables? "Use TEST_foo or UBUNTUTOOLS_foo instead."
[23:15] <bdrung> tumbleweed: 3) i prefer "import sys" over "from sys import argv, stderr" to make it clear where the function come from
[23:16] <tumbleweed> bdrung: 1. I'm busy doing something about logging 2. OK 3. Yes that was necessary for the test-suite hackery.
[23:16] <ari-tczew> bdrung: will sponsor-patch do all things related to bzr without -s option?
[23:17] <tumbleweed> ari-tczew: it only pushes back the branch if you've uploaded to Ubuntu.
[23:19] <ari-tczew> tumbleweed: ok, now I;m going to upload *.changes file and it won't deal with sponsor-patch. what next with bzr branch?
[23:20] <tumbleweed> ari-tczew: https://wiki.ubuntu.com/DistributedDevelopment/Documentation/UploadingAPackage
[23:20] <bdrung> ari-tczew: why don't you use "sponsor-patch -u ubuntu" if you upload the changes file anyway?
[23:20] <ari-tczew> bdrung: I had to test set default key in gnupg.
[23:21] <ari-tczew> tumbleweed: I just want to workaround these steps ;))
[23:21] <ari-tczew> I guessed that it's available with sponsor-patch.
[23:22] <bdrung> ari-tczew: you can see the commands in "sponsor_patch/main.py" ;)
[23:24] <ari-tczew> bdrung: lines 473-488 includes what I mean!
[23:34] <ari-tczew> bdrung: again failed... http://paste.ubuntu.com/546426/
[23:34] <ari-tczew> I won't finish it today.
[23:37] <kklimonda> then just do it by hand
[23:38] <bdrung> ari-tczew: i am currently fixing that
[23:39] <bdrung> ari-tczew: gimme 5 mins
[23:39] <ari-tczew> how do you share script which is broken?
[23:40] <bdrung> ari-tczew: it's not broken for my use cases. some code paths are not tested properly, because u-d-t lacks a test infrastructure
[23:50] <ari-tczew> bdrung: wait wait... now gimme 5 minutes
[23:50] <bdrung> ari-tczew: last test before push (i don't want you to complain again)
[23:52] <ari-tczew> does anybody know how can I force my bzr to remember my password?
[23:53] <bdrung> ari-tczew: pushed
[23:53] <bdrung> ari-tczew: bzr ask you for a password?
[23:53] <ari-tczew> bdrung: yes. always!
[23:53] <bdrung> ari-tczew: i was newer asked. what is the exact message?
[23:54] <ari-tczew> bdrung: Enter passphrase for key '/home/ari/.ssh/id_rsa':
[23:55] <bdrung> ari-tczew: it's your ssh config
[23:55] <ari-tczew> bdrung: It's started after switch to kde :/
[23:56] <bdrung> ari-tczew: kde probably doesn't use gnome-keyring
[23:56]  * ari-tczew is killed