<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
<head>
<meta name="Generator" content="Kopano WebApp v8.1.0-335">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>RE: Kopano etc.</title>
</head>
<body>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;">Good afternoon Carsten,<br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;"><br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;">The good news is that I think I have kopano webmeetings mostly working ( I had to switch back to coturn ).</span></p>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;"><br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;">In regards to building stuff, I am trying on a virtual machine on Debian 8 64 bits and I am getting the following:<br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;"><br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;"><br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;"></span></p>
<div>git-buildpackage --git-ignore-new</div>
<div> dpkg-buildpackage -rfakeroot -D -us -uc -i -I</div>
<div>dpkg-buildpackage: warning: using a gain-root-command while being root</div>
<div>dpkg-buildpackage: source package kopanocore</div>
<div>dpkg-buildpackage: source version 8.1.0-1</div>
<div>dpkg-buildpackage: source distribution unstable</div>
<div>dpkg-buildpackage: source changed by Guido Günther <agx@sigxcpu.org></div>
<div> dpkg-source -i -I --before-build giraffe</div>
<div>dpkg-buildpackage: host architecture amd64</div>
<div>dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 9.20160115) libgsoap-dev (>= 2.8.35) libvmime-dev</div>
<div>dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting</div>
<div> </div>
<div>And when I try to install the remaining dependencies (I have installed everything else successfully) I get the following:</div>
<div> </div>
<div> </div>
<div> </div>
<div>root@mrc-ubz64:~/kopano/giraffe# apt-get install debhelper libgsoap-dev libvimime-dev</div>
<div>Reading package lists... Done</div>
<div>Building dependency tree </div>
<div>Reading state information... Done</div>
<div>E: Unable to locate package libvimime-dev</div>
<p><br /></p>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;"><br /></span></p>
<blockquote style="border-left: 2px solid #325FBA; padding-left: 5px; margin: 0px 5px;"><span style="font-family: tahoma,arial,helvetica,sans-serif; font-size: 10pt;">-----Original message-----<br /><span><strong>From:</strong> Carsten Schoenert <c.schoenert@gmail.com></span><br /><span><strong>Sent:</strong> Sunday 23rd October 2016 8:42</span><br /><span><strong>To:</strong> Marco Costantino <marco@advanced-finance.com></span><br /><span><strong>Subject:</strong> Re: Kopano etc.</span><br /><br /></span>
<div>
<pre style="white-space: pre-wrap; word-wrap: break-word;">Hi,<br /><br />some more explaining words ...<br /><br />On 21.10.2016 16:39, Carsten Schoenert wrote:<br />[...]<br />>> I am just not familiar enough with Debian to do it.<br />> <br />> You can build the packages also on your own. In the long run that's the<br />> best thing.<br /><br />For fast testing and development the best is to create package on your<br />own. That isn't that difficult as it's seems. The tools for building the<br />stuff will help for quite all of the time. As the packages are right now<br />only prepared for unstable/testing/stretch the follwoing steps are for<br />at minimum a system running Debian testing/stretch.<br /><br />1. Installation of the needed tools (probably not all that really<br /> needed, depends on error messages of the following steps)<br /><br />sudo apt install git-buildpackage devscripts cowbuilder dh-systemd<br /><br />2. Clone the repository from Alioth (only needed once)<br /><br />gbp clone https://anonscm.debian.org/cgit/pkg-giraffe/giraffe.git<br /><br />The name of the repository is depending on historical reasons.<br /><br />3. Create a build environment for building (only needed once)<br /><br />We all build packages in a clean chroot to see issues on missing or<br />broken dependencies early. Also we don't want to mix up our local system<br />with ecosystem around the package(s) we want to create. There are<br />various options for a chroot. Probably the easiest for beginners is to<br />use pbuilder. git-buildpackage ships a helper called 'git-pbuilder' that<br />will run the needed commands to get a valid pbuilder environment. So<br />will simply call<br /><br />git-pbuilder create<br /><br />Further informations about possible options for git-pbuilder you can<br />find in the Debian wiki: https://wiki.debian.org/git-pbuilder<br />Note there the tips about eatmydata and ccache, the latter is useful if<br />you need to build a package over and over again.<br /><br />3.1 Update the pbuilder environment<br /><br />From time to time the chroot needs to be updated especially if you want<br />to build kopanocore after some time. That's easy by done calling:<br /><br />git-pbuilder update<br /><br />Please see again the Debian wiki about git-pbuilder for possible options.<br /><br />4. Build the kopanocore packages<br /><br />After the preparations the Kopano related packages should be buildable<br />easily. git-buildpackage will do the trick an run the needed tools in<br />the correct order. So a build with 4 CPUs would be started by:<br /><br />cd giraffe # the folder there the 'gbp clone' was putting the source<br />git checkout debian/sid # if not already staying on that branch<br />git-buildpackage --git-pbuilder -j4<br /><br />This will create the needed tarball kopanocore_8.1.0.orig.xz, applaying<br />the patches and move all the files into the chroot and run the package<br />build.<br />If it's finished you find all the Kopano package in the folder above the<br />git tree.<br />The package can than be manually installed by 'sudo dpkg -i package.deb'<br />or by apt with a dependency solving 'sudo apt install kopano1.deb<br />kopano2.deb ...'<br /><br />5. Create a local apt package store (optional)<br /><br />A more practical way to install the package is to use a local repository<br />like '/var/local/apt-kopano'.<br />To get this working you need<br /><br />a) copy the packages into that folder<br />b) create a file Packages.gz within that folder<br />c) tell apt to use that repository<br /><br />To solve a) simply create a script that will copy the files to the<br />desired place.<br />The needed package summary file Packages.gz can easily created by the<br />command dpkg-scanpackages that is called inside that folder. I created a<br />script for that and I call it after a build manually. It's appended to<br />that email. The local package need to be placed into var/local/apt-kopano<br /><br />The requirement c) can easy be done by adding a local entry in<br />/etc/apt/sources.list.d/kopano-local.list with the following line(s):<br /><br />deb [trusted=yes] file:///var/local/apt-kopano/ ./<br /><br />Now after a call of 'sudo apt update' you can install the kopano<br />packages as usual.<br /><br />sudo apt install kopano-server kopano-foo<br /><br />>> I just need to add the repository, the rest I'll be able to carry on<br />>> myself and do the testing.<br />> <br />> If you have added the repository then the rest is usual installation.<br />> But before we need to fix the repository.<br />> <br />> Hopefully I have some news on this weekend.<br /><br />It seems the setup of the repository is outdated after the changes to<br />apt in the last few months. We need to create a new stronger signing key<br />first before we can create automatically updates to that repository. I<br />uploaded the packages but your local apt wont use the packages from<br />there because the Release file is signed with a key that uses a SHA1<br />signature. The package a valid and you can use them. But you have to do<br />download them manually and use dpkg or apt locally.<br /><br />Sorry, but I haven't access to the key infrastructure to fix this right<br />now. You can place all the files in the local apt folder like described<br />above an create than a Packages.gz file.<br /><br />Please write further informations about progress or issues, like<br />problems while building local packages, to the Alioth mailing list<br />pkg-giraffe-discuss@lists.alioth.debian.org so the other people can act too.<br /><br />Regards<br />Carsten<br /><br /></pre>
</div>
</blockquote>
</body>
</html>