I'm using version 1.5.2 of sonata since the release (renamed ebuild) and now with the official portage ebuild. As it works absolutely flawless on my x86 based system, I request x86 keywords for this one. This of course extends to python-mpd-0.2.0 which sonata-1.5.2 depends on. Greets, Tobias
*** This bug has been marked as a duplicate of bug 226183 ***
How can this be set to RESOLVED? 1) bug 226183 is about sonata 1.5.1 2) bug 226183 is already set to resolved 3) sonata-1.5.2 still has ~x86 keywords (just checked out portage)
read the bug... *** This bug has been marked as a duplicate of bug 226183 ***
Is that your point? "uh, forget that, let's take 1.5.2 next month" Then I don't see why BOTH bugs are set to RESOLVED now. Stabilization for x86 has NOT happened yet because ~x86 keywords are still there, but both bugs are RESOLVED. This doesn't make any sense to me...
that bug is RESOLVED _LATER_, i.e. it will be reopened once said month passed - the comment is about 2 weeks old, that of course is also the reason why stabilization didn't happen yet
Still doesn't make sense to me. Prior to doing the STABLEREQ I searched the open bug list for sonata and didn't find anything about stabilization, so I opened this new bug. Now all bugs concerning STABLEREQ don't appear on the open bug list. IMO that's not how it should be. At least one bug should be marked open so people can find (with normal search) it here and add their comments (like me, who wanted to encourage adding stable keywords). Also: Why is stabilization based on time (one month delay)? It should be based on user feedback or tests the maintainer does. If time is so important every package becomes stable eventually, a behaviour I can't observe in the portage tree. Greets, Tobias
