OK. I figured it out.
You changed the OS name in the %{l_prefix}/etc/openpkg/platform file. I
changed it back to redhat9, and I can now reinstall my openpkg-20043024
binary rpm.
Is there any reason to restore it to "rhl9"? Since I don't know why you
changed it, I don't know if it would hurt anything to leave it as "redhat9".
Thanks,
Dennis
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dennis McRitchie
> Sent: Thursday, April 01, 2004 4:18 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Upgrade from openpkg-20031020 questions (new problem)
>
>
> Hi again.
>
> In following your directions, all went well all the way
> through step 2 (building and installing openpkg-20040324).
>
> However, I realized that I should have executed:
> rpm -Uvh openpkg-20040324-20040324.ix86-redhat9-up.rpm
>
> as root when I received the following messages:
> Preparing...
> ###########################################
> [100%]
> openpkg:WARNING: skipping creation of system run-command hooks
> openpkg:WARNING: (would require root-privileges)
> openpkg:WARNING: skipping creation of system cron hooks
> openpkg:WARNING: (would require root-privileges)
> 1:openpkg
> ###########################################
> [100%]
>
> So I su'd to root and tried to run:
> openpkg rpm -Uvh --force openpkg-20040324-20040324.ix86-redhat9-up.rpm
>
> I now get the following message:
> openpkg rpm -Uvh --force openpkg-20040324-20040324.ix86-redhat9-up.rpm
> Preparing...
> ###########################################
> [100%]
> package openpkg-20040324-20040324 is intended for a
> redhat9 operating system
>
> I exited back to my original login and tried again, but got
> the same error.
>
> I am running under redhat9, and this was not a problem with
> the openpkg-200301020 version. Could this have anything to do
> with the new location tag logic?
>
> Thanks,
> Dennis
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Ralf S.
> > Engelschall
> > Sent: Thursday, April 01, 2004 1:28 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Upgrade from openpkg-20031020 questions
> >
> >
> > On Thu, Apr 01, 2004, Dennis McRitchie wrote:
> >
> > > I am currently running in an openpkg-20031020 environment.
> > I'm trying
> > > to do a minimal 2.0 upgrade that will
> > > 1) allow me to build new 2.0 packages without having to
> > hack the Class
> > > tag out of the spec files, but
> > > 2) also allow me to avoid rebuilding the world.
> >
> > Then do the following:
> >
> > 1. remove openpkg-tool
> >
> > 2. upgrade to the latest "openpkg" from CURRENT by installing
> > ("rpm -Uvh") the openpkg*.src.rpm, removing the Class header once
> > ("vi openpkg.spec"), doing a "rpm -bb" and installing with
> > with "rpm
> > -Uvh" and this way upgrading the bootstrap package from
> 20031020 to
> > 200403xx. The "openpkg rpm --db-rebuild" I recommend you,
> > because it
> > will not destroy anything and makes sure you are
> consistent in your
> > database. If you are sceptic, just backup
> <prefix>/RPM/DB/ before.
> >
> > 3. reinstall openpkg-tool
> >
> > > Could I accomplish this with the following:
> > >
> > > 1) Remove openpkg-tool.
> > > 2) Build and install openpkg-1.9.0-2.0.0
> > > 3) Skip "openpkg rpm --db-rebuild" since openpkg-20031020
> > is already
> > > using RPM 4.2.1.
> > > 4) Avoid upgrading perl-openpkg at all costs! :-)
> > > 5) No need to rebuild and install openpkg-2.0.0 since I
> > plan to keep
> > > the location tag in compatibility mode.
> > > 6) Reinstall openpkg-tool.
> >
> > Yes, will work. But if you run CURRENT and want to still run
> > CURRENT, there is no need to jump through the release version
> > of the "openpkg" package.
> >
> > > If I understood the upgrade documentation correctly, I
> > should now be
> > > able
> > > to:
> > > 1) continue to run all packages that were installed prior
> > to the upgrade,
> > > 2) rebuild any pre-2.0.0 packages that I already have in my
> > repository
> > > (including perl-* packages), and
> > > 3) build any 2.0 packages with the exception of perl-* packages.
> > >
> > > Is that right?
> >
> > Yes.
> >
> > > Alternately, if I were to upgrade perl-openpkg, I would now
> > be unable
> > > to rebuild any pre-2.0.0 perl-* packages, but be able to build 2.0
> > > perl-* packages.
> >
> > Yes.
> >
> > > However, in this case, could I continue to *run* any
> > already installed
> > > pre-2.0 perl-* packages (as long as I don't try to rebuild and
> > > reinstall them) along with any newly built and installed
> 2.0 perl-*
> > > packages? [...]
> >
> > Yes, even if your "perl" version is different, because Perl
> > automatically finds modules also in older versioned directories.
> >
> > Ralf S. Engelschall
> > [EMAIL PROTECTED]
> > www.engelschall.com
> >
> >
> ______________________________________________________________________
> > The OpenPKG Project
> www.openpkg.org
> > User Communication List
> [EMAIL PROTECTED]
> >
>
> ______________________________________________________________________
> The OpenPKG Project www.openpkg.org
> User Communication List [EMAIL PROTECTED]
>
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
