[Pkg-giraffe-discuss] workaround to get zarafa-7.2.0 build?

[Carsten Schoenert]

Hello Guido,

Am 11.06.2015 um 09:00 schrieb Guido Günther:
[snip]
> That's why I'm proposing to switch to th 8 NOW. I checked that the
> generated packages are identical prior and after my switch to dh
> 8. There only changes in the python packages where files were in the
> wrong package before that change.

O.k., Zarafa has released version 7.2.1 as beta version, let's import
this version to see what is left after that debhelper switch. Please
read below ...

[snip]
> But still: Breaks or Conflicts? Very likely breaks is sufficient (see
> section 7.3 and 7.4 of policy).

The relation between Conflicts, Breaks and Replaces isn't really clear
to me (and wasn't ever to me). For now that's the only commit I've
reverted, let's talk about that special thing later.

[snip]
> Please do have a look. There's no need to revert, it's a pretty simple
> git merge, but i don't want to push untested code to the repo.

I fetched your latest work and cherry-picked your commits on top of the
current debian/sid tree. Of course I must git helped a little on your
first commit with the main switch to dh8. But now your changes are
locally included and there are builds successfully packages.

If started to pick up the latest beta release from Zarafa,
zarafa-7.2.1-49597.tar.gz.
You added a branch upstream/7.2 into gbp.conf which doesn't exist right
now. It would be surly the current branch, but from which commit we
should start the new branch? Mattias has imported the 7.2.0 into branch
upstream/7.1 while the groupware meeting, I would branch away from the
tag 7.2.0 into the new upstream/7.2.0 and import then a 7.2.1~rc1 there.

That's the way how it works now here.
To not fall into the same trouble again I'm not pushing my current state
to Alioth. There is the old Giraffe repository on Github I will push all
my work for now.

I append a current lintian output as a first overview of a build from
7.2.1~rc1. The GCC warnings of the build itself has been decreased
against the previous version but now we have much more Lintian warnings. :)

-- 
Regards
Carsten Schoenert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lintian_zarafa_7.2.1~rc1.txt.gz
Type: application/gzip
Size: 3730 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-giraffe-discuss/attachments/20150614/e7020d4a/attachment.bin>