Re: [oi-dev] 2018.10 targets
- Virtualbox failure after FPU changes https://www.illumos.org/issues/9761 , https://www.virtualbox.org/ticket/17947 is a serious one,a. I reviewed it. Can work with their devs (as time permits). - Nimbus theme GTK3 a. Nimbus conversion to GTK3 - MATE 1.20a. Commit what works now. Update vte as time permits. ~K On Friday, September 28, 2018, 2:40:06 AM PDT, Aurélien Larcher wrote: On Fri, Sep 28, 2018 at 10:41 AM Alexander Pyhalov via oi-dev wrote: Hi, folks. We are approaching October. While I have limited time now, I want to coordinate priorities and targets, what should we do till end of October (and due to personal reasons, I'd better announce snapshot till 20 October or earlier or allow someone else to do this). We have several regressions and problems, which would be good to fix. 1) Virtualbox failure after FPU changes https://www.illumos.org/issues/9761 , https://www.virtualbox.org/ticket/17947 is a serious one, but I'm afraid I lack skills to fix it in reasonable time. The stack trace itself doesn't seem related to illumos-gate changes, but likely it is. In KVM Joyent fixed this using new hma_fpu_* API, but Virtualbox structures to store VM registers differ and from brief overlook it has several asm functions to store/restore Host/Base registers state. So far I don't have an idea how convert one to another. So, this likely will be broken in 2018.10 unless someone skillful dig into this. 2) sbcl issues - threaded sbcl can not be built after KPTI changes, it fails FLOCK and posix tests. Needs investigation. It's a serious issue, because threaded sbcl is needed to build pgloader. 3) Our Mate is a bit old, but newer Mate requires updated GTK3 . Updated GTK3 IIRC has dropped support for theme engines, and so our Nimbus theme based on unico engine doesn't work. Also I've heard there were issues with new mate-terminal. Michal, do you have some comments here? 4) As for new features, I really want to see KVM zones, perhaps, I'll dig into this shortly. Does somebody have another targets/comments? Please, avoid turning this topic in bike-shedding, I want to hear OI developers in a way "I ll take item #N" or "I expect to finish feature A before snapshot", not "please, also fix this and that". Hi Alexander, I'll be busy as well and my skills are not up to tasks #1 or #2... the only tracks I can pursue for now are: 1) fixing pkg and gfx-drm components so that we can migrate userland to gcc-8 before or after the snapshot. 2) pushing Firefox 60esr 3) updating Xorg to latest 4) fixing openmpi which has been broken before summer If I have time to fix audacity then we can also update ffmpeg and vlc. I had some fixes for drm/i915 but my Intel box died 4 months ago so this is on hold until I can replace it. Kind regards, Aurélien Best regards, Alexander Pyhalov, system administrator of Southern Federal University IT department ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev -- --- Praise the Caffeine embeddings ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] 2018.10 targets
On Sat, Sep 29, 2018 at 9:01 AM Michal Nowak wrote:
> On 09/28/18 10:41 AM, Alexander Pyhalov via oi-dev wrote:
> > Hi, folks.
> >
> > We are approaching October. While I have limited time now, I want to
> > coordinate priorities and targets, what should we do till end of
> > October (and due to personal reasons, I'd better announce snapshot
> > till 20 October or earlier or allow someone else to do this).
> >
> > We have several regressions and problems, which would be good to
> > fix.
> >
> > 1) Virtualbox failure after FPU changes
> > https://www.illumos.org/issues/9761 ,
> > https://www.virtualbox.org/ticket/17947 is a serious one, but I'm
> > afraid I lack skills to fix it in reasonable time. The stack trace
> > itself doesn't seem related to illumos-gate changes, but likely it
> > is. In KVM Joyent fixed this using new hma_fpu_* API, but Virtualbox
> > structures to store VM registers differ and from brief overlook it
> > has several asm functions to store/restore Host/Base registers state.
> > So far I don't have an idea how convert one to another. So, this
> > likely will be broken in 2018.10 unless someone skillful dig into
> > this.
> >
> > 2) sbcl issues - threaded sbcl can not be built after KPTI changes,
> > it fails FLOCK and posix tests. Needs investigation. It's a serious
> > issue, because threaded sbcl is needed to build pgloader.
> >
> > 3) Our Mate is a bit old, but newer Mate requires updated GTK3 .
> > Updated GTK3 IIRC has dropped support for theme engines, and so our
> > Nimbus theme based on unico engine doesn't work. Also I've heard
> > there were issues with new mate-terminal. Michal, do you have some
> > comments here?
>
> I run MATE 1.20 as seen in the PR and it works fine but:
>
> (1) Nimbus theme. I stick to "Traditional" theme.
>
> (2) Pluma text editor's text area blinks annoyingly. Might be an
> Intel-only issue. Upstream issue reported.
>
> (3) MATE Terminal requires new vte library which does not work for us.
> From my investigation I noticed that some #ifdef __sun were removed
> from newer vte. Also I haven't seen new vte for non-Linux OS (pkgsrc,
> BSDs, ...).
>
> I don't think I am able to do anything about those.
>
Which version does pkgsrc deliver? J. Perkin seems to have worked on MATE
1.20.
>
> >
> > 4) As for new features, I really want to see KVM zones, perhaps, I'll
> > dig into this shortly.
> >
> > Does somebody have another targets/comments?
>
> I will work on openQA tests for them to be in shape for the snapshot and
> test the images once test-snapshot is available.
>
> Also I had some progress with Meson but can't promise this.
>
I packaged Meson last year but this is a mess...
Need to implement the specificities of illumos systems all over again...
and the way it is structures looks like the usual entangled "if(totoOS) {}
else if (babarOS) else if (fooOS) {} etc" all over the place.
First thing back then was to notice that GCC => GNU ld in their rules...
>
> Michal
>
> >
> > Please, avoid turning this topic in bike-shedding, I want to hear OI
> > developers in a way "I ll take item #N" or "I expect to finish
> > feature A before snapshot", not "please, also fix this and that".
> >
> > Best regards, Alexander Pyhalov, system administrator of Southern
> > Federal University IT department
> >
> >
> >
> > ___ oi-dev mailing list
> > oi-dev@openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev
> >
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
--
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] 2018.10 targets
On 09/28/18 10:41 AM, Alexander Pyhalov via oi-dev wrote: Hi, folks. We are approaching October. While I have limited time now, I want to coordinate priorities and targets, what should we do till end of October (and due to personal reasons, I'd better announce snapshot till 20 October or earlier or allow someone else to do this). We have several regressions and problems, which would be good to fix. 1) Virtualbox failure after FPU changes https://www.illumos.org/issues/9761 , https://www.virtualbox.org/ticket/17947 is a serious one, but I'm afraid I lack skills to fix it in reasonable time. The stack trace itself doesn't seem related to illumos-gate changes, but likely it is. In KVM Joyent fixed this using new hma_fpu_* API, but Virtualbox structures to store VM registers differ and from brief overlook it has several asm functions to store/restore Host/Base registers state. So far I don't have an idea how convert one to another. So, this likely will be broken in 2018.10 unless someone skillful dig into this. 2) sbcl issues - threaded sbcl can not be built after KPTI changes, it fails FLOCK and posix tests. Needs investigation. It's a serious issue, because threaded sbcl is needed to build pgloader. 3) Our Mate is a bit old, but newer Mate requires updated GTK3 . Updated GTK3 IIRC has dropped support for theme engines, and so our Nimbus theme based on unico engine doesn't work. Also I've heard there were issues with new mate-terminal. Michal, do you have some comments here? I run MATE 1.20 as seen in the PR and it works fine but: (1) Nimbus theme. I stick to "Traditional" theme. (2) Pluma text editor's text area blinks annoyingly. Might be an Intel-only issue. Upstream issue reported. (3) MATE Terminal requires new vte library which does not work for us. From my investigation I noticed that some #ifdef __sun were removed from newer vte. Also I haven't seen new vte for non-Linux OS (pkgsrc, BSDs, ...). I don't think I am able to do anything about those. 4) As for new features, I really want to see KVM zones, perhaps, I'll dig into this shortly. Does somebody have another targets/comments? I will work on openQA tests for them to be in shape for the snapshot and test the images once test-snapshot is available. Also I had some progress with Meson but can't promise this. Michal Please, avoid turning this topic in bike-shedding, I want to hear OI developers in a way "I ll take item #N" or "I expect to finish feature A before snapshot", not "please, also fix this and that". Best regards, Alexander Pyhalov, system administrator of Southern Federal University IT department ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
