Bug#850670: RFS: rpyc/3.3.0-1 [ITP]
Package: sponsorship-requests Severity: wishlist Control: block 850097 by -1 Dear mentors, I am looking for a sponsor for my package "rpyc" Package name: rpyc Version : 3.3.0-1 Upstream Author : Tomer Filiba URL : https://github.com/tomerfiliba/rpyc License : MIT Section : python I am packaging this as a dependency of flexget (ITP: #724718). It builds these binary packages: python3-rpyc - transparent and symmetric Remote Python Call library -- Python3 module python3-rpyc-doc - transparent and symmetric Remote Python Call library -- documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/rpyc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/r/rpyc/rpyc_3.3.0-1.dsc Cheers, Carl
PAPT membership request for moschlar-guest
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello everyone, I would also like to join the PAPT. I want to help with maintaining the nagstamon package under guidance of chr...@debian.org. My Alioth login is moschlar-guest. I have read the PAPT policy at http://python-apps.alioth.debian.org/policy.html and accept it. Thanks a lot in advance. Moritz On 14.12.2016 10:07, Moritz Schlarb wrote: > Hello everyone, > > I would like to join the DPMT. I want to help with maintaining the > nagstamon package under guidance of chr...@debian.org. > > My Alioth login is moschlar-guest. > > I have read the DPMT policy at > https://python-modules.alioth.debian.org/policy.html and accept > it. > > Thanks a lot in advance. Moritz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJYc6rYAAoJEAwkuEHH3bqvnLUP/ifKcAEWwZ0J8v63Kc0mMHS/ Vg3Ch6d4l+18vXAIFZM/fUzzHbSWaArwj8yCWquorBzvHTs/aR/yP0TfrqeLZS20 YHqLpepk9xE9VmflqOA90BJNQckZrFA1kQRoXpkDJoywjXJGz2jNHGJmTLzjaVNI zDHR1nGCWh1s+3VabCihMwHUbuK0PXLBltdYgTZMXFy31lrWok9TKEMLxvQxqnS6 omZrT+wQI/PORSmTI03+c/A9PX6fa+HmNAt9n9BWP8p5h2PmfUi3JWaNABy+NHLM MQi1sqWtPlna3BAMIVuSoALBVAlGkduk1FYAFpod3um+2ayHhGSxMufnMuyoM0tD oMM2kSN/YG3ZTwt684QVZbb347aat8fdS3HFdovV3Ktcd3Y1D3CzkVe8D3ebia7v ed1lT5jv1sN+jbMxSMgKix3l7oryB9B+n+mTJBbU5UsO/OyD/dozuHBRM8sN7tic dAFY0M0hs8i/O7TBQokH3gnGW6/caOu/OA6FajROvI/D1dDf/qKxHjbU5vnVS2AO RKKTN4vYYVApJTjmFXy7jzsi9LBo2Rlo45EzSVSN26Tkkzufh2MwU8BH0F6ffXXE xriTV2hbgVOYvR1IdIYkNDtvnkB5ybB3+kToafBQbmPxXxTe/PmTgeX/hbZHmFD/ rzrUm5GPPCDmF6OTSZxU =MFAA -END PGP SIGNATURE-
Re: DPMT membership request for randall-guest
On 03/01/17 23:21, Piotr Ożarowski wrote: > [Lee Garrett, 2016-12-23] >> I would like to join the DPMT. I plan on working on modules mainly used for >> Ansible (I'm currently updating pywinrm). I have read and accept the DPMT >> policy found at [1]. >> >> My Alioth account is 'randall-guest'. > > welcome :) > > (sorry for the delay) > Thanks a bunch! Pushing the pywinrm changes now.
#850098 subliminal: change of upstream structure
I see that subliminal is currently using the tarballs from PyPI and then patching in the source for the nautilus extension which is of course absent from there. Also the Github-hosted tarballs include a test suite which is not in the PyPI tarballs. It seems that the upstream nautilus extension has now moved to a different dedicated upstream repo: https://github.com/Diaoul/nautilus-subliminal Unfortunately this repository does not seem to have versioned releases, and has not seen an update in several months. My thinking is that if we continue to provide the nautilus extension at all, it should be built by a new source package src:subliminal-nautilus (which could potentially also build the nemo extension provided in a different branch of the upstream repo) tracking snapshots of the upstream git. I am happy to work on this as part of packaging the latest upstream release, but I just wanted to check before I do so that: 1) the source split I proposed is sensible (if so I'll probably just drop the nautilus extension for now and reopen https://bugs.debian.org/821455 until I repackage the extension in its new home), and 2) if the split is ok, which if either Python packaging team would make a good home for the nautilus extension, and 3) it's ok to change the tarballs to the Github ones and update the d/watch accordingly. The point of this would be to be able to run the test suite. Cheers, Carl