[Pkg-giraffe-discuss] Kopano etc.

Wed Oct 26 15:32:55 UTC 2016

Good afternoon Carsten,

The good news is that I think I have kopano webmeetings mostly working ( I had to switch back to coturn ).

In regards to building stuff, I am trying on a virtual machine on Debian 8 64 bits and I am getting the following:

git-buildpackage --git-ignore-new
 dpkg-buildpackage -rfakeroot -D -us -uc -i -I
dpkg-buildpackage: warning: using a gain-root-command while being root
dpkg-buildpackage: source package kopanocore
dpkg-buildpackage: source version 8.1.0-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Guido Günther <agx at sigxcpu.org>
 dpkg-source -i -I --before-build giraffe
dpkg-buildpackage: host architecture amd64
dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 9.20160115) libgsoap-dev (>= 2.8.35) libvmime-dev
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
 And when I try to install the remaining dependencies (I have installed everything else successfully) I get the following:
   root at mrc-ubz64:~/kopano/giraffe# apt-get install debhelper  libgsoap-dev  libvimime-dev
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package libvimime-dev

-----Original message-----
From: Carsten Schoenert <c.schoenert at gmail.com>
Sent: Sunday 23rd October 2016 8:42
To: Marco Costantino <marco at advanced-finance.com>
Subject: Re: Kopano etc.

Hi,

some more explaining words ...

On 21.10.2016 16:39, Carsten Schoenert wrote:
[...]
>> I am just not familiar enough with Debian to do it.
> 
> You can build the packages also on your own. In the long run that's the
> best thing.

For fast testing and development the best is to create package on your
own. That isn't that difficult as it's seems. The tools for building the
stuff will help for quite all of the time. As the packages are right now
only prepared for unstable/testing/stretch the follwoing steps are for
at minimum a system running Debian testing/stretch.

1. Installation of the needed tools (probably not all that really
   needed, depends on error messages of the following steps)

sudo apt install git-buildpackage devscripts cowbuilder dh-systemd

2. Clone the repository from Alioth (only needed once)

gbp clone https://anonscm.debian.org/cgit/pkg-giraffe/giraffe.git

The name of the repository is depending on historical reasons.

3. Create a build environment for building (only needed once)

We all build packages in a clean chroot to see issues on missing or
broken dependencies early. Also we don't want to mix up our local system
with ecosystem around the package(s) we want to create. There are
various options for a chroot. Probably the easiest for beginners is to
use pbuilder. git-buildpackage ships a helper called 'git-pbuilder' that
will run the needed commands to get a valid pbuilder environment. So
will simply call

git-pbuilder create

Further informations about possible options for git-pbuilder you can
find in the Debian wiki: https://wiki.debian.org/git-pbuilder
Note there the tips about eatmydata and ccache, the latter is useful if
you need to build a package over and over again.

3.1 Update the pbuilder environment

From time to time the chroot needs to be updated especially if you want
to build kopanocore after some time. That's easy by done calling:

git-pbuilder update

Please see again the Debian wiki about git-pbuilder for possible options.

4. Build the kopanocore packages

After the preparations the Kopano related packages should be buildable
easily. git-buildpackage will do the trick an run the needed tools in
the correct order. So a build with 4 CPUs would be started by:

cd giraffe # the folder there the 'gbp clone' was putting the source
git checkout debian/sid # if not already staying on that branch
git-buildpackage --git-pbuilder -j4

This will create the needed tarball kopanocore_8.1.0.orig.xz, applaying
the patches and move all the files into the chroot and run the package
build.
If it's finished you find all the Kopano package in the folder above the
git tree.
The package can than be manually installed by 'sudo dpkg -i package.deb'
or by apt with a dependency solving 'sudo apt install kopano1.deb
kopano2.deb ...'

5. Create a local apt package store (optional)

A more practical way to install the package is to use a local repository
like '/var/local/apt-kopano'.
To get this working you need

a) copy the packages into that folder
b) create a file Packages.gz within that folder
c) tell apt to use that repository

To solve a) simply create a script that will copy the files to the
desired place.
The needed package summary file Packages.gz can easily created by the
command dpkg-scanpackages that is called inside that folder. I created a
script for that and I call it after a build manually. It's appended to
that email. The local package need to be placed into var/local/apt-kopano

The requirement c) can easy be done by adding a local entry in
/etc/apt/sources.list.d/kopano-local.list with the following line(s):

deb [trusted=yes] file:///var/local/apt-kopano/ ./

Now after a call of 'sudo apt update' you can install the kopano
packages as usual.

sudo apt install kopano-server kopano-foo

>> I just need to add the repository, the rest I'll be able to carry on
>> myself and do the testing.
> 
> If you have added the repository then the rest is usual installation.
> But before we need to fix the repository.
> 
> Hopefully I have some news on this weekend.

It seems the setup of the repository is outdated after the changes to
apt in the last few months. We need to create a new stronger signing key
first before we can create automatically updates to that repository. I
uploaded the packages but your local apt wont use the packages from
there because the Release file is signed with a key that uses a SHA1
signature. The package a valid and you can use them. But you have to do
download them manually and use dpkg or apt locally.

Sorry, but I haven't access to the key infrastructure to fix this right
now. You can place all the files in the local apt folder like described
above an create than a Packages.gz file.

Please write further informations about progress or issues, like
problems while building local packages, to the Alioth mailing list
pkg-giraffe-discuss at lists.alioth.debian.org so the other people can act too.

Regards
Carsten

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-giraffe-discuss/attachments/20161026/829c9fa1/attachment.html>