Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h

[Dan McDonald]

Thank you all for your efforts.

Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Upgrade from r151020 to r151022 - python conflicts and fails.

[Andries Annema]

Contrary to the instructions, you might wanna try the suggestion from 
Michael Talbott earlier on this list (look for a discussion titled 
"[OmniOS-discuss] Python conflicts in upgrade from 20 to 22"):


Instead of entering ...

/usr/bin/pkg update --be-name=omnios-r151022entire@11,5.11-0.151022

... you should enter:

/usr/bin/pkg update --be-name=omnios-r151022

This suggestion helped me around this issue as well, two days ago.

Regards,
Andries


On 2017-07-13 13:52, Svavar Örn Eysteinsson wrote:

Thx for the reply Andy.





No zones on this box.

My ca-bundle is april 2017 :

pkg://omnios/web/ca-bundle@5.11-0.151020:20170414T020145Z

No updates needed for pkg, :

pkg install pkg:/package/pkg
No updates necessary for this image.

Strange...






On 13 Jul 2017, at 11:48, Andy Fiddaman  wrote:



On Thu, 13 Jul 2017, Svavar ?rn Eysteinsson wrote:

; As anyone encounter a upgrade fail from 20 to 22 ?
; I'm unable and get conflicts regarding python.
;
; Current system is :
; OmniOS v11 r151020
; OmniOS 5.11 omnios-r151020-4151d05  March 2017
;
; Before I did as the upgrade instructions stated, :
;
;
; /usr/bin/pkg unset-publisher omnios
; /usr/bin/pkg set-publisher -P --set-property 
signature-policy=require-signatures -g https://pkg.omniti.com/omnios/r151022/ 
omnios
;
;
; And my current publishers are :
;
; PUBLISHER   TYPE STATUS P LOCATION
; omnios  origin   online F 
https://pkg.omniti.com/omnios/r151022

What are the versions of of your web/ca-bundle ad package/pkg packages?
Does this system have any zones? If so, what brand?

It is worth making sure that 'pkg' is up-to-date before attempting the upgrade:


pkg install pkg:/package/pkg

and the release notes state that web/ca-bundle must be up-to-date.


https://omnios.omniti.com/wiki.php/Upgrade_to_r151022

Andy

--
Citrus IT Limited | +44 (0)333 0124 007 | enquir...@citrus-it.co.uk
Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
Registered in England and Wales | Company number 4899123



___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss


___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Upgrade from r151020 to r151022 - python conflicts and fails.

[Svavar Örn Eysteinsson]

Thx for the reply Andy.





No zones on this box.

My ca-bundle is april 2017 :

pkg://omnios/web/ca-bundle@5.11-0.151020:20170414T020145Z

No updates needed for pkg, :

pkg install pkg:/package/pkg
No updates necessary for this image.

Strange...





> On 13 Jul 2017, at 11:48, Andy Fiddaman  wrote:
> 
> 
> 
> On Thu, 13 Jul 2017, Svavar ?rn Eysteinsson wrote:
> 
> ; As anyone encounter a upgrade fail from 20 to 22 ?
> ; I'm unable and get conflicts regarding python.
> ;
> ; Current system is :
> ; OmniOS v11 r151020
> ; OmniOS 5.11 omnios-r151020-4151d05  March 2017
> ;
> ; Before I did as the upgrade instructions stated, :
> ;
> ;
> ; /usr/bin/pkg unset-publisher omnios
> ; /usr/bin/pkg set-publisher -P --set-property 
> signature-policy=require-signatures -g https://pkg.omniti.com/omnios/r151022/ 
> omnios
> ;
> ;
> ; And my current publishers are :
> ;
> ; PUBLISHER   TYPE STATUS P LOCATION
> ; omnios  origin   online F 
> https://pkg.omniti.com/omnios/r151022
> 
> What are the versions of of your web/ca-bundle ad package/pkg packages?
> Does this system have any zones? If so, what brand?
> 
> It is worth making sure that 'pkg' is up-to-date before attempting the 
> upgrade:
> 
>> pkg install pkg:/package/pkg
> 
> and the release notes state that web/ca-bundle must be up-to-date.
> 
>> https://omnios.omniti.com/wiki.php/Upgrade_to_r151022
> 
> Andy
> 
> -- 
> Citrus IT Limited | +44 (0)333 0124 007 | enquir...@citrus-it.co.uk
> Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
> Registered in England and Wales | Company number 4899123
> 


___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Upgrade from r151020 to r151022 - python conflicts and fails.

[Andy Fiddaman]

On Thu, 13 Jul 2017, Svavar ?rn Eysteinsson wrote:

; As anyone encounter a upgrade fail from 20 to 22 ?
; I'm unable and get conflicts regarding python.
;
; Current system is :
; OmniOS v11 r151020
; OmniOS 5.11 omnios-r151020-4151d05  March 2017
;
; Before I did as the upgrade instructions stated, :
;
;
; /usr/bin/pkg unset-publisher omnios
; /usr/bin/pkg set-publisher -P --set-property 
signature-policy=require-signatures -g https://pkg.omniti.com/omnios/r151022/ 
omnios
;
;
; And my current publishers are :
;
; PUBLISHER   TYPE STATUS P LOCATION
; omnios  origin   online F 
https://pkg.omniti.com/omnios/r151022

What are the versions of of your web/ca-bundle ad package/pkg packages?
Does this system have any zones? If so, what brand?

It is worth making sure that 'pkg' is up-to-date before attempting the upgrade:

   > pkg install pkg:/package/pkg

