Re: [gentoo-dev] */*: Mask Py2 only packages

2020-06-25 Thread Matt Turner
On Thu, Jun 25, 2020 at 8:14 PM Aaron Bauman  wrote:
>
> On Wed, Jun 24, 2020 at 10:12:18AM -0700, Matt Turner wrote:
> > offlineimap is widely used and blocks no further work. It can easily
> > remain in the tree after all other python2_7 support is gone.
> >
> > This is not a hill worth dying on.
> >
>
> I am confused here... are you saying that due to usage of the package
> that it should stay until dev-lang/python:2 is gone?
>
> More importantly, I simply responded to Thomas' mention that the package
> has alternatives, but apparently, I don't understand how the package is
> used :)

Two reasons: because it's widely used *and* because its python:2.7
dependency is on only the interpreter itself.

The second reason means that its removal doesn't enable any further clean ups.



Re: [gentoo-dev] */*: Mask Py2 only packages

2020-06-25 Thread Aaron Bauman
On Wed, Jun 24, 2020 at 11:52:28AM +0200, Thomas Deutschmann wrote:
> On 2020-06-20 21:24, Aaron Bauman wrote:
> > Thomas, unfortunately, I am shocked at your choice of words here. I
> > think it is reasonable that any developer would understand a lack
> > of forward momentum in removing Py2 only packages only drives
> > stagnation.
> > 
> > If you have a more effective method to doing so, I am open to
> > suggestions.
> 
> Like I am shocked about your recent actions:
> 
> Remember what you did in January. I thought it became clear that next
> time you will share your list before just masking stuff to avoid things
> which happened then.
>

Developers have many tools and *hopefully* the organic ability to determine
which packages are impacted. Especially given previous threads on this
very ML with pleas from other Python team members to assist in cleaning
things up in a deliberate manner.

This is why the QA team interceded... because a couple of individuals
screamed loudly for no reason. Fix it and move on.

> In the beginning of this month you just decided to disband graphics
> project. On your own. Please tell me what gave you the authority to just
> do that? You didn't even share your plan before executing it on any
> mailing list. Something that should be common sense, if not even necessary.
> The whole action was so destructive that you couldn't evenb just undo it
> because you also deleted stuff on Wiki.
> 

I will not apologize for doing something that others have lacked the
intestinal fortitude to do.

> Like multiple people have already shown you, many packages from that
> list are not even blocking Py3 transition.
>

This isn't about transitioning to Py3... it is about removing Py2.

> Let me tell you what a mask will cause:
> A mask is destructive and requires user interaction. Therefore a mask
> isn't something to play with, "Oh, let's test if someone will
> complain... it's just a mask, we can just unmask in case...".
> 

Is that why you assume I masked these things?

> No, imagine there are people out there using Gentoo in production and
> not as playground. These people maybe have automated build systems which
> are creating systems/images (do you know Dockers for example?). Whenever
> you mask something and that package is referenced in configuration, you
> will break that build.
> 
> That's not funny if this is happening for no real reason.
> 

I know you use Gentoo in production, but does this mean we (Gentoo)
can't move forward because *you* want to use something that is EOL and
dying? What if you used a major distro that removed Py2 support already?
Why complain here? There are other ways to safely run your tooling with
Py2 if you so choose.

> 
> > re: net-mail/offlineimap... there are alternatives.
> 
> I think you don't really know that tool. It's an industry standard.
> Sure, there are already successors (however, not in Gentoo). But the
> package itself is still working and actively maintained and when you
> will use it in production you usually have extended/adjusted the tool
> for your environment using the plugin system the tool provides. That's
> not something you will be able to replace with something new in 5 minutes.
> 

You continuously speak condescendingly to me. I am truly starting to
regret my nomination for you on both the security project and for
council. Do you speak to others this way simply because you don't agree
with them?

Yes, I use net-mail/offlineimap... I know how it works. No, I really
hope that a tool which has not been maintained in many years is an
"industry standard" 

Yes, there are successors in Gentoo.

> And I repeat myself: Especially not when there is no need to do that
> because because the package itself is working fine and there is absolute
> no reason to get rid of it.
> 

Take Patrick's approach and move it to an overlay if you want it that
badly.

> Last but not least: Gentoo is about choices. It's not your job to decide
> what people should use. Sure, if you maintained a package and will stop
> using it so it will become maintainer-needed and masked for removal at
> some point because it's outdated, vulnerable and/or not working anymore,
> that's OK. But if someone else will pick up this package... and
> offlineimap in Gentoo is working and up-to-date.
>

Are you implying that because "Gentoo is about choice" that we never
remove an ebuild, interpreter, compiler, etc? Let ::gentoo grow in size
forever to appease the few?

-- 
Cheers,
Aaron


signature.asc
Description: PGP signature


