Re: [Kolab-devel] Announcing some blog posts for building packages for Debian on OBS
Paul Boddie <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Message-ID | <201310301413.10679.paul__44903.1141390607$1383138138$gmane$org@boddie.org.uk> |
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. Any ideas? Paul