Am Mon, Jul 25, 2022 at 10:09:05AM +0200 schrieb Andreas Tille:
> I was able to run
>
> py2dsp pystow
>
> with a sufficient result for my purposes...
While I've read here the suggestion to fetch the Tarball rather vom Github than
from pypi (and I agree with this) I would suggest to implement
Hi Sandro,
I was able to run
py2dsp pystow
with a sufficient result for my purposes with the following patch:
diff --git a/pypi2deb/pypi.py b/pypi2deb/pypi.py
index 3e342c0..0639de3 100644
--- a/pypi2deb/pypi.py
+++ b/pypi2deb/pypi.py
@@ -38,8 +38,8 @@ log = logging.getLogger('pypi2deb')
Hi,
Am Sat, Jul 23, 2022 at 10:21:40AM -0400 schrieb Sandro Tosi:
> > I wonder whether you are able to reproduce the issue at your side since
> > in one of your last mails you asked whether the new version might have
> > fixed the issue. This might implicitly mean it works for you since I
> >
> I wonder whether you are able to reproduce the issue at your side since
> in one of your last mails you asked whether the new version might have
> fixed the issue. This might implicitly mean it works for you since I
> assume you fired up the command line at your side as well.
it never worked.
Hi Sandro,
Am Fri, Jul 22, 2022 at 11:39:50PM -0400 schrieb Sandro Tosi:
>
> this seems to be related to
> https://discuss.python.org/t/backwards-incompatible-change-to-pypi-json-api/17154
> , although they say /pypi//json (what py2dsp uses to gather
> the latest released verison) still contains
> No, the problem persists:
>
> $ py2dsp -v pystow
> D: py2dsp py2dsp:156: version: 3.20220707
> D: py2dsp py2dsp:157: ['/usr/bin/py2dsp', '-v', 'pystow']
> /usr/bin/py2dsp:163: DeprecationWarning: There is no current event loop
> loop = asyncio.get_event_loop()
> D: py2dsp py2dsp:44: args:
Am Thu, Jul 21, 2022 at 05:50:05PM -0400 schrieb Sandro Tosi:
> > Are you sure thet the package version 3.20220721 contains the correct
> > executables?
>
> yes, i simply forgot to bump the internal version; what really matters
> is: does the last release fix the problem you were having?
No, the
> Before I've sent my mail I also checked Git HEAD which was no change.
there was:
https://salsa.debian.org/python-team/tools/pypi2deb/-/commit/f9eda106f1514a1fff83fb3a8324817a91489879
> Are you sure thet the package version 3.20220721 contains the correct
> executables?
yes, i simply forgot
Am Thu, Jul 21, 2022 at 02:52:38PM -0400 schrieb Sandro Tosi:
>
> a fix for this was available in the git repo but not released, i took
> care of that with version 3.20220721 that has just been ACCEPTED.
Before I've sent my mail I also checked Git HEAD which was no change.
Anyway, thanks for
> $ py2dsp -v pystow
> D: py2dsp py2dsp:156: version: 3.20220707
> D: py2dsp py2dsp:157: ['/usr/bin/py2dsp', '-v', 'pystow']
> /usr/bin/py2dsp:163: DeprecationWarning: There is no current event loop
> loop = asyncio.get_event_loop()
> D: py2dsp py2dsp:44: args: Namespace(verbose=True,
Hi Sandro,
Am Thu, Jul 07, 2022 at 11:10:01PM -0400 schrieb Sandro Tosi:
> My goal is to make py2dsp (contained in pypi2deb) the default tool
> used to create Python packages in Debian (like many other
> language-specific tools already do f.e. for go, rust, npm, etc). The
> new release contains
Hi!
El vie, 8 jul 2022 a la(s) 00:10, Sandro Tosi (mo...@debian.org) escribió:
> Hello,
> Piotr has kindly moved pypi2deb to salsa[1] and given me access to the
> project so i was able to merge my changes and release[2] a new version
> of this tool in Debian.
>
> [1]
12 matches
Mail list logo
