Fw: new message
Hello! You have a new message, please read <http://climberbrasov.ro/honey.php?xx8ch> Andreas Barth ___ 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#756648: Fwd: Bug#756648: mplayer2: add support for ppc64el
Hi Reinhard, * Reinhard Tartler (siret...@gmail.com) [141001 21:14]: > The proposed patch (attached to this email) makes sense to me for > inclusion into your mplayer2.git. Can you incorporate it? this issue is now one of the few remaining uninstallability issues in testing. For this reason it would be nice if you could upload this fix to Debian, even in case it's not yet included in upstream. If useful I'd be happy to help by uploading an NMU. If there is no reason why not, I'd do so next week. Andi ___ 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#755830: opencore-amr: please use dh-autoreconf (fixes ftbfs on ppc64el)
* Fernando Seiti Furusato (ferse...@br.ibm.com) [140830 21:30]: > The package opencore-amr fails to build from source on ppc64el. > Adding the usage of dh-autoreconf to the build fixes that and the > packages builds successfully. I'd be willing to help fixing this bug by uploading an NMU. Actually as about 50 other packages depend on this one being fixed I'd do so in the next days unless there is a reason why not. Andi ___ 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#755111: closed by Sebastian Ramacher (Bug#755111: fixed in lame 3.99.5+repack1-4)
Source: lame Source-Version: 3.99.5+repack1-4 * Andreas Barth (a...@ayous.org) [140830 23:20]: > Control: reopen -1 > > * Debian Bug Tracking System (ow...@bugs.debian.org) [140830 21:19]: > >[ Alessio Treglia ] > >* Build with dh-autoreconf. (Closes: #755111) > > According to the build log it still FTBFS on ppc64el. I will check > what the reason is. I was confused, it actually works. Andi ___ 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#755111: closed by Sebastian Ramacher (Bug#755111: fixed in lame 3.99.5+repack1-4)
Control: reopen -1 * Debian Bug Tracking System (ow...@bugs.debian.org) [140830 21:19]: >[ Alessio Treglia ] >* Build with dh-autoreconf. (Closes: #755111) According to the build log it still FTBFS on ppc64el. I will check what the reason is. Andi ___ 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#748584: ardour3 builds with too many parallel processes
Package: ardour3 Version: 3.5.380~dfsg-1 Severity: serious Hi, the package ardour3 doesn't respect parallel in DEB_BUILD_OPTIONS and builds with as many parallel processes as there are CPUs. This is not so helpful on a 16-core-machine which by purpose runs two buildds in parallel with 6 core per buildd. aba@lucatelli:~$ ps -fu buildd2 | grep cc1plus | wc -l 16 aba@lucatelli:~$ ps -fu buildd2 | grep sbuild buildd2 4534 3316 0 15:28 ?00:00:07 /usr/bin/perl /usr/bin/sbuild --apt-update --no-apt-upgrade --no-apt-distupgrade [...] ardour3_3.5.380~dfsg-1 ba@lucatelli:~$ grep DEB_BUILD ~buildd2/build/current-sid DEB_BUILD_OPTIONS=parallel=6 As per policy, package should not build parallel unless indicated by DEB_BUILD_OPTIONS, and then use that setting (or still not build parallel). Please fix this, this hurts the buildd infrastructure. Andi ___ 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: Please enable libffado on mipsel
* Adrian Knoth (a...@drcomp.erfurt.thur.de) [140223 16:08]: > libffado is currently marked as "not for us" on mipsel, thus preventing > jack-audio-connection-kit from being built. > > Please enable libffado on mipsel. done. Andi ___ 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: RFH: SIGBUS in buildd but not in porterbox
* Felipe Sateler (fsate...@gmail.com) [140217 20:33]: > The package liblo runs a test suite at build time. This test suite > failed in mipsel (but not mips)[1]. I tried to reproduce the issue in > eder.d.o but it passed. > > Liblo does use unaligned access (liblo had to be removed from sparc > for this reason). > But I'm confused as to why does the buildd error out and the porterbox > doesn't. Is it possible to (programatically) instruct the kernel to > not raise a SIGBUS? > > > [1] > https://buildd.debian.org/status/fetch.php?pkg=liblo&arch=mipsel&ver=0.28-3&stamp=1392064303 rem and eder are different hardware. Also are you sure your package builds with /bin/sh=bash (just asking because I have seen that issue with another package recently)? Andi ___ 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: Libav 0.7 FTBFS on mipsel: Error: opcode not supported on this processor: mips2 (mips2) `ldl $2, 7($13)'
* Kurt Roeckx (k...@roeckx.be) [110724 15:30]: > /usr/sbin/sbuild-createchroot has: I use /usr/share/sbuild/create-chroot.sh (which is actually the one doing it right for lvm-type chroots), and that does it for mips*, sparc, s390, powerpc. Andi ___ 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: Libav 0.7 FTBFS on mipsel: Error: opcode not supported on this processor: mips2 (mips2) `ldl $2, 7($13)'
* Aurelien Jarno (aurel...@aurel32.net) [110723 23:17]: > On Wed, Jul 20, 2011 at 08:52:45PM +0200, Philipp Kern wrote: > > [ mips* buildds Cc'ed ] > > > > On Tue, Jul 19, 2011 at 09:58:34PM +0200, David Kuehling wrote: > > > The complete userspace *is* o32, just the kernel is not. I think that > > > is a pretty valid way to run a system, compiling the kernel for mips64 > > > gives better performance on those machines that can run mips64 code. > > > > > > A mips64 kernel can run 32 and 64-bit architecture binaries, and has to > > > pick one description when asked via 'uname -m'. The 'setarch' tool can > > > be used to configure which architecture that is. > > > > > > I.e. athough my machine usually returns 'mips64' on 'uname -m', after > > > running, 'setarch mips' it returns just 'mips'. Maybe that'd be a a > > > cleaner way to fix the problem for all package builds? > > > > I think that's a misconfiguration of the buildds. They're supposed to > > put linux32 into the schroot configuration if the kernel arch differs > > from the userspace arch, to get the right entry into uname. > > It should be fixed right now, but it would be nice to have that in > create-chroot.sh as otherwise we might forget next time we create a > chroot or setup a machine. Should be there since commit efb72d2f7ac7bc33470167ffdc74532306f1d58f Author: Andreas Barth Date: Sun Apr 18 20:49:09 2010 +0200 Andi ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
