Re: Major version changes using portupgrade?

On 04/12/2011 20:07, Matthew Pounsett wrote: > On 2011/12/04, at 14:13, Matthew Seaman wrote: > >> > 4) Now for the updating bit. I'm going to use portmaster's '-o' >> > functionality to swap out the postgresql versions. (portupgrade >> > has very similar functionality if you prefer

Re: Major version changes using portupgrade?

On 2011/12/02, at 05:19, Matthew Pounsett wrote: > I was expecting the following to work: > sudo portupgrade -rf -o databases/postgresql91-client > databases/postgresql84-client > > However, I'm running into a problem where the ports makefiles, and by > extension portupgrade, are detecting tha

Re: Major version changes using portupgrade?

On 2011/12/04, at 14:13, Matthew Seaman wrote: > 4) Now for the updating bit. I'm going to use portmaster's '-o' > functionality to swap out the postgresql versions. (portupgrade > has very similar functionality if you prefer that.) postgresql > is trickier than most, because t

Re: Major version changes using portupgrade?

On 04/12/2011 17:16, Matthew Pounsett wrote: > On 2011/12/04, at 02:29, Sergio Tam wrote: > >>> >> ===> postgresql-client-9.1.1_1 conflicts with installed package(s): >>> >> postgresql-client-8.4.8 >>> >> >>> >> They will not build together. >>> >> Please remove them first with pk

Re: Major version changes using portupgrade?

On 2011/12/04, at 02:29, Sergio Tam wrote: >> ===> postgresql-client-9.1.1_1 conflicts with installed package(s): >> postgresql-client-8.4.8 >> >> They will not build together. >> Please remove them first with pkg_delete(1). > attention here >> *** Error c

Re: Major version changes using portupgrade?

2011/12/2 Matthew Pounsett : > > I'm trying to do a major version upgrade of postgres from 8.4 to 9.1.  I've > dumped the db and uninstalled the postgres-server port, and I'd like to use > portupgrade to handle the client upgrade, since it has a number of > dependencies that probably should be r

Major version changes using portupgrade?

I'm trying to do a major version upgrade of postgres from 8.4 to 9.1. I've dumped the db and uninstalled the postgres-server port, and I'd like to use portupgrade to handle the client upgrade, since it has a number of dependencies that probably should be recompiled against the new client libs

Upgrading Bind9 safely using portupgrade

Which is the best way to upgrade bind9 using portupgrade without setting anything on fire? I have two FreeBSDs which act as master and slave DNS (not installed by me), should i upgrade both bind's before they can work again? should i kill bind before upgrading? I'm sorry if any of my

Re: xorg broken after using portupgrade

Le vendredi 30 mars 2007, E. J. Cerejo a écrit : > I'm running FBSD release 6.2 and after updating my ports with portupgrade > I can start xorg. I'm getting this error message: > > waiting for X server to shut down FreeFontPath: FPE > "/usr/X11R6/lib/X11/fonts/misc/:unscaled" refcount is 2, shoul

xorg broken after using portupgrade

