We need this stable for gnome 3.22 and gtk+-3.22, they went to stable but this not, hence, we need arches CCed here soon as, otherwise, people can get ugly blockers when trying to update Thanks
haha, thanks for fixing it so quickly!
(In reply to Pacho Ramos from comment #1) > haha, thanks for fixing it so quickly! oops, wrong browser tab ;)
At least on my setup, the themes I have tried look to behave properly under MATE. It would be nice to CC arches as, currently, people having full Gnome and MATE desktops installed with be unable to update due to trying to pull gtk+-3.22 and 3.20 at the same time
I thought this was made to work with any gtk version as discussed long ago via version specific CSS paths... Anyhow, removing blocker on stabling, as the arches are done there already that have mate-themes keywords and so this blocker is making gnome 3.22 stabilization on alpha/hppa/ia64/sparc not proceed there until arches aren't CCed here, while they don't even have mate-themes keywords.
1.14.x MATE is my daily-driver desktop environment. I've been testing for several months, and kept an eye out for any changes in dependencies or other QA issues. A few days ago when gtk+ was stabilized, I made the appropriate change in /etc/portage/package.keywords for unmasking a sensible version of x11-themes/mate-themes such that my blockers would go away: > gtk+-3.22.11 > mate-themes-3.22.7 This system has been working normally ever since without issue. I'll fire up the relevant change for amd64 stabilization of mate-themes-3.22.7 within the gentoo-mate overlay so it can get signed off and eventually find its way to the portage tree proper. Thanks.
OK, anyway, I would CC arches tomorrow here if we have no reply as we cannot keep stable amd64/x86 tree in this state :/
[18:38:47] <leio> NP-Hardass: ping? [18:39:10] <leio> mudler: or you [18:56:25] <NP-Hardass> Leio, if this is wrt mate-themes I am planning on self stabilizing x86 and amd64 and was waiting to hear from mudler re: arm [19:14:29] <leio> NP-Hardass: can you just do the former two already though? [19:14:40] <leio> NP-Hardass: really no reason to have to do in one push
(In reply to Pacho Ramos from comment #0) > We need this stable for gnome 3.22 and gtk+-3.22, they went to stable but > this not, hence, we need arches CCed here soon as, otherwise, people can get > ugly blockers when trying to update > > Thanks Done. (In reply to Mart Raudsepp from comment #4) > I thought this was made to work with any gtk version as discussed long ago > via version specific CSS paths... Correct. Upstream said they didn't want to do it, leaving it to me. At the time, they were working so feverishly on updating the themes that it was infeasible for me to merge 6 branches properly, so we still have the same situation. And @gnome team, in the future, please try to be a little more patient. It's pretty frustrating when you expect changes immediately. Sometimes things take a day or two. And if you don't want to be held up, please try notifying us with more warning. That said, we should have stabilized these two packages long before now.... Just hadn't gotten around to it, so apologies for that.
> (In reply to Mart Raudsepp from comment #4) > > I thought this was made to work with any gtk version as discussed long ago > > via version specific CSS paths... > > Correct. Upstream said they didn't want to do it, leaving it to me. At the > time, they were working so feverishly on updating the themes that it was > infeasible for me to merge 6 branches properly, so we still have the same > situation. Not sure about what those 6 branches are, but I suppose it's all fine now, as 3.22 is LTS and no more really expected there. > And @gnome team, in the future, please try to be a little more patient. > It's pretty frustrating when you expect changes immediately. Sometimes > things take a day or two. And if you don't want to be held up, please try > notifying us with more warning. That said, we should have stabilized these > two packages long before now.... Just hadn't gotten around to it, so > apologies for that. It didn't even come to my mind that these would get broken based on earlier discussions; should have paid more attention to theme breakages, I though we had all that settled with 3.20 declaring theme API stable. But yeah, I just poked in IRC a bit as gtk3.22 had been stable for a couple days now, just as a poke, not really a big hurry or anything, just your users were suffering on my oversight that pacho filing this bug pointed out, so wanted to get that remedied asap.
(In reply to Mart Raudsepp from comment #9) > > (In reply to Mart Raudsepp from comment #4) > > > I thought this was made to work with any gtk version as discussed long ago > > > via version specific CSS paths... > > > > Correct. Upstream said they didn't want to do it, leaving it to me. At the > > time, they were working so feverishly on updating the themes that it was > > infeasible for me to merge 6 branches properly, so we still have the same > > situation. > > Not sure about what those 6 branches are, but I suppose it's all fine now, > as 3.22 is LTS and no more really expected there. MATE upstream supports >=3.14, and previously said that they wouldn't accept any solution that doesn't include all supported GTK branches.
