Bug#817626: src:poppassd: Co-maintain poppassd

2016-09-21 Thread Peter Colberg 
On Wed, Sep 21, 2016 at 05:46:09PM -0400, Peter Colberg wrote:
> Please clone the updated package using
> 
>   gbp clone ssh://git.debian.org/git/collab-maint/poppassd.git

For verification, these are the current branch heads:

  git show-ref --heads

  6e26c876530625d4cdc3451bef921ce635887658 refs/heads/master
  db27d6addd476baf420d49f362b79b373462063e refs/heads/pristine-tar
  79da3cf634ebe761d494fcbbcf36a4da71379383 refs/heads/upstream

Please note that debian/copyright includes the following line:

  Files-Excluded: m4/* auto.sh

When you download a new tarball using uscan or gbp import-orig --uscan
in the future, this will automatically repack the orig tarball while
excluding the embedded files from the package autoconf-archive.

Peter

Bug#817626: src:poppassd: Co-maintain poppassd

2016-09-21 Thread Peter Colberg 
Hi Adam,

With the stretch freeze getting close, I have imported the poppassd
history into a collab-maint git repository and updated the packaging
to fix #817626 and conform to Debian policy. Please note that I have
*not* added myself to Uploaders. If you wish to continue to maintain
the package on your own, that is perfectly fine with me.

This is the summary of the proposed changes:

  * New upstream version 1.8.7
  * Switch source format to 3.0 (quilt)
  * Use dh with autoreconf in debian/rules (Closes: #817626)
  * Build with hardening flags
  * Add machine-readable debian/copyright
  * Update Homepage field
  * Add Vcs-Git and Vcs-Browser fields
  * Update debian/watch
  * Run wrap-and-sort
  * Update Standards-Version to 3.9.8

Please clone the updated package using

  gbp clone ssh://git.debian.org/git/collab-maint/poppassd.git

Please inspect the changes to the previous version using, e.g.,

  git log -p --stat --decorate --reverse debian/1.8.5-4..master

I have compared the upstream source line-by-line with the former
patched Debian source. The patch for #287820 has been included
upstream, otherwise the upstream changes are cosmetic.

All you would need to do now is update the changelog with

  gbp dch --commit --release

and prepare a source-only upload and tag a new release with

  gbp buildpackage -S --git-tag

In case this is the first time you are using git-buildpackage, it is
good practice to push the debian/* git tag only after the upload has
been accepted. This allows further changes if the upload is rejected.

Thanks,
Peter