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 that.) postgresql is trickier than most, because there have to be both -server and -client ports to deal with. I also have postgresql-contrib-9.0.5 installed, which isn't critical but needs similar treatment. Everything depends on the -client port, so we start with that: # portmaster -o databases/postgresql91-client \ postgresql-client-9.0.5 # portmaster -o databases/postgresql91-server \ postgresql-server-9.0.5_1 # portmaster -o databases/postgresql91-contrib \ postgresql-contrib-9.0.5 This is the problem bit. The -o doesn't work with the ones I'm dealing with because of conflicts between 8.4 and 9.1. 9.1 *won't even build*. If you can find a way to get around that, then you can make life even easier for yourself by doing a recursive build of all of the things that depend on the client. It's getting around the conflict that I'm trying to figure out... the rest is handled. Not a problem with portmaster(1) -- it automatically adds DISABLE_CONFLICTS to the make environment if you're using the '-o' flag. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
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). pay attention here *** Error code 1 postgresql-client-8.4.8 make deinstall That's the ports makefiles talking, isn't it? In order to do that deinstall I need to also remove all of the things that depend on it... portupgrade is supposed to help me do the in-place upgrade without removing everything else first. Even if I forced the deinstall without letting the dependencies get in the way, wouldn't that break the dependency registration (+REQUIRED_BY) for all of those packages in the future? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
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 pkg_delete(1). pay attention here *** Error code 1 postgresql-client-8.4.8 make deinstall That's the ports makefiles talking, isn't it? In order to do that deinstall I need to also remove all of the things that depend on it... portupgrade is supposed to help me do the in-place upgrade without removing everything else first. Even if I forced the deinstall without letting the dependencies get in the way, wouldn't that break the dependency registration (+REQUIRED_BY) for all of those packages in the future? Yes. I've been planning a very similar update -- postgresql 9.0 to 9.1 -- and what I've come up with so far is this: 0) Backup *everything* 1) Stop postgresql daemon and any services that depend on postgresql 2) Move the postgresql data directory aside: # mv ~pgsql/data ~pgsql/data-9.0.5 3) Optional. If you have WITH_PGSQL_VER defined in /etc/make.conf, or similar update it at this point. Or delete it -- ports will pick up the new version automatically once you've updated to it. 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 there have to be both -server and -client ports to deal with. I also have postgresql-contrib-9.0.5 installed, which isn't critical but needs similar treatment. Everything depends on the -client port, so we start with that: # portmaster -o databases/postgresql91-client \ postgresql-client-9.0.5 # portmaster -o databases/postgresql91-server \ postgresql-server-9.0.5_1 # portmaster -o databases/postgresql91-contrib \ postgresql-contrib-9.0.5 5) Now rebuild everything that depends on the new postgresql client port. Use '-x' and '-R' to avoid rebuilding the ports already updated # portmaster -R -r postgresql-client-9.1.1_1 \ -x postgresql-server-9.1.1_1 -x postgresql-contrib-9.1.1_1 6) Re-init the postgresql cluster # su - pgsql % mkdir ~/data % initdb -D ~/data -E utf8 --locale C (or use the rc.d script) % vi ~/data/postgresql.conf(etc...) 7) Restart the postgresql database # /usr/local/etc/rc.d/postgresql start 8) Reload databases from backup. Restart all dependent services. 9) ??? 10) Profit! This does require an appreciable period of system downtime, but as that's fine for my purposes, I haven't put any effort into thinking about how to minimize that. A good thing to do if downtime is a big deal for you would be to build updated packages of everything postgresql related off-line and use portmaster's '-P' package mode to install them. Similarly, make backup packages of everything you're updating (pkg_create -b pkgname) so if you need to back everything out you can just swap those packages back in rather than doing a full-scale recovery from backup. Using this method for a very big database is not amazingly practical -- in that case, using pg_upgrade(8) would probably be preferable, but that's not going to entirely simple given the constraints of the ports system. You'll need to have both the previous and target versions of the postgresql-client and postgresql-contrib installed simultaneously, but those ports all conflict with each other. You'll also need to have two separate data directories -- the original one and one for the new version. The default layout on Linux nowadays includes the postgresql major version in the data directory path and in the names of most conflicting applications, but this capability hasn't come to the ports yet. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
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 there have to be both -server and -client ports to deal with. I also have postgresql-contrib-9.0.5 installed, which isn't critical but needs similar treatment. Everything depends on the -client port, so we start with that: # portmaster -o databases/postgresql91-client \ postgresql-client-9.0.5 # portmaster -o databases/postgresql91-server \ postgresql-server-9.0.5_1 # portmaster -o databases/postgresql91-contrib \ postgresql-contrib-9.0.5 This is the problem bit. The -o doesn't work with the ones I'm dealing with because of conflicts between 8.4 and 9.1. 9.1 *won't even build*. If you can find a way to get around that, then you can make life even easier for yourself by doing a recursive build of all of the things that depend on the client. It's getting around the conflict that I'm trying to figure out... the rest is handled. And by the way, if you're not already doing a recursive build then you can do the server upgrade more simply.. there are no dependencies attached to the server (normally) so you can just pkg_delete it and install 9.1. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
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 that the two packages conflict, and so the 9.1 client won't even build[1]. Thanks to those who tried to help. After poking around in the Mk files A LOT, I eventually stumbled upon a solution. Not sure if this is right or not, but it worked: sudo portupgrade -M DISABLE_CONFLICTS=1 -rf -o databases/postgresql91-client databases/postgresql84-client Surprisingly, despite the -f, none of the dependencies were rebuilt.. I got warnings like this instead, for every dependency: --- Skipping 'databases/postgresql91-client' (apache-2.2.21) because it has already done However, the +REQUIRED_BY file was still rebuilt properly for the 9.1 client, so I can now easily go through and do dependency rebuilds as necessary. Cheers, Matt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
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 (and I'd like to keep the package's +REQUIRED_BY file properly updated anyway). 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 that the two packages conflict, and so the 9.1 client won't even build[1]. This seems to be the sort of situation described by the -o example in the portupgrade man page, but I haven't been able to figure out how to make it work. Does anyone have any suggestions? Thanks! -- [1] [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 140 packages found (-1 +0) (...) done] --- Upgrading 'postgresql-client-8.4.8' to 'postgresql-client-9.1.1_1' (databases/postgresql91-client) --- Building '/usr/ports/databases/postgresql91-client' === Cleaning for postgresql-client-9.1.1_1 cd /usr/ports/databases/postgresql91-client make config; === postgresql-client-9.1.1_1 conflicts with installed package(s): postgresql-client-8.4.8 They install files into the same place. You may want to stop build with Ctrl + C. === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Found saved configuration for postgresql-client-9.1.1_1 = postgresql-9.1.1.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/postgresql. = Attempting to fetch ftp://ftp.se.postgresql.org/pub/databases/relational/postgresql/source/v9.1.1/postgresql-9.1.1.tar.bz2 postgresql-9.1.1.tar.bz2 100% of 14 MB 1349 kBps 00m00s === 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). *** Error code 1 Stop in /usr/ports/databases/postgresql91-client. *** Error code 1 Stop in /usr/ports/databases/postgresql91-client. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20111202-57604-1bstor4-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=postgresql-client-8.4.8 UPGRADE_PORT_VER=8.4.8 make ** Fix the problem and try again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Major version changes using portupgrade?
2011/12/2 Matthew Pounsett m...@conundrum.com: 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 (and I'd like to keep the package's +REQUIRED_BY file properly updated anyway). 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 that the two packages conflict, and so the 9.1 client won't even build[1]. This seems to be the sort of situation described by the -o example in the portupgrade man page, but I haven't been able to figure out how to make it work. Does anyone have any suggestions? Thanks! -- [1] [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 140 packages found (-1 +0) (...) done] --- Upgrading 'postgresql-client-8.4.8' to 'postgresql-client-9.1.1_1' (databases/postgresql91-client) --- Building '/usr/ports/databases/postgresql91-client' === Cleaning for postgresql-client-9.1.1_1 cd /usr/ports/databases/postgresql91-client make config; === postgresql-client-9.1.1_1 conflicts with installed package(s): postgresql-client-8.4.8 They install files into the same place. You may want to stop build with Ctrl + C. === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Found saved configuration for postgresql-client-9.1.1_1 = postgresql-9.1.1.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/postgresql. = Attempting to fetch ftp://ftp.se.postgresql.org/pub/databases/relational/postgresql/source/v9.1.1/postgresql-9.1.1.tar.bz2 postgresql-9.1.1.tar.bz2 100% of 14 MB 1349 kBps 00m00s === 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). pay attention here *** Error code 1 postgresql-client-8.4.8 make deinstall Tip. always run portaudit -F first. Regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
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 questions has an obvoius answer but i really don't know the first thing about FreeBSD and really want to get to know it better. Thanks in advance Rafael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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, should be 1; fixing. X connection to :0.0 broken (explicit kill or server shutdown). Has anyone any idea what might be the problem? Look at : /var/log/Xorg.0.log Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 kill or server shutdown). Has anyone any idea what might be the problem? I deleted xorg and everything connected with it and compiled it anew and the same error happens. Thanks in advance ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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-xml-4.3 -- gnome-doc-utils-0.7.2_1 -- manually run 'pkgdb -F' to fix, or specify -O to force. cassiopeia# pkg_delete gnome-doc-utils-0.7.2_1 pkg_delete: no such package 'gnome-doc-utils-0.7.2_1' installed cassiopeia# Background: I upgraded portupgrade, then I deleted the package database (database format was changed to db4). Now I do not know how to fix this. Can't I just remove this stale origin from the package database? Is there a way to rebuild the whole package database instead of fixing it? It is not clear why pkgdb -F does not recognize the problem while portupgrade does. Any ideas? Thanks, Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 makefile anyway. Thanks. -- Kiffin Gish [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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/pkgtools.conf -- dick -- http://nagual.nl/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 6.1 +++ The Power to Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to upgrade kdenetwork using portupgrade
You should upgrade kdelibs first :) But the better approach is to rebuild all the dependencies also, so you should use -R option. Maybe the version you are trying to upgrade from is too old and you should foce upgrade all the depends! Ivailo Tanusheff Senior System administrator ProCredit Bank (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'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 consequence? Would it be simpler to run portupgrade -rR kde? Thanks, Teo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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'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 consequence? Would it be simpler to run portupgrade -rR kde? Thanks, Teo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 http://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. It doesn't say that, it says a complete error message. What is it? What is the consequence? Would it be simpler to run portupgrade -rR kde? Read /usr/ports/UPDATING - there are special steps you need to go through when updating kde. Kris pgpAKSc5KoWC1.pgp Description: PGP signature
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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 up the software and configs that are currently running. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] portupgrade won't modify your config files. But be sure to read /usr/ports/UPDATING before you upgrade anything. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 running on a server, so I don't want to muck up the software and configs that are currently running. You have good dumps, yes? And you've read /usr/ports/UPDATING, yes? And you've reviewed any changes to the Makefiles of the ports in question, yes? Then you shouldn't have any issues. Best Regards, Christopher Nehren -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCQH9Ek/lo7zvzJioRAo0eAKC7l+QyDgzY4J7bx7Yx/izqDHjHLgCgglXT 5X1U54MJxqxscr7Zl+fAcfc= =m7EO -END PGP SIGNATURE- -- I abhor a system designed for the user, if that word is a coded pejorative meaning stupid and unsophisticated. -- Ken Thompson If you ask the wrong questions, you get answers like 42 and God. Unix is user friendly. However, it isn't idiot friendly. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 I'm using fluxbox as window manager, do I need to run the script? or is portupgrade fine? my portupgrade is currently still running and I don't seem to encounter any problem (yet). Regards, Andri Kok _ SEEK: Now with over 50,000 dream jobs! Click here: http://ninemsn.seek.com.au?hotmail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 question is, if I only have parts of Gnome installed, while I'm using fluxbox as window manager, do I need to run the script? or is portupgrade fine? my portupgrade is currently still running and I don't seem to encounter any problem (yet). I also run that way and from my experience the odds are pretty high that something will be done out of order. I did a portupgrade -pufr glib to do the upgrade and had a few problems that I had to manually update. I understand from other comments that re-running the upgrade script makes the update go faster than a -rf glib. If you look at ports that you have installed that depend on glib, the list seems to go forever. I don't know if a -pufrR glib would have prevented the problems but that would have used even more computer time to do the update. I think the AMD 2400+ needed something like 13 hours to do the update the way I did it. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 should upgrade Gnome using the script provided by FreeBSD Gnome. The question is, if I only have parts of Gnome installed, while I'm using fluxbox as window manager, do I need to run the script? or is portupgrade fine? my portupgrade is currently still running and I don't seem to encounter any problem (yet). I also run that way and from my experience the odds are pretty high that something will be done out of order. I did a portupgrade -pufr glib to do the upgrade and had a few problems that I had to manually update. I understand from other comments that re-running the upgrade script makes the update go faster than a -rf glib. If you look at ports that you have installed that depend on glib, the list seems to go forever. I don't know if a -pufrR glib would have prevented the problems but that would have used even more computer time to do the update. I think the AMD 2400+ needed something like 13 hours to do the update the way I did it. I personal would go for rebuild everything that depend on pkg-config instead glib, because of libxml2, libxslt and etc that don't depend on glib. Cheers, Mezz Kent -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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, 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 I'm using fluxbox as window manager, do I need to run the script? or is portupgrade fine? my portupgrade is currently still running and I don't seem to encounter any problem (yet). I also run that way and from my experience the odds are pretty high that something will be done out of order. I did a portupgrade -pufr glib to do the upgrade and had a few problems that I had to manually update. I understand from other comments that re-running the upgrade script makes the update go faster than a -rf glib. If you look at ports that you have installed that depend on glib, the list seems to go forever. I don't know if a -pufrR glib would have prevented the problems but that would have used even more computer time to do the update. I think the AMD 2400+ needed something like 13 hours to do the update the way I did it. I personal would go for rebuild everything that depend on pkg-config instead glib, because of libxml2, libxslt and etc that don't depend on glib. I think that is close to the overkill -rRfa. You only want to update the ports that should be updated. It hasn't been that long since I did a -rf expat. I feel strongly about updating all dependancies of libraries. That is one of the fine features of make in the programming world. If you modify a library, it updates everything that uses it. It just isn't always necessary. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 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 were failed/skipped. My problem is figuring out the most efficient way to deal with it from here. LAST time I did a portupgrade -Raf I had a much smaller number failed/skipped, and what I did was work out the dependency tree for the remaining ones by hand using pkg_info -R and -r, figure out the order, and do a portupgrade -f on each in the proper order. This was to avoid rebuilding stuff already built on the first -Raf pass, and multiple times over (since I was taking care of each remaining one individually). Seems to me that if 50 of those 132 are X apps and I do a portupgrade -Rf on each, I'll be rebuilding XFree86 50 times. Hence the need to work out the install order by-hand based upon dependencies and only use -f. But I don't see that as practical this time around with so many left to do. So... my ultimate question is: how do you pros handle situations like this? Is there a trick I'm missing? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems using portupgrade to recompile all ports
On Thu, 15 Jan 2004, Scott I. Remick wrote: 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 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 were failed/skipped. My problem is figuring out the most efficient way to deal with it from here. LAST time I did a portupgrade -Raf I had a much smaller number failed/skipped, and what I did was work out the dependency tree for the remaining ones by hand using pkg_info -R and -r, figure out the order, and do a portupgrade -f on each in the proper order. This was to avoid rebuilding stuff already built on the first -Raf pass, and multiple times over (since I was taking care of each remaining one individually). Seems to me that if 50 of those 132 are X apps and I do a portupgrade -Rf on each, I'll be rebuilding XFree86 50 times. Hence the need to work out the install order by-hand based upon dependencies and only use -f. But I don't see that as practical this time around with so many left to do. So... my ultimate question is: how do you pros handle situations like this? Is there a trick I'm missing? Do you know why the failure happened? The most frequent cause of this when I've encountered the problem is that a distfile could not be fetched. I tend to try to avoid that these days by prefetching the distfiles prior to a build (ie, while I'm around to sort out problems manually rather than overnight). -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ If it's broken really badly - don't fix it either. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems using portupgrade to recompile all ports
On Thu, 15 Jan 2004 16:02:44 + (GMT), Jan Grant wrote: On Thu, 15 Jan 2004, Scott I. Remick wrote: 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 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 were failed/skipped. My problem is figuring out the most efficient way to deal with it from here. LAST time I did a portupgrade -Raf I had a much smaller number failed/skipped, and what I did was work out the dependency tree for the remaining ones by hand using pkg_info -R and -r, figure out the order, and do a portupgrade -f on each in the proper order. This was to avoid rebuilding stuff already built on the first -Raf pass, and multiple times over (since I was taking care of each remaining one individually). Seems to me that if 50 of those 132 are X apps and I do a portupgrade -Rf on each, I'll be rebuilding XFree86 50 times. Hence the need to work out the install order by-hand based upon dependencies and only use -f. But I don't see that as practical this time around with so many left to do. So... my ultimate question is: how do you pros handle situations like this? Is there a trick I'm missing? Do you know why the failure happened? The most frequent cause of this when I've encountered the problem is that a distfile could not be fetched. I tend to try to avoid that these days by prefetching the distfiles prior to a build (ie, while I'm around to sort out problems manually rather than overnight). Various reasons. I could post the full list at the end if you'd like (I saved it). Most are skipped (*) due to dependencies on the ones that failed (!). For the failed ones, I got assorted errors: unknown build error, install error, checksum mismatch, linker error, new compiler error, missing header. The ones marked ! failed isn't so large I couldn't investigate/fix each individually, but I'm trying to figure out the best way to deal with the full list of failed/skipped so that once I fix the reason for the failures, I can JUST rebuild those in the failed/skipped list and in the proper order, instead of having to rebuild my entire (400+) ports list again w/ -Raf, most of which compiled fine under 5.2. Hopefully I'm making sense... :) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 all packages installed before the given date. (Note: -R and -r are unnecessary with -a). Rinse, repeat. Until all your ports are up to date. Usually ports problems are either inability to download the required distfiles or a temporary SNAFU by the port maintainer/committer. In most cases it suffices to wait a few hours or days, re-cvsup the ports tree and start the portupgrade job again. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
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. Until all your ports are up to date. Excellent! That should do EXACTLY what I needed. Thank you so much. Usually ports problems are either inability to download the required distfiles or a temporary SNAFU by the port maintainer/committer. In most cases it suffices to wait a few hours or days, re-cvsup the ports tree and start the portupgrade job again. Yeah that was my plan... I'm well-familiar with ports-tree hiccups. I have plenty of other things to do to pass the time while I sort this out (like install 4.9 on a separate drive to try and fix a UFS1 volume I cannot access due to a bad superblock. Or play with my new Palm Tungsten T3 once it arrives) 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 instead of -af of course). Is there a syntax to do that? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 instead of -af of course). Is there a syntax to do that? 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. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
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.. almost, but not quite: su-2.05b# portupgrade -Rfx '=2004-01-14' docbook-xsl ** All the packages matching 'docbook-xsl' were excluded. ** No such package 'docbook-xsl' is installed. So -x is picking up the package name too. Don't want that. So I try: portupgrade -Rf docbook-xsl -x '=2004-01-14' And that seems to work. I've used it with a bunch of my originally-failed ports and making progress. A lot of them are failing with local modification time does not match remote but I delete the file from /usr/ports/distfiles and all is well. Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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_2 A graphics library similar to SGI's OpenGL ORBit-0.5.17High-performance CORBA ORB with support for the C language XFree86-4.3.0,1 X11/XFree86 core distribution (complete, using mini/meta-po Note how Mesa's entry begins immediately after the last character of BitTorrent's. [...] While I actually don't know why the terminating newline is missing in some cases I noticed that there was an MFC to RELENG_4 a couple of days ago that makes 'pkg_info' add a newline if the comment line doesn't have one. You may want to take a look at FreeBSD's CVS repository (src/usr.sbin/pkg_install/info/show.c) in order to build and install a fixed 'pkg_info'. Or if it doesn't happen often you could just as well edit the respective '+COMMENT' file in the '/var/db/pkg' hierarchy. The pragmatic approach. ;-) Uwe -- Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers [EMAIL PROTECTED] | http://www.escapebox.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 ORB with support for the C language XFree86-4.3.0,1 X11/XFree86 core distribution (complete, using mini/meta-po Note how Mesa's entry begins immediately after the last character of BitTorrent's. [...] While I actually don't know why the terminating newline is missing in some cases I noticed that there was an MFC to RELENG_4 a couple of days ago that makes 'pkg_info' add a newline if the comment line doesn't have one. You may want to take a look at FreeBSD's CVS repository (src/usr.sbin/pkg_install/info/show.c) in order to build and install a fixed 'pkg_info'. That did the trick; thanks! Still, why does portupgrade get rid of the newlines in the COMMENT? Has anyone else seen this behavior? -Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 library similar to SGI's OpenGL ORBit-0.5.17High-performance CORBA ORB with support for the C language XFree86-4.3.0,1 X11/XFree86 core distribution (complete, using mini/meta-po Note how Mesa's entry begins immediately after the last character of BitTorrent's. The behavior seems to be that if a package has been installed/upgraded with portupgrade, it eliminates the terminal newline from the pkg_info listing. Running pkg_info with a particular package as an argument works fine. pkgdb reports that the database is uncorrupted and up-to-date. The only effect seems to be this fairly annoying display bug, but nothing that is impairing the functionality of the system in a serious way. Thank you in advance for any help/insights/hints. Have a good day. -Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
