Bug 709446

Summary:	python-single-r1.eclass: dramatic change without a revision.
Product:	Gentoo Linux	Reporter:	Anton Bolshakov <anton.bugs>
Component:	Eclasses	Assignee:	Python Gentoo Team <python>
Status:	RESOLVED INVALID
Severity:	normal	CC:	council, mgorny, qa
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Anton Bolshakov 2020-02-13 01:52:13 UTC

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=494b83570ff7ee8c5796edc1f9ff578ea962459e

I question this commit and call this unacceptable.

There are hundreds or may be even thousands ebuilds which uses eclass with all developers working hard and making a big effort to make stable tested ebuilds.

all of a sudden, this commit was made which affectedly broke all this hard work.

Can you people learn that this -r revision for that purpose? I'm not even talking about an EAPI and proper planing.

I'm not even talking that the new syntax is confusing. Why should I care what all dependants use? Why should I spend more time figuring out SINGLE or MULITPLE use?

This is ridiculous!

Comment 1 Ulrich Müller gentoo-dev

2020-02-13 05:22:21 UTC

This change has been announced in gentoo-dev in November:
https://archives.gentoo.org/gentoo-dev/message/c381a2db549d2e3aa12fef6955b47ebe

Comment 2 Michał Górny archtester

2020-02-13 06:04:38 UTC

Bugzilla is not a chat platform, and this is not the attitude that helps people.  If you have a valid bug to report, please do so.  If you just want to offload your anger, please use a civilized methods of doing so.

Comment 3 Anton Bolshakov 2020-02-13 06:34:50 UTC

I filed a bug report because I want to have record, and I want to let you know that you broke all our python ebuilds. This is a "civilized" way to explain the problem. If I were you, I would revert that change and release it and "-r2".

By filling this bug, I really hope you will do it in the future.

It doesn't really matter if it was announced or not. The point is NOT to break a stable API, and give all maintainers Gentoo/overlays more time to upgrade it gradually.

This was done in the past, with python-r1 and git-r2. 

Why it was so difficult to do it this time?

Gentoo  council: for your follow up please.

Comment 4 Michał Górny archtester

2020-02-13 06:39:07 UTC

Revision wouldn't help you because PYTHON_USEDEPs won't work on migrated dependencies anymore.

Comment 5 Ulrich Müller gentoo-dev

2020-02-13 06:49:47 UTC

A good time to speak up would have been when the change was announced, not more than two months later when it was finally deployed.

"While it is any developer's choice not to participate on the gentoo-dev and gentoo-project mailing lists, they nevertheless serve as main communication channels. If something has been discussed there, and then action has been taken, the council regards ignorance of the discussion not as a good  foundation for protests against the actions." (2014-04-08 council meeting)