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

Sandro Knauß bugs at sandroknauss.de
Wed Dec 16 00:56:00 UTC 2015


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.

mmh i just stated to package it myself and also uploaded it. 

> 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.

"uscan" is enough the compression is select automatically.

> 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.
that is okay but please also add --signed-tag, becuase upstream also has a 
signed tar.xz.

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

:D

> 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.

Well you should see, the same in my uploaded changes - Did you do something 
different?

> 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?

The trick is to create a first patch to d/chagelog via dch -v <version>-0 and 
than add this one. After that if you use gbp dch -a only change to that patch 
are added. generally gbp dch -a only adds patches till the last time d/
changelog was touched.

With 2.1.0 we also can now also build dolphin plugin *YEAH*, so a new binary 
package is added so the version must go through NEW before entering unstable. 
But if it is important to have a fast version for you we can push the dolphin-
plugin to the -2 version, so that -1 can enter unstable directly.

But what is missing for sure from my side:
* update d/copyright - lintian complains already befause of missing files
* test the package on my own laptop

Sorry, that we both came to same idea to update the package at the same day - 
But I was already in the state to click the push when I saw you email. Maybe 
send a shot notice before you start investing time. I will also try to send 
you a notice next time... 

Regards,

sandro
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-owncloud-maintainers/attachments/20151216/4916617e/attachment.sig>


More information about the Pkg-owncloud-maintainers mailing list