Bug#763755: blender: SIGILL on startup

2014-10-10 Thread Johann Klammer
On 10/10/2014 08:48 AM, Matteo F. Vescovi wrote:
 
 No, it doesn't. Your patch wasn't applied in 2.71.
  
I modified it locally...
 
 
 Oh, gotta check this either... but I've no X on my laptop at the moment.
 
 Thanks for reporting.
 
Not sure it's a bug.. it's quite possible they don't support that old
stuff.

___
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#763755: blender: SIGILL on startup

2014-10-10 Thread Matteo F. Vescovi
Hi!

On Fri, Oct 10, 2014 at 9:15 AM, Johann Klammer klamm...@a1.net wrote:

 On 10/10/2014 08:48 AM, Matteo F. Vescovi wrote:
 
  No, it doesn't. Your patch wasn't applied in 2.71.
 
 I modified it locally...


Then, feel free to provide an updated patch. I'll give it a try.


  Oh, gotta check this either... but I've no X on my laptop at the moment.
 
  Thanks for reporting.
 
 Not sure it's a bug.. it's quite possible they don't support that old
 stuff.


They don't, almost for sure. ;-P

Cheers.

-- 
Matteo F. Vescovi
___
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#749659: audacity: Systematic check for Printf/Format mismatches

2014-10-10 Thread Martin Steghöfer

El 09/10/14 a les 01:11, Benjamin Drung ha escrit:

Your patch needs to be forward ported,


We already have a patch that fixes 2.0.6 for wxWidgets 3.0. Back when 
you asked me to forward-port my patch to the current svn head (in order 
to get the changes into upstream), I did. Apart from the porting it 
includes specific fixes for svn head. Fortunately, 2.0.6 isn't that 
different from what was svn head back then, so we have a patch for 
2.0.6, find it attached. To keep it small, I've removed everything that 
isn't relevant here (fixes of dead code or code that otherwise isn't 
relevant on Debian), but we will have that available for upstream. Be 
aware that this patch is by far not as well tested as my patch for 2.0.5!



[...] backport the preliminary upstream changes for wxWidgets 3.0.1 from r13403 
[...]
[...]
Upstream want to get wx3.0 support in for 2.0.7 and is actively working on 
getting it in the svn


Actively working, yes, unfortunately. Why? Your messages sounded like 
upstream was aware of this being resolved already, especially with you 
being part of upstream (AFAIK). Not only was this a major duplication of 
effort, but now it also requires additional porting - which is mainly 
manual work here, given that different people have been working on 
similar issues and touching the same code, but in different ways. What 
we're doing here is really inefficient.




So you could provide the missing bits and we will get
upstream to test your proposed changes (when I commit them to the
upstream repository).


So you're proposing to do the upstream integration first? I'd do it the 
other way round, given that for 2.0.6 we already have a patch and that 
the upstream integration has just gotten more complicated. We've already 
lost a lot of time. And before we just upload stuff to upstream, I'd 
also like to discuss the upstream integration with the person that has 
been working on wx3.0 there, especially as he has been fixing some code 
that I consider obsolete with wx3.0 and that I'd like to fix some things 
in a different way.


Cheers,
Martin

Description: Compile audacity against wxWidgets 3.0
 Solved compilation issues:
 (1.) Allow wxWidgets 3.0 in various configure scripts.
 (2.) The file dialog was derived from an internal wx class that
 disappeared in wx3.0 (discussed in further detail below).
 (3.) In several places the types in interfaces changed between
 wxChar* and wxString. I've tried to modify the code so it works with
 both interfaces (thanks to implicit conversion; may look a bit weird
 in some places).
 (4.) Calls to wxTheApp-SuspendIdleCallback() are no longer
 supported. They were part of a workaround for a clipboard problem,
 which fortunately doesn't seem to be there any longer in wx3.0, so I
 deactivated it for wx3.0.
 (5.) AddPendingEvent() and ProcessEvent() now have the visibility
 protected in wxWindow. It has always been a bad idea to call them
 directly on a wxWindow object, but now it's explicitly forbidden.
 Instead, those functions should be called on the object returned by
 GetEventHandler().
 (6.) The class wxStandardPaths is now a singleton and has to be
 treated as such (no more explicit constructor calls).
 (7.) wxLogWarning is a macro now, so the :: prefix doesn't work
 on it anymore.
 (8.) Several int types (which were actually used as enums) are now
 real enum types (e.g. wxRasterOperationMode, wxMouseButton) and have
 to be used as such.
 (9.) Apart from the FD constants (which have been fixed in Olly's
 patch already) there are some other constants which have received a
 prefix (e.g. wx* - wxFONTFAMILY_*, wx* - wxFONTSTYLE_*, wx* -
 wxFONTWEIGHT_*).
 (10.) Signature changes in constructors of wxFlexGridSizer and wxIcon
 and wxSizeEvent
 (11.) Missing includes (missing header files were probably included
 indirectly in wx2.8 by chance)
 (12.) When deriving from the abstract class wxGridTableBase,
 different methods have to be implemented with wx3.0 (EndEdit with new
 signature and ApplyEdit) than before with wx2.8 (only EndEdit with
 old signature). Now both versions are implemented in parallel in the
 classes TimeEditor and ChoiceEditor (one version essentially being a
 wrapper of the other one).
 Solved runtime issues:
 (1.) Segmentation fault: The LadspaEffectDialog receives EVT_TEXT
 events before it's properly initialized. To prevent this, a
 workaround was already in place, but was only active on Windows. It
 looks like this happens now on more platforms (including GTK). As the
 workaround doesn't do any harm, even if activated unnecessarily, I've
 simply activated it for all environments.
 (2.) GTK critical warning IA__gtk_range_set_range: assertion
 'min  max' failed because of negative numbers as result of window
 size checking. Added a sanity check that straightens up the numbers
 in edge cases.
 (3.) GTK critical warning IA__gdk_window_get_origin: assertion
 'GDK_IS_WINDOW (window)' failed: Received events of type wxSizeEvent
 on the main project 

