[01:43] <mwhudson> what's the voodoo for copying a package from ubuntu to a ppa?
[01:43] <mwhudson> does it involve url-hacking?
[01:45] <maxb> mwhudson: yes, if you want to do it in the web ui
[01:45] <mwhudson> ok
[01:46] <mwhudson> i'm not actually sure i need to do it right now, come to think of it
[03:07] <mih1406> Hi, I want to install launchpad in my site for translation only, can I install it using web-based?
[03:27] <thumper> mih1406: why not use the public launchpad?
[03:41] <mih1406> thumper, they need to confirm the files that I upload as mention in the site. I am translating the same files in Ubuntu for a language that is already supported in launchpad but in other rules!
[03:42] <mih1406> thumper, I have a team for re-translating the Arabic version of Ubuntu packages into another form or Arabic!
[03:42] <mih1406> thumper, are they gonna accept my files?
[03:42] <thumper> mih1406: not sure, I don't know much about the translations bit, ask jtv, henning or danilo
[03:43] <thumper> jtv should be coming online soon
[03:43] <jtv> thumper: you called?
[03:43] <thumper> henning and danilo are europe time
[03:43] <jtv> mih1406: what form of Arabic is this?
[03:44] <mih1406> the same but with a more common usage for computer terms
[03:45] <mih1406> jtv
[03:45] <jtv> So more like what people actually use?  How come there's a difference?
[03:46] <mih1406> The current Arabic translations are not accepted by many many of Arabic users!
[03:47] <mih1406> We are a team and want to edit and re-translate to a more common translations and more (windows-like) translations.
[03:47] <jtv> That sounds like it would be better if the original Arabic could change.  I'm sure you tried talking to the Arabic translation teams though.
[03:49] <mih1406> Yes I we talked to them but they answered it should be accepted in the future!!
[03:49] <mih1406> Do you know arabic?
[03:49] <mih1406> They are translating "Save file" to some thing like "Do Save a File"
[03:50] <mih1406> They are using the "v" form, which is very ugly in computer world!
[03:50] <mih1406> verb form
[03:51] <jtv> I'm sorry, no, I don't know Arabic.
[03:52] <jtv> I've heard it can place a lot of emphasis on form.
[03:52] <mih1406> Do accept it in English like this "Do Save a File"?
[03:52] <mih1406> In a menu item?
[03:52] <mih1406> ;)
[03:52] <jtv> To me, English is quite unusual for a European language—quite lucky really that it became the dominant computer language.
[03:53] <mih1406> Anyway, using a popular form and correct form is better than a strange correct form? Do you agree?
[03:54] <jtv> In English you don't even need to know if "Save File" is in the infinitive or the imperative.  Or what form of "you" to use.  Or whether the computer should speak as a man or a woman.
[03:54] <jtv> mih1406: Yes, personally I agree.  Though of course I just have to believe you on what these issues actually look like in Arabic.  :-)
[03:55] <mih1406> go back to our topic
[03:55] <mih1406> can I start a project in launchpad?
[03:56] <mih1406> or they are going to reject my .po files?
[03:56] <jtv> I don't think a project makes sense.  A translation team, definitely, but then you have a conflict for who does "the real Arabic."
[03:57] <jtv> Another thing we could, in theory, do is create a variant of Arabic.  That's something we didn't support two weeks ago, so some very new decisions to be made.
[03:58] <jtv> So then there'd be an "ar@something" (where "something" is some kind of identifier for this translation style).  But I'm not sure whether that'll be accepted.
[04:00] <mih1406> Our idea is to re-translate the same files and create a new package for the translations. It is not important to be the official package in ubuntu or other distros
[04:00] <mih1406> This package replaces the official package .mo files!
[04:01] <mih1406> After becoming more popular we can have our word in the official GNOME and KDE translations teams
[04:02] <jtv> Translating the same packages (and there are many!) in two places is likely to lead to trouble.  *Technically* a language variant is the best solution, though I can't say that that's the intended use of variants.
[04:03] <jtv> It also means that the existing Arabic translators can enable automatic translation suggestions from your variant, and vice versa.
[04:10] <jtv> I don't think there are any other good solutions besides convincing other translation teams or creating a variant.
[04:11] <jtv> mih1406: it'll be another 7 hours before our team is complete and we can discuss this.
[04:13] <mih1406> tjv, can we have a variant ar_SA (Saudi Arabia) as in windows?
[04:20] <jtv> No, not like that—because that is for countries.
[04:26] <mih1406> ?
[04:27] <mih1406> we are team of SA people
[04:27] <mih1406> linuxKSA.org
[04:28] <jtv> mih1406: you did not say that your version of Arabic is specific to Saudi Arabia.
[04:28] <jtv> If it's not, then ar_SA is not the right code for this.
[04:28] <mih1406> Actually there is no difference in Arabic among countries!
[04:28] <jtv> Nor any other country.
[04:29] <jtv> My point is that we can't abuse the country codes to express differences that have nothing to do with the country.
[04:29] <mih1406> yes, you are right
[04:30] <mih1406> so we have to stick to our idea! until we get more and more people
[04:31] <jtv> If you have enough people, we can discuss an ar@abcd (where "abcd" identifies the translation style somehow).
[04:31] <mih1406> good
[04:32] <jtv> I think it would, however, take enough people that you could achieve reasonably complete translation coverage (otherwise everyone will want to have their own language :)
[04:32] <mih1406> We will translate GNOME and KDE 100% :)
[04:33] <jtv> If you can do that, great!  I wish you good luck.  I'll bring up your use-case with the rest of the team when they get here.
[04:44] <mih1406> thank you
[04:50] <mwhudson> mm
[04:50] <mwhudson> is there an easy way to grab a package from debian and get it into a ppa?
[04:51] <nhandler> mwhudson: You could use pull-debian-source in ubuntu-dev-tools to grab the package
[04:52] <lifeless> mwhudson: bzr branch lp:debian/foo/bar; dch -i; bzr db-do; dput ppa:foo
[04:54] <mwhudson> hmm
[04:54] <mwhudson> the version i want might only be in experimental even
[04:54] <nhandler> mwhudson: pull-debian-source lets you specify where to pull from (pull-debian-source package experimental)
[04:56]  * mwhudson tries to remember how debian works
[04:57] <lifeless> its a series of tubes
[04:57] <lifeless> with flamewars in between
[04:57] <ajmitch> I think the flames help the tubes flow
[04:57] <mwhudson> nhandler: why does "pull-debian-source python-virtualenv sid" get me version 1.4.9-1 while http://packages.debian.org/sid/python-virtualenv says 1.4.9-3 ?
[04:58] <ajmitch> mwhudson: because one of the debian servers that carries such information is having hardware troubles, apparantly
[04:58] <micahg> mwhudson: debian qa madison cache is out of date
[04:59] <nhandler> +1 micahg.
[04:59] <mwhudson> ah ok
[04:59] <nhandler> I'm not sure when that gets updated
[04:59] <ajmitch> & 1.4.9-3 was uploaded only today
[04:59] <ajmitch> http://packages.qa.debian.org/p/python-virtualenv.html
[04:59] <ajmitch> grab the dsc file from there with dget
[04:59] <micahg> mwhudson: if you add this to ~/.devscriipts, it'll work: RMADISON_URL_MAP_DEBIAN=http://qa.debian.org/cgi-bin/madison.cgi
[05:00] <mwhudson> micahg: nope
[05:00] <micahg> hmm
[05:01] <micahg> oh, it must need more ahcking
[05:01] <ajmitch> dget http://ftp.debian.org/debian/pool/main/p/python-virtualenv/python-virtualenv_1.4.9-3.dsc
[05:01] <mwhudson> oh right 1.4.9-2 was only uploaded today too
[05:01] <mwhudson> (which has the fix i care about)
[05:01] <mwhudson> anyone want to sync that to maverick? :-)
[05:02] <mwhudson> gpg: Can't check signature: public key not found
[05:02] <mwhudson> i guess i'm missing some debian key?
[05:02] <ajmitch> that's usual
[05:03] <ajmitch> because you don't have the public key of the person who uploaded it
[05:03] <ajmitch> but it would have grabbed the .dsc & tarballs
[05:03] <ajmitch> you can now use dpkg-source -x on the .dsc file to extract it
[05:04] <ajmitch> or you could have done it with dget -u -x blabla.dsc, but I was silly & didn't give the full info
[05:05] <micahg> mwhudson: requestsync works with that line in devscripts
[05:05] <micahg> mwhudson: but there are ubuntu changes
[05:06] <mwhudson> oh right
[05:06] <mwhudson> seems from https://merges.ubuntu.com/p/python-virtualenv/REPORT that it's just something in the control file that conflicts?
[05:07] <ajmitch> merges.ubuntu.com is also out of date
[05:07] <micahg> mwhudson: that's out of date 1.4.9-1ubuntu1 is current
[05:07] <mwhudson> awesome
[05:08] <ajmitch> reading the changelog of -2, it may be able to be synced now
[05:08] <ajmitch> depending on how much of the ubuntu change they used
[06:40] <mih1406_> are there other translation software for the web?
[07:09] <jtv> mih1406_: there are a few, though afaik they don't have same ability to offer suggestions across projects and languages.
[07:09] <jtv> (I couldn't name any right now, sorry)
[07:28] <thopiekar> moin, I need more space for my ppa (ppa:thopiekar/ppa) while building kde3.5 packages for maverick
[07:29] <thopiekar> the web ui says that 100% space 2GB/2GB is in use..
[07:57] <thopiekar> no chance to request more ppa space here?
[08:00] <mih1406_> jtv: we do not need suggestions. we need to host our files and to visualize the process like in launchpad
[08:01] <jtv> mih1406_: I'm assuming you want other Arabic translators to use your suggestions  :-)
[08:44] <jml> thopiekar, ask a question on Launchpad. https://answers.launchpad.net/launchpad
[10:10] <zyga_> hey
[10:10] <zyga_> I just found a bug in stacked branches handling
[10:10] <zyga_> I just want to confirm with you before I report it
[10:11] <zyga_> I created a branch called 'trunk', then pushed a merge proposal for that branch, then finally renamed the 'trunk' branch (in lp.net, "change branch details" link) to "stable"
[10:12] <zyga_> after that operation attempts to get the merge proposal branch fail with "bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~arm-infrastructure/launch-control/trunk/"
[10:18] <maxb> zyga: known. I believe there's even hope of a fix next cycle
[10:18] <zyga> maxb, thanks,
[10:42] <thumper> zyga: if you rename the trunk branch back, you should be able to get the merge proposal branch
[10:43] <zyga> thumper, I just did that, I have some leftover mess (stable branches got pushed too) but I'm cleaning it up
[10:43] <wgrant> Otherwise you can fix the merge proposal branch's stacked_on URL.
[10:44] <zyga> mmm
[10:44]  * zyga didn't think about that
[15:24] <weather15> Hello Everyone
[16:03] <apachelogger> I just got:
[16:03] <apachelogger> The following errors were encountered:
[16:03] <apachelogger> Object: , name: u'https'
[16:10] <rockstar> weather15, you can find docs on creating new recipes here: https://help.launchpad.net/Packaging/SourceBuilds/Recipes
[16:19] <weather15> Thanks
[16:51] <weather15>  /msg NickServ identify compaq01
[16:51] <weather15> I wonder why that just appeared on my screen
[17:40] <weather15> Hey Rock Star are you still out there?
[17:40] <weather15> I was following your documentation
[17:41] <weather15> Ubuntu gives me an error bzr-builder command does not exists
[17:41] <weather15> *command not found rather
[17:42] <weather15> The plugin is installed how ever
[17:44] <maxb> There is no 'bzr-builder' command. It adds several subcommands to 'bzr'
[17:44] <maxb> Try 'bzr help builder'
[17:45] <weather15> Okay
[17:46] <weather15> should be bzr build
[17:46] <weather15> then unknown command builder
[17:46] <weather15> ??
[17:47] <weather15> help says bzr-builder but that does not work see ^
[17:50] <maxb> weather15: What help are you claiming says bzr-builder?
[17:50] <weather15> https://help.launchpad.net/Packaging/SourceBuilds/GettingStarted
[17:51] <maxb> I don't see that telling you to execute 'bzr-builder' as a command anywhere
[17:52] <weather15> See this part: Simple Example
[17:52] <maxb> I see it. It doesn't tell you to run 'bzr-builder'
[17:53] <weather15> okay then what does it tell you?
[17:54] <maxb> It is a couple of descriptive sentences plus an example builder recipe
[17:54] <weather15> Looks like
[17:54] <weather15> a file
[17:54] <weather15> just what should the file name be
[17:55] <maxb> anything you like - for example, 'recipe.txt'
[17:55] <weather15> okay great
[18:49] <pmatulis> if i add a uid to my gpg key will LP sync with the gpg servers?  no action needed on LP side?
[18:50] <pmatulis> disregard, LP profile links directly to gpg server
[20:22] <weather15> Anyone know what to do about this error: debconf-updatepo /bin/bash: debconf-updatepo: command not found make: *** [clean1] Error 127 dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 debuild: fatal error at line 1340: dpkg-buildpackage -rfakeroot -d -us -uc -i -I -S failed bzr: ERROR: Failed to build the source package
[20:23] <james_w> weather15: add po-debconf to your Build-Depends
[20:24] <weather15> okay
[20:24] <james_w> weather15: probably you are using debhelper and don't have that in Build-Depends either?
[20:25] <weather15> How can I do this?
[20:25] <weather15> I'm using bzr daildeb
[20:25] <weather15> *dailydeb
[20:26] <james_w> whatever branch you are using that provides the packaging needs to change
[20:26] <james_w> or you merge an extra branch that makes the needed changes
[20:27] <weather15> Yes I'm using my branch
[20:27] <weather15> How do I change it?
[20:28] <james_w> commit the changes to the branch with bzr
[20:28] <james_w> edit the debian/control file
[20:28] <weather15> not sure if there is one
[20:30] <james_w> there has to be
[20:30] <weather15> What would be the name of the file?
[20:31] <james_w> debian/contro
[20:31] <james_w> debian/control
[20:31] <weather15> Okay found it now what?
[20:32] <james_w> edit the Build-Depends line to add "debhelper"
[20:33] <weather15> Debhelper is there already
[20:33] <james_w> do you have it installed?
[20:35] <weather15> hold on a minute
[20:35] <weather15> nope I don't
[20:35] <weather15> that's the problem
[20:36] <weather15> let's hope this build suceeds
[20:42] <weather15> It Did thanks James_w
[21:32] <Mez> can a project in launchpad be deleted/archived?
[21:32] <Mez> as it's no longer in development
[21:32] <cody-somerville> Mez, It can be deactivated.
[21:33] <Mez> cody-somerville: can I do that?
[21:33] <Mez> Or do I have to request lp-admin?
[21:34] <cody-somerville> Mez, the latter I believe
[21:34] <cody-somerville> Mez, whats the project? I might be able to do it.
[21:34] <Mez> katapult
[21:34] <Mez> cody-somerville: didn't realise you were an admin
[21:35] <Mez> didn't realise you were a canonical employee now ;)
[21:36] <cody-somerville> Oh, I've been a Canonical employee for two years now.
[21:37] <cody-somerville> I'm also not a full lp admin - just a 'demi-admin'. ;-)
[21:37]  * Mez fails
[21:37] <Mez> cody-somerville: are you able to?
[21:37] <cody-somerville> I'm told the project can't be deactivated because its linked to one or more source packages.
[21:38] <Mez> As far as I'm concerned, they can be removed
[21:39] <Mez> ew
[21:39] <Mez> twas in hardy.
[21:39] <Mez> Is that not EOL'd yet?
[21:40] <Mez> Ah well...
[21:40] <cody-somerville> Mez, okay, all done.
[21:40] <Mez> ooh, ty :D
[21:40] <Mez> any chance of getting rid of the team too?
[21:41] <Mez> https://edge.launchpad.net/~katapult-dev
[21:41] <cody-somerville> Mez, I can try, sure.
[21:41] <Mez> https://edge.launchpad.net/~katapult-testers
[21:41] <Mez> (apparently I made 2 teams!)
[21:42] <cody-somerville> Okay, you want both teams deleted?
[21:42] <Mez> please.
[21:42] <Mez> As I've said, the code's defunct, I'm slowly getting it removed from KDE's stuff
[21:43] <cody-somerville> Mez, done
[21:43] <Mez> cody-somerville: cheers :D
[21:43] <cody-somerville> Mez, cheers! :)
[21:43] <Mez> I've probably got some other cleaning up to do at some point, mind if I poke you then ?
[21:45] <cody-somerville> Mez, If there isn't someone else around that can better help you, sure. :)
[21:46] <Mez> aw :) But I like having my pets^W slaves^W useful contacts
[21:46] <Mez> :-"
[21:47]  * cody-somerville grins.
[22:25] <yofel> is it intentional that edge now shows the login id in the upper right corner instead of the display name and clicking on it on bugs.edge.launchpad.net opens bugs.edge.launchpad.net/~<user> instead of edge.launchpad.net/~<user> (same for the other sections) ?
[22:40] <maxb> yofel: the login vs the display name change is intentional, not sure about the other
[22:44] <wgrant> yofel: The latter is a bug.
[22:45] <wgrant> I think there's a bug filed.
[22:45] <wgrant> I consider the former to be a bug too, but it's apparently deliberate.
[22:45] <micahg> hmm, it's context sensitive now, is that a bad thing?
[22:46] <yofel> ok
[23:01] <weather15_> Anyone know what to do about this error? bzr: ERROR: No previous changelog to take the package name from, and --package not specified: debian/changelog didn't contain any parseable stanzas.
[23:02] <jelmer> weather15_: When does this occur?
[23:02] <wgrant> weather15_: Your recipe is buggy. Your debian directory isn't being merged in properly.
[23:03] <weather15_> I modified the Change Log and boom
[23:03] <wgrant> Oh.
[23:03] <wgrant> The problem is that your changelog is corrupt, actually.
[23:03] <wgrant> It's not formatted properly.
[23:04] <wgrant> But why were you altering it manually?
[23:04] <wgrant> bzr-builder does that.
[23:05] <weather15_> I had to modify it as I am using the source of another application so a new change log was needed
[23:06] <weather15_> Can I just delete it an go from there or what?
[23:06] <wgrant> You can't delete it.
[23:06] <wgrant> Can you link to the recipe?
[23:07] <nhandler> I'm working on testing something with the wiki using WWW::Mechanize::Shell (no javascript, but cookies are supported). When I try to login to the wiki, I get up to the last openid lp page that lists the info that will get sent to the wiki if I hit 'Yes'. However, whenever, I hit yes, the same page simply reloads. I don't get sent to the wiki, and I am not logged in. Any ideas?
[23:07] <weather15_> My Recipe is on my computer but give me a minute
[23:08] <weather15_> See this: http://pastebin.ubuntu.com/483122/
[23:09] <wgrant> weather15_: Check the diff in that last revision.
[23:09] <wgrant> You changed the indentation.
[23:09] <wgrant> Also, package names are lowercase.
[23:10] <weather15_> How's this: http://pastebin.ubuntu.com/483124/
[23:10] <wgrant> james_w: What's with all these attempts to work around 3.0 (quilt) in recipes? Is it that hard to get pristine-tar integrated?
[23:11] <wgrant> weather15_: You should indent the two bullets by two spaces.
[23:11] <weather15_> Okay
[23:11] <weather15_> Otherwise that I'm good to go?
[23:12] <wgrant> Looks like it.
[23:12] <weather15_> Great Thanks
[23:14] <weather15_> bzr: ERROR: No previous changelog to take the package name from, and --package not specified: debian/changelog didn't contain any parseable stanzas.
[23:14] <weather15_> ?? ^
[23:18] <maxb> huh, someone else mentioned getting that on launchpad, but it didn't seem to reproduce when running the recipe locally
[23:18] <wgrant> Oh.
[23:18] <wgrant> weather15_: You changed the indentation of the bottom line.
[23:18] <wgrant> Why are you editing the changelog manually?
[23:18] <wgrant> You should be using 'dch'
[23:19] <weather15_> DCH??
[23:19] <wgrant> The tool to maintain Debian changelogs.
[23:19] <james_w> wgrant: not particularly, but the issue is where do you get the input to pristine-tar?
[23:20] <weather15_> Where can I get this and how do I use it?
[23:21] <wgrant> https://wiki.ubuntu.com/PackagingGuide/Complete#changelog
[23:22] <weather15_> Okay that's what I'm trying to do
[23:31] <lamont> wgrant: so... once I roll out 70 (which looks to be tomorrow morning my time), you'll be able to switch things around... how do you propose making sure that a 32-bit installed x86 box doesn't ever get to try to be an amd64 builder?
[23:31] <lamont> or is that just something that we know?
[23:32] <wgrant> lamont: LP doesn't know at the moment. Once I teach LP about processor compatibility, you'll just leave it set as its real arch.
[23:33] <wgrant> But until then, I'd keep the real arch in the display name.
[23:33] <lamont> makes sense
[23:33] <wgrant> I mean, they shouldn't really need to be moved around too much.
[23:34] <wgrant> So that shouldn't be toooo bad.
[23:38] <lamont> true
[23:47] <wgrant> lamont: So, once Soyuz does ddebs, is there any reason to have primary build on separate builders?
[23:47] <lamont> primary as in main arch?
[23:47] <lamont> main archive
[23:47] <wgrant> Yeah.
[23:48] <lamont> 1) somethings misbehave under xen.  2) no xen support for some architectures.  3) history
[23:48] <lamont> as in "the weight of"
[23:48] <lamont> 4) ppa abuse vs the distro
[23:49] <wgrant> 1) Hm, really? Still?
[23:49] <wgrant> 2) Well, yes, but we already have "virt" armel builders
[23:49] <wgrant> 3) Yay.
[23:49] <lamont> dunno.  I just know that some core-devs specifically have non-virtualized ppas specificially because of that
[23:49] <wgrant> 4) That's a universal scoring problem, which might be fixed soon.
[23:50] <lamont> the virt arm builders are not generally available, specifically because they are LYING
[23:50] <wgrant> Right.
[23:50] <wgrant> But they are a restricted architecture.
[23:50] <lamont> in any case, we have more main-archive builders coming online (e.g. allspice)
[23:51] <wgrant> And once we have no need for non-virt i386/amd64/lpia builders, there's no point having the virt/non-virt distinction. Everything can be done through the restricted architecture handling.
[23:51] <lamont> http://paste.ubuntu.com/483145/ <-- speaking of allspice... WTF is that?
[23:52] <wgrant> Um.
[23:52] <wgrant> What is its status?
[23:54] <lamont> it was aborted when  I noticed it
[23:54] <lamont> which was a few exceptions later.
[23:54] <lamont> I've restarted it to see if it falls over again
[23:54] <wgrant> I wonder why it tried to dispatch, then.
[23:54] <wgrant> Also, aborted builder handling landed yesterday.
[23:54] <wgrant> So it should handle that soon.
[23:54] <lamont> oh, nice
[23:54] <lamont> into lp-buildd, or?
[23:55] <wgrant> buildd-manager.
[23:55] <lamont> anyway, that was shortly after I added the builder, so I think there might be a startup edge condition?  dunno
[23:55] <wgrant> So it will notice that the builder is aborted and clean it up. Rather than leaving it sitting for weeks.
[23:55] <wgrant> Hm. Odd.