[02:02] <Grom> hello
[02:02] <Grom> is possible to make private branch on launchpad?
[02:08] <jmarsden> Grom: Well,   bzr push lp:~grom/+junk/my-private-branch   #  will create your own branch, but it will be visible to others... how "private" do you need?  if 100% private, just keep the repo on your own local machine :)
[03:00] <darkvertex> Hi, I made a translation team called "Launchpad Indonesian Translators" in launchpad a while back. Could it possibly be added to https://translations.launchpad.net/+groups/launchpad-translators/ ? What is the correct procedure?
[03:01] <darkvertex> This id the link: https://launchpad.net/~lp-l10n-id
[03:05] <jmarsden> darkvertex: I would suggest you email rosetta@launchpad.net and ask them to add your team
[03:06] <darkvertex> jmarsden: thank you for your prompt reply. will do as you suggested
[10:58] <didrocks> hey launchpad guys
[10:58] <didrocks> I got some error in staging when using my credential (I don't have this error in edge)
[10:59] <didrocks> so, it seems that the launchpad API binding is broken right now on staging
[13:37] <crevette> hello
[13:39] <crevette> I've put a package to my ppa, and I don't know why soyuz tries to upload then after, and off course it fails
[13:40] <crevette> ... a package to build in my ppa ...
[13:46] <cody-somerville> crevette, Its attempting to upload the binary packages not the source package again. Its a known bug in launchpad that occurs intermittently.
[13:47] <crevette> hey cody-somerville
[13:47] <cody-somerville> crevette, Can you provide a link to the build results page for the package?
[13:47] <crevette> yep of course,
[13:47] <crevette> https://edge.launchpad.net/~bmillemathias/+archive/ppa/+build/1064180
[13:49] <cody-somerville> crevette, ah
[13:49] <cody-somerville> crevette, This is a different matter.
[13:50] <cody-somerville> crevette, You can't upload an older version of a package to a PPA for a series even if you've deleted the newer version.
[13:51] <crevette> ah, is itn't to be superseded by default?
[13:51] <crevette> hmmm, I don't have any other bluez package for jaunty
[13:52] <cody-somerville> crevette, You did.
[13:52] <crevette> yeah
[13:52] <crevette> I had one
[13:53] <cody-somerville> You need to upload a version higher than 4.37-0ubuntu1 for it to be accepted to Jaunty in your PPA.
[13:53] <cody-somerville> https://edge.launchpad.net/~bmillemathias/+archive/ppa?field.name_filter=bluez&field.status_filter=any&field.series_filter=jaunty
[13:54] <crevette> cody-somerville: but I need to test a patch for 4.32, in order to know to be tested by jaunty users
[13:54] <crevette> aaaaaah
[13:54] <crevette> okay understand
[13:55] <cody-somerville> :)
[13:55] <cody-somerville> I believe the current workaround is to create a new PPA.
[13:55] <crevette> okay, this is true now I can haz more ppa
[13:57] <crevette> thanks cody-somerville
[13:57] <cody-somerville> crevette, My pleasure :)
[13:59] <crevette> thanks for the support on sunday
[13:59] <crevette> :)
[14:09] <huayra> hello I want to upload a totally new branch into an existing project (branch would be "drupal6-devel" and project "spreadubuntu")
[14:10] <huayra> should I just push it as indicated here: https://help.launchpad.net/Code/UploadingABranch#Registering%20your%20branch%20in%20Launchpad
[14:10] <huayra> ?
[14:11] <cody-somerville> huayra, That should work, yup.
[14:11] <huayra> thx :)O
[14:11] <cody-somerville> huayra, If you paste in what command you're going to type before you do I can explain to you where exactly the branch will show up if you're uncertain.
[14:13] <huayra> ok, I am now putting everything I am going to upload in the directory I want to commit
[14:13] <huayra> I'll paste it here before pressing enter :)
[14:53] <huayra> hi cody-somerville myline would be something like: "bzr push lp:~spreadubuntu/spreadubuntu/devel-drupal6 --use-existing-dir
[14:53] <huayra> "
[14:53] <huayra> am I right?
[14:54] <cody-somerville> huayra, Are you a member of the spreadubuntu team?
[14:55] <huayra> yes
[14:55] <cody-somerville> huayra, Looks good
[14:55] <cody-somerville> huayra, You probably don't really need --use-existing-dir unless you registered the branch via the UI first
[14:55] <huayra> which I did
[14:56]  * cody-somerville nods.
[14:56] <cody-somerville> Looks like you're good to go!
[14:56] <huayra> but how do I mark the files to be pushed?
[14:56] <cody-somerville> :)
[14:56] <huayra> I have not done anything else than installing bzr where I am developing, login in and now I want to push
[14:56] <huayra> I have use SVN, but BZR is practically a total stranger to me
[14:57] <cody-somerville> huayra, Luckily, if you've used SVN then a lot of the commands you learnt for SVN actually work in bzr in the way you might suspect.
[14:57] <cody-somerville> huayra, To get started, you need to type 'bzr init' in the root/top level directory of your project.
[14:58] <huayra> ok, here we go :)
[14:59] <cody-somerville> huayra, Next you'll do 'bzr add' which will recursively add all your project's files to your new branch.
[14:59] <huayra> even directories?
[14:59] <cody-somerville> huayra, Yes.
[14:59] <huayra> add, just like in svn
[14:59] <huayra> :)
[15:00] <huayra> it tells me that it ignored 3 files... BUt I can't see which files
[15:01] <Nafallo> bzr ignored
[15:01] <cody-somerville> :)
[15:02] <huayra> hehe
[15:02] <cody-somerville> huayra, You can also type 'bzr status' to review all the files it *did* add. If after reviewing 'bzr status' and 'bzr ignored' you're happy, then its time to do your first commit.
[15:02] <huayra> I feel like a n00b (still this far easier than git)
[15:03] <cody-somerville> huayra, To do your first commit, type something similar to the following: bzr commit -m "Initial commit"
[15:04] <cody-somerville> huayra, The -m "Initial commit" after bzr commit is just a shortcut to specifying the commit message. If you had just typed 'bzr commit' then bzr would have opened an editor for you to write your commit message.
[15:04] <huayra> just like svn :)
[15:05] <huayra> ah, ok
[15:05] <huayra> but I do that before pushing, right?
[15:05] <huayra> does commit make the push as well?
[15:05] <Nafallo> no
[15:06] <Nafallo> well
[15:06] <Nafallo> no unless you have a lightweight branch
[15:06] <huayra> ok so I write the commit -m message and then do the push as described above, right?
[15:07] <cody-somerville> huayra, Thats correct. :)
[15:08] <Ampelbein> hi. i get an oops (OOPS-1254EB286) trying to add a bugwatch to bug 357761.
[15:09] <huayra> cody-somerville and Nafallo thank you very much for your help :)
[15:09] <cody-somerville> huayra, No problem! :)
[15:09] <huayra> you guys rock!
[15:10] <Nafallo> :-)
[15:12] <cody-somerville> Ampelbein, You've found a bug.
[15:13] <Ampelbein> cody-somerville: ok, so i report this on https://bugs.launchpad.net/launchpad ? Or directly to project malone?
[15:13] <cody-somerville> Ampelbein, Directly to project malone
[15:13] <Ampelbein> cody-somerville: ok, thanks.
[15:15] <cody-somerville> Ampelbein, If ever in doubt though, file against launchpad. In this case, we're confident enough that its a malone bug.
[15:17] <Ampelbein> thanks again.
[15:21] <Ampelbein> cody-somerville: bug 384513 filed. is there anymore information i should include?
[15:22] <cody-somerville> Ampelbein, No, thats great.
[15:32] <cody-somerville> Ampelbein, It appears that the remote bug tracker information for the viking project isn't correct/valid.
[18:14] <hscdude> hi
[18:14] <hscdude> bugs.launchpad.net uses an invalid security certificate.
[18:14] <hscdude> The certificate is not trusted because the issuer certificate has expired.
[18:14] <hscdude> The certificate will not be valid until 05/08/2009 05:05 PM.
[18:14] <hscdude> what is that
[18:15] <hscdude> it seems to be true only for some people
[18:15] <hscdude> is there some random auto ballancing?
[18:15] <cody-somerville> hscdude, I don't get that error.
[18:16] <hscdude> \well I get it all the time
[18:21] <hscdude> I was in middle of debugging  wakup using CMOS clock magic.  didnt corrected my clock yet lol. n/m
[18:27] <Ampelbein> cody-somerville: re. thanks for looking into bug 384513. After your investigation it now seems to be the same as bug 370117.
[18:34] <EricHerman> Can someone help me break a lock on launchpad?
[18:37] <EricHerman> I see this: http://pastebin.com/d12586552 I see a 'bzr suggests wrong URL for break-lock with a LP hosted branch' bug on this ( https://bugs.launchpad.net/bzr/+bug/250451 ) but I don't see how to work around it.
[18:38] <EricHerman> oh, geeze, I read *right* past it.
[18:39] <EricHerman> illiteracy strikes again
[18:39] <EricHerman> thank you.
[19:47] <hggdh> heh
[22:28] <zsquareplusc> i condsider to register a small project on launchpad, but i wonder what the idea is for project docs. launchpad doesn't seem to offer a place where i can publish a readme (with linked images)?
[22:32] <thumper> zsquareplusc: not right now
[22:44] <Bodsda> Hi, how do I add a jey for someones ppa on ubuntu? I looked at the link provided on launchpad and it says (in a terminal) to add the fingerprint that looks like this "B0BE17C2A0C914F086B7B8327D2C7A23BF810CD5" and then gives an example of an awn testing ppa, but I cant find this fingerprint thing anywhere - I can only fin the whole public key block
[22:46] <mwhudson> Bodsda: it's on the page for the ppa you're adding, i think?
[22:48] <mwhudson> or rather, it's on the page you get after you click the shorter hash
[22:48] <mwhudson> Bodsda: which ppa are you trying to add?
[22:48] <Bodsda> mwhudson: this is the ppa im trying to add --  https://launchpad.net/~andrewfenn/+archive/ppa -- the only thin i can find is this:  1024R/6FED7057   but its a link to his whole public key
[22:48] <mwhudson> ah right
[22:48] <mwhudson> well when it says
[22:48] <mwhudson> Search results for '0xe1ba1ac8f1cea356be76dab5b7a1545c6fed7057'
[22:48] <mwhudson> the key is e1ba1ac8f1cea356be76dab5b7a1545c6fed7057
[22:49] <Bodsda> mwhudson: oh, after the 0x -- they didnt mention that
[22:49] <Bodsda> mwhudson: brilliant, cheers
[22:49] <mwhudson> it's a bit unclear, yes
[22:49] <mwhudson> Bodsda: np
[22:50] <days_of_ruin_> http://www.sourcecode.de/content/some-internals#comment-3710
[22:51] <days_of_ruin_> has anyone gotten this to work on jaunty ;_;