Re: New ports on older stable (4.11)
I still share a part of your trepidation about getting oneself into a bind with uncooperative dependencies, etc. However, I have had more success than I would have imagined. Thats good to hear. What I am intending to do is to backup the whole ports tree, try and do the upgrade, and if it doesnt work then just go and rebuild all the old ones instead. Go slow, read Makefiles first, that sort of thing. You can probably install portupgrade without too much trouble, as it doesn't have a lot Never used portupgrade and am not really in the mood for investigating exciting new software at the same time as the upgrade. My normal procedure is to backup the config files and then delete every single port on the system, until I get nothing out of pkg_info. Then start re-installing one by one, starting with the mail system and finishing woth the webserver. Just for prurient interest, would you care to post your pkg_info? If you have portupgrade installed, or can install it, how about the output from portupgrade -na also. Sure, see the end of this email We have two things not included - which are mailman and python. I'd love those to be from ports, but the guy who originally installed them did them from the tarfiles. As a result puthon seems to use a different encryption to the one in prst, so if I move to using python from ports then none of the passwords work. This has been bugging me since FreeBSD 3, so any suggestions there would be welcome. Meanwhile heres the pkg_info for those interested... -pete. BitchX-1.1 An alternative ircII color client with optional GTK/GNOME analog-5.32_3,1 An extremely fast program for analysing WWW logfiles apache-1.3.33_1 The extremely popular Apache http server. Very fast, very arc-5.21j Create extract files from DOS .ARC files autoconf-2.13.000227_5 Automatically configure source code on many Un*x platforms autoconf-2.53_3 Automatically configure source code on many Un*x platforms automake-1.4.6_1GNU Standards-compliant Makefile generator (legacy version automake-1.5_2,1GNU Standards-compliant Makefile generator (version 1.5) bash-2.05b.007_2The GNU Bourne Again Shell bison-1.75_2A parser generator from FSF, (mostly) compatible with Yacc bitlbee-0.92An IRC to other chat networks gateway bogofilter-0.92.8 Fast, teachable, learning spam detector clamav-0.83 Command line virus scanner written entirely in C cpdup-1.05 A comprehensive filesystem mirroring program ctorrent-1.3.4 BitTorrent Client written in C for FreeBSD and Linux db42-4.2.52_3 The Berkeley DB package, revision 4.2 demime-1.1d A tool to scrub mime from mailing lists docbook-1.3 Meta-port for the different versions of the DocBook DTD docbook-241_2 V2.4.1 of the DocBook DTD, designed for technical documenta docbook-3.0_2 V3.0 of the DocBook DTD, designed for technical documentati docbook-3.1_2 V3.1 of the DocBook DTD, designed for technical documentati docbook-4.0_2 V4.0 of the DocBook DTD, designed for technical documentati docbook-4.1_2 V4.1 of the DocBook DTD, designed for technical documentati docbook-xml-4.2_1 XML version of the DocBook DTD exim-4.43+28_1 High performance MTA for Unix systems on the Internet expat-1.95.8XML 1.0 parser written in C freetype2-2.1.7_4 A free and portable TrueType font rendering engine gd-2.0.33_1,1 A graphics library for fast creation of images gettext-0.14.1 GNU gettext package ghc-6.2.2 A Compiler for the functional language Haskell glib-2.4.8 Some useful routines of C programming (current stable versi gmake-3.80_2GNU version of 'make' utility gsl-1.5 The GNU Scientific Library - mathematical libs help2man-1.34.2 Automatically generating simple manual pages from program o ircii-20040216 The 'Internet Relay Chat' and 'Internet Citizens Band' Clie iso8879-1986_2 Character entity sets from ISO 8879:1986 (SGML) ispell-3.2.06_12An interactive spelling checker for multiple languages ja-p5-Jcode-0.87Perl extension interface to convert Japanese text jpeg-6b_3 IJG's jpeg compression utilities lha-1.14i_6 Archive files using LZSS and Huffman compression (.lzh file libgmp-4.1.3A free library for arbitrary precision arithmetic libgnugetopt-1.2GNU getopt library libiconv-1.9.2_1A character set conversion library libtool-1.3.5_2 Generic shared library support script (version 1.3) libtool-1.5.10 Generic shared library support script (version 1.5) linuxdoc-1.1_1 The Linuxdoc SGML DTD lynx-ssl-2.8.5 A non-graphical, text-based World-Wide Web client with SSL m4-1.4.1GNU m4 mtr-nox11-0.65_1Traceroute and ping in a single graphical network diagnosti mutella-0.4.5,1 A command line Gnutella client mutt-1.4.2.1_1 The Mongrel of Mail User Agents (part Elm, Pine, Mush, mh,
Re: New ports on older stable (4.11)
On Thu, Mar 02, 2006 at 11:41:28AM +, Pete French wrote: I still share a part of your trepidation about getting oneself into a bind with uncooperative dependencies, etc. However, I have had more success than I would have imagined. Thats good to hear. What I am intending to do is to backup the whole ports tree, try and do the upgrade, and if it doesnt work then just go and rebuild all the old ones instead. if you have the place to spare you might want to do this inside a chroot-environment - so if everything goes as expected, you have all the ports available as packages already, and if it doesn't you don't have to revert everything again... Regards, Holger Kipp ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New ports on older stable (4.11)
Chiming in a little bit late. I have a hosting server that's running a patched version of FreeBSD 4.9 and regularly update the ports on it from the ports tree with few if any problems. Mail, web, php, etc. The only port I have installed that won't update is rar, and it's marked as broken in the port makefile. (unrar is fine, btw). JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New ports on older stable (4.11)
On Mar 1, 2006, at 6:05 AM, Pete French wrote: I dont know how backward compatible ports are ggenerally, but I have a 4.11 machine that I really want to upgrade the ports on. But I dont know if they will alla ctually compile, and I dont wnat to start doing the process only to find that I cant build one of them possibly. Does anybody know if this is likely to work, or is it simply unsupported ? i have several 4.11 machines in service with ports mostly up-to- date. what you can do is cd to the port and run make. If it builds chances are it will work, then you can do the necessary port upgrades. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New ports on older stable (4.11)
Vivek Khera wrote: On Mar 1, 2006, at 6:05 AM, Pete French wrote: I dont know how backward compatible ports are ggenerally, but I have a 4.11 machine that I really want to upgrade the ports on. But I dont know if they will alla ctually compile, and I dont wnat to start doing the process only to find that I cant build one of them possibly. Does anybody know if this is likely to work, or is it simply unsupported ? i have several 4.11 machines in service with ports mostly up-to-date. what you can do is cd to the port and run make. If it builds chances are it will work, then you can do the necessary port upgrades. I've done a similar thing on a creaky old P-III lab router/firewall that didn't really need replacing before death, was too slow to bother with religiously updating, yet still needed some degree of ports currency for specific lab scenarios. Using portversion to preview what needs making and portupgrade -aF to prefetch the sources (after doing cvsup ports and make fetchindex) can help streamline your trial and error process. The OP had spake thusly in a prior msg: Never used portupgrade and am not really in the mood for investigating exciting new software at the same time as the upgrade. With sysadmin mood having a lot of influence re: success rates, do what you like, of course. But portupgrade and friends (and competitors) can save you a lot of time and grief. On the other hand, I'm not sure it'd be very happy when you first fire it up on an old box where a lot of manual ports management has already occurred, and cleaning up a messed package database is probably the least fun aspect of portupgrade. The best time to learn it might be the next time you do a clean install of say, 6.1. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) gregb at scls.lib.wi.us, (608) 266-6348 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New ports on older stable (4.11)
99.9% of ports seems to work ... I've hit a few that are marked as BROKEN, like postgis stuff, but nothing that I'd considered mainstream ... On Wed, 1 Mar 2006, Pete French wrote: I dont know how backward compatible ports are ggenerally, but I have a 4.11 machine that I really want to upgrade the ports on. But I dont know if they will alla ctually compile, and I dont wnat to start doing the process only to find that I cant build one of them possibly. Does anybody know if this is likely to work, or is it simply unsupported ? I;d love to upgrade the machine to 6.1 - but I have no physical access to it, nor am I likely to get any for the forseeable future, and upgrading across the 4/5 boundary isn't something I would be happy doing remotiley in multi-user mode (if it's even possible!) -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New ports on older stable (4.11)
99.9% of ports seems to work ... I've hit a few that are marked as BROKEN, like postgis stuff, but nothing that I'd considered mainstream ... Ah, thats great to know, hanks. It's the exim/clamav/spamassassin stuff which I really want to upgrade. cheers, -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New ports on older stable (4.11)
On Wed, 1 Mar 2006, Pete French wrote: 99.9% of ports seems to work ... I've hit a few that are marked as BROKEN, like postgis stuff, but nothing that I'd considered mainstream ... Ah, thats great to know, hanks. It's the exim/clamav/spamassassin stuff which I really want to upgrade. I dont' use exim, so can't comment on that, but I've just gone through and upgraded my amavis/clamav/spamassassin install without any hassles ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: New ports on older stable (4.11)
I have Exim/ClamAV and SpamAssassin from Ports on a 4.11 system. Works fine :) LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New ports on older stable (4.11)
On Wed, Mar 01, 2006 at 03:09:24PM +, Pete French wrote: 99.9% of ports seems to work ... I've hit a few that are marked as BROKEN, like postgis stuff, but nothing that I'd considered mainstream ... Ah, thats great to know, hanks. It's the exim/clamav/spamassassin stuff which I really want to upgrade. My upgrade procedure includes: 1. Backup ports with ports/sysutils/portupgrade. (-b switch) 2. Update the ports collection and index 3. Read ports/UPDATING 4. Upgrade and verify each port individually 5. Keep ports/sysutils/portdowngrade handy -- Kelly D. Grills [EMAIL PROTECTED] pgp7Ys3c1C24n.pgp Description: PGP signature
Re: New ports on older stable (4.11)
Date: Wed, 01 Mar 2006 11:05:13 + From: Pete French [EMAIL PROTECTED] Subject: New ports on older stable (4.11) To: freebsd-stable@freebsd.org Message-ID: [EMAIL PROTECTED] I dont know how backward compatible ports are ggenerally, but I have a 4.11 machine that I really want to upgrade the ports on. But I dont know if they will alla ctually compile, and I dont wnat to start doing the process only to find that I cant build one of them possibly. Does anybody know if this is likely to work, or is it simply unsupported ? I;d love to upgrade the machine to 6.1 - but I have no physical access to it, nor am I likely to get any for the forseeable future, and upgrading across the 4/5 boundary isn't something I would be happy doing remotiley in multi-user mode (if it's even possible!) -pcf. This is rather a case of the extremely near-sighted leading the blind, but I recently inherited the care of some older boxen, and in fact, recently deployed a new 4.11 installation, and proceeded to build up-to-date ports on it. I still share a part of your trepidation about getting oneself into a bind with uncooperative dependencies, etc. However, I have had more success than I would have imagined. Here are some suggestions, and I certainly welcome corrections to my advice from more expert sources. Start by backing up your /usr/ports and your /var/db/pkg and /var/db/ports and anything else you can think of. Heck, back up the whole samn dystem if you can. To paraphrase Douglas Adams, the universe is a lot safer if you have a backup. I should think portaudit would be the first thing you'd want to install, so that you can find out if other ports have security problems. Go slow, read Makefiles first, that sort of thing. You can probably install portupgrade without too much trouble, as it doesn't have a lot of dependencies. Then a lot of use of portupgrade -nR (portname) will tell you which ports have the fewest dependencies, and -nr (portname) will tell you which ports depend on any given port you may be thinking about upgrading. Just for prurient interest, would you care to post your pkg_info? If you have portupgrade installed, or can install it, how about the output from portupgrade -na also. Jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
