The problem still exists in the ON build 139 repo. I suggest opening a
bug for this issue. It might be too late for getting fixed in 139, but
it might have a chance of being addressed for 140.
-- Alan
On 05/ 4/10 04:02 PM, Danek Duvall wrote:
Peter Dennis wrote:
- a package didn't get published to the repository that should have
- something went wrong during merge
Does this imply something is wrong with the repo ? If this is the
case is it worth republishing the storage/mpathadm with a 'correct'
manifest ?
If this were a problem in the release candidates, then yes. And it needs
to be fixed going forward. But for a handful of builds at the beginning of
the next release cycle, it's not worth it. People moving to /dev from
2010.1H will naturally hit a build where this has been fixed, and the next
release won't have this problem.
Danek
_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
