Обсуждение: plv8 and pg_buildext
Hello, I've recently been using pg_buildext to template control.in files, and it's pretty great. However, I did run into this problem with plv8 and its generated control file, with the practical consequence being that it seems that the plv8 debian package cannot really support building for several postgresql versions at the same time (at least, it wouldn't when I submitted to a launchpad), being saved by "supported-versions" *only* possessing 9.3 in current Debian/Trusty. I did get around this by finding this helpful thread reporting the same bug: http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/2013-May/001197.html I applied a workaround seen in that thread and copied a modified pg_buildext (without srcdir=$srcdir) into "debian/" and it worked like a charm, I think: http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/2013-May/001233.html However, as evidenced by that response, it was somehow sub-ideal. This workaround works for my own packages (I want plv8 for 9.2), but I thought I'd re-raise that come 9.4 this may be a problem and caused some grief in at least one instance. Cheers.
Re: Daniel Farina 2014-04-22 <CAAZKuFY=4JX3OMczri5kraJw40d0x55ffNme59QQBEG_LrcuuA@mail.gmail.com> > Hello, > > I've recently been using pg_buildext to template control.in files, and > it's pretty great. However, I did run into this problem with plv8 and > its generated control file, with the practical consequence being that > it seems that the plv8 debian package cannot really support building > for several postgresql versions at the same time (at least, it > wouldn't when I submitted to a launchpad), being saved by > "supported-versions" *only* possessing 9.3 in current Debian/Trusty. > > I did get around this by finding this helpful thread reporting the same bug: > > http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/2013-May/001197.html > > I applied a workaround seen in that thread and copied a modified > pg_buildext (without srcdir=$srcdir) into "debian/" and it worked like > a charm, I think: > > http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/2013-May/001233.html > > However, as evidenced by that response, it was somehow sub-ideal. > > This workaround works for my own packages (I want plv8 for 9.2), but I > thought I'd re-raise that come 9.4 this may be a problem and caused > some grief in at least one instance. Why don't you just use the packages on apt.postgresql.org? postgresql-9.3-plv8 - Procedural language interface between PostgreSQL and JavaScript postgresql-9.0-plv8 - Procedural language interface between PostgreSQL and JavaScript postgresql-9.1-plv8 - Procedural language interface between PostgreSQL and JavaScript postgresql-9.2-plv8 - Procedural language interface between PostgreSQL and JavaScript That's for trusty and many other dists. The problems mentioned in these posts have long been fixed in newer postgresql-common versions. Christoph -- cb@df7cb.de | http://www.df7cb.de/
On Mon, Apr 21, 2014 at 3:14 PM, Christoph Berg <cb@df7cb.de> wrote: > Why don't you just use the packages on apt.postgresql.org? > > postgresql-9.3-plv8 - Procedural language interface between PostgreSQL and JavaScript > postgresql-9.0-plv8 - Procedural language interface between PostgreSQL and JavaScript > postgresql-9.1-plv8 - Procedural language interface between PostgreSQL and JavaScript > postgresql-9.2-plv8 - Procedural language interface between PostgreSQL and JavaScript > > That's for trusty and many other dists. I am using that repository, but I don't see that binary. I had the same issue with launchpad which is why I proceeded to figure out how to make this backport, presuming it was intentional: # apt-get update ... Hit http://apt.postgresql.org trusty-pgdg/main amd64 Packages ... # apt-cache search plv8 postgresql-9.3-plv8 - Procedural language interface between PostgreSQL and JavaScript (no 9.2 or any other version entries) # cat pgdg.list deb http://apt.postgresql.org/pub/repos/apt/ trusty-pgdg main
Re: Daniel Farina 2014-04-22 <CAAZKuFaxPByUPffGSDspVZ2qXyNuv51951NeaMFOeBzFUGrWfA@mail.gmail.com> > I am using that repository, but I don't see that binary. I had the > same issue with launchpad which is why I proceeded to figure out how > to make this backport, presuming it was intentional: Oh, right. Somehow plv8 on trusty fell through the cracks and wasn't promoted from trusty-pgdg-testing to trusty-pgdg. I've promoted it now. Sorry I didn't spot that when I checked yesterday - a webinterface to the repository that would also include some QA pages like "packages that need promotion" is in the works, but not finished yet. Christoph -- cb@df7cb.de | http://www.df7cb.de/
On Apr 22, 2014 1:11 AM, "Christoph Berg" <cb@df7cb.de> wrote:
>
> Re: Daniel Farina 2014-04-22 <CAAZKuFaxPByUPffGSDspVZ2qXyNuv51951NeaMFOeBzFUGrWfA@mail.gmail.com>
> > I am using that repository, but I don't see that binary. I had the
> > same issue with launchpad which is why I proceeded to figure out how
> > to make this backport, presuming it was intentional:
>
> Oh, right. Somehow plv8 on trusty fell through the cracks and wasn't
> promoted from trusty-pgdg-testing to trusty-pgdg. I've promoted it
> now.
Neat, I'm looking forward to killing my package.
Thanks for all the excellent work on the pgdg repositories; I'm really able to shed a lot of effort, mostly in extensions and postgis
I also have maybe improved (well, multi version installable anyway) packages for postgres-hll I'd like to post... How might I do that?
Re: Daniel Farina 2014-04-22 <CAAZKuFbw=CeauCtvHX12kW_PjJiOTYit2Ks6gWSYfDoo9YiYFA@mail.gmail.com> > Neat, I'm looking forward to killing my package. > > Thanks for all the excellent work on the pgdg repositories; I'm really able > to shed a lot of effort, mostly in extensions and postgis Thanks. > I also have maybe improved (well, multi version installable anyway) > packages for postgres-hll I'd like to post... How might I do that? Best try to contact the maintainer to see if he's interested. I'd guess he is, because he's hanging around in our irc channel :) (#postgresql-apt on freenode) Christoph -- cb@df7cb.de | http://www.df7cb.de/