handbrake 0.9.9+svn6422+dfsg1-2 MIGRATED to testing

2014-10-10 Thread Debian testing watch
FYI: The status of the handbrake source package
in Debian's testing distribution has changed.

  Previous version: 0.9.9+svn6422+dfsg1-1
  Current version:  0.9.9+svn6422+dfsg1-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

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


smplayer-themes 1:14.9.0-1 MIGRATED to testing

2014-10-10 Thread Debian testing watch
FYI: The status of the smplayer-themes source package
in Debian's testing distribution has changed.

  Previous version: 0.1.20+dfsg-1
  Current version:  1:14.9.0-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

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


smplayer 14.9.0~ds0-1 MIGRATED to testing

2014-10-10 Thread Debian testing watch
FYI: The status of the smplayer source package
in Debian's testing distribution has changed.

  Previous version: 14.3.0-1
  Current version:  14.9.0~ds0-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
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#762377: closed by Sebastian Ramacher sramac...@debian.org (Re: Bug#762377: vlc: Videos over HTTP stream very slowly in 2.2.0-pre3)

2014-10-10 Thread Andoru Ekkusu
Sorry for the late reply, but indeed it fixed the problem for me as well.

Does anyone know where was this issue fixed? Was it a bug in the debian
packages or was it upstream? Just out of curiosity :)
___
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: Bits from the Debian Multimedia Team [RELOADED]

2014-10-10 Thread Alessio Treglia
Folks,

If you want to add some last bits, please do it by tomorrow morning, I'd
intend to mail it in the early afternoon.

Cheers.

sent via mobile
___
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: What should be done before freeze