I'm running FBSD release 6.2 and after updating my ports with portupgrade I can start xorg. I'm getting this error message: waiting for X server to shut down FreeFontPath: FPE "/usr/X11R6/lib/X11/fonts/misc/:unscaled" refcount is 2, should be 1; fixing. X connection to :0.0 broken (explicit kil

Re: Gnome install - error (using portupgrade)

What is this "null" stale origin? cassiopeia# pkgdb -F ---> Checking the package registry database Stale origin: '(null)': perhaps moved or obsoleted. Skip this for now? [yes] To skip it without asking in future, please list it in HOLD_PKGS. cassiopeia# portupgrade -a Stale dependency: docbook-x

Re: Skip/ignore certain makes using portupgrade ...

On 01 Aug [EMAIL PROTECTED] wrote: > What's the best way to ignore certain dependancies within makefiles > while running a portupgrade? > > For example, I don't want to build the Galeon webbrowser everytime, but > it is present in the Gnome2 makefile. See the HOLDPKG statement in /usr/local/etc/p

Skip/ignore certain makes using portupgrade ...

What's the best way to ignore certain dependancies within makefiles while running a portupgrade? For example, I don't want to build the Galeon webbrowser everytime, but it is present in the Gnome2 makefile. If I delete it from the file this does not help because a cvsup restores the original make

Re: Unable to upgrade kdenetwork using portupgrade

(Bulgaria) AD Teo De Las Heras <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 10/27/2005 04:06 PM To freebsd-questions@freebsd.org cc Subject Unable to upgrade kdenetwork using portupgrade I'm running FreeBSD 5.4 on my dektop with X.org <http://X.org> and KDE 3.4. I&#

Re: Unable to upgrade kdenetwork using portupgrade

On Thu, Oct 27, 2005 at 09:06:36AM -0400, Teo De Las Heras wrote: > I'm running FreeBSD 5.4 on my dektop with X.org and KDE 3.4. > I'm synchronizing my ports tree using cvsup. > When I run the following command > portupgrade -rR kdenetwork > It fails because it is unable to upgrad

Unable to upgrade kdenetwork using portupgrade

I'm running FreeBSD 5.4 on my dektop with X.org and KDE 3.4. I'm synchronizing my ports tree using cvsup. When I run the following command portupgrade -rR kdenetwork It fails because it is unable to upgrade the kdelibs. The error messages says to run -F to force. What is the cons

Re: Using portupgrade

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2005-03-22, Pat Maddox scribbled these curious markings: > What are some considerations to make before upgrading the ports? Does > upgrading them overwrite the existing config files? I've got a number > of ports that aren't up-to-date, but this is

Re: Using portupgrade

On Tue, Mar 22, 2005 at 11:38:52AM -0700, Pat Maddox wrote: > What are some considerations to make before upgrading the ports? Does > upgrading them overwrite the existing config files? I've got a number > of ports that aren't up-to-date, but this is running on a server, so I > don't want to muck

Using portupgrade

What are some considerations to make before upgrading the ports? Does upgrading them overwrite the existing config files? I've got a number of ports that aren't up-to-date, but this is running on a server, so I don't want to muck up the software and configs that are currently running. ___

Re: upgrading Gnome components using portupgrade

On Friday 16 April 2004 12:42 pm, Jeremy Messenger wrote: > On Fri, 16 Apr 2004 11:52:04 -0700, Kent Stewart <[EMAIL PROTECTED]> wrote: > > On Friday 16 April 2004 11:39 am, sAndri Kok wrote: > >> Hi guys, > >> > >> I have what I believe are Gnome components installed on my > >> computer (gimp, Gc

Re: upgrading Gnome components using portupgrade

On Fri, 16 Apr 2004 11:52:04 -0700, Kent Stewart <[EMAIL PROTECTED]> wrote: On Friday 16 April 2004 11:39 am, sAndri Kok wrote: Hi guys, I have what I believe are Gnome components installed on my computer (gimp, Gconf, gtk, glib, etc). I'm running portupgrade now and I read the message that I sho

Re: upgrading Gnome components using portupgrade

On Friday 16 April 2004 11:39 am, sAndri Kok wrote: > Hi guys, > > I have what I believe are Gnome components installed on my computer > (gimp, Gconf, gtk, glib, etc). I'm running portupgrade now and I read > the message that I should upgrade Gnome using the script provided by > FreeBSD Gnome. The

upgrading Gnome components using portupgrade

Hi guys, I have what I believe are Gnome components installed on my computer (gimp, Gconf, gtk, glib, etc). I'm running portupgrade now and I read the message that I should upgrade Gnome using the script provided by FreeBSD Gnome. The question is, if I only have parts of Gnome installed, while

Re: Problems using portupgrade to recompile all ports

On Thu, 15 Jan 2004 17:38:41 +, Matthew Seaman wrote: > portupgrade -rfx '>=2004-01-15' foo > > will force re-install 'foo' and everything that depends on package > 'foo', except those packages installed on or after the given date. Well, actually I want -R and not -r, but anyways.. almos

Re: Problems using portupgrade to recompile all ports

On Thu, Jan 15, 2004 at 12:25:17PM -0500, Scott I. Remick wrote: > One question: it's not clear from man pkg_glob whether I can combine the > date format '<2004-01-15' with a package name, so that I only update the > dependencies of a SPECIFIC package that are older than that date (using -f > inste

Re: Problems using portupgrade to recompile all ports

On Thu, 15 Jan 2004 17:12:27 +, Matthew Seaman wrote: > Work out what went wrong, fix it and then just run: > > # portupgrade -af '<2004-01-15' > > which does a forced update of all packages installed before the given > date. (Note: -R and -r are unnecessary with -a). Rinse, > repeat.

Re: Problems using portupgrade to recompile all ports

On Thu, Jan 15, 2004 at 10:03:31AM -0500, Scott I. Remick wrote: > So... my ultimate question is: how do you pros handle situations like this? > Is there a trick I'm missing? Work out what went wrong, fix it and then just run: # portupgrade -af '<2004-01-15' which does a forced update of a

Re: Problems using portupgrade to recompile all ports

robs. >> >> I noticed some of my daemons (from ports) seemed a bit annoyed though upon >> booting up 5.2. I tried using portupgrade -Rf on them individually, and >> then all was well. I decided then that it'd be best to do everything (-Raf) >> to play it safe. I&#

Re: Problems using portupgrade to recompile all ports

gh upon > booting up 5.2. I tried using portupgrade -Rf on them individually, and > then all was well. I decided then that it'd be best to do everything (-Raf) > to play it safe. I've done this before. > > So it finally finished last night, but not really... about 132 ports

Problems using portupgrade to recompile all ports

So I'm upgrading my 5.1R desktop to 5.2R. Used cvsup, followed the instructions in UPGRADING, did a custom kernel, etc etc. That part went fine, no probs. I noticed some of my daemons (from ports) seemed a bit annoyed though upon booting up 5.2. I tried using portupgrade -Rf on

Re: Strange formatting error with pkg_info after using portupgrade

On Sat, Jun 21, 2003 at 06:54:05PM +0200, Uwe Doering wrote: > > Rev. Joe Doyle Ardent wrote: > > > >please:~> pkg_info |head > >BitTorrent-3.2.1b "Peer to Peer file sharing/mirroring."Mesa-3.4.2_2 > >A graphics library similar to SGI's OpenGL > >ORBit-0.5.17High-performance CORBA O

Re: Strange formatting error with pkg_info after using portupgrade

Hi, Rev. Joe Doyle Ardent wrote: Hello, everyone, I have a fairly strange error, that has popped up on both machines where I have used portupgrade (both 4.8-RELEASE boxes). Here is an example output: please:~> pkg_info |head BitTorrent-3.2.1b "Peer to Peer file sharing/mirroring."Mesa-3.4.2

Strange formatting error with pkg_info after using portupgrade

Hello, everyone, I have a fairly strange error, that has popped up on both machines where I have used portupgrade (both 4.8-RELEASE boxes). Here is an example output: please:~> pkg_info |head BitTorrent-3.2.1b "Peer to Peer file sharing/mirroring."Mesa-3.4.2_2 A graphics libra