[00:00] <cprov> fta: are you okay with it ?
[00:04] <fta> cprov, will I be able to push the same tarball again? ie, without bumping the version?
[00:05] <cprov> fta: yes, even 'undelete' the same version if you discover that the problem is somewhere else.
[00:07] <fta> it's strange as that part of my code hasn't change in a while all ppa builders were fine before
[00:14] <fta> cprov, did builders changed shell recently ? like bash vs dash or something ?
[00:15] <cprov> fta: I don't know for sure, not recently IIRC
[00:15] <Hobbsee> er, is something wrong with the build allocator?
[00:16] <Hobbsee> like the 17 amd64 builds in the queue, and the 6 idle buildds?
[00:17] <stdin> all of them just finished building a minute ago
[00:19] <Hobbsee> oh, there we go.  now the others have some
[00:24] <fta> Hobbsee, those were my 9 songbird builds killed by cprov :P
[00:24] <Hobbsee> fta: ah.
[00:24] <Hobbsee> fta: would you try *not* to break the buildds?  :P
[00:26] <fta> i can't understand why it froze, looks like a bug in cdbs but i seriously doubt it, not on 3 distros at once.
[00:28] <Hobbsee> does it happen if it's not a .bz2 file used?
[00:30] <fta> it used to work just fine, ex: https://edge.launchpad.net/~fta/+archive/+build/749544
[00:34] <wgrant> It's Mozilla. What do you expect?
[00:43] <jml> wgrant: *really* complicated legal issues.
[00:45] <fta> what am i supposed to do now ? give up ?
[00:47]  * Hobbsee hands fta a larger hammer
[00:52] <fta> cprov, what did you mean by 'undelete' the same version ?
 Why are there .tar.bz2s in there? <= embedded tarballs
