Re: Bug#936604: FYI: Python 3 migration of distributuion

2020-12-11 Thread Osamu Aoki
Hi,

It's a fork with a new upstream with some issues.  (Not supported by
the old upstream)

Anyway, I switched out from getmail to other MUA.

No one seems to take over this package maintenance.

So please remove this package.  I am not going to package the new
getmail6.

Regards,

Osamu


On Wed, 2020-10-21 at 22:41 +0200, Moritz Mühlenhoff wrote:
> On Tue, Nov 19, 2019 at 10:43:49PM +0900, Osamu Aoki wrote:
> > On Sun, Nov 17, 2019 at 02:28:44PM +0900, Osamu Aoki wrote:
> > > Hi,
> > > 
> > > On Wed, Nov 13, 2019 at 11:11:43AM -0600, Charles Cazabon wrote:
> > > > Osamu Aoki  wrote:
> > > > > 
> > > > > Currently, getmail is a candidate for removal from the
> > > > > upcoming Debian
> > > > > release if it is not updated to support python 3 by someone
> > > > > (not
> > > > > necessary by upstream).
> > > > 
> > > > Thanks for the update, Osamu.  I have actually been playing
> > > > with a prototype
> > > > refactoring of getmail to not just support but require a recent
> > > > Python 3.x
> > > > version.  Such a project would give me the opportunity to
> > > > remove a lot of
> > > > historical cruft and backwards-compatibility code that getmail
> > > > has accumulated
> > > > over 20+ years.
> > > 
> > > That's great.  (I thought you rejected idea to move to 3.0.)
> > > 
> > > I tried to do it around getmail 5.5 days.  (I didn't finish it)
> > 
> > 
> > FYI: I found this repo
> > https://gitlab.com/dkg/getmail/commits/python3
> > I think this is better work than my local work.
> 
> Hi Osamu,
> given that a Py3-compatible version is now available as src:getmail6,
> let's go ahead and remove getmail?
> 
> Cheers,
>     Moritz    



Re: Joining the team request for salsa user microjoe-guest

2020-12-11 Thread Romain Porte
Hi,

2020-12-02 12:50 CET, Romain Porte:
> In order to publish some Python packages that will act as dependencies
> to packages for font management, I would like to join the fonts team.
>
> [...]
>
> I have read the current python-team policy [1] and agree with its terms.
> [1] 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Gentle reminder to provide me access to python-debian on salsa
for new repository creation.

I have currently 3 packages waiting on mentors.d.n to have the
following repositories created to reserve their names before upload:

 * python-absl
 * python-strictyaml
 * python-vttlib

If access cannot be provided on salsa, I will have to create the
Vcs repositories in my own salsa namespace and remove debian-python@
from the maintainers list of these packages. I would like to avoid this
situation.

> My salsa login is "microjoe-guest".

My login has now be moved to "microjoe", as "-guest" suffix are not
mandatory anymore for non-DD/DM.

Best regards,

Romain.


signature.asc
Description: PGP signature


Re: Joining the team request for salsa user microjoe-guest

2020-12-11 Thread Stefano Rivera
Hi Romain (2020.12.02_11:50:22_+)
> In order to publish some Python packages that will act as dependencies
> to packages for font management, I would like to join the fonts team.

And the python team, presumably :)

> My salsa login is "microjoe-guest".

Guessing you meant "microjoe".

Added, welcome.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Python 2 support for Bullseye

2020-12-11 Thread Stefano Rivera
Hi Moritz (2020.10.16_18:33:06_+)
> > not ok. That would mean removing pypy3 from the archive as well. If you 
> > don't
> > want to support Python2, then why do you care about it's removal for 
> > bullseye+1?
> 
> Ok. I assumed the need for Py2 in pypy3 was a temporary thing? If it's needed
> for longer (is there an estimate of sorts?), I'm also fine with keeping
> it longer.

Sorry, rather late to this thread.

PyPy upstream is looking at converting the rpython toolchain to python3,
but I wouldn't expect progress any time to. So, I'll continue to need
some form of python2.7 (python2.7 or pypy) to build pypy3 for the
foreseeable future.

pypy (2.7) uses python2.7 to build itself on architectures where that's
faster than using pypy (architectures where pypy has no JIT).

But pypy could be entirely self-hosted and then python2.7 could be
dropped from the archive. Downside: manual bootstrapping of pypy would
be required on new archs & after certain build failures. I assume this
will have to happen at some point.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Newcomers project: DPMT/PAPT pristine-tar verification

2020-12-11 Thread Stefano Rivera
Hi Thomas (2020.10.09_11:12:21_+)
> For those:
> 
>python-etcd3 (U)
>python-requests-mock (U)
>python-sphinxcontrib.apidoc (U)
> 
> they in fact live in the OpenStack team namespace, but I don't have
> enough rights to delete the Git repositories. Can someone do it for me
> please?

Deleted.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



sponsor uploading python-discogs-client_2.3.5-1

2020-12-11 Thread jojo

Hi,
I updated a team-maintained package and am looking for an upload 
sponsor. This one: 
https://salsa.debian.org/python-team/packages/python3-discogs-client/-/tree/debian/2.3.5-1. 
I already uploaded the package to my webserver: 
https://jojo.peek-a-boo.at/E950513F/python-discogs-client_2.3.5-1.dsc


I tried to find a sponsor on the irc channel #debian-python already. I 
posted it in the channel and have been told to better just add it to the 
topic of that channel. I didn't do that because I am an irc noob and use 
the irc bridge on matrix.org to access irc rooms and didn't find a way 
to do it yet. Just so you know.


thanks in advance!

Jojo