gtk+ 2.6.0 was released, with many new features and performance improvements. It's source and binary compatible with version 2.4. Reproducible: Always Steps to Reproduce: 1. 2. 3.
*** Bug 74686 has been marked as a duplicate of this bug. ***
*** Bug 74687 has been marked as a duplicate of this bug. ***
yeah we know about releases that took place a few hours ago just as well as you do. This is bugspam, go do something useful.
*** Bug 74761 has been marked as a duplicate of this bug. ***
*** Bug 75131 has been marked as a duplicate of this bug. ***
Question: why is it useful for all bugs on a package that's not in portage (not even hardmasked) or in breakmygentoo to be marked as resolved invalid or duplicate? If some foolhardy individual wants to download an ebuild, he has nowhere to go...
*** Bug 75293 has been marked as a duplicate of this bug. ***
*** Bug 75407 has been marked as a duplicate of this bug. ***
*** Bug 75691 has been marked as a duplicate of this bug. ***
*** Bug 76068 has been marked as a duplicate of this bug. ***
Ok I don't see any sense in making this sort of nonsense :::))), you are running bugzilla only to resolve the bugs in it with invalidation.... and therefore to create more bugs. it is very simple you resolve it with this flag, the shitty bug doesn't show in searches and therefore the next one files the same bug, you resolve it and so on. but this doesn't solve your problems. am i right :::))) it lasts already ages to bring every new gnome release ... ok it's your business i'm running it and you could wait some time :::))) best wishes
a few weeks for a new stable release is ages ? Get a grip on reality here, sure we can do more if we worked on it fulltime. the invalidation of this bug is because of the general nature of these reports : pointless reminders of a bump (of which the first was just hours after release) we obviously know about. Plus that all these reports lack any serious attempt at making a new ebuild (granted, the last one duped does not fit completely in this category). The main reason why this hasn't been done yet is that noone on our team has had the time to fix the one issue here, the adaptation of the patch you conveniently commented out, and noone else offered to do it.
The only patch from 2.4 series that seriously fails is smoothscroll (the others work fine - I don't know why Gergan commented them out). I tried adapting the smoothscroll patch, but some functions, e.g. gtk_range_scroll_event(), have changed enough since 2.4 that I was afraid of breaking things. If you look on http://bugzilla.gnome.org/show_bug.cgi?id=103811, the gnome devs are basically implying that the smoothscroll patch won't work with 2.6 unless a real gtk+ hacker works at it. Is smoothscroll valuable enough that it's holding up the ebuild? Also, gtk+-2.6 has some odd incompatibilities (e.g. with xfce 4.2 betas). It may be a good idea to have a hard-masked ebuild in portage so that people can test it out and find other potential problems soon, before the ~x86 unveiling of 2.6.
Well my idea was in fact, simply to try it whithout patches and see how stable is stable... and probably move gradually the patches in (i use xfce4.RC3 and I don't have problems in the last two days and I could say that in the contrary I see a speed up of the panel loading times). That's the idea of the masked and then the ~arch packages. Well I see that the things are better then I have expected. In fact there is a simply a little problem in the communication. Probably it's a good idea to point out where the problems are in specific ebuild and then there is a chance that someone with time could help in the process. That could make all happy and free some resources for the developers to make their moves. It could be for example a special site for the most wanted ebuilds or sth like that. That could free the bugzilla from the spam and consequently could help the overall QA-process.
*** Bug 76312 has been marked as a duplicate of this bug. ***
Created attachment 47491 [details] x11-libs/gtk+-2.6.0 I don't know if this is the right bug to post it, but since I modifed the bmg ebuild of gtk+-2.5.6 and have gtk+-2.6.0 running after using this ebuild, I think it is a good idea to share it. The smoothscroll patch has been commented out by bmg and was not added back (for obvious reasons :D )
what is the obvious reason i wonder, their inability to fix it ?
The obvious reason is: I'm not a GTK hacker and have no idea how to get that patch working ( see Comment #13 )
*** Bug 76611 has been marked as a duplicate of this bug. ***
Why not leave this bug open? at least it serves as a way to notify users in CC of the progress. I don't think there is other mecanism to do that (I could be wrong).
It was mainly invalidized when assigned to gnome because it was filed less than 48hrs or so after the release and had nothing significant to add. As such we consider it bugspam really, we do get pack update notifications ourselves as well and these 'bugs' are just annoying. Up until the third last bug or so nothing was added in the form of patches or useful updates. I already indicated what needed to be done as far as 'roadmap' goes, nothing has come from the bugfilers in that sense so to me there is no reason to open up this bug : there is nothing to track. Please do understand that we are just people like you and yes we are anxious to get new stuff in as well, but we don't have all the time of the world either. It would be a delight if someone actually acted to our indications and came up with something, but that seldom happens and as such we have a backlog of things to get to and so sometimes updates to packages that work fine currently is not our primary priority and getting several mails a day of people who did not search in the first place about something we are obviously well aware of is not very helpful.
I understand all that, I am not trying to be annoying, nor will I push it any further. I know you know about the release, and you will work on it whenever you have the time. All I am saying is it would be nice if we (users) are notified by email when the ebuild is committed, and this seems to be only medium to do that. The package database would not notify users by email and checking it every day is a waste of time. I am sorry if I bothered you. Good luck with the bug.
gtk+ 2.6.1 is in portage. We can breathe more easily :D
