[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: emdebuild -v: generated package_em1_arm.deb->data.tar.gz empty



On Tue, 23 Jun 2009 17:39:16 +0200
hoefle marco <marco.hoefle@nanotronic.ch> wrote:

> > 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:

I think you probably should - something may well be wrong with your
versioning / native vs non-native and you aren't getting a proper Crush
package because dpkg-source fails to operate.

You may need to experiment with "gripping" the package manually and
seeing what is going wrong. Use multiple --verbose options to emdebuild
to see what is happening and how emgrip is being called.

Also ensure you're using the version of emdebian-grip and
emdebian-tools just uploaded to Debian unstable.

> 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.

That is a bad error and leads to other issues.

> E: libmemman_0.0.0-1em1_arm.changes: file-size-mismatch-in-changes-file
> libmemman_0.0.0-1em1_arm.deb 33224 != 35326

i.e. the file has been reduced but because of issues to do with the
unpacking, the .changes file cannot be uploaded to a repository.

It does sometimes occur with standard Debian packages - I've get
problems with popt on one machine but not on another - so there could
be more to it.

> N:    Severity: serious, Certainty: certain

True.

> 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.

NO! You don't use dpkg-cross except to install the ARM binaries on a
non-ARM box for linking during a cross-build of another package.

For use with emsandbox, you need to put the package into a repository
and use a proxy.

> Afterward emsandbox creates the tarball including our packages.
> Please correct me if I am missing something.

Don't use dpkg-cross on any Emdebian Crush package. It (deliberately)
messes up all the internal paths and configuration of the final package.

-- 


Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

Attachment: pgpWoZexbUKAo.pgp
Description: PGP signature


Reply to: