[00:18] how do you make your branch private? [00:18] dark_soul1: Unless your project has been configured to allow it (normally only for commercial subscriptions), only an admin can do that. [00:18] wgrant: ah [00:19] wgrant: i'm just a simpleton who is using launchpad to do my personal projects :D [00:19] i like launchpad and bzr combo [00:20] Launchpad's only free to use for open source projects. [00:21] wgrant: fair enough [00:22] wgrant: do you know why we start of with a branch?..where's the trunk? [00:23] dark_soul1: Trunk is a branch. [00:23] wgrant: i see..so when your branching ..your branching of a branch? [00:24] dark_soul1: Yes. [00:24] Is there a problem with that? [00:24] then why not call that branch a trunk? [00:24] nothing wrong with it.. [00:24] just semantics [00:24] trunk is special only because it is called trunk. [00:24] yes but follows logic [00:24] It is only socially special; not technically so. [00:24] i agree [00:25] dark_soul1: you can call a branch trunk if it makes you feel better :) [00:25] but when conversing its easier to say trunk, than to say, the "main" branch [00:25] bzr push lp:~USERNAME/PROJECT/trunk [00:25] dark_soul1: Then give the main branch the name 'trunk'. [00:25] well on launchpad its called Branch [00:25] for your projects [00:25] If you set the branch as the development focus of your project, it can then be accessed simply as 'lp:PROJECT' [00:26] dark_soul1: bzr (and most other DVCSes, I believe) call everything a branch. [00:26] i've used svn and the main branch is refered to as a trunk [00:27] afaik [00:27] its no big deal [00:27] i'm just curious [00:27] Subversion doesn't have any concept of branching. [00:28] It can merely copying a subtree to another arbitrary subtree. [00:28] Any naming conventions are just that -- unenforced conventions [00:28] wgrant: will the karma earned over the time the script hasn't been running be still noted? [00:28] kobrien: Yep. It's all recorded in the DB -- the number just hasn't been recalculated yet. [00:29] wgrant: cool, thanks [00:29] yes...there are many methodologies, one of which is that trunk is always active and is not stable..when your a bout to perform a release you branch of a trunk [00:29] under that methodology, if you say branch of a branch it can get confusing [00:30] I branch off branches all the time -- not just trunk. [00:31] You are free to not call trunk a branch. [00:31] But it technically is in a DVCS. [00:31] ok :) [00:41] i look forward to my karma score :) [01:04] Hmm.. when did LP started keeping package upload details? [01:05] I'm looking for details about a dapper package uploaded 24 Jan 2006.. but it's not where i would expect [01:05] Daviey: Late February 2006. [01:06] hah, typical [01:06] Before that Ubuntu was managed in dak, not LP. [01:06] So LP only has the latest packages from each release before that date. [01:06] wgrant: and them logs don't exist anymore? [01:07] Daviey: Probably not. Which package? [01:07] wgrant: vnc4 [01:07] (it looks like it was actually the 30th of January!) [01:07] * wgrant tries to find the email. [01:07] i was expecting https://edge.launchpad.net/ubuntu/+source/vnc4/4.1.1-0ubuntu [01:08] Hm, yes, ubuntu1 to ubuntu3 are missing. [01:10] wgrant: sorry, i dropped the 1 from the url paste [01:10] still 404 [01:10] ahh well, thanks wgrant [01:10] Daviey: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/dapper/vnc4/dapper/changes suggests that even distro folks can't retrieve ancient versions. [01:10] So they are probably really gone. [01:11] Daviey: The migration finished on 2006/02/04. [01:11] vnc4 (4.1.1-0ubuntu1) dapper; urgency=low * Unknown changes -- Bjoern Brauel Tue, 24 Jan 2006 01:01:03 +0200 <-- awesome eh? :) [01:11] Nice. [01:12] I remember trying to deal with that page three or so years ago. [01:12] It was endless pain and suffering. [01:12] Sync it if you can. [01:12] Er, s/page/package/ === MTecknology is now known as MTeck-ricer [03:48] Is there any special steps to adding a software source directly in /etc/apt/sources.list? I get errors doing so, I'm wondering if it needs the key or something. [03:49] Muscovy: You need a key. But why not use the automated tools (add-apt-repository or Software Sources)? [03:50] I'm working on a live cd, and if memory serves, add-apt-repository isn't a default install. [03:53] It is. [03:53] Muscovy: it should be installed by default [03:53] I'll test, then. [03:53] and the package manager is certainly installed, so you could just use that [03:54] Ok, thanks, I can just do that. [03:54] * wgrant proposes to remove add-apt-repository from Lucid, and just include it in a PPA. === collinp is now known as Easter_Bunny [08:35] wgrant: do you have an idea what might have caused the both "Failed to upload" on amd64? I guess I have to wait on someone who can look at those OOPS-IDs [08:35] https://lp-oops.canonical.com/oops.py/?oopsid=IDs [08:43] geser: Yeah, we need any Canonicalite to look at the OOPSes. [08:45] what oops [08:45] OOPS-1553FTPMASTER11 and OOPS-1553FTPMASTER16 [08:45] https://lp-oops.canonical.com/oops.py/?oopsid=1553FTPMASTER11 [08:45] https://lp-oops.canonical.com/oops.py/?oopsid=1553FTPMASTER16 [08:46] Hopefully the syncing is working OK. [08:46] It wasn't working from cocoplum a few weeks ago. [08:46] 1553FTPMASTER16 didn't match any oops [08:47] What about 11? [08:48] It would be odd if one worked but not the other. [08:48] neither [08:49] Damn, must be still broken. [08:49] Thanks for trying. [08:49] We need somebody to actually grab them off cocoplum, which probably means waiting for a LOSA on Monday or Tuesday. [08:51] (that probably also means that the other 14 (at least) cocoplum OOPSes from that day have gone unnoticed [08:51] This is probably bad. [09:17] wgrant: file a bug [09:17] or actually [09:17] ask a question [09:17] or both [09:18] I think I saw a bug about cocoplum log syncing. But I cannot now see it. [09:20] hi [09:20] I've just seen that launchpad has a new login method. could somebody tell me how can I simulate a login with curl or better wget, please? [09:21] sianis: I don't think anyone knows [09:21] sianis: Is there a reson that you cannot use the Launchpad API? [09:21] you need to emulate openid / oauth [09:22] wgrant, can I send po export request with the api? [09:23] sianis: It appears not. But if you report a bug asking for it, it will likely soon become possible. [09:23] the old method was: sending name and password with post method to the login.lp.net and saving the cookie. with this cookie I could send request ... this was so simple [09:24] Otherwise, give curl or wget a cookie rather than a username and password. [09:24] So: [09:25] 1) Report a bug at https://bugs.launchpad.net/rosetta/+filebug requesting that the export facility be exposed on the API. [09:25] 2) Get an authenticated cookie (they last for a year, IIRC), and give it to your curl or wget script. [09:25] 3) When the bug is fixed, use launchpadlib to solve all of your problems. [09:26] ok wgrant thank you [13:10] http://tinypic.zapto.org/2kn4m8.png?t=1270382560 do my breasts look to big? [14:45] any one can help me prob is related to database [14:45] !ask [14:45] Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) [15:13] How do I upload my source/binary packages? Apparently "if I've already got a Bazaar branch on my local machine, getting that branch up to Launchpad couldn't be easier". But this doesn't help much since I don't even know what a branch looks like. [15:13] I am reading from this help page: https://help.launchpad.net/Code/UploadingABranch [16:20] How do I create Bazaar branches on my local machine? [16:23] you branched from LP and want to branch from that? [16:51] geser: ??? [16:53] Penguin: I'm trying to understand your question [16:53] geser: I made my own package from scratch and want to upload it to Laucnhpad. The help page says I need to create a local branch first. [16:53] "If you've already got a Bazaar branch on your local machine, getting that branch up to Launchpad couldn't be easier." [16:54] - https://help.launchpad.net/Code/UploadingABranch [16:55] are you already familiar with bzr? [16:55] geser: No, this is my first package. [16:56] Penguin, are you trying to get a package into ubuntu or create your own software project? [16:57] I wrote a blobber game in python. I then debianized it. I now want to upload it to Launchpad. [16:57] to your PPA, right? [16:58] in that case you need the source package (debuild -S) and "dput" it your PPA [16:58] you don't need a branch for it unless you want that others can branch from it to work on it (e.g. to improve your packaging) [16:59] Err... [16:59] https://code.launchpad.net/~blobber/+junk/blobber [17:00] Is that a good place to put it? [17:00] Penguin, you want to use launchpad for maintaining the source pacakge? [17:00] +junk isn't a good place [17:00] there is currently no automatic way to turn a branch into a deb (but it's being worked on) [17:01] Like I said, I'm completely new to this, so I don't have a clue what I want to do. [17:01] Penguin: see https://help.launchpad.net/Packaging/PPA/Uploading for how to upload a package to your PPA (and get it build) [17:03] Okay. But this is my first version and I have no .diff.gz or .changes [17:04] Penguin: you can use LP for (upstream) codehosting (using bzr for version control, having tarballs of release available for download) and/or (it's independent from codehosting) provide debs in your PPA for a software (be it hosted on LP or somewhere else) [17:05] Penguin: those files get generated when you build the source package [17:05] who can approve imported translations in a project? [17:05] It mentions 'debuild -S -sa', whereas I used 'dpkg-buildpackage -us -uc'. Maybe this is why I am missing those files..? [17:08] not really, as debuild is a wrapper around dpkg-buildpackage [17:08] I just rebuilt it with debuild and it generated said files. [17:08] without "-S -sa" dpkg-buildpackage builds both the binary debs *and* the source package [17:10] for an upload for PPA you need to build only the source package (-S) as else also the binary debs get mentioned in the .changes files which should get uploaded [17:10] Presumably I want it to build the source package as well? [17:11] you need to upload the source package to you PPA to let it build the debs for you. So you need to build the source package. [17:11] Okay. [17:11] A source package is a .tar.gz isn't it? [17:13] yes [17:13] Because it doesn't seem to have built any source packages... [17:14] sorry, excuse that [17:14] Penguin: a source package is tar.gz + dsc + (diff.gz or debian.tar.gz) [17:15] I'm missing the .tar.gz [17:16] Penguin: build the source with -sd then [17:16] -sa, I mean [17:18] Still no .tar.gz [17:19] Penguin: aah, you need to have the .orig.tar.gz before you start, you get it from the upstream source [17:19] -sa just means include it in the upload [17:20] I have: folder, .orig.gz, .diff.gz, .dsc, .deb, .build, .changes, _source.build, _source.changes. [17:21] it sohuld be .orig.tar.gz not orig.gz [17:21] Oh, yeah, soz, it is, just missed it out in typing [17:21] I have: folder, .orig.tar.gz, .diff.gz, .dsc, .deb, .build, .changes, _source.build, _source.changes. [17:22] sounds good [17:22] So I'm not missing anything? [17:22] if it isn't uploading the .orig.tar.gz, rebuild teh source with "debuild -S -sa" [17:23] So what do I dput where? [17:23] you dput the .dsc [17:23] no the .changes [17:24] * tumbleweed needs coffee I think :) [17:24] Lol, yeah, you don't sound very sure... [17:30] "Successfully uploaded packages." === yofel_ is now known as yofel [17:30] Apparently my package has been successfully uploaded. But I can't find it = ( [17:31] Penguin, wait for sometime. LP will send you a mail [17:31] what was the exact command line you used? [17:31] dput joshbrown blobber_0.0a1-1_source.changes [17:32] I assume you have a "joshbrown" stance in your ~/.dput.cf [17:33] in that case it looks ok [17:33] do you have the gpg key you used for signing attached to your LP account? [17:33] geser: Yep [17:34] then wait some minutes. the uploads are processed every 5 minutes. [17:34] Ahh, I apparently need to create my ppa first... [17:35] disoplayname? [17:35] displayname* [17:37] I don't know what to put for displayname and description... [17:38] choose wisely as you can't change them later [17:39] What did you put for yours? [17:44] the description is empty and the displayname contains "PPA for " as I activated my PPA when it was still in beta (and only one PPA per user) [17:44] the display name ends in the gpg key used for signing the PPA [17:47] Description you can change, I believe. The bit which is immutable is that the displayname is used to set the user ID of the generated GPG key [17:48] Hi, I've uploaded a couple of po-files to LP to synchronize some translations with upstream. They have been sitting there for two days, 'approved'. Are the servers really that busy or is something wrong? [17:50] (Waiting wouldn't be much of an issue, except if everything takes days to upload, then I can't use the coloured bars to get an idea about how translations are progressing) [18:01] So displayname:'PPA for Josh Brown' and leave description blank? [18:04] for example [18:04] if you know that you want only provide packages for a specific software in that PPA you can name it accordingly [18:07] I'll just make a general PPA for now. [18:59] I've finally uploaded my first package!! [ blobber @ ppa:joshbrown/ppa ] And it works!! =D === Easter_Bunny is now known as collinp [19:31] is launchpad calculating karma correctly? It's telling me i earn lots in the answer track and not so much in bug management, but really my activities are the other way around. [19:34] my "most active in" confirms this...or do answers count as more karma? [20:59] hey, anybody know anything about the ppa's for xbmc hosted on launchapd? [20:59] *launchpad [21:00] the dependencies for lucid are broken [21:05] GrimmVarg: https://launchpad.net/~team-xbmc/+archive/ppa <- that one? [21:06] yeah [21:06] no [21:06] svn [21:06] https://launchpad.net/~team-xbmc-svn/+archive/ppa/+packages [21:07] james_w: the one you posted does not have a lucid version yet [21:07] then you need to find someone from https://launchpad.net/~team-xbmc-svn/+members [21:08] ah, okay. tnx :) [21:35] Does `lsb_release -is` on a PPA buildslave report "Ubuntu" like other systems? [21:36] I wrote a bit of code in my rules file to detect if the package was being built for Ubuntu, and the result indicated that my test must be flawed in some way. [21:37] ( http://paste.ubuntu.com/409201/ ) === MTeck-ricer is now known as MTecknology [23:41] lfaraone: There's nothing magical about the buildd chroots. [23:41] lfaraone: Are you sure lsb_release was installed? [23:42] It's in -minimal, but it's not Essential or Build-Essential.