Just my 2 cents here but quoting d-mentors FAQ [1]:
"There are cases where upstream ships a tarball which already contains a
debian directory. This is undesirable, even if you're upstream yourself
or can commit there. Keep the released tarballs (used as .orig.tar.gz)
and the debian directory separated."
[1]
https://wiki.debian.org/DebianMentorsFaq#What.27s_wrong_with_upstream_shipping_a_debian.2F_directory.3F
So you should rather have a separate "debian" branch in the upstream
VCS, branched out with the content of the current Debian packaging and
rebase your packaging work on it.
That way, once the new packaging is tested and reviewed then the
maintainers (if they respond) would just have to pull from it. If you're
worried about credit, just add yourself in the list of authors for
debian/ in d/copyright.
Ghis
On 30/10/15 11:14, Gianfranco Costamagna wrote:
BTW if you really think as upstream that the package is in a bad state, and the
maintainer are not answering to mails
please contact MIA team
https://wiki.debian.org/Teams/MIA
and based on the issues on the current version (e.g. does the current debian
version has serious/security bugs?)
you can even raise some bugs severity.
If the new release brings new features, and it is a leaf package I guess it is
worth waiting a month or two for MIA team
to get the package officially orphaned (then you can take over the package
maintenance)
cheers,
G.
Il Venerdì 30 Ottobre 2015 11:27, Alec Leamas <leamas.a...@gmail.com> ha
scritto:
On 30/10/15 09:51, Gianfranco Costamagna wrote:
Hi Alec,
I'm not seeking any argument as to why the Debian packages are still
0.9.0. It's the debian packager's decision. Full stop.
the argument might be: we were in the freeze because of jessie release at that
time,
so no new packages have been uploaded yet.
FYI, 0.9.0 (current version) was released March, 2011. 0.9.1 happened
June, 2014.
and the maintainer retired a few months ago.
Ah...
Cheers!
--alec
PS: Will process review remarks later. Thanks for those!
