On Thu, 29 Dec 2016, Jim Klimov wrote:
Bob, do you mean symbols like 'this requires SUNW_1.23'? Yes, these
are here too. I believe they do not quite work around the issue
James describes, e.g. when your running binary pulls two copies of
different libjpeg.so.* even with proper versioning.
29 декабря 2016 г. 22:25:23 CET, Bob Friesenhahn
пишет:
>On Thu, 29 Dec 2016, James Carlson via openindiana-discuss wrote:
>> Now we deliver a new libfoo.so.2. The guy who maintains our
>application
>> is a real go-getter, so he relinks and redelivers binaries
On Thu, 29 Dec 2016, James Carlson via openindiana-discuss wrote:
Now we deliver a new libfoo.so.2. The guy who maintains our application
is a real go-getter, so he relinks and redelivers binaries almost right
away. When the application runs, it pulls in libfoo.so.2 and (via the
libbar.so.1
Hi.
On 29.12.2016 19:26, russell wrote:
Hi,
I have been able to perform updates using which I find does work.
# pkg refresh --full
# pkg update --be-name openindiana-hipster-NN
Try ' pkg update -v
Hi,
I have been able to perform updates using which I find does work.
# pkg refresh --full
# pkg update --be-name openindiana-hipster-NN
However, when attempt to perform an image update
# pkg image-update -v --be-name openindiana-hipster-NN
Creating Plan (Running solver): /
pkg update: No