how should I upgrade all these ports??
Hi, I just csup my port tree this morning (01/12), and realized there is a whole lot ports need my attention (49 of them). I checked out UPDATES and found out that gnome and GTK+ have just been updated. But i don't have gtkmm or gnome-session installed, I wonder if I should still upgrade my ports just as described in the UPDATES. Here is the list: === New version available: gnomehier-2.3_11 === New version available: lame-3.98.2_1 === New version available: libcheck-0.9.6 === New version available: ORBit2-2.14.16 === New version available: arts-1.5.10_1,1 === New version available: atk-1.24.0 === New version available: cairo-1.8.6,1 === New version available: consolekit-0.3.0_3 === New version available: dbus-1.2.4.2 === New version available: dbus-glib-0.78 === New version available: esound-0.2.41 === New version available: fontconfig-2.6.0,1 === New version available: gamin-0.1.10 === New version available: gconf2-2.24.0 === New version available: gio-fam-backend-2.18.4 === New version available: glib-2.18.4 === New version available: gnome-doc-utils-0.14.2 === New version available: gnome-icon-theme-2.24.0_2 === New version available: gnome-keyring-2.24.1_1 === New version available: gnome-vfs-2.24.0 === New version available: gtk-2.14.7 === New version available: gtk-engines2-2.16.1 === New version available: gvfs-1.0.3 === New version available: hal-0.5.11_10 === New version available: libbonobo-2.24.0 === New version available: libbonoboui-2.24.0 === New version available: libgnome-2.24.1 === New version available: libgnomeui-2.24.0 === New version available: libgsf-1.14.11 === New version available: libnotify-0.4.5 === New version available: librsvg2-2.22.3_1 === New version available: libsoup-2.24.2.1 === New version available: libxml2-2.7.2_1 === New version available: pango-1.22.4 === New version available: pixman-0.12.0 === New version available: policykit-0.9_2 === New version available: policykit-gnome-0.9.2 === New version available: py25-cairo-1.8.0_2 === New version available: py25-gobject-2.16.0 === New version available: py25-gtk-2.13.0_1 === New version available: py25-libxml2-2.7.2 === New version available: firefox-3.0.5_1,1 === New version available: firefox-3.0.a2_5,1 === New version available: gnome-menus-2.24.2 === New version available: intltool-0.40.5 === New version available: libgweather-2.24.2 === New version available: libwnck-2.24.2 === New version available: py25-orbit-2.24.0 === New version available: webkit-gtk2-1.0.1_4 === 49 have new versions available thank you!! TFC ___ 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
how should I upgrade all these ports??
Tsu-Fan Cheng writes: I just csup my port tree this morning (01/12), and realized there is a whole lot ports need my attention (49 of them). I checked out UPDATES and found out that gnome and GTK+ have just been updated. But i don't have gtkmm or gnome-session installed, I wonder if I should still upgrade my ports just as described in the UPDATES. In short, yes. Many (but not all) of these a) are part of GNOME or b) have a GNOME component in their dependencies. The update procedure is there for a reason. (Advice: make sure you have the latest vesion of UPDATING. Additional useful information was added in the last 24 hours.) Robert Huff ___ 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: how should I upgrade all these ports??
Always read /usr/ports/UPDATING before any upgrade. After that you can use portmaster (the one I use) or portupgrade to upgrade all those outdated ports with a single command : portmaster -avd On Mon, 2009-01-12 at 10:08 -0500, Tsu-Fan Cheng wrote: Hi, I just csup my port tree this morning (01/12), and realized there is a whole lot ports need my attention (49 of them). I checked out UPDATES and found out that gnome and GTK+ have just been updated. But i don't have gtkmm or gnome-session installed, I wonder if I should still upgrade my ports just as described in the UPDATES. Here is the list: === New version available: gnomehier-2.3_11 === New version available: lame-3.98.2_1 === New version available: libcheck-0.9.6 === New version available: ORBit2-2.14.16 === New version available: arts-1.5.10_1,1 === New version available: atk-1.24.0 === New version available: cairo-1.8.6,1 === New version available: consolekit-0.3.0_3 === New version available: dbus-1.2.4.2 === New version available: dbus-glib-0.78 === New version available: esound-0.2.41 === New version available: fontconfig-2.6.0,1 === New version available: gamin-0.1.10 === New version available: gconf2-2.24.0 === New version available: gio-fam-backend-2.18.4 === New version available: glib-2.18.4 === New version available: gnome-doc-utils-0.14.2 === New version available: gnome-icon-theme-2.24.0_2 === New version available: gnome-keyring-2.24.1_1 === New version available: gnome-vfs-2.24.0 === New version available: gtk-2.14.7 === New version available: gtk-engines2-2.16.1 === New version available: gvfs-1.0.3 === New version available: hal-0.5.11_10 === New version available: libbonobo-2.24.0 === New version available: libbonoboui-2.24.0 === New version available: libgnome-2.24.1 === New version available: libgnomeui-2.24.0 === New version available: libgsf-1.14.11 === New version available: libnotify-0.4.5 === New version available: librsvg2-2.22.3_1 === New version available: libsoup-2.24.2.1 === New version available: libxml2-2.7.2_1 === New version available: pango-1.22.4 === New version available: pixman-0.12.0 === New version available: policykit-0.9_2 === New version available: policykit-gnome-0.9.2 === New version available: py25-cairo-1.8.0_2 === New version available: py25-gobject-2.16.0 === New version available: py25-gtk-2.13.0_1 === New version available: py25-libxml2-2.7.2 === New version available: firefox-3.0.5_1,1 === New version available: firefox-3.0.a2_5,1 === New version available: gnome-menus-2.24.2 === New version available: intltool-0.40.5 === New version available: libgweather-2.24.2 === New version available: libwnck-2.24.2 === New version available: py25-orbit-2.24.0 === New version available: webkit-gtk2-1.0.1_4 === 49 have new versions available thank you!! TFC ___ 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 -- Julien Cigar Belgian Biodiversity Platform http://www.biodiversity.be Université Libre de Bruxelles (ULB) Campus de la Plaine CP 257 Bâtiment NO, Bureau 4 N4 115C (Niveau 4) Boulevard du Triomphe, entrée ULB 2 B-1050 Bruxelles Mail: jci...@ulb.ac.be @biobel: http://biobel.biodiversity.be/person/show/471 Tel : 02 650 57 52 ___ 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
Can't Upgrade Python Through Ports
Hi; I have python 2.3.5 and I'd like to upgrade to 2.4.3. I've tried installing from FreeBSD ports and the oldfashioned way from source code, with the configure make make install dance, and still when I call up my python interpreter it tells me I'm in 2.3.5! Why? I didn't do altinstall! What gives? TIA, Ted2 - Stay in the know. Pulse on the new Yahoo.com. Check it out. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't Upgrade Python Through Ports
Try the following in the python port directory: make install clean On 10/2/06, Ted Johnson [EMAIL PROTECTED] wrote: Hi; I have python 2.3.5 and I'd like to upgrade to 2.4.3. I've tried installing from FreeBSD ports and the oldfashioned way from source code, with the configure make make install dance, and still when I call up my python interpreter it tells me I'm in 2.3.5! Why? I didn't do altinstall! What gives? TIA, Ted2 - Stay in the know. Pulse on the new Yahoo.com. Check it out. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Best Regards, Ivan Levchenko [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: Can't Upgrade Python Through Ports
Right. I tried that before writing, but I forgot to specify as much. No, that didn't work either. Here are a couple of peculiarities: * I took over this box from someone who didn't know the difference between FreeBSD and Linux. So, he built the original Python in a different dir. * The original python powers several Zope instances. Having said as much, years ago I had two versions of python running, one for Zope and one for everything else. So this should work. Anyway, it doesn't! More ideas? TIA. Ted Ivan Levchenko [EMAIL PROTECTED] wrote: Try the following in the python port directory: make install clean On 10/2/06, Ted Johnson wrote: Hi; I have python 2.3.5 and I'd like to upgrade to 2.4.3. I've tried installing from FreeBSD ports and the oldfashioned way from source code, with the configure make make install dance, and still when I call up my python interpreter it tells me I'm in 2.3.5! Why? I didn't do altinstall! What gives? TIA, Ted2 - Stay in the know. Pulse on the new Yahoo.com. Check it out. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Best Regards, Ivan Levchenko [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't Upgrade Python Through Ports
What are the error messages? On 10/2/06, Ted Johnson [EMAIL PROTECTED] wrote: Right. I tried that before writing, but I forgot to specify as much. No, that didn't work either. Here are a couple of peculiarities: * I took over this box from someone who didn't know the difference between FreeBSD and Linux. So, he built the original Python in a different dir. * The original python powers several Zope instances. Having said as much, years ago I had two versions of python running, one for Zope and one for everything else. So this should work. Anyway, it doesn't! More ideas? TIA. Ted Ivan Levchenko [EMAIL PROTECTED] wrote: Try the following in the python port directory: make install clean On 10/2/06, Ted Johnson wrote: Hi; I have python 2.3.5 and I'd like to upgrade to 2.4.3. I've tried installing from FreeBSD ports and the oldfashioned way from source code, with the configure make make install dance, and still when I call up my python interpreter it tells me I'm in 2.3.5! Why? I didn't do altinstall! What gives? TIA, Ted2 - Stay in the know. Pulse on the new Yahoo.com. Check it out. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Best Regards, Ivan Levchenko [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Best Regards, Ivan Levchenko [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: Can't Upgrade Python Through Ports
--- Ted Johnson [EMAIL PROTECTED] wrote: Hi; I have python 2.3.5 and I'd like to upgrade to 2.4.3. I've tried installing from FreeBSD ports and the oldfashioned way from source code, with the configure make make install dance, and still when I call up my python interpreter it tells me I'm in 2.3.5! Why? I didn't do altinstall! What gives? TIA, Ted2 Where is the 2.3.5 version installed? Perhaps it is installed in a directory earlier in your PATH than the 2.4.3 versions directory(/usr/local/bin/). __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't Upgrade Python Through Ports
When I read your answer I *knew* you were right! And right you were! Thanks! Ted2 Dave McCammon [EMAIL PROTECTED] wrote: --- Ted Johnson wrote: Hi; I have python 2.3.5 and I'd like to upgrade to 2.4.3. I've tried installing from FreeBSD ports and the oldfashioned way from source code, with the configure make make install dance, and still when I call up my python interpreter it tells me I'm in 2.3.5! Why? I didn't do altinstall! What gives? TIA, Ted2 Where is the 2.3.5 version installed? Perhaps it is installed in a directory earlier in your PATH than the 2.4.3 versions directory(/usr/local/bin/). __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - Want to be your own boss? Learn how on Yahoo! Small Business. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrade sendmail via ports - version in smtp greeting doesn't match
All: Not a major issue, but I've upgraded sendmail on a 4.11 box via the ports. All appears to be working, but if I look at the SMTP greeting, the version of sendmail or the config version is incorrect. The latter version (8.13.1) would have been the version prior to the port upgrade. 220 mail.domain.com ESMTP Sendmail 8.13.5/8.13.1; From memory, I think the first number is the sendmail version and the second the config version. I've done the make all, make install, make install-cf etc. from /etc/mail and also done a make mailer.conf from the sendmail ports directory. Any help on what I should do here would be appreciated. Thanks, Barry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrade sendmail via ports - version in smtp greeting doesn't match
Seem to have solved this. Not sure it's the correct thing to do, but modified the Makefile in /etc/mail by adding a check for /usr/local/share/sendmail/cf for the config files. Seems to be OK now. - Barry -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Barry Byrne Sent: 25 January 2006 11:26 To: freebsd-questions@freebsd.org Subject: Upgrade sendmail via ports - version in smtp greeting doesn't match All: Not a major issue, but I've upgraded sendmail on a 4.11 box via the ports. All appears to be working, but if I look at the SMTP greeting, the version of sendmail or the config version is incorrect. The latter version (8.13.1) would have been the version prior to the port upgrade. 220 mail.domain.com ESMTP Sendmail 8.13.5/8.13.1; From memory, I think the first number is the sendmail version and the second the config version. I've done the make all, make install, make install-cf etc. from /etc/mail and also done a make mailer.conf from the sendmail ports directory. Any help on what I should do here would be appreciated. Thanks, Barry ___ 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]
upgrade then no ports
I have Freebsd 5.4 on all my servers. It had been a while since the initial load so I decided to upgrade all source code via cvsup and then ran make buildworld, make buildkernel, make installkernel. After all was said and done everything booted fine and all was working well. When I went to install a new port I noticed that all my ports were gone. All that is in my /usr/ports/ directory are the directories distfiles, and dns and a INDEX-5 file. I ran my ports-supfile for all-ports and it appeared to be installing but when it's done the /usr/ports/ directory is unchanged. When I went to install through sysinstall evey ftp site gives me this: Warning: Can't find the '5.4-RELEASE-p8' distribution on this FTP server. I still consider myself a Freebsd newbie and feel I've probably missed something simple but I have had no luck searching the net or bsd site. Thanks in advance, Steve L __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade then no ports
On Monday 19 December 2005 13:53, steve lasiter wrote: I have Freebsd 5.4 on all my servers. It had been a while since the initial load so I decided to upgrade all source code via cvsup and then ran make buildworld, make buildkernel, make installkernel. After all was said and done everything booted fine and all was working well. When I went to install a new port I noticed that all my ports were gone. All that is in my /usr/ports/ directory are the directories distfiles, and dns and a INDEX-5 file. I ran my ports-supfile for all-ports and it appeared to be installing but when it's done the /usr/ports/ directory is unchanged. When I went to install through sysinstall evey ftp site gives me this: Warning: Can't find the '5.4-RELEASE-p8' distribution on this FTP server. I still consider myself a Freebsd newbie and feel I've probably missed something simple but I have had no luck searching the net or bsd site. Thanks in advance, Steve L In your ports-sup file do you have this line? *default tag=. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade then no ports
On Monday 19 December 2005 14:00, steve lasiter wrote: --- Michael C. Shultz [EMAIL PROTECTED] wrote: On Monday 19 December 2005 13:53, steve lasiter wrote: I have Freebsd 5.4 on all my servers. It had been a while since the initial load so I decided to upgrade all source code via cvsup and then ran make buildworld, make buildkernel, make installkernel. After all was said and done everything booted fine and all was working well. When I went to install a new port I noticed that all my ports were gone. All that is in my /usr/ports/ directory are the directories distfiles, and dns and a INDEX-5 file. I ran my ports-supfile for all-ports and it appeared to be installing but when it's done the /usr/ports/ directory is unchanged. When I went to install through sysinstall evey ftp site gives me this: Warning: Can't find the '5.4-RELEASE-p8' distribution on this FTP server. I still consider myself a Freebsd newbie and feel I've probably missed something simple but I have had no luck searching the net or bsd site. Thanks in advance, Steve L In your ports-sup file do you have this line? *default tag=. -Mike Michael, Yes, I have *default release=cvs tag=RELENG_5_4 Change it to *default release=cvs tag=. see man cvsup (note the .) -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade then no ports
On Monday 19 December 2005 14:04, Michael C. Shultz wrote: On Monday 19 December 2005 14:00, steve lasiter wrote: --- Michael C. Shultz [EMAIL PROTECTED] wrote: On Monday 19 December 2005 13:53, steve lasiter wrote: I have Freebsd 5.4 on all my servers. It had been a while since the initial load so I decided to upgrade all source code via cvsup and then ran make buildworld, make buildkernel, make installkernel. After all was said and done everything booted fine and all was working well. When I went to install a new port I noticed that all my ports were gone. All that is in my /usr/ports/ directory are the directories distfiles, and dns and a INDEX-5 file. I ran my ports-supfile for all-ports and it appeared to be installing but when it's done the /usr/ports/ directory is unchanged. When I went to install through sysinstall evey ftp site gives me this: Warning: Can't find the '5.4-RELEASE-p8' distribution on this FTP server. I still consider myself a Freebsd newbie and feel I've probably missed something simple but I have had no luck searching the net or bsd site. Thanks in advance, Steve L In your ports-sup file do you have this line? *default tag=. -Mike Michael, Yes, I have *default release=cvs tag=RELENG_5_4 Change it to *default release=cvs tag=. see man cvsup (note the .) -Mike Here is a better reference, the man page won't help you http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html Warning: Be very careful to specify any tag= fields correctly. Some tags are valid only for certain collections of files. If you specify an incorrect or misspelled tag, CVSup will delete files which you probably do not want deleted. In particular, use only tag=. for the ports-* collections. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade then no ports
On Monday 19 December 2005 14:59, steve lasiter wrote: Thanks Mike, That did it. Do you think the upgrade of my system wasn't really an upgrade at all now due to that? Steve L ports and src are different things, it depends on how you had your cvs-src files set up. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrade python from ports
I am relatively new to ports. When I type pkg_info, this is what I have for python: py23-MySQLdb-1.2.0_1 Access a MySQL database through Python py23-mx-base-2.0.5 The eGenix mx-Extension Series for Python py23-reportlab-1.19 Library to create PDF documents using the Python language py23-xml-0.8.4 PyXML: Python XML library enhancements py24-statgrab-0.3 A set of Python bindings for libstatgrab python-2.3.4_4 An interpreted object-oriented programming language python-2.4_1An interpreted object-oriented programming language I want to upgrade my python from 2.3.4 to 2.3.5. To I deinstall all py23 ports and python-2.3.4_4 and reinstall or do I run an portupgrade somewhere that will take care of this or do I just install python-2.3.5 In my /usr/local/lib: I have: python2.3 python2.4 What is right approach to updating only my python 2.3 so that it will be right for all py23. I don't want to have two separate versions of 2.3 only update version to 2.3.5 Many thanks David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: re portmanager, how to prevent upgrade of held ports
On Friday 31 December 2004 23:32, Michael C. Shultz wrote: On Friday 31 December 2004 09:49 am, nbco wrote: Any ideas as to how to make portmanager ignore held ports? If you were to move /var/db/pkg/openoffice-1.1.4.20041101_1 (assuming that is the version you have installed) directory to someplace safe, like in your home directory then portmanager nor any part of the ports system would know openoffice-1.1.4.20041101_1 is installed. This will only work for a port that is not a dependency for another port so only if no other ports depend on openoffice-1.1.4.20041101_1 will this work. When you want to upgrade it then move the directory back to /var/db/pkg. You can also create a ports/local/editors/openoffice-1.1which is a bit more involved and way more elegant, I will be happy to explain only if you are truly interested. Many thanks, the first option worked perfectly, inelegant though it may be. .nbco ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
re portmanager, how to prevent upgrade of held ports
Hi list, I am trying out portmanager-0.2.2, on a 5.3-RELEASE box. I have openoffice-1.1.3.20040810 installed. I don't want to upgrade openoffice at this time, as I don't have the space for a full compile and will wait for a new package. I have set openoffice to be held in pkgtools.conf in /usr/local/etc. Portupgrade honours this setting. Portmanager doesn't, therefore every time I attempt to run portmanager it tries to compile openoffice-1.1.4.20041101_1 I have looked at portmanager and cannot find a way to prevent it updating certain ports, and it doesn't honour the hold_pkgs in pkgtools.conf. Any ideas as to how to make portmanager ignore held ports? This problem makes portmanager unusable for me, as it updates openoffice first, so it never actually gets to the smaller out of date ports. Many thanks in advance .nbco ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: re portmanager, how to prevent upgrade of held ports
On Friday 31 December 2004 09:49 am, nbco wrote: Hi list, I am trying out portmanager-0.2.2, on a 5.3-RELEASE box. I have openoffice-1.1.3.20040810 installed. I don't want to upgrade openoffice at this time, as I don't have the space for a full compile and will wait for a new package. I have set openoffice to be held in pkgtools.conf in /usr/local/etc. Portupgrade honours this setting. Portmanager doesn't, therefore every time I attempt to run portmanager it tries to compile openoffice-1.1.4.20041101_1 I have looked at portmanager and cannot find a way to prevent it updating certain ports, and it doesn't honour the hold_pkgs in pkgtools.conf. Any ideas as to how to make portmanager ignore held ports? This problem makes portmanager unusable for me, as it updates openoffice first, so it never actually gets to the smaller out of date ports. Portmanager has no way to ignore ports that need updating, but others have also requested this feature so I will implement it in version 0.2.3. It may be a few weeks before it is ready because I am taking advantage of the port freeze and making fairly extensive changes. There is one thing you can do in the mean time as a work around if you still want to use portmanager: If you were to move /var/db/pkg/openoffice-1.1.4.20041101_1 (assuming that is the version you have installed) directory to someplace safe, like in your home directory then portmanager nor any part of the ports system would know openoffice-1.1.4.20041101_1 is installed. This will only work for a port that is not a dependency for another port so only if no other ports depend on openoffice-1.1.4.20041101_1 will this work. When you want to upgrade it then move the directory back to /var/db/pkg. You can also create a ports/local/editors/openoffice-1.1which is a bit more involved and way more elegant, I will be happy to explain only if you are truly interested. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proper way to upgrade packaes from ports
At 03:39 PM 10/7/02 -0700, you wrote: From: Andrew Knapp [EMAIL PROTECTED] Date: Mon, 7 Oct 2002 18:18:22 -0400 AFAIK, doesn't portupgrade come with another utility called portversion? I use portversion -r (for recursive) to figure out what packages I do need to upgrade. It gives a nice read-out of what to upgrade. Yes, portversion is a part of portupgrade. It should do almost anything pkg_version does except -c. Excuse me? I've been using portversion -c since I installed the damned thing and it does for portupdate exactly what pkg_version -c did for pre-portupdate updating. I would regard it as a boon if the script didn't sometimes do things (at least when run remotely) that cause my machine to reboot spontaneously (fatal trap 12). I use portversion -vL= to check on what needs updating. But I then usually do portupgrade -Rra which will upgrade all ports that are out of date and do so in the correct bottom-up order. sigh wish I had that much disk space. I can only afford to install a few ports. snip The biggest down-side is the requirement that I run portsdb -Uu to update the databases after a cvsup of the ports tree. This is a pretty CPU intensive operation and can take a while on an older system. Yeah, it takes around 16 hours on my system, and usually causes a spontaneous reboot if I do it remotely (fatal trap 12). I haven't figured out a way to find out what it's doing to cause the reboots, since there seems to be no particular reason for fatal trap 12 (what I mean is the error message fatal trap 12 does not indicate one particular type of failure; I usually get the further message Page fault in kernel mode, which also doesn't seem to identify any particular type of problem). R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Roger To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Proper way to upgrade packaes from ports
On Mon, Oct 07, 2002 at 09:00:49AM +0100, Rus Foster wrote: I've got a general question. Say I've install /usr/ports/net/foobar_0.1, I do a cvsup and see new foo_bar0.2. What is the best way to upgrade? Either pkg_rm foobar_0.1 + pkg_add foobar_0.2, force the installation of 0.2 or is there some other way? The third way: which is to install and use portupgrade -- it's in ports/sysutils/portupgrade. Generally, directories under /usr/ports don't have any sort of version information in the name, with some exceptions. Updating those ports is handled very smoothly by portupgrade. However, if there are two different versioned ports, eg. www/apache13 and www/apache2, (or even www/mozilla and www/mozilla-devel), then they are separate ports. Don't assume that just because they have similar names that one can be trivially substituted for the other. Sometimes you can, but more usually it takes a lot of bodging around to sort out dependencies and so forth if it can be done at all. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Proper way to upgrade packaes from ports
Rus, Please take a look at /usr/ports/sysutils/portupgrade, as it is the appropriate tool for these sort of upgrades. Circumstantial evidence over the years has led me to believe that most ports will actually successfully and without issue overwrite their previous iterations that were also installed via the ports tree (lynx, wget, things like that). - John Kozubik - [EMAIL PROTECTED] - http://www.kozubik.com On Mon, 7 Oct 2002, Rus Foster wrote: Hi All, I've got a general question. Say I've install /usr/ports/net/foobar_0.1, I do a cvsup and see new foo_bar0.2. What is the best way to upgrade? Either pkg_rm foobar_0.1 + pkg_add foobar_0.2, force the installation of 0.2 or is there some other way? Rgds Rus -- http://www.fsck.me.uk - Rant wibble wave http://shells.fsck.me.uk - Hosting and stuff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Proper way to upgrade packaes from ports
Date: Mon, 07 Oct 2002 14:49:23 -0500 From: Jack L. Stone [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] At 12:21 PM 10.7.2002 -0700, John Kozubik wrote: Rus, Please take a look at /usr/ports/sysutils/portupgrade, as it is the appropriate tool for these sort of upgrades. Circumstantial evidence over the years has led me to believe that most ports will actually successfully and without issue overwrite their previous iterations that were also installed via the ports tree (lynx, wget, things like that). - John Kozubik - [EMAIL PROTECTED] - http://www.kozubik.com If you don't mind first deinstalling the old port, then a simple way is to: # pkg_delete foo_1 ...then cd /usr/ports/foo_2: #make install clean You are now up to date. This ignores dependencies. If I upgrade some port but don't get the dependencies as well, things can break. portupgrade was designed to handle these. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Proper way to upgrade packaes from ports
Kevin Oberman wrote: Date: Mon, 07 Oct 2002 14:49:23 -0500 From: Jack L. Stone [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] At 12:21 PM 10.7.2002 -0700, John Kozubik wrote: Rus, Please take a look at /usr/ports/sysutils/portupgrade, as it is the appropriate tool for these sort of upgrades. Circumstantial evidence over the years has led me to believe that most ports will actually successfully and without issue overwrite their previous iterations that were also installed via the ports tree (lynx, wget, things like that). - John Kozubik - [EMAIL PROTECTED] - http://www.kozubik.com If you don't mind first deinstalling the old port, then a simple way is to: # pkg_delete foo_1 ...then cd /usr/ports/foo_2: #make install clean You are now up to date. This ignores dependencies. If I upgrade some port but don't get the dependencies as well, things can break. portupgrade was designed to handle these. Some of these are handled when I do a -Rufp. It starts at the port and handles all of its dependancies. This isn't a good idea if XFree86 is one of the dependancies. Then -x option is supposed to take care of that but I have never used it. I have usually done a pkg_version -c and know what needs to be updated. When something disappears, which portupgrade does not handle, I delete the port and the new dependancies and start over. FWIW, I usually portupgrade on one system and I always create a package on that system. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Proper way to upgrade packaes from ports
Kent Stewart wrote: I have usually done a pkg_version -c and know what needs to be updated. I use the pkg_version -c method as well-- it seems so much simpler than portupgrade, but am I missing something and/or running the risk of breaking things? FWIW I think that keeping your ports/packages up-to-date could be covered better in the Handbook, considering how important it is in terms of security. There's no mention of either portupgrade or pkg_version in the ports/packages coverage. chris. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Proper way to upgrade packaes from ports
Date: Mon, 07 Oct 2002 17:23:40 -0400 From: Chris Snyder [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Kent Stewart wrote: I have usually done a pkg_version -c and know what needs to be updated. I use the pkg_version -c method as well-- it seems so much simpler than portupgrade, but am I missing something and/or running the risk of breaking things? FWIW I think that keeping your ports/packages up-to-date could be covered better in the Handbook, considering how important it is in terms of security. There's no mention of either portupgrade or pkg_version in the ports/packages coverage. The -c option to pkg_version is NOT safe. The message it puts out makes this clear. I think Bruce said that he was planning on pulling it once portupgrade stabilized because it was just too dangerous. It has no intelligence on the dependencies and does not always do things in the proper order. To do this properly you need to completely graph all dependencies and their versions and update from the bottom of the graph. I think it was Bruce's comments on this that led knu to write portupgrade. I'm sure that portupgrade would be in the base system except for the dependency on ruby, just as cvsup would if not for the Mobula III requirement. But both are nearly essential to maintaining a robust system. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Proper way to upgrade packaes from ports
in message [EMAIL PROTECTED], wrote Kevin Oberman thusly... The biggest down-side is the requirement that I run portsdb -Uu to update the databases after a cvsup of the ports tree. This is a pretty CPU intensive operation and can take a while on an older system. as i understand portsupgrade, portsdb -U would create the the index as if you had typed make index in your ports ($PORTSDIR). if you don't have the INDEX reflecting the current ports tree, things may go out of hand. such making of INDEX is part of freebsd ports (not portsupgrade). actually, after INDEX is made, portsdb -u finishes lighting fast ... in comparison. for me, creating the INDEX takes less time than updating it cvsup over a dialup connection. i don't have problem w/ the creation process being CPU intensive; bottleneck on my system is heavy disk activity. - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Proper way to upgrade packaes from ports
From: Andrew Knapp [EMAIL PROTECTED] Date: Mon, 7 Oct 2002 18:18:22 -0400 AFAIK, doesn't portupgrade come with another utility called portversion? I use portversion -r (for recursive) to figure out what packages I do need to upgrade. It gives a nice read-out of what to upgrade. Yes, portversion is a part of portupgrade. It should do almost anything pkg_version does except -c. I use portversion -vL= to check on what needs updating. But I then usually do portupgrade -Rra which will upgrade all ports that are out of date and do so in the correct bottom-up order. portupgrade also includes pkgtools which lets you establish routine options you always use for installing a certain port. For example, the make option to use the MGA driver for a Matrox card instead of the XFree86 driver or to build Galeon with full mozilla. The file /usr/local/etc/pkgtools.conf lets you stop automatic upgrade of some ports and many other things to make keeping ports current quite easy. The biggest down-side is the requirement that I run portsdb -Uu to update the databases after a cvsup of the ports tree. This is a pretty CPU intensive operation and can take a while on an older system. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
