Bug#822856: RFS: dvtm/0.15-0.1 NMU
control: owner -1 !
control: tags -1 moreinfo
Hi,
I'm unsure about the copyright of:
forkpty-*
and vt.*
can you please doublecheck?
I'm also unsure about the versioned debhelper override, who cares?
cheers,
G.
Il Giovedì 28 Aprile 2016 14:21, Dmitry Bogatov <KAction@gnu.org> ha scritto:
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "dvtm"
* Package name : dvtm
Version : 0.15-0.1
Upstream Author : Marc Andre Tanner <mat@brain-dump.org>
* Url : http://www.brain-dump.org/projects/dvtm
* Licenses : MIT/X
Section : utils
I want to make NMU, since request to package new version is more then
270 days old and `dvtm-0.15' have features I miss in 0.12. Maintainer
and Uploader are in CC. I am ready to take over package, if current
maintainer (Albin Tonnerre) is too busy.
It builds those binary packages:
dvtm -- Tiling window management for the console
To access futher information about this package, visit the following URL:
http://mentors.debian.net/package/dvtm
Alternatively, one can download the package with dget using this command:
http://mentors.debian.net/debian/pool/main/d/dvtm/dvtm_0.15-0.1.dsc
Alternatively, you can access package debian/ directory via git from URL:
Sorry, git repository is not availiable
More information about dvtm can be obtained from http://www.brain-dump.org/projects/dvtm
Changes since last upload:
* Non-maintainer upload.
* New upstream release (Closes: #793472)
* Bump debhelper compat level (9 -> 10), and add lintian override
about wrong versioned debhelper dependency
* Replace patch about stripping and PREFIX with environment variables,
exported from debian/rules.
* Adjust debian/docs to match upstream, renamed README to README.md
* Convert debian/changelog into DEP-5 format
* Remove `config.h' at clean stage
* Bump standards version to 3.9.8 (no changes needed)
* Enable hardening
* Make copymode work out-of-box in most cases
* Export every available command for fifo scripting
Regards,
Dmitry Bogatov
Reply to: