Arch teams, please stabilize portpeek-2.1.16
amd64 stable
Sorry, Ago. Can you stable -r1, please?
(In reply to Mike Pagano from comment #2) > Sorry, Ago. Can you stable -r1, please? dependency.bad 11 app-portage/portpeek/portpeek-2.1.16-r1.ebuild: RDEPEND: amd64(default/linux/amd64/13.0) ['>=app-portage/gentoolkit-0.3.0.9-r2']
why is this invalid now? :/ If it's because of the blocker you can unCC arches until they are CCed in bug 530264 ;)
How do we remember about this blocking python-3.4 in default PYTHON_TARGETS then? :|
Also, now there is a strange situation with 2.1.16 only being stable on amd64 :/
Can we at least keep the bug opened for letting us to track that this needs to be stabilized before switching PYTHON_TARGETS to python3.4 as default? Thanks
<QAhat> Mike, please do not close the bug until you explain properly how to resolve the matters. Right now we have -r0 stable on one arch, with you wanting to stabilize -r1 instead, then closing the bug and completely refusing any other input. If gentoolkit is the only problem, then please CC arch teams normally and they will stabilize portpeek along with new gentoolkit which is also scheduled for stabilization. If there are other issues, please speak of them and we will look into a proper resolution. The current state of affairs is very undesirable from QA standpoint. </QAhat>
Sorry, I meant: CC arch teams once they're CC-ed in the gentoolkit bug.
Arches were CCed to bug 530264 then, if that was the blocker for this one, you can CC them here too when you think it's safe ;)
I will drop the stable keyword. I got an email about a possible issue with this and I want to see if I can reproduce. I'm going to once again try to close this.
OK, thanks for the explanation :)