Bug 530050

Summary:	=app-portage/portpeek-2.1.16-r1 stabilization request
Product:	Gentoo Linux	Reporter:	Mike Pagano <mpagano>
Component:	[OLD] Keywording and Stabilization	Assignee:	Mike Pagano <mpagano>
Status:	RESOLVED INVALID
Severity:	normal	CC:	pacho, qa
Priority:	Normal	Keywords:	STABLEREQ
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:	530264
Bug Blocks:	530258

Description Mike Pagano gentoo-dev

2014-11-21 14:01:21 UTC

Arch teams, please stabilize portpeek-2.1.16

Comment 1 Agostino Sarubbo gentoo-dev

2014-11-26 10:45:18 UTC

amd64 stable

Comment 2 Mike Pagano gentoo-dev

2014-11-27 17:19:27 UTC

Sorry, Ago. Can you stable -r1, please?

Comment 3 Agostino Sarubbo gentoo-dev

2014-12-03 10:18:27 UTC

(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']

Comment 4 Pacho Ramos gentoo-dev

2014-12-05 13:32:00 UTC

why is this invalid now? :/ If it's because of the blocker you can unCC arches until they are CCed in bug 530264 ;)

Comment 5 Pacho Ramos gentoo-dev

2014-12-07 11:48:56 UTC

How do we remember about this blocking python-3.4 in default PYTHON_TARGETS then? :|

Comment 6 Pacho Ramos gentoo-dev

2014-12-07 11:50:39 UTC

Also, now there is a strange situation with 2.1.16 only being stable on amd64 :/

Comment 7 Pacho Ramos gentoo-dev

2014-12-07 11:58:22 UTC

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

Comment 8 Michał Górny archtester

2014-12-07 12:12:15 UTC

<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>

Comment 9 Michał Górny archtester

2014-12-07 12:19:35 UTC

Sorry, I meant: CC arch teams once they're CC-ed in the gentoolkit bug.

Comment 10 Pacho Ramos gentoo-dev

2014-12-07 15:48:52 UTC

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 ;)

Comment 11 Mike Pagano gentoo-dev

2014-12-08 01:34:30 UTC

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.

Comment 12 Pacho Ramos gentoo-dev

2014-12-08 12:12:24 UTC

OK, thanks for the explanation :)