2014-10-10 Thread Felipe Sateler
On Wed, Oct 8, 2014 at 10:49 AM, Jaromír Mikeš mira.mi...@gmail.com wrote:


 2014-10-08 14:57 GMT+02:00 Felipe Sateler fsate...@debian.org:

 On Mon, Oct 6, 2014 at 3:57 PM, Felipe Sateler fsate...@debian.org
 wrote:
  Hi,
 
  On Mon, Oct 6, 2014 at 3:37 PM, Jaromír Mikeš mira.mi...@gmail.com
  wrote:
 
  BTW would you mind to do team upload of traverso ... it is now builds
  against lilv and this is our last package which depends on slv2.
  The only other package is gstreamer0.10-plugins-bad :(
 
  I will ASAP. I may be a bi tbusy during the week, so if anyone wants
  to beat me to it, be my guest :)

 Please fill out the changelog, and add yourself to uploaders if you
 want to be an uploader. Traverso currently has only one and Gurkan
 does not seem active in this group :(


 Done!

I built it but I'm getting crashes:

Program received signal SIGSEGV, Segmentation fault.
Client::~Client (this=0xd2f320, __in_chrg=optimized out) at
/home/felipe/src/deb/pkg-multimedia/traverso/src/engine/Client.cpp:52
(gdb) bt
#0  Client::~Client (this=0xd2f320, __in_chrg=optimized out) at
/home/felipe/src/deb/pkg-multimedia/traverso/src/engine/Client.cpp:52
#1  0x7fffe99724d3 in FAMOpen2 () from /usr/lib/libfam.so.0
#2  0x7fffebc79439 in ?? () from /usr/lib/libkdecore.so.5
#3  0x7fffebc79fb5 in KDirWatch::KDirWatch(QObject*) () from
/usr/lib/libkdecore.so.5
#4  0x7fffec8bf0f8 in KBookmarkManager::KBookmarkManager(QString
const) () from /usr/lib/libkio.so.5
#5  0x7fffec8bf676 in
KBookmarkManager::managerForExternalFile(QString const) () from
/usr/lib/libkio.so.5
#6  0x7fffe0e5fddd in ?? () from /usr/lib/libkfile.so.4
#7  0x7fffe0e5cbe0 in KFilePlacesModel::KFilePlacesModel(QObject*)
() from /usr/lib/libkfile.so.4
#8  0x7fffe0e439ef in KDirSelectDialog::KDirSelectDialog(KUrl
const, bool, QWidget*) () from /usr/lib/libkfile.so.4
#9  0x7fffe0e45103 in KDirSelectDialog::selectDirectory(KUrl
const, bool, QWidget*, QString const) () from /usr/lib/libkfile.so.4
#10 0x7fffe10a5e59 in ?? () from /usr/lib/kde4/kfilemodule.so
#11 0x7fffec8dd818 in KFileDialog::getExistingDirectory(KUrl
const, QWidget*, QString const) () from /usr/lib/libkio.so.5
#12 0x7fffec8e116b in ?? () from /usr/lib/libkio.so.5
#13 0x7779c0be in QFileDialog::getExistingDirectory(QWidget*,
QString const, QString const, QFlagsQFileDialog::Option) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x00560abe in ProjectManager::start (this=0x8c1400 pm()::projMan)
at 
/home/felipe/src/deb/pkg-multimedia/traverso/src/core/ProjectManager.cpp:311
#15 0x00490191 in Traverso::create_interface (this=optimized out)
at 
/home/felipe/src/deb/pkg-multimedia/traverso/src/traverso/Traverso.cpp:159
#16 0x76da12c1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#17 0x772bc6e3 in QApplication::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#18 0x772b731c in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#19 0x772bde18 in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#20 0x76d87cad in QCoreApplication::notifyInternal(QObject*,
QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#21 0x76d8b541 in
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#22 0x76db7003 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#23 0x72747c5d in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x72747f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x72747ffc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x76db714d in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#27 0x7735c056 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#28 0x76d86801 in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#29 0x76d86b65 in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#30 0x76d8c5c7 in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#31 0x0047ab25 in main (argc=1, argv=0x7fffde28) at
/home/felipe/src/deb/pkg-multimedia/traverso/src/traverso/Main.cpp:131



-- 

Saludos,
Felipe Sateler

___
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: tagging 749385

2014-10-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 749385 + fixed-upstream
Bug #749385 [csound] csound: Conflicting declarations of oscils_set (and others)
Added tag(s) fixed-upstream.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
749385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749385
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#763755: blender: SIGILL on startup

2014-10-10 Thread Johann Klammer
On 10/10/2014 09:47 AM, Matteo F. Vescovi wrote:
 
 Then, feel free to provide an updated patch. I'll give it a try.
Here. but it's against the .71, and looks pretty much the same as the
earlier one. I don't have enough free space to dare the pbuilder thing.
I also added that architecture.mk mentioned earlier.

Description: as usual
 TODO: Put a short summary on the line above and replace this paragraph
 with a longer explanation of this change. Complete the meta-information
 with other relevant fields (see below for details). To make it easier, the
 information below has been extracted from the changelog. Adjust it or drop
 it.
 .
 blender (2.71+dfsg1-2) UNRELEASED; urgency=medium
 .
   * change rules file to set architecture flags
Author: Johann Klammer klamm...@a1.net

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: vendor|upstream|other, url of original patch
Bug: url in upstream bugtracker
Bug-Debian: http://bugs.debian.org/bugnumber
Bug-Ubuntu: https://launchpad.net/bugs/bugnumber
Forwarded: no|not-needed|url proving that it has been forwarded
Reviewed-By: name and email of someone who approved the patch
Last-Update: -MM-DD

