Re: morph's abandoned packages (list)
Hello Alexandre, On 3/16/24 18:37, Alexandre Detiste wrote: CCing Daniele who uploads bespoken flask-login and Carsten who manage whole flaks ecosystem. Sorry for the late reply, just for public archive I was also +1 to remove flask-basicauth. Thanks! Ciao, Daniele
Re: Updating khal to fix RC bug #1023341
Hello Jonas, On 16/12/2022 20:53, Jonas Smedegaard wrote: Seems I only_after_ last release corrected the watch file to fetch from true source at Github. If I guessed wrong and it was something else, then please just ask. You guessed, now I see, many thanks! Cheers, -- Daniele Tricoli https://mornie.org OpenPGP_0x8BAF522C0D6CCEDD.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Updating khal to fix RC bug #1023341
Hello Jonas, On 16/12/2022 18:51, Jonas Smedegaard wrote: As you might have noticed by now, I took the liberty of releasing my changes when I understood what was going on - because by then I had a functioning package ready for upload. Thanks you did the right thing, thanks for taking care of khal, unfortunately I was able to look at this list only now and your last email just arrived to my MUA after I sent my previous one. It was multiple layers of cause for confusion: First layer: Upstream uses setuptools-scm to resolve release version, which is bad because it makes assumptions about things outside of the project - specifically it interacts with VCS (meta)data and assumed that is not replaced by that of another distro by the time the project is built. So our packaging patches away the use of setuptools-scm. > Second layer: Our replacement involved grep'ing for upstream release version from file PKG-INFO which, as you correctly point out, is missing from upstream tarball. It was however included in previous upstream tarball, so this is an upstream change. So our replacement needed to be adjusted (to now instead grep CHANGELOG). > Third layer: Debian build routines call clean target regardless if patches are applied or unapplied. Our patch affects dh_auto_clean so our replacement is extended with checking if patch is applied and skipping dh_auto_clean when it isn't. This makes it appear as if our "clean" target succeeds easily leading to the wrong assumption (at least for me) that it must be something upstream that fails - something mysteriously looking for a missing PKG-INFO file... Hope that was understandable. Many thanks, it is know: I was lost between second and third layer! I have now updated our replacement routines plus a range of other householding changes, and released the new packaging release. Thanks for this! Thanks a lot for bringing it to my attention. In fact I had old work lying around locally from July 30th that had stalled at that exact same failure, so I myself was evidently baffled as well (and then got distracted by something else), despite my having introduced the patch myself. We are a team. ;) ...so I have now also sprinkled a few comments in debian/rules file, to aid future baffld Debian maintainers. countless Cheers, -- Daniele Tricoli https://mornie.org OpenPGP_0x8BAF522C0D6CCEDD.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Updating khal to fix RC bug #1023341
Hello Jonas, On 16/12/2022 15:10, Jonas Smedegaard wrote: [CUT] I will have a closer look now, then get back to you. Oh, many thanks! :) Ususally when I "look" at a package I routinely update it as well. I like this approach, it keep all the stuff clean. Would you prefer that I roll back whatever changes I do during my "looking at it" and guide you to gain same understanding as me? Because if your interest is simply to get khal updated then simpler for me is do (hopefully) all myself and only tell you without leaving room for you to redo and potentially learn more from that DIY experience. I am happy to do that slower process - I find it fun to collaborate (am just not very used to it), so please do tell if you are eager to learn. :-) I would love to learn, but please don't roll back your changes, time is our most precious resource. :) I made a copy of my local clone and I dropped all the new commits you made, so I will be able to use the DIY approach. :) I must confess that I peeked at the new commits while I was searching the commit I had to halt the dropping, so I already know that repacking is not needed anymore, but for me the mystery about the release 0.10.4 remains and I'm eager to learn about it... if you have the time to explain. :) Many thanks in advance, -- Daniele Tricoli https://mornie.org OpenPGP_0x8BAF522C0D6CCEDD.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Updating khal to fix RC bug #1023341
Hello, I tried to update khal to block the autoremoval from testing (due #1023341) but it's not clear to me how to import metadata used to parse the package version with uscan¹ during repack of the tarball. PKG-INFO and the egg.info directory are on salsa¹ upstream branch but I'm not able to see them in the upstream tarballs (I looked also the commit on salsa with hash ba53a6bfb845ab4df3d5298f91f323b070084f4b): also PKG-INFO in the root of the repository is a news to me. How can I put them in the repacked tarball? In d/watch is indicated that for update the classic uscan invocation (through gbp) is used. The only way I can think of is to manually repack (AFAIK uscan doesn't support adding files before the invocation of mk-origtargz)... but it not seems that this was the procedure used according documentation on d/watch. AFAIU this mechanism was introduced to fix #1002406.³ Jonas do you have the time to explain? Many thanks, ¹ I know that it's easy to generate them with python3 setup.py egg_info ² https://salsa.debian.org/python-team/packages/khal ³ I don't know if it's worth to extend python3-setuptools-scm to support version schema we use in Debian, it seems not to hard, we could abuse of https://github.com/pypa/setuptools_scm#adding-a-new-scm P.S. Jonas I don't know if you are subscribed to this list, so I'm adding you to CC. -- Daniele Tricoli https://mornie.org OpenPGP_0x8BAF522C0D6CCEDD.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: python-requests: adding a documentation package python-requests-doc
Hello Mattia, On Tue, Dec 31, 2019 at 09:15:12PM +0100, Mattia Rizzolo wrote: > I recommend you enable notifications for all packages in you are interested > in, by setting the notification switch on salsa to "watch". Many thanks for the hint, I was not aware of this! > Otherwise, you could get into the habit of scrolling through your ddpo page > every so often anche check the VCS column (but there is a huge delay as > iirc salsa is queried once a week for MRs). Yes, I usually look at them there, but as you said there is a huge delay. I will follow your suggestion about switching notification to "watch". Thanks again, -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: PGP signature
Re: python-requests: adding a documentation package python-requests-doc
Hello Fabrice, On Thu, Jan 02, 2020 at 08:46:51AM +0100, Fabrice BAUZAC-STEHLY wrote: > I have updated the merge request. Merged, many thanks for your contribution! Regards, -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: PGP signature
Re: python-requests: adding a documentation package python-requests-doc
Hello Fabrice, thanks for pinging I did not notice the MR :( Please next time can you assign it to me? I should reveive some sort of notification I hope! :) On Tue, Dec 31, 2019 at 12:35:19AM +0100, Fabrice BAUZAC-STEHLY wrote: > Hello, > > I wish there was a python-requests-doc package for browsing > python-requests' documentation offline. I'd like to add it if I can. > > I saw that debian/watch currently targets the PyPI tarball, which lacks > the documentation. Yes, I usually preferred PyPI distribution, but I'm fine switching since it will enhance users experience. > As a first step, I'm submitting a merge request [1] so that debian/watch > tracks the github releases instead, which do contain the documentation. > > After that, once a new upstream release of requests is published and > propagated into the salsa repository, the latter will start > containing the missing docs/ subdirectory. So we'll at least be able to > start working on a new python-requests-doc binary package containing the > documentation. > > In the merge request, I've basically applied the github recipe as > indicated in the uscan(1) manpage. > > If you could have a look at this merge request, that would be excellent. > > [1] https://salsa.debian.org/python-team/modules/requests/merge_requests/1 > Looked at it, I would prefer the more common: -8< version=4 opts=filenamemangle=s/.+\/v?(\d\S+)\.tar\.gz/requests-$1\.tar\.gz/ \ https://github.com/psf/requests/tags .*/v?(\d\S+)\.tar\.gz -8< Please can you update your MR? Can you also update d/changelog, so I will not to have to write manually that I thank you and the attribution of the work you have done? :) Thanks for your contribution! Regards and happy new year, -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: PGP signature
Re: python-urllib3 1.25.6 uploaded to experimental (closes CVE-2019-11236) but fails build tests
On Sun, Oct 13, 2019 at 10:31:31PM +0800, Drew Parsons wrote:
> It conditionally works. Using curl, I found that TLSv1_0 or TLSv1_1 will
> support a successful connection, but only if the maximum SSL_VERSION is
> constrained to TLSv1_0 or TLSv1_1 (e.g. curl -v --tlsv1.1 --tls-max 1.1
> https://pub.orcid.org). Without the max, the connection fails:
> $ curl --tlsv1.1 https://pub.orcid.org
> curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake
> failure
>
> The urllib3 failure was similar, but I do not know how to set tls-max with
> urllib3. I could only find the option with curl. I could set up a custom
> HTTPAdapter as suggested at
> https://requests.readthedocs.io/en/master/user/advanced/#example-specific-ssl-version
> to set ssl_version=ssl.PROTOCOL_TLSv1_1 but the ssl module doesn't have the
> SSLVERSION_MAX_TLSv1_1 value that curl has. I could solve it with pycurl
> using c.setopt(pycurl.SSLVERSION, pycurl.SSLVERSION_TLSv1_1 |
> pycurl.SSLVERSION_MAX_TLSv1_1)
For sure I'm missing something, but why not just set TLS version?
I tried the following on both Python2 and Python3:
>>> import ssl
>>> from urllib3.poolmanager import PoolManager
>>> http = PoolManager(ssl_version=ssl.PROTOCOL_TLSv1)
>>> r = http.request('GET', 'https://pub.orcid.org')
>>> r.status
200
> Evidently the orcid server only supports TLSv1.0 and TLSv1.1 and no higher
> (why haven't they activated TLSv1.3 yet?!), while curl and urllib3 without
> tls-max first test TLSv1.3 and then quit without cascading downwards once
> they receive the TLSv1.3 handshake failure. Which is rather odd behaviour
> when I think about it. The whole point of supporting multiple protocol
> versions is to try the next available version if the first one doesn't work.
Not an expert here, but I think fallback is not done on purpose due downgrade
attacks: https://en.wikipedia.org/wiki/Downgrade_attack
> I had a closer look. The failing tests were in python2 only, coming from
> the non-ascii (Gërman http://Königsgäßchen.de/straße and Japanese
> http://ヒ:キ@ヒ.abc.ニ/ヒ?キ#ワ) unicode url tests. So from one perspective
> we don't need to worry so much about them, we could just disable them (e.g.
> prepend @onlyPy3 to test_parse_url and test_url_vulnerabilities in
> test_util.py). We'll be dropping python2 any way in the near future.
>
> On the other hand, given the nature of the vulnerabilities and the possible
> uses of urllib3, it's probably best not to leave python2 untested,
> especially since they are known to pass on python2 anyway in the right
> conditions. Probably there is some package that should be added to
> Build-Depends to enable python2 tests to pass, though I have no idea which
> that package might be.
Fixed adding python{,3}-idna on B-D. I had to add python3-idna
because the same tests were failing also on Python3 when I tested
them buinding on DoM.
Kind regards,
--
Daniele Tricoli 'eriol'
https://mornie.org
signature.asc
Description: PGP signature
Re: python-urllib3 1.25.6 uploaded to experimental (closes CVE-2019-11236) but fails build tests
Hi Drew, On 12/10/2019 07:57, Drew Parsons wrote: > Hi Daniele, just letting you know I uploaded python-urllib3 1.25.6 to > experimental. Thanks for taking care of urllib3. > I was having some SSL trouble connecting to https://pub.orcid.org. The error > trace cited urllib3/contrib/pyopenssl.py, so I downloaded and installed > python-urllib3 1.25.6 to see if updates to default SSL/TLS versions made any > difference. It didn't fix my problem, but since I had the package update > ready > I figured I might as well present it to experimental. I hope to have the time to investigate also this: urllib3/contrib/pyopenssl.py contains code to have SSL with SNI_-support for Python 2 and it depends on pyOpenSSL, cryptography and idna. Maybe looking at them can give us more clues. Also, could you see if using Python3 the connection to https://pub.orcid.org work? > The new version fixes CVE-2019-11236 (Bug#927172). As far as I can tell it > also fixes CVE-2019-11324 (Bug#927412), but I figured it's best to let you > review that. > > Th package build was successful on my system but gives build-time errors in > chroot (on buildd). I'm not sure why that's failing. I will look at them during this weekend, I already had a look at build log from the phone, but it's better to look from a PC. Regards, -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: OpenPGP digital signature
Re: Use debhelper-compat instead of debian/compat
Hello Ondřej, On 18/07/2019 21:15, Ondrej Novy wrote: > > I would like to mass-commit this change to DPMT/PAPT, example: > > https://salsa.debian.org/python-team/modules/python-geoip2/commit/bc5ce34dd9bbfe3ecb7951aead267dbdaba3376a > > Any thoughts? Thanks, please go ahead! Regards, -- Daniele Tricoli 'eriol' https://mornie.org
Re: Mass commit: Rename d/tests/control.autodep8 to d/tests/control
Hello Ondrej, On 07/01/2019 21:42, Ondrej Novy wrote: > Any thoughts? +1 Thanks for taking care of this! Regards, -- Daniele Tricoli 'eriol' https://mornie.org
Please add my DD account to DPMT
Hello, I'm already a member of DPMT (in the salsa group with my eriol-guest account), but now I have a DD account (eriol) and I would like to start using it. I already accepted the policy when I joined, and I've just re-read it on https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst I agree to follow the team policy. I know that we use gbp and gbp-pq and that the policy is under update. Many thanks! Regards, -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: OpenPGP digital signature
Re: Salsa Vcs-* mass-commits
On Monday, February 12, 2018 6:19:10 PM CET Scott Kitterman wrote: > Looks good to me. Also for me, thanks! Cheers, -- Daniele Tricoli 'eriol' https://mornie.org
Re: [IMPORTANT] DPMT migrated to Salsa
On Friday, February 9, 2018 1:46:34 PM CET Ondrej Novy wrote: > Hi, > > good news everyone. I migrated DPMT to Salsa. Many thanks! \o/ > What is missing: > >- change PAPT policy and change "Joining the team" section to same >wording as DPMT policy >- move all documentation, policy, pages from alioth (to Salsa pages?) >- move mailing lists from alioth >- fix wiki >- prepare script for setting up/fixing repos (i did it by ad-hoc scripts >now) ideally with CI/CD + GitLab Scheduler (runs every week?). Something >like this: > > https://salsa.debian.org/jcowgill/multimedia-cli/blob/master/multimedia-cli > .py - PAPT -> Salsa migration (svn->git) >- fix mr >- mass-commit change of d/control: Vcs-* >- ... did I forgot something? > > Any thoughts? :) If I can help in some way, please tell me. Cheers, -- Daniele Tricoli 'eriol' https://mornie.org
Re: BTS bot in #debian-python IRC channel
On Sunday, August 14, 2016 10:19:12 PM CEST Ondrej Novy wrote: > +1 for moving VCS commits too. +1 also from me! :) -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: [Python-modules-team] Bug#830186: sphinx: intersphinx mapping extension causes network access during package builds
Hello Dmitry, On Monday, July 11, 2016 09:06:57 PM Dmitry Shachnev wrote: > If it's invoked separately the only ways would be to export http(s)_proxy in > debian/rules or patch conf.py to get correct intersphinx mapping. Thanks for the details. I'm already exporting http_proxy inside betamax debian/rules, maybe patch conf.py is needed anyway due DNS queries: it seems confirmed looking at tcpdump log for #830543. Thanks! Cheers, -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: [Python-modules-team] Bug#830186: sphinx: intersphinx mapping extension causes network access during package builds
Hello Brian, On Sunday, July 10, 2016 11:34:53 AM Brian May wrote: > ... in which case building the documentation happens outside > dh_auto_build. > > Did I miss something here? I have the same issue with betamax, and IIUC #830186 we have to patch intersphinx to use the distro provided inventory files. See this reply of Dmitry Shachnev (at the end he point to few examples): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830186#10 Cheers, -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Intention to upload 21 packages to jessie-backports
Hello Thomas, On Tuesday, May 31, 2016 03:44:56 PM Thomas Goirand wrote: > Changed-By: Daniele Tricoli <er...@mornie.org> > Source: betamax It's OK for me. Just a note: betamax 0.7.0-1 is ready, I sent already an RFS to Piotr, but it will go to NEW queue because I built also documentation package. I'll be happy to backport when it will land on testing if it's useful for you. Cheers, -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: dh-python piuparts problem?
Hello Barry, On Tuesday, February 09, 2016 05:10:12 PM Barry Warsaw wrote: > I've seen this failure on a number of packages now, but I haven't > had time to dig into it in detail. I'm not sure if it's a problem in the > individual packages, or a bug in dh-python. I should file a bug. Has > anybody else seen this? > > 4m39.2s ERROR: FAIL: Package purging left files on system: > /usr/share/dh-python/dhpython/__pycache__/ not owned > /usr/share/dh-python/dhpython/build/__pycache__/ not owned I saw this moths ago, but it was fixed by Piotr: https://lists.debian.org/debian-python/2015/07/msg00035.html On debomatic (it runs piuparts at the end of the build) I did not see this issue recently. -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: dh-python piuparts problem?
On Tuesday, February 09, 2016 11:30:53 PM Daniele Tricoli wrote: > On debomatic (it runs piuparts at the end of the build) I did not see this > issue recently. Just rebuilded chardet, and I can confirm the issue: http://debomatic-amd64.debian.net/distribution#unstable/chardet/2.3.0-2/piuparts Regards, -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: [Python-modules-team] My Pip installation is broken after upgrading Debian from oldstable/Wheezy to stable/Jessie...
Hello, sorry for the delay in my reply! On Saturday, January 02, 2016 10:32:50 AM Brian May wrote: > Are you sure? This bug was supposedly fixed in the Jessie version... 03_export-IncompleteRead.patch is still present in the requests packaging (since pip version in Debian still need it) and was shipped with requests 2.4.3-2. @Ant Dude: just to recap and to be sure I understand correctly: you should have installed requests 2.4.3-6 and python-pip (1.5.6-5), right? Renaming requests (Debian packaged version) install directory make pip work, right? Debian packaged version of pip doesn't use convenience copies, so do you have a version of requests installed not using apt? Please can you tell me what is the output of the following? python -c "import requests; print requests.__version__" Please, can you also try: python -c "from requests.compat import IncompleteRead" Thanks! -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Joining the team
On Thursday, December 31, 2015 08:31:31 AM Ian Cordasco wrote: > I would like to join the team to help package and maintain > python-betamax (ITP > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808880) with Daniele > Tricoli. I very glad Ian applied to join the DPMT! I'm happy to have him as a co-maintainer of Betamax, and since he is also upstream of both requests and urllib3, if he want to help me maintaining both, I will feel honoured! :) -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Updating python-requests and python-urllib3
Hello Christopher, On Tuesday, December 22, 2015 03:49:05 PM Christopher Baines wrote: > I have had a go at updating python-requests to the latest upstream > release (from 2.8.1 to 2.9.1). This bundles the latest version of > python-urllib3 (1.13.1) so I have updated that also (from 1.12 to 1.13.1). I'm going to work later on them or at max tomorrow, thanks for your work. For #796717, however, there is no need to use requests: I did change the test a bit to use urllib3 directly but I forgot to send to the bug report. > Its also probably prudent to have the > python-requests package depend on the latest version of python-urllib3 > (which I have not changed). Yes, I follow upstream development closely, and you are right the Depends will be updated. Thanks, -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Pushing a bunch of packages to jessie-backports
Hello Thomas, On Monday, November 23, 2015 09:20:40 AM Thomas Goirand wrote: > If you maintain one of the above packages and want to manage the bpo > upload yourself, please let me know ASAP. Thanks for backporting python-urllib3 and requests. If you did not have to make changes on the packaging to please go ahead, otherwise a debdiff will be very appreciated! :) Please also consider that currently python-etcd is broken by the unbundling logic and we are working on it with upstream: https://github.com/kennethreitz/requests/issues/2870 My plan was to backport requests when we was sure that unbundling logic was completely fine, but python-etcd is not in Jessie so we should not have problems right now. Anyway I will backport requests again when upstream issue 2870 will be fixed. Kind regards, -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Git migration schedule pushback permissions/DEP-3 workflow
On Monday, October 12, 2015 08:13:41 PM Daniel Stender wrote: > I've got a push back error here: > > $ git push > Counting objects: 22, done. > Delta compression using up to 4 threads. > Compressing objects: 100% (21/21), done. > Writing objects: 100% (22/22), 2.72 KiB | 0 bytes/s, done. > Total 22 (delta 12), reused 0 (delta 0) > remote: error: insufficient permission for adding an object to repository > database ./objects remote: fatal: failed to write object > error: unpack failed: unpack-objects abnormal exit > To > ssh://danstender-gu...@git.debian.org/git/python-modules/packages/citeproc- > py.git ! [remote rejected] master -> master (unpacker error) > error: failed to push some refs to > 'ssh://danstender-gu...@git.debian.org/git/python-modules/packages/citeproc > -py.git' I have experienced same problems, but only related to pushing tags (I mean, pushing works except for tags). For example pywavelets: ❯ git push --tags Counting objects: 1, done. Writing objects: 100% (1/1), 176 bytes | 0 bytes/s, done. Total 1 (delta 0), reused 0 (delta 0) remote: error: insufficient permission for adding an object to repository database ./objects remote: fatal: failed to write object error: unpack failed: unpack-objects abnormal exit To git+ssh://git.debian.org/git/python-modules/packages/pywavelets ! [remote rejected] upstream/0.3.0 -> upstream/0.3.0 (unpacker error) error: failed to push some refs to 'git+ssh://git.debian.org/git/python- modules/packages/pywavelets' The same is happening with python-urllib3. Cheers! -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Git migration schedule
Hello Stefano, many thanks for working on this! On Saturday 03 October 2015 20:52:21 Stefano Rivera wrote: [CUT list of packages] > Cannot "git-dpm init" package: python-charade charade was fortunately merged into chardet so we can also remove the SVN repository (or ignore it). Cheers, -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: requests 2.7.0 in Debian experimental
[CC httpie maintainer] Hello Ian, many thanks for your explanation, it saved me a lot of time. On Tuesday 05 May 2015 10:08:13 Ian Cordasco wrote: To make it easier for everyone else, if you want to grep through the packages you maintain for any of the symbols removed here: https://github.com/kennethreitz/requests/commit/f37fe551bbbf6ac8d07c35c64888 b4ab289c967d it should be sufficient. I started testing manually requests dependants, but after reading this I used codesearch.debian.net: https://codesearch.debian.net/results/requests.compat/ I tested packages using requests.compat and they are all fine except for httpie (a recap for Bartosz: with requests = 2.5.2 we need httpie = 0.9.2). pip 1.5.6-5 is doing a “from requests.compat import IncompleteRead” but it's not a problem: I reintroduced IncompleteRead because it was the easiest way to not break pip (see #766419); I will remove this patch when pip will be updated. Since it seems we have only one package maybe I can just add Breaks: httpie ( 0.9.2) to python-requests stanza. Of course I will fill also a bug to httpie (priority wishlist) asking for an updated version and explaining what is going on. Is this considered to rude? Should I have to ask a transition slot instead? Kind regards, -- Daniele Tricoli 'Eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: requests 2.7.0 in Debian experimental
On Monday 18 May 2015 12:51:44 Daniele Tricoli wrote: Is this considered to rude? Should I have to ask a transition slot instead? Of course waiting for Bartosz's ack before proceeding. I will wait a week before pinging again the bug (already sent, I don't have bug number yet). Cheers, -- Daniele Tricoli 'Eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
requests 2.7.0 in Debian experimental
Hello, I have uploaded version 2.7.0 of requests in experimental because it breaks backwards compatibility. I already found that httpie needs to be update to 0.9.2[¹], but I'll start checking all requests dependants in the following days. If your package has requests as dependency, and you want help me (:D), please test it with the new version and make sure all it's fine. My plan is to systematically check dependants before ask from the release team a transition slot for requests (this should be the proper way to handle this issue IIUC). Kind regards, [¹] https://github.com/jakubroztocil/httpie/blob/master/CHANGELOG.rst#092-2015-02-24 -- Daniele Tricoli 'Eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Attempting to remove python-support?
On Sunday 26 April 2015 21:09:16 Vincent Bernat wrote: I am also in favor of removing python-support. It doesn't have any obvious bugs but having several helpers is confusing. pybuild + dh should be used for most packages. +1 I have some packages[¹] that I want to migrate. I had some problem due to #577140: first time I used one of the patch in the comments but I did not remember witch. Unfortunately it seems also git-buildpackage doesn't play well with multiple upstream tarballs: #561071. This time I will patch svn-buildpackage or git-buildpackage and I will migrate them. Cheers, [¹] python-peak.rules, python-peak.util, decoratortools (the last one is not a multiple orig tarball, so it's easy). -- Daniele Tricoli 'Eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Python 2 d-d-a proposal
On Wednesday 15 April 2015 20:54:38 Barry Warsaw wrote: I'm up for helping too, of course. Me too! Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Building Python without SSLv3 breaks requests
Hello Yannick, thanks for this report! On Wednesday 19 November 2014 00:45:19 Yannick Roehlly wrote: and maybe other packages or software (for instance, a local install of Vim's YouCompleteMe embedding it's own Python requests does not work). Should bugs be reported against the broken packages or should the SSLv3 disabling in Python 2 be done with corrections? This breakage is related to urllib3, specifically the SNI support for Python 2. It is showing without using urllib3.contrib.pyonpenssl due to the monkey patch machinery to make requests.package.urllib3 == urllib3. I can patch http://sources.debian.net/src/python-urllib3/1.9.1-2/urllib3/contrib/pyopenssl.py/#L72 to not raise any AttributeError if SSLv3 support is disabled. Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1429442.KxPtxmVTCJ@mornie
Re: About requests.packages.urllib3 in Debian
Hello Tianon, many thanks for this report. On Wednesday 12 November 2014 23:43:58 Tianon Gravi wrote: Any ideas? Do we need to include some kind of further patch in python-docker, or was the patch to requests possibly not complete? After appying the patch I did run requests' testsuite and I tried python- docker, so I thought it was all ok, but I was wrong... :( I'm working on this and I think I have already the proper fix. Sorry for this! :( -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/4853503.E3FVKxfnoS@mornie
Re: About requests.packages.urllib3 in Debian
First of all my apologies for the wasted time...
specially for the Release Team that was so fast on
unblocking requests 2.4.3-3.
On Wednesday 12 November 2014 23:43:58 Tianon Gravi wrote:
Any ideas? Do we need to include some kind of further patch in
python-docker, or was the patch to requests possibly not complete?
I fixed this in requests 2.4.3-4 (RFS already sent to Piotr).
The only changes needed are here:
http://anonscm.debian.org/viewvc/python-modules/packages/requests/trunk/debian/patches/04_make-requests.packages.urllib3-same-as-urllib3.patch?view=markuppathrev=31441
The package build fine twice in a row in a pbuilder chroot.
This time, beyond, running requests' tests I also used these:
--[test_requests.py]--
from __future__ import print_function
import requests
import requests.packages.urllib3
import urllib3
assert requests.packages.urllib3 is urllib3
assert requests.packages.urllib3 == urllib3
from requests.packages.urllib3.util import get_host
from urllib3.util import get_host as get_host_u3
assert get_host is get_host_u3
from requests.packages.urllib3.util.timeout import Timeout as T1
from urllib3.util.timeout import Timeout as T2
assert T1 is T2
--
--[test_docker.py]
from __future__ import print_function
import os
import docker
c = docker.Client(base_url=os.getenv('DOCKER_HOST'))
print(c.version())
--
I ran them both on Python 2 and Python 3.
Also, I noticed that linking urllib3 inside requests.packages
is not needed anymore, but I did not removed *.links due to
the freeze, to keep changes as small as possible.
Of course, I will wait before asking for an unblock. I want to
try
Kind regards,
P.S. Unfortunately I will be off-line during the weekend, so
feel free to work on requests if it's needed. I'll be back on
monday.
--
Daniele Tricoli 'Eriol'
http://mornie.org
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/10591096.Pl2TxDKuMZ@mornie
Re: About requests.packages.urllib3 in Debian
On Monday 10 November 2014 22:02:26 Daniele Tricoli wrote: So, before my analysis on requests' dependant is completed, I'm going to open an RC bug on requests, fix it using Jakub's patch and than open an unblock bug. All done, including unblocking by RT (you rock! :). Many thanks to all! Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: About requests.packages.urllib3 in Debian
Hello Matthias, sorry for the late reply, we had a problematic weekend due to weather in Sicily. On Wednesday 05 November 2014 07:52:55 Matthias Urlichs wrote: I'd add a stub _file_ which just contains from urllib3 import *. Well, urllib3 is composed of multiple subpackage, for a single module this would be the best soluction, but unfortunately it will not works well for a package with multiple submodules. For example, urllib3.contrib.pyopenssl is not imported by from urllib3 import *. IMHO using from-import would be weak: think about new names introduced during an update, missing one will break all code that use the missing name. Cheers, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: About requests.packages.urllib3 in Debian
Hello Jakub, On Wednesday 05 November 2014 12:15:29 Jakub Wilk wrote: Maybe it'd be overkill, but it's possible to teach Python that urllib3 and requests.packages.urllib3 are the same thing. Adding something like this to the top of requests/__init__.py should do the trick: [CUT patch] Many thanks for the patch! On IRC Paul Tagliamonte suggested also something like this and, after looking at half of requests dependant packages (I will continue to look at them) I'm starting to think that this is the best solution because it's entirely transparent both for our package and for users who install packages on Debian using pip install --user. #753578 was, at first, reported upstream: https://github.com/mk-fg/python-onedrive/issues/13 by someone who installed a something not packaged yet for Debian. So, before my analysis on requests' dependant is completed, I'm going to open an RC bug on requests, fix it using Jakub's patch and than open an unblock bug. If there are any objections please let me know. Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: distinguish between PyPI and Debian python packages
On Friday 05 September 2014 12:32:12 Szépe Viktor wrote: Could you help me to get `pip freeze` and `pip list` to display only packages installed by pip and to exclude packages coming from a Debian package? Have you already tried using --local option? $ mkvirtualenv --system-site-packages $ pip install jwt # pyjwt is currently in NEW $ pip list --local jwt (0.3.1) pip (1.5.6) setuptools (5.5.1) You can use --local also with `freeze` option. HTH, -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1671354.A7tacKzA01@mornie
Re: distinguish between PyPI and Debian python packages
On Friday 05 September 2014 12:47:28 you wrote: $ mkvirtualenv --system-site-packages Ehm... $ mkvirtualenv --system-site-packages testlocal Cheers, -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/6159647.LaqvK0xL00@mornie
Re: python-pip and python-virtualenv broken in sid after upgrade to python 2.7.7rc1
On Monday 07 July 2014 16:40:55 Raphael Kubo da Costa wrote: - #754090 (python-urllib3: Version 1.8.2 does not work with HTTPS and proxy tunneling) I'm updating urllib3 right now. Thanks for your report! Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3103012.vgO9e0MJ5R@mornie
Re: Bug#750638: ITP: ndg-httpsclient -- enhanced HTTPS support for httplib and urllib2 using PyOpenSSL
Hello Julien, thanks for packaging ndg-httpsclient! On Thursday 05 June 2014 12:26:22 Julien Cristau wrote: My main interest is to be able to talk to websites using SNI with scripts using python-requests. Once in the archive I will also add ndg-httpsclient into python-requests' Suggests. Kind regards, P.S. I'll do the same for python-urllib3: https://github.com/shazow/urllib3/pull/156 -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Bug#750638: ITP: ndg-httpsclient -- enhanced HTTPS support for httplib and urllib2 using PyOpenSSL
Hello Donald, On Thursday 05 June 2014 10:24:48 Donald Stufft wrote: You need pyasn1, pyopenssl, and ndg-httpsclient in order for the requests/urllib3 stuff to kick in. Yes, of course: I was keeping an eye on all the needed packages. It’d probably be a sane idea to use recommends, at least on Python 2.x since using that also prevents CRIME and the like which Python 2.x is vulnerable to else wise IIRC. Thanks for pointing this: for python-requests I will add to Recommends all of the needed packages to ensure that SNI works as expected and to prevent CRIME. For python3-requests do you think it's needed to also add them to Reccomends? Upstream issue 20994[¹] is still open, but Python3 support SNI, and ssl compression can be disabled, as reported on the issue, using OP_NO_COMPRESSION (on python3 = 3.3, but we have 3.4). I think use Suggests is fine in this case. I will add a README.Debian to explain clearly all of it. Cheers, [¹] http://bugs.python.org/issue20994 -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: python-pip and python-virtualenv broken in sid after upgrade to python 2.7.7rc1
On Tuesday 03 June 2014 20:11:21 Barry Warsaw wrote: Then requests and all other dependents (including those that use the .whls) should get it. I plan to update requests next week, unfortunately I can't work on it during this weekend. If needed, Barry, please go with a team upload! ;) Thanks! -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Dependency on python-oauth2
Hello Iain, On Sunday 09 February 2014 18:41:10 Iain R. Learmonth wrote: If there is no effort to fix these bugs, could someone recommend an alternative package to depend on to provide OAuth2 client functionality for a Python module? You could try python-oauthlib. Upstream is very active and AFAIK python-djangorestframework can use oauthlib thanks to django-oauth-toolkit and python-social-auth (which supersede python-django-social-auth) is already using oauthlib. I also checked, right know, python-keystone and in its requirements.txt there is oauthlib: https://github.com/openstack/keystone/blob/master/requirements.txt#L20 HTH, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: python-django build weirdness
On Wednesday 25 September 2013 15:14:27 Brian May wrote: Guess I should file a bug report against python-django then... Upstream refactored the tests suite during the 1.6 development, so maybe you could also check if the bug is already fixed and mention in the bug report. Thanks! Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/16051556.gDGu7Vgpkz@mornie
Re: Accepted requests 1.2.0-2 (source all)
Hello, On Saturday 11 May 2013 06:33:00 you wrote: Changed-By: Thomas Goirand z...@debian.org Description: python-requests - elegant and simple HTTP library for Python, built for human being python3-requests - elegant and simple HTTP library for Python3, built for human bein Changes: requests (1.2.0-2) unstable; urgency=low . * Uploading to unstable. * rm -rf requests.egg-info on clean so the package can be built twice. Please don't think I'm not open to help from the Team but your upload broke requests on sid: #707780. I was already working on python-urllib3... First time you uploaded requests on experimental I asked only for a ping: just to know and I told you (on IRC) that I want to fix #698258 before uploading requests in sid. Please, next time coordinate with the actual maintainer. Thanks, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Accepted requests 1.2.0-2 (source all)
Hello Thomas, On Saturday 11 May 2013 23:45:13 Thomas Goirand wrote: Please close #707780 in your next upload of python-urllib3. Done! ;) Piotr already sponsored it. Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1888336.uNgFEK5l7F@mornie
Re: statsd + voluptuous packaged!
On Wednesday 03 April 2013 02:10:03 Paul Belanger wrote: [1] https://github.com/pabelanger/python-voluptuous-deb/commit/06f14f76e923f 5dbbed1db8ffd6e0f7a39d8abce Just a quick note: can you honor DEB_BUILD_OPTIONS nocheck? Thanks! Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201304030333.56392.er...@mornie.org
Re: About canonical Vcs fields
On Sunday 17 March 2013 22:56:15 Jakub Wilk wrote: Ugh. I don't mind switching if we switch everything at once. I started to switch my packages to get rid of the warning, but if the team wants to keep svn.d.o I will revert the changes. I'm happy to make the mass-commit if there's consensus that this is the right to do. I don't care about the URL we use but I want to be consistent with the team, so I'm fine with a mass-commit if there's consensus to switch, otherwise I will revert the packages I already switched. Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201303182021.05256.er...@mornie.org
Re: How does team maintenace of python module works?
On Tuesday 19 February 2013 23:20:48 Barry Warsaw wrote: If it makes things easier, I am essentially sided with Piotr. The fact that I don't like git much is immaterial - I want a dvcs and don't have the time to put into a bzr or hg migration. I don't have time to put into a git migration either, but it seems like you've got that covered. :) [CUT: I agree with remaining paragraphs] I'm agree with Barry, although I don't like git, it doesn't matter, I will simply learn git better if it's the best tool for us :) -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130221.46749.er...@mornie.org
Re: How does team maintenace of python module works?
On Saturday 16 February 2013 20:29:07 Dmitrijs Ledkovs wrote: A, F.1 - Migrate to Mercurial, if and only if mercurial queues are fully functional and are used to maintain the debian/patches sub-repository. realisticly i am opposed to a mix of version control systems. someone to do the work - means starting a mirror which works in read-only / mirror mode only. I'm also for A, F.1 but my F option imply that I will help to do the work :) Cheers, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: [psf-trademarks] [PSF-Board] may be a logo?
On Friday 16 September 2011 17:20:45 Barry Warsaw wrote: #7! I like #7 too. -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201109161733.28277.er...@mornie.org
RFS: sphinxcontrib-spelling
Dear mentors, I am looking for a sponsor for my package sphinxcontrib-spelling. It builds these binary packages: python-sphinxcontrib.spelling - Sphinx spelling extension The upload would fix these bugs: #628649. The package appears to be lintian¹ clean (also when builded inside a pbuilder chroot using --twice option), except for the following: P: python-sphinxcontrib.spelling: no-upstream-changelog However upstream is not including changelog in sdist (I will fill a wishlist bug for this). The package is available in SVN: - svn+ssh://svn.debian.org/svn/python-modules/packages/sphinxcontrib-spelling/trunk I would be glad if someone uploaded this package for me. Kind regards, [¹] lintian -IE --pedantic --show-overrides -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Inquiry.
Hello Haris, On Saturday 03 September 2011 19:42:01 Haris Ibrahim K. V. wrote: I would like to know more about how your project works out. You can find more info here: http://wiki.debian.org/Python HTH, -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201109041651.46203.er...@mornie.org
RFS: pdfminer
Dear mentors, I am looking for a sponsor for my adopted package pdfminer. It builds these binary packages: pdfminer-data - PDF parser and analyser (encoding data) python-pdfminer - PDF parser and analyser The upload would fix these bugs: #629178 The package appears to be lintian clean. The package is available in SVN: - svn://svn.debian.org/svn/python-modules/packages/pdfminer/trunk I would be glad if someone uploaded this package for me. Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
RFS: python-peak.util
Dear mentors, I am looking for a sponsor for my package python-peak.util. It builds these binary packages: python-peak.util - utilities from the Python Enterprise Application Kit The upload would fix these bugs: #606382, #607083 Fixing #606382 will close also an FTBFS (LP: #795096) on Ubuntu (which already has Python 2.7 as default). The package appears to be lintian[¹] clean, except for the following: I: python-peak.util source: debian-watch-file-is-missing P: python-peak.util: no-upstream-changelog P: python-peak.util: no-homepage-field The package is available in SVN: - svn+ssh://svn.debian.org/python-modules/packages/python-peak.util/trunk/ I tried to use the multiple upstream tarballs in Debian source packages, but I discovered that svn-buildpackage doesn't support it. I would be glad if someone uploaded this package for me. Kind regards, [¹] lintian -IEm --pedantic --show-overrides -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: RFS: python-peak.util
On Tuesday 14 June 2011 02:47:16 Jakub Wilk wrote: * Daniele Tricoli er...@mornie.org, 2011-06-14, 02:26: I tried to use the multiple upstream tarballs in Debian source packages, but I discovered that svn-buildpackage doesn't support it. Sure it does. Great! http://wiki.debian.org/Projects/DebSrc3.0 should be updated. It point to #577140: it should be already fixed then, or am I missing something? Thanks, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: RFS: decoratortools
On Monday 30 May 2011 20:24:15 Jakub Wilk wrote: That said, I'm not a fan of package bundles like python-peak.util. If no one is against it, I can split python-peak.util into individual packages and transform it into a virtual package. Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: RFS: decoratortools
On Tuesday 31 May 2011 13:58:19 Jakub Wilk wrote: On the other hand, ftp-masters are not fans of tiny packages: http://bugs.debian.org/606411 Then, maybe, is better to preserve the actual situation... s/virtual/transitional/? Of course. -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: RFS: decoratortools
Hello, On Monday 30 May 2011 16:40:36 Jakub Wilk wrote: 1. (Quoting long description:) It provides [...] support for decorating arbitrary assignments, synchronized methods, and more. I didn't check what more means, though. ;) More means: - signature matching - debug generated code - meta-less classes --- a one-size-fits-all metaclass, so that most of the common use cases for metaclasses can be handled with just one metaclass. 2. There are 4 reverse-dependencies in the archive. I discovered that decoratortools was orphaned working on #607083. My first thought was to include decoratortools in python-peak.util, but the former has a popcon score about twice the latter. In addiction after this change python-peak.rules, python-protocols and python-turbogears have to be fixed. Kind records, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: RFS: decoratortools
On Monday 30 May 2011 19:41:20 Daniele Tricoli wrote: In addiction after this change python-peak.rules, python-protocols and python-turbogears have to be fixed. I can volunteer to manage this fixing work but python-protocols is not under the DPMT umbrella. What do you think? Cheers, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
RFS: decoratortools
Dear mentors, I am looking for a sponsor for my package decoratortools. It builds these binary packages: python-decoratortools - version-agnostic decorators support for Python The upload would fix these bugs: #590781 The package appears to be lintian clean, except for the following: P: python-decoratortools: no-upstream-changelog But upstream is not providing any changelog. The package is available in SVN: - svn+ssh://svn.debian.org/svn/python-modules/packages/decoratortools/trunk I would be glad if someone uploaded this package for me. Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
RFS: python-pyth
Dear mentors, I am looking for a sponsor my package python-pyth. It builds these binary packages: python-pyth - library to convert marked-up text between different formats The package appears to be lintian clean[¹]. The upload would fix these bugs: #590037. The package can be found on: - SVN: http://svn.debian.org/wsvn/python-modules/packages/python-pyth/ I would be glad if someone uploaded this package for me. Kind regards [¹] I'm using lintian 2.4.3 -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Request to join the Python Modules Packaging Team
Hello everyone! I would be glad to join the Python Modules Packaging Team. I would like to start taking care of #579114 continuing to maintain it as part of the Debian Python Modules Team and packaging pyth[1], a module intended to make it easy to convert marked-up text between different common formats. I immagine I have to send an ITA for pywavelets, right? My alioth login is: eriol-guest Thanks!!! [1] http://pypi.python.org/pypi/pyth/ -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Request to join the Python Modules Packaging Team
On Wednesday 23 June 2010 12:27:05 Piotr Ożarowski wrote: [Daniele Tricoli, 2010-06-23] I would be glad to join the Python Modules Packaging Team. I will add you this evening. Many thanks!!! :) I immagine I have to send an ITA for pywavelets, right? I hope you mean to *rename* 586894 to ITA... Of course, sorry for my poor English :( I wrote send because I have to send a mail to cont...@b.d.o Send me RFS mail once you will want to upload new version, see A3 from my FAQ¹ [¹] http://people.debian.org/~piotr/sponsor Thanks for your attention! Regards, -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201006231347.54197.er...@mornie.org
