[02:25] <falktx_> hey there
[02:26] <falktx_> I'm having a *major* launchpad bug!
[02:27] <falktx_> I have a launchpad team with a set of ppas
[02:27] <falktx_> this one has the problem:
[02:27] <falktx_> https://launchpad.net/~kxstudio-team/+archive/hydrogen
[02:28] <falktx_> full link to all package list -> https://launchpad.net/~kxstudio-team/+archive/hydrogen/+packages?field.name_filter=&field.status_filter=published&field.series_filter=
[02:28] <falktx_> I can see there for example,
[02:28] <falktx_> libgen3d (1.0.1svn940-1) karmic; urgency=low
[02:29] <falktx_> from a 'salikhmetov', which is not part of the team!
[02:30] <falktx_> from what I can tell, this new packages have been copied (it has, for example, 'Copied from ubuntu karmic in PPA for Animux')
[02:30] <wgrant> falktx_: The uploader is the person who initially uploaded the package to Launchpad -- it's not who did the copy.
[02:30] <falktx_> this is very serious
[02:31] <wgrant> Someone in your team copied the package into your PPA.
[02:31] <falktx_> I seriously doubt that
[02:32] <falktx_> that ppa is for a single project (only binaries for hydrogen), and the original devs are not part of the team
[02:32] <wgrant> The team has 13 members.
[02:32] <falktx_> other team members don't usually do uploads (last one was a year ago)
[02:34] <falktx_> I'm the only active developer on the team that does uploads right now
[02:35] <falktx_> wgrant: is there a way I can check who did these copies?
[02:35] <wgrant> I'm checking.
[02:35] <wgrant> It's not visible in the UI at the moment, stupidly.
[02:35] <falktx_> oh, ok
[02:36] <falktx_> wgrant: please do let me know
[02:38] <falktx_> wgrant: any idea how much that will take?
[02:39] <jbicha> falktx_: I blame dreamstudio
[02:40] <falktx_> jbicha: oh, you got the info, is this correct, wgrant?
[02:40] <jbicha> but it's just a guess, without it showing up it's hard to tell
[02:40] <falktx_> oh, ok
[02:40] <jbicha> no I have no idea, I just looked at people's karma
[02:41] <falktx_> I need to have sure, as I'll probably need to speak with this person
[02:41] <jbicha> right, of course
[02:41] <jbicha> maybe it doesn't even show up in karma
[02:43] <falktx_> hm, I can compare upload dates I guess
[02:43] <falktx_> jbicha: does copying packages counts for karma?
[02:45] <falktx_> copies have been made in 2011-08-12, so I guess it's not dreamstudio
[02:47]  * falktx_ only know realizes about so many karma points... :)
[02:47] <falktx_> err, *now
[02:48] <jbicha> karma's pretty useless as it doesn't give enough info so I'm going to stop making uneducated guesses
[02:48] <wgrant> This package has been copied around a lot, so it's taking a little longer than expected.
[02:48] <wgrant> A dreamstudio PPA does show up in the list of copies, though.
[02:49] <falktx_> I checked all users' karma, and no one has relevant points on 2011-08-12
[02:49] <wgrant> Copies don't show give karma.
[02:49] <falktx_> let me check that ppa
[02:49] <falktx_> oh, ok
[02:49] <wgrant> They're plagiarism, not karma :P
[02:51] <falktx_> I have to guess dreamstudio is the author of this, since he seems to have been copied a lot of packages into his ppas
[02:52] <wgrant> This very package is in one of his PPAs three times.
[02:52] <falktx_> wgrant: how far are you from a real answer?
[02:52] <falktx_> oh
[02:53] <falktx_> wgrant: which package?
[02:53] <wgrant> That same libgen3d package has been copied into http://launchpad.net/~dreamstudio/+archive/graphics-testing three times.
[02:54] <falktx_> ah yes, nice catch
[02:54] <falktx_> wgrant: I guess that's it, thanks!
[02:54] <wgrant> I haven't found a log entry for this particular copy yet, but it seems very likely that it was dreamstudio.
[02:54] <falktx_> I was really worried this was some kind of launchpad bug...
[02:55] <falktx_> err, now I need to check all my team ppas for non-wanted copies...
[02:56] <jbicha> falktx_: it is a bug, it should tag a copy with who did it & show it
[02:56] <wgrant> Ahhh.
[02:56] <falktx_> ah, yes, that will surely be helpful
[02:56] <wgrant> It helps if I look at the right day of logs.
[02:56] <wgrant> It was dreamstudio.
[02:56] <falktx_> wgrant: I just deleted the packages
[02:56] <wgrant> I was looking at the day after.
[02:56] <falktx_> oh, thanks!
[02:57] <wgrant> (most of the servers are UTC, but the logging server is still BST, and this occured at 00:09 UTC.
[02:57] <wgrant> So it was right in that hour where the log dates are confusing :(
[02:58] <falktx_> haha, ouch
[02:58] <wgrant> Anyway, yeah, copied from ppa:dreamstudio/graphics-testing, by dreamstudio.
[02:58] <falktx_> yep, thanks again
[02:59] <falktx_> I should have a word with him ;)
[03:10] <falktx_> well, I'm off
[03:10] <falktx_> thanks, and keep working on launchpad cause it rocks ;)
[07:52] <noodles775> hey all. Is there a way to trigger an update of the MP diff of a branch that I don't own?
[07:53] <noodles775> (ie. without needing to modify the branch itself - trunk has changed to now include much of what's in the diff)
[07:53] <wgrant> noodles775: There's not, unfortunately.
[07:53] <noodles775> Currently I'm just generating it locally (easy enough)
[07:53] <noodles775> wgrant: ah, ok. Thanks!
[08:17] <mrevell> Hello 'padders
[08:33] <nigelb> mrevell: aww, no anniversary blog post ;)
[08:33] <mrevell> nigelb, Not yet, it's still yesterday somewhere, I'm sure.
[08:33] <mrevell> :)
[08:33] <nigelb> hehe
[08:33] <mrevell> I didn't have time to do it justice yesterday.
[08:59] <Tblue> Hello. So unfortunately, the developer who owned our project on Launchpad recently passed away, is there any way to transfer ownership?
[09:00] <Tblue> I guess LP answers would be the right place to ask?
[09:03] <StevenK> Tblue: Yes.
[09:05] <Tblue> StevenK: Well, I'll do that then. Thanks. :)
[12:21] <ahasenack> hi guys, how do I build a package with a recipe if a) base branch has debian/ already b) I want to nest another branch for debian/
[12:22] <ahasenack> I can't use the "run" command in launchpad to rm -rf debian before nesting, it's forbidden
[12:22] <tumbleweed> afaik the only way is to merge rather than nest
[12:23] <ahasenack> but these branches diverge, one only has debian/, the other has the source code
[12:24] <tumbleweed> yes, it means preparing a different branch
[12:33] <wgrant> ahasenack: Why doesn't your branch contain the full source?
[12:34] <ahasenack> wgrant: why should it? It's just a packaging branch
[12:35] <wgrant> ahasenack: All Ubuntu branches are full source.
[12:35] <wgrant> It is the standard nowadays.
[12:37] <CarlFK> I think I messed up my package name version numbers, so apt-get isn't getting the version I want
[12:37] <CarlFK> how do I force a version from my ppa?  https://launchpad.net/~carlfk/+archive/ppa/+packages  I want          dvswitch - 0.9.1-ubuntu1, I am getting 0.9~rc2-ubuntu3
[12:37] <CarlFK> is there some way to delete the older version?
[12:38] <CarlFK> oh crap.. maveric
[13:33] <ahasenack> wgrant: found this: https://bugs.launchpad.net/bzr-builder/+bug/617653
[13:33] <ahasenack> wgrant: that would help me too, I would just "run rm -rf debian" before nesting
[13:39] <wgrant> ahasenack: Why would you have to keep updating the packaging branch with code changes? And even if you did want to update the code when you changed the packaging, you can just bzr merge...
[13:42] <ahasenack> wgrant: it's not a show stopper bug, it's a convenience to be able to use a separate packaging branch with just debian/, and the nest command, which was created for this purpose I think
[13:43] <ahasenack> specially since many packages are non-native, this mimics this type of package better I think
[13:44] <ahasenack> but policies are policies, nm, I will yell at the fellow developers who told me to use a separate packaging-only branch instead of here :)
[13:45] <wgrant> I would suggest that it's not a convenience so much as unnecessary ugliness :)
[13:45] <ahasenack> wgrant: it's quite easy to forget that patches are applied after you build, so one has to be careful when running "bzr commit"
[13:45] <ahasenack> I wouldn't want to change the source code in a branch dedicated to packaging only
[13:50] <wgrant> Ah, if you are using patches in a bzr branch, that is indeed a mess.
[13:50] <sdeziel> hi all. I made a mistake when editing https://bugs.launchpad.net/openvswitch/+bug/829250. I accidentally added a link to www.nlnetlabs.nl/bugs-script/#405 but that was meant for another bug.
[13:51] <sdeziel> I would like to cleanup the unrelated stuff that imported to the bug in question on LP
[13:53] <sdeziel> can anyone provide me instruction on how to do this cleanup ?
[14:13] <pfarrell> hi! I have a ppa question. I have a ppa in which I built a source pkg which has both arch-dependent and arch-independent parts. When I look at the build, it says it only produced the arch-specific parts: https://code.launchpad.net/~fluidity-core/+archive/ppa/+build/2747358
[14:14] <pfarrell> where do the arch-independent parts get build? is it on the x86 builder?
[14:14] <pfarrell> (or the i386 builder, I mean)
[14:15] <TheEvilPhoenix> pfarrell:  are they separate packages, these parts?
[14:15] <pfarrell> yes
[14:15] <pfarrell> one source package, 5 binary packages
[14:16] <TheEvilPhoenix> wasnt my question
[14:16] <TheEvilPhoenix> were the architecture-dependent source parts and architecture-independent package parts separate?
[14:16] <wgrant> pfarrell: Architecture-independent binaries are only built once -- in the i386 build.
[14:16] <TheEvilPhoenix> oop i'll let wgrant answer :P
[14:16] <pfarrell> wgrant: ok, thanks, that answers my question :-)
[14:16] <TheEvilPhoenix> i should be in class anyways
[14:49] <caravena> Hello,  I admin of report in LP.
[14:50] <caravena> I'm administrador of report in LP
[14:50] <caravena> https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/832378
[14:54] <caravena> 1) pgraner create report of empathy 2) pgraner change status of private to public 3) caravena (I'm) change of status -> public to private (CoreDump) 4) #Cha chan# I'm admin of bug
[15:02] <maxb> There's no such thing as an administrator of a bug
[15:07] <caravena> maxb, Talk to Pedro Villavicencio (pvillavi@ubuntu.com) and I said okay. Thanks.
[15:08] <caravena> maxb, Sorry. Not problem
[15:12] <hakermania> When should I mark a bug as 'Fix Released'? When there's an upstream release fixing the bug? And when saying an upstream release we mean a new PPA package on LP or a new update on USC?
[15:14] <tumbleweed> hakermania: https://wiki.ubuntu.com/Bugs/Status
[16:08] <joey> mrevell: do you remember how to export stuff from BPs in LP as csv?
[16:13] <joey> mrevell: I think I found what I was thinking about... can't do it in LP but can do +rdf
[16:13] <mrevell> joey, Hey, I half-remember how to export a sprint's attendee list.
[16:13] <mrevell> joey, Ah, okay
[16:14] <joey> mrevell: https://blueprints.launchpad.net/linaro/+rdf  :-)
[16:14] <mrevell> Aha :)
[16:15] <mrevell> Hey, I don't wanna be nosey, but do you have a use in mind for that?
[16:17] <joey> mrevell: a PM of mine NEEDS an API based export of blueprints on a milestone (as well as bugs, etc) so he can import that into a project management tool.  So he's learning how to use the LP API. In the meantime he wanted an easy way to extract stuff so he could parse it into an XML format for the PM tool.
[16:18] <joey> the API is the right way to go but the +RDF is likely to be the fast solution to the immediate problem.
[16:19] <joey> There is something like this that matsubara-lunch wrote for OEM but I can't use that in Linaro because...it's not OEM. :-)
[16:20] <mrevell> matsubara-lunch may be able to modify that for you. Do you need anything new exposed in the API for this joey?
[16:21] <joey> mrevell: I don't think so.  I'd have to look at the latest apidoc but I think it has everything we need.  We just need a one-way/RO connector to extract stuff from LP.  Since we  have essentially all that data being used in http://status.linaro.org I feel pretty confident that it already exists to the extent we need it
[16:22] <mrevell> Cool.
[16:22] <joey> I've suggest my pm chat with james_w about it since he's the mastermind behind status.l.o
[21:12] <grimm_> Hello there! Can somebody help me with the bug triage process please?
[21:13] <micahg> grimm_: for which project?  ubuntu?
[21:15] <grimm_> micahg: Hello! I was reading about the triage process on the Launchpad project.
[21:16] <grimm_> micahg: Maybe the problem is generic... Do I have to be a member of any team in order to triage a launchpad project bug? I cannot change the importance and the status of any bug...
[21:17] <micahg> grimm_: yes, to change importance, one has to be a member of the bug supervisor team for that project
[21:17] <micahg> some statuses are restricted to that group as well (triaged, won't fix)
[21:19] <achiang> does anyone here have experience writing tools to sync launchpad bugs with an external bug tracker?
[21:19] <grimm_> micahg: Thanks. The strange thing is that i can add tags but not importance or status. Is that the expected behaviour?
[21:20] <achiang> this is different than simply adding a watch on an upstream bug. i'm thinking (minimally) of syncing up the comments
[21:20] <micahg> grimm_: well, depending on which status you're trying to set, a logged in user should be able to set a bug to confirmed
[21:21]  * achiang finds #557032
[21:21] <grimm_> micahg: thats true. the other options of status seem enabled but never tried them.
[21:22] <achiang> oh, and #785173
[21:22] <grimm_> micahg: thanks a lot for your time. i'll try to locate the relevant team for the launchpad triage process
[21:26] <micahg> grimm_: it's the launchpad security team ATM
[21:31] <grimm_> micahg: it's a pitty that its not mentioned in the wiki
[21:31] <grimm_> micahg: thanks a lot
[21:34] <micahg> grimm_: it's here: https://bugs.launchpad.net/launchpad on the top right
[21:37] <grimm_> micahg: you are right. i never saw this
[21:39] <grimm_> micahg: lol, i cannot apply to join the team! the team is restricted! thanks anyway!
[22:17] <jo-erlend> I keep forgetting how to file a bug against ubuntu when you don't know which package to file against. It's really annoying that I have to read this long page every time.
[22:18] <jo-erlend> in this case, it's an issue that enables you to gain access of a locked screen by pressing a keyboard combination. I have no idea what package to file that agaist.
[22:20] <jo-erlend> and since it doesn't really affect me in any way, I keep postponing the report, but it should really be fixed. In an office environment, that can be a really bad thing.
[23:10] <micahg> jo-erlend: ubuntu-bugs would be a better place to ask, but it's Friday, so idk if anyone's around
[23:12] <jo-erlend> that feature is really annoying.