Upstream advises against everyday use of 2.7 as it's a development branch. 2.7 ebuilds treated the same as the latest 2.6 ebuilds gives users a false sense of the stability of 2.7. Given the use cases for gnucash this seems irresponsible. Please mask 2.7 until upstream considers it stable for everyday use. Reproducible: Always
webkit-gtk:2 is unmaintained upstream for 2 years and I don't maintain it downstream anymore either. It has 400+ security vulnerabilities, which some argue aren't relevant to gnucash use case, but I wouldn't be so sure about that. Perhaps more importantly for gnucash, webkit-gtk:2 fails to build (e.g. bug 621532), or often hits such issues. At this point I have given up and don't try to fix it anymore, as it has hundreds of security issues anyways, and all upstream projects knew that gtk2 has been deprecated for 7 years and webkit-gtk old API isn't really supported since over 2 years (and knew before that, since introduction of the new API). Got to draw the line somewhere as webkit-gtk maintainer. I would say: Either we aim for 2.7 stable, or we remove all stable and ~arch versions of gnucash and only have a p.masked 2.7. Or no stable versions and 2.7 in ~arch. 2.6 ebuilds have to go away and I put a timer on Aaron for that as I agreed to give away the primary maintenance of the package. He seemed to find 2.7 rather stable and on the way to be released as stable 3.0 soon.
(In reply to Mart Raudsepp from comment #1) > I would say: Either we aim for 2.7 stable, or we remove all stable and ~arch > versions of gnucash and only have a p.masked 2.7. Or no stable versions and > 2.7 in ~arch. +1 This is really urgent as we want to stabilise icu-60.2 now.
2.7 is now in a feature freeze, has been stable for me over a month's use, and no bugs have been opened for 2.7.3 or 2.7.4 regarding any issues. While upstream may discourage it, we are moving ahead with marking it stable. Individuals who wish to remain on 2.6 may do so, though it may take more effort than just masking anything above 2.6 as it'll become more likely that the system becomes discoherent as the old webkit goes away and ICU moves forward as incompatible and greater versions of those are required by still more packages in the tree.
gnucash 2.6 ebuilds will be removed from main tree as well, after 2.7 stabilization has completed. Maybe at first p.masked together with webkit-gtk:2 for a short while, but I don't see a reason for that alternative path.
