Hi,
If this issue is resolved, I am planning to integrate the changes in
build 146 that closes on 8/2.
So, any inputs would be appreciated.
Regards,
Gowtham
On 7/30/2010 12:49 AM, Gowtham wrote:
Hi
There are 3 packages I am obsoleting from ON gate(sea, sea-config,
mibiisa). Of which one of them is required by a package in SFW gate.
net-snmp(SFW) requires sea-config(ON - which I am obsoleting).
The net-snmp package(from SFW) when being converted from SVR4 to
IPS(through scripts in pkg-gate), a dependency on sea-config package
is added to the pkg manifest.
Does this dependency need to be removed from pkg-gate a build before
my EOF changes, or can they happen in the same build?
To check my EOF changes, I tried doing an ONU on the nightly generated
packages from my workspace.
Base system was running freshly installed snv_142 and my workspace
nightly had snv_146 packages.
Result: The image-update in ONU does not find any upgrade plan.
I interrupted the ONU at image-update phase and ran verbose pkg
install of all consolidations to get the error log.
Reason of failure might be due to the net-snmp -> seaport dependency
on the system.(as in last lines of the log)
Log at
http://jurassic.eng/net/onnv-x86-build.india/builds/gowtham/seach/test/log
To verify whether that was the correct root-cause, I reinstalled the
net-snmp package on the base system
to the one in my custom repo that does not have a dependency on
sea-config.
Even then, the ONU failed with other reasons as in the below log
http://jurassic.eng/net/onnv-x86-build.india/builds/gowtham/seach/test/log_sec
I have followed the steps in usr/src/pkg/README to remove the packages
and its renamed ancestors.
I would like to get some help on the failures.
And, how can we make sure that the ONU does not fail after I EOF the
packages? Can we make ONU pull in the modified net-snmp(from SFW)
before it can image-update?
You can have a look at the last page of the following webrev to find
the IPS specific changes in ON
http://jurassic.eng/net/10.12.184.118/builds/gowtham/seach/webrev
And one more question. Being a dev repo, doesn't
http://pkg.opensolaris.org/dev need to contain packages of latest
Nevada builds?
I only see pkg upto build 134 on the pkg list. ONU uses this specific
repo in its script before it runs a image-update.
Regards,
Gowtham
On 07/27/10 00:07, Liane Praza wrote:
On 07/26/10 04:44 AM, Gowtham T wrote:
Hi,
I am working on SEA code removal from Nevada which involves file
removal
from ON and SFW gates.
Some, daemons and SMF services are removed. And the changes also
involve
removing some packages, modifying some others.
Removing sea, sea-config, mibiisa
Modifying library/lint, net-snmp, net-snmp/addons
The ON gate on nightly generates IPS packages and the SFW gate
generates
SVR4 packages.
To test my package specific changes, I created a custom repository with
the modified/obsoleted packages along with necessary changes to
consolidations. The commands run are as below
For ON, osnet-incorporation should have been updated for you when you
did the EOF as is described in
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/pkg/README.pkg
in the EOFs and Removals section. Please make sure you've followed
those instructions carefully. Never ever hg remove a package
manifest file in ON.
For SFW, simply doing the normal package EOF process (mail to RE,
remove the SVR4 package data) will cause the right thing to be done
by David Comay during the build where your SFW changes are integrated.
The other test I'd suggest is that if you aren't intending on
creating a cross-consolidation flag-day, please make sure you test
*just* your ON changes without having upgraded your test system to
your SFW changes. That is, make sure that life for normal ON
developers will work. For SFW developers, where they aren't yet
using IPS packages natively, there isn't as much you can or need to
test.
Finally, I suggest searching ipkg.sfbay/dev for the packages you're
obsoleting to make sure that there's nothing else surprising that's
depending on those packages.
I had to modify the consolidations osnet and sfw because to upgrade my
custom packages, I had to
remove those entries from the consolidations. Otherwise, pkg command
would not allow them to be upgraded.
While that's a workaround, the WOS constructs things to incorporate
the obsolete packages at the obsolete version. That's what the ON
instructions described above make sure happen.
I am not sure if this testing done is sufficient. So, I wanted to know
what sort of
testing should be done when IPS/SVR4 packages are obsoleted/modified?
And, how do u test a complete image upgrade of a system to the latest
modified packages? Do I need to setup a complete to do so?
You can easily do this in ON by installing a system with the last WOS
build of OpenSolaris normally, installing the package you expect to
be removed, and then using onu/image-update to update to your built
ON repository. If you've done everything correctly, the
files/services you deleted will no longer be on the system, and the
packages you've obsoleted will no longer be there either.
liane
_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
