Re: [Kolab-devel] Announcing some blog posts for building packages for Debian on OBS

Op woensdag 30 oktober 2013 14:13:10 schreef Paul Boddie:
> On Tuesday 29. October 2013 19.17.36 Paul Boddie wrote:
> > 
> > I'll see if this makes things a bit easier, especially when it comes to
> > handling previously unpackaged build dependencies, but as Mateusz noted
> > it's a bit different from the way Debian packaging is normally done and
> > some familiarisation with the tools is obviously required.
> 
> Well, following up to myself, I can say that osc does manage to build 
> packages, but it also prompted me to try and rebuild them using pbuilder. 
> Clearly, the packages are built from their sources and genuine packages are 
> placed in the /var/tmp/build-root/Debian_7.0-i586/usr/src/packages directory 
> (although they get replaced when one does a new build), so they should be 
> usable and rebuildable.
> 
> However, when trying to rebuild libkolabxml with pbuilder, I get the 
> following:
> 
> cp: cannot stat 'debian/tmp/usr/lib/cmake/Libkolabxml/LibkolabxmlTargets-
> noconfig.cmake': No such file or directory
> 
> I saw this error before, but I wonder why osc doesn't fail when building the 
> package since osc should be adhering to Debian packaging guidelines, and it 
> obviously produces the libkolabxml-dev.install file that causes this error.
> 
I've seen this when we were building kolab packages targeting Debian Wheezy, and I was building libkolab* for Debian unstable. There was a difference in the way these build commands are called because the Debian toolchain versions differed between wheezy and unstable. If memory serves, debhelper in sid defaults to a default setting  CMAKE_BUILD_TYPE=RelWithDebInfo, which was empty before. This causes a file LibkolabxmlTargets-RelWithDebInfo.cmake to be created instead of LibkolabxmlTargets-noconfig.cmake. So if the *.install file contains explicit references to these cmake files, it will fail on one of these versions. I put usr/lib/cmake/Libkolab/*.cmake in my libkolab-dev.install file to make it work in either version.

What I don't know what this means in the current OSB environment, though.

Cheers,

Paul

PGP: 8FE6E0BD

_______________________________________________
devel mailing list
[email protected]
https://lists.kolab.org/mailman/listinfo/devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAABCAAGBQJSgVa8AAoJEHtCjbaP5uC9ApQQAKJhLdTtlK+WyncW43scRgiz
TI9swJ+Gqukq84EVrbeycMyPioY2l80fy4dVniAnEXETriOq1X/s0eafCMIQRUM1
igRjHZamBpCCBRJUjNjSWtq4EgstGma9XxhFf3Eh0EkrmWOBN5EbRLzM/aRChKWJ
Le2JFuE3XgXHqVlY5C8XX5YswEqJIXzYIjK5mzP6H6MpkDiMxKyUKzM11evOGg+O
89n2jIfhDua+zy90FuifcptF8tqfwmFLj0P2Mfm6rd71yy1KQmS12OCtGjv/3fDd
QnNDEVOjgjgIjsXIuAtQNWPbU4R7d8s2C9PAtQSL6Ry4L4dj0WPm01DZC1gthKBy
DMdW3wd0rS3bagM8ezgXKoPuPk48cJEgrLT6HE4PE+ahtqGN1qCgjxSuGVu5G4Rm
gDx2/MCih4fBCQ2l7O0cu4wa63WWIXI/gRH7fw61SFV/rbLu1jKAZUvtWlvFxTWL
DZPyrsaFD/93E3aqINQDviotHTPJ4WuCBByO+CDJA9U82tCmiRkEFITtWeePNsPx
r1V1glbH0JvPP84e9TSPbGAgBp8o0XaTBpY9Wwm9HsTOAt16Ski/1jDvLVoAWj6W
J0Te6SU7fThG8oNsUrAQ4BCNF5z6pLln5K7qf80hO1LYvqKpsJBJGspMp8ZrHnK9
CdnGcpGcqxqzf96ZO0Kl
=4YGZ
-----END PGP SIGNATURE-----