El vie., 4 de oct. de 2019 a la(s) 18:00, Povilas Kanapickas
(povi...@radix.lt) escribió:
>
> Hi,
>
> I would like to package this Python library that is not yet in Debian:
> https://github.com/peterbe/premailer as a new version of the
> cppreference-doc package that I maintain has it as a build de
Hi,
I would like to package this Python library that is not yet in Debian:
https://github.com/peterbe/premailer as a new version of the
cppreference-doc package that I maintain has it as a build dependency.
What would be the best organizational approach to do that? I could
maintain the premailer
Piotr, please do not hold onto the upload - the reason is still there
it's because it's a cruft package, which will be removed once we fix
dh-python and make pylint conflict with pylint3 (instead of just
provide it), which we currently cant do due to dh-python still
producing the pylint3 dependency
> Yes this is a known issue and we are currently waiting for an upload
> of dh-python to avoid automatic replacement of pylint by pylint3 when
> on python3 before pushing those changes further.
http://ftp.debian.org/debian/dists/unstable/main/Contents-amd64.gz
still contains pylint3 so I'm waiting
4 matches
Mail list logo