Hi,
We still have ~31 packages still not declaring support for newer Python 3
targets than Python 3.7,
we have ~1085 packages still not declaring support for newer Python 3 targets
than Python 3.8 (i.e.
Python 3.9).
Please review this list to see if your packages are stuck on Python 3.7:
# Sam James (2021-03-03)
# Declared abandoned upstream and stuck
# on Python 3.7.
# Removal in 30 days.
app-office/moneyguru
signature.asc
Description: Message signed with OpenPGP
> On 3 Mar 2021, at 22:55, Sam James wrote:
>
> Hi,
>
> We still have ~31 packages still not declaring support for newer Python 3
> targets than Python 3.7,
> we have ~1085 packages still not declaring support for newer Python 3 targets
> than Python 3.8 (i.e.
> Python 3.9).
Further to
> On 2 Mar 2021, at 15:05, Michał Górny wrote:
>
> Hi,
>
> I think I've made a mistake by stabilizing PyPy(3), and I would like to
> drop it back to ~arch (and stable-mask the relevant flags).
>
> Roughly, there are 4 problems with it:
>
> [snip]
> Honestly, I've tried to improve PyPy in
On Wed, 2021-03-03 at 23:00 +, Sam James wrote:
> > On 2 Mar 2021, at 15:05, Michał Górny wrote:
> >
> > Hi,
> >
> > I think I've made a mistake by stabilizing PyPy(3), and I would like
> > to
> > drop it back to ~arch (and stable-mask the relevant flags).
> >
> > Roughly, there are 4
> On Tue, 02 Mar 2021, Michael Orlitzky wrote:
>> Are you volunteering to fix all the tools to support the new format
>> correctly?
> The PMS says that KEYWORDS is whitespace-separated. Probably only
> repoman/pkgcheck would require trivial changes.
No, there are other tools as well, e.g.
> On 2 Mar 2021, at 03:54, Matt Turner wrote:
>
> tl;dr: In app-portage/gentoolkit-0.5.1 there's a new tool I wrote,
> called merge-driver-ekeyword that can automatically resolve git merge
> conflicts involving the KEYWORDS=... line in ebuilds.
>
Thanks a lot for your work here, Matt! It’s
On Wed, 2021-03-03 at 13:09 +0100, Ulrich Mueller wrote:
> > > > > > On Tue, 02 Mar 2021, Michael Orlitzky wrote:
> > > Are you volunteering to fix all the tools to support the new format
> > > correctly?
> > The PMS says that KEYWORDS is whitespace-separated. Probably only
> > repoman/pkgcheck
Hi,
This is a begging notice to ideally use NATTkA if possible for your keywording
or stabilisation bugs!
[If you don’t know what to do, I hereby give you permission to nag me and ask
me to check each one
of your bugs to let you know if it’s working okay and if it’s all gone alright.
New
Hi,
This is a friendly reminder that you should CC arch teams *for all arches which
currently have a stable keyword for your package*. NATTkA
handles this for you (see my other email [0]), but if you decide to not use it,
please be sure you do CC all arches for which the previous
stable version
10 matches
Mail list logo
