[00:00] <gmb> wgrant: Ohnononnono. We want that in the bug tracker. It's a matter of resources and other priorities.
[00:01] <gmb> (Two hours later, I grant you, but hey, such is asynchronous communication, and I wanted to stick my oar in before I went to bed.)
[00:02] <wgrant> gmb: Oh good, you've changed your attitude. It was very strongly shot down years ago.
[00:05] <gmb> wgrant: No, I haven't changed my attitude, I'm just expressing what the bugs team have said themselves. Whether it has been shot down from on high in the past I don't know (and our data model - or at least our understanding of how to refine it - is better now). Of course, there's always the chance that any new feature will get the stompy boot of doom applied to it by the people who have the last word.
[00:07] <wgrant> gmb: 'You' meaning the LP developer collective, sorry.
[00:08] <gmb> wgrant: Ah right. Well, like I said, I can't speak for the PTB but in the trenches it's something we'd very much like to see.
[00:08] <wgrant> gmb: Excellent, thanks.
[00:08] <gmb> np.
[00:17] <wgrant> Should a single PPA really be allowed to die up all of the PPA buildds for ages?
[00:17] <wgrant> s/die/tie/
[02:03] <dnyy> Is there a channel for help with package building?
[02:12] <thumper> dnyy: not a specific one that I know of
[02:12] <thumper> not related to launchpad anyway
[02:14] <nhandler> dnyy: #ubuntu-motu might be your best bet (if the packages are for Ubuntu)
[02:15] <dnyy> they are, thanks thumper and nhandler. :)
[02:16] <nhandler> You're welcome dnyy
[03:00] <wgrant> Soyuz, stop lieing to me!
[03:01] <wgrant> It is telling me that I copied packages from a PPA which is different from the one I actually copied them from.
[03:08] <det> Are there any plans for launchpad to be able to build packages for Debian ?
[03:11] <thumper> det: it has been considered
[03:11] <mwhudson> det: in the "hmm, yeah, that would be nice" sense, yes
[03:11] <thumper> but I'm not sure on the current status of the plans
[03:11] <det> It would be really nice, IMO, and show that Ubuntu gives back to Debiab,
[03:12] <det> I currently maintain packages for a game for Ubuntu users, it seems a shame that Debian users cant piggyback off my packaging, when the source packages are compatible with both.
[03:13]  * lamalex dreams of a universal build service
[03:13] <lamalex> maybe when LP is open sourced..
[03:14] <thumper> heh
[03:14] <lamalex> suse, red hat, debian, ubuntu packages all in the same place
[03:14] <lamalex> that'd be a dream come true for projects
[03:14] <thumper> lamalex: interesting dream
[03:14] <lamalex> "I have a dream"
[03:15] <lamalex> thumper: it should be that hard, there are already great build services for most major distros
[03:15] <lamalex> shouldn't
[03:15] <lamalex> they just need an abstracted front end and probably a roll of duct tape
[03:15] <mwhudson> yeah, specifying build dependencies should be a breeze?!
[03:16] <lamalex> mwhudson: i'm not voting for one service that builds N packages
[03:16] <lamalex> you say I want a suse package, give it the sauce to make a suse package, it hands it off to the suse builder
[03:17] <mwhudson> oh right
[03:17] <mwhudson> that sounds a lot saner :)
[03:17] <lamalex> haha indeed
[03:17] <lamalex> it just gives projects one place to tell users to get packages
[03:18] <lamalex> which has value
[03:18] <lamalex> and increases LPs appeal to projects
[03:20] <wgrant> lamalex: Note that the relevant bit of Launchpad isn't being open-sourced.
[03:21]  * lamalex puts his head down
[03:21] <lamalex> is that Charlie Brown music I hear?
[03:24] <wgrant> Hm?
[03:24] <lamalex> nevermind, arrested development reference
[03:25] <wgrant> We can hope that the lords of Launchpad will change their minds soon.
[03:28] <mwhudson> -s, possibly
[03:28] <wgrant> Well, yes.
[03:29] <maxb> It's a shame Soyuz isn't going to be opened. I'd be interested in it purely from the PoV of understanding Ubuntu better
[03:29] <lamalex> I'm going to assume Soyuz is the PPA part
[03:29] <wgrant> lamalex: Soyuz is Launchpad's package management component, which deals with both PPAs and Ubuntu itself.
[03:30] <lamalex> gotcha
[03:30] <wgrant> (yet apparently it doesn't include the bit that deals with Debian in Launchpad... I'm not entirely sure what is and isn't included in the open sourcing)
[03:31] <maxb> Does launchpad deal with Debian other than in the sense of bugtracker linking?
[03:31] <maxb> Oh, and using P-a-s (wrongly, I might add)
[03:31] <wgrant> maxb: It imports the packages.
[03:32] <wgrant> The Debian imports have nothing to do with P-a-s.
[03:33] <wgrant> Ooh dear.
[03:33] <wgrant> Launchpad is not going to be happy with me, I don't think... I wonder how that will work.
[03:44] <wgrant> Aw, it didn't break. It just didn't publish.
[03:46] <maxb> ooh?
[03:48] <wgrant> I got a Debian package into my PPA. i was hoping it would crash the publisher or something creative like that, but it apparently does really only publish Ubuntu.
[04:22] <mkanat> What's the canonical URL for a bug? bugs.launchpad.net/bugs/123456 ?
[04:24] <thumper> mkanat: that'll work
[04:25] <mkanat> Okay. How many variations are there? Just bugs/12345$ and +bug/12345$ ?
[04:25] <mkanat> (In regex terms.)
[04:26]  * thumper pokes ubottu
[04:26] <thumper> bug 123
[04:26] <thumper> mkanat: that url will redirect to the main bug-task
[04:26] <thumper> mkanat: so there are lots of variations depending on what the bug relates to
[04:27] <mkanat> Sure, but they all end in either +bug/1234 or bugs/1234
[04:27] <thumper> mkanat: however bugs/1234 will work
[04:27] <thumper> probably
[04:27] <thumper> I can't say with 100% certainty
[04:27] <mkanat> Okay.
[04:27] <thumper> but most likely
[04:27] <mkanat> This is basically for an API, so I just need to know all the possible variations of URLs that people could give me.
[04:32]  * wgrant doesn't know of any other formats.
[04:32] <mkanat> Okay. :-)
[06:42] <StevenK> I'm having trouble creating a branch, with bzr giving me a permission denied trying to push to bzr+ssh://bazaar.launchpad.net/~ubuntu-mobile/unr/ubuntu-netbook-remix-default-settings
[06:54] <wgrant> StevenK: Pastebin the output, please.
[06:56] <StevenK> http://paste.ubuntu.com/108471/
[06:59] <james_w> StevenK: does that branch exist?
[07:00] <StevenK> james_w: Nope, I'm trying to create it
[07:00] <wgrant> Wow. It is OOPSing at me and telling me that the project doesn't exist, depending on whether I do it on edge or staging.
[07:00] <persia> Maybe because lpnet/unr is a metaproject?
[07:00] <james_w> that's probably it
[07:00] <wgrant> Oh, so it is.
[07:00] <wgrant> I didn't notice that.
[07:01] <wgrant> It still shouldn't OOPS.
[07:01] <StevenK> Agreed
[07:05] <wgrant> Mmmm. Package branches work on staging now.
[07:07] <persia> james_w, about package branches: how would these interact with Vcs-* in debian/control?  Would it be sensible to just use package branches, or to have also another branch?
[07:08] <wgrant> Vcs-* fails to make sense for Ubuntu packages once we have and use package branches.
[07:08] <james_w> Vcs-* for most packages will be essentially lp:ubuntu/$suite/$package
[07:09] <james_w> however, if there is say a SVN repo used for collaboration between Ubuntu and Debian then that is useful information
[07:09] <wgrant> $suite or +latest?
[07:09] <james_w> so we shouldn't overried it for every package, but for consistency have the tools default to those branches
[07:10] <wgrant> Ah.
[07:10] <james_w> well, that's one of the under-specified things about Vcs-*, do you document the branch that things came from, or the branch for the latest code, or the branch that you want changes submitted back to?
[07:11] <persia> Within the original context, it's usually been the second and third, which were typically identical.
[07:12] <persia> So would you recommend not specifying Vcs-* for ubuntu-local native packages?
[07:12] <persia> And just letting the package branching infrastructure manage it?
[07:12] <james_w> that's not what I said
[07:12] <james_w> having that information would be useful
[07:13] <persia> But it should be lp:ubuntu/$suite/$package ?
[07:13] <james_w> but the toolset isn't based on that information
[07:13] <james_w> (the toolset not being Debian things such as debcheckout)
[07:13] <persia> heh
[07:14] <persia> So, when preparing a new ubuntu-local native package not expected to be used externally to Ubuntu, what would you recommend?
[07:34] <james_w> persia: sorry, missed your question. I would recommend adding the Vcs-* header, pointing to the package branch.
[07:34] <persia> So lp:ubuntu/$suite/$package ?
[07:40] <james_w> yeah
[07:40] <james_w> the expanded version probably
[07:42] <persia> right.  Thanks
[09:36] <mvo> hello! what is the best way if I want to upgrade a branch on LP? when I try it, I get: "starting upgrade of sftp://mvo@bazaar.launchpad.net/%7Eubuntu-core-dev/app-install-data-ubuntu/ubuntu/; bzr: ERROR: File exists: '/~ubuntu-core-dev/app-install-data-ubuntu/ubuntu/backup.bzr': mkdir failed: unable to mkdir" - is there way around this other than poking with sftp manually around?
[09:36] <mvo> (and I I somehow trigger it remote so that I don't have to do all the dowload/upload? this branch is really big)
[09:36] <mvo> $ du -sh .bzr
[09:36] <mvo> 68M	.bzr
[09:51] <james_w> mvo: you have to delete the backup.bzr using lftp or similar currently
[09:51] <james_w> and unfortunately there is no way to do it server side yet, that is being worked on
[09:52] <mvo> james_w: ok, thanks. I whish there was a LP button "update my branch" :)
[10:54] <shilbert> Hi, I have started to read up on uploading packages to my PPA. I am stuck at multiple points in the procedure. Let me try to explain what I aim for
[10:54] <shilbert> I am from the GNUmed team
[10:55] <shilbert> there are uptodate packages for debian in sid
[10:55] <shilbert> and I would like to get these into the GNUmed PPA for Hardy, Intrepid and Jaunty
[10:55] <shilbert> I am looking for advice on how to best achieve this
[10:56] <shilbert> First attempt was to go through the complete build and upload from source cycle
[10:57] <shilbert> This fails as to it apparently uploads ok but I don't receive any email on success or failure nor does it appear in the PPA
[10:57] <shilbert> So I found this manual where ist states that one can copy from one PPA to another
[10:58] <shilbert> this however is not an option as GNUmed is only in Debian Sid and not in another PPA
[10:58] <shilbert> Please advise on the best way to do this
[10:58] <noodles775> shilbert: Yes, I'd recommend trying to find out if and why the builds from the sources failed...
[10:59] <noodles775> Was it hours/days ago that you uploaded the sources?
[10:59] <shilbert> I might be impatient and did not know it can take hours, it was only two hours ago, sorry if that is the problem
[11:00] <shilbert> is there any sync possible from Debian Sid ?
[11:00] <noodles775> No problem... I just recall someone the other day being given the advice "Just wait a bit"
[11:01] <shilbert> I am just starting to learn packaging and all I want to do is copy it from Debian :-)
[11:01] <noodles775> shilbert: have you gone through the video tutorials? I reckon they're a great way to start...
[11:02] <shilbert> Sorry did not find those. I have read many pages starting with launchpad help
[11:02] <shilbert> will go and check it out now
[11:02] <shilbert> thanks
[11:03] <noodles775> np... http://www.youtube.com/watch?v=zKLabbXTqMc
[11:03] <wgrant> noodles775: Is it intentional that one can have packages in multiple distros in a single archive? Does that make sense at all?
[11:04] <noodles775> shilbert: In your case it should be a bit easier as you won't need to create the debian files...
[11:04] <wgrant> (if I try to copy from a Debian archive into my PPA, I can only copy into Debian series, which is unfortunate and useless)
[11:05] <noodles775> wgrant: I'm not certain that the possibility has been considered...
[11:05] <noodles775> bigjools: will be back soon and can probably provide more helpful info...
[11:05] <wgrant> Well, it's certainly possible, and it would be useful to be able to copy from Debian to a PPA and have things built and published.
[11:06] <wgrant> Actually, I wonder if I can do that through the API...
[11:06] <noodles775> Yeah, good question...
[11:18] <noodles775> wgrant: AFAICS, the UI definitely does not support it (although it's currently noted as a bug)... so it should be fixed if PPAs for other distributions are supported...
[11:18] <shilbert> wgrant: just in case you find an elegant way it would be nice if you could somehow notify the gnumed team (time permitting)
[11:19] <wgrant> noodles775: The UI does not support what?
[11:19] <shankhs> Is geany in LP?
[11:20] <noodles775> wgrant: sorry, I meant to say, that allowing the selection of distroseries (other than that of the source archive) is something that should be fixed...
[11:21] <noodles775> in the UI
[11:22] <wgrant> noodles775: Do Archives have distros linked directly, or is it just the SPPHs?
[11:23] <shankhs> I was trying to install geanydebug plugin but it seems that the configure.in file in geany needs the source code I found the geany source code in /usr/include/geany and gave the path but at the end it always says FATAL ERROR : source code not found
[11:23] <noodles775> wgrant: Archives are linked directly to distros, yes.
[11:24] <shankhs> How should I change the configure.in file?
[11:25] <wgrant> noodles775: That's what I thought until this afternoon, but how on earth does it let me copy something into the wrong distro in an archive?
[11:25] <noodles775> wgrant: as I said, I don't think it's intentional...
[11:26] <noodles775> but I'm not certain...
[11:26] <wgrant> noodles775: I guess it's an easy fix since archives are linked to distros.
[11:26] <wgrant> Hmmm, except not.
[11:26] <noodles775> wgrant: if you've time, can you submit a bug for this?
[11:27] <wgrant> noodles775: Sure, I was planning to once I checked with one of you guys.
[11:27] <noodles775> :) - migth be worth checking with bigjools first, but AFAICS, it looks like a bug.
[11:30] <wgrant> The API looks up the distroseries name against the archive's distro, and I can do Debian Primary -> Ubuntu PPA copies fine that way.
[11:30] <wgrant> shilbert: ^^
[11:31] <noodles775> Great
[11:32] <wgrant> If archives are bound to distros, is there no namespacing reason for the 'ubuntu' in PPA URLs?
[11:34] <noodles775> wgrant:  f someone's copying it into their sources.list, it's handy for the url to be descriptive isn't it?
[11:34] <wgrant> noodles775: True. So it's just descriptive, not for namespacing? Interesting.
[11:36] <maxb> The URL is ppa.launchpad.net/USER/ubuntu - so perhaps it's there to reserve a level of namespacing for giving a user a second PPA for a different distro, should that ever happen?
[11:36] <wgrant> maxb: It's actually ppa.launchpad.net/USERNAME/ubuntu/PPANAME now.
[11:37] <maxb> well, yes, but only on edge so far
[11:37] <wgrant> IIRC the constraint is only (person, distro, name), so the web UI's URLs are wrong.
[11:37] <wgrant> And ppa.launchpad.net's are right.
[11:38] <wgrant> ('wrong' meaning special-cased to Ubuntu)
[11:41] <wgrant> Bug #320398
[11:41] <noodles775> wgrant: don't you mean: /USERNAME/PPANAME/ubuntu ? (on edge)
[11:41] <noodles775> Thanks wgrant
[11:42] <wgrant> noodles775: That I do. That doesn't make sense if archives are linked to distros.
[11:45] <noodles775> Well, it only doesn't make sense if you imply from that url that one archive might have content for multiple distros...
[11:45] <noodles775> wgrant: ^^^
[11:45] <noodles775> wgrant: but my *guess* would be that the intention people will use a different ppa for the different distro...
[11:46] <noodles775> wgrant: but... you've been around here longer than me, so you could be right!
[11:46] <wgrant> noodles775: Right, but it would make more sense, to group the PPAs by distro in the directory hierarchy, I think, and it's less confusing.
[11:46] <wgrant> Hah.
[11:46] <wgrant> Argh, I am going to die of commas.
[11:46]  * noodles775 laughs
[11:48] <noodles775> wgrant: possibly, but as you said, there may not be a need for the distro in the directory hierarchy, except so the url is descriptive...
[11:48]  * wgrant looks up the constraint for a definitive answer to that.
[11:49]  * noodles775 is out of his depth here... so take it with a grain of salt
[11:49] <wgrant> (distro, person_name, ppa_name)
[11:49] <wgrant> So the 'ubuntu' is necessary.
[11:49] <noodles775> wgrant: where are you looking for the constraint?
[11:50] <wgrant> noodles775: The spec and some bugs.
[11:51] <bigjools> it's placeholder as much as anything, the pain involved to add a named PPA to things was not good so when/if we start supporting more than Ubuntu PPAs it will be easier
[11:53] <wgrant> bigjools: I wondered as soon as I saw the +archive URL changing a couple of months ago why you didn't take this opportunity to fix it forever in one hit and add the distro in there too...
[11:53] <bigjools> URLs are easy to deal with, they can be redirected
[11:54] <wgrant> bigjools: True, true.
[11:54] <bigjools> as I've done for the ppa name :)
[11:55] <wgrant> Right.
[11:55] <wgrant> Has a policy for multiple PPA usage been decided upon yet?
[11:55] <bigjools> policy in what regard?
[11:55] <wgrant> What they are to be used for. Last I heard it was to be very restricted.
[11:56] <bigjools> where did you hear that, out of interest?
[11:57] <wgrant> In hear.
[11:57] <wgrant> Gah.
[11:57] <wgrant> *here*. I suck.
[11:57]  * wgrant is grepping.
[12:09] <wgrant> bigjools: Oh, I remember now, the spec says that only ~admins are meant to be able to create them.
[12:10] <bigjools> wgrant: ok.  I'm not sure that's completely decided yet but it will be firmed up before the full launch, of course
[14:38] <weboide> Hi, I need to reupload a orig.tar.gz to my PPA, but with the same version, how could I do?
[14:38] <wgrant> weboide: You cannot.
[14:38] <weboide> wgrant: argh :/
[14:38] <weboide> wgrant: I always have to superseed it?
[14:38] <wgrant> Both because it's not possible, and because it's not a good idea.
[14:38] <wgrant> Why do you need to modify it?
[14:39] <wgrant> The point of it is that it's *not* modified from the upstream release, so it should never change.
[14:39] <weboide> because the upstream changed it
[14:39] <wgrant> ....
[14:39] <wgrant> The upstream is wrong.
[14:39] <weboide> it needs to increase the version?
[14:39] <wgrant> Yes.
[14:40] <weboide> okay, I'll ask then.
[14:40] <weboide> Thanks wgrant :)
[14:40] <wgrant> It's very, very strange to alter a release after it's released..
[14:40] <wgrant> It defies the point of having a release.
[14:41] <weboide> wgrant: yeah but I'll contact them ;)
[14:41] <weboide> wgrant: thanks for your help
[14:42] <wgrant> np
[15:12] <mkanat> gmb: All of the Bugzilla API stuff is upstream now, and we freeze in six days, so make sure to let me know if anything doesn't work the way you want.
[15:17] <gmb> mkanat: Excellent, thanks. I'll take a look at the start of next week (it's freeze day for us today).
[15:17] <mkanat> gmb: Okay. :-)
[15:18] <mkanat> gmb: I think everything is doc'ed at http://www.bugzilla.org/docs/tip/en/html/api/Bugzilla/WebService/Bug.html
[15:18] <gmb> mkanat: Brilliant, thanks.
[15:18] <mkanat> gmb: They did change a lot from what's in the plugin, FWIW.
[15:19] <gmb> mkanat: Okay. That shouldn't be a problem; I'll just need to do plenty of testing and tweaking :)
[15:19] <mkanat> gmb: Okay. :-)
[15:21] <beuno> mkanat, hi!
[15:21] <mkanat> Hey beuno!
[15:21] <beuno> mkanat, there's a Loggerhead branch waiting for your comments
[15:21] <mkanat> I should test that branch for you, shouldn't I?
[15:22] <beuno> mkanat, just to know if that addresses what you need, or if I need to work on it further
[15:23] <beuno> if you give me the thumbs up
[15:23] <mkanat> beuno: Does it display a list of revisions that ends at a certain point?
[15:23] <beuno> I'll clean it up a bit and land it into trunk
[15:23] <beuno> mkanat, it does
[15:23] <mkanat> beuno: Okay. And it still paginates revisions normally, I'd imagine?
[15:23] <beuno> mkanat, it should, yes
[15:23] <beuno> I refactored some parts of the code to take revision ranges
[15:24] <mkanat> beuno: That's what I need then, yeah. :-)
[15:24] <beuno> mkanat, how's the migration going?
[15:24] <mkanat> beuno: Oh, it's a little controversial.
[15:25] <beuno> mkanat, well, let us know if we can do anything to smoothen it out
[15:26] <mkanat> beuno: The key point is that Mozilla mainly uses Hg.
[15:27] <mkanat> beuno: So we have to have a compelling reason to move to bzr instead of Hg.
[15:27] <mkanat> beuno: Other than "mkanat likes bzr more." :-)
[15:27] <beuno> mkanat, bzr rocks?
[15:27] <beuno> it's even a command!
[15:27] <mkanat> :-D
[15:28] <mkanat> Well, I definitely prefer it. I would have rather Mozilla moved to it, but I understand the scaling problems at their level.
[15:31] <beuno> mkanat, oh, the scaling problems we can work out, I'm sure, if Mozilla is interested in us helping
[15:31] <mkanat> beuno: We already had the whole discussion about a year ago.
[15:31] <beuno> mkanat, a lot has changed in a year  ;)
[15:31] <mkanat> beuno: Yeah, but they've already moved to Hg.
[15:32]  * beuno tickles kiko
[15:33] <beuno> mkanat, I know  :(
[15:33] <beuno> but just throwing it out there
[15:34] <mkanat> Sure, I'd love it.
[15:34] <mkanat> They only committed to hg for this development cycle, but they're building a lot of infrastructure around it now.
[15:35] <poolie> hello
[15:36] <mkanat> Howdy. :-)
[16:57] <heikki> i'm trying to upload a package to my ppa and get this error: "Unhandled exception processing upload: 'ascii' codec can't encode character u'\xe4' in position 77: ordinal not in range(128)", any ideas how to fix this? u'\xe4' is 'ä', there is ä in my name and I'v been able to upload packages with my name in changelog/control file before
[16:58] <heikki> (um, was that message too long?)
[17:01] <rockstar> heikki, where are you getting this error?
[17:02] <heikki> i run the dput command and get a mail which says that my package is rejected
[17:03] <heikki> whole message: http://paste.ubuntu.com/108647/
[17:04] <bigjools> heikki: known bug, can you change your name in LP to a non-unicode one temporarily during the upload
[17:05] <heikki> ok i'll try
[17:05] <bigjools> it'll be fix in 2.2.2
[17:06] <bigjools> fixed*
[17:16] <heikki> bigjools: it works, thanks!
[19:12] <LaserJock> beuno: it seems like there's gotta be a decent way to let people know that a vcs-import is just plain dead
[19:12] <beuno> LaserJock, sure, we just have to find it
[19:12] <LaserJock> I've had to completely give up on using Launchpad for non-bzr projects
[19:13] <LaserJock> which makes the whole "everything on LP" thing hard
[19:13] <poolie> LaserJock: because the imports are out of date and you can't find out?
[19:13] <LaserJock> yeah, vcs-imports are too unreliable
[19:13] <LaserJock> I'll be pulling along and then I think, "hmm, it's been a couple weeks since I got any updates"
[19:13] <LaserJock> I check the LP page and it's dead
[19:14] <LaserJock> it would've been nice to get something when I do a pull
[19:14] <LaserJock> not sure how possible that is
[19:14] <rockstar> LaserJock, there needs to be a good way to know about this.  It's a bug that there isn't a notfication sent out.
[19:15] <LaserJock> I wonder if there could be a redirect or something
[19:15] <rockstar> LaserJock, also, where are your vcs-imports coming from?
[19:15] <LaserJock> like bzr knows when a branch format needs to be upgraded, when there's a redirect
[19:16] <LaserJock> I wonder if it could somehow "know" that the branch has some "dead import" flag
[19:16] <LaserJock> rockstar: as in which VCS hosting?
[19:16] <rockstar> LaserJock, bzr knows it needs an upgrade.  Launchpad doesn't tell it that.
[19:16] <rockstar> LaserJock, yea.  We seem to have all sorts of issues with Google Code.
[19:16] <LaserJock> rockstar: right, what I'm saying is maybe there's something within the branch itself we can set
[19:17] <LaserJock> no, no Google Code
[19:17] <LaserJock> mostly SourceForge
[19:17] <LaserJock> and at least one on Savannah
[19:17] <rockstar> LaserJock, there is something we can set, but it's manual right now.
[19:19] <LaserJock> rockstar: perhaps that could be leveraged in some sort of automatic way, that'd be cool
[19:19] <rockstar> LaserJock, yeah.  We need to be able to do that.
[19:20] <rockstar> LaserJock, also, you should note that today is my day off, and I'm hacking on the import code.
[19:20] <LaserJock> I mean, I realize that vcs-imports are bound to break sometimes (though i don't understand why they're so bad currently) so a good notification system would be a big help
[19:21] <rockstar> LaserJock, well, they are so bad because we've had other plates that needed to keep spinning.
[19:21]  * LaserJock gives rockstar a cookie
[19:21] <LaserJock> rockstar: right, I mean so bad comparied to bzr-svn
[19:22]  * rockstar eats the cookie and asks for a glass of milk.
[19:22] <rockstar> LaserJock, I'm actually working on making bzr-svn the svn importer for VcsImports
[19:22] <LaserJock> I've *never* had a failure with bzr-svn, but like I said earlier, I can't seem to get above a 50% success rate with vcs-imports
[19:23] <LaserJock> rockstar: are you guys looking much at github for ideas?
[19:24] <rockstar> Yea, sometimes.
[19:24] <LaserJock> a project I work on recently went form SVN/Sourceforge to git/Github
[19:24] <LaserJock> there are some interesting "social networking" bits
[19:24] <LaserJock> a lot more personal than LP
[19:25] <rockstar> Yea, we've talked about that.
[19:25] <rockstar> However, github is also pretty much one thing.  Launchpad is trying to be a whole suite of tools.
[19:25] <LaserJock> right
[19:25] <rockstar> Er, we're not really trying.  We succeeding.  :)
[19:25] <LaserJock> heh
[19:25] <LaserJock> whatever you say
[19:26] <LaserJock> interestingly, that same project is using LP too
[19:26] <LaserJock> so they have wiki/download/bug tracking on SourceForge, VCS on github, and translations on Launchpad
[19:27] <rockstar> Geez, that's gotta be rough.  I believe in monogamy (and I should note that I'm a mormon :)
[19:27] <LaserJock> hehe
[19:27] <LaserJock> it is rough
[19:28] <LaserJock> especially since there's still an SVN repo on SourceForge
[19:28] <LaserJock> so technically there's VCS on both SF and Github
[19:31] <LaserJock> rockstar: I did try to pimp bzr/code hosting though :-)
[19:31] <LaserJock> but for a developer group of ~6-7 I was the only one that'd even used bzr so I go pretty outvoted :(
[19:32] <rockstar> It's too bad though.  People get stockholm syndrome with their tools.
[19:32] <LaserJock> the main dev is sorta like that
[19:32] <LaserJock> he said he invested a lot of time/effort into learning git, he wasn't going to switch
[19:33] <LaserJock> and he's a speed freak so I don't think he'd have liked bzr anyway
[19:33] <mkanat> That's like why people use Windows. :-|
[19:33] <mkanat> It took them so long to learn how to make it work, they feel invested.
[19:34] <thomasdelbeke> Hi again
[19:34] <thomasdelbeke> I am looking for advice on a hurestore bug
[19:34] <thomasdelbeke> It is ancient
[19:35] <thomasdelbeke> but I now have an strace and valgrind log that indicate memory leak
[19:35] <thomasdelbeke> gdb was semi succesful
[19:35] <thomasdelbeke> Do I mark mine as a duplicate and reattach
[19:36] <thomasdelbeke> or the other way around
[19:36] <thomasdelbeke> ???
[19:36] <Ape3000> How can I join the launchpad-users mailing list?
[19:36] <thomasdelbeke> If so, which reports and comments yo attach?
[19:37] <thomasdelbeke> anyone there?
[19:38] <LaserJock> thomasdelbeke: so there's 2 bugs, the later, more  complete one is yours?
[19:38] <thomasdelbeke> yes
[19:39] <thomasdelbeke> #320421
[19:39] <LaserJock> thomasdelbeke: I generally favor the one with the most complete report, but all things being equal go with the earliest
[19:39] <thomasdelbeke> that is mine
[19:39] <thomasdelbeke> OK, I will keep mine than maybe
[19:40] <thomasdelbeke> but the other one is already triaged
[19:40] <thomasdelbeke> marked importance high
[19:40] <thomasdelbeke> Is that a problem?
[19:40] <LaserJock> hmm
[19:40] <LaserJock> then maybe it would be better to make yours the dup and add your material to the other bug
[19:41] <LaserJock> so you don't waste any triaging :-)
[19:41] <thomasdelbeke> Bug #64594:
[19:42] <thomasdelbeke> This report is public
[19:42] <thomasdelbeke> that is the original one
[19:43] <thomasdelbeke> Is there an alternative BTW?
[19:43] <thomasdelbeke> Maybe I will post this on the forum
[19:43] <thomasdelbeke> If there is not alternative
[19:44] <thomasdelbeke> It should be marked critical
[19:44] <LaserJock> thomasdelbeke: there are a bunch of dupes for that bug
[19:44] <LaserJock> thomasdelbeke: just mark yours a dup
[19:44] <thomasdelbeke> People can loose data this way
[19:44] <thomasdelbeke> If you reformat your system and it is not working
[19:45] <thomasdelbeke> OK I will mark it as a dup
[19:45] <thomasdelbeke> and post it on the forum
[19:45] <thomasdelbeke> Thanks for the info
[19:45] <LaserJock> np
[20:30] <Adri2000> got OOPS-1119ED453 when renewing team membership
[20:56] <flacoste> hi Adri2000
[20:57] <flacoste> Adri2000 how did you renew your membership?
[20:57] <flacoste> sinzui, Adri2000 hit an assertion error when renewing his membership
[20:57] <flacoste> sinzui: OOPS-1119ED453
[20:57] <flacoste> Adri2000: it seems that you can't renew your membership yourself, the team admin should do it
[20:58] <savvas> nice error, hehe
[20:58] <savvas> "OOPS"
[21:11] <shilbert> Hi, how can I investigate why I do not receive any feedback from launchpad via email after dput upload to my PPA? Thanks.
[21:14] <flacoste> shilbert: do you receive email from Launchpad regularly
[21:29] <sinzui> Adri2000: How did you get to that page to renew your membership? The only documented way to do get to that page was by typing the URL into the browser.
[21:35] <bigjools> shilbert: you've either signed with the wrong key or not signed at all
[21:37] <maxb> Hi, is there anyone around who can poke yellow.buildd with a big stick? It's apparently been building qt4-x11 for three _days_
[21:38] <Adri2000> flacoste, sinzui: it was for the ~motu team, and despite the oops, the renewal itself did work. and I just followed the link given in the email I received, and hit the "renew" button
[21:38] <Adri2000> also, I use edge, being in the beta testers team
[21:39] <flacoste> herb, mthaddon, do any of you can help maxb?
[21:40] <sinzui> Adri2000: thanks. There is a discrepancy in the code the generates the form and the rules for renewal. I'll file a bug about it.
[21:41] <herb> maxb, flacoste: one moment
[21:41] <Adri2000> sinzui: ok
[21:42] <flacoste> bac, sinzui: can we grant a vouchour for gary's https://edge.launchpad.net/lpbuildbot ?
[21:42] <bac> flacoste: i did it about an hour ago
[21:43] <flacoste> bac: thanks
[22:01] <sinzui> mthaddon: can you confirm the ~motu team's member policy is ondemand?
[22:03] <mthaddon> sinzui: where would I find that - I see it's restricted team
[22:07] <sinzui> mthaddon: do you have access to the change details page? Which number radio button is selected for " When someone's membership is about to expire, notify them and: "
[22:07] <mthaddon> sinzui: "invite them to renew their own membership"
[22:07] <sinzui> 2 is ondemand, Thanks
[22:12] <elmo> maxb: fixed
[22:15] <maxb> excellent :-)
[23:09] <maxb> I don't suppose anyone's considered making an "upload multiple attachments to bug" feature?
[23:10] <beuno> maxb, we have, in several ways
[23:17] <Blackfate> anyone here?
[23:18] <beuno> Blackfate, 125 people, what's up?
[23:18] <Blackfate> i see laucnchpad imported keys
[23:18] <Blackfate> for the ubuntu repositories
[23:19] <Blackfate> i made a bash script which allows you to auto scan the pc for the launchpad sources and and auto download keys
[23:19] <Blackfate> you can check more here
[23:19] <Blackfate> http://ubuntuforums.org/showthread.php?p=6605259#post6605259
[23:20] <beuno> Blackfate, that's awesome
[23:20] <Blackfate> ^^
[23:20] <Blackfate> clean code! you can change it if you like
[23:58] <spitfire_> Hi. I have a strange problem. I've uplodaed package to my PPA, and it failed to build, but building it locally, using pbuilder worked.
[23:58] <spitfire_> Any clues?
[23:58] <spitfire_> http://launchpadlibrarian.net/21582680/buildlog_ubuntu-intrepid-amd64.gnome-do_0.7.98-0~intrepid~ppa2_FAILEDTOBUILD.txt.gz
[23:58] <spitfire_> And it's strange it failed to build only on amd64 arch.
[23:59] <spitfire_> Is there some kind of problem with mono, when building in buildd system?