Hi
On one box i had SRU1 build 03 installed on topof 175b, I ran pkg update
and hit CR 7110134, fair enough, on another box that had vanilla 175b
though, with SRU publisher repo set, I tried a pkg update as well and it
went though fine, but turns out it only took me to SRU1 build 03, when
build 04 is available in the repo.
pkg update neever mentioned that it was taking me to a version of entire
I did not want, I explicitly wanted 04 build of SRU 1.
It was only after I rebooted and chekcked entire I saw that I had a
version that I did not want, only then when I ran pkg update again did I
see the error message telling me about the data/xml-common dependency issue.
Only the fact that I was expecting the error initially made me double
check what pkg had done and discover that it had done something very
much against my wishes without me knowing, I had rebooted etc by this stage.
Surely a packaging system that makes arbitrary decisions with out
telling me is at best a bug?
If it had at least told me there was a problem with going to latest and
still done the update to say build 03 I would have been somewhat
happier, I would have seen it was 7110134 and just removed the new BE
without doing a reboot.
Are customers/end users seriously expected to double check before a
reboot every time?
Is it documented that end users need to double check things like this?
A warning after pkg update had completed that there was an issue going
to latest is the very minimum I'd have expected.
I can log a CR to get pkg update to at least inform user of why it has
made a decision about what version it has determined is the latest it
can go to if there is later available.
Enda
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
