<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi guys,</p>
<p>Trying to update a r151022 (test)system with a number of lipkg
and lx zones to the latest r151022al version, using "pkg update
-nv", but it fails with:</p>
<p><quote><br>
Planning linked: 1/7 done; 1 working: zone:<zonename><br>
Linked progress: -pkg: update failed (linked image exception(s)):<br>
<br>
A '<b>sync-linked</b>' operation failed for child
'zone:<zonename>' with an unexpected<br>
return value of 1 and generated the following output:<br>
pkg: 0/1 catalogs successfully updated:<br>
<br>
The content of the catalog for publisher 'omnios' doesn't match
the catalog's attributes. This is likely the result of a mix of
older and newer catalog files being provided for the publisher.<br>
</quote><br>
</p>
<p><br>
</p>
<p>When I instead run "pkg update -nrv", it fails with almost the
same message:<br>
</p>
<p><quote><br>
Planning linked: 1/7 done; 1 working: zone:<zonename><br>
Linked progress: |pkg: update failed (linked image exception(s)):<br>
<br>
A '<b>update</b>' operation failed for child
'zone:<zonename>' with an unexpected<br>
return value of 1 and generated the following output:<br>
pkg: 0/1 catalogs successfully updated:<br>
<br>
The content of the catalog for publisher 'omnios' doesn't match
the catalog's attributes. This is likely the result of a mix of
older and newer catalog files being provided for the publisher.<br>
</quote><br>
</p>
<p><br>
</p>
<p>Google-ing for this issue does give some reports, but mostly of
age and a clear solution - at least to me - doesn't seem
available.<br>
I have never before updated this system - since I installed this
test-VM last summer - not from the GZ, nor from within any NGZ.<br>
Funny thing is that not every zone leads to such an error; for at
least one other zone a nice update plan was reported before it
bailed out on the next zone with the error quoted above.<br>
</p>
<p>Other than destroying each zone for which it reports this error,
any thoughts on how to solve this issue?<br>
In the past, I've never had such issues with ipkg zones; I may be
doing something wrong with these lipkg zones.<br>
</p>
<p>Cheers,<br>
Andries<br>
</p>
</body>
</html>