On 09/15/10 10:33 PM, Liane Praza wrote:
On 09/15/10 20:57, Susan Scheufele wrote:
Hello IPS dev,
I have an X86 box with OpenSolaris 147 as the initially installed OS, and
I have been trying to onu it to a 147 DEBUG kernel, with no luck so far.
First, I ran into CR 6982819 (onu(1) exits with error - Framework error:
code: 7 reason: couldn't connect to host - on nv147), and used the first
workaround in the bug. Even after that, I still can't seem to onu a 147
DEBUG kernel, and have attached some verbose output from running onu to
install the 147 DEBUG packages. It looks like it succeeds, but then it
does not boot up with the DEBUG kernel afterwards.
Generally speaking, the output that's necessary to debug any failure to
update ("no updates available") is the output from:
pkg install -nv osnet-incorporation@<your version>
For your particular case, I believe that's:
pkg install -nv [email protected],5.11-0.147:20100817T095330Z
The output will be copious, so redirecting to a file and looking for
FAIL is often useful.
The most common failure I see on recently installed machines, though, is
that your publishers don't point to a non-ON repository with recent
enough bits. If "pkg publisher" doesn't say opensolaris.org is pointing
to ipkg.sfbay/dev (or an equivalent in your locale), that's your
problem. The ouptut I mentioned above will confirm that you can't get
non-ON packages from a recent enough version.
Another possibility to keep in mind is that 'image-update' (and
therefore, onu) updates your system to the *newest* versions of packages
it *can* on your system.
That means if the non-debug packages were built *after* the debug ones,
then the system will be upgraded to the non-debug ones.
Long term, debug and non-debug for ON packages will be handled through
variants and then you can explicitly select which you want and go back
and forth between them.
-Shawn
_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
