as per $URL
What are the blocking issues for a 4.6.1 ebuild?
There aren't any.
(In reply to comment #2) > There aren't any. So, why is 4.6.1 not in portage yet?
Seriously? 4.4 has been waiting two months for a bump. You can wait.
(In reply to comment #4) > Seriously? 4.4 has been waiting two months for a bump. You can wait. I don't get it. You said there is nothing blocking it getting into portage. And then its not there in portage. These two contradict each other. Since you are telling me to wait, it means there is something blocking it. So, what is blocking 4.6.1? I genuinely want to know. 1. Is it that the ebuild needs to be re-written wrt 4.6? 2. Are there patches which don't apply anymore and need to be cleaned up? 3. Is it because there is no active maintainer of gcc on Gentoo? 4. Is it because there is active maintainer of gcc but he is too busy with something else? 5. Are there bugs in gcc 4.6.1 which needs to be fixed before Gentoo devs can consider releasing it even in testing? Some of these things can be handled. But we need to know what's going on to help fix it. I am curious because to me, it looks like a minor bump in version should be rather straight forward, as opposed to a major version bump.
2 & 4. I have several patchsets to push out, then version bumps for 4.4 and 4.5. I have to review a couple dozen bugs for each. Then I have 11000 gcc-related emails to sort through. Bumping a masked version isn't my first priority but I'll try and get to it soon.
*** Bug 373879 has been marked as a duplicate of this bug. ***
@Ryan Hill, excuse me for my bug below, I didnt see this one. In https://bugs.gentoo.org/show_bug.cgi?id=373879 I described what patches are obsolete: - gcc-4.6.0-ICE patches - the freebsd patch doesnt apply So, Freebsd might be a problem I dont know. On ~amd64 gcc-4.6.1 compiles a fully functional system for me.
*** Bug 373925 has been marked as a duplicate of this bug. ***
@Ryan Hill wrote: "Then I have 11000 gcc-related emails to sort through." 11 thousand emails. This is a bug on its own! Perhaps we could help Ryan by forming an assistant team, which tags the gcc-related emails? Some kind of assistance the bug triage teams at ubuntu do?
Not sure how you reading my mailing lists helps me. :P Anyways, bumped.