and the release notes state that web/ca-bundle must be up-to-date.

   > https://omnios.omniti.com/wiki.php/Upgrade_to_r151022

Andy

-- 
Citrus IT Limited | +44 (0)333 0124 007 | enquir...@citrus-it.co.uk
Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
Registered in England and Wales | Company number 4899123

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h

[Al Slater]

Congratulations and thank you for your efforts!!

On 12/07/2017 16:32, Tobias Oetiker wrote:
> # OmniOS Community Edition 
> 
> On April 21st 2017, OmniTI announced that they would suspend active 
> development of OmniOS and support contracts would not be renewed. 
> 
> While this announcement left many users stunned, others focused more on the 
> fact that OmniTI in their announcement also expressed the hope that "the 
> community" would take up further development of the OS. 14 weeks later, 
> OmniOS Community Edition is a reality. 
> 
> Andy Fiddaman (www.citrus-it.net), Tobias Oetiker (www.oetiker.ch) and 
> Dominik Hassler have spent some quality time setting up the systems and 
> procedures allowing us to take over maintenance and development of OmniOS. In 
> this endeavour we were supported by many. Special thanks to Stefan Husch 
> (www.qutic.com), Peter Tribble (www.petertribble.co.uk), Dan McDonald and 
> Theo Schlossnagle (www.circonus.com). 
> 
> We have forked the OmniOS repos and pulled in bugfixes and security fixes 
> that have been published since the release of OmniOS r151022. After setting 
> up our own package repository and updating the build infrastructure, we are 
> finally ready to go public. We are following the established OmniOS release 
> naming scheme by releasing 
> 
> 
> ## OmniOSce r151022h, 12th July 2017
> 
> The new release contains the following fixes: 
> 
> - expat updated to version 2.2.1 (fixes CVE-2017-9233) 
> - openssl updated to version 1.0.2l 
> - curl updated to version 7.54.1 
> - bind updated to version 9.10.5-P3 
> - p7zip updated to fix CVE-2016-9296 
> - web/ca-bundle updated to include OmniOSce Certificate Authority certificate 
> 
> `uname -a` shows omnios-r151022-f9693432c2 (no change in this release) 
> 
> Our work does not stop here though. First we are committed to quickly 
> releasing updates for r151022 as the need arises. We are also working towards 
> releasing r151024 on schedule. To that end, we have already updated the 
> bloody environment with all the latest goodies from upstream illumos and 
> joyent-lx repositories. 
> 
> OmniOS community edition hosts its sources on https://github.com/omniosorg/ 
> and if you want to get in touch, you can find us on 
> https://gitter.im/omniosorg/Lobby 
> 
> https://pkg.omniosce.org/r151022/core/
> ## Release Schedule 
> 
> The intention is for new stable releases to continue to come out every 26 
> weeks. Interim, "weekly" updates to stable follow a fixed schedule denoted by 
> letters, one per week. Weekly releases are made as needed, so there may not 
> be a release each week. The first release of a new stable version is 
> synonymous with weekly release "a", though the letter is not used. 
> 
> During the intervals between stable releases, Bloody moves forward rapidly, 
> picking up changes from upstream illumos-gate and illumos-joyent as well as 
> updating various userland packages. In general, upstream merges will be 
> performed on a Thursday/Friday each week and weekly releases will be 
> published on a Monday. 
> 
> Bloody releases will be published on an ad-hoc basis but may be as frequent 
> as every week. 
> 
> Security fixes are excluded from the schedule and handled with priority as 
> they occur. 
> 
> 
> ## How to Upgrade 
> 
> All OmniOS packages are signed and the pkg installer is configured to only 
> allow trusted sources for the core packages. In order to upgrade to the new 
> OmniOS community edition, you have to let your box know that the updates will 
> be coming from a new trusted source. This means you will have to import our 
> CA certificate into your system. 
> 
> 1. Get a copy of the new certificate 
> 
> ```
> # /usr/bin/wget -P /etc/ssl/pkg \
> https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem 
> ```
> https://pkg.omniosce.org/r151022/core/
> 2. Check the certificate fingerprint 
> 
> ```
> # /usr/bin/openssl x509 -fingerprint \
> -in /etc/ssl/pkg/omniosce-ca.cert.pem -noout 
> ```
> 
> `8D:CD:F9:D0:76:CD:AF:C1:62:AF:89:51:AF:8A:0E:35:24:4C:66:6D`
> 
> 
> 3. Change the publisher to our new repo 
> 
> ```
> # /usr/bin/pkg set-publisher -P \
>-G https://pkg.omniti.com/omnios/r151022/ \
>-g https://pkg.omniosce.org/r151022/core/ omnios 
> ```
> 
> 4. For each native zone (if you have any), run 
> https://pkg.omniosce.org/r151022/core/
> ```
> # /usr/bin/pkg -R  set-publisher -P \
>-G https://pkg.omniti.com/omnios/r151022/ \
>-g https://pkg.omniosce.org/r151022/core/ omnios 
> ```
> 
> (get a list of all your zones by running `zoneadm list -cv` for the 
> ``, add `/root` to the PATH given in the list.) 
> 
> 
> 5. Install the new ca-bundle containing our new CA 
> 
> ```
> # /usr/bin/pkg update -rv web/ca-bundle 
> ```
> 
> 6. Remove the CA file imported by hand 
> 
> ```
> # rm /etc/ssl/pkg/omniosce-ca.cert.pem 
> ```
> 
> 7. Finally update as usual 
> 
> ```https://pkg.omniosce.org/r151022/core/
> # /usr/bin/pkg update -rv 
> ```
> 
> 
> ##