Re: [blfs-dev] sassc and gtk+3
On 12/3/19 4:04 PM, Pierre Labastie via blfs-dev wrote: Le 03/12/2019 à 21:52, Wayne Blaszczyk via blfs-dev a écrit : On Tue, 2019-12-03 at 12:15 -0600, Bruce Dubbs wrote: On 12/3/19 1:49 AM, Wayne Blaszczyk wrote: On Mon, 2019-12-02 at 21:44 -0600, Bruce Dubbs via blfs-dev wrote: I've been trying to update to the latest gtk+3, but have been getting massive failures during the regression tests. Upon investigation, most of the failures are due to a .css file generated by sassc. With some manual modification, the gtk+ tests are back to normal. This problem seems to occur with sassc-3.6, but not sassc-3.5. Upstream gtk maintainers and most other distros that we checked are still at sassc-3.5, although I can find references to both sassc-3.5.5 and sassc 3.6.1 on Arch. In BLFS, the packages that use sassc are gnome-shell, gnome-shell-extensions, plasma, and gtk+3. We currently have sassc-3.6.1 and libsass-3.6.3. The question is whether we should roll back sassc/libsass to version 3.5 or should just say that the test suite for gtk+3 is broken? Opinions? Probably related, but I had issues with libsass-3.6.3. The Gnome environment was basically unusable. Things like gnome-terminal would not start most of the time. I had to revert back to libsass-3.6.1, before things became stable again. I kept sassc at 3.6.1 . This was all running under a VM. I don't run the gtk3 tests, so I cannot comment on that. Probably due to this issue: https://github.com/sass/libsass/issues/303 Sorry, copy/paste issue, it should be https://github.com/sass/libsass/issues/3033 Looks like there are commits in the GTK+ repo: https://gitlab.gnome.org/GNOME/gtk/commit/619c892032cab24dadceb8ca9025486419fcde9c https://gitlab.gnome.org/GNOME/gtk/commit/87ea0253aaa2f750de32be7e0ab51f0a1f5ba123 Not sure whether both are needed... I looked at those, but they didn't work. I'll test it again when the next version of gtk3 is released. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] sassc and gtk+3
Le 03/12/2019 à 21:52, Wayne Blaszczyk via blfs-dev a écrit : > On Tue, 2019-12-03 at 12:15 -0600, Bruce Dubbs wrote: >> On 12/3/19 1:49 AM, Wayne Blaszczyk wrote: >>> On Mon, 2019-12-02 at 21:44 -0600, Bruce Dubbs via blfs-dev wrote: I've been trying to update to the latest gtk+3, but have been getting massive failures during the regression tests. Upon investigation, most of the failures are due to a .css file generated by sassc. With some manual modification, the gtk+ tests are back to normal. This problem seems to occur with sassc-3.6, but not sassc-3.5. Upstream gtk maintainers and most other distros that we checked are still at sassc-3.5, although I can find references to both sassc-3.5.5 and sassc 3.6.1 on Arch. In BLFS, the packages that use sassc are gnome-shell, gnome-shell-extensions, plasma, and gtk+3. We currently have sassc-3.6.1 and libsass-3.6.3. The question is whether we should roll back sassc/libsass to version 3.5 or should just say that the test suite for gtk+3 is broken? Opinions? >>> Probably related, but I had issues with libsass-3.6.3. The Gnome >>> environment was >>> basically unusable. Things like gnome-terminal would not start most of the >>> time. >>> I had to revert back to libsass-3.6.1, before things became stable again. I >>> kept sassc at 3.6.1 . >>> This was all running under a VM. I don't run the gtk3 tests, so I cannot >>> comment on that. >>> Probably due to this issue: >>> https://github.com/sass/libsass/issues/303 > > Sorry, copy/paste issue, it should be > https://github.com/sass/libsass/issues/3033 > Looks like there are commits in the GTK+ repo: https://gitlab.gnome.org/GNOME/gtk/commit/619c892032cab24dadceb8ca9025486419fcde9c https://gitlab.gnome.org/GNOME/gtk/commit/87ea0253aaa2f750de32be7e0ab51f0a1f5ba123 Not sure whether both are needed... Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] sassc and gtk+3
On Tue, 2019-12-03 at 12:15 -0600, Bruce Dubbs wrote: > On 12/3/19 1:49 AM, Wayne Blaszczyk wrote: > > On Mon, 2019-12-02 at 21:44 -0600, Bruce Dubbs via blfs-dev wrote: > > > I've been trying to update to the latest gtk+3, but have been getting > > > massive failures during the regression tests. > > > > > > Upon investigation, most of the failures are due to a .css file > > > generated by sassc. With some manual modification, the gtk+ tests are > > > back to normal. > > > > > > This problem seems to occur with sassc-3.6, but not sassc-3.5. Upstream > > > gtk maintainers and most other distros that we checked are still at > > > sassc-3.5, although I can find references to both sassc-3.5.5 and sassc > > > 3.6.1 on Arch. > > > > > > In BLFS, the packages that use sassc are gnome-shell, > > > gnome-shell-extensions, plasma, and gtk+3. We currently have > > > sassc-3.6.1 and libsass-3.6.3. > > > > > > The question is whether we should roll back sassc/libsass to version 3.5 > > > or should just say that the test suite for gtk+3 is broken? > > > > > > Opinions? > > Probably related, but I had issues with libsass-3.6.3. The Gnome > > environment was > > basically unusable. Things like gnome-terminal would not start most of the > > time. > > I had to revert back to libsass-3.6.1, before things became stable again. I > > kept sassc at 3.6.1 . > > This was all running under a VM. I don't run the gtk3 tests, so I cannot > > comment on that. > > Probably due to this issue: > > https://github.com/sass/libsass/issues/303 Sorry, copy/paste issue, it should be https://github.com/sass/libsass/issues/3033 > > Hmm, That issue was closed in 2014. > > > I see there are some recent commits in relation to this issue which I > > haven't tried out yet. > > I did back off to libsass-3.6.1 and the gtk3 failures returned to > normal. I'll revert the book to that. Thanks for the feedback. > >-- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] sassc and gtk+3
On 12/3/19 1:49 AM, Wayne Blaszczyk wrote: On Mon, 2019-12-02 at 21:44 -0600, Bruce Dubbs via blfs-dev wrote: I've been trying to update to the latest gtk+3, but have been getting massive failures during the regression tests. Upon investigation, most of the failures are due to a .css file generated by sassc. With some manual modification, the gtk+ tests are back to normal. This problem seems to occur with sassc-3.6, but not sassc-3.5. Upstream gtk maintainers and most other distros that we checked are still at sassc-3.5, although I can find references to both sassc-3.5.5 and sassc 3.6.1 on Arch. In BLFS, the packages that use sassc are gnome-shell, gnome-shell-extensions, plasma, and gtk+3. We currently have sassc-3.6.1 and libsass-3.6.3. The question is whether we should roll back sassc/libsass to version 3.5 or should just say that the test suite for gtk+3 is broken? Opinions? Probably related, but I had issues with libsass-3.6.3. The Gnome environment was basically unusable. Things like gnome-terminal would not start most of the time. I had to revert back to libsass-3.6.1, before things became stable again. I kept sassc at 3.6.1 . This was all running under a VM. I don't run the gtk3 tests, so I cannot comment on that. Probably due to this issue: https://github.com/sass/libsass/issues/303 Hmm, That issue was closed in 2014. I see there are some recent commits in relation to this issue which I haven't tried out yet. I did back off to libsass-3.6.1 and the gtk3 failures returned to normal. I'll revert the book to that. Thanks for the feedback. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] More breakage from ICU-65.1 U16_NEXT requiring semilong
After happening upon the problem in libfreehand (for libreoffice)
where one line in the file had a U16_NEXT( ... )
without a terminating semicolon I've hit the same thing in the
chromium part of qtwebengine-5.13.2.
The initial error messages point to the _next_ line, in this case
./../../../../src/3rdparty/chromium/third_party/blink/renderer/core/dom/document.cc:5714:5:
error: expected ';' before 'if'
5714 | if (c == ':') {
| ^~
and line 5713 again uses U16_NEXT. Fortunately, this time we have
the source when we start to build. Normally I dislike seds which
address a line number by it's number, but in this case I think it's
appropriate:
sed -i '5713s/.*/&;/' \
src/3rdparty/chromium/third_party/blink/renderer/core/dom/document.cc
Will address it in a mo.
ĸen
--
Whilst all mushrooms are edible, the trick is to eat only those which
will prove to be edible more than once. The Celebrated Discworld Almanak
recommends you play safe and eat beans on toast.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-dev] sassc and gtk+3
On Mon, 2019-12-02 at 21:44 -0600, Bruce Dubbs via blfs-dev wrote: > I've been trying to update to the latest gtk+3, but have been getting > massive failures during the regression tests. > > Upon investigation, most of the failures are due to a .css file > generated by sassc. With some manual modification, the gtk+ tests are > back to normal. > > This problem seems to occur with sassc-3.6, but not sassc-3.5. Upstream > gtk maintainers and most other distros that we checked are still at > sassc-3.5, although I can find references to both sassc-3.5.5 and sassc > 3.6.1 on Arch. > > In BLFS, the packages that use sassc are gnome-shell, > gnome-shell-extensions, plasma, and gtk+3. We currently have > sassc-3.6.1 and libsass-3.6.3. > > The question is whether we should roll back sassc/libsass to version 3.5 > or should just say that the test suite for gtk+3 is broken? > > Opinions? > >-- Bruce Probably related, but I had issues with libsass-3.6.3. The Gnome environment was basically unusable. Things like gnome-terminal would not start most of the time. I had to revert back to libsass-3.6.1, before things became stable again. I kept sassc at 3.6.1 . This was all running under a VM. I don't run the gtk3 tests, so I cannot comment on that. Probably due to this issue: https://github.com/sass/libsass/issues/303 I see there are some recent commits in relation to this issue which I haven't tried out yet. Regards, Wayne. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
