Pikkachu | hi, is it possible to create a recipe for an specific revision of a branch? | 08:25 |
---|---|---|
Pikkachu | hi, I thought creating a recipe would easily create a deb and put it onto a ppa | 09:56 |
Pikkachu | in 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 | ||
shnatsel | Hello! 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.gz | 16:36 |
Pikkachu | I'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 |
Pikkachu | I have a modified pidgin plugin in a branch but for compiling it you need to do it under pidgin-source/pidgin/plugins directory | 16:39 |
Pikkachu | you need $apt-get build-dep pidgin for that, and pidgin's source code. So I wonder how to put this in the recipe | 16:40 |
Pikkachu | Also, I wonder if it's not possible to the recipe to just create the deb metafiles on the fly | 16:40 |
shnatsel | Pikkachu: metafiles? | 16:40 |
Pikkachu | shnatsel: 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 about | 16:45 |
Pikkachu | shnatsel: you mean I will put build instructions within deb metafiles? ok but I don't know how to do that | 16:46 |
shnatsel | Pikkachu: I don't know what you mean by metafiles, but by what you describe I see the folliwing solutions: | 16:48 |
shnatsel | Pikkachu: extract the build dependencies from pidgin's debian/control and put it in yours debian/control; that will solve apt-get build-dep | 16:49 |
shnatsel | Pikkachu: nest or nest-part the parts of Pidgin source code you need | 16:49 |
shnatsel | Pikkachu: looking at how existing plugins are packaged also might be a good idea | 16:49 |
shnatsel | I 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 |
Pikkachu | it's not the best if it's complicated, but ok | 16:58 |
Pikkachu | ok 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 |
shnatsel | AFAIK there's no easy way to do it, but I'm not an expert | 17:00 |
Pikkachu | I 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 source | 17:00 |
Pikkachu | I mean, it's necessary to at least ./configure pidgin itself | 17:01 |
shnatsel | I'd look at existing packaging for plugins if I were you | 17:02 |
Pikkachu | ok thanks anyway | 17:05 |
Pikkachu | but they likely are not using recipes or PPAs | 17:05 |
shnatsel | Pikkachu: anything that builds as-is will build in recipe and PPA too | 17:07 |
Ampelbein | Pikkachu: For building pidgin plugins, doesn't libpurple-dev have the required headers? | 17:30 |
Pikkachu | Ampelbein: only headers are not enough | 17:33 |
Ampelbein | Pikkachu: What is the plugin you are trying to package? | 17:34 |
Pikkachu | at least iirc I couldn't build pidgin or purple-plugin-pack wihtout having their lot of build-deps installed | 17:35 |
Pikkachu | Ampelbein: what do you mean type? | 17:35 |
Ampelbein | Pikkachu: The name. | 17:36 |
Pikkachu | Ampelbein: the name is "IRC Away", @@? | 17:37 |
Pikkachu | Ampelbein: you mean the ID? | 17:37 |
Ampelbein | Pikkachu: 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 |
Pikkachu | Ampelbein: yeah they usually don't, but pidgin website doesn't provide guidelines for building the plugins without at least ./configuring pidgin | 17:38 |
Ampelbein | Pikkachu: I mean the name of the plugin you are trying to build. And preferably it's homepage. | 17:39 |
Pikkachu | Ampelbein: it has no homepage, I am the author | 17:39 |
Ampelbein | Pikkachu: Ok. Can you give a link to the file? | 17:39 |
Pikkachu | https://code.launchpad.net/~renatosilva/pidgin/ircaway | 17:41 |
Pikkachu | windows and linux builds here: http://developer.pidgin.im/ticket/11483 | 17:41 |
=== Pikkachu is now known as Pikkachu^Away | ||
=== yofel_ is now known as yofel | ||
Ampelbein | !away | Pikkachu^Away | 17:50 |
ubot5 | Pikkachu^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 | ||
rebel | I 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 |
rebel | who can I set as maintainer if a project is not currently being maintained? | 18:44 |
lifeless | click on the edit link beside the maintainer, and you can disavowe it | 18:46 |
rebel | I can only select a new maintainer | 18:46 |
lifeless | it should have an option there to say you don't want to maintain it anymore | 18:51 |
lifeless | maybe on the admin page | 18:52 |
lifeless | failing that, tell me the project name | 18:52 |
rebel | horde3d | 18:52 |
lifeless | so, you may not know this, but the project has no bearing on PPA builds | 18:58 |
lifeless | we could just deactivate it | 18:58 |
lifeless | That said, I will get a sysadmin to hand it over to registry when one turns up (in a few hours) | 18:58 |
rebel | I wasn't able to do a source import without there being a project first | 18:59 |
lifeless | ah, so not PPA; source import. | 18:59 |
lifeless | yes, you do need it for that | 18:59 |
rebel | what I'm trying to accomplish is supplying a launchpad-ppa-hosted, locally built package for Horde3D | 19:02 |
rebel | so 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 |
Pikkachu | hi, 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 |
Pikkachu | https://launchpad.net/~renatosilva/+archive/ppa | 19:04 |
lifeless | Pikkachu: only you can see it, you can see your own deleted ppas. | 19:04 |
lifeless | rebel: that sounds fine | 19:05 |
lifeless | rebel: you can also use a recipe to automate the PPA build step | 19:05 |
rebel | thanks lifeless, also for turning the project over to registry | 19:05 |
Pikkachu | if 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 |
lifeless | Pikkachu: you can undelete it yourself; why do you say it is unrecoverable ? | 19:07 |
Pikkachu | I didn't see a link, let me try again | 19:10 |
Pikkachu | I can't see any link for recovery anywhere | 19:11 |
lifeless | 'change details' -> enabled + publish | 19:23 |
Pikkachu | thanks lifeless, https://launchpad.net/~renatosilva/+archive/ppa | 19:33 |
Pikkachu | I had to manually add '+edit' though, there wasn't any edit link | 19:33 |
Pikkachu | there is not, still http://i.imgur.com/NeMUi.png | 19:34 |
lifeless | Pikkachu: not what? | 19:36 |
Pikkachu | there is not an edit link, I posted a screenshot | 19:37 |
lifeless | thats unusual | 19:37 |
lifeless | not sure why | 19:37 |
Pikkachu | ok so thanks for helping :) | 19:39 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!