Bug#667653: mpg123 FTBFS on armhf
I pulled that change into another 1.13 release, it is a bit different from your patch. Could you (peter?) test http://mpg123.org/download/mpg123-1.13.8.tar.bz2 if it builds now? I'll make it officialy public, then. Final report. I tested it with: --with-cpu=neon + -marm = WORKS --with-cpu=neon + -mthumb = WORKS --with-cpu=arm_nofpu + -marm= WORKS --with-cpu=arm_nofpu + -mthumb = WORKS Seems that using the new LSL notation was not needed and the old MOV with inline shift still work in this case. Regards, Miguel ___ 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#667653: mpg123 FTBFS on armhf
As mpg123 upstream it would be cool to get note of such issues without having to look for them in the debian bts. Having some bot subscribe and post to mpg123-de...@lists.sourceforge.net would be splendit; but if that is too troublesome, sending an info to maintai...@mpg123.org would be just as fine (using the generic address in case I vanish in future). But perhaps I overlooked a generic way to subscribe an address to all future reports. Hello: I have not tried it myself but I think this is what you are asking for: http://www.debian.org/doc/manuals/developers-reference/resources.html#pkg-tracking-system Section 4.10.1 explains the subscribe and the keyword options. I would filter out some of them since it would be too verbose IMO. Second: There is no inline assembly in mpg123. The file at hand (layer3.c) is plain C all around. So, without further data, I must assume that this is a bug in gcc that is worked around by adding -marm. You might consider asking gcc folks about this. I had some free time so I looked into this. The armhf architecture defaults to -mthumb instead of -marm and: 1) --with-cpu=arm_nofpu it fails with -mthumb and works with -marm (-DOPT_ARM -DREAL_IS_FIXED) 2) --with-cpu=neon it works with both. (-DOPT_NEON -DREAL_IS_FLOAT) This lead me to believe that it was most likely related to -DOPT_ARM. I saw that layer3.c includes #include mpg123lib_intern.h and that in that file there is a block: # elif defined(OPT_ARM) /* for arm */ # define REAL_MUL_ASM(x, y, radix) \ snip I patched this file by basically doing -# elif defined(OPT_ARM) +# elif defined(OxPT_ARxM) Without the patch it FTBFS but with the patch it builds. Looking at the ASM code it seems that these 2 asm block use PRE-UAL ARM syntax which only work in ARM and not thumb. The newer UAL syntax works with both. Here is a link that mentions some of the changes: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0204j/Cjagjjbc.html Attached is a patch to really fix this and the orr problem with a header inside the patch explaining the changes. Using -marm was really a workaround to hide the problem but not a real solution to this and disabled all the advantages of using -mthumb. Reference for thumb2 instructions: http://infocenter.arm.com/help/topic/com.arm.doc.qrc0001m/QRC0001_UAL.pdf Hope this helps, Miguel 0005-thumbs2.patch Description: Binary data ___ 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#664998: Too much CPU used
I cannot reproduce that on my personal box. I have a Duron at 800 MHz with debian squeeze on it. Running mpg123 -v needs around 1% of CPU! There must be something else going on. Also please note that nowadays, the audio output happily gobbles up way more CPU than mpg123 needs. An example is the ALSA library resampling 44100 Hz material to 48000 Hz. Can you produce a profile of your CPU-consuming mpg123 (using the perf tool, for example)? Hello Santiago: One of the upstream authors replied to your bug report but forgot to CC you. This is email is just to relay the message. Cheers, Miguel ___ 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: [SCM] mpg123/master: Add -marm to CFLAGS to fix FTBFS on armhf.
Add -marm to CFLAGS to fix FTBFS on armhf. Closes: #667658 Thanks: peter green for the patch. Hello: I already had fixed this FTBFS by adding this: ifeq ($(ARCH),armhf) CONF_arm:=--with-cpu=neon CFLAGS += -mfpu=neon endif This also added the optimizations that you wanted the package to build with earlier but had FTBFS since Debian uses -mfpu=vfpv3-d16 by default. The patch was only needed if --with-cpu=arm_nofpu since the git branch before the patch did not FTBFS. If the idea was to be able to build with the current default --with-cpu=neon OR with a user selected --with-cpu=arm_nofpu then it could have been added inside the current IF as CFLAGS += -mfpu=neon -marm instead of adding another IF check. Cheers, Miguel ___ 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: [SCM] mpg123/master: Pass --with-cpu=arm_nofpu to configure for armhf too.
On Sun, Apr 1, 2012 at 4:26 AM, ales...@users.alioth.debian.org wrote: The following commit has been merged in the master branch: commit 726c947f2edde84a0a86ed972cb61a5e669501b7 Author: Alessio Treglia ales...@debian.org Date: Sun Apr 1 10:25:41 2012 +0200 Pass --with-cpu=arm_nofpu to configure for armhf too. diff --git a/debian/rules b/debian/rules index bc8a8cd..9f82935 100755 --- a/debian/rules +++ b/debian/rules @@ -17,13 +17,7 @@ CONF_COMMON:=--enable-static=no --enable-shared --enable-lfs-alias \ --with-module-suffix=.so CONF_i486:=--with-cpu=x86_dither -ifeq ($(ARCH),armel) CONF_arm:=--with-cpu=arm_nofpu -else -ifeq ($(ARCH),armhf) -CONF_arm:=--with-cpu=neon -endif -endif SOVERSION:=0 LIB_PKG:=libmpg123-$(SOVERSION) -- mpg123 packaging ___ pkg-multimedia-commits mailing list pkg-multimedia-comm...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-commits Hello: To make this work you could have done: ifeq ($(ARCH),armhf) CONF_arm:=--with-cpu=neon CFLAGS += -mfpu=neon endif and moved ___ 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: [SCM] mpg123/master: Pass --with-cpu=arm_nofpu to configure for armhf too.
Hello: To make this work you could have done: ifeq ($(ARCH),armhf) CONF_arm:=--with-cpu=neon CFLAGS += -mfpu=neon endif and moved (Not sure why the email got sent before I was done.) CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS) CFLAGS:=$(shell dpkg-buildflags --get CFLAGS) CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS) LDFLAGS:=$(shell dpkg-buildflags --get LDFLAGS) to the top or at least above the if statement. I had made the change really quick but did not commit it since I wanted to test it first with qemu first but by the time I finished I had fallen asleep (took way longer to make qemu work than to compile, heh). Anyway reverting the optimization or adding the -mfpu flag works. - Miguel ___ 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#664967: Segfaulting is caused by copyObject in version 0.12.1-3
Hello: I managed to reproduce the segfaults and I believe I just fixed this in the version available in the git repository. If you want, you can try to compile it and report if it fixed your issue. The following or something similar should work for building the packages: sudo apt-get install git git clone git://anonscm.debian.org/pkg-multimedia/mediatomb.git sudo apt-get build-dep mediatomb cd mediatomb sed -i s/(0.12.1-4)/(0.12.1-4~local1)/g debian/changelog dpkg-buildpackage -b cd .. sudo dpkg -i mediatomb_*_all.deb mediatomb-common_*.deb mediatomb-daemon_*_all.deb Hope this helps, Miguel ___ 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#635321: Unable to reproduce with soundtouch 1.6.0-1 or 1.6.0-2
Hello: Today I tried to reproduce this bug but I could not do it. I also could not find a change in soundtouch BPM routines from 1.5.0 to 1.6.0 that could have caused it. Here is a log of what I did but I cut out some of the verbose: $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-2 $ sudo apt-get install banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.0.1-4+b2 $ banshee [Info 21:06:18.659] Running Banshee 2.0.1: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-28 13:30:52 UTC] snip $ sudo apt-get install -t experimental banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 $ banshee [Info 21:07:13.017] Running Banshee 2.1.3: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-25 13:36:14 BST] snip $ rm -rf ~/.config/banshee-1/ I went to http://snapshot.debian.org/package/soundtouch/1.6.0-1/#libsoundtouch0_1.6.0-1 and installed the 1.6.0-1 as originally reported. $ sudo dpkg -i libsoundtouch0_1.6.0-1_amd64.deb $ sudo apt-get install banshee/sid -qq $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.0.1-4+b2 $ banshee [Info 21:08:58.164] Running Banshee 2.0.1: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-28 13:30:52 UTC] snip $ sudo apt-get install -t experimental banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 $ banshee [Info 21:09:59.268] Running Banshee 2.1.3: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-25 13:36:14 BST] snip $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 Both soundtouch 1.6.0-1 and 1.6.0-2 worked fine with Banshee from sid and experimental. For a final test I tried the version that was originally reported: $ rm -rf ~/.config/banshee-1/ $ sudo dpkg -i libgdata1.7-cil_1.7.0.1-1_all.deb banshee_2.1.0-1_amd64.deb libmtp8_1.0.6-7_amd64.deb $ banshee [Info 21:32:02.028] Running Banshee 2.1.0: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-05-17 11:03:27 UTC] snip $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.1.0-1 So the current 2.0.1, the reported 2.1.0-1 and the current version from experimental seem to work with a current and up to date system. I guess that there was a different package that caused the original crash and that package got updated again and the original issue was resolved. If the original submitter could confirm it would help. Hope this helps, Miguel ___ 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#615269: audacity: Dependency conflict on installation on libsoundtouch
On Sat, Feb 26, 2011 at 5:12 PM, Benjamin Drung bdr...@debian.org wrote: reassign 615269 libsoundtouch0 1.5.0-3 thanks Am Samstag, den 26.02.2011, 17:07 +0100 schrieb Daniel Andersson: I don't know if it's Pidgin, Audacity or libsoundtouch that should be contacted, but I asked on #debian and someone suggested Audacity. The problem lies in soundtouch. libsoundtouch0 conflicts with libsoundtouch1c2, but these two package should be installable side-by-side. I'm not really sure what happened but I guess gst-plugins-bad0.10 (and others) were supposed to get updated or gotten a sourceful NMU and never did. Since otherwise this would have happened when moving the package from experimental. I commited some changes to git that should close this by letting libsoundtouch1c2 and libsoundtouch0 be installable side by side. This line which has all the affected packages now works (assuming the user never removed libsoundtouch1c2 and libsoundtouch1-dev for OCAML): sudo apt-get install ardour djplay mixxx audacity freecycle gstreamer0.10-plugins-bad ihu yatm libsoundtouch-ocaml libsoundtouch-ocaml-dev liquidsoap This should help fix this mess until all the BinNMU/NMU/Regular uploads get eventually done. Hopefully the git version gets approved and uploaded soon. Cheers, Miguel ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#615141: libsoundtouch0: conflicts with gstreamer-plugins-bad libpurple/pidgin
Hello: A possible fix has been commited to git. Waiting for it to get approved and uploaded. Cheers, Miguel ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#613677: slv2: Please recompile against versioned redland
Hey all: Just a FYI. Bug #613673 already got fixed/closed. Not sure if there is any other holdup. Cheers, Miguel ___ 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
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. Cheers, Miguel On Wed, Feb 2, 2011 at 7:53 AM, Joel Roth jo...@pobox.com wrote: 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 ___ 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
Hello: That should work. Try to pull the commit I just made to make sure. It should complain at dh_installchangelogs now. Cheers, Miguel On Wed, Feb 2, 2011 at 9:16 AM, Joel Roth jo...@pobox.com wrote: 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 ___ 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
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. Cheers, Miguel On Wed, Feb 2, 2011 at 5:44 PM, Joel Roth jo...@pobox.com wrote: 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 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Libsoundtouch{0,1}-dev?
So looks like a transition to me, and we probably need to readjust ardour's build dependency (to libsoundtouch-dev). I can take care of this if agreed upon. Hello, yes it's a transition I was the one that made renamed it. Perhaps Alessio wants to provide further clarification. Last time I spoke with Alessio about it from what I understood and remember he was waiting for post-squeeze. But better to wait for an official response since I might have misunderstood. Ardour (perhaps among others) build-depends on libsoundtouch1-dev, but this is not built by the archive as soundtouch provides libsoundtouch-dev but not libsoundtouch1-dev. Is this just a typo in soundtouch packaging, or do we have a more serious problem? The source packages affected are: Package: ardour Package: audacity Package: djplay Package: freecycle Package: gst-plugins-bad0.10 Package: ihu Package: ocaml-soundtouch Package: rezound Package: yatm In addition: - liquidsoap just needs to be rebuilt whenever ocaml-soundtouch get updated since it depends on libsoundtouch-ocaml-dev and not libsoundtouch directly. - mixx just needs to be rebuilt since it depends on libsoundtouch-dev so it should be fine after a binary upload or something. I basically got this information by adding sid/experimental source repos to the source.list and doing: grep-dctrl -FBuild-Depends libsoundtouch -sPackage /var/lib/apt/lists/*Sources | sort | uniq and confirming with apt-cache rdepends (not sure if there was a better way or if doing it with these 2 commands is not exhaustive enough) I locally recompiled all the packages in a clean chroot when I made the initial rename and what I just posted are my notes from that time. Also, from what I wrote down, all packages except ocaml-soundtouch and liquidsoap worked with just renaming the build dependency but as luck would have it ardour is the only package that I forgot to document the changes I made to it so it would build. Finally I remember Alessio uploading a new version of audacity and freecycle to experimental using the renamed library so the transition on those 2 I assume is done or started. Hope I made some sense. Cheers, Miguel ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Introduction
Heh, thank y'all. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Introduction
Hello Multimedia Team: I was working on updating the soundtouch package that was orphaned some time ago. I uploaded it to mentors.debian.net and Alessio Treglia was kind enough to sponsor it. I'm interested on joining the team so I can continue maintaining this package and possibly help on others. I have an alioth account micove-guest and already subscribed to both mailing list as instructed in the http://wiki.debian.org/DebianMultimedia/Join page. I also have experience using debhelper/quilt and always build on a clean chroot using pbuilder. I also have read the debian policy / debian's new maintainers guide / debian's developer reference / DEP-3 guidelines / DEP-5 guidelines / etc. I don't have much experience using git besides downloading from projects using clone/checkout/pull but I will read http://wiki.debian.org/PackagingWithGit and other sources to get a better hang on it. Look forward to your guidance and assistance. Regards, - Miguel Colon ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
