Let me know if you find this useful and if there are
issues/enhancement you'd like to see added/fixed.
It would be useful if it could also be run against a tarball
or git repository (a directory) that one has already downloaded.
It would be useful if it could also be run against a tarball
this is already supported (but in general by py2dsp and in the context
of --github), f.e.:
$ ./py2dsp --profile dpt --distribution unstable --revision 1 --gh https://github.com/indygreg/python-zstandard
./zstandard_0.14.1.orig.tar.gz
uses the locally available zstandard_0.14.1.orig.tar.gz tarball (which
is not the latest available on gh) to create the source pkg with the
github customizations
or git repository (a directory) that one has already downloaded.
i dont see how starting from a git repo is useful, can you expand?
or git repository (a directory) that one has already downloaded.
i dont see how starting from a git repo is useful, can you expand?
instead of generating a .dsc first and then importing it into a git repository, it's more logical to me to import an upstream tarball into a
git repository first (gbp import-orig), and then generate the debian packaging on top of that.
Let me know if you find this useful and if there are
issues/enhancement you'd like to see added/fixed.
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.
However, I am running into an issue (or I guess I am just not doing it correctly).As far as I can see, the change is only about getting the tarball, it
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?
that's correct, the package still needs to be on PyPI, as that's the
place where py2dsp obtains most of the package metadata
But Github doesn't provide the metadata. You would need to get a tarball
and run sdist or something like that.
Hello,But Github doesn't provide the metadata. You would need to get a tarball
On Thu, May 6, 2021 at 12:33 AM Sandro Tosi <morph@debian.org> 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?
this solution also underestimates the in-progress migration towards
poetry and pyproject.toml, where `python3 setup.py sdist` is not
available.
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?
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.
Hello,
recently i've been making some enhancements to py2dsp (part of
pypi2deb[1] ); for those who dont know what that is, py2dsp is a tool
that, given a PyPI project, will create an (initial) Debian source
package.
[1] https://packages.qa.debian.org/p/pypi2deb.html
I've just finished a patch that extend py2dsp to fetch the upstream
tarball from GitHub instead; nowadays this is my preferred source for upstream tarballs, given it contains all the project files (not only
the one published on pypi via sdist, often missing important files
like tests, or doc sources, etc).
it's currently available at the git branch at [2] (there's a PR open at [3]):
[2] https://github.com/sandrotosi/pypi2deb/tree/morph
[3] https://github.com/p1otr/pypi2deb/pull/27
once you cloned/checkout that branch, you can run:
$ ./py2dsp --profile dpt --distribution unstable --revision 1 --github https://github.com/USER/PROJECT
alternatively, you can specify an additional argument `<source name>`,
if PROJECT is not the source name you want to use in Debian:
$ ./py2dsp --profile dpt --distribution unstable --revision 1 --github https://github.com/USER/PROJECT <source name>
and it will create the source package in the `result/` directory.
Let me know if you find this useful and if there are
issues/enhancement you'd like to see added/fixed.
Regards,
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 349 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 117:34:53 |
| Calls: | 7,612 |
| Files: | 12,786 |
| Messages: | 5,683,872 |