Re: Adopting Ecasound
On Wed, Feb 02, 2011 at 04:45:19PM +0100, Alessandro Ghedini wrote: > Hello, > sorry for the late reply, I'm currently on vacation and Internet > connectivity is quite unreliable (I also don't have my PC). Thanks for dropping by! :-) > On Sun, Jan 30, 2011 at 03:24, Joel Roth wrote: > > TODO says: > > > >> * Fix Python module > > > > Builds without errors. > > That wasn't the problem. I have no exprience in Python modules > packaging, so I'm not sure it is the right way to do it (even if it > builds). > > >> * Maybe build shared libecasound, libecasoundc, libkvutils > > > > they all appear to build > > They are built statically. Since this is not a good thing we should > make them build "dynamically" and add some new packages (e.g. > libecasound2 libecasoundc2 and libkvutils2). I'll have a look at this > when I'll be back home. > > >> * ... > > > > What about large file support? Does anyone know what the dependencies are? > > This seems a good idea to me. I asked on the ecasound list. Apparently we don't need to do anything special to support large files. On amd64 systems (which I tested on) there is no problem, although the ./configure output is misleading. Someone should still probabaly test under a 32-bit system. Meanwhile, enjoy :-) :-) Best, Joel > Cheers > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Adopting Ecasound
Hello, sorry for the late reply, I'm currently on vacation and Internet connectivity is quite unreliable (I also don't have my PC). On Sun, Jan 30, 2011 at 03:24, Joel Roth wrote: > TODO says: > >> * Fix Python module > > Builds without errors. That wasn't the problem. I have no exprience in Python modules packaging, so I'm not sure it is the right way to do it (even if it builds). >> * Maybe build shared libecasound, libecasoundc, libkvutils > > they all appear to build They are built statically. Since this is not a good thing we should make them build "dynamically" and add some new packages (e.g. libecasound2 libecasoundc2 and libkvutils2). I'll have a look at this when I'll be back home. >> * ... > > What about large file support? Does anyone know what the dependencies are? This seems a good idea to me. Cheers ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Adopting Ecasound
On Sun, Jan 30, 2011 at 04:56:37PM -1000, Joel Roth wrote: > Second, when I working on a patch with quilt, I noticed > that two patches were already applied. Answering myself, that was mistaken. However for some reason I needed the -f flag to unapply, and after that the series applies and unapplies fine. It's easy to see if patches are applied, because git-diff suddenly shows a zillion changes! Cheers -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Adopting Ecasound
On Sun, Jan 30, 2011 at 12:51:15PM +0100, IOhannes m zm??lnig wrote: > -BEGIN PGP SIGNED MESSAGE- > 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/pyeca.py > > W: python-ecasound2.2: executable-not-elf-or-script > > ./usr/share/pyshared/ecacontrol.py > > W: python-ecasound2.2: executable-not-elf-or-script > > ./usr/share/pyshared/eci.py > > 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! Joel > fgmad > IOhannes > > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk1FULMACgkQkX2Xpv6ydvRJ4wCfQsdiaT+DKyEWwedca3jvKqqC > /jAAoI67OZ+CUAU7vkl0vjHQc/mjVKR6 > =eK99 > -END PGP SIGNATURE- -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Adopting Ecasound
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/30/2011 03:24 AM, Joel Roth wrote: > Alessandro and others, > > > Does someone know what to do with these? > > --snip-- > Now running lintian... > W: python-ecasound2.2: executable-not-elf-or-script > ./usr/share/pyshared/pyeca.py > W: python-ecasound2.2: executable-not-elf-or-script > ./usr/share/pyshared/ecacontrol.py > W: python-ecasound2.2: executable-not-elf-or-script > ./usr/share/pyshared/eci.py > 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) fgmad IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1FULMACgkQkX2Xpv6ydvRJ4wCfQsdiaT+DKyEWwedca3jvKqqC /jAAoI67OZ+CUAU7vkl0vjHQc/mjVKR6 =eK99 -END PGP SIGNATURE- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Adopting Ecasound
Alessandro and others, I tried building the package today. TODO says: > * Fix Python module Builds without errors. > * Fix debian/copyright (needs to be updated) Done > * Clean lintian errors/warnings/... Does someone know what to do with these? --snip-- Now running lintian... W: ecasound: manpage-has-errors-from-man usr/share/man/man1/ecasound.1.gz 61: warning: numeric expression expected (got `c') W: python-ecasound2.2: executable-not-elf-or-script ./usr/share/pyshared/pyeca.py W: python-ecasound2.2: executable-not-elf-or-script ./usr/share/pyshared/ecacontrol.py W: python-ecasound2.2: executable-not-elf-or-script ./usr/share/pyshared/eci.py W: libecasound-ruby1.8: executable-not-elf-or-script ./usr/lib/ruby/1.8/ecasound.rb Finished running lintian. --snip-- > * Maybe build shared libecasound, libecasoundc, libkvutils they all appear to build > * ... What about large file support? Does anyone know what the dependencies are? Regards, Joel ./configure script output: - Following packages are now configured: ecasound: yes (ecasound,libecasound,libecasoundc) ecatools: yes pyecasound: yes (as Python C extension module) rubyecasound: yes libkvutils: yes - Compiler options: CFLAGS: -ffast-math -fstrict-aliasing -DNDEBUG -DENABLE_DBC -g -O2 CXXFLAGS:-ffast-math -fstrict-aliasing -DNDEBUG -DENABLE_DBC -g -O2 CPPFLAGS:-D_REENTRANT -D_XOPEN_SOURCE=500 LDFLAGS: - Following features were selected: Debugging info: no Effects enabled:yes Largefile support: no Termcap:ncurses Use system readline:yes Use curses interface: yes Libaudiofile: yes Libsndfile: yes ALSA support: yes OSS support:yes aRts support: yes JACK support: no Libsamplerate support yes Liboil support: yes Liblo (OSC) support:yes - Following directories are used: Directory prefix: /usr/local Python include dir: /usr/include/python2.6 Python module dir: /usr/lib/python2.6 Ruby module dir: Extra headers: -I/usr/include/kde/artsc -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/liboil-0.3 Extra libs: -L/usr/lib -lartsc -lsamplerate -laudiofile -lsndfile -lasound -loil-0.3 -lm -lrt -llo -lpthread -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Adopting ecasound
On Thu, Jan 27, 2011 at 09:11:12AM +0100, IOhannes m zmoelnig wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 2011-01-27 02:29, Joel Roth wrote: > > On Tue, Jan 25, 2011 at 04:10:48PM +0100, Alessandro Ghedini wrote: > >> If you want to help, whatever help you can provide is welcome. > >> > >> Have a look at the debian/TODO file [0] to see what needs to be done. > > > > Hi everyone, > > > > Sure this is a FAQ, but a cursory search of the wiki didn't > > turn anything up. > > > > I've updated debian/copyright. > > > > Can someone direct me to docs on how to push to the > > repository or standard procedure to submit a patch? > > > > My .git/config file (produced by git-clone) currently looks like this: > > go to: > http://git.debian.org/?p=pkg-multimedia/ecasound.git;a=summary > and look for "URL". > > (hint: you need an account on alioth which you can access via ssh) Thanks, IOhannes the git+ssh URL works fine. Joel > fgamsdr Sounds friendly! What language is that? > IOhannes > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk1BKKAACgkQkX2Xpv6ydvR1pwCeLDyI6PHr8yTFjTeBgXYP4B9Q > 6rcAoI0+7NJ3wjCwmn4uBrNWhPpcqBUa > =h35h > -END PGP SIGNATURE- > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Adopting ecasound
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-01-27 02:29, Joel Roth wrote: > On Tue, Jan 25, 2011 at 04:10:48PM +0100, Alessandro Ghedini wrote: >> If you want to help, whatever help you can provide is welcome. >> >> Have a look at the debian/TODO file [0] to see what needs to be done. > > Hi everyone, > > Sure this is a FAQ, but a cursory search of the wiki didn't > turn anything up. > > I've updated debian/copyright. > > Can someone direct me to docs on how to push to the > repository or standard procedure to submit a patch? > > My .git/config file (produced by git-clone) currently looks like this: go to: http://git.debian.org/?p=pkg-multimedia/ecasound.git;a=summary and look for "URL". (hint: you need an account on alioth which you can access via ssh) fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1BKKAACgkQkX2Xpv6ydvR1pwCeLDyI6PHr8yTFjTeBgXYP4B9Q 6rcAoI0+7NJ3wjCwmn4uBrNWhPpcqBUa =h35h -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Adopting ecasound
On Tue, Jan 25, 2011 at 04:10:48PM +0100, Alessandro Ghedini wrote: > If you want to help, whatever help you can provide is welcome. > > Have a look at the debian/TODO file [0] to see what needs to be done. Hi everyone, Sure this is a FAQ, but a cursory search of the wiki didn't turn anything up. I've updated debian/copyright. Can someone direct me to docs on how to push to the repository or standard procedure to submit a patch? My .git/config file (produced by git-clone) currently looks like this: [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = http://git.debian.org/git/pkg-multimedia/ecasound.git [branch "master"] remote = origin merge = refs/heads/master I've tried https:// and git:// URLs at random. Regards, Joel > [0] > http://git.debian.org/?p=pkg-multimedia/ecasound.git;a=blob;f=debian/TODO;h=98c19f390c57619c117966a3f3fbb7e2414783d8;hb=HEAD -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
