Re: pkg_upgrade seems to try server that isn't right
On 10/10/2011 2:13 PM, Conrad J. Sabatier wrote: On Sun, 9 Oct 2011 09:33:41 +0100 Mike Clarkejmc-freeb...@milibyte.co.uk wrote: On Sunday 09 October 2011, Conrad J. Sabatier wrote: I assume you mean pkg_upgrade (not upgrade_pkg)? See the ENVIRONMENT section of the man page. All of the pkg_* tools are consistent in how they reference these variables. Thanks. I'll look into this. It took me a while to reply I know, I've been busy the last few weeks and haven't really had much time to do much so, sorry about taking forever to reply. I appreciate any help given. There isn't a pkg_upgrade in the base system and I'm not aware of one in ports either but I'm open to correction. There is a python script, pkgupgrade, developed by Michel Talon which might meet the OP's needs http://www.lpthe.jussieu.fr/~talon/. Alternatively the OP could use either portmaster or portupgrade from ports, both of these can be forced to use packages instead of building from source by using the -P or -PP options. Whoops. My mistake: $ pkg_which `which pkg_upgrade` bsdadminscripts-6.1.1_1 Yea, that's one of the things I've installed. I in general have a very distinct way I install FreeBSD, and, really, ANY OS I use, which is basically the Net Install CD. I've been using Net Install for some time now because I like it, and I first started doing this when I realized one day during a Debian install, that I REALLY didn't feel like downloading 14 CDs, when in reality, I only wanted a certain number of Packages, so, I looked around, and saw that the Net Installer was not only a fairly small CD, but ONE CD, and I could tell it what I wanted to do exactly. Debian's fairly similar to FreeBSD in that respect; It has the Net Installer Option, and, the APT system with apt-get install, is a lot like FreeBSD's pkg_add -r option, and I like that a lot. So basically, after I downloaded the ISO file for the Net Installer, I booted from it, installed, and then, I loaded up a Terminal, and started adding exactly what I wanted to install. I installed some normal stuff, like Gnome, KDE, Enlightenment, E-Term, and a few others, and once I had all that going, I started just adding what I actually wanted. When I started downloading a new version of FreeBSD, I noticed that it too had this option the entire time, and after feeling a little bit stupid for not realizing it sooner, I started using it right away. I haven't downloaded an entire set in some time. Basically, I like very much how FreeBSD and Debian share a common ground in this respect. I usually grab a CD for FreeBSD, then, once I've booted from the CD, I tell it to use an FTP Server for installation, and I install the Base system only. This came from me wanting to install FreeBSD, and the Ports Collection, and then, realizing that the FreeBSD Installer, does NOT have an option to skip anything. I got stuck in an infinite loop while it tried, over and over again, to install a certain couple of Ports that were required, and I couldn't get it to skip that Port. I'd Love it if FreeBSD started doing this, as it would be a lot easier. I mean if you have a Dependency that doesn't want to install, or fails to install period, it would be nice for it to ask you Would you like to skip this for now, and all required ports that depend on it? But, it doesn't. So, for now, I just do a Net Install, get the Base System done, and once I finish with that, I boot up, log in, and once I finish logging in, I either use pkg_add -r, or, I load sysinstall, and then I select the Ports / Packages I want to install, usually in a batch kind of style; I'll select one section of them categories, and start selecting what I want, then let it install. Once that finishes up, I'll load up /etc/rc.conf and add Linux BASE and all that, and then grab the Packages for that and a few other things. In general I want to have a selection of text editors, and I use both VI, Vim, and Emacs, and a few others, and then of course Window Maker and so on, and once I finish up, I have my system exactly how I want it. I've written multiple installation HOWTOs for FreeBSD, Linux, and dual booting with FreeBSD, Linux, and Windows, and of course, one file I did for AntiOnline, which was titled FreeBSD for Linux users which was pretty popular actually; I wrote a HOWTO, and posted it, and it wasbasically meant to sort of help explain how things work in FreeBSD compared to Linux, like getting sound working, getting locate going, and a bunch more, and asked anyone who'd like to, to add in their own data, and it was actually pretty nice. Sorry about rambling on, but I haven't been around for weeks heh. Anyway, I will be checking into that, and I've saved all the mails sent about this so I can go over them. Thanks again very much, -Allen ___ freebsd-questions@freebsd.org mailing list
Re: pkg_upgrade seems to try server that isn't right
On Sunday 09 October 2011, Conrad J. Sabatier wrote: I assume you mean pkg_upgrade (not upgrade_pkg)? See the ENVIRONMENT section of the man page. All of the pkg_* tools are consistent in how they reference these variables. There isn't a pkg_upgrade in the base system and I'm not aware of one in ports either but I'm open to correction. There is a python script, pkgupgrade, developed by Michel Talon which might meet the OP's needs http://www.lpthe.jussieu.fr/~talon/. Alternatively the OP could use either portmaster or portupgrade from ports, both of these can be forced to use packages instead of building from source by using the -P or -PP options. -- Mike Clarke ___ 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: pkg_upgrade seems to try server that isn't right
On Sat, 08 Oct 2011 04:35:11 -0400 Allen unix.hac...@comcast.net wrote: [snip] I noticed a little while ago I had upgrade_pkg and since I have 0 Ports (I don't need to squeeze out extra performance, I'm not running a Server, so I only compile when I have to, and I like Binaries more so I generally install my software either with sysinstall, or, pkg_add -r whateverIWant) and then, get emailed that my software has a security flaw, and from there it usually went down hill. Well, now I have Hardware security in place, and that allowed me to not worry about it as much, su, I started reading the man page. I saw that I could do this: upgrade_pkg -a When I ran this, I noticed it was trying to get to a server about FreeBSD Release 8, and freebsd-update, uses the right one. freebsd-update grabs patches no problem, but for software packages it doesn't touch them, though I DO wish it did If I could code in C, the first thing I would do, would be to build a Package for FreeBSD that basically was like this: fbsdupdate --update --all That would download, and install, ALL Security and Bug Fixes, no matter if it was in the base system, the ports, or whatever. Since I'm no coder, I can't though. But I did wonder why it wouldn't work. I read through the man page, looking to see if it showed a file it uses to decide where to contact the server, but there isn't one. So basically, how do you make upgrade_pkg work the way it says in the man page? I basically figured I'd run upgrade_pkg -af and let it update and reinstall everything, and Hoped that would patch it, but it kept going for some FreeBSD8-RELEASE server saying it couldn't contact it, and as I said, freebsd-update works fine, grabbing things from the server for FreeBSD-RELEASE 8.2 which is what I'm running. I assume you mean pkg_upgrade (not upgrade_pkg)? See the ENVIRONMENT section of the man page. All of the pkg_* tools are consistent in how they reference these variables. -- Conrad J. Sabatier conr...@cox.net ___ 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: pkg_upgrade?
Kris Kennaway wrote: On Tue, May 30, 2006 at 08:12:25PM -0400, Joe wrote: The .ko files have a Nov 3 2005 date, whereas the files in /boot including the kernel directory have a May 6 2006 date. I take it that Nov 3 means 6.0-RELEASE since the announcement was done on Nov 4. So, I guess I'm back to the question of how to do a binary upgrade from 6.0 to 6.1 (and particularly where is this documented). Should I attempt another sysinstall Upgrade? Show me sysctl kern.version kern.version: FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Note, btw that the manpages (at least the one for sysctl) show 6.1-RELEASE at the bottom, confirming that parts of the base were indeed updated. and the output of a failed package fetch. I'll try to send that a little later but seeing the above, shouldn't I just retry the binary upgrade and if so, what precautions should I take? I'm thinking of skipping the install of X.org so that no package conflicts turn up. Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_upgrade?
Kris Kennaway wrote: On Tue, May 30, 2006 at 08:12:25PM -0400, Joe wrote: The .ko files have a Nov 3 2005 date, whereas the files in /boot including the kernel directory have a May 6 2006 date. I take it that Nov 3 means 6.0-RELEASE since the announcement was done on Nov 4. So, I guess I'm back to the question of how to do a binary upgrade from 6.0 to 6.1 (and particularly where is this documented). Should I attempt another sysinstall Upgrade? Show me sysctl kern.version and the output of a failed package fetch. Here is the output of portupgrade -PP -v expat: --- Session started at: Wed, 31 May 2006 09:21:25 -0400 --- Checking for the latest package of 'textproc/expat2' --- Found a package of 'textproc/expat2': /usr/ports/packages/All/expat-1.95.8_3.tbz (expat-1.95.8_3) --- Fetching the package(s) for 'expat-2.0.0_1' (textproc/expat2) --- Fetching expat-2.0.0_1 ++ Will try the following sites in the order named: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6.0-release/ --- Invoking a command: /usr/bin/fetch -o '/var/tmp/portupgrade8rSLsPlD/expat-2.0.0_1.tbz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6.0-release/All/expat-2.0.0_1.tbz' fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6.0-release/All/expat-2.0.0_1.tbz: File unavailable (e.g., file not found, no access) ** The command returned a non-zero exit status: 1 ** Failed to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6.0-release/All/expat-2.0.0_1.tbz --- Invoking a command: /usr/bin/fetch -o '/var/tmp/portupgrade8rSLsPlD/expat-2.0.0_1.tgz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6.0-release/All/expat-2.0.0_1.tgz' fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6.0-release/All/expat-2.0.0_1.tgz: File unavailable (e.g., file not found, no access) ** The command returned a non-zero exit status: 1 ** Failed to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6.0-release/All/expat-2.0.0_1.tgz ** Failed to fetch expat-2.0.0_1 --- Listing the results (+:done / -:ignored / *:skipped / !:failed) ! expat-2.0.0_1 (fetch error) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed --- Fetching the latest package(s) for 'expat' (textproc/expat2) --- Fetching expat ++ Will try the following sites in the order named: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6.0-release/ --- Invoking a command: /usr/bin/fetch -o '/var/tmp/portupgradeKe8LJnQa/expat.tbz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6.0-release/Latest/expat.tbz' /var/tmp/portupgradeKe8LJnQa/expat.tbz 0% of 137 kB0 Bps/var/tmp/portupgradeKe8LJnQa/expat.tbz 2% of 137 kB 32 kBps/var/tmp/portupgradeKe8LJnQa/expat.tbz 98% of 137 kB 126 kBps/var/tmp/portupgradeKe8LJnQa/expat.tbz100% of 137 kB 128 kBps --- Downloaded as expat.tbz --- Identifying the package /var/tmp/portupgradeKe8LJnQa/expat.tbz --- Saved as /usr/ports/packages/All/expat-1.95.8_3.tbz --- Listing the results (+:done / -:ignored / *:skipped / !:failed) + expat@ --- Packages processed: 1 done, 0 ignored, 0 skipped and 0 failed ** Ignoring the package, which is the same version as is installed (1.95.8_3) ** No package available: textproc/expat2 --- Found a package of 'textproc/expat2': /usr/ports/packages/All/expat-1.95.8_3.tbz (expat-1.95.8_3) --- Located a package version 1.95.8_3 (/usr/ports/packages/All/expat-1.95.8_3.tbz) --- Listing the results (+:done / -:ignored / *:skipped / !:failed) ! textproc/expat2 (expat-1.95.8_3) (package not found) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed --- Session ended at: Wed, 31 May 2006 09:21:34 -0400 (consumed 00:00:08) I tried running another sysinstall Upgrade without installing X.org and now I didn't have any errors. 'kernels' was one of the distributions selected (by default) so I was wondering how *does* the kernel get swapped while it's still running. So I ran another sysinstall but this time from the 6.0-RELEASE CD-ROM. I chose 6.1-RELEASE from Options, FTP from ftp.freebsd.org as the source of the distribution, and didn't install X.org. It went OK as the previous one did, but upon reboot I still have a 6.0-RELEASE kernel. So I'm back to wondering how do those 6.0 .ko objects get replaced by 6.1 .ko's in the upgrade process ... Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_upgrade?
On Wed, May 31, 2006 at 07:51:38AM -0400, Joe wrote: Kris Kennaway wrote: On Tue, May 30, 2006 at 08:12:25PM -0400, Joe wrote: The .ko files have a Nov 3 2005 date, whereas the files in /boot including the kernel directory have a May 6 2006 date. I take it that Nov 3 means 6.0-RELEASE since the announcement was done on Nov 4. So, I guess I'm back to the question of how to do a binary upgrade from 6.0 to 6.1 (and particularly where is this documented). Should I attempt another sysinstall Upgrade? Show me sysctl kern.version kern.version: FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Yep, it's a 6.0-RELEASE kernel. I noticed that you didn't actually confirm whether /boot/kernel/kernel has the right date - only the files in /boot including the kernel directory. Anyway, retry the binary upgrade as you say. Kris pgp3JWEq4ElCF.pgp Description: PGP signature
Re: pkg_upgrade?
Kris Kennaway wrote: Anyway, retry the binary upgrade as you say. The binary upgrade started from the 6.0-RELEASE CD-ROM didn't work, but using 6.1-RELEASE floppies was successful. I peaked at the debug screen and saw how it gets done: The GENERIC .ko's get put into a separate directory, then there's an 'rm -rf /boot/kernel' and then the GENERIC directory is moved to /boot/kernel. I presume that doing it from sysinstall in a running 6.0 system, the 'rm -rf' fails in spite of the force flag. You'd think the 6.0 CD ought not to have that problem, but I'm not sure if it fetched the .ko's from 6.1 even though it got everything else from 6.1. Thanks for your help. Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_upgrade?
On Wed, May 31, 2006 at 05:05:28PM -0400, Joe wrote: Kris Kennaway wrote: Anyway, retry the binary upgrade as you say. The binary upgrade started from the 6.0-RELEASE CD-ROM didn't work Wait, you were trying to update to 6.1-RELEASE using the 6.0-RELEASE CD-ROM? :) Kris pgpiCq50hC5hV.pgp Description: PGP signature
Re: pkg_upgrade?
Kris Kennaway wrote: On Wed, May 31, 2006 at 05:05:28PM -0400, Joe wrote: Kris Kennaway wrote: Anyway, retry the binary upgrade as you say. The binary upgrade started from the 6.0-RELEASE CD-ROM didn't work Wait, you were trying to update to 6.1-RELEASE using the 6.0-RELEASE CD-ROM? :) Yes, I mentioned that a couple of times before. However, in the options screen, I requested the *6.1-RELEASE* to be fetched, and it did do that--except for the kernel, or actually it seems it fetched that too but it was unable to move it into place. I'm fairly knew at FreeBSD (but definitely not at software) and I don't see why I shouldn't be able to upgrade an OS starting from the earlier release, i.e., without having to bootstrap from the new release, particularly when upgrading within the same major release, from one minor to the next. Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_upgrade?
On Wed, May 31, 2006 at 10:23:46PM -0400, Joe wrote: Kris Kennaway wrote: On Wed, May 31, 2006 at 05:05:28PM -0400, Joe wrote: Kris Kennaway wrote: Anyway, retry the binary upgrade as you say. The binary upgrade started from the 6.0-RELEASE CD-ROM didn't work Wait, you were trying to update to 6.1-RELEASE using the 6.0-RELEASE CD-ROM? :) Yes, I mentioned that a couple of times before. However, in the options screen, I requested the *6.1-RELEASE* to be fetched, and it did do that--except for the kernel, or actually it seems it fetched that too but it was unable to move it into place. I'm fairly knew at FreeBSD (but definitely not at software) and I don't see why I shouldn't be able to upgrade an OS starting from the earlier release, i.e., without having to bootstrap from the new release, particularly when upgrading within the same major release, from one minor to the next. The necessary steps for upgrading from an old release to the current one sometimes change. The old release doesn't know all of the future upgrading procedures for subsequent releases. That's almost certainly what went on here. Kris pgpdFCUxW8gJd.pgp Description: PGP signature
Re: pkg_upgrade?
Kris Kennaway wrote: On Mon, May 29, 2006 at 07:42:43PM -0400, Joe wrote: Hi, I've read the documentation and it seems there's no pkg_upgrade or pkg_update, or a way to install an updated/upgraded package. I'd like to determine if that is indeed the case. portupgrade -P or -PP OK, since I had upgraded to 6.1-RELEASE, I used portsnap to get the ports, then I used pkg_add -r to get portupgrade and then, as a test ran portupgrade -PP expat It failed to update expat however, because it kept looking in the 6.0-RELEASE paths. I presume this is because even though the binary upgrade of the base to 6.1 went well, uname, etc., think I still have a 6.0 machine. So where is the *real* version id stored and how can it be (should it be?) safely modified? Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_upgrade?
On Tue, May 30, 2006 at 04:51:51PM -0400, Joe wrote: Kris Kennaway wrote: On Mon, May 29, 2006 at 07:42:43PM -0400, Joe wrote: Hi, I've read the documentation and it seems there's no pkg_upgrade or pkg_update, or a way to install an updated/upgraded package. I'd like to determine if that is indeed the case. portupgrade -P or -PP OK, since I had upgraded to 6.1-RELEASE, I used portsnap to get the ports, then I used pkg_add -r to get portupgrade and then, as a test ran portupgrade -PP expat It failed to update expat however, because it kept looking in the 6.0-RELEASE paths. I presume this is because even though the binary upgrade of the base to 6.1 went well, uname, etc., think I still have a 6.0 machine. So where is the *real* version id stored and how can it be (should it be?) safely modified? It's reported by the kernel, so if it's still saying 6.0-RELEASE then that's what you're still running. Kris pgpoB5bPfeXeZ.pgp Description: PGP signature
Re: pkg_upgrade?
Kris Kennaway wrote: On Tue, May 30, 2006 at 04:51:51PM -0400, Joe wrote: [...] It failed to update expat however, because it kept looking in the 6.0-RELEASE paths. I presume this is because even though the binary upgrade of the base to 6.1 went well, uname, etc., think I still have a 6.0 machine. So where is the *real* version id stored and how can it be (should it be?) safely modified? It's reported by the kernel, so if it's still saying 6.0-RELEASE then that's what you're still running. I don't have access to the system right now, but after the sysinstall I looked at some of the files in /bin and saw that most had a date of May 6, 2006 (or thereabouts) so I assumed that meant the binary upgrade had been successful. How can I verify that the actual kernel was upgraded? Also, I haven't been able to locate much information about a binary upgrade in the Handbook. The only reference was in the INSTALL.htm in the release directory. Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_upgrade?
On Tue, May 30, 2006 at 06:14:32PM -0400, Joe wrote: Kris Kennaway wrote: On Tue, May 30, 2006 at 04:51:51PM -0400, Joe wrote: [...] It failed to update expat however, because it kept looking in the 6.0-RELEASE paths. I presume this is because even though the binary upgrade of the base to 6.1 went well, uname, etc., think I still have a 6.0 machine. So where is the *real* version id stored and how can it be (should it be?) safely modified? It's reported by the kernel, so if it's still saying 6.0-RELEASE then that's what you're still running. I don't have access to the system right now, but after the sysinstall I looked at some of the files in /bin and saw that most had a date of May 6, 2006 (or thereabouts) so I assumed that meant the binary upgrade had been successful. How can I verify that the actual kernel was upgraded? Also, I haven't been able to locate much information about a binary upgrade in the Handbook. The only reference was in the INSTALL.htm in the release directory. ls -l /boot/kernel Kris pgpBXKG8r2A33.pgp Description: PGP signature
Re: pkg_upgrade?
Kris Kennaway wrote: On Tue, May 30, 2006 at 06:14:32PM -0400, Joe wrote: I don't have access to the system right now, but after the sysinstall I looked at some of the files in /bin and saw that most had a date of May 6, 2006 (or thereabouts) so I assumed that meant the binary upgrade had been successful. How can I verify that the actual kernel was upgraded? Also, I haven't been able to locate much information about a binary upgrade in the Handbook. The only reference was in the INSTALL.htm in the release directory. ls -l /boot/kernel The .ko files have a Nov 3 2005 date, whereas the files in /boot including the kernel directory have a May 6 2006 date. I take it that Nov 3 means 6.0-RELEASE since the announcement was done on Nov 4. So, I guess I'm back to the question of how to do a binary upgrade from 6.0 to 6.1 (and particularly where is this documented). Should I attempt another sysinstall Upgrade? Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_upgrade?
On Tue, May 30, 2006 at 08:12:25PM -0400, Joe wrote: Kris Kennaway wrote: On Tue, May 30, 2006 at 06:14:32PM -0400, Joe wrote: I don't have access to the system right now, but after the sysinstall I looked at some of the files in /bin and saw that most had a date of May 6, 2006 (or thereabouts) so I assumed that meant the binary upgrade had been successful. How can I verify that the actual kernel was upgraded? Also, I haven't been able to locate much information about a binary upgrade in the Handbook. The only reference was in the INSTALL.htm in the release directory. ls -l /boot/kernel The .ko files have a Nov 3 2005 date, whereas the files in /boot including the kernel directory have a May 6 2006 date. I take it that Nov 3 means 6.0-RELEASE since the announcement was done on Nov 4. So, I guess I'm back to the question of how to do a binary upgrade from 6.0 to 6.1 (and particularly where is this documented). Should I attempt another sysinstall Upgrade? Show me sysctl kern.version and the output of a failed package fetch. Kris pgpGt2JJlb4uC.pgp Description: PGP signature
Re: pkg_upgrade?
On Tuesday 30 May 2006 01:42, Joe wrote: Hi, I've read the documentation and it seems there's no pkg_upgrade or pkg_update, or a way to install an updated/upgraded package. I'd like to determine if that is indeed the case. [...] The documentation mentions portupgrade and portmanager as mechanisms to upgrade ports, but if I'm not mistaken these invoke source updates, not a binary upgrade as was done for the OS. It appears that the only way to upgrade in binary form is to use pkg_delete -f to remove each package, e.g., expat 1.98, and then pkg_add to get the newer (2.0) version. And then you have to be extra careful with dependencies between packages. [...] portupgrade actually does support packages as well. Use the --use-packages switch. It will look for local packages, remote packages, and if both fail, fall back to compiling the ports. Cheers Benjamin pgpWuRQ0cUDNJ.pgp Description: PGP signature
Re: pkg_upgrade?
On Mon, May 29, 2006 at 07:42:43PM -0400, Joe wrote: Hi, I've read the documentation and it seems there's no pkg_upgrade or pkg_update, or a way to install an updated/upgraded package. I'd like to determine if that is indeed the case. portupgrade -P or -PP Kris pgpGNkBQGy4Ip.pgp Description: PGP signature
Re: pkg_upgrade ?
In [EMAIL PROTECTED], David Bear [EMAIL PROTECTED] typed: I do have cvsup installed, and can run cvsup to update my ports collection. My question is if I already have a package installed, running cvsup, the make install again for a preexisting port will mess up the pkg-data base right? Wrong. If you are installing a port a second time, make install will refuse to install the port because it's already installed. If you are installing an updated port, then the pkg-data will be in a different place because the port has a different name. The latter case may leave parts of the first port laying around unused, and deinstalling it will probably break the second port. So, if I only want to upgrade a single port, is the recommended way 1) pkg_deinstall 2) cvsup ports collection 3) pkg_install again (or make install) This seems rather poor as I don't want to have all the downtime between deinstalling and installing again. Try this: 1) cvsup ports collection 2) make 3) pkg_deinstall 4) make install If I cvsup ports and then make install, is there a fix to update the pkg data base? It's not needed. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_upgrade ?
On Tue, 2003-03-18 at 12:56, Mike Meyer wrote: In [EMAIL PROTECTED], David Bear [EMAIL PROTECTED] typed: I do have cvsup installed, and can run cvsup to update my ports collection. My question is if I already have a package installed, running cvsup, the make install again for a preexisting port will mess up the pkg-data base right? Wrong. If you are installing a port a second time, make install will refuse to install the port because it's already installed. If you are installing an updated port, then the pkg-data will be in a different place because the port has a different name. The latter case may leave parts of the first port laying around unused, and deinstalling it will probably break the second port. So, if I only want to upgrade a single port, is the recommended way 1) pkg_deinstall 2) cvsup ports collection 3) pkg_install again (or make install) This seems rather poor as I don't want to have all the downtime between deinstalling and installing again. Try this: 1) cvsup ports collection 2) make 3) pkg_deinstall 4) make install If I cvsup ports and then make install, is there a fix to update the pkg data base? It's not needed. mike Of course, this method does not work if there are any packages/ports depending on the port you are upggrading. The pkg_deinstall will fail because of the dependencies. I believe a pkg_deinstall -f will forcibly remove the package anyway. Unfortunately, I still sometimes find the dependent ports need to be recompiled for the new version of the port you are installing. -Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_upgrade ?
In [EMAIL PROTECTED], Matthew Smith [EMAIL PROTECTED] typed: Of course, this method does not work if there are any packages/ports depending on the port you are upggrading. The pkg_deinstall will fail because of the dependencies. I believe a pkg_deinstall -f will forcibly remove the package anyway. Unfortunately, I still sometimes find the dependent ports need to be recompiled for the new version of the port you are installing. Yup. That's what portupgrade is for. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_upgrade ?
Nope. pkgdb -F fixes the package database and removes old entries... Anthony On Tue, 2003-03-18 at 17:55, David Bear wrote: I've been searching the handbook and can't seem to find what I'm looking for regarding upgrading a port. I know there is portupgrade... which I'd like to avoid because I don't want to install ruby as well. I do have cvsup installed, and can run cvsup to update my ports collection. My question is if I already have a package installed, running cvsup, the make install again for a preexisting port will mess up the pkg-data base right? So, if I only want to upgrade a single port, is the recommended way 1) pkg_deinstall 2) cvsup ports collection 3) pkg_install again (or make install) This seems rather poor as I don't want to have all the downtime between deinstalling and installing again. If I cvsup ports and then make install, is there a fix to update the pkg data base? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_upgrade ?
Nope. pkgdb -F fixes the package database and removes old entries... Anthony On Tue, 2003-03-18 at 17:55, David Bear wrote: I've been searching the handbook and can't seem to find what I'm looking for regarding upgrading a port. I know there is portupgrade... which I'd like to avoid because I don't want to install ruby as well. I do have cvsup installed, and can run cvsup to update my ports collection. My question is if I already have a package installed, running cvsup, the make install again for a preexisting port will mess up the pkg-data base right? So, if I only want to upgrade a single port, is the recommended way 1) pkg_deinstall 2) cvsup ports collection 3) pkg_install again (or make install) This seems rather poor as I don't want to have all the downtime between deinstalling and installing again. If I cvsup ports and then make install, is there a fix to update the pkg data base? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: pkg_upgrade ?
In [EMAIL PROTECTED], David Bear [EMAIL PROTECTED] typed: I do have cvsup installed, and can run cvsup to update my ports collection. My question is if I already have a package installed, running cvsup, the make install again for a preexisting port will mess up the pkg-data base right? Wrong. If you are installing a port a second time, make install will refuse to install the port because it's already installed. If you are installing an updated port, then the pkg-data will be in a different place because the port has a different name. The latter case may leave parts of the first port laying around unused, and deinstalling it will probably break the second port. So, if I only want to upgrade a single port, is the recommended way 1) pkg_deinstall 2) cvsup ports collection 3) pkg_install again (or make install) This seems rather poor as I don't want to have all the downtime between deinstalling and installing again. Try this: 1) cvsup ports collection 2) make 3) pkg_deinstall 4) make install If I cvsup ports and then make install, is there a fix to update the pkg data base? It's not needed. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: pkg_upgrade ?
On Tue, 2003-03-18 at 12:56, Mike Meyer wrote: In [EMAIL PROTECTED], David Bear [EMAIL PROTECTED] typed: I do have cvsup installed, and can run cvsup to update my ports collection. My question is if I already have a package installed, running cvsup, the make install again for a preexisting port will mess up the pkg-data base right? Wrong. If you are installing a port a second time, make install will refuse to install the port because it's already installed. If you are installing an updated port, then the pkg-data will be in a different place because the port has a different name. The latter case may leave parts of the first port laying around unused, and deinstalling it will probably break the second port. So, if I only want to upgrade a single port, is the recommended way 1) pkg_deinstall 2) cvsup ports collection 3) pkg_install again (or make install) This seems rather poor as I don't want to have all the downtime between deinstalling and installing again. Try this: 1) cvsup ports collection 2) make 3) pkg_deinstall 4) make install If I cvsup ports and then make install, is there a fix to update the pkg data base? It's not needed. mike Of course, this method does not work if there are any packages/ports depending on the port you are upggrading. The pkg_deinstall will fail because of the dependencies. I believe a pkg_deinstall -f will forcibly remove the package anyway. Unfortunately, I still sometimes find the dependent ports need to be recompiled for the new version of the port you are installing. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: pkg_upgrade ?
In [EMAIL PROTECTED], Matthew Smith [EMAIL PROTECTED] typed: Of course, this method does not work if there are any packages/ports depending on the port you are upggrading. The pkg_deinstall will fail because of the dependencies. I believe a pkg_deinstall -f will forcibly remove the package anyway. Unfortunately, I still sometimes find the dependent ports need to be recompiled for the new version of the port you are installing. Yup. That's what portupgrade is for. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
