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

[Gaudenz Steinlin]

Sandro Knauß <bugs at sandroknauss.de> writes:
>
>> 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?

No the changes more or less match. The only noticable difference is that
you decided to resolve the conflict on
cmake/modules/GNUInstallDirs.cmake by adding this file while I decided
to keep it deleted from the master branch. This file was deleted by
taffit in commit f67673b1f8484febec1797ce854d9a6c526b05ea. So keeping it
deleted looked like the better option.

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

Nice trick. Will keep this in mind.

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

It's not very important to me. I have my fixed package and the Lernstick
distribution is not really affected as suspend/resume is not really
supported on Live Systems on USB. On the other hand NEW processing is
rather slow these days, so uploading 2.1.0-1 without this change might
be worth it. You can then upload the new package to experimental and get
it through NEW while still being able to update the package in unstable
if needed. 

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

No need to be sorry, you are the Maintainer so I should have asked or
expect my work to be not needed. ;-)

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/20151216/af229919/attachment.sig>