Bug#806301: RFS: libechonest/2.3.1-0.1 [NMU] -- library for communicating with The Echo Nest platform

[Gianfranco Costamagna <costamagnagianfranco@yahoo.it>]

Hi Stefan,

The best thing about open source is

that when you have a problem you sleep a

little and when you wake up somebody fixed

it for you :)

https://launchpadlibrarian.net/229562183/libechonest_2.3.1-0.1_2.3.1-0.1ubuntu1.diff.gz

you can apply this debdiff and copy the files for the other Debian architecture that have failed (alpha kfreebsd-amd64 mips64el ppc64 sparc64)

I can probably try sh4 in a porterbox if needed (and if a porterbox is available).

Otherwise if have a way to mark the architectures inside or the symbols as optional I guess it will be fine anyway 

Cheers

G 

Sent from Yahoo Mail on Android

On Wed, 9 Dec, 2015 at 23:09, Stefan Ahlers

<stef.ahlers@t-online.de> wrote:

Hi,

> Built&Signed&Uploaded, don't forget next time to put a link to where
the original maintainer
> acked the upload, and also you can consider using -1 as Debian
revision, and maybe add a
> "Team Upload" (dch --team), if the maintainer is aware of the changes

Thank you for signing and uploding! I read the article about
"Non-maintainer upload" (https://wiki.debian.org/NonMaintainerUpload)
and I thought it is correct to use -0.1.

> Now Stefan as soon as the package is accepted you will need to fix the
build failures (if any), and ask for a rebuild binNMU of the reverse
dependencies

I asked for a rebuild (#807509). I hope this is the correct way.

It looks like some 64bit-based builds failed
(https://buildd.debian.org/status/package.php?p=libechonest) because of
incorrect symbol files. There are six symbols, which are different on
32bit and 64bit platforms.

What is the best way of writing the symbol files? One file for every
architecture or is there a way to combine this in one or two symbol files?

Kind regards,

Stefan Ahlers