Otherwise, the test phase fails with linking errors looking for PNG-related symbols. I could reproduce it on both alpha and amd64.
pretty sure it's not a regression, so it's not a stable blocker
(In reply to SpanKY from comment #1) > pretty sure it's not a regression, so it's not a stable blocker Not aimed at you specifically, but in my experience, that statement means that the maintainer will never look at the failure because it's not happening on amd64/x86 or any of the maintainer's pet archs. And it wastes AT time every time we run into it. If this is not going to be fixed (which is a valid choice!), let's just mask USE=test for alpha for this package and move on.
(In reply to Tobias Klausmann from comment #2) it is not appropriate to hold hostage a stabilization request for a non-regression, especially a security based one. the status quo is not being made worse. this is standard Gentoo practice, and you haven't made an argument for changing it, nor would it be done here. such a topic is fodder for gentoo-dev (not that i see much chance of your position succeeding). in this case, there's already an upstream report on the topic, and trying to fix it only in Gentoo doesn't make much sense. architectures are irrelevant here as it happens on all of them.
(In reply to SpanKY from comment #3) > (In reply to Tobias Klausmann from comment #2) > > it is not appropriate to hold hostage a stabilization request for a > non-regression, especially a security based one. the status quo is not > being made worse. this is standard Gentoo practice, and you haven't made an > argument for changing it, nor would it be done here. such a topic is fodder > for gentoo-dev (not that i see much chance of your position succeeding). I am not holding anything hostage, I just have a day job and haven't gotten to another pass of stabilization. I haven't re-added the blocker, either. So that accusation is uncalled for. In this particular case, I am hopeful that upstream will fix the matter, but I suspect you can see how perpetually-broken test suites are frustrating for ATs. Especially since *I* get yelled at for ignoring them when something breaks. I will stabilize gd2 sometime during the weekend, probably, since I am currently traveling and don't have access to my signing keys.
(In reply to Tobias Klausmann from comment #4) chill out. i wasn't accusing you of anything. you were talking in generalizations, so i responded in generalizations. you originally added it as a blocker, and then you said it was a good idea.
i've fixed this upstream now. prob will just try to get a new 2.2.5 out instead since the testsuite updates weren't exactly trivial. *** This bug has been marked as a duplicate of bug 608724 ***
