Adopting Ecasound

Joel Roth joelz at
Mon Jan 31 02:56:37 UTC 2011

On Sun, Jan 30, 2011 at 12:51:15PM +0100, IOhannes m zm??lnig wrote:
> Hash: SHA1
> On 01/30/2011 03:24 AM, Joel Roth wrote:
> > Does someone know what to do with these?
> > 
> > --snip--
> > Now running lintian...
> > W: python-ecasound2.2: executable-not-elf-or-script ./usr/share/pyshared/
> > W: python-ecasound2.2: executable-not-elf-or-script ./usr/share/pyshared/
> > W: python-ecasound2.2: executable-not-elf-or-script ./usr/share/pyshared/
> > W: libecasound-ruby1.8: executable-not-elf-or-script ./usr/lib/ruby/1.8/ecasound.rb
> i strongly suspect that's because these files are missing the shebang.
> try patching the source files to have a
> "#!/usr/bin/python" or a
> "#!/usr/bin/env python"
> at the beginnin (of the python files; use ruby for the .rb file)
> alternatively (and i think that's better) would be to remove the
> executable bit from the files in the installation stage)

Hi IOhannes and all,

As usual, one answer brings up two questions!

First, can you explain how I could "remove the
executable bit in the installation stage"?

Second, when I working on a patch with quilt, I noticed
that two patches were already applied.

In the pkg-perl group (using subversion) the patches
had to be popped before commits, and before building.

Are there any requirements or conventions for the multimedia
team about the patch status (applied or unapplied) when
making commits or when building?

Thanks for any light on this!


> fgmad
> IOhannes
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla -
> iEYEARECAAYFAk1FULMACgkQkX2Xpv6ydvRJ4wCfQsdiaT+DKyEWwedca3jvKqqC
> /jAAoI67OZ+CUAU7vkl0vjHQc/mjVKR6
> =eK99

Joel Roth

More information about the pkg-multimedia-maintainers mailing list