# Michał Górny (2020-06-24)
# A thin wrapper to run pytest via setup.py that must not be used
# in Gentoo packages. Calling 'setup.py test' is deprecated upstream
# anyway. Just call 'pytest' directly. The last revdep is last rited.
# Removal in 30 days. Bug #729376.
dev-python/pytest-runner
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 t
# Ulrich Müller (2020-06-20)
# Separate package in dev-tex is unmaintained. Included with TeX Live.
# Use >=dev-texlive/texlive-latexextra-2020-r1 as replacement.
# Removal in 30 days. Bug #729394.
dev-tex/leaflet
signature.asc
Description: PGP signature
On Sat, Jun 20, 2020 at 1:36 PM Aaron Bauman wrote:
>
> On Sat, Jun 20, 2020 at 10:32:28AM +0200, Ulrich Mueller wrote:
> > > On Sat, 20 Jun 2020, Aaron Bauman wrote:
> >
> > >> # Aaron Bauman (2020-06-20)
> > >> # Py2 only
> > >> # Removal in 14 days
> >
> > I see these short deadlines quite
On Wed, 2020-06-24 at 11:52 +0200, Thomas Deutschmann wrote:
>
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. Someth
Using M="${S}" breaks in the pkg_setup phase where the S variable is
not valid. Previous commit messages don't give any rationale why some
phases would need the dir pointing to ${S}. Therefore, use ${T} in all
phases unconditionally.
Closes: https://bugs.gentoo.org/729178
Bug: https://bugs.gentoo.
# Ulrich Müller (2020-06-24)
# Included with TeX Live. The separate Gentoo packages are
# unmaintained and had their last version bump in 2010 or earlier.
# Use >=dev-texlive/texlive-latexextra-2020-r2 as replacement.
# Removal in 30 days. Bug #729394.
dev-tex/currvita
dev-tex/envlab
dev-tex/europ
On Sat, Jun 20, 2020 at 12:24 PM Aaron Bauman wrote:
>
> On Sat, Jun 20, 2020 at 01:29:46PM +0200, Thomas Deutschmann wrote:
> > On 2020-06-20 12:07, Michał Górny wrote:
> > >> Al least, python2 is not on your list.
> > >>
> > >> Be first into the future by masking this stuff and
> > >> Last out
On Wed, Jun 24, 2020 at 2:52 AM 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 o
On Wednesday, 24 June 2020 13:19:08 CEST Rich Freeman wrote:
> You seem to think that maintainers should know if they're maintaining
> a v2-only package. I suspect that most maintainers don't pay that
> close attention to what versions of python are supported by their
> various packages, and neithe
On Wed, 2020-06-24 at 19:48 +0200, Andreas Sturmlechner wrote:
> On Wednesday, 24 June 2020 13:19:08 CEST Rich Freeman wrote:
> > You seem to think that maintainers should know if they're maintaining
> > a v2-only package. I suspect that most maintainers don't pay that
> > close attention to what v
On Wednesday, 24 June 2020 20:03:57 CEST Michał Górny wrote:
> I think you're making the wrong assumption that Gentoo developers run
> bleeding edge systems. Instead, many of them prefer running stable
> and avoiding anything even remotely problematic.
That's not a contradiction for stable system
On Wed, Jun 24, 2020 at 2:18 PM Andreas Sturmlechner wrote:
>
> The lack of curiosity for one's own packages' python compatibility is not just
> a py27 isolated issue, it was a big problem with py36 -> py37 with so many
> devs simply not filing that necessary stabilisation.
That suggests that if
On Wed, Jun 24, 2020 at 11:29 AM Rich Freeman wrote:
> On Wed, Jun 24, 2020 at 2:18 PM Andreas Sturmlechner
> wrote:
> >
> > The lack of curiosity for one's own packages' python compatibility is
> not just
> > a py27 isolated issue, it was a big problem with py36 -> py37 with so
> many
> > devs
On Wed, Jun 24, 2020 at 2:40 PM Alec Warner wrote:
>
> On Wed, Jun 24, 2020 at 11:29 AM Rich Freeman wrote:
>>
>> Sure, you can use the portage API to find this info. However, that is
>> as easy to do for a list of all impacted packages in the tree with
>> their maintainers as for any individual
> On Wed, Jun 24, 2020 at 11:29 AM Rich Freeman wrote:
> > Sure, you can use the portage API to find this info. However, that is
> > as easy to do for a list of all impacted packages in the tree with
> > their maintainers as for any individual maintainer to obtain this info
> > for their own pack
# Ulrich Müller (2020-06-24)
# Included with TeX Live. The separate Gentoo package is
# unmaintained and had its last version bump in 2004.
# Use dev-texlive/texlive-bibtexextra as replacement.
# Removal in 30 days. Bug #729470.
dev-tex/harvard
# Ulrich Müller (2020-06-24)
# Included with TeX Li
On Wed, Jun 24, 2020 at 3:04 PM Andreas Sturmlechner wrote:
>
> > On Wed, Jun 24, 2020 at 11:29 AM Rich Freeman wrote:
> > > Sure, you can use the portage API to find this info. However, that is
> > > as easy to do for a list of all impacted packages in the tree with
> > > their maintainers as f
On Wed, 2020-06-24 at 16:03 -0400, Rich Freeman wrote:
> On Wed, Jun 24, 2020 at 3:04 PM Andreas Sturmlechner
> wrote:
> > > On Wed, Jun 24, 2020 at 11:29 AM Rich Freeman wrote:
> > > > Sure, you can use the portage API to find this info. However, that is
> > > > as easy to do for a list of all
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-announc
20 matches
Mail list logo