On Mon, Feb 08, 2016 at 10:05:21PM +0100, Tino Mettler wrote: > thanks for the offer to sponsor the upload. I'll incorporate the change > in a new package and also upgrade to the current upstream version.
ok.
feel free to hurry as you are pleased since this is the last package
blocking that transition ;)
For completeness sake: this kind of thing should not happen. See the
transition bug to see what went wrong with it.
> > I haven't used the git repository since there seems to not be the
> > applied patches in d/patches, and the top d/changelog is not finalized
> > (still use UNRELEASED, even if there is a tag....)
>
> I use gitpkg which handles the patches from corresponding git commits
> inside a patches branch. That's why there is no debian/patches in the
> master branch.
ok, I've never used gitpkg, and even if I use git-buildpackage for some
tasks I'm still in love with plain raw quilt for handing the patches.
And I also now see that README.source I really should have noticed
before...
> The UNRELEASED in debian/changelog is intended. I'm not
> a DD and AFAIK the release is finally set by the uploader.
well, guess that any sponsor is different. I'd usually agree that doing
the change before a sponsor say "ok, let's upload now" may be a waste,
but I also personally believe that the tag should really reflect that
uploaded package, and in this case doesn't. And anyway there are no
written rules about how one is supposed to handle the git repository of
a package (some teams have some rules, but otherwise there are really
none). Given this whole business if you are going to ask sponsorship to
me please send me a signed .dsc somewhere (mentors.d.n, for example) :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
