#
# bts-link upstream status pull for source package mplayer
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #576592 (http://bugs.debian.org/576592)
# * http://bugzilla.mplayerhq.hu/show_bug.cgi
On Thu, Apr 29, 2010 at 04:54:43PM +0200, Jonas Smedegaard wrote:
>> I had jackd1 in master/upstream and jackd2 in
>> master.jackd2/upstream.jackd2. Given that we want to re-introduce
>> jackd1, it might be a good idea to fix this (if possible). OTOH, we
>> could create a dedicated jackd1 re
Hi!
I wrote a fix for this bug and forwarded it upstream.
JFTR:
http://trac.jackaudio.org/attachment/ticket/170/jackd2-powerpc.patch
I suggest we wait a few hours for upstream to apply and then update to
current svn version.
--
mail: a...@thur.de http://adi.thur.de PGP/GPG: k
Hi Adrian,
On Thu, Apr 29, 2010 at 04:18:54PM +0200, Adrian Knoth wrote:
It looks like the branches in our jackd repo have been merged. Was this
intended?
Yes, it was intended.
Once upon a time (some weeks ago) we decided to switch from jackd1 to
jackd2, without looking back, i.e. treating
Processing commands for cont...@bugs.debian.org:
> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 579479 + upstream patch
Bug #579479 [jack-audio-connection-kit] jack-audio-connection-kit: FTBFS on
powerpc
Added tag(s) upstream and patch.
>
End of message, stopp
Processing commands for cont...@bugs.debian.org:
> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> forwarded 579479 http://trac.jackaudio.org/ticket/170
Bug #579479 [jack-audio-connection-kit] jack-audio-connection-kit: FTBFS on
powerpc
Set Bug forwarded-to-address to
Hi!
It looks like the branches in our jackd repo have been merged. Was this
intended?
I had jackd1 in master/upstream and jackd2 in
master.jackd2/upstream.jackd2. Given that we want to re-introduce
jackd1, it might be a good idea to fix this (if possible). OTOH, we
could create a dedicated jackd1
I am having the same symptom. Seems to be related to this upstream bug,
which though marked as fixed, appears not to be fixed in SVN as of today
(based on my own testing).
http://sourceforge.net/tracker/?func=detail&aid=2779907&group_id=129766&atid=715780
The suggested workaround, to add to the
