Re: Debian package transition: Rename package and reuse old name with new content

2018-08-23 Thread Alexis Murzeau
Hi,

Thanks for your replies.

On 19/08/2018 12:18, Simon McVittie wrote:
> According to apt-file(1), python3-pycryptodome contains
> /usr/lib/python3/dist-packages/Cryptodome, which you use via "import
> Cryptodome". If you're renaming packages anyway, would it be better for
> the package containing /usr/lib/python3/dist-packages/Cryptodome to be
> the python3-cryptodome package?
>
> (My reasoning is that the name you import is the name of the "ABI",
> the same way the ABI of, for example, libdbus is represented by its
> SONAME libdbus-1.so.3, which we translate into libdbus-1-3 as a Debian
> package name.)

The naming pycryptodome and pycryptodomex are the ones used by upstream
on PyPi. So the goal is to have the same names as upstream uses for
these too different packages. pycryptodome on PyPi use
`dist-packages/Crypto` which is meant to be a drop-in replacement for
python-crypto.


> It's OK for packages in unstable to be uninstallable or unbuildable for
> a short time, as long as Depends/Breaks/Conflicts or RC bugs ensure that
> the brokenness doesn't propagate into testing.
>
> For instance, if you are going ahead with your renaming plan, you could
> give the new packages a versioned Breaks on python3-httpsig (<< H) and
> python3-pysnmp4 (<< S), where H is the first version of python3-httpsig
> that has been modified to use/expect the new (py)cryptodome(x) package
> layout, and S is the corresponding version of python3-pysnmp4.
>
> smcv
>

On 20/08/2018 16:11, Gianfranco Costamagna wrote:
> 
> 
>> I'm not sure of the transition policies when handling transitions on
>> testing and unstable only (ie: not involving stable).
>> But that should ensure there is no breakage between package in the archive.
> 
> 
> if you are just renaming a package,, and the reverse-deps are not too many,
> better avoid transitional packages, ask for a transition slot on release.d.o,
> open bugs (MBF?) with patches, and raise to serious once RT acks the 
> transition.
> 
> G.
> 

Ok thanks, I will consider the transition slot and adding breaks to the
new pycryptodome packages over the old reverse-dependencies.
Actually, pycryptodome is under the ongoing transition of python 3.7 so
any package changes will wait the end of that one.

-- 
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F



signature.asc
Description: OpenPGP digital signature


Re: ITP: wikitrans -- MediaWiki markup translator

2018-08-23 Thread أحمد المحم
Please create the 'wikitrans' repository in python-team/modules on 
salsa.
Thanks

On Thu, Aug 23, 2018 at 07:12:41PM +0200, أحمد المحم wrote:
> Package: wnpp
> Severity: wishlist
> Owner: "أحمد المحمودي (Ahmed El-Mahmoudy)" 
> 
> * Package name: wikitrans
>   Version : 1.0
>   Upstream Author : Sergey Poznyakoff 
> * URL : https://puszcza.gnu.org.ua/projects/wikitrans
> * License : GPL-3+
>   Programming Lang: Python
>   Description : MediaWiki markup translator
> 
>  This package provides Python framework for translating WikiMedia articles to 
>  various formats. The present version supports conversions to plain text, 
> HTML, 
>  and Texinfo formats.
>  
>  
>  - This package is needed by new versions of dico
> 
>  - I intend to maintain the package under Python modules team
> 
> -- 
> ‎أحمد المحمودي (Ahmed El-Mahmoudy)
>  Digital design engineer
> GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
> GPG Fingerprints:
>  6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
>  8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


---end quoted text---

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature


Request to join DPMT and PAPT

2018-08-23 Thread Nick Morrott
Hi,

I would like to join the Python Modules (DPMT) and Python Applications
(PAPT) teams, initially in order to package the mu editor [1] and help
out with packaging future dependencies.

  [1] https://bugs.debian.org/901461

I have read, and accept, the Python Modules policy [2]. I have been
unable to find the Python Applications policy document [3] (linked
from the PAPT wiki page [4]) on salsa since the alioth transition.

  [2] 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
  [3] http://python-apps.alioth.debian.org/policy.html
  [4] https://wiki.debian.org/Teams/PythonAppsPackagingTeam

My salsa login is nickm-guest.

I have been a member of the Debian Perl team since November 2015 [6].

  [6] https://qa.debian.org/developer.php?login=knowledgejunkie%40gmail.com

Thanks,
Nick