[00:02] <kiko> thewrath, did you get your problems sorted?
[00:08] <thewrath> i believe so
[00:08] <thewrath> everything seems to be working
[00:08] <thewrath> you mean with pushing hte code, etc out to launchpad.net?
[00:09] <thewrath> kiko: is that correct? and also do you have a pgp or a gpg key?
[00:12] <kiko> gpg
[00:12] <kiko> gpg rocks
[00:12] <kiko> but the keys are the same
[00:13] <thewrath> right
[00:13] <thewrath> i ahve that all working but want to test it
[00:13] <thewrath> can you help me test it?
[00:15] <thewrath> how long does it take for an admin or someone else to change the name of a project
[00:34] <thewrath> kiko: ?
[01:54] <kiko> thewrath, sorry, I gotta dash, catch you tomorrow
[02:31] <Hobbsee> way cool.  it really does die.
[02:31] <Hobbsee> OOPS-1189EA13
[02:32] <Hobbsee> and OOPS-1189D145 for production.
[02:32] <Hobbsee> for https://launchpad.net/ubuntu/+source/konversation
[02:34] <Hobbsee> What's the intended workaround?
[02:43] <jamesh> Hobbsee: maybe try looking at a different page?
[02:55] <jamesh> Hobbsee: for what it is worth, that page appears to be spending a lot of its time looking up email addresses (probably to linkify changelogs)
[02:59] <wgrant> Hobbsee: There's no workaround to see that page, but you can sometimes check the version history at +publishinghistory
[03:06] <VK7HSE> I've made a small blunder! I'm currently uploading packages for Me Tv (both into my own PPA and the Me Tv PPA) where I have gone wrong is that as of the current version it was decided to include the bzr build number into the package name. So the initial upload was called me-tv (0.8.0-0ubuntu1~ppa1) but then we decided to rename to me-tv (0.8.0-0ubuntu1-beta-bzr386~ppa1) so now the problem is that the beta side of testing is 
[03:07] <Ursinha> Hobbsee, bug 353568
[03:07] <Ursinha> people are working on it
[03:10] <wgrant> VK7HSE: The correct version would have been 0.8.0+bzr386-0ubuntu1~ppa1 or similar
[03:11] <wgrant> The bzr revision is part of the tarball version, surely.
[03:11] <wgrant> But your message got cut off, so I don't quite know what you're asking.
[03:11] <VK7HSE> the bzr pull created me-tv-0.8.0.tar.gz ...
[03:12] <VK7HSE> hang on I'll paste it....
[03:12] <VK7HSE> http://paste.ubuntu.com/143226/
[03:13] <VK7HSE> I'm still relatively new to the build process! so I was sure to make a mistake! :-/
[03:14] <wgrant> VK7HSE: The correct thing to do was to use 0.8.0~beta or similar.
[03:14] <wgrant> As ~ is less than anything else.
[03:14] <VK7HSE> so to rectify, requsting a new release would then fix?
[03:14] <wgrant> For now you can use 0.8.0.0, or 0.8.0+something
[03:15] <wgrant> Or get them to do a new release.
[03:15] <wgrant> And research version sorting thoroughly in future.
[03:15] <VK7HSE> I'll give the suggestions a try thanks...
[04:50] <DBO2> so what do I have to do to get access to the launchpad api =)  I'd like to rework our plugin for GNOME Do
[04:51] <wgrant> DBO2: http://help.launchpad.net/API
[04:54] <DBO2> so I need to become a launchpad beta tester
[04:56] <wgrant> Yes.
[04:57] <DBO2> is it possible for me to do that or is that a closed group?
[05:01] <wgrant> DBO2: There are more than 2000 members - it's quite open.
[05:02] <wgrant> Just request to join.
[05:02] <wgrant> And somebody will generally approve you within a day or two.
[05:02] <DBO2> sweet
[05:43] <MTecknology> heh - I found a bug in launchpad design :)
[05:43] <MTecknology> I feel special
[05:47] <dlynch> wgrant: I was able to use the API in a simple way from a python script, and I didn't join the beta group
[05:57] <MTecknology> Does launchpad offer private branches for proprietary software?
[06:00] <MTecknology> everyone sleeping?
[06:01] <spm> MTecknology: I believe so. for $ aiui
[06:02] <MTecknology> spm: you mean it's something that they pay for?
[06:02] <spm> yes
[06:03] <spm> AIUI. I'm a sysadmin, not a sales/marketing person. :-)
[06:03] <noodles775-afk> MTecknology: https://answers.edge.launchpad.net/launchpad/+faq/208
[06:03] <wgrant> Launchpad developers seem to be very good at long-range typing.
[06:03] <spm> noodles775-afk: ta. I keep forgetting about the faq... :-)
[06:04] <noodles775-afk> wgrant: just getting away from the keyboard now :)
[06:04] <noodles775-afk> spm: np!
[06:05] <spm> wgrant: the rumours about the canonical-sponsored-proprietary-keyboard-control-via-thought software; are just that. mere rumours. no truth to it at all. honest. cross my heart etc.
[06:07] <wgrant> sinzui: Hmm, if all map checkboxes are driven by the same piece of code, why are the in different places on person and team pages?
[06:07] <wgrant> spm: Damn.
[06:17] <jamesh> wgrant: because person and team pages use different templates?
[06:54] <Hobbsee> jamesh: they all seem to be like that
[06:54] <Hobbsee> wgrant: ah, right
[06:55] <Hobbsee> Ursinha: thanks, hope to see it fixed soon
[07:03] <wgrant> jamesh: They're not in the templates.
[07:03] <wgrant> jamesh: they're generated by JavaScript.
[07:40] <MTecknology> Does staging.launchpad.net actually host bazaar branches? ie - can code be uploaded there?
[07:41] <wgrant> MTecknology: Yes.
[07:48] <MTecknology> Hobbsee: hi
[07:48] <MTecknology> Hobbsee: it seems to be months between times when I see you around
[07:48] <Hobbsee> MTecknology: greetings.  And I don't frequent here so much anymore, which is probably why
[07:53] <MTecknology> Hobbsee: only other channels I sit in that you're also in right now are -bugs and -meetings
[07:54] <MTecknology> s/ngs/ns/
[07:54] <Hobbsee> sounds about right
[07:56] <jamesh> MTecknology: don't expect uploads to bazaar.staging.launchpad.net to stick though.
[08:01] <MTecknology> jamesh: I was curious because of this - https://answers.edge.launchpad.net/launchpad/+question/65927
[08:04] <wgrant> Huh./
[08:04] <wgrant> Indeed, the branches don't seem to be there any more.
[08:04] <wgrant> But I'm fairly sure I was able to use even private codebrowse on there a month ago.
[08:04] <wgrant> But maybe that was only for a new branch.
[08:09] <speakman> Hi LP folks! Can I create a "superproject" myself, or is it something launchpad admins has to create for you?
[08:09] <RAOF> That needs an LP admin, IIRC.
[08:12] <wgrant> speakman: Ask at https://answers.launchpad.net/launchpad/+addquestion
[08:12] <noodles775> Yeah, best to put a request like one of the others here speakman :
[08:12] <noodles775> https://answers.edge.launchpad.net/launchpad-project/+questions?field.sort=by+relevancy&field.language-empty-marker=1&field.actions.search=Search&field.status=Open&field.status=Needs+information&field.status=Answered&field.status=Solved&field.search_text=super+project
[08:13] <noodles775> wgrant: too quick!
[08:13] <wgrant> noodles775: Only by a fraction of a second :(
[08:14]  * wgrant laments the lack of a 'Nearby' part of the breadcrumbs.
[08:14] <wgrant> There used to be menus that almost fulfilled that purpose, but they got culled for 2.0.
[08:15] <noodles775> wgrant: what do you mean by a 'Nearby' part? What's an eg on another site?
[08:16] <wgrant> noodles775: I don't know of any examples
[08:16] <wgrant> But I should be able to click on an arrow next to my PPA in the breadcrumbs, and it will drop down a list of my other PPAs.
[08:16] <noodles775> Ah... neat idea...
[08:16] <wgrant> For a source package in a distroseries it should drop down links to that source package in its other distroseries.
[08:17] <noodles775> Sounds like it'd be worth chatting with beuno when he's around!
[08:17] <wgrant> That's what I thought.
[08:17] <wgrant> Because at the moment you have to hack URLs or perform an awful lot of clicks.
[08:19] <noodles775> Yeah
[08:20] <wgrant> Do you remember the old breadcrumb menus? They might have gone before you appeared on the scene.
[08:20] <speakman> wgrant: noodles775: thanks! (just curios: why do you link primarly to edge..?)
[08:21] <mdke> edge comes up automatically in urls for those using it
[08:21] <noodles775> speakman: it happens by default if you sign up as a beta tester...
[08:21] <mdke> it's difficult to remember every time to remove it from urls
[08:21] <wgrant> Maybe we need an irssi plugin to strip 'edge.'
[08:22] <mdke> so, on the subject of project groups, is it possible to set single milestones and series for projects in a particular group, or do they need to be kept up to date individually?
[08:22]  * mdke goes back and erases the "so," part of the question for popey's benefit
[08:23] <wgrant> I don't think you can do it globally.
[08:23] <wgrant> Since it doesn't make sense, in most cases.
[08:23] <wgrant> In Launchpad's case it does, but that's because Launchpad's usage of Launchpad is somewhat wrong.
[08:24] <popey> haha mdke
[08:24] <popey> tis okay, it's not a blog post :)
[08:24] <mdke> wgrant: that's what I figured
[08:24] <mdke> popey: ;p
[08:25] <jamesh> MTecknology: the branches uploaded to staging are not available, but if you push a new branch to bazaar.staging.launchpad.net, it will be listed on code.staging.launchpad.net
[08:25] <popey> i used to think I had no irrational OCD behaviours, now I realise I have quite a few
[08:25] <jamesh> MTecknology: at least until the database gets wiped the next day
[08:25] <wgrant> jamesh: Is this a new thing?
[08:25] <mdke> wgrant: I suppose that really there should be a further subdivision, so that there are project groups, projects, and then components of projects
[08:26] <wgrant> mdke: I think that last case can be fulfilled by supercharged tags.
[08:26] <jamesh> wgrant: not particularly new.
[08:26] <mdke> wgrant: for bug reporting only, surely?
[08:26] <speakman> noodles775: i meant your link in here :)
[08:26] <mdke> wgrant: how can tags be used for translations or code?
[08:26] <speakman> wgrant: noodles775: btw, here's my question: https://answers.edge.launchpad.net/launchpad/+question/66316
[08:27] <wgrant> mdke: I'm not quite sure how translations or code need to be kept separate.
[08:27] <wgrant> jamesh: I recall using private codebrowse, and I would only have done that on staging (as it was during a session of poking holes in lp-bzr, which I would only have done on staging)
[08:28] <noodles775> speakman: yeah, I know... as the others mentioned, it had 'edge' in it because I copy-n-pasted it from my browser (as a beta tester, my lp account defaults to edge). I'll try to remember to remove it before pasting links :)
[08:28] <mdke> wgrant: it can be convenient to have a separate lp shortcut, so "bzr branch lp:malone" and "bzr branch lp:rosetta", as for translations, you might have components which use similar templates with different content
[08:29] <wgrant> mdke: In Launchpad's case it's actually all in one branch.
[08:29] <wgrant> Although that will change soon.
[08:29] <mdke> wgrant: I'm speaking hypothetically
[08:29] <wgrant> (although not to the extent of the current proliferation of projects)
[08:29] <wgrant> Right.
[08:29] <mdke> I used the example of Launchpad because you said that its use of group projects is wrong
[08:29] <mdke> and I can see what you meant by that
[08:29] <wgrant> I can see rationale for splitting a project's bugs, but splittiing the code would seem to split it into multiple codebases, which means multiple projects make sense.
[08:29] <speakman> noodles775: oh, I see! :D
[08:30] <mdke> wgrant: ok, that's clearer
[08:30] <jamesh> wgrant: Launchpad code isn't split between the historic malone, rosetta, etc projects.
[08:30] <mdke> wgrant: in that case, a feature to set single series and milestones across projects would make sense for some projects
[08:30] <jamesh> you'll see things split up a bit more closer to the release though
[08:30] <wgrant> jamesh: 'In Launchpad's case it's actually all in one branch.'
[08:31] <wgrant> I did just say exactly that, I think.
[08:31] <jamesh> [some infrastructure bits have already been separated and released]
[08:31] <noodles775> speakman: I've assigned your question to kiko :)
[08:33] <wgrant> jamesh: It won't be split up apart from the infrastructure and non-free bits, will it?
[08:33] <jamesh> wgrant: there are plans to make the codebase more modular.  I don't know how much will be in separate branches though.
[08:34] <jamesh> a lot of the infrastructure will be in separate branches though.
[08:34] <speakman> noodles775: thanks, but why did it move from "Launchpad-itself" to one of our projects? :D
[08:34] <wgrant> As we already have in /lazr, right.
[08:39] <noodles775> speakman: Sorry, my mistake :D Set back to launchpad.
[08:39] <speakman> noodles775: The email just arrived :D
[08:40]  * wgrant feared that the Blueprint bug had hit Answers too.
[08:40] <speakman> noodles775: There was one swedish talking person @ launchpad according to the question form. Is that "kiko"?
[08:41] <noodles775> speakman: kiko loves languages, but I don't think he's started swedish yet. Not sure who it might be.
[08:43] <speakman> noodles775: i see :)
[08:44] <speakman> Another Launchpad question; When doing Merge Proposals, how do I know which one actually does the merge? The "Status:" might changes from "Needs review" to "Approved", but it's not clear wheter the person changing the status also should be the one who do the merging.
[08:50] <noodles775> speakman: I guess that depends on the project... and who has permission to merge into the parent branch.
[08:51] <speakman> noodles775: oh, okay. It's up the team to have policys like if the approver also makes the merge? There's no way for Launchpad to tell if the merge has been completed?
[08:51] <RAOF> speakman: Some people run a daemon that automatically merges approved branches into trunk, too.
[08:52] <wgrant> Launchpad will notice when the branch is merged, but someone (or a robot, as RAOF suggested) needs to do the actual merging once it's approved.
[08:54] <speakman> wgrant: is the merge proposal closed when merge is committed?
[08:54] <wgrant> speakman: Yes.
[08:55] <speakman> oh,
[08:55] <speakman> oh great. then two people doing the same merge is not so likly :)
[08:56] <wgrant> I'd be a bit suspicious if I did a merge and there were no revisions to merge, I think.
[08:56] <wgrant> So it's not likely in any case.
[11:24] <tormod> is lp b0rked? some pages only return OOPS, like https://edge.launchpad.net/ubuntu/+source/xorg-server/
[11:25] <wgrant> tormod: Bug #353568
[11:25] <tormod> thanks
[11:51] <pvandewyngaerde> how can i prevent my membership in a team to expire ?
[14:03] <jpds> Anyone know how I can remove a bug watch?
[14:05] <MrKanister> jpds: just assign the project to "nobody"
[14:06] <wgrant> jpds: You can't remove a watch, but you can unlink it from the task easily.
[14:07] <jpds> wgrant: That's a shame, I just set it as "None" and marked as invalid.
[14:08] <wgrant> jpds: You wanted to remove the whole task, not just the watch?
[14:08] <wgrant> Ah, you can actually delete the watch if it's not linked to a task.
[14:08] <jpds> wgrant: That too would be preferable (it's bug #335715).
[14:09]  * wgrant resolves to port ubottu to launchpadlib tomorrow
[14:09] <wgrant> jpds: Oh, you can't actually delete tasks.
[14:09] <wgrant> (yet, hopefully)
[14:09] <vorian> thanks for the million karma points guys <3
[14:09] <wgrant> You might as well delete the bug watch (hit the edit icon in the portlet)
[14:10] <wgrant> vorian: Wow. Literally.
[14:10]  * wgrant remembers the days when 10 million was commonplace.
[14:10]  * vorian chuckles at "it's fixed"
[14:10] <wgrant> But... that's a bit extreme now.
[14:11] <wgrant> vorian: I don't think they ever fixed the karma bug.
[14:11] <vorian> it's not karma, it's rosetta
[14:11] <wgrant> I mean the karma-giving bit of rosetta.
[14:11] <vorian> i used a filter this time to auto-delete all the rosetta spam
[14:11] <wgrant> It's not spamming you 20000 times any more, is it?
[14:12] <vorian> only about a 10th this time around
[14:12] <wgrant> danilos: ^^
[14:12] <vorian> I'm still got a ton of successful import emails
[14:12] <vorian> and they are still hitting my trashbin
[14:14] <wgrant> beuno: Did you see my UI suggestion here about 6 hours ago?
[14:21] <beuno> wgrant, I didn't
[14:22] <beuno> wgrant, care to copy'n'paste it?
[14:23] <wgrant> beuno: Basically, I'd like the breadcrumbs to have 'nearby' links, as a sort of restricted version of the dropdowns that were removed for 2.0.
[14:24] <wgrant> I could navigate between a user's PPAs by clicking on an arrow next to one of their PPA breadcrumbs. Down would drop links to their other PPAs.
[14:24] <wgrant> On a distribution series source package breadcrumb, I would get links to the source package in other distro series.
[14:24] <wgrant> At the moment there's no way to do that sort of thing without going most of the way back up the hierarchy, then all the way down again.
[14:24] <beuno> wgrant, oh, I have plans for something like that  :)
[14:25] <wgrant> beuno: Ah, good.
[14:25] <beuno> something among the lines of having arrows on all breadcrumbs
[14:25] <wgrant> Right.
[14:25] <beuno> and being able to jump between that object
[14:25] <wgrant> Like we had until a year ago.
[14:25] <beuno> yes, but better
[14:25] <beuno> a smart "top 5 list" and a search box that will jump directly if there's an exact match
[14:26] <wgrant> IIRC that was more focused on things related to the breadcrumb in question (eg. milestones for a product), rather than alternatives.
[14:26] <wgrant> Hmmm. interesting.
[14:27] <beuno> I'll poke you when I manage to see this through a little bit more
[14:27] <wgrant> Thanks.
[15:36] <mvo> hm, https://launchpad.net/ubuntu/+source/python-central gives me a timeout :/ (both edge and normal) - OOPS-1189A1407
[15:38] <gary_poster_> mvo: looking
[15:39] <gary_poster_> mvo: yeah, duped...looking further
[15:39] <mvo> thanks
[15:47] <gary_poster_> mvo: the fix for this is currently running through our build system.  That means it will be on edge tonight and possibly cherrypicked for production even sooner.  I'll ping you if I hear more.
[15:47] <matsubara> mvo, it's bug https://bugs.edge.launchpad.net/bugs/353568 and cprov fixed. we're waiting on tests to finish and that will be included in today's batch of fixes to lp.net
[15:47] <mvo> great, thanks for the quick response matsubara and gary_poster_
[16:13] <seiflotfy> hi guys
[16:13] <seiflotfy> we want to remove a team form launchpad
[16:13] <seiflotfy> hwo do we do it
[16:15] <beuno> seiflotfy, you have to request it via Launchpad answers:  https://answers.launchpad.net/launchpad
[16:43] <danilos> vorian: hey, I've been pointed at how much trouble you are having with Launchpad Translations; please email me or update bugs (eg. 337313 and 353648) appropriately so we can evaluate impact of them and prioritize based on that
[17:34] <nhandler> Is it still possible to copy a package from a private ppa to a public ppa?
[17:37] <gary_poster> nhandler: not sure, will check for you
[17:37] <nhandler> gary_poster: Thanks a lot. I know it used to be possible, but now Launchpad keeps throwing an error
[17:45] <cprov> nhandler: hi, copy from private to public PPAs is not possible
[17:46] <cprov> nhandler: I think before 2.2.2 we didn't raise an error on the UI but the files could never be published in the repository.
[17:46] <nhandler> I am almost positive that it successfully copied the files for us. Or at least people were able to install using the public ppa after the copy
[17:47] <cprov> nhandler: P3A files are stored in a separated (private) librarian instance.
[17:48] <cprov> nhandler: the only way it could work was if the file was already public, i.e uploaded to a public PPA, then copied to a P3A then copied back to a public location.
[18:27] <maxb> ooi, what criteria does Launchpad apply to discriminate "Incomplete (without response)" and "Incomplete (with reponse)"
[18:27] <maxb> ?
[18:29] <beuno> maxb, I guess when there's a comment?
[18:29] <maxb> Any comment since the status was last changed?
[18:30] <maxb> I suppose I could answer this myself by messing around on staging
[18:30] <beuno> BjornT, intellectronica, gmb, ^
[18:30] <maxb> Or I could wait until 3.0 :-)
[18:31] <intellectronica> maxb: incomplete (with response) means there was a new comment on that bug since it was last put in the incomplete state
[18:32] <intellectronica> so the workflow is: you say "this bug is incomplete, please provide more info", then you wait for a comment...
[18:33] <maxb> thanks
[19:39] <thou> hi!  if i add a PGP key to my user, is it possible to remove it later?
[19:40] <kiko> thou, you can, yes -- but why would you want to?
[19:40] <kiko> or thou canst, more appropriately :)
[19:40] <thou> :-)
[19:40] <thou> kiko, my team has a code-signing pgp key; it's not my personal one
[19:41] <kiko> thou, hmmm. and why do you wanna associate that with your account?
[19:41] <thou> i am exploring the best way to manage uploading source packages to a PPA, signed by the team's key
[19:41] <thou> i don't want to sign the packages with my personal key
[19:42] <thou> i'm not sure if i should add a new launchpad user for the team, and associate the key with that user
[19:43] <kiko> cprov, can you advise thou on the best course of action
[19:43] <thou> i thought, if the team's key is associated with any user that is a member of the project, then it would work
[19:44] <cprov> thou: let me catch up quickly
[19:44] <thou> sure
[19:46] <thou> fyi, we build our software on a lot of platforms; trying to use launchpad for handling ubuntu packages, but we use a common user on our build farm to build everything, and we have a single host that has the private key for signing all of our packages
[19:46] <cprov> thou: okay, if the key signing a source belong to a member of the team owning the PPA the upload will be accepted.
[19:46] <cprov> thou: I just don't understand why you don't want the person responsible for a source change to sign it.
[19:47] <kiko> thou, gpg keys are pretty personal things :)
[19:47] <thou> sure
[19:47] <thou> that's why i *don't* want my key used for this
[19:47] <thou> there might be 5 different people working on building a release
[19:47] <thou> and 100 people who made code changes
[19:47] <kiko> thou, right, but any of those people can sign the source and it will be accepted
[19:48] <kiko> that's cprov's point -- not using a shared gpg key makes a lot more sense
[19:48] <thou> but we use a shared account
[19:48] <kiko> a shared account.. where?
[19:48] <thou> and we have a single code-signing key that is well known (build@mysql.com)
[19:49] <thou> not a launchpad account, but ... hrm, i'm not explaining well
[19:49] <kiko> thou, I think I'd create a separate LP account for that address, then.
[19:49] <kiko> thou, we do that for our PQM account for instance
[19:49] <kiko> (not for the same reason, I'm just giving the rationale for having an account for a robot)
[19:49] <thou> ok, and subscribe that account as a member of the project team
[19:49] <kiko> precisely
[19:50] <thou> that "feels" better to me
[19:50] <kiko> for launchpad the pqm bot can write to our branches
[19:50] <thou> i was concerned if launchpad users are meant to be real people
[19:50] <kiko> and in fact it is the only thing that actually does (USUALLY, though sometimes we break the rules)
[19:50] <thou> ok, great
[19:50] <kiko> they mostly are, but this is an acceptable violation of that guideline
[19:51] <kiko> usually people ask that bots be created as teams
[19:51] <kiko> which often works, but for this case, obviously doesn't
[19:51] <thou> and it's not a bot, really
[19:52] <thou> although we will script it, of course, someone will have to push the button to say "yes, it's OK, publish this"
[19:53] <thou> kiko, cprov: thanks a lot for your advice
[19:54] <kiko> thou, a pleasure talking to you by the way, haven't seen you asking around here before
[19:54] <thou> no, i'm trying to take over from mordred
[19:54] <kiko> thou, yeah.. pqm is similar in that it is email controlled
[19:54] <kiko> thou, the main difference is probably that while I don't know your script I absolutely HATE pqm
[19:55] <kiko> oh-oh said it out loud again
[19:55]  * kiko gets in trouble
[19:55] <thou> i don't know my script either.  not sure it exists yet.
[19:56] <kiko> thou, there's this autoppa thing that jamu wrote. have you seen it?
[19:56] <thou> yeah
[19:56] <thou> too limited for me
[19:56] <kiko> not extensible enough, or just the wrong design?
[19:56] <thou> the template thing only handles different ubuntu releases (hardy/intrepid/etc.)
[19:56] <cprov> thou: I'm glad to help, let me know if you guys need help with multiple-ppas (just released in 2.2.3).
[19:57] <thou> i need to be able to create some packages that, e.g., don't include innodb at all
[19:57] <kiko> mmm
[19:57] <thou> so my files listing will or won't include some sets
[19:57] <jkakar> thou: You mean not including innodb in a Depends: line?
[19:57] <thou> i'm planning to use m4 to generate the real debian/*
[19:58] <jkakar> That sounds weird. :)
[19:58] <jkakar> It sounds like you want different packages that pull in different things.  Like a myproject-common for the common stuff and a myproject-innodb for the InnoDB extensions.
[19:58] <kiko> jkakar, hey, some people use m4 to generate .procmailrc files
[19:59] <thou> hmm
[19:59] <jkakar> kiko: Sure, m4 is great.  From knowing nothing about thou's problem I get the sense he may be generating different Debian packaging files and using them to build packages with the same name, which is a bad idea.
[19:59] <kiko> with the same name?!
[20:00] <thou> we'll have mysql-enterprise-classic-gpl, mysql-enterprise-pro-commercial, etc.
[20:00] <jkakar> thou: You can specify more than one package in your control file.  AutoPPA can build more than one .deb at a time for the same release.
[20:00] <thou> where classic, pro, advanced, etc. include different sets of features
[20:00] <jkakar> Those sound like different packages with different inputs.  Perhaps all relying on some shared core package.
[20:01] <thou> jakwell, that's like building client, server, libs, test packages
[20:01] <thou> like sub-packages, right?
[20:02] <thou> so we have libmysqlclientVER-dev.deb, mysql-client-VER.deb, mysql-common-VER.deb, mysql-server-VER.deb
[20:02] <thou> those are all defined in the control file
[20:03] <jkakar> Cool, then you can build them all at once with AutoPPA.
[20:03] <thou> but i need the option of building all of those in the 'pro' or 'classic' configuration
[20:03] <thou> and 'pro' and 'classic', etc., are almost identical
[20:04] <thou> but have different features sets defined, which means different ./configure --foo, resulting in different files and directories lists
[20:04] <thou> and of course build those for dapper, hardy, intrepid, ...
[20:04] <jkakar> Right.  All possible permutations of terribleness. ;)
[20:05] <thou> afaiks autoppa handles the hardy/intrepid mess
[20:05] <jkakar> thou: Your idea to generate the debian directory doesn't sound so bad now.
[20:05] <thou> but doesn't handle the pro/classic mess
[20:05] <jkakar> thou: Yep.
[20:07] <cprov> thou: the classic/pro mess could be handled in the debian/rules, as "a single source generating multiple debs", but it may get *too* complex for managing
[20:07] <jkakar> In which case AutoPPA templating system will work for you (though, yeah, it could get pretty hairy).
[20:07] <thou> cprov: yes, i can see that for rules (it could be any executable, after all) but how to handle the .files and so forth, which are text files?
[20:08] <thou> i can use wildcards, perhaps
[20:08] <thou> but that is kind of sketchy it seems
[20:09] <jkakar> I wonder how common this problem is.  I think it wouldn't be too hard to extend AutoPPA to handle "custom keys" that one could use to make the templating magic work more magically.
[20:09] <jkakar> But it feels a bit special-cased... which makes me wonder about supporting plugins for this kind of thing.
[20:09] <jkakar> Though, implementing a plugin is probably too much work for most people.
[20:10] <adrian15555> Hi. I had a problem on uploading a package named: fai to PPA. Unknown distribution: fai. More details here: http://www.gulic.org/pastebin/27    Can you please help me? Thank you.
[20:11] <cprov> adrian15555: it's a broken debian/changelog entry, use one of the ubuntu series (intrepid, jaunty, ...)
[20:12] <thou> ... e.g., the .files for our mysql-server* package may include some things in usr/bin (mysqld_safe, mysqladmin for example), and our client .deb includes other things (mysql, etc.).  I don't see how to handle that with wildcards, but also be able to leave out usr/bin/innochecksum if innodb isn't included
[20:14] <thou> jkakar: from a 30-minute glance at AutoPPA, my opinion (and remember I'm very new to this area) is that it's great for the normal (99%) case where you need to manage different debian versions automatically. I think that is what I would focus on.  It's really quite simple regarding what it does, and i see that as a positive thing.
[20:15] <thou> even for mysql, community packages only have a single flavor
[20:16] <thou> it's just our crazy sales/marketing (and some weird licensing issues) that make us have these different flavors that i'm worried about, and i think it's a very special case
[20:16] <jkakar> thou: Cool.  AutoPPA needs some love (to fix a variety of small issues), but it does work fairly well for that typical case, yeah.
[20:16] <jkakar> thou: Yeah.
[20:16] <jkakar> thou: it sounds like you could still use m4 (or whatever) to generate the packaging files and get benefit from AutoPPA for the build-for-every-release use case.
[20:17] <adrian15555> cprov, Do you mean that "fai (3.2.4+svn4837-0ubuntu2~ppa1) intrepid; urgency=low" is wrong?
[20:18] <thou> jkakar: yep, what i have to determine is ... do i want one more tool in my toolchain? does it buy me anything, when i'm already generating everything?
[20:18] <cprov> adrian15555: no, this one looks correct.
[20:18] <adrian15555> cprov, So what did you mean then?
[20:18] <thou> jkakar: at the very least, i'll steal some code from you :-)
[20:19] <jkakar> thou: Please do. :)
[20:19] <jkakar> thou: Also, patches welcome. :)
[20:19] <adrian15555> cprov, I can give you more details if you want to.
[20:20] <cprov> adrian15555: the upload path is the problem,  '~adrian15/ppa/fai/'
[20:20] <thou> jkakar: i certainly will, if i manage to get that far
[20:21] <cprov> adrian15555: if you are aiming you ppa named 'fai' it should be '~adrian/fai/' only
[20:21] <adrian15555> cprov, "Change the incoming entry to the path to the PPA you're working with" That's what I read at: https://help.launchpad.net/Packaging/PPA How am I supposed to
[20:21] <adrian15555> cprov, ok.
[20:21] <adrian15555> cprov, This howto needs improvement then
[20:21] <adrian15555> cprov, I am going to try your suggestion. Thank you very much.
[20:36] <adrian15555> Whenever you upload a package to your PPA. If it gets accepted. How long are you supposed to wait until the Accept message? Thank you.
[20:40] <mwhudson> adrian15555: i think it's the next */20 in cron-speak
[20:40] <mwhudson> (though that might be something else)
[20:41] <cprov> adrian15555: the process runs */5, so if you are unlucky up to 10 min ;)
[20:44] <maxb> */20 is the publisher?
[20:45] <adrian15555> cprov, ok. I am going to upload two more packages and tomorrow I will check it
[20:46] <cprov> maxb: exactly
[20:49] <adrian15555> Thank you much everyone. Bye.
[20:50] <cprov> maxb: btw, I've just run queue-builder to create builds for the binary P-a-s lines, it's done.
[20:50] <cprov> maxb: let me know if there are other missing builds.
[20:52] <maxb> Looks good, I see the hppa builders just finishing up those builds :-)
[21:00] <cprov> maxb: very nice, -1 problem.
[21:16] <Tiefflieger> hi, anyone else having problems connecting to https://edge.launchpad.net/ubuntu/+source/gnome-games ?
[21:16] <beuno> Tiefflieger, yes, we're working on fixing it
[21:16] <beuno> well, cprov is  :)
[21:17] <Tiefflieger> ok, thanks :-)
[21:17] <cprov> Tiefflieger: the fix will be released very soon.
[21:18] <Tiefflieger> i just wanted to ask because it's been hours since it first occurs... and like the header of 'edge' says: 'please report all bugs' ;-)
[21:19] <beuno> Tiefflieger, sure, thanks for letting us know
[21:23] <Agafonov> Hi, I wish to know the status of launchpad bug I've submitted - https://bugs.launchpad.net/launchpad/+bug/353950 - anyone cares?
[21:24] <beuno> Agafonov, of course we care!
[21:25] <beuno> Agafonov, we've just been busy rolling out a new version of Launchpad these past days
[21:25] <beuno> I've re-assigned it to the correct sub-project, and the right people will look at it early next week
[21:26] <Agafonov> I've noted some changes :)
[21:26] <Agafonov> beuno: how can I learn which sub-project?
[21:27] <beuno> Agafonov, well, anything to do with people/teams/projects is the "registry" sub-project
[21:27] <beuno> but it's hard to guess
[21:27] <beuno> which is why we ask people to file it against launchpad, and we re-jiggle them later on
[21:29] <Ursinha> beuno, catch me in midair, just opened that bug for triage :)
[21:29] <Ursinha> *caught
[21:31] <Agafonov> beuno: oh, already re-assigned, thanks.
[21:34] <beuno> Ursinha, :)
[21:38] <mdke> any rosetta developers around?
[21:39] <beuno> mdke, unlikely, but maybe danilos is
[21:39]  * mdke tickles danilos 
[22:20] <BUGabundo> trying to make my 1st patch
[22:20] <BUGabundo> need help branching in LP https://code.edge.launchpad.net/~network-manager/mobile-broadband-provider-info/mobile-broadband-provider-info.ubuntu
[22:20] <BUGabundo> what do I need to do?
[22:20] <Snova> You're trying to create a branch?
[22:20] <BUGabundo> yes
[22:21] <beuno> BUGabundo, aren't the instructions right on the page?
[22:21] <BUGabundo> to fix a string and then request a merge
[22:21] <beuno> bzr branch lp:~network-manager/mobile-broadband-provider-info/mobile-broadband-provider-info.ubuntu
[22:21] <BUGabundo> from ubuntu archive version
[22:21] <Snova> bzr branch lp:~network-manager/...
[22:21] <BUGabundo> done that!
[22:21] <BUGabundo> but that just takes if offline, correct?
[22:21] <beuno> BUGabundo, that gets you the code
[22:21] <BUGabundo> not to my LP branch!
[22:21] <Snova> Modify it, the push it to your own branch: bzr push lp:~<username>/network-manager/<branch name>
[22:21] <BUGabundo> ahh ok
[22:21] <beuno> BUGabundo, then you want to push the cahnges
[22:22] <beuno> changes
[22:22] <BUGabundo> so I need to push *everything*
[22:22] <beuno> have you committed them?
[22:22] <BUGabundo> I thought I could just push the changes
[22:22] <BUGabundo> if LP branched everything internally
[22:22] <Snova> No, you have to commit them first: bzr commit -m "Description of change"
[22:22] <Snova> Then push to the new branch. How you request a merge, I don't know.
[22:23] <BUGabundo> local commit done
[22:23] <Snova> I know how to use Bzr reasonably well, but I don't get a lot of opportunities to learn other features...
[22:23] <BUGabundo> now to push it
[22:24] <Snova> Ok, then I believe the next step is to push it, and then request the merge (not sure where that is).
[22:24] <BUGabundo> what is the correct command?
[22:24] <Snova> bzr push lp:~<username>/network-manager/<branch name> # I think
[22:25] <BUGabundo> No handlers could be found for logger "bzr"
[22:25] <beuno> BUGabundo, ignore that for now
[22:26] <BUGabundo> ok
[22:26] <BUGabundo> [ 3589] 2009-04-03 22:25:48.100 INFO: Created new branch.
[22:26] <BUGabundo> Created new branch.
[22:26] <Snova> What does it mean? I've never seen it.
[22:26] <BUGabundo> I don't know
[22:26] <BUGabundo> https://code.edge.launchpad.net/~bugabundo/network-manager/bug353957
[22:26] <BUGabundo> but its there
[22:27] <BUGabundo> merge request done
[22:27] <BUGabundo> WOOT
[22:30] <BUGabundo> is this any good https://code.edge.launchpad.net/~bugabundo/network-manager/bug353957/+merge/5210 ?
[22:53] <mterry> I can't find the 'register a release' link anymore off the series page...  Am I being stupid?
[22:53] <beuno> mterry, no, I'm sorry about that
[22:53] <beuno> we changed something
[22:53] <beuno> we will fix it soon
[22:53] <beuno> in the meantime, register a milestone
[22:54] <mterry> beuno: Ah.  So right now I can't?
[22:54] <mterry> beuno: OK.  Will that have a side-effect of registering a release?
[22:54] <beuno> mterry, yes  :)
[22:54] <mterry> beuno: Sweet.  Thanks
[22:55] <beuno> welcome'
[22:55] <mterry> beuno: I see, I then 'Publish a release' from the milestone page?
[22:56] <beuno> mterry, yes
[23:18] <joshjtl> hi folks
[23:19] <joshjtl> trying to report a bug... need to know what info to attach to it
[23:20] <BUGabundo> joshjtl: this is not the place to ask
[23:20] <BUGabundo> eheh
[23:20] <BUGabundo> #ubuntu-bugs tends to be better
[23:20] <joshjtl> ok thx
[23:35] <MTecknology> joey: HEY!
[23:36] <BUGabundo> hey MTecknology.... no I remember from where I used to talk to you
[23:36] <MTecknology> joey: you made me report a bug.... bug 354823 - I was retargetting that the exact same time you were....
[23:36] <MTecknology> BUGabundo: oh?
[23:37] <BUGabundo> from #lp
[23:37] <MTecknology> oh
[23:37] <MTecknology> and where did we talk last?
[23:38] <BUGabundo> on +1
[23:39] <MTecknology> oh
[23:39] <MTecknology> I'm in a lot of channels, I don't bother remembering where I know somebody from, only who they are
[23:40] <BUGabundo> I also have bad memory
[23:42] <MTecknology> Work at 01:00 - so it's bed time before a long night
[23:47] <joey> MTecknology, lol