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
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
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
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
://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
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
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
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
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
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
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
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
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)
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
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
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
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
17 matches
Mail list logo
