Re: Howto upgrade a source-build OpenPkg-2.0 instalation
On Fri, Jul 23, 2004, Alexander Belck wrote: Alex, How should I proceed to upgrade all packages [from 2.0] to the equivalent of release 2.1 ? my approach manually upgrading a instance from 2.0 to 2.1 is: - read and understand the release notes [1] :-) - backup the instance, especially the etc, share and var directories. - make sure there's plenty of hard disk space available. - download and upgrade the bootstrap openpkg package. - upgrade/install make, binutils, gcc, perl and openpkg-tools packages. Assumed you're lucky with the gcc default options, which is likely to be the case, these steps can be automated by running openpkg rpm install openpkg-tools. This makes - see what openpkg build -Ua suggests and if it works and the output (which is a shell script) looks reasonably run it. [1] http://cvs.openpkg.org/openpkg-re/releasenotes.txt -- [EMAIL PROTECTED], Cable Wireless __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: openpkg build -Ua question
On Fri, Jul 23, 2004 at 05:55:22PM -0300, Alexander Belck wrote: Is this constant use of --force normal ? The build tool will always use --force if it updates a package. This asks rpm to do two things: - to ignore if the package or a more recent version is already installed, the build tool already takes care of this issue and may make different decisisions. - to overwrite files that may belong to different packages. Here it is the OpenPKG developers who need to be careful that this is safe, usually by ensuring that there are no such file conflicts between packages. My poor expirience with rpm got to unstable rpm instalations when using --force. The second point can lead to instabilities if the packages aren't created carefully, but avoiding --force doesn't solve the problem of broken packages :) Greetings, -- Michael van Elst Internet: [EMAIL PROTECTED] A potential Snark may lurk in every tree. __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: openpkg build -Ua question
I allready needed to reenter twice the openpkg build -Ua upgrad.sh after execution exited with error from previos upgrad.sh version. Each time I generate a new upgrad.sh script, the sequence is altered. Could it be that openpkg is unable to decide the apropriate order to upgrade all packages from an instalation ? Thanks again, Alex Citando Michael van Elst [EMAIL PROTECTED]: On Fri, Jul 23, 2004 at 05:55:22PM -0300, Alexander Belck wrote: Is this constant use of --force normal ? The build tool will always use --force if it updates a package. This asks rpm to do two things: - to ignore if the package or a more recent version is already installed, the build tool already takes care of this issue and may make different decisisions. - to overwrite files that may belong to different packages. Here it is the OpenPKG developers who need to be careful that this is safe, usually by ensuring that there are no such file conflicts between packages. My poor expirience with rpm got to unstable rpm instalations when using --force. The second point can lead to instabilities if the packages aren't created carefully, but avoiding --force doesn't solve the problem of broken packages :) Greetings, -- Michael van Elst Internet: [EMAIL PROTECTED] A potential Snark may lurk in every tree. __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED] -- ATIX Tecnologia e Com Ltda Tel.: +55-(11) 4667-5900 This message was sent using IMP, the Internet Messaging Program. __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: openpkg build -Ua question
On Fri, Jul 23, 2004, Alexander Belck wrote: I allready needed to reenter twice the openpkg build -Ua upgrad.sh after execution exited with error from previos upgrad.sh version. Each time I generate a new upgrad.sh script, the sequence is altered. I typically do an ``openpkg build -Ua /tmp/build.update'' to create the initial update file, looking at it to see if there's anything obvious that I need to deal with. After that, I then execute the script, redirecting output to a file through ``tee'' which will allow me to look at the output in case of problems: sh /tmp/build.update 21 | tee /tmp/build.update_log_01 If the update fails for some reason, I'll normally try to address that issue (say moving the autoconf lines above automake if automake says it needs a more current version of autoconf), comment out everthing that's already built successfully, the rerun the build from that point on, usually increasing the log_0n number so I have a record of the changes made. Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC UUCP: camco!bill PO Box 820; 6641 E. Mercer Way FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 URL: http://www.celestial.com/ ``Scientists are explorers. Philosophers are tourists.'' -- Richard Feynman __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Ever rebuilding openpkg-2.1.0
After I build all packages (except postfix that doesn't compile), but shurly twice the openpkg-2.1.0, if I run openpkg build -Ua it always whants to rebuild openpkg-2.1.0. Why is this happining ? openpkg-2.1.0 is already installed Thanks, Alex -- ATIX Tecnologia e Com Ltda Tel.: +55-(11) 4667-5900 This message was sent using IMP, the Internet Messaging Program. __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
