Re: Build an initial Debian source package with py2dsp from a GitHub project

2021-10-28 Thread Sandro Tosi
couple of features recently introduced that may interest people:

- rudimental support for autopkgtests: autodep8 + a stub for
developers to setup autopkgstests for unittests
- salsa repo creation, if SALSA_TOKEN is available in ~/.devscripts;
this also setup the KGB webhook to post in #d-p-changes

I'm definitely no expert in autopkgtests, so if there's something to
improve, lemme know.

On Sun, Apr 25, 2021 at 12:22 AM Sandro Tosi  wrote:
>
> 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 ``,
> 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 
>
> 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



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Re: Why is isal limited to just three archs?

2021-10-28 Thread Ondrej Novy
Hi Nilesh,

so 16. 10. 2021 v 9:09 odesílatel Nilesh Patra 
napsal:

> I see that isal package is limited to amd64, arm64 and kfreebsd-amd64.
> Is there a particular reason for this? -- Is it possible to extend support
> to other archs?
>

When I packed libisal, only "customer" was liberasurecode. Liberasurecode
supports many backends and supports all archs. And because libisal is
highly optimized for ARM and amd64, I built it only for these archs. Other
platforms are supported, but not optimized. liberasurecode directly should
perform better.

Actually, a -med team package fastp has started to depend on libisal-dev


And because there is other "customer", I will try to build it for all
archs.

Thanks.

-- 
Best regards
 Ondřej Nový