On Thu, 2009-06-18 at 17:14 +0100, Neil Williams wrote: > On Thu, 18 Jun 2009 15:10:28 +0100 > Wookey <[email protected]> wrote: > > > > > What I did now to get an emdebian package: > > > > > > > > -dh_make -e [email protected] > > > > -f ../libdbusapihasler-0.0.0.tar.gz > > > > > > That is nowhere near enough to generate a Debian package and therefore > > > insufficient to create an Emdebian package from that. Packaging for > > > Debian is not a trivial task, especially for libraries. > > > > > > > This creates the ./debian/control file + several others. I edited the > > > > control file, dh_make suggests the package name, so > > > > libdbusapihaslerBROKEN was changed to libdbusapihasler. > > You've probably got a lot of cruft in the debian/ directory that needs > to be removed too. Example files etc. > > > > The dh_make template files need considerable editing before they will > > > generally make a useful package. > > > > Yes - there is a fair amount more fettling you need to do, although > > for a simple library package it's not that difficult. The main thing > > is to be careful about naming, and so-names. The Debian policy > > document explains how it should be done. > > It isn't easy to automate based on metadata already available within > the upstream sources either, which is why dh_make is such a partial > solution. > > The majority of lintian warnings are relevant for an Emdebian package - > the reason we only check a subset is due to a bug in lintian itself. It > is worth fixing as many lintian errors as possible as some will have > direct implications for the cross-build.
I got one (lintian warning) but the emdebian package was build, yipee. I am not sure if I should dig deeper into that: ostprocessing cross-built libmemman for Emdebian Crush. dpkg-architecture: warning: Specified GNU system type arm-linux-gnu does not match gcc system type i486-linux-gnu. Building libmemman-dev_0.0.0-1em1_arm.deb in /mnt/ext3_data/projects/hasler/emdebian_eval/emdebian_src/libs/hr/libmemman/libmemman.grip dpkg-deb: building package `libmemman-dev' in `/mnt/ext3_data/projects/hasler/emdebian_eval/emdebian_src/libs/hr/libmemman/libmemman.grip/libmemman-dev_0.0.0-1em1_arm.deb'. Building libmemman_0.0.0-1em1_arm.deb in /mnt/ext3_data/projects/hasler/emdebian_eval/emdebian_src/libs/hr/libmemman/libmemman.grip dpkg-deb: building package `libmemman' in `/mnt/ext3_data/projects/hasler/emdebian_eval/emdebian_src/libs/hr/libmemman/libmemman.grip/libmemman_0.0.0-1em1_arm.deb'. Unable to find the unpacked source directory: /mnt/ext3-data/projects/hasler/emdebian_eval/emdebian_src/libs/hr/libmemman/libmemman.grip/libmemman_0.0.0. dpkg-architecture -aarm -c 'DEB_BUILD_OPTIONS="usecrush" emgrip -o ../libmemman.grip ../libmemman_0.0.0-1em1_arm.changes ' Running lintian checks for Emdebian only. E: libmemman_0.0.0-1em1_arm.changes: file-size-mismatch-in-changes-file libmemman_0.0.0-1em1_arm.deb 33224 != 35326 N: N: The actual file size does not match what's listed in the .changes file. N: N: Severity: serious, Certainty: certain N: E: libmemman_0.0.0-1em1_arm.changes: file-size-mismatch-in-changes-file libmemman-dev_0.0.0-1em1_arm.deb 1758 != 1424 Recording that 'libmemman' has failed a lintian check I installed the new packages on the target and they worked as expected. However, for later I don't want them to install on the target but into the tarball created by emsandbox. Thus I suppose sudo dpkg-cross --install libdbusapihasler_0.0.0-1em1_arm.deb does the job. Afterward emsandbox creates the tarball including our packages. Please correct me if I am missing something. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
