[00:02] thewrath, did you get your problems sorted? [00:08] i believe so [00:08] everything seems to be working [00:08] you mean with pushing hte code, etc out to launchpad.net? [00:09] kiko: is that correct? and also do you have a pgp or a gpg key? [00:12] gpg [00:12] gpg rocks [00:12] but the keys are the same [00:13] right [00:13] i ahve that all working but want to test it [00:13] can you help me test it? [00:15] how long does it take for an admin or someone else to change the name of a project === Snova_ is now known as Snova [00:34] kiko: ? === Snova_ is now known as Snova [01:54] thewrath, sorry, I gotta dash, catch you tomorrow [02:31] way cool. it really does die. [02:31] OOPS-1189EA13 [02:32] and OOPS-1189D145 for production. [02:32] https://devpad.canonical.com/~jamesh/oops.cgi/1189D145 [02:32] for https://launchpad.net/ubuntu/+source/konversation [02:34] What's the intended workaround? [02:43] Hobbsee: maybe try looking at a different page? [02:55] 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] Hobbsee: There's no workaround to see that page, but you can sometimes check the version history at +publishinghistory [03:06] 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] Hobbsee, bug 353568 [03:07] Launchpad bug 353568 in soyuz "ubuntu/source/package/+index timing out" [High,In progress] https://launchpad.net/bugs/353568 [03:07] people are working on it [03:10] VK7HSE: The correct version would have been 0.8.0+bzr386-0ubuntu1~ppa1 or similar [03:11] The bzr revision is part of the tarball version, surely. [03:11] But your message got cut off, so I don't quite know what you're asking. [03:11] the bzr pull created me-tv-0.8.0.tar.gz ... [03:12] hang on I'll paste it.... [03:12] http://paste.ubuntu.com/143226/ [03:13] I'm still relatively new to the build process! so I was sure to make a mistake! :-/ [03:14] VK7HSE: The correct thing to do was to use 0.8.0~beta or similar. [03:14] As ~ is less than anything else. [03:14] so to rectify, requsting a new release would then fix? [03:14] For now you can use 0.8.0.0, or 0.8.0+something [03:15] Or get them to do a new release. [03:15] And research version sorting thoroughly in future. [03:15] I'll give the suggestions a try thanks... === matsubara is now known as matsubara-afk [04:50] 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] DBO2: http://help.launchpad.net/API [04:54] so I need to become a launchpad beta tester [04:56] Yes. [04:57] is it possible for me to do that or is that a closed group? [05:01] DBO2: There are more than 2000 members - it's quite open. [05:02] Just request to join. [05:02] And somebody will generally approve you within a day or two. [05:02] sweet === spiv_ is now known as spiv [05:43] heh - I found a bug in launchpad design :) [05:43] I feel special [05:47] wgrant: I was able to use the API in a simple way from a python script, and I didn't join the beta group === noodles775 is now known as noodles775-afk [05:57] Does launchpad offer private branches for proprietary software? [06:00] everyone sleeping? [06:01] MTecknology: I believe so. for $ aiui [06:02] spm: you mean it's something that they pay for? [06:02] yes [06:03] AIUI. I'm a sysadmin, not a sales/marketing person. :-) [06:03] MTecknology: https://answers.edge.launchpad.net/launchpad/+faq/208 [06:03] Launchpad developers seem to be very good at long-range typing. [06:03] noodles775-afk: ta. I keep forgetting about the faq... :-) [06:04] wgrant: just getting away from the keyboard now :) [06:04] spm: np! [06:05] 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] 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] spm: Damn. === DBO2 is now known as DBO [06:17] wgrant: because person and team pages use different templates? [06:54] jamesh: they all seem to be like that [06:54] wgrant: ah, right [06:55] Ursinha: thanks, hope to see it fixed soon [07:03] jamesh: They're not in the templates. [07:03] jamesh: they're generated by JavaScript. [07:40] Does staging.launchpad.net actually host bazaar branches? ie - can code be uploaded there? [07:41] MTecknology: Yes. [07:48] Hobbsee: hi [07:48] Hobbsee: it seems to be months between times when I see you around [07:48] MTecknology: greetings. And I don't frequent here so much anymore, which is probably why [07:53] Hobbsee: only other channels I sit in that you're also in right now are -bugs and -meetings [07:54] s/ngs/ns/ [07:54] sounds about right [07:56] MTecknology: don't expect uploads to bazaar.staging.launchpad.net to stick though. === noodles775-afk is now known as noodles775 [08:01] jamesh: I was curious because of this - https://answers.edge.launchpad.net/launchpad/+question/65927 [08:04] Huh./ [08:04] Indeed, the branches don't seem to be there any more. [08:04] But I'm fairly sure I was able to use even private codebrowse on there a month ago. [08:04] But maybe that was only for a new branch. [08:09] Hi LP folks! Can I create a "superproject" myself, or is it something launchpad admins has to create for you? [08:09] That needs an LP admin, IIRC. [08:12] speakman: Ask at https://answers.launchpad.net/launchpad/+addquestion [08:12] Yeah, best to put a request like one of the others here speakman : [08:12] 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] wgrant: too quick! [08:13] noodles775: Only by a fraction of a second :( [08:14] * wgrant laments the lack of a 'Nearby' part of the breadcrumbs. [08:14] There used to be menus that almost fulfilled that purpose, but they got culled for 2.0. [08:15] wgrant: what do you mean by a 'Nearby' part? What's an eg on another site? [08:16] noodles775: I don't know of any examples [08:16] 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] Ah... neat idea... [08:16] For a source package in a distroseries it should drop down links to that source package in its other distroseries. [08:17] Sounds like it'd be worth chatting with beuno when he's around! [08:17] That's what I thought. [08:17] Because at the moment you have to hack URLs or perform an awful lot of clicks. [08:19] Yeah [08:20] Do you remember the old breadcrumb menus? They might have gone before you appeared on the scene. [08:20] wgrant: noodles775: thanks! (just curios: why do you link primarly to edge..?) [08:21] edge comes up automatically in urls for those using it [08:21] speakman: it happens by default if you sign up as a beta tester... [08:21] it's difficult to remember every time to remove it from urls [08:21] Maybe we need an irssi plugin to strip 'edge.' [08:22] 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] I don't think you can do it globally. [08:23] Since it doesn't make sense, in most cases. [08:23] In Launchpad's case it does, but that's because Launchpad's usage of Launchpad is somewhat wrong. [08:24] haha mdke [08:24] tis okay, it's not a blog post :) [08:24] wgrant: that's what I figured [08:24] popey: ;p [08:25] 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] i used to think I had no irrational OCD behaviours, now I realise I have quite a few [08:25] MTecknology: at least until the database gets wiped the next day [08:25] jamesh: Is this a new thing? [08:25] 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] mdke: I think that last case can be fulfilled by supercharged tags. [08:26] wgrant: not particularly new. [08:26] wgrant: for bug reporting only, surely? [08:26] noodles775: i meant your link in here :) [08:26] wgrant: how can tags be used for translations or code? [08:26] wgrant: noodles775: btw, here's my question: https://answers.edge.launchpad.net/launchpad/+question/66316 [08:27] mdke: I'm not quite sure how translations or code need to be kept separate. [08:27] 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] 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] 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] mdke: In Launchpad's case it's actually all in one branch. [08:29] Although that will change soon. [08:29] wgrant: I'm speaking hypothetically [08:29] (although not to the extent of the current proliferation of projects) [08:29] Right. [08:29] I used the example of Launchpad because you said that its use of group projects is wrong [08:29] and I can see what you meant by that [08:29] 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] noodles775: oh, I see! :D [08:30] wgrant: ok, that's clearer [08:30] wgrant: Launchpad code isn't split between the historic malone, rosetta, etc projects. [08:30] wgrant: in that case, a feature to set single series and milestones across projects would make sense for some projects [08:30] you'll see things split up a bit more closer to the release though [08:30] jamesh: 'In Launchpad's case it's actually all in one branch.' [08:31] I did just say exactly that, I think. [08:31] [some infrastructure bits have already been separated and released] [08:31] speakman: I've assigned your question to kiko :) [08:33] jamesh: It won't be split up apart from the infrastructure and non-free bits, will it? [08:33] wgrant: there are plans to make the codebase more modular. I don't know how much will be in separate branches though. [08:34] a lot of the infrastructure will be in separate branches though. [08:34] noodles775: thanks, but why did it move from "Launchpad-itself" to one of our projects? :D [08:34] As we already have in /lazr, right. [08:39] speakman: Sorry, my mistake :D Set back to launchpad. [08:39] noodles775: The email just arrived :D [08:40] * wgrant feared that the Blueprint bug had hit Answers too. [08:40] noodles775: There was one swedish talking person @ launchpad according to the question form. Is that "kiko"? [08:41] speakman: kiko loves languages, but I don't think he's started swedish yet. Not sure who it might be. [08:43] noodles775: i see :) [08:44] 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] speakman: I guess that depends on the project... and who has permission to merge into the parent branch. [08:51] 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] speakman: Some people run a daemon that automatically merges approved branches into trunk, too. [08:52] 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] wgrant: is the merge proposal closed when merge is committed? [08:54] speakman: Yes. [08:55] oh, [08:55] oh great. then two people doing the same merge is not so likly :) [08:56] I'd be a bit suspicious if I did a merge and there were no revisions to merge, I think. [08:56] So it's not likely in any case. [11:24] is lp b0rked? some pages only return OOPS, like https://edge.launchpad.net/ubuntu/+source/xorg-server/ [11:25] tormod: Bug #353568 [11:25] Launchpad bug 353568 in soyuz "ubuntu/source/package/+index timing out" [High,In progress] https://launchpad.net/bugs/353568 [11:25] thanks [11:51] how can i prevent my membership in a team to expire ? === salgado-afk is now known as salgado === bac` is now known as bac === al-maisan is now known as al-maisan-afk === matsubara-afk is now known as matsubara [14:03] Anyone know how I can remove a bug watch? [14:05] jpds: just assign the project to "nobody" [14:06] jpds: You can't remove a watch, but you can unlink it from the task easily. [14:07] wgrant: That's a shame, I just set it as "None" and marked as invalid. [14:08] jpds: You wanted to remove the whole task, not just the watch? [14:08] Ah, you can actually delete the watch if it's not linked to a task. [14:08] wgrant: That too would be preferable (it's bug #335715). [14:08] Error: Could not parse data returned by Launchpad: timed out (https://launchpad.net/bugs/335715/+text) [14:09] * wgrant resolves to port ubottu to launchpadlib tomorrow [14:09] jpds: Oh, you can't actually delete tasks. [14:09] (yet, hopefully) [14:09] thanks for the million karma points guys <3 [14:09] You might as well delete the bug watch (hit the edit icon in the portlet) [14:10] vorian: Wow. Literally. [14:10] * wgrant remembers the days when 10 million was commonplace. [14:10] * vorian chuckles at "it's fixed" [14:10] But... that's a bit extreme now. [14:11] vorian: I don't think they ever fixed the karma bug. [14:11] it's not karma, it's rosetta [14:11] I mean the karma-giving bit of rosetta. [14:11] i used a filter this time to auto-delete all the rosetta spam [14:11] It's not spamming you 20000 times any more, is it? [14:12] only about a 10th this time around [14:12] danilos: ^^ [14:12] I'm still got a ton of successful import emails [14:12] and they are still hitting my trashbin [14:14] beuno: Did you see my UI suggestion here about 6 hours ago? [14:21] wgrant, I didn't [14:22] wgrant, care to copy'n'paste it? [14:23] 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] 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] On a distribution series source package breadcrumb, I would get links to the source package in other distro series. [14:24] 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] wgrant, oh, I have plans for something like that :) [14:25] beuno: Ah, good. [14:25] something among the lines of having arrows on all breadcrumbs [14:25] Right. [14:25] and being able to jump between that object [14:25] Like we had until a year ago. [14:25] yes, but better [14:25] a smart "top 5 list" and a search box that will jump directly if there's an exact match [14:26] IIRC that was more focused on things related to the breadcrumb in question (eg. milestones for a product), rather than alternatives. [14:26] Hmmm. interesting. [14:27] I'll poke you when I manage to see this through a little bit more [14:27] Thanks. === gary_poster changed the topic of #launchpad to: https://launchpad.net/ | Help contact: gary_poster | Join https://launchpad.net/~launchpad-users | Channel logs: http://irclogs.ubuntu.com [15:36] hm, https://launchpad.net/ubuntu/+source/python-central gives me a timeout :/ (both edge and normal) - OOPS-1189A1407 [15:36] https://devpad.canonical.com/~jamesh/oops.cgi/1189A1407 [15:38] mvo: looking [15:39] mvo: yeah, duped...looking further [15:39] thanks [15:47] 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] 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] Launchpad bug 353568 in soyuz "ubuntu/source/package/+index timing out" [High,Fix committed] [15:47] great, thanks for the quick response matsubara and gary_poster_ === gary_poster_ is now known as gary_poster [16:13] hi guys [16:13] we want to remove a team form launchpad [16:13] hwo do we do it [16:15] seiflotfy, you have to request it via Launchpad answers: https://answers.launchpad.net/launchpad === salgado is now known as salgado-lunch [16:43] 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 === kiko is now known as kiko-phone === Nicke_ is now known as Nicke [17:34] Is it still possible to copy a package from a private ppa to a public ppa? === salgado-lunch is now known as salgado [17:37] nhandler: not sure, will check for you [17:37] gary_poster: Thanks a lot. I know it used to be possible, but now Launchpad keeps throwing an error [17:45] nhandler: hi, copy from private to public PPAs is not possible [17:46] 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] 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] nhandler: P3A files are stored in a separated (private) librarian instance. [17:48] 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. === gary_poster is now known as gary_poster_lunc === gary_poster_lunc is now known as gary_posterLUNCH === kiko-phone is now known as kiko === kiko is now known as kiko-fud === matsubara is now known as matsubara-lunch [18:27] ooi, what criteria does Launchpad apply to discriminate "Incomplete (without response)" and "Incomplete (with reponse)" [18:27] ? [18:29] maxb, I guess when there's a comment? [18:29] Any comment since the status was last changed? [18:30] I suppose I could answer this myself by messing around on staging [18:30] BjornT, intellectronica, gmb, ^ [18:30] Or I could wait until 3.0 :-) [18:31] maxb: incomplete (with response) means there was a new comment on that bug since it was last put in the incomplete state [18:32] so the workflow is: you say "this bug is incomplete, please provide more info", then you wait for a comment... [18:33] thanks === gary_posterLUNCH is now known as gary_poster === kiko-fud is now known as kiko === matsubara-lunch is now known as matsubara [19:39] hi! if i add a PGP key to my user, is it possible to remove it later? [19:40] thou, you can, yes -- but why would you want to? [19:40] or thou canst, more appropriately :) [19:40] :-) [19:40] kiko, my team has a code-signing pgp key; it's not my personal one [19:41] thou, hmmm. and why do you wanna associate that with your account? [19:41] i am exploring the best way to manage uploading source packages to a PPA, signed by the team's key [19:41] i don't want to sign the packages with my personal key [19:42] i'm not sure if i should add a new launchpad user for the team, and associate the key with that user [19:43] cprov, can you advise thou on the best course of action [19:43] 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] thou: let me catch up quickly [19:44] sure [19:46] 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] 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] thou: I just don't understand why you don't want the person responsible for a source change to sign it. [19:47] thou, gpg keys are pretty personal things :) [19:47] sure [19:47] that's why i *don't* want my key used for this [19:47] there might be 5 different people working on building a release [19:47] and 100 people who made code changes [19:47] thou, right, but any of those people can sign the source and it will be accepted [19:48] that's cprov's point -- not using a shared gpg key makes a lot more sense [19:48] but we use a shared account [19:48] a shared account.. where? [19:48] and we have a single code-signing key that is well known (build@mysql.com) [19:49] not a launchpad account, but ... hrm, i'm not explaining well [19:49] thou, I think I'd create a separate LP account for that address, then. [19:49] thou, we do that for our PQM account for instance [19:49] (not for the same reason, I'm just giving the rationale for having an account for a robot) [19:49] ok, and subscribe that account as a member of the project team [19:49] precisely [19:50] that "feels" better to me [19:50] for launchpad the pqm bot can write to our branches [19:50] i was concerned if launchpad users are meant to be real people [19:50] and in fact it is the only thing that actually does (USUALLY, though sometimes we break the rules) [19:50] ok, great [19:50] they mostly are, but this is an acceptable violation of that guideline [19:51] usually people ask that bots be created as teams [19:51] which often works, but for this case, obviously doesn't [19:51] and it's not a bot, really [19:52] although we will script it, of course, someone will have to push the button to say "yes, it's OK, publish this" [19:53] kiko, cprov: thanks a lot for your advice [19:54] thou, a pleasure talking to you by the way, haven't seen you asking around here before [19:54] no, i'm trying to take over from mordred [19:54] thou, yeah.. pqm is similar in that it is email controlled [19:54] thou, the main difference is probably that while I don't know your script I absolutely HATE pqm [19:55] oh-oh said it out loud again [19:55] * kiko gets in trouble [19:55] i don't know my script either. not sure it exists yet. [19:56] thou, there's this autoppa thing that jamu wrote. have you seen it? [19:56] yeah [19:56] too limited for me [19:56] not extensible enough, or just the wrong design? [19:56] the template thing only handles different ubuntu releases (hardy/intrepid/etc.) [19:56] 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] i need to be able to create some packages that, e.g., don't include innodb at all [19:57] mmm [19:57] so my files listing will or won't include some sets [19:57] thou: You mean not including innodb in a Depends: line? [19:57] i'm planning to use m4 to generate the real debian/* [19:58] That sounds weird. :) [19:58] 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] jkakar, hey, some people use m4 to generate .procmailrc files [19:59] hmm [19:59] 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] with the same name?! [20:00] we'll have mysql-enterprise-classic-gpl, mysql-enterprise-pro-commercial, etc. [20:00] 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] where classic, pro, advanced, etc. include different sets of features [20:00] Those sound like different packages with different inputs. Perhaps all relying on some shared core package. [20:01] jakwell, that's like building client, server, libs, test packages [20:01] like sub-packages, right? [20:02] so we have libmysqlclientVER-dev.deb, mysql-client-VER.deb, mysql-common-VER.deb, mysql-server-VER.deb [20:02] those are all defined in the control file [20:03] Cool, then you can build them all at once with AutoPPA. [20:03] but i need the option of building all of those in the 'pro' or 'classic' configuration [20:03] and 'pro' and 'classic', etc., are almost identical [20:04] but have different features sets defined, which means different ./configure --foo, resulting in different files and directories lists [20:04] and of course build those for dapper, hardy, intrepid, ... [20:04] Right. All possible permutations of terribleness. ;) [20:05] afaiks autoppa handles the hardy/intrepid mess [20:05] thou: Your idea to generate the debian directory doesn't sound so bad now. [20:05] but doesn't handle the pro/classic mess [20:05] thou: Yep. [20:07] 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] In which case AutoPPA templating system will work for you (though, yeah, it could get pretty hairy). [20:07] 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] i can use wildcards, perhaps [20:08] but that is kind of sketchy it seems [20:09] 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] But it feels a bit special-cased... which makes me wonder about supporting plugins for this kind of thing. [20:09] Though, implementing a plugin is probably too much work for most people. [20:10] 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] adrian15555: it's a broken debian/changelog entry, use one of the ubuntu series (intrepid, jaunty, ...) [20:12] ... 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] 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] even for mysql, community packages only have a single flavor [20:16] 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] 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] thou: Yeah. [20:16] 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] cprov, Do you mean that "fai (3.2.4+svn4837-0ubuntu2~ppa1) intrepid; urgency=low" is wrong? [20:18] 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] adrian15555: no, this one looks correct. [20:18] cprov, So what did you mean then? [20:18] jkakar: at the very least, i'll steal some code from you :-) [20:19] thou: Please do. :) [20:19] thou: Also, patches welcome. :) [20:19] cprov, I can give you more details if you want to. [20:20] adrian15555: the upload path is the problem, '~adrian15/ppa/fai/' [20:20] jkakar: i certainly will, if i manage to get that far [20:21] adrian15555: if you are aiming you ppa named 'fai' it should be '~adrian/fai/' only [20:21] 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] cprov, ok. [20:21] cprov, This howto needs improvement then [20:21] cprov, I am going to try your suggestion. Thank you very much. [20:36] 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] adrian15555: i think it's the next */20 in cron-speak [20:40] (though that might be something else) [20:41] adrian15555: the process runs */5, so if you are unlucky up to 10 min ;) [20:44] */20 is the publisher? [20:45] cprov, ok. I am going to upload two more packages and tomorrow I will check it [20:46] maxb: exactly [20:49] Thank you much everyone. Bye. [20:50] maxb: btw, I've just run queue-builder to create builds for the binary P-a-s lines, it's done. [20:50] maxb: let me know if there are other missing builds. [20:52] Looks good, I see the hppa builders just finishing up those builds :-) [21:00] maxb: very nice, -1 problem. [21:16] hi, anyone else having problems connecting to https://edge.launchpad.net/ubuntu/+source/gnome-games ? [21:16] Tiefflieger, yes, we're working on fixing it [21:16] well, cprov is :) [21:17] ok, thanks :-) [21:17] Tiefflieger: the fix will be released very soon. [21:18] 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] Tiefflieger, sure, thanks for letting us know [21:23] Hi, I wish to know the status of launchpad bug I've submitted - https://bugs.launchpad.net/launchpad/+bug/353950 - anyone cares? [21:23] Launchpad bug 353950 in launchpad "Timeout while approving large group membership" [Undecided,New] [21:24] Agafonov, of course we care! [21:25] Agafonov, we've just been busy rolling out a new version of Launchpad these past days [21:25] I've re-assigned it to the correct sub-project, and the right people will look at it early next week [21:26] I've noted some changes :) [21:26] beuno: how can I learn which sub-project? [21:27] Agafonov, well, anything to do with people/teams/projects is the "registry" sub-project [21:27] but it's hard to guess [21:27] which is why we ask people to file it against launchpad, and we re-jiggle them later on [21:29] beuno, catch me in midair, just opened that bug for triage :) [21:29] *caught [21:31] beuno: oh, already re-assigned, thanks. [21:34] Ursinha, :) [21:38] any rosetta developers around? [21:39]