On 11/29/10 20:00, Shawn Walker wrote:
On 11/26/10 06:48 AM, Chris Gerhard wrote:
On 11/23/10 18:42, Shawn Walker wrote:
On 11/23/10 09:58 AM, Chris Gerhard wrote:
Is there a way to list packages that are going to cause problems? The
upgrade I have just done appears to have completed but when booted
show it still on 134b/
No, because that package system doesn't know what packages are a
"problem". The package system intentionally allows you to install and/or
create packages that constrain your system in a way that prevents all or
certain parts of it from upgrading.
That's necessary functionality so that your system can be upgraded
properly from build to build.
However, it also means that it can't automatically determine when your
system "should have been" upgraded and when it "should not be". It only
knows what the packages you installed tell it.
With that said, you can "tell it" what you expect to happen by doing
things like this:
pkg install -nv ent...@0.5.11-0.151 \
`pkg list -H | grep 'consolidation/*incorporation' |\
awk '{print $1"@0.5.11-0.151"}'` 2>&1 > /tmp/pkg.debug
Then check the output like this:
grep -e FAIL -e incompatible /tmp/pkg.debug
If the grep produces anything, you'll need to look at the log file and
read through to determine what went wrong.
If the grep didn't produce anything, you likely didn't configure your
system according to the release notes. Check the configuration of your
publishers, verify that everything matches the release notes, and try
again.
-Shawn
I don't think there is anything that is contrary to the release notes.
kr...@cores2-dm-dev:~$ pkg install -nv ent...@0.5.11-0.151 \
`pkg list -H | grep 'consolidation/*incorporation' |\
awk '{print $1"@0.5.11-0.151"}'` 2>&1 > /tmp/pkg.debug
pkg: No solution was found to satisfy constraints
kr...@cores2-dm-dev:~$ grep -e FAIL -e incompatible /tmp/pkg.debug
grep: illegal option -- e
Use 'ggrep' instead of 'grep' here. Sorry, the -e option is GNU grep
specific; forgot about that.
I did that (well used /usr/gnu/bin/grep ) and it was in my email:
I don't think there is anything that is contrary to the release notes.
kr...@cores2-dm-dev:~$ pkg install -nv ent...@0.5.11-0.151 \
`pkg list -H | grep 'consolidation/*incorporation' |\
awk '{print $1"@0.5.11-0.151"}'` 2>&1 > /tmp/pkg.debug
pkg: No solution was found to satisfy constraints
kr...@cores2-dm-dev:~$ grep -e FAIL -e incompatible /tmp/pkg.debug
grep: illegal option -- e
Usage: grep -hblcnsviw pattern file . . .
kr...@cores2-dm-dev:~$ /usr/gnu/bin/grep -e FAIL -e incompatible /tmp/pkg.deb>
kr...@cores2-dm-dev:~$ pkg publisher
PUBLISHER TYPE STATUS URI
solaris (preferred) origin online
http://pkg.oracle.com/solaris/release/
opensolaris.org (non-sticky) origin online
http://pkg.opensolaris.org/release/
kr...@cores2-dm-dev:~$
I followed the instructions to the letter and have just tried it again. Same
thing.
--
Oracle <http://www.oracle.com/>
Chris Gerhard - Chief Technologist
Systems TSC
Phone: +44 (0) 11892 49022
The *MSC* and *SunSolve* Will Soon Retire
Find out what you need to know about the migration
to "My Oracle Support"
<http://www.oracle.com/us/support/044752.html>
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
