Hi.
Thanks for the detailed report.
On 06/ 7/16 10:20 PM, Tim Mooney wrote:
I also see that firefox 45.0.2 isn't happy with the Java plug-in:
LoadPlugin: failed to initialize shared library
/usr/jdk/instances/jdk1.7.0_80/jre/lib/i386/libnpjp2.so [ld.so.1:
firefox: fatal: relocation error: file
On 06/ 7/16 09:20 PM, Tim Mooney wrote:
First: Nikola, shouldn't the wiki article be more obvious in giving
credit
to Ben for his post?
Article written on Wiki is inspired by obviously useful stop-by-step
procedure but is part of Openindiana. In the bottom of the post you will
find "Article
In regard to: Re: [OpenIndiana-discuss] Testing updates from /dev to...:
Thanks for the great job.
Sorry to follow up to a month-old post, but I wanted to give thanks and
a "shout out" to Ben for posting these step-by-step instruction, which Nikola
has replicated to the wiki:
http://w
On 05/12/16 06:27 AM, benta...@chez.com wrote:
Hi,
For the moment I just notice tiny differences :
- openvpn on /dev comes from sfe and uses /etc/openvpn/config as default
config file
- openvpn on /hipster-2015+ comes from main and uses
/etc/openvpn/openvpn.conf as default config file
Testing m
Hi,
For the moment I just notice tiny differences :
- openvpn on /dev comes from sfe and uses /etc/openvpn/config as default
config file
- openvpn on /hipster-2015+ comes from main and uses
/etc/openvpn/openvpn.conf as default config file
Testing more package is quite hard, for example I only d
Hi,
What I mean is during the validation phases of the pkg update, pkg
refuse to update various package due to conflicts not resolvable
(notably perl, php, mysql) when pkg update from /dev to /hipster-2015
does validate and succeed.
So to speak, the update doesn't take place per say as it fail
On 05/10/16 09:58 AM, Alexander Pyhalov wrote:
On 05/10/2016 01:13, benta...@chez.com wrote:
Hi,
But the latest fails due to a bunch of pkg list |grep '0\.151\.1\.'
packages.
Hi.
What do you mean by "the latest fails" - does update fail or after
update there are *0.151.1* packages are left
On 05/10/2016 01:13, benta...@chez.com wrote:
Hi,
But the latest fails due to a bunch of pkg list |grep '0\.151\.1\.' packages.
Hi.
What do you mean by "the latest fails" - does update fail or after
update there are *0.151.1* packages are left? If the latter, can you
share the list?
--
С
On 05/10/16 12:13 AM, benta...@chez.com wrote:
But the latest fails due to a bunch of pkg list |grep '0\.151\.1\.' packages.
So it is not possible right now to update directly from /dev to /hipster
Thanks very much Ben!
See if you can stay inside ML thread with a reply, with no new thread
(ne
Hi,
Today I started to the update from 151a9 to hipster (without hipster-2015
stage).
I followed the same process than the one I described before :
1 - Create a BE to start and boot to it :
# beadm create -a Openindiana-HipUpdate-S1
# reboot
2 - remove all packages from external repositories (li
On 05/ 9/16 07:20 AM, benta...@chez.com wrote:
Thanks for the great job.
Yes, thanks actually to those people making it possible.
Thank you bentahyr very much for testing and putting updating
instructions on the ML, even more nicer ones then I expected.
I have put update and testing instructi
Thanks for the great job.
I tested today the update from oi_151a9 to Hipster2015 to hipster.
It was a long journey.
The hardware is a Dell Precision T5400 (16GB of memory and 2 mirrored pools)
It took me the whole day as I have very poor IO performance on that hardware.
Here is the process I foll
On 05/ 7/16 02:06 PM, Alexander Pyhalov wrote:
Not sure that we can update /hipster-2015 fast. Current build server
can't be used for this,
as it has already gone further. So, for example, if you want to
rebuild A and A needs B, and
build server has B installed from /hipster, and B from /hipster
Nikola M писал 07.05.2016 09:11:
So if some problem with updating is found, we can spin up build
process and renew some packages in hipster-2015, while making also the
same changes in /hipster if it makes better for /dev update.
After that, hipster-2015 -> 20160421 snapshot update should also wo
On 05/ 6/16 10:25 PM, Tim Mooney wrote:
For example, the repo for hipster has changed, correct? Should it
(in theory) be possible to go directly from /dev to the latest /hipster,
or is the chance for success higher if one first updates from /dev to
/hipster-2015, and then (if that works) from /h
In regard to: [OpenIndiana-discuss] Testing updates from /dev to...:
On 05/ 5/16 07:56 PM, Tim Mooney wrote:
Can you point out the email message in the archives or elsewhere that
the /dev-to-/hipster process is documented?
It is not documented because it requires from you and everyone else r
On 05/ 5/16 07:56 PM, Tim Mooney wrote:
Can you point out the email message in the archives or elsewhere that
the /dev-to-/hipster process is documented?
It is not documented because it requires from you and everyone else
reading this, to start testing updating from /dev to /hipster-2015 (or
17 matches
Mail list logo