[01:00] <kiko> fta, not sure either. hmmm
[01:03] <wgrant> fta: Why is there an embedded xulrunner? Security people will eat you alive.
[01:04] <wgrant> fta: You can copy the deleted source back into your PPA, effectively undeleting it.
[01:05] <Hobbsee> wow, really?  That's an interesting workflow.
[01:06]  * Hobbsee wonders how many people have figured out to use that, and wonders how many other such interesting workflows there are, waiting, undiscovered
[01:06] <wgrant> One can't really just mangle the old publishing. That would be ugly.
[01:07] <Hobbsee> being able to copy something that's "deleted" is also ugly.
[01:07]  * Hobbsee empties the trash, the trash is gone.  I can't do anything else with it.  Why is LP different?
[01:07] <Hobbsee> i'm sure it can be useful, at times - but damn, it's rather counterintuitive!
[01:07] <wgrant> You should know by now that you can't delete anything unless it's in launchpad-bazaar.
[01:10] <fta> wgrant, there's an embedded xul because it is patched afterwards by songbird. it's not different from other xulapps, such as flock, instandbird, openkomodo, and many more
[01:10] <wgrant> Oh dear god.
[01:11] <wgrant> That's really not cool.
[01:11] <fta> we are trying to fight against that but so far, only firefox is ready to have the xul engine outside
[01:12] <kiko> wgrant, real life is full of reality :) the xul runner isn't quite there yet..
[01:12] <fta> in fact, the xul sdk is heavily patched by a lot of upstream projects
[01:13] <fta> so far, xul is mainly driven by firefox and to some extents, by thunderbird and seamonkey
[01:14] <fta> so all the other xul users have their own patches
[01:15] <wgrant> WHy haven't they sent them upstream?
[01:15] <kiko> oh, they do. but I think there are a few design issues and these patches aren't exactly quick to review
[01:15] <fta> wgrant, they did, but there are zillions of patches are waiting in bugzilla
[01:15] <fta> -are
[01:18] <fta> kiko, i don't know what i should do with songbird now. i need a clue of what is going on from the inside. a strace or something.
[01:18] <kiko> fta, one of the problems is that we don't easily have access to the buildds
[01:18] <fta> hm
[01:18] <kiko> though.. lamont` aya?
[01:18] <wgrant> Doesn't cprov have lots of access to the PPA builders?
[01:18] <kiko> I don't think he does
[01:19] <kiko> but lamont` is a safer bet for help
[01:19] <wgrant> Hm, I thought he did, but /me will trust you on that.
[01:21] <fta> kiko, so no songbird for you today, i'm afraid.
[01:22]  * wgrant bashes the SP home page for losing useful information.
[01:22] <kiko> fta, snif. but we'll get to the bottom of it tomorrow
[01:22] <fta> too bad because it's really nice
[01:22] <kiko> fta, it's a weird thing. an admin being around will help though
[01:22] <kiko> yeah, I hear it is -- jdahlin is all ravin about it here in the office
[01:23] <fta> i have a deb for i386/jaunty if you want :)
[01:23] <kiko> I'm not THAT brave no matter what my scars might suggest!!
[01:24] <fta> ok, np.
[01:24] <wgrant> kiko: Pfft, we're way past Alpha 1!
[01:24] <kiko> okay let's get some rest
[01:24] <kiko-zzz> but catch you tomorrow!
[01:24] <wgrant> Night.
[01:24] <fta> me too. 2am+ here
[01:24] <fta> ++
[01:24] <kiko-zzz> fta, I appreciate the effort on your end though
[01:24] <kiko-zzz> many thanks
[01:25] <kiko-zzz> will look into it tomorrow
[01:25] <fta> thanks
[01:36] <hggdh> heh. rutadeeavuacion is back
[01:36] <hggdh> sigh, cannot event write the name of the sucker right...
[01:37] <hggdh> 29 new bugs by him/her
[01:38] <wgrant> There is no spm :(
[01:38] <wgrant> Ursinha: ^^
[01:38] <Hobbsee> hggdh: he's only going to go away when they manage to get the bugs out of hte account locking.
[01:38] <wgrant> I haven't seen a fix for that yet.
[01:38] <hggdh> Hobbsee, I know. I wonder if he is just trying to piss us off
[01:38] <Hobbsee> hggdh: likely
[01:38] <wgrant> maurizio-live is the account in question this time.
[01:39]  * hggdh bets the sucker about 13 years -- full of testosterone, and no real functional brain
[01:40] <Ursinha> hggdh, wgrant, back, again?
[01:40] <wgrant> hggdh: I was a perfectly useful community member at 13.
[01:40] <wgrant> Ursinha: As usual.
[01:40] <hggdh> Ursinha, yay
[01:40] <Ursinha> haha no real functional brain
[01:40] <hggdh> wgrant, there are always exceptions to the rule
[01:40]  * hggdh was not one
[01:40] <jml> my brain uses monads for extra functional power.
[01:41] <wgrant> Ursinha: Is there any progress on the fix to make account deactivation actually work?
[01:41] <mthaddon> have just disabled that user again...
[01:41] <wgrant> mthaddon: Thanks.
[01:41] <Ursinha> mthaddon, thanks
[01:41] <wgrant> How long until it reactivates it, I wonder.
[01:42] <hggdh> by know he knows the drill
[01:42] <Hobbsee> time it takes for him to realise he's logged out + a few seconds + 3 mins to exploit the LP bug to reactivate it + another minute to log in
[01:42] <Hobbsee> so, probably, not long.
[01:42] <hggdh> are the bugs going to be, huh, auto-rejected?
[01:43] <wgrant> I would hope they have the script to mark private and remove all subscribers by now.
[01:43] <Hobbsee> apparently launchpad doesn't have that functionality either, when I asked about it.
[01:43] <Hobbsee> but, if there's another answer, it'd be great ;)
[01:44] <hggdh> ah, back to linking blueprints
[01:45] <wgrant> Excellent.
[01:45] <wgrant> I must file a bug about that.
[01:45] <wgrant> Private bugs show up there.
[01:45] <Hobbsee> oh, do they?
[01:45] <Hobbsee> wonderful
[01:45] <hggdh> clamav has lotsa of them
[01:46] <hggdh> https://blueprints.launchpad.net/ubuntu/+spec/clamav-spamassassin-in-main
[01:46] <Hobbsee> mthaddon: there's no functionality to keep a user's account alive, but not let them post anything, is there?
[01:46] <mthaddon> Hobbsee, fraid not
[01:47] <Hobbsee> mthaddon: pity.  Perhaps there needs to be a new category for that, rather than just disabling the accounts, or something.
[01:48] <mthaddon> Hobbsee, I think it'd be better to be able to disable an account and prevent it being re-enabled (i.e. blacklist email addresses, perhaps)
[01:48] <Hobbsee> mthaddon: perhaps.  And IP or something, i'd hope
[01:48] <Hobbsee> email addresses are cheap.
[01:48] <mthaddon> Hobbsee, yeah, IPs can be changed too - but I agree, would be a good facility to have
[01:49] <Hobbsee> .htaccess?  :P
[01:50] <mthaddon> Hobbsee, we don't use apache in that way :)
[01:50] <Hobbsee> mthaddon: i'm sure you could find an equivalent :P
[01:50] <mthaddon> yeah...
[02:59] <meoblast001> hi
[02:59] <meoblast001> is launchpad opensource?
[03:04] <beuno> meoblast001, not yet
[03:04] <beuno> next year
[03:04] <meoblast001> for real?
[03:04] <beuno> we're in the process of shaping things to be able to release it
[03:04] <beuno> yeap
[03:04] <meoblast001> YAY
[03:05] <meoblast001> cuz i have a "team" thats outragously small that uses launchpad
[03:05] <meoblast001> we do opensource and eventually will do a few proprietary too
[03:05] <meoblast001> but the current LP setup doesnt like proprietary
[03:05] <beuno> well
[03:05] <beuno> there's a service you can pay for to use launchpad with propietary projects
[03:06] <meoblast001> beuno, yeah thats a bit of a problem =P
[03:06] <meoblast001> im 15 and cant work due to child labor laws in the US
[03:06] <meoblast001> no money.... cant pay
[03:06] <beuno> right
[03:06] <beuno> well, you'll have to wait til next year
[03:06] <meoblast001> ok
[03:07] <meoblast001> dont have any proprietary apps planned for this year though
[03:07] <meoblast001> all opensource
[03:07] <beuno> cool
[03:08] <jamesh> jml: so, it turns out that the test sorting in testresources was completely busted up until last night.  If you're using it for anything, you might want to upgrade.
[03:08] <jml> jamesh: by "completely busted", what do you mean?
[03:08] <meoblast001> beuno, and i also fear dependence..... which the current launchpad setup makes me do
[03:09] <jamesh> jml: as in "did not do what it claimed to do"
[03:09] <meoblast001> beuno, if some crazy stock market crash miraculously made canonical go under... no more launchpad
[03:09] <jml> jamesh: because I've known about some pretty severe bugs in it for a while.
[03:09] <jml> jamesh: where it picked an arbitrary start node, for example.
[03:10] <jamesh> jml: it was ordering tests based on their distance from the start node only.
[03:10] <jamesh> distance being resource setup cost
[03:10] <jml> jamesh: oh wow.
[03:11] <jamesh> jml: trunk is fixed now (checking each test permutation), and I've got a branch pending to make it a bit faster and not rearrange tests unnecessarily
[03:11] <jml> jamesh: sweet.
[03:12] <jamesh> my branch just groups the tests by the resource combinations they use, then does the same brute force search on those resource combinations instead of on the tests
[03:12] <jamesh> which is a lot less work
[03:12] <jml> I thought I already did that :(
[03:13] <jml> it's possible that lifeless changed it around when he landed his recent sorting improvements.
[03:13] <jamesh> If you did, I didn't see it up on LP :(
[03:13] <jml> jamesh: hmm.
[03:13] <jml> jamesh: it's also possible that I thought it really loudly.
[03:14] <jamesh> jml: his initial sorting improvements just created a dummy 'start' node in the graph that represented "no resources"
[03:14] <jamesh> it was still using "distance from starting node" to sort though
[03:15] <jamesh> yesterday we moved from there to a locally optimised walk of the graph to the globally optimised sort it now uses.
[03:19] <jamesh> All your pending branches on LP seemed to be related to the resource handling rather than sorting code, so should be unaffected by these changes
[03:34] <jml> cool.
[04:51] <lamont`> kiko_: I'm afk and just passing through...
[05:10] <Chaosmagi>  Do u feel like your life is stuck in a rut, just going around in circles. Do u feel Spirituality left out then all u have to do is !!!!TAKE BACK REALITY!!!! www.ellis69.webs.com
[05:12] <jamesh> wow.
[05:13] <wgrant> I do, I do.
[05:21] <Ursinha> holy cow
[05:26]  * Hobbsee grumbles
[05:26] <Hobbsee> spm!
[05:26] <spm> Hobbsee: hows it going!
[05:27] <Hobbsee> spm: good, although it's surprisingly hard to get US money converted, apparently!
[05:28] <spm> Hobbsee: You're off to UDS I gather?
[05:28] <Hobbsee> spm: yup
[05:43] <jamesh> Hobbsee: just use an ATM at the airport
[05:43] <jamesh> that's what I generally do.
[05:43] <Hobbsee> jamesh: oh, i eventually got money :)
[05:43] <jamesh> if your card is on the visa or mastercard network, it shouldn't be hard to get cash
[05:44] <wgrant> That's what I plan to do (with a Cirrus keycard).
[05:44] <Hobbsee> that's true
[05:44] <Hobbsee> that's what I tend to do, after I get there.
[05:44]  * Hobbsee wonders how difficult it would be to get black hole contact addresses set.
[05:45] <wgrant> You'd have to blackhole it after setting it.
[05:45] <wgrant> Or convince somebody that a blackhole flag for teams is a good idea.
[05:45] <wgrant> Which it is.
[05:46] <Hobbsee> wgrant: well, seeing as it's for large-person teams, getting consensus on that (or even having a poll) is difficult.
[05:56] <Hobbsee> I wonder...is there an easy way to shut all the feisty tasks of https://bugs.edge.launchpad.net/ubuntu/feisty/+bugs ?
[05:57] <spm> drop table feisty_bugs?
[05:58] <Hobbsee> oh, that'd be nice:)
[05:59] <jamesh> web services API?
[06:00] <Hobbsee> will that work on that entire list of bugs, without having to type them all in?
[06:02] <wgrant> Probably.
[06:02] <spm> Hobbsee: I wish :-) It's possible some magic could be done? But suggest more likely not. Raise a question?
[06:02] <wgrant> I think searchTasks or similar should be exposed for all bug targets.
[06:02] <Hobbsee> spm: mmm...might be an idea.
[06:02]  * wgrant plays around with launchpadlib.
[06:02] <Hobbsee> wgrant: thanks
[06:02] <jamesh> Hobbsee: ideally you'd be able to find all the required bugs with the API
[06:03] <jamesh> if you can't, report a bug :)
[06:04] <wgrant> jamesh: Are you coming to UDS?
[06:04] <jamesh> yeah
[06:17]  * wgrant gives Launchpad a few good thwackings.
[06:18] <wgrant> The webservice strongly dislikes behaving properly.
[06:19] <wgrant> AFAICT, I'm trying to search for tasks properly. IDistroSeries only recently became exposed, and it doesn't work too well.
[06:19] <wgrant> searchTasks() on a current or supported distoseries OOPSes.
[06:19] <wgrant> searchTasks() on a development or obsolete distroseries returns 0 tasks, even when that's not right.
[06:19] <wgrant> Thankyou Launchpad.
[06:19] <jamesh> if you make enough OOPSes, someone should notice :)
[06:19] <Hobbsee> jamesh: well, he's trying for a non-supported release, ideally
[06:23]  * wgrant turns on debugging and gets an OOPS id.
[06:24] <wgrant> jamesh: Can you look at OOPS-1068S27 in a couple of minutes and tell me if I'm obviously doing something wrong and LP isn't validating properly, or if LP might just be genuinely broken?
[06:25] <wgrant> Oh. It's the getSeries that's failing.
[06:25] <wgrant> Hmmm.
[06:47]  * wgrant thwacks Launchpad for failing at security.
[06:47] <wgrant> Failing at security on security vulnerabilities, to make it even better.
[06:50] <jamesh> wgrant: that OOPS report is a NotFoundError for getSeries("8.1")
[06:52] <Hobbsee> should that be 8.10?
[06:52] <jamesh> Hobbsee: yes.  So either wgrant passed in a bad version number, or Launchpad handed him a bad number that he then passed back to LP
[06:58] <wgrant> Thankyou Optus.
[07:00] <wgrant> Is it just me, or is there significant latency in the replication on staging?
[07:04] <wgrant> jamesh: I just saw your comment on that OOPS report on irclogs.u.c... I'm fairly sure that I asked for 8.10, so maybe it's trimming things somewhere.
[07:04]  * wgrant watches the HTTP requests more closely this itme.
[07:06] <jamesh> wgrant: I wonder if a float is being used somewhere rather than a string?
[07:07] <wgrant> jamesh: Right, maybe the webservice code is trying to parse it as a float first... I definitely sent 8.10 over the wire in OOPS-1068S70, and I'm pretty sure I did in 27 too.
[07:08] <wgrant> win 39
[07:08] <wgrant> Damn.
[07:08] <jamesh> wgrant: you can probably pass in distro codenames to getSeries(), btw.
[07:08]  * Hobbsee hands wgrant a \
[07:08] <Hobbsee> and a /
[07:08] <wgrant> jamesh: Oh, I can, yes. I tried that after I saw your analysis.
[07:09] <wgrant> Thanks.
[07:10] <wgrant> ICVE needs some love :(
[07:10] <jamesh> wgrant: if you're sure you're using strings on the client side, perhaps file a bug report.
[07:10] <wgrant> jamesh: I plan to, once that OOPS appears and you can confirm it still says 8.1.
[07:10] <wgrant> And I guess it should be there now.
[07:10] <jamesh> wgrant: hmm.  I see the query string for the request is ws.op=getSeries&name_or_version=8.10
[07:10] <wgrant> Yep.
[07:11] <wgrant> That's what I see too.
[07:11] <jamesh> wgrant: in that case, I can confirm that it looks like a Launchpad problem :)
[07:11] <wgrant> jamesh: Excellent, thanks. I'll file it.
[08:20]  * wgrant is loving the test plans being public - it means defective feature designs can be shot down within hours of their merging!
[11:49] <tkamppeter> I need help, I have subscribed a wrong person to https://blueprints.edge.launchpad.net/ubuntu/+spec/printer-driver-auto-download-service
[11:49] <tkamppeter> and it seems a non-undoable feature.
[11:52] <wgrant> tkamppeter: Only the user themselves or a LOSA can remove a subscription.
[11:53] <intellectronica> tkamppeter: file a question, and an admin will tend to it asap
[11:54] <intellectronica> tkamppeter: also, you can just contact the user, apologize, and suggest that they unsubscribe themselves. most people would be quite understanding :)
[12:38] <glade88> hello, I noticed a text overflow at a notification box: http://img380.imageshack.us/img380/8672/overflowxl1.png
[12:39] <fta2> kiko_, ping
[12:47] <intellectronica> glade88: care to report a bug?
[12:47] <glade88> intellectronica: sure, a min
[12:47] <glade88> intellectronica: part of Launchpad registry, I gess?
[12:47] <glade88> s/gess/guess
[12:48] <intellectronica> glade88: take your time. report the bug on 'launchpad'
[12:48] <intellectronica> no, it's not a registry bug, it's a general launchpad bug
[12:48] <glade88> ah, ok.
[12:52] <glade88> intellectronica: https://bugs.edge.launchpad.net/launchpad/+bug/304795
[13:05] <intellectronica> glade88: cool, thanks
[13:05] <glade88> intellectronica: np
[13:41] <epsy> hi, how do I check if a tag(for a revision) was correctly set?
[13:55] <balor> What URL does  lp:bzr-cvsps-import resolve to?
[13:56] <LarstiQ> balor: it resolves to the branch the bzr-cvsps-import project on launchpad has pointed it's trunk at.
[13:56] <LarstiQ> balor: `bzr info lp:bzr-cvsps-import` will tell you what exactly that is.
[13:56] <gary_poster> balor: LarstiQ is right.  If you are using bzr, 'lp:' == 'bzr+ssh://bazaar.launchpad.net/'
[13:56] <balor> LarstiQ: But what's the actual URL of the bzr repo?  I think I need to expand it to get round my http_proxty.
[13:57] <balor> ah
[13:57] <balor> I need http access to the repo.
[13:57] <LarstiQ> gary_poster: bzr+ssh:// depends on wether you have write access to the branch or not.
[13:57] <gary_poster> LarstiQ: True
[13:57] <LarstiQ> balor: http://bazaar.launchpad.net/%7Ebzr/bzr-cvsps-import/trunk/
[13:57] <kiko> fta2, yo!
[13:58] <balor> LarstiQ: Thanks.
[14:10] <balor> I'm told that my Project is an "invalid value" when trying to import it as a CVS project to launchpad.  The value I specified is "libamore".  What value should I specify?
[14:14] <kiko> balor, there is no libamore project registered at launchpad.
[14:14] <kiko> balor, launchpad.net/projects/+new
[14:14] <balor> kiko: So I have to register the project first.  Ah.
[14:14] <kiko> yep
[14:14] <gary_poster> kiko: thanks. :-)  was just wondering myself.
[14:15] <fta2> kiko, hi! so, about songbird, what should I do? re-push the exact same thing?
[14:15] <kiko> fta2, yeah, let me get hold of somebody at IS to assist.
[14:16] <fta2> kiko, ok, nice. tell me when I can repush.
[14:17] <balor> kiko: Is that the "Register a Branch" or am I looking to register a project?
[14:17] <kiko> balor, launchpad.net/projects/+new
[14:17] <kiko> I meant it :)
[14:17] <balor> kiko: Sorry....bad day :(
[14:18] <kiko> nah, that's fine :)
[14:21] <kiko> fta2, you can repush. let me and lamont know when it is hung
[14:21] <lamont> fta2: my precognition skills are a bit rusty, and all that... :))
[14:24] <balor> Why might my import be "Pending Review"?  particularly when I get an email stating "Your message was rejected"
[14:24] <kiko> balor, that message is bogus and I am still struggling to fix it
[14:24] <kiko> balor, imports are reviewed for sanity -- what's the URL for it?
[14:24] <balor> kiko: np.
[14:25] <balor> kiko: https://code.launchpad.net/~vcs-imports/libamore/trunk
[14:25] <fta2> kiko, lamont: pushing..
[14:25] <kiko> in fact, I've fixed that bogus message right now using a HUGE hammer
[14:26] <fta2> 50%
[14:26] <glade88> is there a way to list just wishlist bugs related to a specific user (or me) ?
[14:26] <kiko> glade88, yes, bugs.l.n/~user/ and advanced search
[14:28] <glade88> kiko: thanks
[14:28] <kiko> sure
[14:28] <kiko> balor, so, libamore is the name of that project, and it contains a bunch of stuff -- not just libamore proper, right?
[14:28] <balor> kiko: It contains the library and a GUI etc....
[14:29] <balor> kiko: We just need a bzr repo to kickstart development again.
[14:29] <kiko> cool
[14:30] <kiko> balor, I'm only slightly curious as to whether this would be better modeled as a project group with other pieces in it
[14:30] <kiko> but since it's one tree, bombs away
[14:30] <balor> kiko: For the moment we just want to get stuff done.  We're taking it in a new direction.
[14:30] <kiko> yeah
[14:31] <kiko> IKWYM
[14:31] <fta2> kiko, lamont: done. waiting for the accept/reject now
[14:32] <balor> kiko: So am I ready for bzr branch on https://code.launchpad.net/~vcs-imports/libamore/trunk now?
[14:32] <kiko> balor, well, the import's running shortly. when it runs and if it succeeds (flaky CVS repos n all) you'll have a beautiful bzr branch
[14:33] <balor> kiko: thanks
[14:36] <fta2> kiko, rejected, as i expected :(
[14:36] <fta2> Rejected:
[14:36] <fta2> The source songbird - 1.0.0-0ubuntu1~fta1 is already accepted in ubuntu/jaunty and you cannot upload the same version within the same distribution. You have to modify the source version and re-upload.
[14:39] <kiko> fta2, but why did you upload it again? just refer to it, no?
[14:39] <fta2> refer to it?
[14:39] <kiko> I wish I knew more about how to undelete stuff
[14:39] <fta2> Rejected:
[14:39] <fta2> Unable to find songbird_1.0.0.orig.tar.gz in upload or distribution.
[14:39] <fta2> Files specified in DSC are broken or missing, skipping package unpack verification.
[14:39] <kiko> bigjools, read up -- does fta2 really need to bump version just to get a deleted package to rebuild?
[14:39] <kiko> hmmm
[14:39] <bigjools> yes
[14:40] <kiko> bigjools, cancha undelete it?
[14:40] <bigjools> not w/o DB surgery
[14:40] <kiko> I don't quite understand why cprov deleted it to be honest
[14:40] <kiko> instead of marking the builds as failed
[14:40] <bigjools> I don't know either
[14:40] <fta2> kiko, that's why i asked if i should re-up the exact same thing, i expected the reject
[14:41] <bigjools> whoa, the .orig is missing?
[14:41] <fta2> apparently
[14:41] <bigjools> he's really cleaned it out then!
[14:41] <bigjools> how bizarre
[14:42] <kiko> fta2, just bump version, I'll ask cprov when he's back from the airport
[14:42] <tkamppeter> wgrant, intellectronica, thank you, I have sent a PM to this user via LP. Let's see what happens.
[14:42] <fta2> kiko, the src version ? too bad for the shiny 1.0.0 :(
[14:43] <kiko> 1.0.0revenge
[14:43] <kiko> well.. I don't have any smart suggestions
[14:43] <kiko> my brain is only half operational this week
[14:45] <bigjools> fta2: bump to 1.0.0+something
[14:46] <fta2> yeah, i know :(
[14:51] <kiko> I don't quite understand why this happened though
[14:51] <kiko> it /looks/ like cprov overcooked it
[14:51] <kiko> but he rarely does that so.. not sure
[14:57] <fta2> too bad my bug 263301 has been rejected
[14:58] <bigjools> fta2: that is a FAQ, really
[14:58] <bigjools> considering how easy it is to just bump versions, I don't know why everyone complains
[15:02] <kiko> bigjools, well, it's kinda nasty to have to do it when the source hasn't actually changed.
[15:02] <bigjools> kiko: if the source hasn't changed then you don't need to re-upload
[15:02] <kiko> bigjools, well, in fta2's case he does :)
[15:02] <fta2> it's rejected
[15:03] <fta2> see above
[15:03] <bigjools> kiko: well if it's deleted, all bets are off :)
[15:03] <fta2> the delete is not a real delete then
[15:03] <kiko> bigjools, that's what I don't understand. the file's still in the librarian, we still know about the publication, etc.
[15:03] <kiko> that's also true
[15:04] <bigjools> kiko: I guess we could add an undelete
[15:04] <bigjools> if nothing was uploaded since
[15:04] <kiko> yeah, let's see how much it comes up.
[15:04] <bigjools> it's not a real deletion because it needs to remember what you already uploaded
[15:04] <bigjools> and published
[15:05] <bigjools> apt clients tend to get very confused if they try and download the same version of something that has a different md5
[15:13] <fta2> not when no bin were produced
[15:13] <fta2> btw, re-upped
[15:15] <bigjools> fta2: not so, you're forgetting the source
[15:16] <fta2> bigjools, what i mean it that re-up the same or another tarball with the same version should not hurt when no debs have been produced
[15:16] <fta2> -it+is
[15:17] <bigjools> fta2: the source has been published in the repo
[15:17] <bigjools> it's too late at that point
[15:19] <fta2> i consider my PPA as highly experimental. I take great care of what i push there but yet, it's not bullet proof and users know the risks. at least they should.
[15:20] <bigjools> fta2: well it's nothing to do with the quality of the code and everything to do with the packaging toolchain
[15:21] <bigjools> fta2: the only way around this is to know if a source/binary has been downloaded or not, but we're a way off implementing that yet
[15:21] <fta2> kiko, lamont: same issue as yesterday. all 9 builds stuck at the same place.
[15:21] <lamont> yay!
[15:21] <lamont> consistency ftw
[15:21] <fta2> https://edge.launchpad.net/+builds/iridium
[15:21] <kiko> thanks fta2
[15:22] <kiko> now let's see what lamont can find for us :)
[15:22] <fta2> here are my logs (jaunty/i386): http://paste.ubuntu.com/79849/
[15:22] <lamont> sigh.
[15:23]  * lamont is reminded that not being the UOSA means that he forgets things
[15:24] <lamont> like the fact that the ppa buildds are so completely locked down as to be totally undebuggable
[15:28] <lamont> and I don't know that we needed to upload _all_ of them when we expected them to hang...
[15:28]  * lamont will try to reproduce the issue locally
[15:30] <kiko> lamont, it appears to work fine for fta2 locally
[15:31] <kiko> lamont, if you have a PPA image you can build inside it will probably enlighten
[15:32] <lamont> locally with sbuild, or locally outside sbuild?
[15:35] <kiko> fta2?
[15:53] <kiko> lamont, got anywhere?
[15:54] <fta2> kiko, ? (sorry, i was busy)
[15:56] <fta2> lamont, locally outside sbuild
[15:57] <MTecknology> How do I link a bug to another bug tracker?
[15:57] <kiko> MTecknology, I'll explain. which bug?
[15:57] <MTecknology> https://bugs.edge.launchpad.net/blueproximity/+bug/286820
[16:02] <MTecknology> kiko: ?
[16:02] <kiko> MTecknology, what's the remote bug? it sounds like blueproximity upstream uses launchpad?
[16:03] <MTecknology> http://sourceforge.net/tracker/index.php?func=detail&aid=2383237&group_id=203022&atid=983922
[16:04] <kiko> that's weird.
[16:04] <MTecknology> ?
[16:04] <kiko> MTecknology, does blueproximity use SF or Launchpad?
[16:04] <MTecknology> I'm not really sure - I think they use SF
[16:05] <kiko> https://edge.launchpad.net/blueproximity
[16:06] <kiko> MTecknology, so in this specific case it's weird because they seem to use both. we normally only link to remote bugs if the project doesn't use LP officially
[16:06] <kiko> MTecknology, maybe the easiest thing is to just add the URL in a comment and figure it out later.
[16:06] <MTecknology> ok
[16:06] <kiko> MTecknology, if you want to help further you can contact the project lead and ask him what the story is
[16:06] <kiko> the Launchpad project page says it uses LP
[16:06] <kiko> but the project homepage says it uses SF
[16:07] <kiko> which is correct?
[16:07] <MTecknology> How do I do it? Could you walk me through linking process so I know how?
[16:07] <MTecknology> nvm - I found it
[16:07] <kiko-fud> cool
[16:08] <MTecknology> kiko-fud: thanks
[16:09] <kiko-fud> sure thing
[16:48] <fta2> lamont, kiko: any progress with songbird?
[16:50] <lamont> fta2: the level of ppa-buildd hackery it wants really calls for infinity, not me.
[17:42] <fta2> lamont, kiko: ok, please keep me posted. If you need to kill my stuff, please don't delete everything
[17:43] <kiko> gar
[17:43] <kiko> lamont, when do we have infinity around for this?
[17:43] <kiko> lamont, or elmo?
[17:46] <lamont> elmo is in transit -> UDS
[17:48] <lamont>  /usr/bin/ld: final link failed: Memory exhausted
[17:48] <lamont> well, that's a different (albeit maybe related?) error
[17:48]  * lamont looks to see how much memory that vm instance has
[17:49] <lamont> meh.  640M should be enough for anyone, right?
[17:49] <lamont> and 400MB of swap...
[17:50]  * lamont checks on a ppa config
[17:56] <fta2> to link chromium (the browser), ldd takes nearly 1GB
[17:57] <fta2> ld
[17:59] <kiko> lamont, could that be?
[17:59] <fta2> i even had to limit to -j 1 as by default, it was sucking 4G on my quadcore.
[18:00] <fta2> brb
[18:12] <lamont> ppas have 1549MB of ram, and (looks like at first blush without doing anything invasive) 2GB of swap.
[18:12] <lamont> and no, I don't know where that RAM size number comes from
[18:36] <infinity> kiko, fta: I hear there are some problems with PPA and songbird?
[18:37] <infinity> kiko, fta: Except that when I go to look, all I see are a bunch of identical failures at the ~3 hour mark, which looks like it's not PPA's fault...
[19:04] <pygi> how does one appoint driver for a project?
[19:04] <pygi> totally un-intuitive :/
[19:10] <gary_poster> pygi from project home page, click "change details"
[19:10] <gary_poster> pypi: then click on the "People" sub-sub tab
[19:10] <pygi> gary_poster, ah, sub-tabs
[19:11] <pygi> see?! Tabs are not intuitive :P
[19:11] <gary_poster> :-)
[19:11] <pygi> you can see that with the tabs-frenzy joke at gnome :P
[19:12] <pygi> thanks gary_poster :)
[19:12] <mpt> They're just not drawn in an obvious style at the moment
[19:12] <gary_poster> pygi: :-) glad I could help
[19:21] <kiko_> the appservers are acting up, mthaddon and flacoste looking into it.
[19:24] <MTecknology> 13:22 < xteejx> MTecknology: Tell me about it! Is there any way to refile his comments under another bug for him (Socrates) and get rid of them in that report?
[19:24] <MTecknology> He asked that in reference to https://bugs.edge.launchpad.net/ubuntu/+source/xorg/+bug/231455
[19:25] <MTecknology> kiko: is there any way to do that for him?
[19:26] <kiko> nope.
[19:26] <MTecknology> About the only thing he could do is mark the bug invalid and make a clean one which isn
[19:26] <MTecknology> 't worth it?
[19:27] <MTecknology> kiko: is that about right?
[19:30] <kiko> yeah, pretty much
[19:31] <MTecknology> kiko: so - now that I know that much, do I get a job at canonical? :D
[19:31] <MTecknology> :P
[19:31] <MTecknology> How hard is it to scare a job like that anyway?
[19:32] <kiko> you can apply! there are a bunch of job postings up at canonical.com. :)
[19:33] <MTecknology> Are they pretty much jobs where you can work from anywhere in the world?
[19:35] <MTecknology> nope
[19:37] <MTecknology> "Launchpad Bugs Application Engineer" Looks nice. I'll probably have to apply for it out after I get out of college
[19:37] <MTecknology> I assume that will still be open
[19:46] <MTecknology> kiko: What I really want is to be a systems administrator somewhere around here. I don't imagine that's likely.
[19:49] <MTecknology> kiko: If it's ok to ask, what kind of salary does canonical offer?
[19:50] <MTecknology> I imagine it varies a lot, I'm just curious.
[19:52] <pygi> MTecknology, dont you know contracts say that you're not allowed to say that? :p
[19:52] <MTecknology> pygi: nope, I didn't
[19:52] <pygi> now you know :)
[19:52] <MTecknology> yup
[19:53] <MTecknology> brb
[20:04] <MTecknology> pygi: Are the jobs pretty competitive or is canonical expanding plenty fast?
[20:05] <pygi> MTecknology, I'm not working at Canonical
[20:05] <MTecknology> oh - I suppose I'd know that if I saw your hostmask :P
[21:21] <MTecknology> What's with launchpad.com
[21:22] <kiko> spam
[21:24] <MTecknology> Somebody else registered it?
[21:25] <kiko> it was already owned by some loser before
[21:26] <kiko> I guess they just messed up the config
[21:26] <kiko> dunno
[21:34] <fta> lamont, what did you do to unblock the builders ?
[21:34] <fta> kiko, ^^ do you know ?
[21:34] <kiko> did they unblock? :)
[21:34] <lamont> fta: ??
[21:35]  * lamont did nothing wrt songbird
[21:35] <fta> yes, but something else happened. i'm investigating the failure
[21:35] <fta> (that i didn't see locally)
[21:35] <kiko> file not found: /build/buildd/songbird-1.0.0+0/build-tree/songbird/app/content/bindings/content/songbird/bindings//build/buildd/songbird-1.0.0+0/build-tree/songbird/app/content/bindings/browser/tabBrowserCompat.xml at /build/buildd/songbird-1.0.0+0/build-tree/songbird/dependencies/linux-i686/mozilla/release/scripts/make-jars.pl line 430, <STDIN> line 76.
[21:36] <fta> yes yes... digging
[21:36] <MTecknology> I'm getting 0 (Error ID: OOPS-1068EA222)
[21:36] <kiko> maybe they weren't hanging after all?
[21:36] <lamont> given the size, I expect that "hang" == "swaping heavily"
[21:36] <lamont> after all, they _only_ have 1.5GB of RAM
[21:36] <fta> kiko, it's supposed to build in less than 1h, not in 3h
[21:37] <kiko> fta, inside a VM with limited memory? dunno
[21:37] <fta> and logs started to flow during the build after ~2h of no activity
[21:38] <fta> looks like a timeout to me
[21:50] <kiko> fta, there are no timeouts in the buildds.
[21:54] <fta> no watchdog of any kind? killing zombies or dead locked processes? i think there is. I remember a jemalloc problem with xul1.9.1 that hold the builders for 4h before the pkg is killed.
[21:54] <kiko> not that I know of.
[22:03] <exarkun> I'm looking for the bugs page for the kernel package in Hardy
[22:10] <exarkun> Is it this?  https://bugs.launchpad.net/ubuntu/hardy/+source/linux-meta
[22:13] <stdin> exarkun: more likely https://bugs.launchpad.net/ubuntu/hardy/+source/linux
[22:14] <drguildo> bug reporting seems to be broken
[22:15] <beuno> drguildo, how so?
[22:15] <drguildo> i'm getting timeout errors
[22:15] <drguildo> Error ID: OOPS-1068B4511
[22:16] <beuno> drguildo, known issue being worked on
[22:27] <drguildo> beuno: seems to be working now. thanks.
[22:58] <fta> kiko, found the bug
[22:59] <kiko> fta!
[22:59] <kiko> you rock duder
[22:59] <fta> kiko, it's an upstream bug. it's caused by the only change i've made 1.0.0 -> 1.0.0+0 in the tarball name, hence in the path
[23:00] <kiko> damn
[23:00] <fta> the "+" is used in a perl regexp
[23:00] <kiko> fta, does that mean that the 1.0.0 build actually would have worked if we hadn't killed it?
[23:00] <fta> probably
[23:01] <fta> i still don't understand why there a 2h window at the beginning where nothing happened (in the cdbs tarball parsing)
[23:01] <fta> +'s
[23:06] <kiko> same here but only infinity or elmo might be able to tell us..
[23:08] <kiko> that's kinda why I suggested 1.0.0revenge :)
[23:11] <fta> ok, i just patched it
[23:25] <wgrant> I feel like launchpad-users.
[23:30] <wgrant> mpt: Wasn't the point of the new bad-looking subtabs to make them more obviously tabbish?
[23:33] <kiko> and they actually do work
[23:33] <wgrant> Didn't mpt see say they weren't obvious?
[23:33] <wgrant> s/see //
[23:34] <kiko> he tried to justify the general problem of not being able to navigate to and under +edit
[23:34] <wgrant> Can we get a 'THIS IS NOT FOR ORDERING CDS OR ORDERING LAUNCHPADS' in big red bold text on top of +contactuser?
[23:34] <wgrant> Somebody wants me to send them a Launchpad :(
[23:34] <kiko> wgrant, same here. if you want consolation we're going to change the feature.
[23:35] <wgrant> I can't see any sane way to restrict it.
[23:35] <Nafallo> send them a launchpad? BWAHAHA
[23:36] <kiko> Nafallo, that's like sending him raw plutonium
[23:37] <kiko> wgrant, follow the l-u thread
[23:37] <wgrant> kiko: I've just finished that.
[23:37] <Nafallo> kiko: I was actually thinking about the weight of all those servers :-P
[23:37] <wgrant> That doesn't seem to cover users, just teams.
[23:37] <wgrant> Nafallo: Right, plutonium isn
[23:37] <wgrant> ... isn't light :P
[23:37] <Nafallo> wgrant: plutonium is a PPA ;-)
[23:37] <kiko> wgrant, you're getting email because of a team in that case. it's a frenchman, right?
[23:38] <Nafallo> well. if it had actually worked :-P
[23:38] <Nafallo> kiko: SEB! :-D
[23:38] <kiko> lol
[23:38] <wgrant> kiko: Ah, yes, it doesn't actually say that *anywhere*.
[23:38] <kiko> wgrant, read my l-u email god dammit :)
[23:39] <mpt> wgrant, I think it was to make them more visible
[23:39] <mpt> which is different from making them more tabbish
[23:39] <mpt> bbiab
[23:41] <wgrant> kiko: Ah, I didn't look at those bug.s
[23:41] <wgrant> Nor can I type.
[23:51] <fta> kiko, https://edge.launchpad.net/~fta/+archive/+builds?build_text=&build_state=building
[23:58] <mpt> wgrant, I think it would be entirely possible to achieve both