[02:15]  * gilbert is trying unity on 11.10, and isn't going completely mad
[02:16] <gilbert> progress, ooh
[02:17] <gilbert> but why oh why oh why can't i modify the panel??? come on...
[02:20] <gilbert> wrong chan :( oops
[02:20] <gilbert> disregard
[08:01] <dholbach> good morning
[10:01] <micahg> anyone have the URL handy that searches UDD for uploads by an individual?
[10:21] <Guest51058> ooh, I like this nick!
[10:21] <Laney> boring :(
[10:22] <micahg> Laney: hi, do you have that link handy where I can look up my uploads in UDD?
[10:22] <Laney> ooh, err, ooh
[10:23] <Laney> the sponsoring thing? tumbleweed did that
[10:23] <micahg> yeah, ok, I wasn't sure who did that, let me see if I can find it now then
[10:24] <Laney> http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi
[10:24] <Laney> micahg: that?
[10:24] <micahg> yes :), thanks
[10:24] <Laney> thank god for browser history
[10:25] <micahg> yeah, was lacking in mine and I thought I bookmarked it
[10:25]  * micahg needs to find who to hassle for endorsement
[10:25] <micahg> *endorsements
[10:25] <micahg> s/hassle/ask nicely/ :D
[10:26] <Laney> heh
[10:54] <micahg> tumbleweed: http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi seems to not show sponsors anymore
[11:01] <broder> micahg: it looks like the sponsors import is broken
[11:01] <broder> the ubuntu_upload_history table seems to just have "N/A" for signed_by_name
[11:03] <broder> http://pastebin.ubuntu.com/752368/
[11:06] <Laney> BLAST!
[11:10] <Laney> erm
[11:10] <Laney> https://launchpadlibrarian.net/86055975/facter_1.6.2-1ubuntu1_source.changes
[11:10] <Laney> no signed-by?
[11:11] <tumbleweed> oh, right, sanity checking? who does that? :)
[11:11] <Laney> epic fail
[11:11] <Laney> https://lists.ubuntu.com/archives/precise-changes/2011-November/003573.html
[11:11] <Laney> it is in the first part but not the changesfile
[11:12] <tumbleweed> well it's in the gpg signature in the changesfile
[11:12] <Laney> which you don't have in changesFileUrl()
[11:13] <Laney> woe is us
[11:13] <tumbleweed> oh, that's problematic
[11:13] <tumbleweed> must be in the spph, though
[11:14] <Laney> the worst part is
[11:14] <Laney> http://anonscm.debian.org/gitweb/?p=users/laney/ubuntu-upload-history.git;a=blob;f=munge_ddc.py;h=11b3d28818110d84f23859de0b3e64fae80fcfed;hb=HEAD#l130
[11:15] <tumbleweed> the "some reason" is quite logical...
[11:15] <Laney> :P
[11:16] <Laney> i meant that i knew about it
[11:16] <Laney> and then promptly forgot said knowledge
[11:16] <tumbleweed> right, so did I :/
[11:17] <Laney> reimport time!
[11:17] <tumbleweed> you think I can do it in one go?
[11:18] <Laney> launchpad downtime might get you
[11:18] <tumbleweed> yeah :/
[11:19] <tumbleweed> I'll do per-release again
[11:19] <Laney> we should sanity check the dates
[11:20] <Laney> there was only ~10 uploads with borked ones so it's not too bad to ignore them
[11:20] <tumbleweed> can we not trust date_created?
[11:20] <Laney> i guess fall back to that
[11:20] <tumbleweed> or date_published even
[11:21] <tumbleweed> hard to sanity check, though
[11:23] <Laney> parsedate_tz doesn't :(
[11:24] <tumbleweed> if you want proper TZ handling in python you want dateutil and/or pytz
[11:29] <Laney> also doesn't validate it
[11:29] <Laney> i think the errors come from postgres itself
[11:31] <tumbleweed> oh, I didn't see the errors you were getting
[11:32] <Laney> they were when importing
[11:33] <tumbleweed> yes, what sort of problems?
[11:33] <Laney> #ubuntu-motu.log-20111124:23/11 00:26:02 <Laney> psycopg2.DataError: time zone displacement out of range: "Thu, 12 Oct 2006 22:43:00 +2000"
[11:33] <Laney> like that
[11:35] <tumbleweed> oh, /me remembers
[14:53] <tumbleweed> Laney: are you doing anything about ubuntu-upload-history (I'm about to start looking at it)
[14:53] <Laney> not atm, feel free
[15:42] <tumbleweed> Laney: how about this: If abs(Changes Date - Date Created) > 24 hours, use Date Created ?
[15:42] <Laney> are there legitimate situations when that might be true?
[15:43] <tumbleweed> stuck in a queue?
[15:43] <Laney> the +2000 case might not even be caught by that
[15:43] <tumbleweed> embargoed uploads?
[15:43] <tumbleweed> that's catchable by hand
[15:43] <Laney> you could just try to parse it
[15:44] <Laney> some of them were e.g. typoed days and months
[15:44] <Laney> which should hopefully fail to parse
[15:44] <tumbleweed> but there were also things that were clearly wrong
[15:44] <Laney> and then check the tz is within a valid range
[15:44] <tumbleweed> i.e. out by months
[15:44] <Laney> then making your check much longer (say 2 weeks) should be a good compromise
[15:45] <tumbleweed> ok, I like that
[15:45] <Laney> I bet if the parser is lazy that it would accept invalid days though
[15:45] <Laney> as those are technically redundant
[15:45] <tumbleweed> render it back to a string and compare?
[15:46] <Laney> sounds good
[15:46] <tumbleweed> hrm, we don't have dateutil on syklone
[15:46]  * tumbleweed tries to work out if we need it
[15:53] <tumbleweed> Laney: hrm, dateutil does sanity-check the TZ, but allows a greater range
[15:53] <tumbleweed> -1439 to 1439
[15:54] <tumbleweed> (minutes)
[15:58] <Laney> another alternative is to let the udd importer skip invalid records
[15:59] <tumbleweed> it's fine, I can easily enforce a tighter restriction here
[16:23] <tumbleweed> Laney: ok, running a smallish import of karmic from the beginning of 2009-10 (that'll also cover some odd e-mail addresses) http://people.ubuntuwire.org/~stefanor/out/
[16:24] <Laney> cool
[16:24] <Laney> what did you do about the emails?
[16:25] <tumbleweed> http://anonscm.debian.org/gitweb/?p=users/stefanor/ubuntu-upload-history.git;a=commitdiff;h=ab8f776c22ac367c28caa6fd2405d22d83557146
[16:25] <Laney> WARNING:lp-udd:Date does not render back to itself: Mon,  12 Oct 2009 15:47:58 +0100 != Mon, 12 Oct 2009 15:47:58 +0100. Going with date_created
[16:25] <Laney> can we handle that?
[16:25] <tumbleweed> I'm putting Signed-By on every record, seem sensible?
[16:26] <tumbleweed> yes, we could special-case that
[16:26] <Laney> I guess signed_by <> 'N/A' was never good enough on its own, so I guess so
[16:31] <tumbleweed> re-importing with double spaces special-cased
[17:25] <l3on> cjwatson, hey... are you working on flphoto?
[17:28] <cjwatson> lenios_: yes
[17:28] <cjwatson> er
[17:28] <cjwatson> l3on: yes
[17:28] <l3on> ah ok :) I see it fails :P
[17:28] <l3on> ok, don't worry.... let's see something else... :)
[17:28] <cjwatson> yes, I know, I'm working through the failures
[17:29] <l3on> flphoto for example...
[17:29] <l3on> ops sorry -.-
[17:29] <cjwatson> the failures in flphoto I mean
[17:29] <cjwatson> just a bit tedious
[17:29] <l3on> can I take git-annex  ?
[17:31] <cjwatson> it's possible git-annex might succeed if retried
[17:31] <cjwatson> run it through pbuilder or something to chekc?
[17:31] <cjwatson> *check
[17:31] <cjwatson> it might have got caught up in the perl and imagemagick transitions
[17:32] <l3on> ok... let's see :)
[17:32] <Laney> still fails
[17:34] <Laney> sid version does too
[17:37] <cjwatson> it looks like a bug in whatever library that is it's using though?
[17:38] <Laney> i would say so
[17:40] <cjwatson> flphoto fix uploaded
[17:48] <l3on> Yep.. I'm going to test "perl -e 'use Image::Magick'" in precise
[17:48] <l3on> because in oneiric builds fine
[17:50] <cjwatson> Given all the transitions, problems in this area aren't especially surprising
[17:59] <Laney> that file hasn't been linked properly
[18:09] <l3on> hey men... I found the problem about myodbc ...
[18:09] <l3on> in precise we have libmysqlclient-dev > 5.1
[18:10] <l3on> and myodbc seems to build only with libmysqlclient-dev <= 5.1
[18:10] <l3on> in other words, in precise control should set "libmysqlclient16-dev" instead of "libmysqlclient-dev"
[18:10] <l3on> what the best way to do that?
[18:11] <l3on> and... debian sees libmysqlclient-dev > 5.1 in experimental... we have to file bug in debian or just merge in ubuntu for now ?
[18:12] <micahg> l3on: no, libmysqlclient16-dev is going away, we need it to build with libmysqlclient-dev (or 5.5)
[18:12] <l3on> micahg, ok... I'm going to figure out ...
[18:13] <micahg> libmysqliclient-dev should be libmysqlclient18-dev ATM
[18:13] <micahg> l3on: thanks :)
[18:13] <l3on> yes, you're right
[18:36] <l3on> hey micahg ... why don't we use myodbc 5.1.9 ?
[18:37] <l3on> I'm looking at code and bug has fixed there...
[18:38] <micahg> l3on: Debian hasn't updated yet?  you can certainly propose a merge/debdiff with that update, might want to check with Spamaps in #ubuntu-devel first so as not to duplicate work
[18:38] <l3on> upstream changelog says http://paste.ubuntu.com/752778/
[18:38] <l3on> ok.. I'm going..
[18:47] <l3on> what diff between this channel and ubuntu-devel ?!
[18:48] <l3on> should I join both to get involved in ubuntu development cycle ?!
[18:50] <micahg> l3on: well, this channel is more geared towards universe/multiverse packages and mentoring, whereas ubuntu-devel is focused on main/restricted, patch piloting, and other development related discussions (such as transitions)
[19:26] <l3on> mmm... in precise:
[19:27] <l3on> perl -e 'use Image::Magick'
[19:27] <l3on> perl: symbol lookup error: /usr/lib/perl5/auto/Image/Magick/Magick.so: undefined symbol: MagickCoreGenesis
[20:18] <broder> oh hey - the backports pocket does enforce some form of archive upload permissions! "tomcat6_6.0.18-0ubuntu3.3~hardy1_source.changes rejected [...] Signer is not permitted to upload to the component 'main'."
[20:24] <micahg> :)
[20:25] <tumbleweed> Laney: finished running
[20:41] <l3on> hey guys... could you explain me something ? :)
[20:41] <l3on> I would understand... how to fix -as-needed ..
[20:42] <tumbleweed> l3on: https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition
[20:42] <l3on> what I get is: put libs "-laaabbb" alway after "-o output" ...
[20:42] <l3on> tumbleweed, I'm reading that :)
[20:42] <tumbleweed> no. put -laaabbb after foo.o
[20:42] <l3on> but.. what is not clear... what to do with '-L' ?
[20:42] <l3on> yeah yeah tumbleweed, I wrote it wrong... :)
[20:43] <tumbleweed> -L probably doesn't matter here
[20:43] <l3on> ok, let's try :)
[20:44] <tumbleweed> how exactly you go about fixing the build failure will depend on the package
[20:44] <tumbleweed> most common cause is people misusing LDFLAGS
[20:44] <l3on> tumbleweed, problem here is not a fail in building, but something wrong at runtime
[20:44] <l3on> bug 897380
[20:45] <tumbleweed> right, that's common for plugins, where we expect some symbols to not be resolved in the shared library
[20:46] <tumbleweed> if only more packages had test suites...
[20:47] <tumbleweed> Laney: just as well I ran that test, the weird e-mail addreses were in the changes files not lp. Duh!
[23:57] <Laney> l3on: I informed mterry about that, don't know if he was looking at it but you might want to check
[23:57] <Laney> tumbleweed: yeah, that's where all of the dubious data is
[23:58]  * tumbleweed ran another test, but it got killed by ubuntuwire admins trying to add more disk space :)