On Wed, Jun 24, 2020 at 04:21:14PM -0400, Rich Freeman wrote:
> On Wed, Jun 24, 2020 at 4:08 PM Michał Górny <mgo...@gentoo.org> wrote:
> >
> > $ git grep -l mgo...@gentoo.org '**/metadata.xml' | cut -d/ -f1-2 |
> > xargs gpy-py2 2>/dev/null
> >
> I have no idea what gpy-py2 is, but I'll take your word for it.
> In any case, the solution in this case is to send a nice email to
> -dev-announce saying:
> We're removing python2 around <date>.  You can help us out by updating
> any packages you have that use python2.  If you want to easily
> identify these packages just do <insert quick script here>.
> I think the problem here is that we're basically telling maintainers
> that the beatings will continue until morale improves.  Then we're
> wondering why nothing is getting done.
> I'm not saying anybody has to do it a particular way - it just seems
> obvious that the way we're doing it is more successful at getting
> people upset than actually getting results.
> Ideally you would just open a tracker bug and then per-package bugs
> for every impacted package.  That would be the cleanest solution.  If
> that is too painful then by all means do some email announcements, but
> make it easy for devs to realize when they're missing something.
> Having a package mask be the first time a maintainer finds out that
> they have a problem isn't good.  Now, you can blame that on the
> maintainer, or you can blame that on the python team, but either way
> the users end up getting exposed to breakage unnecessarily.
> -- 
> Rich

I am thoroughly confused here. Some how you have completely changed your
opinion from previous posts. Furthermore, this has turned into a debate
of how to find packages that are Py2 only which is just absurd.

Of all the methods listed in the previous posts, the QA reports, etc.
there is no excuse individuals can't find out if their package is py2

Ironically, it would be a very sad state if an individual doesn't know
what Python interpreter their package is compatible with. This is the
essence of "maintainer" status, correct?

Can we stop finding excuses and let folks fix their packages?

Obviously, the myriad of tools, ML threads, and all the other "avenues"
individual developers have taken to alert others simply doesn't work...
until something is p.masked... people don't budge.


Attachment: signature.asc
Description: PGP signature

Reply via email to