/srv/irclogs.ubuntu.com/2012/03/04/#launchpad.txt

Pikkachuhi, is it possible to create a recipe for an specific revision of a branch?08:25
Pikkachuhi, I thought creating a recipe would easily create a deb and put it onto a ppa09:56
Pikkachuin this process I've created a PPA which can't either be deleted completely or superseded. Can anyone delete it completely for me?09:57
=== Pikkachu is now known as Pikkachu^Away
=== Pikkachu^Away is now known as Pikkachu
=== Quintasan_ is now known as Quintasan
shnatselHello! I'm having trouble with Launchpad recipes. I'm trying to apply a trivial patch to packaging of qt4-x11 in a recipe to get the most recent version patched and uploaded to PPA automatically, but bzr gives me a memory error. Is there anything I can do about it? Here's the build log: https://launchpadlibrarian.net/95276071/buildlog.txt.gz16:36
PikkachuI'm having trouble with recipes and PPAs too. I took a look at the docs which are complicated, so I ask in the simpler form:16:37
PikkachuI have a modified pidgin plugin in a branch but for compiling it you need to do it under pidgin-source/pidgin/plugins directory16:39
Pikkachuyou need $apt-get build-dep pidgin for that, and pidgin's source code. So I wonder how to put this in the recipe16:40
PikkachuAlso, I wonder if it's not possible to the recipe to just create the deb metafiles on the fly16:40
shnatselPikkachu: metafiles?16:40
Pikkachushnatsel: the docs on recipes, PPAs and packaging are confusing, I would just know how to build a deb with random content, what are you talking about16:45
Pikkachushnatsel: you mean I will put build instructions within deb metafiles? ok but I don't know how to do that16:46
shnatselPikkachu: I  don't know what you mean by metafiles, but by what you describe I see the folliwing solutions:16:48
shnatselPikkachu: extract the build dependencies from pidgin's debian/control and put it in yours debian/control; that will solve apt-get build-dep16:49
shnatselPikkachu: nest or nest-part the parts of Pidgin source code you need16:49
shnatselPikkachu: looking at how existing plugins are packaged also might be a good idea16:49
shnatselI agree Ubuntu packaging has a steep learning curve, and ubuntu packaging manual is a TL;DR which doesn't help solve real problems anyway. Unfortunately, packaging is complicated, and Ubuntu's way to do it is one of the best, if not the best.16:52
Pikkachuit's not the best if it's complicated, but ok16:58
Pikkachuok I got the build-dep, but it's a long list, can't I just joint to pidgin? something like 'Build-Dependencies: bd1 bd2 lookup:pidgin bd3...'16:59
shnatselAFAIK there's no easy way to do it, but I'm not an expert17:00
PikkachuI have no idea how to figure out which parts of pidgin's source I'd need to compile the plugin, so is it ok to just use the whole pidgin source17:00
PikkachuI mean, it's necessary to at least ./configure pidgin itself17:01
shnatselI'd look at existing packaging for plugins if I were you17:02
Pikkachuok thanks anyway17:05
Pikkachubut they likely are not using recipes or PPAs17:05
shnatselPikkachu: anything that builds as-is will build in recipe and PPA too17:07
AmpelbeinPikkachu: For building pidgin plugins, doesn't libpurple-dev have the required headers?17:30
PikkachuAmpelbein: only headers are not enough17:33
AmpelbeinPikkachu: What is the plugin you are trying to package?17:34
Pikkachuat least iirc I couldn't build pidgin or purple-plugin-pack wihtout having their lot of build-deps installed17:35
PikkachuAmpelbein: what do you mean type?17:35
AmpelbeinPikkachu: The name.17:36
PikkachuAmpelbein: the name is "IRC Away", @@?17:37
PikkachuAmpelbein: you mean the ID?17:37
AmpelbeinPikkachu: And yes, to build pidgin you'd need it's build-deps. But plugins usually don't require a full rebuild of their host software.17:37
PikkachuAmpelbein: yeah they usually don't, but pidgin website doesn't provide guidelines for building the plugins without at least ./configuring pidgin17:38
AmpelbeinPikkachu: I mean the name of the plugin you are trying to build. And preferably it's homepage.17:39
PikkachuAmpelbein: it has no homepage, I am the author17:39
AmpelbeinPikkachu: Ok. Can you give a link to the file?17:39
Pikkachuhttps://code.launchpad.net/~renatosilva/pidgin/ircaway17:41
Pikkachuwindows and linux builds here: http://developer.pidgin.im/ticket/1148317:41
=== Pikkachu is now known as Pikkachu^Away
=== yofel_ is now known as yofel
Ampelbein!away | Pikkachu^Away17:50
ubot5Pikkachu^Away: Please do not use noisy away messages and nicks in Ubuntu channels. It is annoying and unnecessary. Use the command "/away <reason>" to set your client away silently. See also «/msg ubottu Guidelines»17:50
=== Pikkachu^Away is now known as Pikkachu
rebelI just created a launchpad project to create a ppa i can link to it, and apparently I forgot to check the "I don't want to be the maintainer" checkbox - now I'm the maintainer.18:43
rebelwho can I set as maintainer if a project is not currently being maintained?18:44
lifelessclick on the edit link beside the maintainer, and you can disavowe it18:46
rebelI can only select a new maintainer18:46
lifelessit should have an option there to say you don't want to maintain it anymore18:51
lifelessmaybe on the admin page18:52
lifelessfailing that, tell me the project name18:52
rebelhorde3d18:52
lifelessso, you may not know this, but the project has no bearing on PPA builds18:58
lifelesswe could just deactivate it18:58
lifelessThat said, I will get a sysadmin to hand it over to registry when one turns up (in a few hours)18:58
rebelI wasn't able to do a source import without there being a project first18:59
lifelessah, so not PPA; source import.18:59
lifelessyes, you do need it for that18:59
rebelwhat I'm trying to accomplish is supplying a launchpad-ppa-hosted, locally built package for Horde3D19:02
rebelso my thinking was to let launchpad sync to the svn, sync locally to launchpad with bzr, build locally + push to ppa.. is this how it should be done?19:04
Pikkachuhi, I have source code I wanted to make easily available for end users then I tried the recipes link, the failed process created a PPA which I deleted, but it's still visible from my start page, and it's not recoverable as stated in docs. Can one either recover it (is "ppa" a good PPA name?) or delete it completely?19:04
Pikkachuhttps://launchpad.net/~renatosilva/+archive/ppa19:04
lifelessPikkachu: only you can see it, you can see your own deleted ppas.19:04
lifelessrebel: that sounds fine19:05
lifelessrebel: you can also use a recipe to automate the PPA build step19:05
rebelthanks lifeless, also for turning the project over to registry19:05
Pikkachuif ppa is a good ppa name (I find ppa:foo/ppa odd), I wanted it available in the future, besides I was seduced for the recipes link, my fail but that's a wrong deletion (it should not exist at all) :(19:06
lifelessPikkachu: you can undelete it yourself; why do you say it is unrecoverable ?19:07
PikkachuI didn't see a link, let me try again19:10
PikkachuI can't see any link for recovery anywhere19:11
lifeless'change details' -> enabled + publish19:23
Pikkachuthanks lifeless, https://launchpad.net/~renatosilva/+archive/ppa19:33
PikkachuI had to manually add '+edit' though, there wasn't any edit link19:33
Pikkachuthere is not, still http://i.imgur.com/NeMUi.png19:34
lifelessPikkachu: not what?19:36
Pikkachuthere is not an edit link, I posted a screenshot19:37
lifelessthats unusual19:37
lifelessnot sure why19:37
Pikkachuok so thanks for helping :)19:39

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!