Re: postgresql patch

I'll check it out, but I believe a correct patch is not quite as simple, it needs some tuning when installing files as well, but I may be wrong. --On 15 november 2010 17.44.27 -0800 Jason Helfman wrote: Hi, I was hoping you would be able to consider implementing this PR (ports/113707) in a

Re: FreeBSD Port: postgresql-server-8.4.8_1

13 jun 2011 kl. 20.07 skrev John Bleichert: > creating template1 database in /usr/local/pgsql/data/base/1 ... child process > was terminated by signal 12: Bad system call > initdb: removing contents of data directory "/usr/local/pgsql/data" > $ exit > boogie:/var/log uname -a > FreeBSD boogie 8.

Re: FreeBSD Port: postgresql-server-8.4.8_1

14 jun 2011 kl. 06.34 skrev John Bleichert: > > On Jun 13, 2011, at 4:31 PM, Christer Solskogen wrote: > >> On Mon, Jun 13, 2011 at 8:07 PM, John Bleichert wrote: >> >>> Suggestions? Shall I hit the postgresql forums? I thought I'd ask here >>> first. >>> >> >> This is in a jail, right? >>

Re: Question about postgresql 9 and pg_upgrade

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Rees skrev: > > On 29 Sep 2012 09:49, "Axel Rau" > wrote: >> >> >> Am 21.09.2010 um 09:15 schrieb Alexander Pyhalov: >> >>> All latest PostgreSQL ports has conflicts with earlier >>> versions. > May this be correc

Re: Question about postgresql 9 and pg_upgrade

29 sep 2012 kl. 19:43 skrev Axel Rau : > As my server itself runs in a jail, this won't work, I think. You could try just unpacking a package tarball as I suggested at the end of the mail?___ freebsd-ports@freebsd.org mailing list http://lists.freebs

Re: databases/postgresql90-{client, server, contrib} not hooked up to ports

Nope, no reason, my mistake! Thanks, I will fix that. PAlle --On 3 oktober 2010 23.28.42 +0100 Matthew Seaman wrote: Is there any reason why the 3 postgresql90 ports aren't mentioned in ${PORTSDIR}/databases/Makefile ? They seem to work perfectly well for installing postgresql-9.0.0

Re: new version of postgresql port

Hi, True, it is a first shot at breaking the 1:1 relationship, it is not a solution. I think that if you install all PostgreSQL:s in different PREFIXes, it will work to install them. As you say, they should opimtally install in their own non-conflicting places without changing prefix. Lets

Re: new version of postgresql port

--On 7 oktober 2010 15.06.37 +0200 Palle Girgensohn wrote: Hi, True, it is a first shot at breaking the 1:1 relationship, it is not a solution. I think that if you install all PostgreSQL:s in different PREFIXes, it will work to install them. or if you install in prefix first... or

Re: new version of postgresql port

different PREFIX'es at least because of bsd.databases.mk: lines 181 - 186: if we look at postgresql version in $LOCALBASE, it will be different from one from $PREFIX. Palle Girgensohn wrote: True, it is a first shot at breaking the 1:1 relationship, it is not a solution. I think that i

Re: no MAINTAINER for postgresql90-client

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jason Helfman skrev: >> * Robert Huff [Tue, 5 Jun 2012 09:53:37 -0400]: >> >>> The Makefile has no MAINTAINER line. Is this deliberate? If so, >>> why? And who do I contact about a problem building this port? >>> (Tarball doesn't fetch.) >>> >> In

Re: "make index" shows missing port directory

Chris Rees skrev: > On 8 June 2012 08:15, Alfred Bartsch wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi, >> ... >> Adding this missing entry to the portstree should solve this issue. >> To avoid such problems in the future, it would IMHO be preferable to >> have only one port

Re: postgresql 8.4

Consider me ping:ed. :-) Just got back from vacation, I'll be fixing the port tomorrow. Regards, Palle --On måndag, må 6 jul 2009 20.20.17 +0400 Dmitry Morozovsky wrote: On Mon, 6 Jul 2009, Peter Czanik wrote: PC> Hello, PC> Postgresql 8.4 was released last week. I wanted to test it, but

Re: postgresql 8.4

Bummer, I had an old WITHOUT_NLS=YES in my /etc/make.conf... If you can't wait, deselect NLS in make config. I'll look into this in the afternoon. Thanks for the heads-up. Palle --On onsdag, on 8 jul 2009 14.15.31 +0200 Peter Czanik wrote: On 2009-07-06 22:44, Palle Girgen

