=== graber1 is now known as graber | ||
=== graber1 is now known as graber | ||
guruprasad | If I want to backport a package in a PPA and that build-depends on another package which also needs to be backported to the same series, do I need to upload the dependency package to a separate PPA, have the main package to another PPA which depends on the separate PPA? Launchpad doesn't allow a PPA to depend on itself, unfortunately. :( | 14:11 |
---|---|---|
guruprasad | 's/have the/upload the/g' | 14:12 |
guruprasad | There might be good reasons for Launchpad not allowing a PPA to depend on itself, but I don't know what they are. | 14:12 |
RikMills | guruprasad: if I understand your question, you would put both in the same PPA. If a PPA has a newer version of a dependency than in the archive or another PPA that it depends on, then that higher version in the original PPA will be used for the build | 14:36 |
RikMills | i.e. PPAs sort of depend on themselves by default in that sense | 14:36 |
guruprasad | RikMills, thanks! I think this explanation makes sense but I couldn't find any reason in the Launchpad codebase. That is why I asked :) | 14:39 |
guruprasad | If what you have mentioned is the current behaviour, it will be helpful to mention that in the error message that shows up when trying to add PPA as a dependency to itself. | 14:41 |
guruprasad | I will make a note of this and propose an enhancement to the current message. | 14:41 |
RikMills | guruprasad: that is just how apt archives work at a basic level. a PPA is one after all. I guess it doesn't need to be in LP code, as it is assumed | 14:41 |
RikMills | guruprasad: yeah, that would be good | 14:41 |
guruprasad | Yeah, unfortunately most of the current Launchpad team are just Launchpad developers and do not have a lot of Ubuntu/Debian context or knowledge to use. | 14:42 |
guruprasad | We are learning on the go. | 14:42 |
RikMills | that is fair :) | 14:42 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!