What is pre-moderation?
Upgrade install - how to
Hello Guest
  
  • Login
• Register…
• Start blog
  • Who, Where, When
• What can I do?
• What to Read?
  • Polls
• Avatars
• Interests
  • Cities and Countries
• Random blog
• Users search
  • Search
• Games
• Tests
• RYXI
  • Сообщества
• Talxy Chat
• Horoscope
• Online
 
Зарегистрируйся!

RYXI > Solaris > Upgrade install - how to 13 May 2005 00:58:38

  Recent blog posts: 
  They have birthday today: 
  Forums:   
  Discuss: 
  Recent forum topics: 
  Recent forum comments:
  Moderators:

Upgrade install - how to

Enda Mannioooo 13 May 2005 00:58:38
 Hello,

To make a long Q? shorter "How do I do an upgrade on Solaris?"

OK - here is my pkginfo file

PKG=bag
NAME=Big Bag of Sticks
VERSION="Version 1.3.0"
CATEGORY=system
ARCH=sparc
BASEDIR=/
UPGRADE=
CLASS=none

but if I change the version to 1.4.0 then i'm not allowed to perform the install.

get this:
Current administration requires that a unique instance of the <bag>
package be created. However, the maximum number of instances of the
package which may be supported at one time on the same system has
already been met.

No changes were made to the system.

Any ideas how I can go about performing this upgrade

Thanks
Enda
Add comment
Jorgen Moquist 21 April 2005 03:12:48 permanent link ]
 Enda Mannioooo wrote:> Hello,>
To make a long Q? shorter "How do I do an upgrade on Solaris?">
OK - here is my pkginfo file>
PKG=bag> NAME=Big Bag of Sticks> VERSION="Version 1.3.0"> CATEGORY=system> ARCH=sparc> BASEDIR=/> UPGRADE=> CLASS=none>
but if I change the version to 1.4.0 then i'm not allowed to perform the install.>
get this:> Current administration requires that a unique instance of the <bag>> package be created. However, the maximum number of instances of the> package which may be supported at one time on the same system has> already been met.>
No changes were made to the system.>
Any ideas how I can go about performing this upgrade>
Thanks> Enda
im not sure, but i think MAXINST=1000 in pkginfo is what you are looking
for.
it makes you overwrite a package with the same name MAXINST=n of times.

whithout MAXINST=n , you have to pkgrm <bag>(1.3), then pkgadd <bag>(1.4).

/jГ¶rgen
Add comment
Enda Mannioooo 26 April 2005 12:46:30 permanent link ]
 Hi,

I am now using MAXINST=1000 in my pkginfo file. But when I increment
the version string also in the pkginfo file from say 1.3.0 to 1.4.0 a
new package is installed.

from pkginfo command:

system bag3 B A G (bag)
system bag3.2 B A G (bag)

But I want to do an upgrade on the same package and not add a new
package.

How can I upgrade on the same package.

-Enda

Jorgen Moquist <jorgen.moquist@n.o­.s.p.a.m.mailbox.swi­pnet.se> wrote in message news:<koB9e.48124$O­f5.31339@nntpserver.­swip.net>...> Enda Mannioooo wrote:> > Hello,> >
To make a long Q? shorter "How do I do an upgrade on Solaris?"> >
OK - here is my pkginfo file> >
PKG=bag> > NAME=Big Bag of Sticks> > VERSION="Version 1.3.0"> > CATEGORY=system> > ARCH=sparc> > BASEDIR=/> > UPGRADE=> > CLASS=none> >
but if I change the version to 1.4.0 then i'm not allowed to perform the install.> >
get this:> > Current administration requires that a unique instance of the <bag>> > package be created. However, the maximum number of instances of the> > package which may be supported at one time on the same system has> > already been met.> >
No changes were made to the system.> >
Any ideas how I can go about performing this upgrade> >
Thanks> > Enda> im not sure, but i think MAXINST=1000 in pkginfo is what you are looking > for.> it makes you overwrite a package with the same name MAXINST=n of times.>
whithout MAXINST=n , you have to pkgrm <bag>(1.3), then pkgadd <bag>(1.4).>
/jГ¶rgen
Add comment
Jorgen Moquist 27 April 2005 05:29:16 permanent link ]
 Enda Mannioooo wrote:> Hi,>
I am now using MAXINST=1000 in my pkginfo file. But when I increment> the version string also in the pkginfo file from say 1.3.0 to 1.4.0 a> new package is installed.>
from pkginfo command:>
system bag3 B A G (bag)> system bag3.2 B A G (bag)>
But I want to do an upgrade on the same package and not add a new> package.>
How can I upgrade on the same package.>
-Enda>
you're printout show a package name change not a version change.
pkginfo does not show versions if not asked to.
package names is not versions, its names.
so bag3 and bag3.2 are different names.
if you post pkginfo & prototype files it will be much easyer.
for anybody to fix you a solution.

/jГ¶rgen
Jorgen Moquist <jorgen.moquist@n.o­.s.p.a.m.mailbox.swi­pnet.se> wrote in message news:<koB9e.48124$O­f5.31339@nntpserver.­swip.net>...>
Enda Mannioooo wrote:>>
Hello,>>>
To make a long Q? shorter "How do I do an upgrade on Solaris?">>>
OK - here is my pkginfo file>>>
PKG=bag>>>NAME=B­ig Bag of Sticks>>>VERSION="V­ersion 1.3.0">>>CATEGORY=s­ystem>>>ARCH=sparc>>­>BASEDIR=/>>>UPGRADE­=>>>CLASS=none>>>
but if I change the version to 1.4.0 then i'm not allowed to perform the install.>>>
get this:>>>Current administration requires that a unique instance of the <bag>>>>package be created. However, the maximum number of instances of the>>>package which may be supported at one time on the same system has>>>already been met.>>>
No changes were made to the system.>>>
Any ideas how I can go about performing this upgrade>>>
Thanks>>>Enda>>
im not sure, but i think MAXINST=1000 in pkginfo is what you are looking >>for.>>it makes you overwrite a package with the same name MAXINST=n of times.>>
whithout MAXINST=n , you have to pkgrm <bag>(1.3), then pkgadd <bag>(1.4).>>
/jГ¶rgen
Add comment
Scott Howard 27 April 2005 14:48:19 permanent link ]
 Jorgen Moquist <jorgen.moquist@n.o­.s.p.a.m.mailbox.swi­pnet.se> wrote:>> from pkginfo command:>>
system bag3 B A G (bag)>> system bag3.2 B A G (bag)>>
you're printout show a package name change not a version change.

No, it shows an new instance of the same package, which occurs when you
install a new version of a package (and MAXINST is >1)

This is expected behaviour - if you don't want this occuring then you
need to pkgrm the old verison of the package before adding the new one.

Scott
Add comment
Guest 27 April 2005 17:08:14 permanent link ]
 The package name has not changed just the version number, here is the
pkginfo file:

PKG=bag3
NAME=B A G
VERSION="Version 1.3.0"
CATEGORY=system
ARCH=sparc
BASEDIR=/
UPGRADE=
CLASS=none
MAXINST=1000


I just increment the version but still it looks like a new package gets
installed not a new version. I just want to do an upgrade not remove
the old kit and install the new kit, there are files I do not want to
loose.

Also during the new install of the kit with the updated version number
I do a version check on the previously installed kit using 'pkgparam -v
mc3 VERSION'
and compare this against the $VERSION variable of the new kit. But
'pkgparam -v mc3 VERSION' returns the updated version number not the
one of the previously installed kit. Seems to be related to the problem
above where new kits gets installed on each version increment.

Hope this is readable. Any ideas.
Enda

Add comment
Guest 4 May 2005 12:50:51 permanent link ]
 Any help with my upgrade problem.

Can not upgrade on same package a new package is installed.

Is there a way to upgrade without removing the previous package.


Enda

keepyourstupidspam@­yahoo.co.uk wrote:> The package name has not changed just the version number, here is the> pkginfo file:>
PKG=bag3> NAME=B A G> VERSION="Version 1.3.0"> CATEGORY=system> ARCH=sparc> BASEDIR=/> UPGRADE=> CLASS=none> MAXINST=1000>
I just increment the version but still it looks like a new package
gets> installed not a new version. I just want to do an upgrade not remove> the old kit and install the new kit, there are files I do not want to> loose.>
Also during the new install of the kit with the updated version
number> I do a version check on the previously installed kit using 'pkgparam
-v> mc3 VERSION'> and compare this against the $VERSION variable of the new kit. But> 'pkgparam -v mc3 VERSION' returns the updated version number not the> one of the previously installed kit. Seems to be related to the
problem> above where new kits gets installed on each version increment.>
Hope this is readable. Any ideas.> Enda

Add comment
Darren Dunham 4 May 2005 20:26:05 permanent link ]
 keepyourstupidspam@y­ahoo.co.uk wrote:> Any help with my upgrade problem.
Can not upgrade on same package a new package is installed.
Is there a way to upgrade without removing the previous package.

Maybe not easily. Why do you want to avoid removing the package? I
would say that's the most common method that applications use (think
Veritas and Legato packages).

You might be able to create a patch that would update the files in the
package, but I seem to recall that there's no easy user guide for patch
creation like there is for a package.

--
Darren Dunham ddunham@taos.com
Senior Technical Consultant TAOS http://www.taos.com­/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
Add comment
Guest 12 May 2005 14:10:54 permanent link ]
 It seems a little strange that I can not perform an upgrade without
having to remove the kit I about to upgrade on.

I attempted this, I call "pkgrm -n -a $CONFIGDIR/rmnoask bag" from my
preinstall script if this kit is already installed\upgrade.

But it fails, it seems I can not call pkgrm while I am running pkgadd.
I get the following message.

NOTE: Waiting for pkgadd of bag to complete.
pkgrm: ERROR: unable to install governing lock on
</var/sadm/install/­.lockfile>.

Removal of <bag> failed (internal error).
No changes were made to the system.
pkgadd: ERROR: preinstall script did not complete successfully

Installation of <bag> failed.


Therefore I can not perform an upgrade. Can anyone tell me the normal
way of doing this?


Enda

Darren Dunham wrote:> keepyourstupidspam@­yahoo.co.uk wrote:> > Any help with my upgrade problem.>
Can not upgrade on same package a new package is installed.>
Is there a way to upgrade without removing the previous package.>
Maybe not easily. Why do you want to avoid removing the package? I> would say that's the most common method that applications use (think> Veritas and Legato packages).>
You might be able to create a patch that would update the files in
package, but I seem to recall that there's no easy user guide for
patch> creation like there is for a package.>
--> Darren Dunham
ddunham@taos.com> Senior Technical Consultant TAOS
http://www.taos.com­/> Got some Dr Pepper? San Francisco, CA bay
area> < This line left intentionally blank to confuse you. >

Add comment
James Carlson 12 May 2005 16:39:12 permanent link ]
 keepyourstupidspam@y­ahoo.co.uk writes:> It seems a little strange that I can not perform an upgrade without> having to remove the kit I about to upgrade on.>
I attempted this, I call "pkgrm -n -a $CONFIGDIR/rmnoask bag" from my> preinstall script if this kit is already installed\upgrade.

No, that's not going to work for the same reason you can't have two
pkg* commands modifying packages at the same time.
Therefore I can not perform an upgrade. Can anyone tell me the normal> way of doing this?

The normal way of doing it is to do pkgrm first and then pkgadd. The
pkgrm should be crafted so that it leaves any modified configuration
in place. (Ftype 'e' in prototype with class "preserve.")

You should also be able to set MAXINST to 1, or just omit it. That
way, you can pkgadd on top of the existing package without doing pkgrm
first.

--
James Carlson, KISS Network <james.d.carlson@su­n.com>
Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677
Add comment
Guest 12 May 2005 20:26:52 permanent link ]
 
You should also be able to set MAXINST to 1, or just omit it. That>way, you can pkgadd on top of the existing package without doing pkgrm>first.

This brings me back to a previous posting I have had. If I leave
MAXINST at 1 and I increment the version from sat 1.3.0 to 1.4.0 the
install will not continue with:

Current administration requires that a unique instance of the <mc3>
package be created. However, the maximum number of instances of the
package which may be supported at one time on the same system has
already been met.

No changes were made to the system.


-Enda

Add comment
Markus Gyger 12 May 2005 23:20:55 permanent link ]
 James Carlson writes:> The normal way of doing it is to do pkgrm first and then pkgadd. The> pkgrm should be crafted so that it leaves any modified configuration> in place. (Ftype 'e' in prototype with class "preserve.")

Note that preserve only preserves at pkgadd time -- it doesn't
during a pkgrm (but one could include an own class action script
r.preserve that does only cat >/dev/null).


Markus
Add comment
James Carlson 13 May 2005 00:58:38 permanent link ]
 Markus Gyger <markus+news@gyger.­org> writes:> James Carlson writes:> > The normal way of doing it is to do pkgrm first and then pkgadd. The> > pkgrm should be crafted so that it leaves any modified configuration> > in place. (Ftype 'e' in prototype with class "preserve.")>
Note that preserve only preserves at pkgadd time -- it doesn't> during a pkgrm (but one could include an own class action script> r.preserve that does only cat >/dev/null).

... which is generally what I do.

--
James Carlson, KISS Network <james.d.carlson@su­n.com>
Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677
Add comment
 

Add new comment

As:
Login:  Password:  
 
 
  
 
Пожалуйста, относитесь к собеседникам уважительно, не используйте нецензурные слова, не злоупотребляйте заглавными буквами, не публикуйте рекламу и объявления о купле/продаже, а также материалы нарушающие сетевой этикет или УК РФ.


RYXI > Solaris > Upgrade install - how to 13 May 2005 00:58:38

see also:
BG2: Turnabout V1 Released
CoV free for CoH players!
CoV: Overview
пройди тесты:
see also:
music transfer
Canon Pixma IP1500 how to replace waste…

  Copyright © 2001—2008 RYXI
Idea: Miсhael Monashev
Помощь и задать вопросы можно в сообществе support.ryxi.com.
Сообщения об ошибках оставляем в сообществе bugs.ryxi.com.
Предложения и комментарии пишем в сообществе suggest.ryxi.com.
Информация для родителей.
Write us at:
If you would like to report an abuse of our service, such as a spam message, please .