Jasmine and I were trying out another twist on this, and I think we're seeing a problem with the pkg command. We're working on two changes at the same time which might be a mistake. One change is to do a patch update to the sunstudio12u1 package. The other change is the developer/ rename which was put into the import file for sunstudio, but which has never been used in real life yet.
We're trying to test what happens when the user upgrade from various old packages to the new ones we're creating. I install pkg://opensolaris.org/sunstudio12u1. But then when I install the updated package from the test repository it clobbers the files from the first package. It doesn't uninstall the old package before installing the new one, like I would expect. % uname -a SunOS tiaga 5.11 snv_130 i86pc i386 i86pc % pkg publisher PUBLISHER TYPE STATUS URI opensolaris.org (preferred) origin online http://ipkg.sfbay/dev/ opensolaris.org (preferred) mirror online http://pkg-na-2.opensolaris.org/ bug13191 origin online http://sqao43.sfbay.sun.com:32999/ % pkg list -a -f 'pkg://bug13191/*' NAME (PUBLISHER) VERSION STATE UFOXI SUNWiscsi (bug13191) 0.5.11-0.128 known u---- developer/sunstudio (bug13191) 12.1.1-0.128 known ----- developer/sunstudio12u1 (bug13191) 12.1.1-0.128 known ----- developer/sunstudioexpress (bug13191) 0.2009.3.1-0.128 known ----- sunstudio (bug13191) 12.1.1-0.128 known --r-- sunstudio12u1 (bug13191) 12.1.1-0.128 known --r-- sunstudioexpress (bug13191) 0.2009.3.1-0.128 known --r-- % pkg list -a -v 'pkg://opensolaris.org/sunstudio*' FMRI STATE UFOXI pkg://opensolaris.org/[email protected],5.11-0.111:20090617T225406Z known u---- pkg://opensolaris.org/[email protected],5.11-0.111:20090617T225413Z known u---- pkg://opensolaris.org/[email protected],5.11-0.111:20090617T230835Z known u---- % pfexec pkg install sunstudio12u1 ... % pkg list -v '*sunstudio*' FMRI STATE UFOXI pkg://opensolaris.org/[email protected],5.11-0.111:20090617T225413Z installed u---- Note that I'm installing the "alias" package here, (sunstudio). It is empty except for a dependency on sunstudio12u1. % pfexec pkg install pkg://bug13191/sunstudio ... % pkg list -v sunstudio12u1 FMRI STATE UFOXI pkg://bug13191/developer/[email protected],5.11-0.128:20100105T231323Z installed ----- pkg://opensolaris.org/[email protected],5.11-0.111:20090617T225413Z installed u---- % pkg verify pkg://bug13191/developer/[email protected],5.11-0.128:20100105T231323Z % (everything is okay for the new package) % pkg verify pkg://opensolaris.org/[email protected],5.11-0.111:20090617T225413Z installed u---- PACKAGE STATUS pkg://opensolaris.org/sunstudio12u1 ERROR file: opt/sunstudio12.1/prod/include/CC/Cstd/memory Size: 24792 bytes should be 24611 Hash: 71e69188f8a41bb10c8ded763a563e9c5cb7b748 should be bbd3990ba19ef154e254a8e3133097bd33afd85d file: opt/sunstudio12.1/prod/include/CC/Cstd/streambuf Size: 31274 bytes should be 29804 Hash: a007e637cc09e01e932fd2a8614ce80020ecb1a2 should be 12d6330a1c9f1549f968e8fa2218ea37bbd695ee ..... So it looks like files from the old package get clobbered when there are two versions of the same package on two different publishers. Perhaps we need to create a repo with a complete set of old and new sunstudio packages in order to run a sensible test? Does anyone want to suggest the right recipe for transferring the existing sunstudio packages from ipkg.sfbay to our test repo? Assuming that would work around the problem... --chris jasmine wrote: > Hi, > I am testing upgrading sunstudio12u1 to sunstudio12u1(v12.1.1) which is > the patched version. I've done this testing on two environments: > * A system that has the latest dev build installed - build 130 > * A system that has 2009.06 installed > > The steps/results are as follows: > * Dev system > > * Publisher set to opensolaris.org(dev). Installed > [1][email protected];build111 > * Added bug13191(test repo with ss12u1;12.1.1) as preferred > publisher. Tried "pkg install sunstudio12u1" and this failed with > "matching multiple packages" error. I therefore tried and installed > developer/sunstudio12u1. Running CC-V confirmed that I indeed had > the latest version of sunstudio12u1 on the system. (I'll send a > separate email on the import file issues...) > > 2009.06 system > * Publisher set to opensolaris.org(release). Installed sunstudio12u1 > - okay. > * I proceeded to install developer/sunstudio12u1 (as in the above > scenario) and ran into : > > d...@cooljaz:/export/home# pkg install developer/sunstudio12u1 > Creating Plan | > pkg: The following package(s) violated constraints: > Package [2]pkg:/[email protected],5.11-0.128 conflicts with > constraint in installed pkg:/entire: > Pkg SUNWarc: Optional min_version: 0.5.11,5.11-0.111 max > version: 0.5.11,5.11-0.111 defined by: pkg:/entire > > In discussing this issue with an engineer on my team, the error > appears to be the result of "stickiness" i.e. a package can only be > updated from the same repository it was originally installed. > Apparently this is true for 2009.06 (though this doesn't appear to > be true for the dev repo.) > > At this point, I can't do further testing on the "upgradeability" of > sunstudio12u1 without having a repository completely populated with > sunstudio versions 12.1 and 12.1.1. However, in doing the "dev" test as > indicated above, I believe that I've proved that ss12u1 is indeed > upgradeable. > Let me know if I need to do further upgrade testing with specific > instructions on how to mimic the 2009.06 environment. > Thanks > Jas > > References > > 1. mailto:[email protected];build111 > 2. mailto:pkg:/[email protected],5.11-0.128 > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
