Bug#586728: vlc: Incorrect aspect ratio on initialization
It's possible this bug is identical or related to #528365: vlc: Squashed and greyscale picture with x11 video output I am using Debian sid, and find one solution to be: apt-get install vlc-plugin-sdl vlc -V sdl somevideo.avi This setting can be made permanent in ~/.config/vlc/vlcrc : vout=sdl Note that I have debian-multimedia.org in my /etc/apt/sources.list file. -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Introduction
Hi Multimedia Packaging Wizards and Wizardrettes! I'm a long-time Debian user. I mainly work in perl. I'm author of nama, a text/graphic UI for multitrack recording based on Ecasound, and maintain a couple of CPAN modules. I've got an alioth account, bolangi-guest, and have been involved in the pkg-perl team. I'm interested in seeing that an orphaned-but-useful python app, MMA - Musical Midi Accompaniment, gets updated, hopefully in time to squeeze into squeeze. Current (outdated) package: http://packages.debian.org/lenny/mma Orphan status (missing): http://bugs.debian.org/cgi-bin/pkgreport.cgi?include=subject%3Amma;dist=unstable;package=wnpp Author's Website: http://mellowood.ca/mma/ Look forward to your guidance and assistance. Regards, -- 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: Introduction
On Tue, Jan 04, 2011 at 01:44:19PM +0100, Jonas Smedegaard wrote: > On Mon, Jan 03, 2011 at 06:33:54PM -1000, Joel Roth wrote: > >Hi Multimedia Packaging Wizards and Wizardrettes! > > Welcome, Joel, > > > >I'm a long-time Debian user. I mainly work in perl. I'm author > >of nama, a text/graphic UI for multitrack recording based on > >Ecasound, and maintain a couple of CPAN modules. I've got an > >alioth account, bolangi-guest, and have been involved in the > >pkg-perl team. > > > >I'm interested in seeing that an orphaned-but-useful python app, > >MMA - Musical Midi Accompaniment, gets updated, hopefully in time > >to squeeze into squeeze. > > As I already mentioned at the Perl list, I am interested in helping > out maintaining mma. But I am more hesitant if I am alone on it, > and am ot quite sure what is your intend here: Do you just want to > make us aware of this and encourage us to adopt the mma package, or > (preferrably) want to join this team and get involved yourself > together with those of us interested in this package as well? > > If the latter, then please tell us when you've subscribed to our > mailinglist (so we need not cc you on further discussions), and look > through our guidelines of how our teamwork here is currently > conducted: http://wiki.debian.org/DebianMultimedia Am joined to the lists. Am looking through guidelines. I maintain packages at pkg-perl. I'm familiar with the basics of git, quilt, and the dh scripts, so if someone can help me get started, I will probably be able handle most of the updating. My immediate questions are: 1) The app, mma, is not in your repository. Is that something I can introduce? 2) I seem to recall that a debian package does not include all the files used to create it. If so, is there a source for the original package? (The source code package, perhaps?) Pointer to appropriate references will be welcome. Regards, Joel > Kind regards, and hope to see you join this team, > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private -- 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: Introduction
On Wed, Jan 05, 2011 at 10:02:53AM +0100, Reinhard Tartler wrote: > On Wed, Jan 05, 2011 at 09:21:47 (CET), Joel Roth wrote: > > > Am joined to the lists. > > > > Am looking through guidelines. > > > > I maintain packages at pkg-perl. I'm familiar with the > > basics of git, quilt, and the dh scripts, so if someone can > > help me get started, I will probably be able handle most of > > the updating. > > > In that case, welcome to the team, I've just added you to the team, so > that you have write access to all team repositories and can create new > ones. Thanks! > > My immediate questions are: > > > > 1) The app, mma, is not in your repository. Is that > > something I can introduce? > > sure! > > > 2) I seem to recall that a debian package does not > > include all the files used to create it. If so, > > is there a source for the original package? (The > > source code package, perhaps?) > > I don't understand the question. You claim above that you do maintain > packages with git, quilt and dh scripts in pkg-perl, we do the very same > in pkg-multimedia as well, and create source packages from the git > branches for testing, building and (restricted to DMs and DDs) uploading. I claim some familiarity, *and* occasionally suffer various misconceptions that I hope you will help me right. Best, Joel -- 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: Introduction
On Wed, Jan 05, 2011 at 10:02:53AM +0100, Reinhard Tartler wrote: > On Wed, Jan 05, 2011 at 09:21:47 (CET), Joel Roth wrote: > > 2) I seem to recall that a debian package does not > > include all the files used to create it. If so, > > is there a source for the original package? > > I don't understand the question. Hi Reinhard, I would like to build on previous packaging effort for mma. Clearly, mma couldn't have been packaged without a changelog. Do you know where to find it? I would hope there is another location for these files than the package itself. Mma's package control.tar.gz only contains control md5sums mmadebian postinst prerm For example, a different package I maintain has these files in the debian/ directory. changelog compat control copyright files patches rules source watch So my question is where can I find the original files used to create this debian package? Thanks for your help. Joel -- 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: Introduction
On Mon, Jan 10, 2011 at 09:46:20PM +0100, Jonas Smedegaard wrote: > On Mon, Jan 10, 2011 at 10:03:14AM -1000, Joel Roth wrote: > >I would like to build on previous packaging > >effort for mma. > > > >Clearly, mma couldn't have been packaged without > >a changelog. Do you know where to find it? > > > >I would hope there is another location for these files > >than the package itself. Mma's package control.tar.gz only contains > > > > control > > md5sums > > mmadebian > > postinst > > prerm > > > >For example, a different package I maintain has these > >files in the debian/ directory. > > > > changelog > > compat > > control > > copyright > > files > > patches > > rules > > source > > watch > > > >So my question is where can I find the > >original files used to create this debian package? > > > Sounds like you are confusing upstream and Debian parts No, the above list of files is from a representative package's debian/directory. Those are files I'm looking for for mma > As for your underlying question - how to start working on this > package, based on existing official packaging efforts, here's a > smart oneliner I just discovered to day, which generates a new Git > repository from all officially archived prior releases of a package > (i.e. relevant when the package was not previously maintained in a > VCS): > > git-import-dscs --debsnap --pristine-tar --sign-tags mma > Hope that helps, I tried this. It looks like I have some DNS problems. Can you believe that my ISP doesn't resolve debian subdomains bugs.debian.org or snapshot.debian.org? Best, Joel -- 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: Introduction
On Mon, Jan 10, 2011 at 09:46:20PM +0100, Jonas Smedegaard wrote: > On Mon, Jan 10, 2011 at 10:03:14AM -1000, Joel Roth wrote: > >I would like to build on previous packaging > >effort for mma. > git-import-dscs --debsnap --pristine-tar --sign-tags mma > > Hope that helps, Yes, I succeeded in importing this package. Thanks. Joel -- 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: Adoptiong ecasound
On Thu, Jan 20, 2011 at 07:59:38PM +0100, Alessandro Ghedini wrote: > Hi all, > I've just adopted the bug #520271 (RFA: ecasound2.2), I think it is a good > candidate to get maintained by the Multimedia Team. > > The main problem I see is that the source package is named 'ecasound2.2' > even if the current version is 2.7.0 (2.7.2 if you consider upstream). > >From the README.Debian: > > ecasound2.2 release was a major change from 2.0 series; > and that was the reason for ecasound2.2 package name; we had two > versions to coexist. > > For transition purposes Debian source package name still retains > the ecasound2.2 name. > I think this may lead to confusion and renaming the source package to just > 'ecasound' would make things cleaner and clearer. AFAIK a solution would be > to upload the new 'ecasound' and ask for removal for the 'ecasound2.2'. > Is this right? > > Also, there are a lot of problems with the packaging (e.g. 24 lintian > warnings, "ancient" packaging and a lot of mess with the generated binary > packages) that would probably make easier to re-start packaging from > scratch (this would be made easier by replacing 'ecasound2.2' with > 'ecasound', see above). What do you think? > > Cheers > > P.S. If anyone is interested in helping with this, I'll push everything > to git as soon as I finish initial clean-up. Hi, I think it will be great to clean up and maintain the ecasound source package. I'm no expert in C, but I maintain a couple packages that depend on ecasound, and have an interest in seeing Debian packages being maintained. Regarding the name, the status-quo isn't especially bad. the 2.2 refers to the C library API, which is still current, even tho the ecasound software is up to version 2.7.x. For example, the header file package for using the ecasound C library is called libecasoundc2.2-dev. The python bindings are in python-ecasound2.2. I'll be glad to bring any issues we encounter upstream to developers on the Ecasound mailing list. Joel -- 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 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
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
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: Adoptiong ecasound
On Thu, Jan 20, 2011 at 07:59:38PM +0100, Alessandro Ghedini wrote: > Hi all, > I've just adopted the bug #520271 (RFA: ecasound2.2), I think it is a good > candidate to get maintained by the Multimedia Team. > > The main problem I see is that the source package is named 'ecasound2.2' > even if the current version is 2.7.0 (2.7.2 if you consider upstream). > >From the README.Debian: > > ecasound2.2 release was a major change from 2.0 series; > and that was the reason for ecasound2.2 package name; we had two > versions to coexist. > > For transition purposes Debian source package name still retains > the ecasound2.2 name. > > I think this may lead to confusion and renaming the source package to just > 'ecasound' would make things cleaner and clearer. AFAIK a solution would be > to upload the new 'ecasound' and ask for removal for the 'ecasound2.2'. > Is this right? Having had a look, I agree it would be cleaner for the source package to be named ecasound. And for all the others to be renamed, too. $ grep Package: debian/control Package: ecasound Package: libecasound2.2-dev Package: libecasoundc2.2-dev Package: libkvutils2.2-dev Package: python-ecasound2.2 Package: libecasound-ruby1.8 (??) Package: ecasound-el Here is the output from 'apt-cache showpkg' on my sid distribution. Package: ecasound2.2 Reverse Depends: ecasound,ecasound2.2 2.3.2-1 Package: libecasound2.2-dev Reverse Depends: Package: libecasoundc2.2-dev Reverse Depends: Package: libkvutils2.2-dev Reverse Depends: libecasound2.2-dev,libkvutils2.2-dev Package: python-ecasound2.2 Reverse Depends: ecasound,python-ecasound2.2 2.7.0-1.1 Package: libecasound-ruby1.8 Reverse Depends: All of the packages depending on these packages appear to be within the ecasound source package. Based on this information, it looks like we could go through a renaming without harming others. If we need to be extra-careful, we could use Provides: field to supply aliases to the old package names. Does that seem right? > Also, there are a lot of problems with the packaging (e.g. 24 lintian > warnings, "ancient" packaging and a lot of mess with the generated binary > packages) that would probably make easier to re-start packaging from > scratch (this would be made easier by replacing 'ecasound2.2' with > 'ecasound', see above). What do you think? You must have done a lot since then; there are only a few lintian warnings left. Best, Joel > 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
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: Adoptiong ecasound
On Thu, Jan 20, 2011 at 07:59:38PM +0100, Alessandro Ghedini wrote: > Hi all, > I've just adopted the bug #520271 (RFA: ecasound2.2), I think it is a good > candidate to get maintained by the Multimedia Team. > > The main problem I see is that the source package is named 'ecasound2.2' > even if the current version is 2.7.0 (2.7.2 if you consider upstream). > >From the README.Debian: > > ecasound2.2 release was a major change from 2.0 series; > and that was the reason for ecasound2.2 package name; we had two > versions to coexist. > > For transition purposes Debian source package name still retains > the ecasound2.2 name. > > I think this may lead to confusion and renaming the source package to just > 'ecasound' would make things cleaner and clearer. AFAIK a solution would be > to upload the new 'ecasound' and ask for removal for the 'ecasound2.2'. > Is this right? I haven't see a reply to this. One question I have is about handling bug relationships for all the renamed packages. For example, can a new source package 'ecasound' close bugs submitted against package ecasound2.2? Best, Joel -- 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: Adoptiong ecasound
On Mon, Jan 31, 2011 at 07:04:09AM +0100, Reinhard Tartler wrote: > On Mon, Jan 31, 2011 at 05:10:31 (CET), Joel Roth wrote: > > > One question I have is about handling bug relationships for all the > > renamed packages. > > > > For example, can a new source package 'ecasound' close bugs > > submitted against package ecasound2.2? > > yes, you can accidentally or on purpose close bugs in other packages in > debian/changelog. As soon ecasound2.2 is superseeded, you need to > manually reassign the remaining packages, though. Thanks Reinhard! Okay, so far so good. I have renamed all packages, removing the 2.2 suffix, and the source package builds. The remaining lintian complaints are: Now running lintian... W: ecasound: manpage-has-errors-from-man usr/share/man/man1/ecasound.1.gz 61: warning: numeric expression expected (got `c') E: libecasound-ruby1.8: ruby-script-but-no-ruby-dep ./usr/lib/ruby/1.8/ecasound.rb Finished running lintian. I think I've fixed the error, by modifying the shebang line to ruby1.8 I tried to rename the source package ecasound2.2 -> ecasound. However encountered some error and reverted it. Regards, Joel > -- > Gruesse/greetings, > Reinhard Tartler, KeyID 945348A4 -- 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: Adoptiong ecasound
On Mon, Jan 31, 2011 at 10:14:45AM +0100, IOhannes m zmoelnig wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 2011-01-31 08:53, Joel Roth wrote: > > Now running lintian... > > W: ecasound: manpage-has-errors-from-man > > usr/share/man/man1/ecasound.1.gz 61: warning: numeric expression expected > > (got `c') > > i fixed the remaining errors in the ecasound manpage. > > > E: libecasound-ruby1.8: ruby-script-but-no-ruby-dep > > ./usr/lib/ruby/1.8/ecasound.rb > > Finished running lintian. > > > > I think I've fixed the error, by modifying the shebang line > > to ruby1.8 > > > actually i initially thought it would be better to remove the executable > bits from the scripts (by running something like > $ chmod a+x $(pkgdir)/usr/share/pyshared/pyeca.py > $(pkgdir)/usr/share/pyshared/ecacontrol.py > $(pkgdir)/usr/share/pyshared/eci.py $(pkgdir)/usr/lib/ruby/1.8/ecasound.rb > in the the dh_fixperms section. That does seem neater. > otoh, i guess this would not have pulled in automatic ruby/python > dependencies, as the shebang does. Do the existing shebangs in the ruby/python test scripts accomplish this? > > > > I tried to rename the source package ecasound2.2 -> > > ecasound. However encountered some error and reverted > > it would be interesting to know "some". Reinhard suggests that it might have been due to changing only d/control and not d/changelog. I'll have another go. Cheers, Joel > fgmadf > IOhannes -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Ecasound - largefile support
Hi, I was under the impression that linux and Debian support the largefile option. However when I run ./configure under my sid system, it reports that largefile support is not enabled. checking for largefile support (>2GB files)... checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no Is someone familiar with this issue? Best, Joel -- 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: [SCM] ecasound/master: debian/patches/0003-fix-shebangs.patch: add shebangs to python/ruby code
On Mon, Jan 31, 2011 at 01:31:02PM +0100, Jonas Smedegaard wrote: > On Mon, Jan 31, 2011 at 06:50:43AM +, > bolangi-gu...@users.alioth.debian.org wrote: > > debian/patches/0003-fix-shebangs.patch: add shebangs to python/ruby code > > Don't just blindly add shebangs because lintian complains. > > Is it really executables? > As mentioned by others, it is more likely that these are in fact > _libraries_, not executable, so their executable bit should be unset > instead. Done. (And patch removed.) Joel > > - Jonas -- 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: Introduction
On Mon, Jan 10, 2011 at 09:46:20PM +0100, Jonas Smedegaard wrote: > As for your underlying question - how to start working on this > package, based on existing official packaging efforts, here's a > smart oneliner I just discovered to day, which generates a new Git > repository from all officially archived prior releases of a package > (i.e. relevant when the package was not previously maintained in a > VCS): > > git-import-dscs --debsnap --pristine-tar --sign-tags mma Hi Jonas, This works on my local machine. How would I go about creating the corresponding git repository corresponding to this? git+ssh://git.debian.org/git/pkg-multimedia/mma.git Regards, Joel > Hope that helps, > > - Jonas -- 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: Introduction
On Mon, Jan 31, 2011 at 02:09:50PM -1000, Joel Roth wrote: > On Mon, Jan 10, 2011 at 09:46:20PM +0100, Jonas Smedegaard wrote: > > As for your underlying question - how to start working on this > > package, based on existing official packaging efforts, here's a > > smart oneliner I just discovered to day, which generates a new Git > > repository from all officially archived prior releases of a package > > (i.e. relevant when the package was not previously maintained in a > > VCS): > > > > git-import-dscs --debsnap --pristine-tar --sign-tags mma > > Hi Jonas, > > This works on my local machine. How would I go about > creating the corresponding git repository corresponding > to this? > > git+ssh://git.debian.org/git/pkg-multimedia/mma.git This should be: ssh://git.debian.org/git/pkg-multimedia/mma.git Sufficient details can be found here: http://pkg-perl.alioth.debian.org/git.html Cheers, Joel > > Regards, > > Joel > > > Hope that helps, > > > > - Jonas > -- > Joel Roth > > ___ > 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: Introduction
On Tue, Feb 01, 2011 at 02:34:37AM +0100, Jonas Smedegaard wrote: > On Mon, Jan 31, 2011 at 02:09:50PM -1000, Joel Roth wrote: > >On Mon, Jan 10, 2011 at 09:46:20PM +0100, Jonas Smedegaard wrote: > >>As for your underlying question - how to start working on this > >>package, based on existing official packaging efforts, here's a > >>smart oneliner I just discovered to day, which generates a new > >>Git repository from all officially archived prior releases of a > >>package (i.e. relevant when the package was not previously > >>maintained in a VCS): > >> > >> git-import-dscs --debsnap --pristine-tar --sign-tags mma > > > >Hi Jonas, > > > >This works on my local machine. How would I go about > >creating the corresponding git repository corresponding > >to this? > > > > git+ssh://git.debian.org/git/pkg-multimedia/mma.git > > Since you address me explicitly: > > Sorry, I will not (at the moment, at least) take time to guide you > in detail on the basics of packaging and using Alioth. I am > involved in many exciting projects already, and I might help out > with your needs here too, but don't count on it. > Please read http://wiki.debian.org/DebianMultimedia - and especially > http://wiki.debian.org/DebianMultimedia/DevelopPackaging - and if > you still need help then please do seek it more generally, both at > this list (without addressing me in particular) and at other parts > of the larger Debian community. Thank you. References, as above, are often sufficient guidance. I try to hit them first. In this case, I overlooked the link to that fine documentation. I will honor your request to avoid mentioning your name specifically, except where appropriate to the context. I, too, am excited about the quality of both the software and the packaging made available through the work of the DMT. Regards, Joel > Kind regards, > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > ___ > 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: [SCM] mma packaging annotated tag, upstream/1.7, created. upstream/1.7
Michael and others, I wonder if I made a mistake in merging the upstream version. When I try building this package, I get a huge raft of errors. Could someone see if these are common or readily solved? thanks, Joel -- 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: [SCM] mma packaging annotated tag, upstream/1.7, created. upstream/1.7
On Wed, Feb 02, 2011 at 08:09:44AM +, Miguel Colon wrote: > Hello: > > Assuming you did a gbp-pull and git-buildpackage is configured > correctly it should work. Also when I created the missing tag a while > ago I confirmed that upstream/1.7 contain the correct source when > compared to a tarball I downloaded from upstream and I also merged > upstream/1.7 to master and verified that everything was peachy. So the > git in alioth should be fine. Try doing a gbp-pull or cloning it > again. > > You will get build errors during dh_install since files got renamed. I > could fix them but not sure if you already fixed it all. Thanks Miguel, Looks better. With git-buildpackage, I now get as far as dh_install: dh_installdirs dh_install cp: cannot stat `./mma': No such file or directory The following line in mma.install appears to be at fault. mma usr/bin The executable is actally called mma.py. I'd like to do this: mma.py usr/bin/mma But according to 'man dh_install' the destination must be a directory. Any suggestions? thanks again, Joel -- 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: [SCM] mma packaging annotated tag, upstream/1.7, created. upstream/1.7
On Wed, Feb 02, 2011 at 09:45:50AM +, Miguel Colon wrote: > Hello: > > That should work. Try to pull the commit I just made to make sure. > > It should complain at dh_installchangelogs now. Great. It goes much further. A few lintian warnings remain. W: mma source: changelog-should-mention-nmu W: mma source: source-nmu-has-incorrect-version-number 1.7-1 W: mma source: no-human-maintainers W: mma source: ancient-standards-version 3.7.3 (current is 3.9.1) W: mma: binary-without-manpage usr/bin/mma-gb Will study the patches you made. Regards, Joel > Cheers, > Miguel -- 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 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: [SCM] mma packaging annotated tag, upstream/1.7, created. upstream/1.7
On Wed, Feb 02, 2011 at 08:21:49PM +, Miguel Colon wrote: > Hello: > > Sure, I fixed a few things since I only planned to make 1 commit but > made a mistake since I forgot about the dh_install limitations. > > Anyway since you seem to be doing well on your own now I was gonna > leave it at this but I noticed that you added a new manpage on the > source. When using quilt (3.0) all the changes should be done inside > the debian folder and the source left untouched. You should revert the > commit that adds docs/man/mma-gb.1 and add it as a patch in > debian/patches that creates this file and (if applicable) report it > upstream (this link should give you some info: > http://dep.debian.net/deps/dep3/) . At this point you will probably > also want to add a .gitignore file to ignore the .pc folder. Yes, I forgot that I should be using quilt for that. I'll add the .gitignore, too. Regards, Joel > Cheers, > Miguel > -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Ecasound - getting quilt to pop -a after git-buildpackage
The ecasound package currently requires a manual 'pop -a' after a git-buildpackage before another git-buildpackage is possible. Successive builds are possible by adding dh_quilt_unpatch to the override_dh_auto_clean rule. But that still leaves the package sources with the patch applied. Is there a place to put dh_quilt_unpatch at the *end* of the build process? btw, the debian policy manual is unclear (to me) about whether the 'clean' target cares about the quilt patch queue status. Regards, Joel -- 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: Ecasound - getting quilt to pop -a after git-buildpackage
On Fri, Feb 04, 2011 at 06:37:25AM +0100, Reinhard Tartler wrote: > On Fri, Feb 04, 2011 at 01:21:57 (CET), Joel Roth wrote: > > > The ecasound package currently requires a manual 'pop -a' after > > a git-buildpackage before another git-buildpackage is > > possible. > > > > Successive builds are possible by adding dh_quilt_unpatch to the > > override_dh_auto_clean rule. But that still leaves > > the package sources with the patch applied. > > > > Is there a place to put dh_quilt_unpatch at the *end* > > of the build process? > > > > btw, the debian policy manual is unclear (to me) about whether the > > 'clean' target cares about the quilt patch queue status. > > FYI (and because not everyone was around at that time yet), this is > pretty much why I was against adpoting v3 source package for > pkg-multimedia. The git integration still seems less than ideal to me. > > Joel, it seems that you have to live with manually popping the patches > from the stack, until the integration matures. Thanks for clarifying this. Of course I can easily add a wrapper to handle it; mainly concerned about general practice. From your reply I understand that completed build with patches applied is current behavior. If this is the only problem for quilt 3.0, it doesn't seem like much, at least to my newbie sensibilities. Regards, Joel > > -- > Gruesse/greetings, > Reinhard Tartler, KeyID 945348A4 > > ___ > 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: Ecasound - getting quilt to pop -a after git-buildpackage
On Fri, Feb 04, 2011 at 01:34:35PM +0100, Jonas Smedegaard wrote: > On Fri, Feb 04, 2011 at 06:37:25AM +0100, Reinhard Tartler wrote: > >On Fri, Feb 04, 2011 at 01:21:57 (CET), Joel Roth wrote: > > > >>The ecasound package currently requires a manual 'pop -a' after > >>a git-buildpackage before another git-buildpackage is possible. > >> > >>Successive builds are possible by adding dh_quilt_unpatch to the > >>override_dh_auto_clean rule. But that still leaves the package > >>sources with the patch applied. > >> > >>Is there a place to put dh_quilt_unpatch at the *end* of the > >>build process? > >> > >>btw, the debian policy manual is unclear (to me) about whether > >>the 'clean' target cares about the quilt patch queue status. > > > >FYI (and because not everyone was around at that time yet), this > >is pretty much why I was against adpoting v3 source package for > >pkg-multimedia. The git integration still seems less than ideal to > >me. > > Yes, you _were_ against it earlier on. What is more relevant here, > and surprises me, is that you _still_ find it less than ideal. > > >Joel, it seems that you have to live with manually popping the > >patches from the stack, until the integration matures. > > Since the time of some hesitating and others pushing for source v3, > we have found - I believe - a sane way for source v3 and > git-buildpackage to work reliably together: > > * Add this to debian/source/format: > > 3.0 (quilt) > > * Add this to .gitignore: > > /.pc > > * Add this to debian/source/local-options: > > unapply-patches > abort-on-upstream-changes Can this be added to the docs? > If anyone find this "less than ideal" then please elaborate on why. > > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > ___ > 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: [SCM] ecasound/master: Enable Large File support
On Wed, Feb 09, 2011 at 10:36:18PM +, ghedo-gu...@users.alioth.debian.org wrote: > The following commit has been merged in the master branch: > commit 719ef87d9794d6a3f375efa0d5b269fcd2325044 > Author: Alessandro Ghedini > Date: Wed Feb 9 22:32:50 2011 +0100 > > Enable Large File support > > diff --git a/debian/rules b/debian/rules > index 20bebcf..372d2ce 100755 > --- a/debian/rules > +++ b/debian/rules > @@ -3,6 +3,9 @@ > %: > dh $@ --with autotools-dev > > +override_dh_auto_configure: > + dh_auto_configure -- --enable-largefile We don't need to enable this option: it is default behavior. - commit af792796fe9c3f87690b39a9b531d5ef1b53c0fb Author: Kai Vehmanen Date: Sun Feb 1 23:18:05 2009 +0200 Changed largefile support to be enabled by default if supported by the system. - > override_dh_auto_clean: > mv ecasound.spec ecasound.spec.orig > dh_auto_clean > > -- > ecasound packaging > > ___ > pkg-multimedia-commits mailing list > pkg-multimedia-comm...@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-commits -- 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: [SCM] ecasound/master: Enable Large File support
On Thu, Feb 10, 2011 at 11:17:10AM +0100, Alessandro Ghedini wrote:
> On Wed, Feb 09, 2011 at 03:09:10PM -1000, Joel Roth wrote:
> > We don't need to enable this option: it is default behavior.
>
> I thought so, but I noticed that on my system it gets disabled, after
> running dh_auto_configure I see:
>
>Largefile support: no
>
> It may be a problem with my configuration (I didn't investigate any
> further), but explicitly enabling that option is not a big deal.
You're right, it's not a big deal. FWIW,
when I asked on the Ecasound list, Kai Vehmanen replied that the
option correctly means largefile support for 32bit system.
To avoid future confusion, ideally configure should be patched.
> When I run ./configure under Debian sid, the script
>
> fails to find largefile support.
>
>
>
>checking for largefile support (>2GB files)...
>
>checking for special C compiler options needed for large files... no
>
>checking for _FILE_OFFSET_BITS value needed for large files... no
>
Is this on a 64bit system perhaps? I believe on 64bit systems,
_FILE_OFFSET_BITS has not effect, and then the above checks should be
correct.
So if this is indeed the case, then the things are working as they
should, but ecasound's configure summary is just misleading (it should
say "largefile for 32bit systems...: yes/no".
-
Best,
Joel
>
> Cheers
>
> --
> perl -E'$_=q;$/= @{[@_]};and s;\S+;;eg;say~~reverse'
>
> ___
> 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
debian/copyright
Hi all, I'm working on Ecasound's copyright file. Would like to ask for a review. This project has lots of contributors with different dates in different files. The catchall entry points to the original developer covering all years listed in the project files. Files: * Copyright: 1997-2010 Kai Vehmanen License: GPL-2+ A general review would also help. I wonder if we're about ready to ask for an upload. Thanks, -- 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: debian/copyright
On Tue, Mar 22, 2011 at 08:19:55PM +0100, Jonas Smedegaard wrote: > On Tue, Mar 22, 2011 at 08:29:04AM -1000, Joel Roth wrote: > >I'm working on Ecasound's copyright file. Would like to ask for a > >review. > > > >This project has lots of contributors with different dates in > >different files. > > > >The catchall entry points to the original developer covering all > >years listed in the project files. > > > >Files: * > >Copyright: 1997-2010 Kai Vehmanen > >License: GPL-2+ > > Was there an implicit question somewhere in the above? Not from me. Alessandro, was there something you wanted to ask about? > Regards, > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > ___ > 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
Bug#629871: missing man pages for ecasound-iam, ecatools, ecalength
Package: ecasound Version: 2.8.1-1 Severity: normal No result for 'man' command. According to http://packages.debian.org/sid/amd64/ecasound/filelist There should be man pages in /usr/share/man/man1/ However removing and reinstalling the package, the man files are not present. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36.20101128 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Versions of packages ecasound depends on: ii libasound21.0.23-2.1 shared library for ALSA applicatio ii libaudiofile0 0.2.6-8Open-source version of SGI's audio ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-17 GCC support library ii libjack-jackd2-0 [libjack 1.9.6~dfsg.1-2 JACK Audio Connection Kit (librari ii libkvutils4 2.8.1-1Multitrack-capable audio recorder ii liblo70.26~repack-5 Lightweight OSC library ii libncurses5 5.7+20100313-5 shared libraries for terminal hand ii liboil0.3 0.3.17-2 Library of Optimized Inner Loops ii libreadline6 6.1-3 GNU readline and history libraries ii libsamplerate00.1.7-3Audio sample rate conversion libra ii libsndfile1 1.0.23-1 Library for reading/writing audio ii libstdc++64.6.0-10 The GNU Standard C++ Library v3 ecasound recommends no packages. Versions of packages ecasound suggests: ii amb-plugins [ladspa-plugin] 0.8.1-2 ambisonics LADPSA plugins ii caps [ladspa-plugin]0.4.2-1 C* Audio Plugin Suite ii ladspa-sdk [ladspa-plugin] 1.13-1 sample tools for linux-audio-dev p pn mikmod (no description available) pn mp3-encoder(no description available) ii mpg321 [mp3-decoder]0.2.13-1 Simple and lightweight command lin ii nama1.073-1 Ecasound-based multitrack recorder ii rev-plugins [ladspa-plugin] 0.3.1-1 greverb-like ladspa plugin ii swh-plugins [ladspa-plugin] 0.4.15+1-5 Steve Harris's LADSPA plugins ii tap-plugins [ladspa-plugin] 0.7.1-1 Tom's Audio Processing LADSPA plug ii timidity2.13.2-39+b1 Software sound renderer (MIDI sequ ii vlc [mp3-decoder] 1.1.9-1+b1 multimedia player and streamer ii vlc-nox [mp3-decoder] 1.1.9-1+b1 multimedia player and streamer (wi ii vorbis-tools1.4.0-1 several Ogg Vorbis tools -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#629871: missing man pages for ecasound-iam, ecatools, ecalength
On Thu, Jun 09, 2011 at 10:21:20AM +0200, Alessandro Ghedini wrote:
> On Wed, Jun 08, 2011 at 04:34:42PM -1000, Joel Roth wrote:
> > No result for 'man' command.
> >
> > According to http://packages.debian.org/sid/amd64/ecasound/filelist
> >
> > There should be man pages in /usr/share/man/man1/
> >
> > However removing and reinstalling the package, the man files
> > are not present.
>
> Please note that the ecatools (as well as their manpages) have been moved
> to the 'ecatools' package since version 2.8.0-1, to avoid a circular
> dependency between ecasound and python-ecasound.
> $ dpkg -L ecatools | grep man1
> /usr/share/man/man1/ecalength.1.gz
> /usr/share/man/man1/ecatools.1.gz
> /usr/share/man/man1/ecasound-iam.1.gz
> /usr/share/man/man1/ecasignalview.1.gz
> /usr/share/man/man1/ecanormalize.1.gz
> /usr/share/man/man1/ecamonitor.1.gz
> /usr/share/man/man1/ecafixdc.1.gz
> /usr/share/man/man1/ecaplay.1.gz
> /usr/share/man/man1/ecaconvert.1.gz
That's all good, however the man page for ecasound-iam,
which is necessary to use ecasound interactively, is
in ecatools. I think it should be moved to ecasound.
Finally, someone trying out ecasound may be expecting the
docs and ecatools utilities. These packages are relatively
small. Could they be recommended (so they are pulled in
automatically)? IMO they should be suggested, at least.
> Also, the file list on packages.d.o is quite outdated :)
Good to know, also about dpkg -L.
Thanks again for what has turned out to be a rather complex
packaging job!
> Cheers
>
> --
> perl -E'$_=q;$/= @{[@_]};and s;\S+;;eg;say~~reverse'
--
Joel Roth
--
Joel Roth
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#633815: jackd2: High CPU usage following sleep (top reports 190% on quad-core)
Package: jackd2 Version: 1.9.6~dfsg.1-2 Severity: normal Observed when running jackd with user privileges. System is extremely sluggish until I kill jackd. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36.20101128 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Versions of packages jackd2 depends on: ii coreutils 8.5-1 GNU core utilities ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy ii libasound21.0.23-2.1 shared library for ALSA applicatio ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib ii libcelt0-00.7.1-1The CELT codec runtime library ii libdbus-1-3 1.4.6-1simple interprocess messaging syst ii libexpat1 2.0.1-7XML parsing C library - runtime li ii libgcc1 1:4.4.4-17 GCC support library ii libjack-jackd2-0 1.9.6~dfsg.1-2 JACK Audio Connection Kit (librari ii libncurses5 5.7+20100313-5 shared libraries for terminal hand ii libreadline6 6.1-3 GNU readline and history libraries ii libsamplerate00.1.7-3Audio sample rate conversion libra ii libsndfile1 1.0.23-1 Library for reading/writing audio ii libstdc++64.6.0-10 The GNU Standard C++ Library v3 ii python-dbus 0.83.1-1 simple interprocess messaging syst Versions of packages jackd2 recommends: ii jackd2-firewire 1.9.6~dfsg.1-2 JACK Audio Connection Kit (FFADO a ii libpam-modules1.1.2-2Pluggable Authentication Modules f ii qjackctl 0.3.6-1+b1 User interface for controlling the Versions of packages jackd2 suggests: ii jack-tools0.0.2-7+b1 various JACK tools: plumbing, play ii meterbridge 0.9.2-8+b1 A collection of Audio meters for t -- debconf information: * jackd/tweak_rt_limits: true ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#633815: jackd2: High CPU usage following sleep (top reports 190% on quad-core)
On Thu, Jul 14, 2011 at 07:25:39PM +0200, Adrian Knoth wrote: > On 07/14/11 01:49, Joel Roth wrote: > > Hi! > > > Package: jackd2 > > Version: 1.9.6~dfsg.1-2 > > Severity: normal > > > > Observed when running jackd with user privileges. > > > > System is extremely sluggish until I kill jackd. > > Can we have some numbers, please? > Many people run jackd2 with user privileges, that's actually the > recommended way, and none of them experiences a substantial slowdown. > > So we need to find out what's wrong with your system or particular > setup. > > I suggest a procedure like this: > >0. Update to the current package version >1. Stop jackd (killall -9 jackd, if need be) >2. Start top, htop or another CPU >3. Start jackd -d dummy > > This must not trigger an considerable increase in CPU usage. Then, stop > this jackd and start your real jackd. Which parameters do you use? Which > soundcard is it? 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) A couple of naive attempts with version 1.9.7~dfsg-1 don't show any slowdown. I'll look into this further. My parameters are mostly defaults: jackd -d alsa -d hw:0,0 -r 44100 -H Thanks for your attention. > Increasing the buffer size will ease the timing and hence lower the CPU > load. Assuming you use ALSA: > >$ jackd -d alsa -p 2048 --> relaxed timing >$ jackd -d alsa -p 128 --> stresses the CPU a bit more > > In case of firewire audio interfaces, there has been made a fix recently > that triggered tons of error messages to be printed on the console, thus > making the entire system awfully slow. The newest package has the fix. > > > Cheers -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
MMA package, install targets
Hi Multimedia Maintainers, I've merged the new upstream version 12.01, now trying to get the package to build. Could someone check the install targets in the files below, or point me to some examples/references? Isn't clear which of the following I should be using: debian/mma/usr/bin/executable /usr/bin/executable usr/bin/executable Thanks, Joel debian/rules --- #!/usr/bin/make -f # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 override_dh_install: dh_install cp mma.py /usr/bin/mma cp mma-mnx.py /usr/bin/mma-mnx cp mma-rm2std.py /usr/bin/mma-rm2std cp mma-splitrec.py /usr/bin/mma-splitrec cp mup2mma.py /usr/bin/mup2mma cp pg2mma.py /usr/bin/pg2mma cp synthsplit.py /usr/bin/synthsplit override_dh_installchangelogs: dh_installchangelogs text/CHANGES-1.7 %: dh $@ debian/mma.install -- mma-* usr/bin lib usr/share/mma includes usr/share/mma MMA/*.py usr/share/mma/MMA -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: MMA package, install targets
On Thu, Jan 05, 2012 at 10:12:10AM +0100, Reinhard Tartler wrote: > On Do, Jan 05, 2012 at 08:42:25 (CET), Joel Roth wrote: > > > Hi Multimedia Maintainers, > > > > I've merged the new upstream version 12.01, > > now trying to get the package to build. > > > > Could someone check the install targets in > > the files below, or point me to some > > examples/references? > > > > Isn't clear which of the following I should be using: > > > > debian/mma/usr/bin/executable > > /usr/bin/executable > > usr/bin/executable > > > > I see that mma is a python project. I think you can save yourself and > upstream a *lot* of time and headaches if you would write a proper > setup.py using the standard distutils python package. I'll look into it. Thanks for the pointer. Joel > Cheers, > Reinhard > > -- > Gruesse/greetings, > Reinhard Tartler, KeyID 945348A4 > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers > -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: MMA package, install targets
On Thu, Jan 05, 2012 at 10:12:10AM +0100, Reinhard Tartler wrote: > On Do, Jan 05, 2012 at 08:42:25 (CET), Joel Roth wrote: > > > Hi Multimedia Maintainers, > > > > I've merged the new upstream version 12.01, > > now trying to get the package to build. > > > > Could someone check the install targets in > > the files below, or point me to some > > examples/references? > > > > Isn't clear which of the following I should be using: > > > > debian/mma/usr/bin/executable > > /usr/bin/executable > > usr/bin/executable > > > > I see that mma is a python project. I think you can save yourself and > upstream a *lot* of time and headaches if you would write a proper > setup.py using the standard distutils python package. Hi Reinhard, I've put in some time studying distutils and other modules for this purpose. Writing setup.py seems like the right direction for upstream. For the moment, I have corrected the installation paths in d/mma.install and d/rules. Is commiting dch -r sufficient to signal uploaders to review the package? Thanks, Joel > Cheers, > Reinhard -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: MMA package, install targets
On Tue, Jan 10, 2012 at 10:18:26PM +0100, Reinhard Tartler wrote: > On Di, Jan 10, 2012 at 20:10:55 (CET), Joel Roth wrote: > > > On Thu, Jan 05, 2012 at 10:12:10AM +0100, Reinhard Tartler wrote: > >> On Do, Jan 05, 2012 at 08:42:25 (CET), Joel Roth wrote: > >> > >> > Hi Multimedia Maintainers, > >> > > >> > I've merged the new upstream version 12.01, > >> > now trying to get the package to build. > >> > > >> > Could someone check the install targets in > >> > the files below, or point me to some > >> > examples/references? > >> > > >> > Isn't clear which of the following I should be using: > >> > > >> > debian/mma/usr/bin/executable > >> > /usr/bin/executable > >> > usr/bin/executable > >> > > >> > >> I see that mma is a python project. I think you can save yourself and > >> upstream a *lot* of time and headaches if you would write a proper > >> setup.py using the standard distutils python package. > > > > Hi Reinhard, > > > > I've put in some time studying distutils and other modules > > for this purpose. Writing setup.py seems like the right > > direction for upstream. > > Why not write one right now, use the benefits it brings for the package, > and then ask upstream to integrate your package? I'll need to go through the app and replace all paths with references to sys.prefix. But yes, the app is well organized, and it would be possible to do with quilt, if not upstream. It's slow for me, being new to the language and its conventions. > > For the moment, I have corrected the installation paths in > > d/mma.install and d/rules. > > What you did looks, at least on the first look, correct, but does not > help upstream or other distributors. The app already has install scripts that work on OS X, Windows and Linux, and have been working fine for eight years. > > Is commiting dch -r sufficient to signal uploaders > > to review the package? > > At least I scan PET when I have some spare time: > http://pet.debian.net/pkg-multimedia/pet.cgi > > I notice that the mma package list only you as Uploader. Who else from > the team is going to back you up in case you become unavailable or > otherwise too busy to care for the package? I agree that this another argument to use setup.py I'm all for using standard methods and tools. OTOH, 1. the app is mature, and isn't expected to change much. 2. I'm working with upstream to convert to distutils, and at that point we can easily import a new upstream version with these improvements. 3. I would like to release something usable when that is possible; having done enough to get the package to install, why *not* release? > Also, the package has been removed from unstable for being buggy and > dead upstream. What has changed since September 2010? This needs to be > documented and discussed in a new ITP bug, which is then closed in > debian/changelog (at least IMO). AFAIK, the package never made it to unstable. Since Sept 2010 a new upstream version was released. I imported it into the Debian multimedia git repository. Do I need to open an new ITP bug? Thanks for your attention! Joel > Cheers, > Reinhard > > -- > Gruesse/greetings, > Reinhard Tartler, KeyID 945348A4 -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Python app package data in Debian
Hi all, I'm working on packaging Musical Midi Accompaniment (MMA) for Debian, currently in the Debian Multimedia applications repository. I've been strongly urged to install it using distutils. MMA contains some data files along with the packages. In Pythonland, it seems kosher to install that data with the packages, e.g. using package_data keyword in the call to setup(). Working that way is convenient, as it solves the issue of choosing/accessing appropriate directories under other platforms such as Windows and OS X. What I'm wondering is if this will be a problem WRT Debian Policy. In practical terms it would mean installing some data files under /lib/user/python2.x/mma/ Since Debian users are accustomed to find some package data files under /usr/share/mma I'm wondering if it is kosher to let /usr/share/mma be a link to /lib/user/python2.x/mma/resources. Thanks for your attention. -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: need help /fixing/ WNPP 594784
On Tue, Jan 17, 2012 at 07:14:52PM +0100, Robin Gareus wrote: > Hi *, > > Could you please point me to a short concise walk-though for using > git.debian.org as pkg-multimedia-maintainer? Hi Robin, Here's one: http://wiki.debian.org/Alioth/Git In case you missed it, this page is a useful starting point. http://wiki.debian.org/DebianMultimedia > And/Or tell me how to get a packaged software from github into debian. > I can't seem to find this info on https://alioth.debian.org/ > Specifically, > I am interested to upload: > https://github.com/x42/paulstretch_cpp > > which has an 'upstream' and 'master' branch and produces a lintian clean > debian package with git-buildpackage. > > Shall I simply dput it somewhere (where?) or is it preferred to clone > the git repository to debian.org (how?) Do you need to keep previous history in the new Debian repository? Well, I thought about how to do that, will post if that is an issue. HTH, Joel > > TIA, > robin > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
