Bug#831369: audacity: In LADSPA effect settings, sliders cannot handle negative integers

2016-07-14 Thread Kyanos
Package: audacity
Version: 2.1.2-1+b1
Severity: minor

Dear Maintainer,

In the settings window for LADSPA effects, the sliders do not move to
negative integers. If, for example, an integer option ranges from -3 to
3 (inclusive), the slider will only move within one half of the bar.

What is interesting is that negative values can still be entered
manually, and the slider will even move to the appropriate position in
the negative part! But trying to adjust the slider will cause it to jump
back to the 0 position.

Also, the lower-bound label for the slider is incorrect when negative
integers are involved: It is one greater than the true lower bound. So,
if the range were from -3 to 3, the lower-bound label would be -2.
However, the slider seems to behave as if the lower bound is correct.

I first discovered these issues while using Tom Baran's Autotalent
plugin (packaged as "autotalent"), so that may be used to reproduce
these issues. I have also attached a test plugin which may help.

Thank you for your consideration.

Kyanos

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (300, 'oldstable-updates'), (300,
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages audacity depends on:
ii  audacity-data   2.1.2-1
ii  libasound2  1.1.1-2
ii  libavcodec577:3.0.2-4
ii  libavformat57   7:3.0.2-4
ii  libavutil55 7:3.0.2-4
ii  libc6   2.23-1
ii  libexpat1   2.2.0-1
ii  libflac++6v51.3.1-4
ii  libflac81.3.1-4
ii  libgcc1 1:6.1.1-9
ii  libgdk-pixbuf2.0-0  2.34.0-1
ii  libglib2.0-02.48.1-1
ii  libgtk2.0-0 2.24.30-2
ii  libid3tag0  0.15.1b-11
ii  liblilv-0-0 0.22.0~dfsg0-1
ii  libmad0 0.15.1b-8
ii  libmp3lame0 3.99.5+repack1-9+b1
ii  libogg0 1.3.2-1
ii  libportaudio2   19+svn20140130-1
ii  libportsmf0 0.1~svn20101010-4
ii  libsbsms10  2.0.2-1
ii  libsndfile1 1.0.25-10
ii  libsoundtouch1  1.9.2-2
ii  libsoxr00.1.2-1
ii  libstdc++6  6.1.1-9
ii  libsuil-0-0 0.8.2~dfsg0-1
ii  libtwolame0 0.3.13-1.2
ii  libvamp-hostsdk3v5  2.6~repack0-2
ii  libvorbis0a 1.3.5-3
ii  libvorbisenc2   1.3.5-3
ii  libvorbisfile3  1.3.5-3
ii  libwxbase3.0-0v53.0.2+dfsg-1.4
ii  libwxgtk3.0-0v5 3.0.2+dfsg-1.4

audacity recommends no packages.

Versions of packages audacity suggests:
ii  autotalent [ladspa-plugin]   0.2-5
ii  caps [ladspa-plugin] 0.9.24-2
ii  ladspa-sdk [ladspa-plugin]   1.13-2+b1
ii  swh-plugins [ladspa-plugin]  0.4.16+git20160602~repack1-2
ii  tap-plugins [ladspa-plugin]  0.7.3-1

-- no debconf information
#include 
#include 
#include 

/*
 * This is a LADSPA plugin that merely copies the audio input to the output.
 * The primary purpose of this plugin is to test hosts' handling of control
 * inputs.
 *
 * To the extent possible under law, Kyanos has waived all copyright and
 * related or neighboring rights to this work, using Creative Commons
 * CC0 1.0 Universal. For more information, please visit:
 * https://creativecommons.org/publicdomain/zero/1.0/
 */

/* Port count (1 audio in, 1 audio out, 1 control in) */
#define LT_PORTS_COUNT 3

/* Port numbers */
#define LT_PORT_AUDIO_IN 0
#define LT_PORT_AUDIO_OUT 1
#define LT_PORT_CONTROL_IN 2

typedef struct lt_instance_s {
	LADSPA_Data* connections[LT_PORTS_COUNT];
} lt_instance;

const LADSPA_PortDescriptor lt_port_descs[] = {
	LADSPA_PORT_AUDIO | LADSPA_PORT_INPUT,
	LADSPA_PORT_AUDIO | LADSPA_PORT_OUTPUT,
	LADSPA_PORT_CONTROL | LADSPA_PORT_INPUT,
};
const char* lt_port_names[] = {
	"Audio In",
	"Audio Out",
	"Test Option",
};
const LADSPA_PortRangeHint lt_port_range_hints[] = {
	/* Dummy hints for audio ports */
	{0, 0, 0},
	{0, 0, 0},
	/* Hints for control port */
	{
		LADSPA_HINT_BOUNDED_BELOW | LADSPA_HINT_BOUNDED_ABOVE
			| LADSPA_HINT_INTEGER | LADSPA_HINT_DEFAULT_0
		,
		-0.1,
		3.1
	},
};

LADSPA_Handle lt_instantiate(
	const struct _LADSPA_Descriptor * Descriptor, unsigned long SampleRate
);

void lt_connect_port(
	LADSPA_Handle Instance, unsigned long Port, LADSPA_Data * DataLocation
);

void lt_run(LADSPA_Handle Instance, unsigned long SampleCount);

void lt_cleanup(LADSPA_Handle Instance);

/* Descriptor for this plugin */
const LADSPA_Descriptor lt_descriptor = {
	/*
	 * Unique ID.
	 *
	 * "Plugin IDs 1-1000 are reserved for development use"
	 * (LADSPA SDK documentation)
	 */
	1,

	/* Label */
	"ladspatest",

	/* Properties */
	LADSPA_PROPERTY_REALTIME | LADSPA_PROPERTY_HARD_RT_CAPABLE,

	/* Name */
	"LADSPA Test Plugin",

	/* Maker */
	"Kyanos ",

	/* Copyright */
	"Public Domain (CC0 1.0 Universal)",

	/* Port count (1 audio 

Re: musescore 2.0.3+dfsg-1

2016-07-14 Thread Fabian Greffrath
Hi again,

Am Donnerstag, den 14.07.2016, 17:18 +0100 schrieb Peter Jonas:
> Freetype is included because not included for convenience. It is
> included because MuseScore's code has been tailored towards a
> specific
> version of Freetype and other versions of Freetype have been known to
> cause problems in the past.

hm, I still don't really buy this argument. Some more thoughts on this
matter:

1) Debian Policy should always have top-priority for decisions to be
made regarding software that is maintained in Debian. If "but upstream
may complain" is reason enough to grant an exception from Debian
Policy, then we may sooner or later end up with more exceptions than
rules.

2) We should ask ourselves *why* upstream is embedding libfreetype. If
they want the best font rendering result for their users, please feel
certain that Debian wants to achieve the same result with its own
library package. I don't see why musescore is so much more tied to a
specific font rendering library version than other more complex
applications. And if it is, this somehow tastes like bad practice.

3) We should ask ourselves *what* upstream is actually embedding. If
they are embedding a pristine copy of libfreetype, I don't see any
problem with using Debian's version either. If they are embedding a
modified version with non-upstreamed changes, they are actually
creating a fork. Are we as the pkg-multimedia team in a position to
maingain a fork of a library such as freetype for the sole purpose of
being used in one single package?

Also, please keep in mind that for some time especially freetype could
have been used to sneek in potentially patented font rendering code
paths -- although I am not saying that this is happening here or has
ever happened at all.

Cheers,

 - Fabian


signature.asc
Description: This is a digitally signed message part
___
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: modifying libva (master) .gitignore

2016-07-14 Thread Nicholas D Steeves
On 8 July 2016 at 04:33, Sebastian Ramacher  wrote:
> On 2016-07-06 16:17:09, Nicholas D Steeves wrote:
>> Hi Sebastian,
>>
>> On 5 July 2016 at 05:30, Sebastian Ramacher  wrote:
>> >
>> > On 2016-07-04 14:54:17, Nicholas D Steeves wrote:
>> >> I ran into an issue with backporting libva.  Is it ok if I add the
>> >> following to libva (master) .gitignore?:
>> >>
>> >> debian.upstream/changelog
>> >> debian.upstream/control
>> >
>> > How will this change affect gbp import-orig since these files come from the
>> > upstream tarball?
>> >
>> > I usually use --git-ignore-new and cases where I really need gbp 
>> > buildpackage.
>> >
>>
>> From what I understand of that page, and what I understand of the
>> build process, it should be safe and desirable to prevent the
>> debian.upstream/* from being imported into (master), because we use
>> the ones in the (master) libva/debian.  Debian.upstream should
>> probably still be imported into the (upstream) branch.
>>
>> Today I a tested a variety of approaches in combination with gbp
>> import-orig, and it seems like this simple .gitignore solution might
>> not be viable.  For example, adding debian.upstream to .gitignore and
...
> I think it's overly complicated for something that can simply be solved by 
> using
> --git-ignore-new when using gbp buildpackage or patching the upstream build
> system to not include debian.upstream/Makefile.am. I'll probably add a patch 
> for
> the latter.

It seems I spoke too soon wrt my last email.  Currently, libva still
wants to run make in debian.upstream.  What I find strange is that
outright removing the debian.upstream dir didn't cause the following
build failures:

checkout f57b4ed747be83f72a4c6b72a845011ef6c35ce6
  * I then removed the debian.upstream directory, and commited the changes
  * It built just fine for sid and for jessie-backports (gbp)

checkout dbb99e381206508d213797dbe1214a8f04368333
  * build fails (gbp) with

make[5]: Nothing to be done for 'all-am'.
make[5]: Leaving directory '/build/libva-1.7.1/test'
make[4]: Leaving directory '/build/libva-1.7.1/test'
Making all in debian.upstream
make[4]: Entering directory '/build/libva-1.7.1/debian.upstream'
make[4]: *** No rule to make target 'all'.  Stop.
make[4]: Leaving directory '/build/libva-1.7.1/debian.upstream'
Makefile:465: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/build/libva-1.7.1'
Makefile:397: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/build/libva-1.7.1'
dh_auto_build: make -j1 returned exit code 2
debian/rules:20: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/libva-1.7.1'
debian/rules:14: recipe for target 'build' failed
make: *** [build] Error 2

checkout 3836579b289964afe57ed3986693d1b882b74efb
  * build fails for the same reason

checkout 22796dd3c4cf90c44e27ca74692fdad127b545e5
  * build fails for the same reason

Cheers,
Nicholas

___
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: musescore 2.0.3+dfsg-1

2016-07-14 Thread Jonas Smedegaard
[replying only to list, as per mailingst policy]

Quoting Peter Jonas (2016-07-14 18:18:56)
> As Tiago said the policy is a guideline,

Agreed.  But a strong recommendation: For starters, each inclusion of an 
embedded code copy is burden on the security team!


> but I don't believe it applies here anyway. The policy defines 
> convenience copies as dependencies included "so that users compiling 
> from source don't have to download multiple packages". It goes on to 
> say that the policy does not apply when "the included package is 
> explicitly intended to be used in this way."
> 
> Freetype is included because not included for convenience. It is 
> included because MuseScore's code has been tailored towards a specific 
> version of Freetype and other versions of Freetype have been known to 
> cause problems in the past.

I believe it does apply here: What Policy mentions as reason for not 
avoiding embedded code copies is if the _library_ is intended to be used 
that way - not if the consuming project intended to do so (arguably it 
is always intentional).

Freetype has had quite a few bugs in the past, but fixating to a "known 
working release" is *not* the solution, as that only hides the problems 
- something we explicitly promise not to do in Debian.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature
___
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: musescore 2.0.3+dfsg-1

2016-07-14 Thread Peter Jonas
Hi Fabian,

As Tiago said the policy is a guideline, but I don't believe it
applies here anyway. The policy defines convenience copies as
dependencies included "so that users compiling from source don't have
to download multiple packages". It goes on to say that the policy does
not apply when "the included package is explicitly intended to be used
in this way."

Freetype is included because not included for convenience. It is
included because MuseScore's code has been tailored towards a specific
version of Freetype and other versions of Freetype have been known to
cause problems in the past.

Best,
Peter

On 14 July 2016 at 17:11, Tiago Bortoletto Vaz  wrote:
> Hi,
>
> On Thu, Jul 14, 2016 at 05:58:08PM +0200, Fabian Greffrath wrote:
>> Hi there,
>>
>> Am Donnerstag, den 14.07.2016, 11:18 -0400 schrieb Tiago Bortoletto
>> Vaz:
>> > lot! I agree with Peter about Freetype inclusion. I've had a not so
>> > good
>> > experience on reporting issues to upstreams when using a slightly
>> > modified version of MuseScore. So, for the sake of piece I'd just
>> > keep
>>
>> sorry, but I have to disagree. Debian has a policy and that explicitely
>> discourages embedding convenience library copies in §4.13:
>>
>> https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles
>
> You're right, but I see it mostly as a recommendation, which can be
> eventually bypassed on special situations:
>
> "Non-conformance with guidelines denoted by should (or recommended) will
> generally be considered a bug, but will not necessarily render a package
> unsuitable for distribution."
> (https://www.debian.org/doc/debian-policy/ch-scope.html)
>
> Anycase, as I said, I don't know details about this need, and I don't
> know how MuseScore would be affected in Debian if we use our freetype
> packages. I'm just trusting the upstreams (whom I've been working with
> for some time). But as I don't have much time now to go into the issue,
> I'll be fine with any decision from the team.
>
> Bests,
>
> --
> tiago

___
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: musescore 2.0.3+dfsg-1

2016-07-14 Thread Tiago Bortoletto Vaz
Hi,

On Thu, Jul 14, 2016 at 05:58:08PM +0200, Fabian Greffrath wrote:
> Hi there,
> 
> Am Donnerstag, den 14.07.2016, 11:18 -0400 schrieb Tiago Bortoletto
> Vaz:
> > lot! I agree with Peter about Freetype inclusion. I've had a not so
> > good
> > experience on reporting issues to upstreams when using a slightly
> > modified version of MuseScore. So, for the sake of piece I'd just
> > keep
> 
> sorry, but I have to disagree. Debian has a policy and that explicitely
> discourages embedding convenience library copies in §4.13:
> 
> https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles

You're right, but I see it mostly as a recommendation, which can be
eventually bypassed on special situations:

"Non-conformance with guidelines denoted by should (or recommended) will
generally be considered a bug, but will not necessarily render a package
unsuitable for distribution."
(https://www.debian.org/doc/debian-policy/ch-scope.html)

Anycase, as I said, I don't know details about this need, and I don't
know how MuseScore would be affected in Debian if we use our freetype
packages. I'm just trusting the upstreams (whom I've been working with
for some time). But as I don't have much time now to go into the issue,
I'll be fine with any decision from the team.

Bests,

-- 
tiago

___
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: musescore 2.0.3+dfsg-1

2016-07-14 Thread Fabian Greffrath
Hi there,

Am Donnerstag, den 14.07.2016, 11:18 -0400 schrieb Tiago Bortoletto
Vaz:
> lot! I agree with Peter about Freetype inclusion. I've had a not so
> good
> experience on reporting issues to upstreams when using a slightly
> modified version of MuseScore. So, for the sake of piece I'd just
> keep

sorry, but I have to disagree. Debian has a policy and that explicitely
discourages embedding convenience library copies in §4.13:

https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles

 - Fabian


signature.asc
Description: This is a digitally signed message part
___
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: musescore 2.0.3+dfsg-1

2016-07-14 Thread Tiago Bortoletto Vaz
Hi James, Peter,

The package has been really improved from previews version, thanks a
lot! I agree with Peter about Freetype inclusion. I've had a not so good
experience on reporting issues to upstreams when using a slightly
modified version of MuseScore. So, for the sake of piece I'd just keep
it, also believing there's a good reason for that, even I don't know the
details.

Bests,

On Thu, Jul 14, 2016 at 02:56:46PM +0100, Peter Jonas wrote:
> Hi James,
> 
> Many thanks for these changes!
> 
> They all look good to me, except for the patch to exclude Freetype
> which upstream will not be too happy about. Upstream includes Freetype
> intentionally to ensure that font rendering is consistent across
> operating systems. Prior to 2.0.3 MuseScore relied on the system's
> Freetype but this gave results that were inconsistent across different
> systems and fixing kerning issues on one platform would break it on
> another. Of course, if excluding Freetype is an *absolute requirement*
> for inclusion in Debian then MuseScore will of course comply, but I
> know that upstream would *much prefer* to include their own Freetype.
> See 
> https://musescore.org/en/developers-handbook/release-notes/release-notes-musescore-2.0.3#known-incompatibilities
> 
> The other patches will all be welcome upstream. (OpenSSL is only
> needed for the Windows build.)
> 
> Best wishes,
> Peter
> 
> On 14 July 2016 at 13:27, James Cowgill  wrote:
> > Hi,
> >
> > I've made some changes to the musescore packaging which I've pushed to
> > git. Since I have not worked on musescore before and these changes are
> > quite big, it would be good if someone could comment on them before I
> > upload it.
> >
> > If noone replies I'll probably go ahead and upload it in a day or so.
> >
> > https://anonscm.debian.org/cgit/pkg-multimedia/musescore.git
> >
> > Thanks,
> > James

-- 
tiago

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Processed: Re: pyliblo: Build not reliable

2016-07-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 819842 pyliblo: Build not reliable
Bug #819842 [src:pyliblo] pyliblo: FTBFS when built with dpkg-buildpackage -A 
(test suite fails)
Changed Bug title to 'pyliblo: Build not reliable' from 'pyliblo: FTBFS when 
built with dpkg-buildpackage -A (test suite fails)'.
> severity 819842 normal
Bug #819842 [src:pyliblo] pyliblo: Build not reliable
Severity set to 'normal' from 'important'
> user sanv...@debian.org
Setting user to sanv...@debian.org (was sanv...@unex.es).
> usertags 819842 - binary-indep
Usertags were: binary-indep.
Usertags are now: .
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
819842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
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#819842: pyliblo: Build not reliable

2016-07-14 Thread Santiago Vila
retitle 819842 pyliblo: Build not reliable
severity 819842 normal
user sanv...@debian.org
usertags 819842 - binary-indep
thanks

I have both successful and unsuccessful build logs for this package.
All of them for version 0.10.0-1.

Status: successful  pyliblo_0.10.0-1_amd64-20160225-2103
Status: successful  pyliblo_0.10.0-1_amd64-20160227-1325
Status: successful  pyliblo_0.10.0-1_amd64-20160313-1519
Status: attempted   pyliblo_0.10.0-1_amd64-20160402-0031
Status: attempted   pyliblo_0.10.0-1_amd64-20160402-1951
Status: attempted   pyliblo_0.10.0-1_amd64-20160402-2012
Status: attempted   pyliblo_0.10.0-1_amd64-20160402-2024
Status: attempted   pyliblo_0.10.0-1_amd64-20160521-1427
Status: successful  pyliblo_0.10.0-1_amd64-20160621-2143

This bug needs to be investigated, but it does not seem to be the
typical binary-indep bug so I'm removing it from my list of
binary-indep bugs for now.

Thanks.

___
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: musescore 2.0.3+dfsg-1

2016-07-14 Thread Peter Jonas
Hi James,

Many thanks for these changes!

They all look good to me, except for the patch to exclude Freetype
which upstream will not be too happy about. Upstream includes Freetype
intentionally to ensure that font rendering is consistent across
operating systems. Prior to 2.0.3 MuseScore relied on the system's
Freetype but this gave results that were inconsistent across different
systems and fixing kerning issues on one platform would break it on
another. Of course, if excluding Freetype is an *absolute requirement*
for inclusion in Debian then MuseScore will of course comply, but I
know that upstream would *much prefer* to include their own Freetype.
See 
https://musescore.org/en/developers-handbook/release-notes/release-notes-musescore-2.0.3#known-incompatibilities

The other patches will all be welcome upstream. (OpenSSL is only
needed for the Windows build.)

Best wishes,
Peter

On 14 July 2016 at 13:27, James Cowgill  wrote:
> Hi,
>
> I've made some changes to the musescore packaging which I've pushed to
> git. Since I have not worked on musescore before and these changes are
> quite big, it would be good if someone could comment on them before I
> upload it.
>
> If noone replies I'll probably go ahead and upload it in a day or so.
>
> https://anonscm.debian.org/cgit/pkg-multimedia/musescore.git
>
> Thanks,
> James

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


musescore 2.0.3+dfsg-1

2016-07-14 Thread James Cowgill
Hi,

I've made some changes to the musescore packaging which I've pushed to
git. Since I have not worked on musescore before and these changes are
quite big, it would be good if someone could comment on them before I
upload it.

If noone replies I'll probably go ahead and upload it in a day or so.

https://anonscm.debian.org/cgit/pkg-multimedia/musescore.git

Thanks,
James

signature.asc
Description: This is a digitally signed message part
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

FW:

2016-07-14 Thread Trinity Jones
Your RSA Email has won R1.75M and a trip to Brazil to watch the 2016 Rio 
Olympic Games with Ref: BRZ/SA/01/08/16. Contact; cla...@vavosascofirm.co.za or 
00447937349377. T's and C's apply!




___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Processed: reassign 830715 to src:musescore, forcibly merging 824956 830715

2016-07-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 830715 src:musescore 2.0.2+dfsg-2
Bug #830715 [musescore] musescore not installable
Bug reassigned from package 'musescore' to 'src:musescore'.
No longer marked as found in versions musescore/2.0.2+dfsg-2.
Ignoring request to alter fixed versions of bug #830715 to the same values 
previously set
Bug #830715 [src:musescore] musescore not installable
Marked as found in versions musescore/2.0.2+dfsg-2.
> forcemerge 824956 830715
Bug #824956 [src:musescore] QtQuick1 will be removed from the archive with Qt 
5.6
Bug #830715 [src:musescore] musescore not installable
Severity set to 'serious' from 'normal'
827194 was blocked by: 824956 824959
827194 was not blocking any bugs.
Added blocking bug(s) of 827194: 830715
Added tag(s) pending.
Merged 824956 830715
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
824956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824956
827194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827194
830715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
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#831246: bs1770gain: FTBFS: ffsox_audiostream.c:50:5: error: 'codec' is deprecated [-Werror=deprecated-declarations]

2016-07-14 Thread Lucas Nussbaum
Source: bs1770gain
Version: 0.4.9-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -I../libpbutil 
> -I../lib1770-2  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Werror -Wall -Wformat -Wpointer-arith -Wcast-align 
> -Wcast-qual -Wreturn-type -Wextra -Wstrict-prototypes -c ffsox_audiostream.c
> ffsox_audiostream.c: In function 'ffsox_audiostream':
> ffsox_audiostream.c:50:5: error: 'codec' is deprecated 
> [-Werror=deprecated-declarations]
>  cc=fc->streams[i]->codec;
>  ^
> In file included from ./ffsox_dynload.h:25:0,
>  from ./ffsox.h:23,
>  from ffsox_audiostream.c:20:
> /usr/include/x86_64-linux-gnu/libavformat/avformat.h:880:21: note: declared 
> here
>  AVCodecContext *codec;
>  ^
> cc1: all warnings being treated as errors
> make[3]: *** [ffsox_audiostream.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/14/bs1770gain_0.4.9-1_unstable_gcc5.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


mixxx_2.0.0~dfsg-4~bpo8+1_amd64.changes ACCEPTED into jessie-backports, jessie-backports

2016-07-14 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 08 Jul 2016 22:08:29 +0200
Source: mixxx
Binary: mixxx mixxx-data
Architecture: source amd64 all
Version: 2.0.0~dfsg-4~bpo8+1
Distribution: jessie-backports
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Matteo F. Vescovi 
Description:
 mixxx  - Digital Disc Jockey Interface
 mixxx-data - Digital Disc Jockey Interface -- data files
Closes: 820805
Changes:
 mixxx (2.0.0~dfsg-4~bpo8+1) jessie-backports; urgency=medium
 .
   * Rebuild for jessie-backports.
 .
 mixxx (2.0.0~dfsg-4) unstable; urgency=medium
 .
   [ Sebastian Ramacher ]
   * Import manpage changes from upstream
 .
   [ Alessio Treglia ]
   * Remove myself from the Uploaders list
 .
   [ Matteo F. Vescovi ]
   * debian/control:
 - libqt4-sql-sqlite dependency re-added
   for binary package (Closes: #820805)
 - S-V bump 3.9.6 -> 3.9.7 (no changes needed)
Checksums-Sha1:
 7ae342da46b7c20d341ebac789199e233ae30ba0 2836 mixxx_2.0.0~dfsg-4~bpo8+1.dsc
 68163a8ac5bf936a3aa560c8a861439ade22bec1 16736 
mixxx_2.0.0~dfsg-4~bpo8+1.debian.tar.xz
 6378aade56126bd05b2e35a805b6ff0624e4b1ac 4801998 
mixxx_2.0.0~dfsg-4~bpo8+1_amd64.deb
 2c1491070459e2404b709786f1f842b6ee25bd58 1742020 
mixxx-data_2.0.0~dfsg-4~bpo8+1_all.deb
Checksums-Sha256:
 9f001bef0ee048322065f4daa13f5c8f14a57e6b9dc9b7fb1b2b00472b24f631 2836 
mixxx_2.0.0~dfsg-4~bpo8+1.dsc
 162574593e10b2ddfe986e0dadd482f8e25380baba3a9be8bb2d74479ef0c965 16736 
mixxx_2.0.0~dfsg-4~bpo8+1.debian.tar.xz
 d1f05bd12eaf678e5c8aae64886403fc2cff1065fd8bb9320a12f5b3137ab5e7 4801998 
mixxx_2.0.0~dfsg-4~bpo8+1_amd64.deb
 b31d7eeb708be217bc8ba430c0808eef23e5d8bb0449fc46fefd6f14b9809c3a 1742020 
mixxx-data_2.0.0~dfsg-4~bpo8+1_all.deb
Files:
 8c7e91d19cc664154fb8ae3834089bc3 2836 sound optional 
mixxx_2.0.0~dfsg-4~bpo8+1.dsc
 b357563100d7b81aee729f65f2bcf68b 16736 sound optional 
mixxx_2.0.0~dfsg-4~bpo8+1.debian.tar.xz
 18c3661e361f0fce1f984159041d1e23 4801998 sound optional 
mixxx_2.0.0~dfsg-4~bpo8+1_amd64.deb
 e9d094858127ddcd1849a7eb3a0597f0 1742020 sound optional 
mixxx-data_2.0.0~dfsg-4~bpo8+1_all.deb

-BEGIN PGP SIGNATURE-
Comment: Debian powered!

iQJ8BAEBCgBmBQJXhLU5XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGM0REMDlGOERBODdEMURGNTA0NkM5OUIw
NjEyRjQ5NDRFQ0RDRDVBAAoJEAYS9JROzc1aKLgP/0jPZ7icCJoJQJ1r0vKzUqtu
lQ2UbzHvPw6tu7hiq/+qLrQEGYSexr06NsioE8dt2gDZ55y/r1NkX1uiVn7vv+kp
J8XedoTHD+I4MopkoEqEM7InQu8mbqEx8AfSe5figju01iUg7AyAtoQ5c2KA8BeQ
GJ2Es+Y3n3gI4O69L3ZCVTcNiQPvx56//Vgqrnciwfdu6xqEEPGPF25LN75CCqOh
/CUEYJAs7OL4lVWVYAdGENMtFSaQFFbPl+uA5CYUuAAUJm3uz9JOQqH4qvENjE7H
zIu0E6SttV41mvoqVnWl6R/KL9SjS39qCyEzdiqVkDYksmkBykZ1JEyWp/ZsC+ZN
oT4zimA6YxLyZLRQezDMXrbyF6oMcVX3TQymXxQJzUG+jjf8JrdZlL4YVhXiDsiF
TnzDscVqmkejWf3yYnD3/ZI3PghDRitcLXEXAFSLo/PsufdaKgQnPKWHNFecessh
EJxFfRbxqBSwmhSI/axjgEl3PZc7PY2ZckHP/9S/Daq2VEds9LF3V309lDBmsMFI
5CMsbb1/JgEhhave/L17EUMv37Z+hTVTagd+xlJra2IBW8eDhzBp+4FZ3FOSGLpR
PeYDH0tEcZceNdQQ1ECGaM8F7F7LPO3W4cYmO7odJ1IAD2C6EYQNUAQtc1RpLxHz
aKJhH43eIT7nYq1iSBaB
=itkO
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
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#831183: giada: FTBFS with GCC 6: src/core/recorder.cpp:654:2: error: this 'if' clause does not guard... [-Werror=misleading-indentation]

2016-07-14 Thread Lucas Nussbaum
Source: giada
Version: 0.12.2~dfsg1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -DPACKAGE_NAME=\"giada\" -DPACKAGE_TARNAME=\"giada\" 
> -DPACKAGE_VERSION=\"0.12\" -DPACKAGE_STRING=\"giada\ 0.12\" 
> -DPACKAGE_BUGREPORT=\"giadaloopmach...@gmail.com\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"giada\" -DVERSION=\"0.12\" -DHAVE_LIBPTHREAD=1 -DSTDC_HEADERS=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_UNISTD_H=1 -I.   -D__UNIX_JACK__ -D__LINUX_ALSA__ -Wdate-time 
> -D_FORTIFY_SOURCE=2 -DBUILD_DATE='"2016/07/04"' -std=c++11 -Wall -Werror 
> -Wno-error=vla  -g -O2 -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -std=c++11 -c -o src/core/giada-recorder.o `test -f 
> 'src/core/recorder.cpp' || echo './'`src/core/recorder.cpp
> src/core/recorder.cpp: In function 'void recorder::stopOverdub(int)':
> src/core/recorder.cpp:654:2: error: this 'if' clause does not guard... 
> [-Werror=misleading-indentation]
>   if (!nullLoop)
>   ^~
> src/core/recorder.cpp:656:3: note: ...this statement, but the latter is 
> misleadingly indented as if it is guarded by the 'if'
>deleteActions(cmp.a2.chan, cmp.a1.frame, cmp.a2.frame, cmp.a2.type);
>^
> cc1plus: all warnings being treated as errors
> make[1]: *** [src/core/giada-recorder.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/giada_0.12.2~dfsg1-2_unstable_gcc6.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#831185: rumor: FTBFS with GCC 6: notator.cc:337:43: error: call of overloaded 'abs(unsigned int)' is ambiguous

2016-07-14 Thread Lucas Nussbaum
Source: rumor
Version: 1.0.5-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I..   -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -D_REENTRANT -pthread -I/usr/include/guile/2.0 -ggdb3 
> -O0 -Wall -pedantic -c -o notator.o notator.cc
> notator.cc: In member function 'std::__cxx11::string Notator::PitchName(int, 
> bool)':
> notator.cc:337:43: error: call of overloaded 'abs(unsigned int)' is ambiguous
>NumTics=(abs(RefPitch_wt-AbsPitch_wt)+3)/7;
>^
> In file included from /usr/include/c++/6/cstdlib:75:0,
>  from /usr/include/c++/6/ext/string_conversions.h:41,
>  from /usr/include/c++/6/bits/basic_string.h:5402,
>  from /usr/include/c++/6/string:52,
>  from /usr/include/c++/6/bits/locale_classes.h:40,
>  from /usr/include/c++/6/bits/ios_base.h:41,
>  from /usr/include/c++/6/ios:42,
>  from /usr/include/c++/6/ostream:38,
>  from /usr/include/c++/6/iostream:39,
>  from rumor.hh:14,
>  from notator.cc:8:
> /usr/include/stdlib.h:774:12: note: candidate: int abs(int)
>  extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
> ^~~
> In file included from /usr/include/c++/6/ext/string_conversions.h:41:0,
>  from /usr/include/c++/6/bits/basic_string.h:5402,
>  from /usr/include/c++/6/string:52,
>  from /usr/include/c++/6/bits/locale_classes.h:40,
>  from /usr/include/c++/6/bits/ios_base.h:41,
>  from /usr/include/c++/6/ios:42,
>  from /usr/include/c++/6/ostream:38,
>  from /usr/include/c++/6/iostream:39,
>  from rumor.hh:14,
>  from notator.cc:8:
> /usr/include/c++/6/cstdlib:185:3: note: candidate: __int128 std::abs(__int128)
>abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
>^~~
> /usr/include/c++/6/cstdlib:180:3: note: candidate: long long int 
> std::abs(long long int)
>abs(long long __x) { return __builtin_llabs (__x); }
>^~~
> /usr/include/c++/6/cstdlib:172:3: note: candidate: long int std::abs(long int)
>abs(long __i) { return __builtin_labs(__i); }
>^~~
> make[4]: *** [notator.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/rumor_1.0.5-2_unstable_gcc6.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#831170: qjackctl: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory

2016-07-14 Thread Lucas Nussbaum
Source: qjackctl
Version: 0.4.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -c -m64 -pipe -Wall -g -O2 -std=gnu++0x -Wall -W -D_REENTRANT -fPIC 
> -DDATADIR="/usr/share" -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB 
> -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. -I. -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/local/include -isystem 
> /usr/include -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I.ui 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o .obj/qjackctl.o 
> qjackctl.cpp
> In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
>  from /usr/include/c++/6/algorithm:62,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:88,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:37,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:41,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:40,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qsettings.h:37,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QSettings:1,
>  from qjackctlConnectAlias.h:25,
>  from qjackctlSetup.h:25,
>  from qjackctl.cpp:23:
> /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or 
> directory
>  #include_next 
>  ^
> compilation terminated.
> make[3]: *** [.obj/qjackctl.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/qjackctl_0.4.2-1_unstable_gcc6.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#831141: qmidinet: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory

2016-07-14 Thread Lucas Nussbaum
Source: qmidinet
Version: 0.4.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -c -m64 -pipe -g -O2 -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -std=gnu++0x -Wall 
> -W -D_REENTRANT -fPIC -DDATADIR="/usr/share" -DQT_WIDGETS_LIB -DQT_GUI_LIB 
> -DQT_CORE_LIB -I. -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/local/include -isystem /usr/include -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I.ui 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o .obj/qmidinet.o 
> qmidinet.cpp
> In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
>  from /usr/include/c++/6/algorithm:62,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:88,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:37,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:41,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:40,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1,
>  from qmidinetUdpDevice.h:34,
>  from qmidinet.h:25,
>  from qmidinet.cpp:22:
> /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or 
> directory
>  #include_next 
>  ^
> compilation terminated.
> make[3]: *** [.obj/qmidinet.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/qmidinet_0.4.0-1_unstable_gcc6.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#831137: kodi: FTBFS with GCC 6: stl_algobase.h:243:56: error: macro "min" passed 3 arguments, but takes just 2

2016-07-14 Thread Lucas Nussbaum
Source: kodi
Version: 16.1+dfsg1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> make[3]: Entering directory 
> '/«BUILDDIR»/kodi-16.1+dfsg1/lib/cximage-6.0/CxImage'
> CPP lib/cximage-6.0/CxImage/DllInterface.o
> CPP lib/cximage-6.0/CxImage/ximadsp.o
> In file included from /usr/include/c++/6/deque:60:0,
>  from /usr/include/c++/6/queue:60,
>  from ximadsp.cpp:3480:
> /usr/include/c++/6/bits/stl_algobase.h:243:56: error: macro "min" passed 3 
> arguments, but takes just 2
>  min(const _Tp& __a, const _Tp& __b, _Compare __comp)
> ^
> /usr/include/c++/6/bits/stl_algobase.h:265:56: error: macro "max" passed 3 
> arguments, but takes just 2
>  max(const _Tp& __a, const _Tp& __b, _Compare __comp)
> ^
> In file included from xfile.h:51:0,
>  from ximage.h:62,
>  from ximadsp.cpp:6:
> /usr/include/c++/6/bits/stl_algobase.h:195:5: error: expected unqualified-id 
> before 'const'
>  min(const _Tp& __a, const _Tp& __b)
>  ^
> /usr/include/c++/6/bits/stl_algobase.h:195:5: error: expected ')' before 
> 'const'
> /usr/include/c++/6/bits/stl_algobase.h:195:5: error: expected ')' before 
> 'const'
> /usr/include/c++/6/bits/stl_algobase.h:195:5: error: expected ')' before 
> 'const'
> /usr/include/c++/6/bits/stl_algobase.h:195:5: error: expected initializer 
> before 'const'
> /usr/include/c++/6/bits/stl_algobase.h:219:5: error: expected unqualified-id 
> before 'const'
>  max(const _Tp& __a, const _Tp& __b)
>  ^
> /usr/include/c++/6/bits/stl_algobase.h:219:5: error: expected ')' before 
> 'const'
> /usr/include/c++/6/bits/stl_algobase.h:219:5: error: expected ')' before 
> 'const'
> /usr/include/c++/6/bits/stl_algobase.h:219:5: error: expected ')' before 
> 'const'
> /usr/include/c++/6/bits/stl_algobase.h:219:5: error: expected initializer 
> before 'const'
> In file included from /usr/include/c++/6/deque:60:0,
>  from /usr/include/c++/6/queue:60,
>  from ximadsp.cpp:3480:
> /usr/include/c++/6/bits/stl_algobase.h:243:5: error: 'std::min' declared as 
> an 'inline' variable
>  min(const _Tp& __a, const _Tp& __b, _Compare __comp)
>  ^~~
> /usr/include/c++/6/bits/stl_algobase.h:246:7: error: expected 
> primary-expression before 'if'
>if (__comp(__b, __a))
>^~
> /usr/include/c++/6/bits/stl_algobase.h:246:7: error: expected '}' before 'if'
> /usr/include/c++/6/bits/stl_algobase.h:246:7: error: expected ';' before 'if'
> /usr/include/c++/6/bits/stl_algobase.h:248:7: error: expected unqualified-id 
> before 'return'
>return __a;
>^~
> /usr/include/c++/6/bits/stl_algobase.h:265:5: error: 'max' declared as an 
> 'inline' variable
>  max(const _Tp& __a, const _Tp& __b, _Compare __comp)
>  ^~~
> /usr/include/c++/6/bits/stl_algobase.h:268:7: error: expected 
> primary-expression before 'if'
>if (__comp(__a, __b))
>^~
> /usr/include/c++/6/bits/stl_algobase.h:268:7: error: expected '}' before 'if'
> /usr/include/c++/6/bits/stl_algobase.h:268:7: error: expected ';' before 'if'
> /usr/include/c++/6/bits/stl_algobase.h:270:7: error: expected unqualified-id 
> before 'return'
>return __a;
>^~
> /usr/include/c++/6/bits/stl_algobase.h:271:5: error: expected declaration 
> before '}' token
>  }
>  ^
> make[3]: *** [ximadsp.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/kodi_16.1+dfsg1-1_unstable_gcc6.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#831133: ardour: FTBFS with GCC 6: ../libs/ardour/parameter_descriptor.cc:181:40: error: no matching function for call to 'max(double, float)'

2016-07-14 Thread Lucas Nussbaum
Source: ardour
Version: 1:4.7~dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> 18:28:42 runner ['/usr/bin/g++', '-I/«PKGBUILDDIR»', '-Wdate-time', 
> '-D_FORTIFY_SOURCE=2', '-g', '-O2', '-fstack-protector-strong', '-Wformat', 
> '-Werror=format-security', '-DWAF_BUILD', '-DNDEBUG', '-fshow-column', '-O3', 
> '-fomit-frame-pointer', '-ffast-math', '-fstrength-reduce', '-pipe', 
> '-DARCH_X86', '-mmmx', '-msse', '-mfpmath=sse', '-DUSE_XMMINTRIN', 
> '-DBUILD_SSE_OPTIMIZATIONS', '-DLXVST_64BIT', '-Wall', '-Wpointer-arith', 
> '-Wcast-qual', '-Wcast-align', '-Wno-unused-parameter', 
> '-DBOOST_SYSTEM_NO_DEPRECATED', '-D_ISOC9X_SOURCE', '-D_LARGEFILE64_SOURCE', 
> '-D_FILE_OFFSET_BITS=64', '-DENABLE_NLS', '-DPROGRAM_NAME="Ardour"', 
> u'-DPROGRAM_VERSION="4"', '-std=c++11', '-DBOOST_NO_AUTO_PTR', 
> '-Woverloaded-virtual', '-Wno-unused-local-typedefs', 
> '-D__STDC_LIMIT_MACROS', '-D__STDC_FORMAT_MACROS', '-DCANVAS_COMPATIBILITY', 
> '-DCANVAS_DEBUG', '-fPIC', '-fPIC', '-std=c++11', '-pthread', '-pthread', 
> '-pthread', '-pthread', '-std=c++11', '-pthread', '-std=c++11', 
> '-I/«PKGBUILDDIR»/build/libs/ardour', '-I/«PKGBUILDDIR»/libs/ardour', 
> '-I/«PKGBUILDDIR»/build/libs/surfaces/control_protocol', 
> '-I/«PKGBUILDDIR»/libs/surfaces/control_protocol', 
> '-I/«PKGBUILDDIR»/build/libs', '-I/«PKGBUILDDIR»/libs', 
> '-I/«PKGBUILDDIR»/build/libs/midi++2', '-I/«PKGBUILDDIR»/libs/midi++2', 
> '-I/«PKGBUILDDIR»/build/libs/evoral', '-I/«PKGBUILDDIR»/libs/evoral', 
> '-I/«PKGBUILDDIR»/build/libs/audiographer', 
> '-I/«PKGBUILDDIR»/libs/audiographer', 
> '-I/«PKGBUILDDIR»/build/libs/audiographer/src', 
> '-I/«PKGBUILDDIR»/libs/audiographer/src', '-I/«PKGBUILDDIR»/build/libs/pbd', 
> '-I/«PKGBUILDDIR»/libs/pbd', '-I/«PKGBUILDDIR»/build/libs/evoral/src/libsmf', 
> '-I/«PKGBUILDDIR»/libs/evoral/src/libsmf', 
> '-I/«PKGBUILDDIR»/build/libs/timecode', '-I/«PKGBUILDDIR»/libs/timecode', 
> '-I/usr/include/glibmm-2.4', 
> '-I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include', '-I/usr/include/glib-2.0', 
> '-I/usr/lib/x86_64-linux-gnu/glib-2.0/include', '-I/usr/include/sigc++-2.0', 
> '-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include', '-I/usr/include/libxml2', 
> '-I/usr/include/taglib', '-I/usr/include/sratom-0', '-I/usr/include/sord-0', 
> '-I/usr/include/serd-0', '-I/usr/include/lilv-0', '-I/usr/include/suil-0', 
> '-I/usr/include/giomm-2.4', '-I/usr/lib/x86_64-linux-gnu/giomm-2.4/include', 
> '-I/«PKGBUILDDIR»/build', '-DINTERNAL_SHARED_LIBS=1', 
> '-DUSE_EXTERNAL_LIBS=1', '-DHAVE_DLOPEN=1', '-DHAVE_ALSA=1', '-DHAVE_GLIB=1', 
> '-DHAVE_GTHREAD=1', '-DHAVE_GLIBMM=1', '-DHAVE_SNDFILE=1', '-DHAVE_GIOMM=1', 
> '-DHAVE_CURL=1', '-DHAVE_LO=1', '-DHAVE_TAGLIB=1', '-DHAVE_VAMPSDK=1', 
> '-DHAVE_VAMPHOSTSDK=1', '-DHAVE_RUBBERBAND=1', 
> '-DEXPORT_VISIBILITY_HIDDEN=False', '-DENABLE_NLS=1', '-DLXVST_SUPPORT=1', 
> '-DCONFIG_ARCH="x86_64"', '-DHAVE_TOOLS_SANITY_CHECK=1', 
> '-DHAVE_TOOLS_GCCABICHECK=1', '-DHAVE_LIBS_CLEARLOOKS_NEWER=1', 
> '-DHAVE_LIBS_QM_DSP=1', '-DHAVE_FFTW3F=1', '-DHAVE_AUBIO=1', 
> '-DHAVE_AUBIO4=1', '-DHAVE_LIBS_VAMP_PLUGINS=1', '-DHAVE_LIBLTC=1', 
> '-DHAVE_LIBS_LIBLTC=1', '-DHAVE_LIBS_PTFORMAT=1', '-DHAVE_XML=1', 
> '-DHAVE_SIGCPP=1', '-DHAVE_GETMNTENT=1', '-DHAVE_EXECINFO=1', 
> '-DHAVE_POSIX_MEMALIGN=1', '-DHAVE_LOCALTIME_R=1', '-DHAVE_LIBS_PBD=1', 
> '-DHAVE_LIBS_MIDIPP2=1', '-DHAVE_LIBS_EVORAL=1', '-DHAVE_CWIID_H=1', 
> '-DHAVE_BLUETOOTH_H=1', '-DHAVE_CWIID=1', '-DBUILD_WIIMOTE=1', 
> '-DHAVE_CONTROL_PROTOCOL=1', '-DHAVE_FADERPORT=1', '-DHAVE_GENERIC_MIDI=1', 
> '-DHAVE_MACKIE=1', '-DHAVE_WIIMOTE=1', '-DHAVE_LIBS_SURFACES=1', 
> '-DHAVE_2IN2OUT=1', '-DHAVE_1IN2OUT=1', '-DHAVE_VBAP=1', 
> '-DHAVE_STEREOBALANCE=1', '-DHAVE_LIBS_PANNERS=1', '-DHAVE_JACK=1', 
> '-DHAVE_JACK_METADATA=1', '-DHAVE_LIBS_BACKENDS=1', '-DHAVE_LIBS_TIMECODE=1', 
> '-DHAVE_LRDF=1', '-DHAVE_SAMPLERATE=1', '-DHAVE_LV2=1', '-DHAVE_LV2_1_2_0=1', 
> '-DHAVE_LV2_1_10_0=1', '-DHAVE_SERD=1', '-DHAVE_SORD=1', '-DHAVE_SRATOM=1', 
> '-DHAVE_LILV=1', '-DHAVE_LILV_0_16_0=1', '-DHAVE_LILV_0_19_2=1', 
> '-DHAVE_LILV_0_21_3=1', '-DHAVE_SUIL=1', '-DLV2_SUPPORT=1', '-DHAVE_OGG=1', 
> '-DHAVE_FLAC=1', '-DUSE_RUBBERBAND=1', '-DCURRENT_SESSION_FILE_VERSION=3001', 
> '-DHAVE_SYS_VFS_H=1', '-DHAVE_SYS_STATVFS_H=1', '-DHAVE_UNISTD=1', 
> '-DHAVE_BOOST_SCOPED_PTR_HPP=1', '-DHAVE_BOOST_PTR_CONTAINER_PTR_LIST_HPP=1', 
> '-DHAVE_LIBS_ARDOUR=1', '-DHAVE_GTKMM=1', '-DHAVE_GTK=1', 
> '-DHAVE_LIBS_GTKMM2EXT=1', '-DHAVE_BOOST_FORMAT_HPP=1', 
> '-DHAVE_LIBS_AUDIOGRAPHER=1', '-DHAVE_CAIROMM=1', '-DHAVE_LIBS_CANVAS=1', 

Bug#831099: rosegarden: FTBFS with GCC 6: PitchBendSequenceDialog.cpp:922:73: error: call of overloaded 'abs(double)' is ambiguous

2016-07-14 Thread Lucas Nussbaum
Source: rosegarden
Version: 1:16.02-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> [  5%] Building CXX object 
> src/CMakeFiles/rosegardenprivate.dir/document/GzipFile.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/c++   -DBUILD_RELEASE 
> -DHAVE_ALSA -DHAVE_LIBJACK -DHAVE_LIBSNDFILE -DNDEBUG -DNO_TIMING 
> -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS 
> -DQT_TEST_LIB -DQT_XML_LIB -DROSEGARDENPRIVATE_LIB_MAKEDLL -DSTABLE 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src -isystem 
> /usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem 
> /usr/include/qt4/QtTest -isystem /usr/include/qt4/QtXml -isystem 
> /usr/include/qt4/QtNetwork -isystem /usr/include/qt4/QtCore -isystem 
> /usr/share/qt4/mkspecs/default  -g -O2 -fPIE -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall 
> -Woverloaded-virtual -Wextra -Wformat-nonliteral -Wformat-security 
> -Winit-self -Wswitch-enum -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef 
> -Wcast-align -Wchar-subscripts -W -Wpointer-arith -fno-check-new -fno-common 
> -fvisibility=hidden   -o 
> CMakeFiles/rosegardenprivate.dir/document/GzipFile.cpp.o -c 
> /«PKGBUILDDIR»/src/document/GzipFile.cpp
> [  5%] Building CXX object 
> src/CMakeFiles/rosegardenprivate.dir/document/LinkedSegmentsCommand.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/c++   -DBUILD_RELEASE 
> -DHAVE_ALSA -DHAVE_LIBJACK -DHAVE_LIBSNDFILE -DNDEBUG -DNO_TIMING 
> -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS 
> -DQT_TEST_LIB -DQT_XML_LIB -DROSEGARDENPRIVATE_LIB_MAKEDLL -DSTABLE 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src -isystem 
> /usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem 
> /usr/include/qt4/QtTest -isystem /usr/include/qt4/QtXml -isystem 
> /usr/include/qt4/QtNetwork -isystem /usr/include/qt4/QtCore -isystem 
> /usr/share/qt4/mkspecs/default  -g -O2 -fPIE -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall 
> -Woverloaded-virtual -Wextra -Wformat-nonliteral -Wformat-security 
> -Winit-self -Wswitch-enum -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef 
> -Wcast-align -Wchar-subscripts -W -Wpointer-arith -fno-check-new -fno-common 
> -fvisibility=hidden   -o 
> CMakeFiles/rosegardenprivate.dir/document/LinkedSegmentsCommand.cpp.o -c 
> /«PKGBUILDDIR»/src/document/LinkedSegmentsCommand.cpp
> [  5%] Building CXX object 
> src/CMakeFiles/rosegardenprivate.dir/document/Command.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/c++   -DBUILD_RELEASE 
> -DHAVE_ALSA -DHAVE_LIBJACK -DHAVE_LIBSNDFILE -DNDEBUG -DNO_TIMING 
> -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS 
> -DQT_TEST_LIB -DQT_XML_LIB -DROSEGARDENPRIVATE_LIB_MAKEDLL -DSTABLE 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src -isystem 
> /usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem 
> /usr/include/qt4/QtTest -isystem /usr/include/qt4/QtXml -isystem 
> /usr/include/qt4/QtNetwork -isystem /usr/include/qt4/QtCore -isystem 
> /usr/share/qt4/mkspecs/default  -g -O2 -fPIE -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall 
> -Woverloaded-virtual -Wextra -Wformat-nonliteral -Wformat-security 
> -Winit-self -Wswitch-enum -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef 
> -Wcast-align -Wchar-subscripts -W -Wpointer-arith -fno-check-new -fno-common 
> -fvisibility=hidden   -o 
> CMakeFiles/rosegardenprivate.dir/document/Command.cpp.o -c 
> /«PKGBUILDDIR»/src/document/Command.cpp
> [  5%] Building CXX object 
> src/CMakeFiles/rosegardenprivate.dir/document/BasicCommand.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/c++   -DBUILD_RELEASE 
> -DHAVE_ALSA -DHAVE_LIBJACK -DHAVE_LIBSNDFILE -DNDEBUG -DNO_TIMING 
> -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS 
> -DQT_TEST_LIB -DQT_XML_LIB -DROSEGARDENPRIVATE_LIB_MAKEDLL -DSTABLE 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src -isystem 
> /usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem 
> /usr/include/qt4/QtTest -isystem /usr/include/qt4/QtXml -isystem 
> /usr/include/qt4/QtNetwork -isystem /usr/include/qt4/QtCore -isystem 
> /usr/share/qt4/mkspecs/default  -g -O2 -fPIE -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  

Bug#831092: qsynth: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory

2016-07-14 Thread Lucas Nussbaum
Source: qsynth
Version: 0.4.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -c -m64 -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -O2 -std=gnu++0x 
> -Wall -W -D_REENTRANT -fPIC -DDATADIR="/usr/share" -DQT_NO_DEBUG 
> -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -I. 
> -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/local/include 
> -isystem /usr/include -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets 
> -isystem /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I.ui 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o .obj/qsynth.o 
> qsynth.cpp
> In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
>  from /usr/include/c++/6/algorithm:62,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:88,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:37,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:37,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstringlist.h:34,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QStringList:1,
>  from qsynthSetup.h:25,
>  from qsynthOptions.h:25,
>  from qsynth.cpp:23:
> /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or 
> directory
>  #include_next 
>  ^
> compilation terminated.
> make[3]: *** [.obj/qsynth.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/qsynth_0.4.1-1_unstable_gcc6.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#831078: supercollider-sc3-plugins: FTBFS with GCC 6: DWG.hpp:1271:53: error: no matching function for call to 'min(float, double)'

2016-07-14 Thread Lucas Nussbaum
Source: supercollider-sc3-plugins
Version: 3.7.1~repack-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> [ 26%] Building CXX object 
> source/CMakeFiles/DWGPlucked.dir/DWGUGens/DWGPlucked.cpp.o
> cd "/«PKGBUILDDIR»/obj-x86_64-linux-gnu/source" && /usr/bin/c++   
> -DDWGPlucked_EXPORTS -DNOVA_SIMD -DSYSTEM_STK 
> -I"/«PKGBUILDDIR»/external_libraries/nova-simd" -I"/«PKGBUILDDIR»/include" 
> -I"/«PKGBUILDDIR»/source/scfft_old" -I/usr/include/SuperCollider/common 
> -I/usr/include/SuperCollider/plugin_interface 
> -I/usr/include/SuperCollider/include/plugin_interface 
> -I/usr/include/SuperCollider/include/common 
> -I/usr/include/SuperCollider/server/plugins 
> -I/usr/include/SuperCollider/common/Headers/plugin_interface 
> -I/usr/include/SuperCollider/common/Headers/common 
> -I/usr/include/SuperCollider/common/Source/plugins 
> -I/usr/include/SuperCollider/external_libraries/libsndfile 
> -I"/«PKGBUILDDIR»/source/DEINDUGens/include" -I/usr/include/stk 
> -I"/«PKGBUILDDIR»/source/AYUGens/AY_libayemu/include"  -g -O2 -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -msse -msse2 -mfpmath=sse -std=c++11 -O3 -DNDEBUG -fPIC  
>  -fvisibility=hidden -o CMakeFiles/DWGPlucked.dir/DWGUGens/DWGPlucked.cpp.o 
> -c "/«PKGBUILDDIR»/source/DWGUGens/DWGPlucked.cpp"
> In file included from /«PKGBUILDDIR»/source/DWGUGens/dwglib/DWG.cpp:19:0,
>  from /«PKGBUILDDIR»/source/DWGUGens/DWGPlucked.cpp:19:
> /«PKGBUILDDIR»/source/DWGUGens/dwglib/DWG.hpp: In member function 'void 
> TUBE::set_area(float, float)':
> /«PKGBUILDDIR»/source/DWGUGens/dwglib/DWG.hpp:1271:53: error: no matching 
> function for call to 'min(float, double)'
>  loss = 1.0 - std::min(lossF/sqrt(a1),1.0);
>  ^
> In file included from /usr/include/c++/6/algorithm:61:0,
>  from /usr/include/SuperCollider/common/SC_BoundsMacros.h:26,
>  from 
> /usr/include/SuperCollider/plugin_interface/SC_RGen.h:54,
>  from 
> /usr/include/SuperCollider/plugin_interface/SC_World.h:28,
>  from 
> /usr/include/SuperCollider/plugin_interface/SC_PlugIn.h:24,
>  from /«PKGBUILDDIR»/source/DWGUGens/dwglib/DWG.hpp:22,
>  from /«PKGBUILDDIR»/source/DWGUGens/dwglib/DWG.cpp:19,
>  from /«PKGBUILDDIR»/source/DWGUGens/DWGPlucked.cpp:19:
> /usr/include/c++/6/bits/stl_algobase.h:195:5: note: candidate: template _Tp> const _Tp& std::min(const _Tp&, const _Tp&)
>  min(const _Tp& __a, const _Tp& __b)
>  ^~~
> /usr/include/c++/6/bits/stl_algobase.h:195:5: note:   template argument 
> deduction/substitution failed:
> In file included from /«PKGBUILDDIR»/source/DWGUGens/dwglib/DWG.cpp:19:0,
>  from /«PKGBUILDDIR»/source/DWGUGens/DWGPlucked.cpp:19:
> /«PKGBUILDDIR»/source/DWGUGens/dwglib/DWG.hpp:1271:53: note:   deduced 
> conflicting types for parameter 'const _Tp' ('float' and 'double')
>  loss = 1.0 - std::min(lossF/sqrt(a1),1.0);
>  ^
> In file included from /usr/include/c++/6/algorithm:61:0,
>  from /usr/include/SuperCollider/common/SC_BoundsMacros.h:26,
>  from 
> /usr/include/SuperCollider/plugin_interface/SC_RGen.h:54,
>  from 
> /usr/include/SuperCollider/plugin_interface/SC_World.h:28,
>  from 
> /usr/include/SuperCollider/plugin_interface/SC_PlugIn.h:24,
>  from /«PKGBUILDDIR»/source/DWGUGens/dwglib/DWG.hpp:22,
>  from /«PKGBUILDDIR»/source/DWGUGens/dwglib/DWG.cpp:19,
>  from /«PKGBUILDDIR»/source/DWGUGens/DWGPlucked.cpp:19:
> /usr/include/c++/6/bits/stl_algobase.h:243:5: note: candidate: template _Tp, class _Compare> const _Tp& std::min(const _Tp&, const _Tp&, _Compare)
>  min(const _Tp& __a, const _Tp& __b, _Compare __comp)
>  ^~~
> /usr/include/c++/6/bits/stl_algobase.h:243:5: note:   template argument 
> deduction/substitution failed:
> In file included from /«PKGBUILDDIR»/source/DWGUGens/dwglib/DWG.cpp:19:0,
>  from /«PKGBUILDDIR»/source/DWGUGens/DWGPlucked.cpp:19:
> /«PKGBUILDDIR»/source/DWGUGens/dwglib/DWG.hpp:1271:53: note:   deduced 
> conflicting types for parameter 'const _Tp' ('float' and 'double')
>  loss = 1.0 - std::min(lossF/sqrt(a1),1.0);
>

Bug#831071: mixxx: FTBFS with GCC 6: src/util/fpclassify.h:22:20: error: 'std::util_fpclassify' has not been declared

2016-07-14 Thread Lucas Nussbaum
Source: mixxx
Version: 2.0.0~dfsg-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -o lin64_build/analyserqueue.o -c -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -Wall 
> -Wextra -g -pthread -O3 -ffast-math -funroll-loops -fomit-frame-pointer 
> -mtune=generic -Damd64 -DMIXXX_BUILD_RELEASE -D'Q_ASSERT(x)=qt_noop()' 
> -D__LINUX__ -D__UNIX__ -DSETTINGS_PATH=\".mixxx/\" 
> -DSETTINGS_FILE=\"mixxx.cfg\" -DUNIX_SHARE_PATH=\"/usr/share/mixxx\" 
> -DUNIX_LIB_PATH=\"/usr/lib/mixxx\" -D__PORTAUDIO__ -DQT_SHARED 
> -DQT_TABLET_SUPPORT -DQT_CORE_LIB -DQT_GUI_LIB -DQT_OPENGL_LIB -DQT_XML_LIB 
> -DQT_SVG_LIB -DQT_SQL_LIB -DQT_SCRIPT_LIB -DQT_NETWORK_LIB -DQT_SHARED 
> -D__SNDFILE__ -D__MAD__ -D__HID__ -D__BULK__ -D__VINYLCONTROL__ 
> -D__SHOUTCAST__ -D__OPUS__ -DDISABLE_BUILDTIME -DHAVE_FFTW3 
> -D__AUTODJCRATES__ -D__SQLITE3__ -Ilin64_build -Isrc 
> -I/usr/include/soundtouch -Ilib/replaygain -I/usr/include/qt4 
> -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSvg 
> -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtXmlPatterns -
 I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtTest 
-I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtGui 
-I/usr/include/qt4/QtScript -I/usr/include/qt4/QtCore -Ilib/gtest-1.7.0/include 
-Ilib/fidlib-0.9.10 -I/usr/include/taglib -I/usr/include/libusb-1.0 -Ilib/xwax 
-Ilib/scratchlib -I/usr/include/opus src/analyserqueue.cpp
> In file included from src/util/math.h:11:0,
>  from src/util/types.h:4,
>  from src/analyser.h:4,
>  from src/analyserqueue.h:11,
>  from src/analyserqueue.cpp:8:
> src/util/fpclassify.h:22:20: error: 'std::util_fpclassify' has not been 
> declared
>  #define fpclassify util_fpclassify
> ^
> src/util/fpclassify.h:23:18: error: 'std::util_isfinite' has not been declared
>  #define isfinite util_isfinite
>   ^
> src/util/fpclassify.h:20:15: error: 'std::util_isinf' has not been declared
>  #define isinf util_isinf
>^
> src/util/fpclassify.h:19:15: error: 'std::util_isnan' has not been declared
>  #define isnan util_isnan
>^
> src/util/fpclassify.h:21:18: error: 'std::util_isnormal' has not been declared
>  #define isnormal util_isnormal
>   ^
> scons: *** [lin64_build/analyserqueue.o] Error 1
> scons: building terminated because of errors.
> make[1]: *** [override_dh_auto_build] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/mixxx_2.0.0~dfsg-4_unstable_gcc6.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Processed (with 1 error): musescore *still* not installable

2016-07-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forcemerge 824956 830715
Bug #824956 [src:musescore] QtQuick1 will be removed from the archive with Qt 
5.6
Unable to merge bugs because:
package of #830715 is 'musescore' not 'src:musescore'
Failed to forcibly merge 824956: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
824956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824956
830715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
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#824956: musescore *still* not installable

2016-07-14 Thread Thorsten Glaser
forcemerge 824956 830715
thanks

Will there be anything done about it soon, please?

Thanks,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers