[Pkg-owncloud-maintainers] Updating owncloud-client to 2.1.0

[Gaudenz Steinlin]

Hi

I'd like to update owncloud-client to 2.1.0 because the new version
fixes some issues with reconnecting after network changes and
suspend/resume.

I built a new version locally and it looks good so far, but I'm not sure
if I used the correct workflow:

1. Downloaded the upstream source with "uscan --compression xz". This
automatically repacked the source to remove the non DFSG components.

2. To update the upstream branch in the GIT repository I added the
upstream GIT repo from Github as an additional remote. Then I did "gbp
import-orig --upstream-vcs-tag=v2.1.0
../owncloud-client_2.1.0+dfsg.orig.tar.xz". As far as I understand this
is how things have been done for the other upgrades. But I could be
wrong.

3. I checked for patches in debian/patches applied upstream and
refreshed all patches.

If this is the correct workflow and you agree I can push my changes to
the Alioth repository for additional review and eventually upload the
2.1.0 package.

How do you manage the debian/changelog file? AFAICS directly using gbp
dch will include all upstream commits in the changelog which is not what
we want. Is there an option to avoid this or do you manually use --since
or do you completely manage the changelog by hand?

Gaudenz


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 464 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-owncloud-maintainers/attachments/20151215/3087cd52/attachment-0001.sig>