Re: Build an initial Debian source package with py2dsp from a GitHub project
> > this solution also underestimates the in-progress migration towards
> > poetry and pyproject.toml, where `python3 setup.py sdist` is not
> > available.
>
> Where does the metadata come from for projects using these things?
that'd be pyproject.toml AFAIUI
the point i wanted to make is that it would require to implement a
parser for setup.{py,cfg} and pyproject.toml, plus some way to decide
which one to use in case a project supports both (it happens) and how
to override the selection in case one system is available and outdated
(it happens).
All of this is done by PyPI already, and the fact a project exists on
GH but not on PyPI it's either because it's such a niche project or
it's still under heaving development, that working on a solution
*right now* is not a good use of our time.
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi
Re: Build an initial Debian source package with py2dsp from a GitHub project
On Wed, May 5, 2021 at 10:14 PM Sandro Tosi wrote: > this solution also underestimates the in-progress migration towards > poetry and pyproject.toml, where `python3 setup.py sdist` is not > available. Where does the metadata come from for projects using these things? -- bye, pabs https://wiki.debian.org/PaulWise
Re: Build an initial Debian source package with py2dsp from a GitHub project
On Wed, May 5, 2021 at 7:50 PM Andrey Rahmatullin wrote: > But Github doesn't provide the metadata. Usually the metadata is available in setup.cfg (or possibly setup.py), both of which should be in GitHub, although data in setup.py would be harder to extract. -- bye, pabs https://wiki.debian.org/PaulWise
Re: Build an initial Debian source package with py2dsp from a GitHub project
> Right and thus I am wondering if we could work through this, somehow? > That is, $something fetches the tarball, runs sdist or whatever, and > then the py2dsp magic. > > P.S. I know this sounds a little ambitious but I believe this would > really help, too. i do not plan to implement such a feature. this solution also underestimates the in-progress migration towards poetry and pyproject.toml, where `python3 setup.py sdist` is not available. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Re: Build an initial Debian source package with py2dsp from a GitHub project
On Thu, May 6, 2021 at 1:20 AM Andrey Rahmatullin wrote: > But Github doesn't provide the metadata. You would need to get a tarball > and run sdist or something like that. Right and thus I am wondering if we could work through this, somehow? That is, $something fetches the tarball, runs sdist or whatever, and then the py2dsp magic. P.S. I know this sounds a little ambitious but I believe this would really help, too. - u
Re: Build an initial Debian source package with py2dsp from a GitHub project
On Thu, May 06, 2021 at 01:16:40AM +0530, Utkarsh Gupta wrote: > Hello, > > On Thu, May 6, 2021 at 12:33 AM Sandro Tosi wrote: > > that's correct, the package still needs to be on PyPI, as that's the > > place where py2dsp obtains most of the package metadata > > Can we change that or have a flag or something added so that it pulls > from g/h directly? But Github doesn't provide the metadata. You would need to get a tarball and run sdist or something like that. -- WBR, wRAR signature.asc Description: PGP signature
Re: Build an initial Debian source package with py2dsp from a GitHub project
Hello, On Thu, May 6, 2021 at 12:33 AM Sandro Tosi wrote: > that's correct, the package still needs to be on PyPI, as that's the > place where py2dsp obtains most of the package metadata Can we change that or have a flag or something added so that it pulls from g/h directly? - u
Re: Build an initial Debian source package with py2dsp from a GitHub project
On Wed, May 5, 2021 at 2:58 PM Andrey Rahmatullin wrote: > > On Thu, May 06, 2021 at 12:08:06AM +0530, Utkarsh Gupta wrote: > > However, I am running into an issue (or I guess I am just not doing it > > correctly). > > Whilst trying to package from the g/h source > > (https://github.com/keylime/keylime), it fails like this: > > http://paste.debian.net/1195339/ > > > > Am I missing something? > As far as I can see, the change is only about getting the tarball, it > still needs metadata from PyPI. that's correct, the package still needs to be on PyPI, as that's the place where py2dsp obtains most of the package metadata -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Re: Build an initial Debian source package with py2dsp from a GitHub project
On Thu, May 06, 2021 at 12:08:06AM +0530, Utkarsh Gupta wrote: > However, I am running into an issue (or I guess I am just not doing it > correctly). > Whilst trying to package from the g/h source > (https://github.com/keylime/keylime), it fails like this: > http://paste.debian.net/1195339/ > > Am I missing something? As far as I can see, the change is only about getting the tarball, it still needs metadata from PyPI. -- WBR, wRAR signature.asc Description: PGP signature
Re: Build an initial Debian source package with py2dsp from a GitHub project
Hi Sandro, On Sun, Apr 25, 2021 at 9:53 AM Sandro Tosi wrote: > Let me know if you find this useful and if there are > issues/enhancement you'd like to see added/fixed. This looks great! Thank you! However, I am running into an issue (or I guess I am just not doing it correctly). Whilst trying to package from the g/h source (https://github.com/keylime/keylime), it fails like this: http://paste.debian.net/1195339/ Am I missing something? - u
