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
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
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
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
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)