--- blender-2.71+dfsg1.orig/build_files/cmake/macros.cmake
+++ blender-2.71+dfsg1/build_files/cmake/macros.cmake
@@ -446,34 +446,42 @@ macro(TEST_SSE_SUPPORT
 
set(CMAKE_REQUIRED_FLAGS ${${_sse_flags}} ${${_sse2_flags}})
 
-   if(NOT DEFINED SUPPORT_SSE_BUILD)
-   # result cached
-   check_c_source_runs(
-   #include xmmintrin.h
-   int main(void) { __m128 v = _mm_setzero_ps(); return 0; 
}
-   SUPPORT_SSE_BUILD)
 
-   if(SUPPORT_SSE_BUILD)
-   message(STATUS SSE Support: detected.)
-   else()
-   message(STATUS SSE Support: missing.)
+   if(NOT ( $ENV{DEB_HOST_ARCH_CPU} STREQUAL i386 ) )
+
+   if(NOT DEFINED SUPPORT_SSE_BUILD)
+   # result cached
+   check_c_source_runs(
+   #include xmmintrin.h
+   int main(void) { __m128 v = _mm_setzero_ps(); 
return 0; }
+   SUPPORT_SSE_BUILD)
+
+   if(SUPPORT_SSE_BUILD)
+   message(STATUS SSE Support: detected.)
+   else()
+   message(STATUS SSE Support: missing.)
+   endif()
endif()
-   endif()
 
-   if(NOT DEFINED SUPPORT_SSE2_BUILD)
-   # result cached
-   check_c_source_runs(
-   #include emmintrin.h
-   int main(void) { __m128d v = _mm_setzero_pd(); return 
0; }
-   SUPPORT_SSE2_BUILD)
+   if(NOT DEFINED SUPPORT_SSE2_BUILD)
+   # result cached
+   check_c_source_runs(
+   #include emmintrin.h
+   int main(void) { __m128d v = _mm_setzero_pd(); 
return 0; }
+   SUPPORT_SSE2_BUILD)
 
-   if(SUPPORT_SSE2_BUILD)
-   message(STATUS SSE2 Support: detected.)
-   else()
-   message(STATUS SSE2 Support: missing.)
+   if(SUPPORT_SSE2_BUILD)
+   message(STATUS SSE2 Support: detected.)
+   else()
+   message(STATUS SSE2 Support: missing.)
+   endif()
endif()
+   else()
+   message(STATUS SSE Support: missing.)
+   message(STATUS SSE2 Support: missing.)
endif()
 
+
unset(CMAKE_REQUIRED_FLAGS)
 endmacro()
 
#!/usr/bin/make -f

#they say I should not rely on DEB_HOST_ARCH being correctly set automagically, 
and do this to be sure...
include /usr/share/dpkg/architecture.mk

export REPACK_SH=$(CURDIR)/debian/repack.sh

INSTDIR = debian/tmp
PY3VERS = $(shell py3versions -dv)
SRC_VER = $(shell uscan --report | grep blender-.* | sed 's/^.*-//' | sed 
's/\.tar.*$$//')

get-orig-source:
uscan --force-download --repack --compression xz
$(REPACK_SH) --upstream-version $(SRC_VER) 
../blender_$(SRC_VER).orig.tar.xz

override_dh_auto_configure:
dh_auto_configure -- \
-DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_SKIP_RPATH=ON \
-DCMAKE_VERBOSE_MAKEFILE=ON \
-DFREETYPE_INCLUDE_DIRS=/usr/include/freetype2 \
-DPYTHON_VERSION=$(PY3VERS) \
-DWITH_IMAGE_OPENJPEG=ON \
-DWITH_FFTW3=ON \
-DWITH_JACK=ON \
-DWITH_PLAYER=ON \
-DWITH_INSTALL_PORTABLE=OFF \

Bug#749659: audacity: Systematic check for Printf/Format mismatches

2014-10-10 Thread Martin Steghöfer

Hi Benjamin!


Martin Steghöfer wrote:
And before we just upload stuff to upstream, I'd also like to discuss 
the upstream integration with the person that has been working on 
wx3.0 there


Looking at the recent upstream activity, I've changed my mind about 
this: We should get this into upstream as soon as possible! Otherwise 
porting the fixes is just going to be even more difficult. Now that 
someone has made an initial commit about wxWidgets 3.0, people upgrade 
and try to fix things - but not always in the proper way.


Today's upstream commits alone justify being worried: 3 commits arrived 
upstream trying to fix wx3.0-related stuff: The first one removed 
functionality (!) in order to avoid the problems. The second one 
replaced one inadequate function call by another inadequate function 
call - which avoids the crash for the moment, but is equally wrong and 
may still crash with other compiler flags. The third one silenced a 
warning instead of fixing the underlying problem - which causes an 
invalid memory access and therefore a possible crash. With all those 
fixes in place, porting the patch won't only get harder (because of 
conflicts), but the diff will also become more cryptic (it's easier to 
understand a simple fix than to understand the fix of an existing fix).


So today I took the time to port my fixes (again) to the current svn 
head. I've got them sitting in my local git, divided in many commits, 
for better documentation (the Debian patch is huge and no one can tell 
any more, which change corresponds to which fix). I can send them all to 
you and you import them manually into svn. Or I can commit them directly 
to the svn - I've got git-svn set-up, I'd just need access to the 
repository. I can also send the patches to you first, for inspection 
(but it's mainly what you've seen here in the debdiff, just divided, 
ported and with non-Debian-relevant changes).


For the Debian package I still recommend the patch I've sent earlier 
today. Why bother with extra porting work and combining several patches 
(including additional porting work)?


Cheers,
Martin

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