anyone working on an update of www/plone to 3.0.1?

Hi, www/plone needs updating. Is anyone working on it already? If not, I will. Since plone has a rather akward dependency chain, I'm looking at using the unified installer for installing plone, and hence use that for a port. Anyone else doing any work already? Zope, and hence Plone, is very

Re: anyone working on an update of www/plone to 3.0.1?

it seems hard to upgrade from zope 2.9 + plone 2.5 to zope 2.10 + plone 3.x. And, some zope/plone products depend on plone 2.x and they may not work on plone 3.x, for example, coreblog2. I'm not sure which products work or not work on plone3. In <[EMAIL PROTECTED]> Palle Girg

Re: postgresql 8.1.11 with icu 3.8: incompatible

Hi, From what I remember, I had to make it version dependent, since there where no symbols that where not verisioned. I have a look at it, though. Regards Palle --On måndag, februari 11, 2008 06.05.54 -0500 Mikhail Teterin <[EMAIL PROTECTED]> wrote: On неділя 10 лютий 2008, [EMAIL PROTECT

Re: postgresql 8.1.11 with icu 3.8: incompatible

Hi, I just committed a patch that fixes the problem. Regards, Palle --On måndag, må 11 feb 2008 06.05.54 -0500 Mikhail Teterin <[EMAIL PROTECTED]> wrote: On неділя 10 лютий 2008, [EMAIL PROTECTED] wrote: = It seems that postgresql 8.1 port's icu patch need icu <= 3.6: The patch is wrong, u

FreeBSD Port: selenium-0.6.1

Hello! Thanks for maintaining the selenium port for FreeBSD. I saw on their web site that a new version is out. Are you planning an upgrade of the port? I'd love to give it a try! ;-) Best regards Palle Girgensohn <[EMAIL P

Re: Postgresql81-server port update

Currently the FreeBSD ports tree is frozen to prepare for the 6.2 release. Since the postgresql upgrade is not really a security release, I don't think I can persuade the RE team to accept an update to the port at this stage. As soon as the ports tree is unfrozen, I'll commit upgrades for all t

Re: ports/databases/postgresql81-server

--On måndag, oktober 30, 2006 19.00.37 -0600 Mark Linimon <[EMAIL PROTECTED]> wrote: On Mon, Oct 30, 2006 at 06:42:45PM -0600, Craig Boston wrote: Great, I'll file a PR later tonight unless somebody beats me to it. Well, we just lifted the freeze, so it's too late for 6.2, but it can go into

Re: [Mulberry-discuss] Problem with mail/mulberry

Hi Paul, Sounds strange that it complains about libXext.so.6, but perhaps you just didn't have linux-xorg-libs installed or up to date. Seens like the deinstall/reinstall process fixed that. How did you portupgrade, with `-R'? What versions of linux-emulation and other linux ports do you have?

Re: [Mulberry-discuss] Problem with mail/mulberry

manually approved each upgrade. linux-emulation: pkg_info -a | grep linux_base Information for linux_base-fc-4_9: Yes, the S/MIME plugin worked in previous versions. Not sure what happened, because the plugin is there. --On Wednesday, January 03, 2007 10:16:58 +0100 Palle Girgensohn <[EM

Re: [Mulberry-discuss] Problem with mail/mulberry

4 jan 2007 kl. 05.23 skrev Paul Schmehl: --On January 3, 2007 11:58:43 PM +0100 Palle Girgensohn <[EMAIL PROTECTED]> wrote: If you try to downgrade to the previous version, does it help? Just to let me know for sure it is the upgrade that gives you the trouble. Downgrading to v

default postgresql 7.4 -> 8.1, OK?

Hi! As the maintainer of the PostgreSQL ports, I'm planning a move to set the 8.1.x branch as the default version for FreeBSD. Now it is 7.4, which starts to get a bit rusty. Any objections? /Palle Index: Mk/bsd.database.mk ===

Re: default postgresql 7.4 -> 8.1, OK?

13 feb 2007 kl. 18.17 skrev Koen Martens: Palle Girgensohn wrote: Hi! As the maintainer of the PostgreSQL ports, I'm planning a move to set the 8.1.x branch as the default version for FreeBSD. Now it is 7.4, which starts to get a bit rusty. Any objections? I'm all in favour of

Re: default postgresql 7.4 -> 8.1, OK?

13 feb 2007 kl. 20.00 skrev Kris Kennaway: On Tue, Feb 13, 2007 at 04:37:00PM +0100, Palle Girgensohn wrote: Hi! As the maintainer of the PostgreSQL ports, I'm planning a move to set the 8.1.x branch as the default version for FreeBSD. Now it is 7.4, which starts to get a bit rusty.

Re: default postgresql 7.4 -> 8.1, OK?

14 feb 2007 kl. 05.29 skrev Ade Lovett: On Feb 13, 2007, at 09:17 , Koen Martens wrote: I'm all in favour of this. Any specific reason you're not moving to the 8.2.x branch? 8.2.x isn't really stable enough yet for Joe User to pick it up when they want postgresql support for random-port.

zope and py24-zopeInterface clash

Hi, Check this thread, it helped me after zope refused to start after a portupgrade -a So, it seems to me there's a bug in the ports tree, somehow? When installing plone, it installs zope29 and python24, and python

Re: PostgreSQL 8.x defaults

5 apr 2007 kl. 15.24 skrev Craig Boston: I recently installed some PostgreSQL 8.2 servers (and upgraded some from 8.1), and it reminded me of a few lingering nits in our port that bug me. Mostly the port seems that it can't make up its mind about VACCUM strategy. * We have a patch that sets

Re: PostgreSQL 8.x defaults

--On måndag, april 09, 2007 08.36.19 -0500 Craig Boston <[EMAIL PROTECTED]> wrote: I'm not sure of a good solution however. Do you think it would be possible / reasonable for the periodic job to check if the user has set postgresql_enable and do nothing if it is not enabled? That is certa

Re: postgresql93 port and libedit

17 jan 2015 kl. 01:41 skrev Baptiste Daroussin : > On Thu, Jan 15, 2015 at 08:02:22PM -0800, Waitman Gobble wrote: >> On Thu, Jan 15, 2015 at 8:01 AM, Baptiste Daroussin wrote: >>> On Wed, Jan 14, 2015 at 10:27:14PM -0800, Waitman Gobble wrote: Hi, I noticed that postgresql93-cl

Re: postgresql93 port and libedit

;>>>> wrote: >>>>>> On Sat, Jan 17, 2015 at 10:37:49AM +0100, Palle Girgensohn wrote: >>>>>> >>>>>> >>>>>>> 17 jan 2015 kl. 01:41 skrev Baptiste Daroussin : >>>>>>> >>>>>>&g

Re: postgresql93 port and libedit

> 7 feb 2015 kl. 12:27 skrev Baptiste Daroussin : > >> On Sat, Feb 07, 2015 at 10:33:48AM +0100, Palle Girgensohn wrote: >> Hello, >> >> I switched to Libedit with the latest release, and it appears that some >> colour code support is missing from Li

Re: Postgresql 92 XML gone?

I believe you also need to create extension xml ? > 2 aug 2015 kl. 11:59 skrev Andrea Venturoli : > > Hello. > > I've recently updated postgresql92-server and now a script of mine gives: >> ERROR: unsupported XML feature >> DETAIL: This functionality requires the server to be built with lib

Re: Proposal to fix postgresql package maintainance nightmare

> 21 jul 2015 kl. 15:03 skrev Baptiste Daroussin : > >> On Tue, Jul 21, 2015 at 09:22:31PM +0930, Shane Ambler wrote: >>> On 21/07/2015 19:16, Baptiste Daroussin wrote: >>> Hi, >>> >>> We do manage a bunch of postgresql servers on FreeBSD, and I really find the >>> current model of packages p

Re: Proposal to fix postgresql package maintainance nightmare

> 4 aug 2015 kl. 14:33 skrev Kimmo Paasiala : > >> On Tue, Aug 4, 2015 at 1:07 PM, Michael Grünewald >> wrote: >> >>> On 21 Jul 2015, at 11:46, Baptiste Daroussin wrote: >>> - Impossible to have tools from both old and new version at the same time >>> (which >>> is necessary to upgrade db

Re: Proposal to fix postgresql package maintainance nightmare

> 4 aug 2015 kl. 12:11 skrev Baptiste Daroussin : > >> On Tue, Aug 04, 2015 at 10:54:03AM +0300, Palle Girgensohn wrote: >> >> >> >> >>>> 21 jul 2015 kl. 15:03 skrev Baptiste Daroussin : >>>> >>>>> On Tue, Jul

Re: coinstallable version of pgsql (POC)

> 7 maj 2016 kl. 01:35 skrev Baptiste Daroussin : > > Hi all, > > Apparently noone had time to work on making all the version of pgsql > coinstallable since we last talked about it > > Here is a proof of concept done on pg95 which makes it coinstallable: > https://people.freebsd.org/~bapt/pgsql

Is there a mechanism to select the preferred version from mulitple installed versions of a port?

Hi, MacPorts has this and I believe that Debian has something similar. Say I want to install foobar-1.0 and foobar-2.0 and they CONFLICT what if I could change the foobar ports to install in, say ${PREFIX}/libexec/foobar-1.0 and ${PREFIX}/libexec/foobar-2.0 respectively, and then add a metap

Re: poudriere - postgresql90-client, LDAP, requires ldap.h

28 apr 2013 kl. 10:37 skrev Chris Rees : > Please CC maintainers when you're asking about specific ports! > On 28 April 2013 07:05, Scot Hetzel wrote: >> On Sat, Apr 27, 2013 at 4:32 PM, Florent Peterschmitt < >> flor...@peterschmitt.fr> wrote: >> >>> Le 27/04/2013 23:13, Matthew Seaman a écri

repo copy (svn cp) gives pre-commit "Do not replace a file. This will break the CVS exporter."

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I though I could just do my own repo copies not, using svn copy in the ports tree. Is this just not allowed, due to the CVS exporter? Will I still have to request a repo copy from portmgr@? Palle -BEGIN PGP SIGNATURE- Version: GnuPG/MacG

Re: repo copy (svn cp) gives pre-commit "Do not replace a file. This will break the CVS exporter."

n 11 May 2013 14:24, Palle Girgensohn wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi, >> >> I though I could just do my own repo copies not, using svn copy in the >> ports tree. Is this just not allowed, due to the CVS exporter? &g

Re: repo copy (svn cp) gives pre-commit "Do not replace a file. This will break the CVS exporter."

Ok, thanks. That is probably exactly what happened. I'll check it out tomorrow. PostgreSQL 9.3 beta1 will be announced on Monday... :-) 11 maj 2013 kl. 16:54 skrev Chris Rees : > On 11 May 2013 15:29, Palle Girgensohn wrote: >> Hi Chris, >> >> I did >> >

Re: repo copy (svn cp) gives pre-commit "Do not replace a file. This will break the CVS exporter."

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ah yes, thanks, that did the trick. Thanks! :) Palle Palle Girgensohn skrev: > Ok, thanks. That is probably exactly what happened. I'll check it out > tomorrow. > > PostgreSQL 9.3 beta1 will be announced on Monday... :-) > >

Re: Is postgresql83-server broken?

I submitted a patch yesterday the I think fixes this problem. Please try upgrading, and if it still doesn't work, email me again. Regards, Palle --On fredag, fr 29 aug 2008 13.37.06 +0200 Ivan Voras <[EMAIL PROTECTED]> wrote: There are two problems about this port that I've encountered yes

Re: Is postgresql83-server broken? (update: ICU and autotools problems?)

Mea culpa, I failed to committ the Makefile change last week. Now everything should work fine. Regards, Palle --On måndag, må 1 sep 2008 13.45.32 +0200 Ivan Voras <[EMAIL PROTECTED]> wrote: 2008/9/1 Alex Goncharov <[EMAIL PROTECTED]>: ,--- You/Ivan (Mon, 01 Sep 2008 11:29:39 +0200) * |

Re: Is postgresql83-server broken? (update: ICU and autotools problems?)

--On måndag, må 1 sep 2008 08.01.05 -0400 Alex Goncharov <[EMAIL PROTECTED]> wrote: ,--- You/Ivan (Mon, 1 Sep 2008 13:45:32 +0200) * | After I fix this manually with "make makesum", there's another problem: Did you try this simple fix instead: diff Makefile~ Makefi

Re: postgresql-server depends on client. Why?

Hi Dan, Well, it has always been like that, actually. PostgreSQL does not really support installing them completely separately. PostgreSQL does support minimiziing the installation to the client only, but not really the other way around. Maybe they are independent, I didn't really check it ou

Re: postgresql-server depends on client. Why?

Thing is, we install header files and man pages in the client only, if memory serves me right. Also, tools like createdb are in the client package. So, apart from the obvious "I want to upgrade the client separately (before) the server", there are no arguments for not doing it the way we do it