I am happy to sponsor this upload; will dput the built package in a
moment.
Two tangential points.
First, examination of the source reveals that the packaging is quite
old, and could use some updating.
Second, upstream development has restarted in a git repo on
sourceforge.
242fb85387ffbd503d466bd90c8516
> gbp buildpackage
>
> Changes since the last upload:
>
> [ Sean Whitton ]
> * New upstream release (Closes: #845061).
> * Adopt package on behalf of pkg-emacsen team.
> This has been approved by the de facto maintainer, Barak A. Pearlmutter
Well, it's not a *violation* of the DFSG to include derived files in
the upstream sources, as long as the source needed to regenerate them
is also included. That's often done for bootstrapping compilers.
Source tarballs also often include documentation PDFs and such so
people installing the
I use transmission constantly and would be happy to sponsor. In
principle of course: assuming there are no technical show-stoppers.
I already have my own fork on salsa.debian.org/bap/transmission with
some very minor tweaks.
In the meantime, I note that Sandro Tosi has dropped his
maintainership
with that. What do you think? This would be:
Maintainer: Leo Antunes
Uploaders: Alexandre Rossi ,
Barak A. Pearlmutter
and would allow "proper" uploads, not just NMUs.
I merged your "fix build on bookworm" patch, but the package still
builds fine on a chro
5 matches
Mail list logo