Dear Andreas, Thanks for your prompt reply on this. > This should be separately packaged. There is actually no need to wait > until it passes new queue. You can build against your local package > and we upload both to new in the right sequence. Sounds good! Unfortunately, there are no github releases for pll-modules[3] and the last commit pushed was back in 2017 with pending pull requests and issues open for over a year now, so I fear that the author is unresponsive. Would it be acceptable policy-wise if I was to locally create an upstream tarball and package that way as there is no upstream release for uscan to work on? Kind regards, Shayan Doust On 29/05/2020 19:59, Andreas Tille wrote: > On Fri, May 29, 2020 at 07:04:22PM +0100, Shayan Doust wrote: >> I've just been working on getting raxml-ng[1] up and going as a package. >> I've realised that it depends on libpll[2] but also on pll-modules[3]. >> Luckily, libpll is packaged and the development package is labelled as >> libpll-dev. > > Yes. I havn't touched that package long ago. If you realise some issues > with it in connection with raxml-ng feel free to tweak it. > >> Unfortunately, pll-modules isn't (nor has its author readily >> made a release available for it on github). >> >> Now in cases like this, should I try and push for pll-modules to be >> packaged, wait until an upload and then finish packaging raxml-ng or >> should I use missing-sources for now until the dependency is packaged >> (considering it is embedded into the raxml-ng repository but as a >> submodule)? > > This should be separately packaged. There is actually no need to wait > until it passes new queue. You can build against your local package > and we upload both to new in the right sequence. > > Thanks for working on this > > Andreas. > >> [1]: https://salsa.debian.org/med-team/raxml-ng >> [2]: https://salsa.debian.org/med-team/libpll >> [3]: https://github.com/ddarriba/pll-modules > > pub RSA 4096/19D02395 2019-09-04 Shayan Doust (Personal EMAIL) <hello@shayandoust.me> >> > > > >
Attachment:
0x6D7D441919D02395.asc
Description: application/pgp-keys
Attachment:
signature.asc
Description: OpenPGP digital signature