Re: [gentoo-dev] */*: Mask Py2 only packages

2020-06-25 Thread Aaron Bauman
On Wed, Jun 24, 2020 at 10:12:18AM -0700, Matt Turner wrote:
> offlineimap is widely used and blocks no further work. It can easily
> remain in the tree after all other python2_7 support is gone.
> 
> This is not a hill worth dying on.
> 

I am confused here... are you saying that due to usage of the package
that it should stay until dev-lang/python:2 is gone?

More importantly, I simply responded to Thomas' mention that the package
has alternatives, but apparently, I don't understand how the package is
used :)

-- 
Cheers,
Aaron


signature.asc
Description: PGP signature


Re: [gentoo-dev] */*: Mask Py2 only packages

2020-06-25 Thread Aaron Bauman
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  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 .  You can help us out by updating
> any packages you have that use python2.  If you want to easily
> identify these packages just do .
> 
> 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
only.

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.

-- 
Cheers,
Aaron


signature.asc
Description: PGP signature


Re: [gentoo-dev] dev-python/rstcheck-3.3.1: Add rstcheck python package (#16399)

2020-06-25 Thread Brian Dolbec
On Thu, 25 Jun 2020 23:23:29 +0100
Samuel Bernardo  wrote:

> Hi Brian
> 
> On 6/25/20 11:18 PM, Brian Dolbec wrote:
> > You add yourself as primary maintainer.  The proxy maintainers will
> > add themselves for the merge to the repo after all review is done.
> > This will mean that you will need to maintain the pkg, do the
> > version bumps, etc..  The proxy team will help merge the changes to
> > the ebuild tree.  
> 
> That means that I can submit the ebuild metadata without maintainer?
> 
> Thanks
> 
> 

yes, you do not need to add a Gentoo maintainer unless asked to.



Re: [gentoo-dev] dev-python/rstcheck-3.3.1: Add rstcheck python package (#16399)

2020-06-25 Thread Samuel Bernardo
Hi Brian

On 6/25/20 11:18 PM, Brian Dolbec wrote:
> You add yourself as primary maintainer.  The proxy maintainers will add
> themselves for the merge to the repo after all review is done.  This
> will mean that you will need to maintain the pkg, do the version bumps,
> etc..  The proxy team will help merge the changes to the ebuild tree.

That means that I can submit the ebuild metadata without maintainer?

Thanks




signature.asc
Description: OpenPGP digital signature


Re: [gentoo-dev] dev-python/rstcheck-3.3.1: Add rstcheck python package (#16399)

2020-06-25 Thread Brian Dolbec
On Thu, 25 Jun 2020 23:11:29 +0100
Samuel Bernardo  wrote:

> Hi,
> 
> I send this email to ask for your help on selecting the project
> maintainer for a new ebuild.
> 
> I created a pull request for the ebuild in subject[1] and the QA
> reports complaints about missing project maintainer[2]. What should I
> do?
> 
> Thanks
> 
> [1] https://github.com/gentoo/gentoo/pull/16399
> 
> [2]
> https://qa-reports.gentoo.org/output/gentoo-ci/2e4d12bbfa/output.html#dev-python/rstcheck
> 
> 

You add yourself as primary maintainer.  The proxy maintainers will add
themselves for the merge to the repo after all review is done.  This
will mean that you will need to maintain the pkg, do the version bumps,
etc..  The proxy team will help merge the changes to the ebuild tree.



[gentoo-dev] dev-python/rstcheck-3.3.1: Add rstcheck python package (#16399)

2020-06-25 Thread Samuel Bernardo
Hi,

I send this email to ask for your help on selecting the project
maintainer for a new ebuild.

I created a pull request for the ebuild in subject[1] and the QA reports
complaints about missing project maintainer[2]. What should I do?

Thanks

[1] https://github.com/gentoo/gentoo/pull/16399

[2]
https://qa-reports.gentoo.org/output/gentoo-ci/2e4d12bbfa/output.html#dev-python/rstcheck




signature.asc
Description: OpenPGP digital signature


Re: [gentoo-dev] */*: Mask Py2 only packages

2020-06-25 Thread Rich Freeman
On Thu, Jun 25, 2020 at 2:45 PM John Helmert III  wrote:
>
> On Thu, Jun 25, 2020 at 07:32:04AM -0400, Michael Orlitzky wrote:
> > On 2020-06-24 16:08, Michał Górny wrote:
> > >
> > > $ git grep -l mgo...@gentoo.org '**/metadata.xml' | cut -d/ -f1-2 |
> > > xargs gpy-py2 2>/dev/null
> > find -L "${REPO}" \
> maint=$(pquery ${pkg} --one-attr maintainers | tail -1)

Great, so now we have 4 ways (and counting) to get 4 answers to this
question that hopefully will be mostly the same.

My point is more that it makes more sense for one person to just file
the bugs or send out the list so that maintainers can go fix their
packages, as opposed to playing a game where every developer in Gentoo
independently engineers a solution to the same problem.  If some
maintainers decide not to play the game, or play it and make a
mistake, then it ends up being the python team or the users who lose.

If a maintainer ignores a blocker bug for too long nobody is going to
shed a tear over some treecleaning.  Spending a bit more time on
communication might save a lot more time in cleanup.

-- 
Rich



Re: [gentoo-dev] */*: Mask Py2 only packages

2020-06-25 Thread John Helmert III
On Thu, Jun 25, 2020 at 07:32:04AM -0400, Michael Orlitzky wrote:
> On 2020-06-24 16:08, Michał Górny wrote:
> > 
> > $ git grep -l mgo...@gentoo.org '**/metadata.xml' | cut -d/ -f1-2 |
> > xargs gpy-py2 2>/dev/null
> > 
> 
> The big problem with this is that it misses any aliases (like graphics@)
> that you're a member of. But let's golf; this is POSIX sh, doesn't use
> grep to parse XML, and takes the maintainer's email address as an argument:
> 
> REPO=/var/db/repos/gentoo
> XPATH="/pkgmetadata/maintainer/email[normalize-space(text()) = '${1}']"
> 
> find -L "${REPO}" \
>   -mindepth 3 \
>   -maxdepth 3 \
>   -name 'metadata.xml' \
>   -exec sh -c "
> for f in \"\${@}\"; do
>   xmllint --xpath \"${XPATH}\" \"\${f}\" >/dev/null 2>&1 && \
> echo \"\$(dirname -- \"\${f}\")\" | sed \"s:${REPO%/}/::\"
> done
>   " - {} +
> 

We can instead avoid parsing XML at all if we're not averse to using
`pquery`, and we can avoid the limitation of scanning the entire tree
for a single name/email by outputting the maintainers for all of the
problematic packages at once (in this case, packages output by
`gpy-py2`) in a greppable format. Not sure why pquery doesn't see
maintainers for things like automake:1.9, so this implementation is
imperfect, but here:

REPO=/var/db/repos/gentoo

for pkg in $(gpy-py2 -r "${REPO}"); do
maint=$(pquery ${pkg} --one-attr maintainers | tail -1)
if [[ ${maint} ]]; then
echo "${pkg}: ${maint}"
else
echo "${pkg}: maintainer-needed"
fi
done


signature.asc
Description: PGP signature


[gentoo-dev] Last-rites: media-sound/rgain

2020-06-25 Thread Andreas Sturmlechner
# Andreas Sturmlechner  (2020-06-25)
# Stuck on Python 2, no maintainer; rgain3 fork available for sb. taking over
# at https://github.com/chaudum/rgain - masked for removal in 30 days.
media-sound/rgain


signature.asc
Description: This is a digitally signed message part.


[gentoo-dev] Last-rites: x11-misc/nts

2020-06-25 Thread Andreas Sturmlechner
# Andreas Sturmlechner  (2020-06-25)
# Stuck on Python 2, m-n, we have no shortage on note taking applications.
# Masked for removal in 30 days.
x11-misc/nts

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-dev] */*: Mask Py2 only packages

2020-06-25 Thread Michael Orlitzky
On 2020-06-24 16:08, Michał Górny wrote:
> 
> $ git grep -l mgo...@gentoo.org '**/metadata.xml' | cut -d/ -f1-2 |
> xargs gpy-py2 2>/dev/null
> 

The big problem with this is that it misses any aliases (like graphics@)
that you're a member of. But let's golf; this is POSIX sh, doesn't use
grep to parse XML, and takes the maintainer's email address as an argument:

REPO=/var/db/repos/gentoo
XPATH="/pkgmetadata/maintainer/email[normalize-space(text()) = '${1}']"

find -L "${REPO}" \
  -mindepth 3 \
  -maxdepth 3 \
  -name 'metadata.xml' \
  -exec sh -c "
for f in \"\${@}\"; do
  xmllint --xpath \"${XPATH}\" \"\${f}\" >/dev/null 2>&1 && \
echo \"\$(dirname -- \"\${f}\")\" | sed \"s:${REPO%/}/::\"
done
  " - {} +



[gentoo-dev] Last rites: dev-tex/cdcover, dev-tex/translator

2020-06-25 Thread Ulrich Mueller
# Ulrich Müller  (2020-06-25)
# Included with TeX Live. Last version bump in 2003.
# Use dev-texlive/texlive-latexextra as replacement.
# Removal in 30 days. Bug #729470.
dev-tex/cdcover

# Ulrich Müller  (2020-06-25)
# Included with TeX Live. Last version bump in 2008.
# Use dev-texlive/texlive-latexrecommended as replacement.
# Removal in 30 days. Bug #729470.
dev-tex/translator


signature.asc
Description: PGP signature