[00:01] <poolie> ah, could be
[00:02] <poolie> it failed 5/5 times, even though hydrazine already has a workaround for it being out of date because of a prior change
[00:02] <poolie> imbw but i don't think the client can do any better
[00:02] <poolie> it's just reading and then updating one value, how can it get any simpler?
[00:04] <poolie> hello emmajane
[00:04] <emmajane> poolie, ola :)
[00:10] <poolie> https://edge.launchpad.net/launchpad-project/+milestones is persistently timing out
[00:12] <mwhudson> poolie: me too
[00:27] <rdz> i just realized, that the package i created just contains documentation files, but no binaries at all. when i install manually from source, binaries are installed.. whjat might be wrong here?
[01:02] <rdz> i can see get everything compiled, when doing 'pbuilder build', but still the resulting deb does not contain any binary files. what might be wrong here?
[01:03] <poolie> rdz, i'd suspect something wrong in the way you're calling debhelper or whatever
[01:03] <poolie> perhaps you should ask in #ubuntu-motu
[01:07] <rdz> poolie, i now get an error:/usr/bin/install: cannot create regular file `/usr/lib/libgavl.so.1.0.0': Permission denied
[01:07] <poolie> hm, maybe pbuilder is not running fakeroot or something?
[01:08] <rdz> how can i check that?
[01:08] <rdz> fakeroot does also fake a / directory? or does it only fake having root privileges?
[01:09] <poolie> it fakes having root privileges
[01:09] <poolie> because debs must normally be built as root
[01:10] <rdz> hm.. but then it is obvious, that it cannot install to /usr/lib.. no?
[01:10] <rdz> but how to change that?
[01:16] <crimsun> rdz: #ubuntu-motu is the better place for packaging questions. Your symptom reads suspiciously as if your debian/rules or debian/foo.install is incorrect.
[01:16] <rdz> crimsun, thanks .. i'll check there
[03:05] <persia> I just got a "This does not look like a patch" warning for http://launchpadlibrarian.net/40462740/qemu-kvm_0.12.3-0ubuntu11.debdiff : did I do something odd, or is there a bug in the patch detection algorithm?
[03:15] <wgrant> persia: The extension isn't recognised.
[03:15] <wgrant> Sounds like we need some monkeypatching.
[03:16] <wgrant> Ahem.
[03:16] <wgrant>     mimetypes.add_type('text/plain', '.debdiff')
[03:17] <persia> The *extension* is being checked.
[03:18] <wgrant> Yes.
[03:18] <persia> That's SO WRONG
[03:18] <wgrant> It's not ideal.
[03:19] <idnar> there's not much else you can do, given the way browsers handle file uploads
[03:19] <wgrant> But it seems to be the standard way to determine MIME types these days.
[03:19] <idnar> in theory the browser could specify the correct type
[03:19] <idnar> in practice, there's no way for the user to control that, and no way for the browser to know the correct type
[03:21] <persia> Can we not do content analysis on the files?
[03:21] <wgrant> It's possible.
[03:21] <wgrant> And would be ideal.
[03:21] <persia> Well, it would probably expose some bugs in magic handling for patches, but aside from that, yes.
[03:23] <wgrant> But Python's mimetypes module uses extensions, and that's what zope.contenttype uses, and that's what LP uses.
[03:24] <persia> Well that's annoying.  There's all kinds of non-standard extensions used for patches (diff, patch, dpatch, debdiff, nothing, etc.)
[03:24] <wgrant> Yes.
[03:25] <persia> I can't decide if it's actually a bug though.
[03:26] <persia> I think I'll not file a bug about it: it's mildly annoying, but I suppose the reason for it to be that way.
[03:26] <persia> And I don't think it's that hard to confirm things are really patches.  I just now think any detection logic that may exist is useless.
[03:27] <wgrant> The fix for debdiffs is trivial.
[03:27] <wgrant> Right.
[03:27] <persia> The fix for ".debdiff" is trivial, until the next extension comes along.
[03:28] <wgrant> Yep.
[03:28] <persia> Plus some patches are large, so we convince people to upload compressed versions.
[03:28] <persia> I might later file a bug about the language "This doesn't look like a diff" being potentially inappropriate when launchpad didn't even look at it, but that's very minor.
[03:29] <wgrant> Adding a .gz or .bz2 or similar shouldn't affect the detection.
[03:30] <lifeless> wgrant: its broken no matter what?
[03:30] <lifeless> wgrant: :P
[03:30] <rdz> hi all. i am spending hours on fixing a  build of a package: the only relevant file gets not included in the resulting packages. it seems i am overseeing to most obvious, but i am not able to track it down
[03:30] <wgrant> lifeless: Heh, true.
[03:31] <wgrant> rdz: I'd suggest continuing your hunt for assistance in #ubuntu-motu.
[03:31] <rdz> wgrant, ok thanks
[03:35] <persia> There ought to be a channel for getting support for packaging stuff.  The issue seems to be that nobody would staff it.
[03:36] <persia> I'm not always in the mood to support PPA packagers (and lots of other folks also), but here almost never seems right.
[03:36] <wgrant> Indeed :(
[03:36] <wgrant> Neither channel is correct.
[03:36] <persia> But if we created a new channel, would anyone staff it?
[03:37] <persia> I'm really happy about #ubuntu-app-devel but that took years to form.
[03:37] <rww> We get people asking about it in #ubuntu every so often, and I always feel kinda bad about redirecting them to #ubuntu-motu, because it doesn't really fit :\
[03:37] <persia> (and I'm not sure it's the right place for PPA packagers)
[03:37] <persia> rww: Unless someone happens to be in a good mood, -motu usually redirects here.
[03:37] <persia> But here sometimes redirects to -motu and mostly just can't help.
[03:37] <wgrant> Create #ubuntu-packaging and direct the people from here and #-motu to there? But then that might leave #-motu near-empty.
[03:38] <persia> wgrant: The trick being: who offers support in #ubuntu-packaging?
[03:38] <wgrant> Well, -motu redirects here more often when certain people are around.
[03:38] <persia> Well, I'm one of the people who redirects here : it just depends on my mood.
[03:38] <wgrant> persia: Most of the people who offer packaging support in #ubuntu-motu now, I would imagine.
[03:39] <persia> Right then.
[03:39]  * persia goes off to create a channel, not promising to keep it staffed or anything
[03:40] <wgrant> It's a start.
[03:42] <lifeless> I redirect to u-m all the time
[03:44] <persia> lifeless: You shouldn't.  That's not the right place.
[03:45] <micahg> which component has to do with series for projects?
[03:45] <mwhudson> micahg: registry
[03:45] <micahg> mwhudson: thanks
[03:54] <persia> So, #ubuntu-packaging defined.  Please redirect folk there.  If anyone wants to suggest changes to topic or access, please give me hints.
[03:55] <wzssyqa> what should i do,if a lost my privte keys
[04:00] <rww> wzssyqa: private keys for what? gnupg or ssh or something else?
[04:01] <wzssyqa> rww: all,i formate my /home
[04:01] <wzssyqa> now ,i am cring :'(
[04:02] <rww> wzssyqa: For SSH, you can just generate a new one and replace the old one with the new one on Launchpad. For GNUPG, if you don't have a revocation certificate and it isn't set to expire eventually, the old key is going to be on the keyserver forever, but you can still generate a new one and tell LP about it, it'll just be mildly confusing.
[04:03] <wzssyqa> rww: thx
[04:03] <rww> But yeah, in general, if you lose the private key, you can't regenerate that particular private key, and thus have to make a new one.
[04:03] <wzssyqa> rww: i see
[04:04] <wgrant> That is, of course, the point of a private key.
[04:04] <rww> indeed :)
[04:31] <lifeless> persia: It has been the best place to date.
[04:31] <wgrant> lifeless: Yes, but it's wrong :(
[04:31] <lifeless> wgrant: -<>-
[04:31] <wgrant> Pardon?
[04:33] <lifeless> wgrant: :P
[04:37] <persia> lifeless: Not it's not only wrong, but there's a better place :)
[04:38] <dickelbeck> Any one home?
[04:39] <wgrant> Nobody.
[04:39] <dickelbeck> I am trying to establish a new launchpad account named "Kicad".  The attempt is failing saying that an account by that name already exists.  We once had an account here, and asked that it be removed, and it was to our knowledge.  The we recently started kicad-newlib but this is for libraries, not for the core program itself.
[04:40] <wgrant> dickelbeck: By "account" do you mean a project?
[04:40] <dickelbeck> Yes project
[04:43] <dickelbeck> The UI and slow speed at sourceforge.net has recently crossed into the intolerable realm.
[04:44] <thumper> dickelbeck: was the project named kicad?
[04:45] <dickelbeck> yes
[04:45] <thumper> dickelbeck: and you want it reactivated, yes?
[04:45] <dickelbeck> yes we want that name now for real.
[04:45] <thumper> dickelbeck: this: The well known electronic design automation tool on GPL license.?
[04:46] <thumper> dickelbeck: done: https://launchpad.net/kicad
[04:46] <dickelbeck> Yes, the very one.  I am an admin for it at sourceforge.net
[04:47] <thumper> dickelbeck: if this is you, you are the owner/maintainer in lp too https://edge.launchpad.net/~manveru
[04:47]  * thumper goes to make dinner
[04:48] <dickelbeck> No manveru is not an admin for the project.  He is only a developer.  You can verify this at sourceforge.net.  This was a political problem and is a main reason why it was shutdown in the first place.  Manveru set it up without any authority.  Since then we have had a vote, etc.
[04:49] <wgrant> dickelbeck: If you ask at https://answers.launchpad.net/launchpad/+addquestion and provide evidence supporting your request and identity, the project can be transferred to you.
[05:00] <dickelbeck> OK, I asked the question over there.  Anything else I need to do here, or any reason to wait around?
[05:00] <wgrant> That should be all you need to do. Somebody will probably get to it in the next day or two.
[05:01] <dickelbeck> OK thanks, bye.
[05:08] <rww> mthaddon: answering PPA rename reqests with "This isn't possible, see bug" and linking to a bug that says "this is possible, but time-consuming and error-prone" is... confusing.
[05:09] <mthaddon> rww: I guess I should have more clearly said "this isn't possible through the UI"
[05:10] <rww> (I'm the asker in https://answers.edge.launchpad.net/launchpad/+question/102481 , in case anyone is wondering where that statement randomly came from :)
[05:10] <rww> mthaddon: I'm guessing the policy on this changed? Because I've heard from others who've had it done in the past, hence filing the question in the first place.
[05:11] <rww> or they might have been mistaken, iono
[05:11] <wgrant> Deleting a PPA that has never contained any packages is possible.
[05:12] <mthaddon> rww: er, kind of - we're getting more and more requests to do this, and it's becoming clear it really needs to be something we can do through the UI - so from that perspective, yeah, I'm trying to push to get it added to avoid us having to do it manually
[05:12] <persia> rww: Way back in the beginning, PPA renames were done, which caused lots of problems, and the establishment of the policy, which may be the source of confusion.
[05:12] <mthaddon> wgrant: well, yes and no - it's not possible through the UI
[05:12] <wgrant> mthaddon: Right.
[05:13] <micahg> just got an oops...should I file a bug or post here?
[05:13] <wgrant> It's not an easy problem to solve, sadly.
[05:13] <wgrant> Since it's not a simple problem of renaming a directory; the name is embedded in the PPA indices too.
[05:14] <mthaddon> name abstraction like we do for branches would be nice
[05:15] <rww> wgrant, mthaddon: My PPA had packages in it at one point, I don't think I specified that in the original question. Does that mean I'm screwed, or will that be possible to rename when that bug's resolved?
[05:16] <mthaddon> once the bug has been resolved, it'd be possible to rename with a PPA I think (certainly with a disabled PPA)
[05:16] <wgrant> Exactly.
[05:16] <rww> alright
[05:17] <rww> the main concern here from my end is that I have the whole @ubuntu.com email address thing going on, so if I start using it now, I'd have to switch over when I renamed the account, which would be annoying
[05:18] <rww> (I just got membership recently, and have been holding off on various things because of this)
[05:20] <rww> hmm, there wouldn't happen to be a way to use something other than mylpusername@ubuntu.com, would there? that would also solve this problem. given persia's explanation to someone else the other day I'm guessing not, but...
[05:20] <mthaddon> yeah, I understand this is a real pain - hopefully with enough pressure the priority of the bug can be raised
[05:20] <persia> rww: There's a decent chance you'll have to take some special action to get your email changed after you change your LP account anyway.
[05:21] <rww> persia: https://wiki.ubuntu.com/UbuntuEmail says it's automagic
[05:22] <persia> OK.  s/decent/small/ :)
[08:25] <Fly-Man-> Morning
[08:25] <Fly-Man-> Anyone getting the same error messages on the Bazaar this morning ?
[08:25] <Fly-Man-> When trying to view a branch, the message: "Internal Server Error" pops ip
[08:25] <Fly-Man-> up*
[08:35] <mkanat> lifeless: Is loggerhead hung?
[08:36] <lifeless> Fly-Man-: what branch
[08:36] <lifeless> mkanat: dunno if its hung per se - I can't log into that box to check
[08:36] <Fly-Man-> lifeless: let me grab the link
[08:36] <mkanat> lifeless: Okay. When it hangs, none of it works.
[08:36] <mkanat> lifeless: So you could go to any codebrowse page and it wouldn't work.
[08:36] <lifeless> losa ping - is loggerhead hung ? - data gathering for mkanat :>
[08:37] <Fly-Man-> lifeless: http://bazaar.launchpad.net/~flyman/fusionforge/translate/files
[08:37] <Peng> http://bazaar.launchpad.net/~mnordhoff/loggerhead/cheezum/changes works, though.
[08:37] <Peng> /files, too
[08:37] <lifeless> Fly-Man-: ok, looks like a branch specific issue
[08:37] <mkanat> Okay.
[08:37] <mkanat> So that would be something separate from my issue.
[08:37] <lifeless> Fly-Man-: that could be a) a bug in loggerhead, or b) a problem with your branch.
[08:37] <mkanat> Dang. :-)
[08:37] <lifeless> mkanat: thanks for popping in to check.
[08:37] <mkanat> lifeless: np!
[08:38] <mkanat> I'm out; finishing up a Bugzilla release.
[08:38] <Peng> mkanat: See you later. :)
[08:38] <mkanat> Peng: Later! :-)
[08:38] <Fly-Man-> lifeless: a) could be b) possibly, it hasn't been grabbing the latest pot/po files as well from the branch
[08:38] <lifeless> Fly-Man-: can you please file a bug at bugs.launchpad.net/launchpad-code ?
[08:38] <Fly-Man-> lifeless: Already on it :)
[08:39] <mthaddon> lifeless: checking
[08:39] <mthaddon> lifeless: not according to nagios
[08:39] <lifeless> mthaddon: thanks!
[08:39] <lifeless> mthaddon: if you can get a log extract for the ISE's that Fly-Man- was triggering that would be great
[08:40] <mthaddon> lifeless: ISE's?
[08:40] <lifeless> internal server error - python-paste tracebacks
[08:42] <Fly-Man-> mthaddon: lifeless : Bug #534245
[08:42] <mthaddon> ah
[08:43] <Fly-Man-> O yeah .. ubottu was awake ;)
[08:43] <Fly-Man-> I tend to forget about him :p
[08:43] <lifeless> mthaddon: so there should be something in the logfile and if you can find it and attach to the bug ^ that would be good
[11:50] <aquarius> Can I construct a bug search which searches across two projects rather than just one or all?
[11:55] <beuno> aquarius, not AFAIK
[11:57] <wgrant> aquarius: Unless you have a project group or a team or person common to all of them, not really.
[11:57]  * aquarius grumbles.
[12:01] <aquarius> and search results don't have an atom feed, correct?
[12:01] <beuno> correct
[12:04] <Daviey> aquarius: If you are bored, you could do client side processing using the api?
[12:08] <aquarius> yep, I could indeed, which is what I'm debating doing :)
[12:11] <aquarius> given that login_anonymously() only exists in launchpadlib >= 1.5.4, how did one log in anonymously using 1.5.1? or could it just not be done?
[12:13] <thekorn> aquarius, launchpad = Launchpad.login("client", "", "", service_root)
[12:13] <danilos> aquarius, it could not be done, it was introduced into Launchpad server-side API at the same time
[12:13] <danilos> aquarius, or at least that's my guess, perhaps thekorn is right :)
[12:13] <aquarius> those two answers are contradictory ;-)
[12:13] <thekorn> I'm right ;)
[12:13] <danilos> aquarius, there you go, thekorn is right :)
[12:14] <aquarius> superb :)
[12:29] <Daviey> aquarius: it's pretty dirty, and should really check that raise error is due to not having the right lplib installed, or check what version after importing; but this is how i overcame anon usage http://bazaar.launchpad.net/~loco-directory-dev/loco-directory/0.2/annotate/head:/loco_directory/common/launchpad.py
[12:29] <aquarius> thekorn's suggestion works perfectly :)
[12:33] <Daviey> aquarius: not knowing the reason for usage, but if it's to make your life easier handling bugs - using the anon api, you will obviously not be able to see security bugs you are privy to, or other non-public bugs.
[12:35] <aquarius> yep, but I don't mind about that :)
[12:55] <rdz> how can i re-upload the same package sources after having modified only some control files but not the sources themselves?
[12:59] <danilos> rdz, you have to up the version number still
[13:00] <rdz> danilos, thanks
[13:01] <danilos> rdz, you can also find more help at https://help.launchpad.net/Packaging/UploadErrors
[13:02] <danilos> bigjools, would it be worth having this (changing package without updating version number) as a FAQ on answers.launchpad.net/soyuz as well? (that's where I looked first)
[13:54] <bigjools> danilos: I thought it was already there, let me check
[13:54] <bigjools> danilos: ah I was thinking of the help wiki, you're right
[13:59] <bigjools> danilos: I added one
[13:59] <danilos> bigjools, excellent, thanks a lot
[14:00] <bigjools> danilos: welcome
[14:10] <ricotz> danilos, i am trying to do a manual sync from a bzr branch since automatic seems not working, but triggering the manual sync doesnt show anything in the import queue
[14:11] <danilos> ricotz, which project is that?
[14:12] <ricotz> docky
[14:14] <ricotz> danilos, are you an admin?
[14:19] <danilos> ricotz, yeah, I am LP Translations developer as well, so you're lucky
[14:19] <danilos> ricotz, (sorry, been busy with some other things)
[14:21] <ricotz> danilos, so there was a automatic import from bzr active but there is no update since 22 hours, so i triggered a "one time import" which doesnt work, only a manual upload seems to work
[14:21] <danilos> ricotz, ok, so the problem is that your latest upload was manual (or so it seems) and auto-approval is done based on the full path
[14:22] <danilos> ricotz, in general, we suggest people use bzr imports exclusively, but of course, if it's broken, it's understandable why you didn't use that
[14:22] <danilos> ricotz, let me see if bzr imports are working well
[14:22] <ricotz> i just uploaded the template
[14:23] <ricotz> automatic import and manual export to bzr worked fine until now
[14:24] <danilos> ricotz, right, I am trying to look into bzr imports; manual uploads sometimes require manual approval (i.e. someone from the LP translations team has to do it)
[14:24] <danilos> ricotz, right, we've hit a bug in exports last night, we are working on fix for that
[14:26] <ricotz> danilos, ok, but the sync back from bzr after a manual download and commit works automatic without any approval
[14:27] <danilos> ricotz, that's right
[14:28] <ricotz> danilos, ok, so triggering an "one time import" isnt working because of this bug
[14:29] <danilos> ricotz, I am not sure why one time import isn't working for you
[14:32] <danilos> ricotz, btw, I see that http://bazaar.launchpad.net/~docky-core/docky/trunk/revision/1173 was successfully imported
[14:32] <ricotz> no this was a manual upload
[14:32] <aquarius> Can I get a list of merge proposals that I reviewed, using launchpadlib? I can get a list of merge proposals that i proposed, and for a given merge proposal I can see who reviewed it, but I can't find a way of getting a list of all merge proposals that I reviewed.
[14:32] <danilos> ricotz, ok
[14:33] <danilos> rockstar, abentley: can you help aquarius please?
[14:34] <abentley> aquarius, I don't think you can.
[14:35]  * aquarius does a sort of sad Bambi-eyes look
[14:35] <abentley> aquarius, if you'd like to submit a branch to provide that, I'd be happy to review it.
[14:35]  * aquarius girns
[14:35]  * aquarius grins, too
[14:37] <aquarius> I'm not even sure it's doable the long way (i.e, by walking through everything) because there's no branch_merge_proposals collection either, afaics? So to do it I'd have to get all branches for all projects I care about, walk each one to get merge proposals, then check each proposal to see if I'm in the reviewers list. ouch.
[14:37] <danilos> ricotz, I am looking at logs and it seems rosetta import jobs have stopped working on March 4th, basically after our last rollout
[14:37] <aquarius> might as well just inhale all of launchpad at that point :)
[14:37] <danilos> jtv, it seems we've broken rosetta branch imports on March 4th
[14:38] <jtv> danilos: that may be the "non-ascii exception" error... hang on, I'll check
[14:38] <danilos> jtv, this is imports
[14:38] <jtv> oh imports, sorry
[14:39] <jtv> So... that was the rollout?
[14:39] <danilos> jtv, this is how the log file looks http://paste.ubuntu.com/391083/ (and nothing continues until this very day)
[14:39] <ricotz> danilos, ok, so this can be fixed?
[14:40] <danilos> ricotz, we will work on it immediately, it will probably take a day or two to fix it
[14:40] <jtv> danilos: ouch, that's not a lot to go on
[14:41] <jtv> danilos: I'm basically eod (apart from a call soon), but it's worth asking the losas if there's a lock file hanging around
[14:41] <danilos> jtv, sure, I'll take it with henninge
[14:42] <danilos> ricotz, I'll file a bug and let you know so you can subscribe to it
[14:42] <jtv> danilos: note that we also had a segfault while a branch was being scanned around rollout
[14:42] <danilos> jtv, right, nice
[14:42] <jtv> I filed a bug about that, but not under rosetta since it seemed a generic branch-scanning issue
[14:42] <ricotz> danilos, thank you, seems to be bigger problem ;-)
[14:42] <danilos> ricotz, yeah
[14:43] <ricotz> danilos, a least manual updates are working
[14:43] <danilos> ricotz, we are actually thankful for you pointing us at it
[14:43] <jtv> So by all means first check that branches are still being scanned.  They probably are, but...
[14:43] <ricotz> danilos, your welcome
[14:43] <abentley> aquarius, Person.getRequestedReviews should return a superset including the branches you own and those you've been asked to review or have reviewed.
[14:43] <danilos> ricotz, yeah, I guess you'll have to use that until we fix it, sorry for the inconvenience :)
[14:43] <ricotz> s/your/youre
[14:43] <ricotz> danilos, no problem
[14:44] <danilos> jtv, they are being scanned, my guess is the code that introduces new disabled auto-generation of templates is what broke something
[14:44] <aquarius> abentley, yep, I saw that, but it's not useful for my specific use case because it doesn't include reviews requested of a team that I'm in...does getRequestedReviews include proposals where I wasn't *asked* to review it (my team was) but I *did* review it?
[14:45] <jtv> danilos: I *think* that would break scanning as well though... certainly it'd break generation of the jobs, so we can check if there are any pending rosettauploadjobs.
[14:45] <aquarius> abentley, it is possible that I am wrong and it is ideal for my use case :)
[14:45] <abentley> aquarius, yes, it should include everything you've reviewed, whether or not your team was also requested to review it.
[14:45] <aquarius> rock and roll!
[14:46] <danilos> jtv, I'd say generation of jobs is what's broken
[14:49] <abentley> danilos, if this turns out to be a branch scanner event notification issue, be aware that I have changed things considerably since the rollout.
[14:49] <jtv> danilos: it may be something to do with how the creation of these jobs was moved to another file (but the old dead code was still kept around at that time)
[14:49] <jtv> abentley: how simultaneous of us
[14:50] <danilos> abentley, thanks for the heads up
[14:50] <abentley> jtv, actually I mean that the event subscriptions are now done via zcml.
[14:50] <jtv> abentley: oh, so there have been multiple changes
[14:50] <jtv> our branches may have crossed  :(
[14:51] <abentley> jtv, point is that my changes haven't hit production, so if you look at stable/db-stable, you aren't looking at the production code.
[14:52] <jtv> abentley: I can't even find the relevant bits in devel atm...
[14:52] <danilos> abentley, thanks, I've added a comment along those lines to bug 534427
[14:53] <aquarius> abentley, on a merge proposal Entry, is registrant_link ("The person who registered the landing target"), in English, the person who proposed the merge? Having difficulty deciphering it
[14:53] <abentley> aquarius, yes.
[14:53] <aquarius> cool
[14:53] <danilos> ricotz, the bug is filed as bug 534427, so you can subscribe to it if you want to know when is it 'fix released'
[14:54] <ricotz> danilos, rhanks
[14:54] <ricotz> thanks
[14:54] <jtv> abentley: ah, got a better view of things now...  thanks for explaining
[14:57] <aquarius> abentley, brilliant, that works, thanks
[14:58] <jtv> abentley: the branch scanner wouldn't happen to run in autocommit, would it?
[14:59] <abentley> aquarius, you're welcome.
[14:59] <abentley> jtv, I don't think it does.  It should just use the default, like other job scripts.
[15:00] <jtv> ok
[15:09] <aquarius> abentley, new question: I'd like to work out what the list of bugs that I've touched this week is (i.e., commented on, changed status of). I'm not sure I can find a good way of doing that#
[15:09] <aquarius> ?
[15:15] <Lord-Readman> Hello, have a problem were something wont work in launchpad
[15:15] <Lord-Readman> https://translations.edge.launchpad.net/ubuntu/lucid/+source/enscript/+pots/enscript/en_GB/+translate?show=untranslated
[15:15] <Lord-Readman> those two will not translate
[15:16] <Lord-Readman> once that is translated the entire en_GB translation is 100% :-)
[15:17] <Lord-Readman> so could an admin please take alook
[15:19] <henninge> Lord-Readman: I suspect that this is a bug in the source code.
[15:20] <henninge> no, leave out the "I suspect", it *is* a bug in the source code.
[15:20] <Lord-Readman> ah well i downloaded the .po
[15:20] <Lord-Readman> when processed i will do it there
[15:20] <Lord-Readman> and reupload
[15:20] <Lord-Readman> hopefully that will fix it
[15:20] <henninge> The English singular should be "%d line was %s"
[15:21] <Lord-Readman> why would it?
[15:21] <danilos> Lord-Readman, PO file upload won't help if it's something like wrong flags on the message
[15:21] <Lord-Readman> oh
[15:21] <abentley> aquarius, have you looked at Person.searchTasks?
[15:21] <henninge> danilos: I still find it strange that we see no error message.
[15:22] <danilos> henninge, that seems related to 'untranslated' filter, doing it on shows the error message: https://translations.staging.launchpad.net/ubuntu/lucid/+source/enscript/+pots/enscript/en_GB/72/+translate
[15:22] <danilos> Lord-Readman, basically, packager/upstream need to fix the template
[15:23] <henninge> danilos: I see
[15:23] <danilos> Lord-Readman, it'd be worth filing a bug under enscript source package and adding a task for ubuntu-translations project
[15:23] <Lord-Readman> ok
[15:24] <danilos> Lord-Readman, btw, the workaround you can use is to translate initial English string to "%d line was %s"
[15:25] <Lord-Readman> wont that break it?
[15:25] <Lord-Readman> in the app?
[15:26] <danilos> Lord-Readman, most likely not, but depends on the actual original string usage
[15:26] <Lord-Readman> done
[15:30] <aquarius> abentley, I have indeed. Doesn't that only return bugs that are assigned to me? launchpad.me.searchTasks doesn't include bugs that I've commented on, does it?
[15:31] <abentley> aquarius, I don't work on bugs, so I don't know anything about that part of the API.
[15:31] <aquarius> abentley, ah, OK. is that a rockstar thing?
[15:31] <abentley> aquarius, no
[15:32] <abentley> I and rockstar work on the code team, not the bugs team.
[15:32] <aquarius> ah, OK. Who knows about the intersection of bugs and launchpadlib?
[15:32] <aquarius> abentley, you've proved dead knowledgeable about the bits you do work on, though, for which much thanks :)
[15:34] <abentley> aquarius, members of the bug team include allenap, gmb, intellectronica, deryck
[15:34] <intellectronica> aquarius: whassup?
[15:34] <intellectronica> can't patch bugtasks?
[15:34] <aquarius> aha, gmb and intellectronica, I don't mind poking them :)
[15:35] <gmb> For the purposes of this question, I disavow myself of all knowledge of anything.
[15:35]  * deryck just waves
[15:35] <aquarius> intellectronica, I would like to, using launchpadlib, get a list of the bugs that I have touched in some way (commented on, changed status of) in the last week
[15:35] <aquarius> deryck, I'm pretty sure that intellectronica has stolen cigarettes from me in the past so he's in the chair ;-)
[15:36] <deryck> heh
[15:36] <intellectronica> aquarius: unfortunately, the launchpad bug tracker doesn't really allow you to search anything by time spans, so you'll have to do much of the work locally
[15:36] <aquarius> intellectronica, does launchpad.me.searchTasks return bugs that I've commented on, or just bugs where I'm assignee?
[15:37] <intellectronica> aquarius: the latter
[15:37] <aquarius> that's what I feared :(
[15:37] <intellectronica> aquarius: though bugs you've commented on will almost always be a subset of the bugs you're subscribed to, so you can start with that
[15:38] <aquarius> how do I get bugs I'm subscribed to?
[15:38] <aquarius> I can do something.searchTasks(bug_subscriber=launchpad.me), but I don't know what "something" is.
[15:38] <aquarius> is there just "launchpad.searchTasks"?
[15:39] <intellectronica> aquarius: you pass yourself as the bug_subscriber parameter
[15:39] <intellectronica> aquarius: no, there's no global search. person is the only thing that crosses project boundaries and you can search on
[15:40] <aquarius> but launchpad.me.searchTasks(bug_subscriber=launchpad.me) will only get bugs where I'm the owner, right?
[15:40] <intellectronica> aquarius: you'll have to run the search several times over all projects (or packages or whatever) you want to get results from
[15:40] <aquarius> I was worried you were going to say that.
[15:41] <aquarius> OK. take https://edge.launchpad.net/libubuntuone, for example. It's "Part of" https://edge.launchpad.net/ubuntuone. What's https://edge.launchpad.net/ubuntuone in launchpad language? Is it a project?
[15:41] <aquarius> aha, it might be a project_group?
[15:42] <intellectronica> aquarius: it's a 'project group'
[15:42] <aquarius> aha, and it has .searchTasks! yay :)
[15:43] <aquarius> so ralistically I have to walk the output of launchpad.projects["ubuntuone"].searchTasks(bug_subscriber=launchpad.me) and test each one to see if I've touched it in the last week? I don't suppose the bugs come back in descending order of activity?
[15:44] <intellectronica> aquarius: what do you mean by 'touched it'?
[15:44] <aquarius> commented on it, set its status to something else
[15:45] <intellectronica> aquarius: it's quite easy to tell if you commented lately, but finding out if you changed metadata on it is harder, because we only keep this info in the activity log, which is, essentially, text
[15:45] <intellectronica> so you can sort of do it but you'll have to do some parsing
[15:46] <intellectronica> aquarius: but you only care about stuff that mentions yourself that's not so hard. we do keep a real link to the person who took the action
[15:47] <aquarius> that'd be cool
[15:47] <aquarius> bugs don't have a last_time_anyone_did_anything_to_this_bug attribute, do they? I can't find one (that would be a quick way to discard bugs that haven't been touched this week by anyone)
[15:48] <intellectronica> aquarius: they do
[15:48] <intellectronica> aquarius: Bug.date_last_updated
[15:48] <aquarius> aha, winner
[15:49] <aquarius> I was looking at bug_task, not bug!
[15:49] <intellectronica> aquarius: but i promised you access to the activity log, and looking at the api now i don't find it. maybe i was hallucinating and this never got exported via the api
[15:50] <allenap> intellectronica, aquarius: a_person.searchTasks(), by default, will return bugs related to a_person, be they the assignee, the reporter, a subscriber or a commenter, afaict. See get_related_bugtasks_search_params() in lp.bugs.model.bugtask.
[15:50] <aquarius> o rly? magic darts
[15:51] <intellectronica> allenap: ah, nice, so that simplifies things
[15:51] <intellectronica> the activity log isn't exported, though
[15:51] <aquarius> does status in a searchTasks request default to all statuses, or all open statuses?
[15:52] <allenap> aquarius: Open.
[16:03] <aquarius> ok, looks like I have something approximating what I need. thanks intellectronica, allenap, abentley!
[16:05] <intellectronica> cool
[16:11]  * kfogel is away: reboot
[16:30] <kirkland> can someone explain what the burning bush from zelda means with respect to bugs?
[16:34] <cody-somerville> lol
[16:38] <intellectronica> kirkland: http://blog.launchpad.net/bug-tracking/bug-heat
[17:18] <kirkland> intellectronica: thanks
[21:07] <keithy> Hi, any admins around?
[21:08] <keithy> my emails to support about licencing of squeak project are not illiciting a response?
[21:16] <mneptok> keithy: i think you mean "eliciting" ;)
[21:21] <keithy> maybe I do
[21:37] <mneptok> keithy: maybe you do mean "illicit," and you want suggestions on illegal means of distributing Squeak. :)
[21:39] <keithy> you would think so
[21:39] <keithy> given how hard it is to get the licence situation sorted
[22:29] <c7p> hey im trying to access https://translations.launchpad.net/ubuntu/lucid/+source/gnome-power-manager/+pots/gnome-power-manager/el/+translate and also other pages and i get an error (please try again etc ... )
[23:32] <kenix> hello
[23:33] <kenix> is there anyone arround here?
[23:34] <mwhudson> yes
[23:34] <mwhudson> although i'm about to have lunch
[23:34] <kenix> Okai , I've a lil problem when uploading to the PPA
[23:36] <kenix> Checksum doesn't match for /home/ken/ubudsl/ubudsl_1.0.0.301-1karmic.dsc
[23:36] <wgrant> kenix: What is the command that you're running?
[23:37] <kenix> dput ppa:ubudsl-maintainers/ubudsl ~/ubudsl/ubudsl_1.0.0.301-1karmic_source.changes
[23:37] <wgrant> kenix: So, that normally means you've caused the .dsc to be rebuilt since the .changes was created.
[23:37] <wgrant> Try running debuild -S again.
[23:38] <wgrant> But... that version number is a bit strange.
[23:38] <kenix> Ow
[23:39] <wgrant> Check out the Versioning section on https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage
[23:42] <kenix> oki
[23:42] <kenix> thank you a ot
[23:42] <wgrant> np
[23:42] <kenix> lot
[23:42] <persia> What's wrong with 1.0.0.103-1karmic?
[23:42] <persia> s/103/301/
[23:43] <wgrant> persia: 1.0.0.301-1 is not in Debian, and it is not a conventional way to indicate the series.
[23:43] <wgrant> And in the chaotic world of PPAs, a little bit of versioning consistency is nice.
[23:43] <persia> I guess.  I'm just not a fan of ~${series} for any number of reasons.
[23:44] <persia> And I'm not a fan of including "ubuntu" in the version for PPAs, because it confuses dpkg-source
[23:44] <wgrant> I version new packages 0ppa1, normally.
[23:45] <wgrant> Less than just about anything else.
[23:46] <persia> I use -0persiaX myself, but same idea.
[23:46] <wgrant> Right, I would like to.
[23:46] <wgrant> But both the PPAs I upload to are > ubuntu
[23:47] <persia> dpkg-compare-versions tells me -0wgrant > -0ubuntu :)  But yeah.
[23:47] <wgrant> persia: Right, which means if the package ever ends up in Ubuntu then mine will clobber it.
[23:47] <wgrant> Which is wrong.
[23:47] <persia> Right.
[23:47] <persia> I mostly only use the PPA for brand-shiny new packages where it doesn't matter.
[23:48] <persia> (as much)
[23:48] <persia> But -0ppa seems good for new stuff, for consistency.
[23:48] <persia> I guess my issue is "To do this, increase the Ubuntu version number and add a suffix of ~ppan (where n is your package's revision number)."
[23:49] <wgrant> Right, that sort of assumes that the version is destined to become the next primary archive release.
[23:49] <persia> Should we perhaps instead have "To do this, add the suffix "+ppan (where n is your package's revision number)."?  Or does that break also?
[23:49] <wgrant> I think that is better.
[23:49] <wgrant> We should develop and provide provide guidelines for all the common cases.
[23:50] <persia> Where the common cases are new packages and private tweaks?
[23:50] <wgrant> New packages, private tweaks, and possibly something different for packages that are just thrown into a PPA for quick testing before release into primary.
[23:50] <wgrant> ~ppan works well for the last case.
[23:51] <wgrant> 0ppa1 for the first, +ppa1 for the second.
[23:53] <persia> I think anyone who performs case 3 is expected to be familiar enough to make it work.
[23:53] <persia> Plus +ppan won't break anything (except the kernel) if used that way.
[23:53] <wgrant> Right.
[23:54] <wgrant> Using ~ppan is probably just a bit more semantically correct and obvious if used consistently.
[23:55] <persia> Right, but based on what I see of usage patterns, that use case is the minority, and doesn't tend to include those who need to read that documentation.
[23:55] <wgrant> Indeed.
[23:56] <wgrant> But if we include it there, maybe people will see that it has a real purpose and avoid it like the plague.
[23:56] <persia> Any suggestions on where to put the hint for new packages?  Also, did I miss anything in my edit?
[23:56] <wgrant> You have a mismatched quote before +ppan
[23:56] <persia> I'd like to think that, but I also suspect many folk would like to think their PPA upload will be the next Ubuntu revision
[23:56]  * wgrant reads.
[23:57]  * persia has seen many bugs in which someone asks something like "why hasn't this been pulled from my PPA already?  I made it available ages ago."
[23:57] <wgrant> Urgh.
[23:57] <wgrant> Good point.
[23:58] <wgrant> Do you want to maybe re-embolden the 'n' in '+ppan'?
[23:59] <persia> embolden?  I thought it was italicised.
[23:59]  * persia tries to remembe syntax