Bug#859305: forked-daapd: please make the build reproducible

[Balint Reczey]

Control: tags -1 + confirmed upstream fixed-upstream - patch
Control: forwarded -1 https://github.com/ejurgensen/forked-daapd/pull/328

Hi Chris,

On 04/01/2017 11:26 PM, Chris Lamb wrote:
> Source: forked-daapd
> Version: 24.2-1
> Severity: wishlist
> Tags: patch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: timestamps
> X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
> 
> Hi,
> 
> Whilst working on the Reproducible Builds effort [0], we noticed
> that forked-daapd could not be built reproducibly.
> 
> Patch attached.
> 
>  [0] https://reproducible-builds.org/

Thanks for the patch but it already has been fixed by moving to
__DATE__ at upstream, thus I will fix this bug with next upstream
release instead.

Cheers,
Balint

--
Balint Reczey
Debian & Ubuntu Developer

___
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#855115: kodi does not work wireless xbox360 controller

[Balint Reczey]

Control: tags -1 moreinfo
Control: version -1 2:17.0+dfsg1-2

Hi Tommy,

On 02/14/2017 11:49 AM, Tommy P wrote:
> Package:  Kodi
> Version:  2:17.0+dfsg1-2 and others
> 
> 
> I cannot get a wireless xbox360 controller to work with kodi v17.
> The controller works fine using the xboxdrv package and it controls
> the menus of retroarch (a different program).  But I could not get
> the controller to work with kodi. The kodi.tv wiki wasn't much help.
> :(It could be something stupid I've tried too, but 8 hours was my
> limit of troubleshooting this.

There is a thread about this problem on kodi.tv with potential solution:
http://forum.kodi.tv/showthread.php?tid=210551=2177036#pid2177036

Does that work for you?

Cheers,
Balint

___
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: Kodi Chorus2 web interface (RFH)

[Balint Reczey]

Hi Ross,

Ross Gammon  wrote:

> Hi Bálint,
> 
> On 01/17/2017 03:28 PM, Bálint Réczey wrote:
>> Dear Team,
>> 
>> I have started packaging Kodi's new web interface but it looks like
>> there are many missing build dependencies.
>> 
>> We are in soft freeze thus the package would not have been accepted,
>> but it could have been uploaded as an additional source tarball for
>> kodi like the patched libdvd* sources are handled now.
>> 
>> If someone could figure out how to build the web interface without all
>> the grunt npm packages and Ruby gems it could make Kodi be released
>> with a functional web interface.
>> 
>> Any help is appreciated in packaging. Even if we miss Stretch, I will
>> keep backporting new Kodi versions and having a working web interface
>> earlier would be nice.
>> 
>> Cheers,
>> Balint
> 
> Can you point me to where I can find out which node-* packages and gems
> are needed?
> 
> I have been working on node packages for other software, and most of the
> grunt stuff has been uploaded by Pirate Praveen in the last few months.
> 
> I was also thinking of packaging another couple of gems that I was
> forced to install locally recently.
> 
> So if there was a list, I might be able to help share some of the load
> for Buster.

Thanks for your help in advance!

I have started packaging and the WIP version can be found here:
https://anonscm.debian.org/gitweb/?p=pkg-multimedia/kodi-addon-webinterface-chorus2.git

The missing grunt packages are listed in d/control:
https://anonscm.debian.org/cgit/pkg-multimedia/kodi-addon-webinterface-chorus2.git/tree/debian/control

Cheers,
Balint

PS: I have just noticed that I have sent the email to the low traffic
email list which I have not been subscribed to. :-(


___
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#844162: src:kodi: validation failure with new fontforge

[Balint Reczey]

Control: severity -1 minor
Control: tags -1 confirmed upstream
Control: forwarded -1 https://github.com/fontforge/fontforge/issues/2920


Hi Adam,

On Sat, 12 Nov 2016 22:08:03 +0100 Adam Borowski 
wrote:
> Package: src:kodi
> Version: 17.0~beta5+dfsg1-1
> Severity: normal
> 
> Hi!
> The new version of fontforge, just uploaded to unstable, has a more stringent
> validator, which causes:
> 
> fontforge -script /<>/kodi-17.0~beta5+dfsg1/debian/mergefonts.ff \
> /usr/share/fonts/truetype/droid/DroidSansFallbackFull.ttf \
> /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf \
> /<>/kodi-17.0~beta5+dfsg1/media/Fonts/arial.ttf
> Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
>  License GPLv3+: GNU GPL version 3 or later 
>  with many parts BSD . Please read LICENSE.
>  Based on sources from 20161112-ML-D.
>  Based on source from git with hash:
> Cannot find your hotkey definition file!
> This font contains both a 'kern' table and a 'GPOS' table.
>   The 'kern' table will only be read if there is no 'kern' feature in 'GPOS'.
> Use-my-metrics flag set on at least two components in glyph 685
> The glyph named Omega is mapped to U+03A9.
>   But its name indicates it should be mapped to U+2126.
> 
> I don't know the first two problems, but the last one is caused by a
> confusion between U+03A9 GREEK CAPITAL LETTER OMEGA and U+2126 OHM SIGN;
> in an Adobe name list used by fontforge for some strange reason the name
> "Omega" maps to the latter.  The list was apparently changed by Adobe some
> time ago, between fontforge 20120731 and 20161005.  A workaround is to
> explicitly use "Omega.greek".  There's some discussion at:
> https://github.com/fontforge/fontforge/issues/2920

Thanks for the report!

It luckily does not break the build nor cause visible problems AFAIK in
kodi.

We will see how it gets resolved at fontforge or at the font upstreams.

Cheers,
Balint

___
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#847490: unblock: ffmpeg/7:3.2.2-1

[Balint Reczey]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-CC: pkg-multimedia-maintainers@lists.alioth.debian.org

Please unblock package ffmpeg and please decrease the migration delay
to 2 days.

According to Andreas Cadhalpun ffmpeg maintainer it fixes the following
security issues:

1: https://trac.ffmpeg.org/ticket/5992
2: https://trac.ffmpeg.org/ticket/5994

Please see the debdiff attached.

Thanks,
Balint

unblock ffmpeg/7:3.2.2-1
diff -Nru ffmpeg-3.2.1/Changelog ffmpeg-3.2.2/Changelog
--- ffmpeg-3.2.1/Changelog	2016-11-26 03:12:05.0 +0100
+++ ffmpeg-3.2.2/Changelog	2016-12-06 00:28:58.0 +0100
@@ -1,6 +1,26 @@
 Entries are sorted chronologically from oldest to youngest within each release,
 releases are sorted from youngest to oldest.
 
+version 3.2.2:
+- ffserver: Check chunk size
+- Avoid using the term "file" and prefer "url" in some docs and comments
+- avformat/rtmppkt: Check for packet size mismatches
+- zmqsend: Initialize ret to 0
+- avcodec/flacdec: Fix undefined shift in decode_subframe()
+- avcodec/get_bits: Fix get_sbits_long(0)
+- avformat/ffmdec: Check media type for chunks
+- avcodec/flacdec: Fix signed integer overflow in decode_subframe_fixed()
+- avcodec/flacdsp_template: Fix undefined shift in flac_decorrelate_indep_c
+- avformat/oggparsespeex: Check frames_per_packet and packet_size
+- avformat/utils: Check start/end before computing duration in update_stream_timings()
+- avcodec/flac_parser: Update nb_headers_buffered
+- avformat/idroqdec: Check chunk_size for being too large
+- avcodec/me_cmp: Fix median_sad size
+- avformat/utils: Fix type mismatch
+- configure: check for strtoull on msvc
+- http: move chunk handling from http_read_stream() to http_buf_read().
+- http: make length/offset-related variables unsigned
+
 version 3.2.1:
 - avcodec/aac_adtstoasc_bsf: validate and forward extradata if the stream is already ASC
 - mss2: only use error correction for matching block counts
diff -Nru ffmpeg-3.2.1/configure ffmpeg-3.2.2/configure
--- ffmpeg-3.2.1/configure	2016-11-26 03:12:05.0 +0100
+++ ffmpeg-3.2.2/configure	2016-12-06 00:28:58.0 +0100
@@ -6271,6 +6271,7 @@
 EOF
 fi
 check_func strtoll || add_cflags -Dstrtoll=_strtoi64
+check_func strtoull || add_cflags -Dstrtoull=_strtoui64
 # the new SSA optimzer in VS2015 U3 is mis-optimizing some parts of the code
 # this flag should be re-checked on newer compiler releases and put under a
 # version check once its fixed
diff -Nru ffmpeg-3.2.1/debian/changelog ffmpeg-3.2.2/debian/changelog
--- ffmpeg-3.2.1/debian/changelog	2016-11-27 02:27:33.0 +0100
+++ ffmpeg-3.2.2/debian/changelog	2016-12-06 23:59:13.0 +0100
@@ -1,3 +1,12 @@
+ffmpeg (7:3.2.2-1) unstable; urgency=medium
+
+  * Import new upstream bugfix release 3.2.2.
+  * Fix log messages in autopkgtest.
+  * Enable frei0r on powerpcspe.
+  * Drop --disable-tesseract.
+
+ -- Andreas Cadhalpun <andreas.cadhal...@googlemail.com>  Tue, 06 Dec 2016 23:58:20 +0100
+
 ffmpeg (7:3.2.1-1) unstable; urgency=medium
 
   [ Balint Reczey ]
diff -Nru ffmpeg-3.2.1/debian/control ffmpeg-3.2.2/debian/control
--- ffmpeg-3.2.1/debian/control	2016-11-27 02:27:33.0 +0100
+++ ffmpeg-3.2.2/debian/control	2016-12-06 23:59:13.0 +0100
@@ -25,7 +25,7 @@
 # --enable-libflite
  flite1-dev,
 # --enable-frei0r
- frei0r-plugins-dev [!powerpcspe] ,
+ frei0r-plugins-dev ,
 # --enable-ladspa
  ladspa-sdk,
 # --enable-libass
diff -Nru ffmpeg-3.2.1/debian/rules ffmpeg-3.2.2/debian/rules
--- ffmpeg-3.2.1/debian/rules	2016-11-27 02:27:33.0 +0100
+++ ffmpeg-3.2.2/debian/rules	2016-12-06 23:59:13.0 +0100
@@ -47,7 +47,6 @@
 	--libdir=/usr/lib/$(DEB_HOST_MULTIARCH) \
 	--incdir=/usr/include/$(DEB_HOST_MULTIARCH) \
 	--enable-gpl \
-	--disable-libtesseract \
 	--disable-stripping \
 	--enable-avresample \
 	--enable-avisynth \
@@ -142,10 +141,10 @@
 		--disable-libopencv \
 		--disable-libx264
 else
-	CONFIG += --enable-libopencv
+	CONFIG += --enable-libopencv \
+		--enable-frei0r
 ifeq (,$(filter $(DEB_HOST_ARCH),powerpcspe))
-	CONFIG += --enable-frei0r \
-		--enable-libx264
+	CONFIG += --enable-libx264
 endif
 ifeq (,$(filter $(DEB_HOST_ARCH),sh4))
 	CONFIG += --enable-chromaprint
diff -Nru ffmpeg-3.2.1/debian/tests/encdec ffmpeg-3.2.2/debian/tests/encdec
--- ffmpeg-3.2.1/debian/tests/encdec	2016-11-27 02:27:33.0 +0100
+++ ffmpeg-3.2.2/debian/tests/encdec	2016-12-06 23:59:13.0 +0100
@@ -313,7 +313,7 @@
 else
 failures="${failures}${errmsg}\n"
 fi
-echo -e "FAILED: $errmsg\n\n"
+echo -e "\nFAILED: $errmsg\n\n"
 continue
 fi
 ret=0
@@ -326,7 +326,7 @@
 else
 failures="${failures}${errmsg}\n"
 fi
-echo -e "FAILED: $errmsg\n\n"
+echo -e "\nFAILED: $er

Bug#813940: forked-daapd: Fails to scrobble plays to lastfm

[Balint Reczey]

Control: fixed -1 24.2-1

On Wed, 9 Nov 2016 22:18:03 +0100 =?UTF-8?B?QsOhbGludCBSw6ljemV5?=
 wrote:
...
> 
> Hi Chris,
> 
> 2016-02-06 22:47 GMT+01:00 Chris Carr :
> > Package: forked-daapd
> > Version: 22.0-2
> > Severity: normal
> >
> > Dear Maintainer,
> >
> >* What led up to the situation?
> >
> > I played some songs and checked my lastfm profile
> >
> >* What exactly did you do (or not do) that was effective (or
> >  ineffective)?
> >
> > I followed the instructions to put my lastfm credentials into a temporary 
> > file
> > which would enable forked-daapd to obtain a lastfm session key when it 
> > started
> > up.
> >
> >* What was the outcome of this action?
> >
> > The log file (attached) shows that forked-daapd obtained a lastfm session 
> > key,
> > but none of my plays have been scrobbled.
> >
> >* What outcome did you expect instead?
> >
> > I expected each played track to be scrobbled, either as it finished, or 
> > every
> > hour, or something.
> 
> Upstream fixed the issue.

And I forgot closing this bug from the changelog. :-)

Cheers,
Balint

___
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#843166: kodi: block migration to testing untill all reverse dependencies are ready

[Balint Reczey]

Control: notfound -1 17.0~beta5+dfsg1-1

On Fri, 4 Nov 2016 11:58:21 -0300 Felipe Sateler <fsate...@debian.org>
wrote:
> On 4 November 2016 at 11:57, Bálint Réczey <bal...@balintreczey.hu> wrote:
> > Hi Felipe,
> >
> > 2016-11-04 15:50 GMT+01:00 Felipe Sateler <fsate...@debian.org>:
> >> On 4 November 2016 at 11:21, Balint Reczey <bal...@balintreczey.hu> wrote:
> >>> Source: kodi
> >>> Version: 17.0~beta5+dfsg1-1
> >>> Severity: grave
> >>>
> >>> To not break testing users' addon configuration I'm blocking kodi's
> >>> migration to testing until all addons are ready to migrate together.
> >>>
> >>> Close this bug when all reverse dependencies are ready.
> >>
> >> It seems to me that then kodi and the plugin should have stricter
> >> dependencies. Maybe kodi should Provides: kodi-plugin-$version and the
> >> plugins should Depend: on that?
> >
> > Yes, this is the plan and Tobias already offered implementing it later.

Tobias implemented providing various API versions in kodi and some
add-ons started using it already.
The rest of the addons will depend on the right API version with their
next upload.

Closing this bug since the kodi addons are ready.

Kodi can't yet migrate to testing due to mips* builds failing probably
because of a toolchain problem (#844227).

Cheers,
Balint

___
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#772347: xbmc: bashism in /bin/sh script

[Balint Reczey]

Control: fixed -1 15.1+dfsg1-3

On Mon, 8 Dec 2014 15:12:27 +0100 =?UTF-8?B?QsOhbGludCBSw6ljemV5?=
 wrote:
> Control: severity -1 important
> Control: tags -1 confirmed pending
> 
> Hi Raphael,
> 
> Thank you for the bug report.
> 
> 2014-12-06 15:34 GMT+01:00 Raphael Geissert :
> > Package: xbmc
> > Severity: serious
> > Version: 2:13.2+dfsg1-4
> > User: debian-rele...@lists.debian.org
> > Usertags: goal-dash
> >
> > Hi,
> >
> > I've ran checkbashisms (from the 'devscripts' package) over the whole
> > archive and I found that your package has a /bin/sh script that uses a
> > "bashism".
> >
> > checkbashisms' output:
> >> possible bashism in ./usr/bin/xbmc line 81 (should be >word 2>&1):
> >> if which systemd-coredumpctl &> /dev/null; then
> >> possible bashism in ./usr/bin/xbmc line 82 (should be >word 2>&1):
> >>   systemd-coredumpctl dump -o core xbmc.bin &> /dev/null
> Those are bashisms indeed, but they are harmless IMO.
> I will include the fix in next upload, but since the package is quite
> big I wouldn't like to prepare an upload just to fix this bug.

The issue has been fixed in Kodi.

Cheers,
Balint

___
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#751634: /usr/lib/xbmc/xbmc.bin: XBMC aborts when scrolling over some directory

[Balint Reczey]

Control: fixed -1 17.0~beta5+dfsg1-1

On Sun, 15 Jun 2014 16:38:32 -0700 =?UTF-8?B?QsOhbGludCBSw6ljemV5?=
 wrote:
> Hi Sjors,
> 
> 2014-05-30 16:40 GMT-07:00 Sjors Gielen :
> > Package: xbmc-bin
> > Version: 2:11.0~git20120510.82388d5-1+b1
> > Severity: important
> > File: /usr/lib/xbmc/xbmc.bin
> >
> > Since upgrading from Wheezy to Jessie, xbmc has started to crash (sometimes
> > SIGABRT, sometimes SIGSEGV) while scrolling through a directory of videos 
> > that
> > previously worked fine. The specific directory it crashes on tends to 
> > change a
> > bit, but there is one that has always made XBMC crash until now. Next to the
> > crash itself, this also means I cannot scroll past the directory in 
> > question,
> > unless I connect a mouse, therefore filing as important.
> Are you sure you performed a full upgrade? The package versions makes
> me think that you are still using Wheezy.
> The version shipped in Wheezy is not supported by upstream for a long time.
> If you would like to use xbmc on Wheezy please consider using the
> version available in wheezy-backports.

Closing due to no activity for years.
The bug if ever existed is probably gone.

Cheers,
Balint

___
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#843166: kodi: block migration to testing untill all reverse dependencies are ready

[Balint Reczey]

Source: kodi
Version: 17.0~beta5+dfsg1-1
Severity: grave

To not break testing users' addon configuration I'm blocking kodi's
migration to testing until all addons are ready to migrate together.

Close this bug when all reverse dependencies are ready.

Cheers,
Balint

___
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#816907: kodi: Crashes on shutdown

[Balint Reczey]

Control: fixed -1 17.0~beta5+dfsg1-1

On Sun, 06 Mar 2016 15:31:34 +0100 Valery Melou 
wrote:
> Package: kodi
> Version: 15.2+dfsg1-3
> Severity: normal
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>   I cliked on the shutdown button.
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>   The shutdown was effective but created a kodi_crashlog file in my home 
> folder.
>* What was the outcome of this action?
>   The creation of that crash log file.
>* What outcome did you expect instead?
>   I expected the app to close without creating that file.

This seems to be fixed in latest version.

Cheers,
Balint

___
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#831591: ffmpeg: kodi crash

[Balint Reczey]

Control: forwarded -1 https://github.com/xbmc/xbmc/pull/10846
Control: tags -1 upstream


Hi Andreas,

On Fri, 14 Oct 2016 01:27:47 +0200 Andreas Cadhalpun
 wrote:
...

> 
> Hi,
> 
> The relevant backtrace from the kodi_crashlog is:
> 
> Thread 1 (Thread 0x7f1b6bffe700 (LWP 16893)):
> #0  0x7f1ba92991c8 in __GI_raise (sig=sig@entry=6) at 
> ../sysdeps/unix/sysv/linux/raise.c:54
> #1  0x7f1ba929a64a in __GI_abort () at abort.c:89
> #2  0x7f1ba92d4f4a in __libc_message (do_abort=do_abort@entry=2, 
> fmt=fmt@entry=0x7f1ba93cdb30 "*** Error in `%s': %s: 0x%s ***\n") at 
> ../sysdeps/posix/libc_fatal.c:175
> #3  0x7f1ba92da6b6 in malloc_printerr (action=3, str=0x7f1ba93ca909 
> "free(): invalid pointer", ptr=, ar_ptr=) at 
> malloc.c:5004
> #4  0x7f1ba92dae9e in _int_free (av=0x7f1ba9601b20 , 
> p=, have_lock=0) at malloc.c:3865
> #5  0x7f1baa6d4a9d in av_buffer_unref () from 
> /usr/lib/x86_64-linux-gnu/libavutil.so.55
> #6  0x7f1baa6e15d2 in av_frame_unref () from 
> /usr/lib/x86_64-linux-gnu/libavutil.so.55
> #7  0x7f1bab93cf10 in avcodec_decode_video2 () from 
> /usr/lib/x86_64-linux-gnu/libavcodec.so.57
> #8  0x0090b26c in CDVDDemuxFFmpeg::ParsePacket(AVPacket*) ()
> #9  0x0090d0c2 in CDVDDemuxFFmpeg::Read() ()
> #10 0x01079b53 in CDVDPlayer::ReadPacket(DemuxPacket*&, 
> CDemuxStream*&) ()
> #11 0x0107ecd7 in CDVDPlayer::Process() ()
> #12 0x012103ff in CThread::Action() ()
> #13 0x012106bf in CThread::staticThread(void*) ()
> #14 0x7f1bb23e5464 in start_thread (arg=0x7f1b6bffe700) at 
> pthread_create.c:333
> #15 0x7f1ba934d30d in clone () at 
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> 
> Looking at the ParsePacket function reveals [1]:
> AVFrame picture;
> memset(, 0, sizeof(AVFrame));
> picture.pts = picture.pkt_dts = picture.pkt_pts = 
> picture.best_effort_timestamp = AV_NOPTS_VALUE;
> picture.pkt_pos = -1;
> picture.key_frame = 1;
> picture.format = -1;
> 
> This is using non-public ABI, e.g. the size of AVFrame, while the 
> documentation
> explicitly says "sizeof(AVFrame) is not a part of the public ABI" [2].
> What's worse is that it doesn't use av_frame_alloc as required [3]:
> "AVFrame must be allocated using av_frame_alloc()."
> 
> The whole block quoted above should be replaced with:
> AVFrame *picture = av_frame_alloc().
> 
> Then the following code should use picture instead of :
> avcodec_decode_video2(st->codec, picture, _picture, pkt);
> 
> And at the end it can be freed (instead of using av_frame_unref) with:
> av_frame_free();
> 
> In the experimental kodi branch there is another occurrence of this bug
> in xbmc/cores/VideoPlayer/VideoRenderers/HwDecRender/MMALRenderer.cpp.

Thank you for the triaging and extensive description of the problem.
I have now forwarded the patch to upstream under your name since I did
not really add anything to the patch.

> 
> Best regards,
> Andreas
> 
> 
> 1: 
> https://anonscm.debian.org/cgit/pkg-multimedia/kodi.git/tree/xbmc/cores/dvdplayer/DVDDemuxers/DVDDemuxFFmpeg.cpp?id=8d5cf423001aa4e7f850c20b158b2811e637e607#n1665
> 2: 
> https://anonscm.debian.org/cgit/pkg-multimedia/ffmpeg.git/tree/libavutil/frame.h?id=87b93f4e3ee2b6253ab9f5a166860a1ff18877d5#n174
> 3: 
> https://anonscm.debian.org/cgit/pkg-multimedia/ffmpeg.git/tree/libavutil/frame.h?id=87b93f4e3ee2b6253ab9f5a166860a1ff18877d5#n154
> 
> 

___
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#838051: kodi: Embedded libsquish library now available in debian

[Balint Reczey]

Control: notfound -1 17.0~alpha3+dfsg1-1
Control: found -1  16.1+dfsg1-2

Hi Wookey,

On Mon, 26 Sep 2016 11:46:50 +0200 =?UTF-8?B?QsOhbGludCBSw6ljemV5?=
 wrote:
> Hi Wookey,
> 
> 2016-09-25 0:49 GMT+02:00 Wookey :
> > On 2016-09-24 14:14 +0200, Bálint Réczey wrote:
> >> Control: tags -1 upstream fixed-upstream pending
> >> Control: notfound -1 17.0~alpha3+dfsg1-1
> >>
> >> Hi Wookey,

> >>
> >> 2016-09-17 2:26 GMT+02:00 Wookey :
> >
> >> > The changes have also been sent upstream and will hopefully appear
> >> > in libsquish 1.14 at some point.
> >
> > This has now happened, so I just uploaded 1.14. (no functional changes over 
> > 1.13-3)
> >
> >> Thank you for packaging libsquish.
> >> Kodi upstream dropped many embedded code copies recently including
> >> libsquish in 17.x.
> >> Experimental already has a kodi version without libsquish.
> >
> > You mean that it doesn't actually use it any more?
> 
> Yes, upstream stopped using it before the removal:
> 
> commit 7d9b190a0a87a23ad2108889b20840be9b759fb8
> Author: Stefan Saraev 
> Date:   Sun Feb 7 22:02:38 2016 +0200
> 
> [guilib] remove libsquish usage
> ---
>  xbmc/guilib/DDSImage.cpp | 86
> ++
>  xbmc/guilib/DDSImage.h   | 21 -
>  xbmc/guilib/Texture.cpp  | 41 
> ++---
>  xbmc/guilib/TextureBundleXBT.cpp |  5 ++---
>  4 files changed, 26 insertions(+), 127 deletions(-)

Kodi 17 is now in unstable, this bug can be closed.

Cheers,
Balint

___
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#833841: kodi: Checks fail at TestSystemInfo.GetOsVersion when building package

[Balint Reczey]

Control: fixed -1 17.0~alpha3+dfsg1-1

Hi,

On Tue, 9 Aug 2016 13:02:39 +0200 Simon Frei  wrote:
> In the meantime I realised there is already a patch for the tests, so I 
> updated it such that it works in my case (see attached patch).

Thank you for the report and the patch.
The build is not failing now for failing tests thus I think we don't
need to patch this failing test out.

Cheers,
Balint

___
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#818201: marked as pending

[Balint Reczey]

Hi,

On Sat, 24 Sep 2016 13:36:07 + Balint Reczey
<bal...@balintreczey.hu> wrote:
> tag 818201 pending
> thanks
> 
> Hello,
> 
> Bug #818201 reported by you has been fixed in the Git repository. You can
> see the changelog below, and you can check the diff of the fix at:
> 
> http://git.debian.org/?p=pkg-multimedia/kodi.git;a=commitdiff;h=a979624

I plan uploading kodi 17 beta4 to unstable next week which will fix this
bug.

Cheers,
Balint

___
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#839686: forked-daapd: does not recreate stuff in /var/cache after deletion

[Balint Reczey]

Control: notfound -1 24.1-1+b1

Hi Dominik,

On Mon, 03 Oct 2016 23:23:26 +0200 Dominik George  wrote:
> Package: forked-daapd
> Version: 24.1-1+b1
> Severity: serious
> Justification: Policy 9.1.1
> 
> After deleting /var/cache/forked-daapd, forked-daapd cannot start up
> again because it fails to open the database.
> 
> forked-daapd seems to require its data files there, while the FHS
> unmistakably states:
> 
> "Unlike /var/spool, the cached files can be deleted without data loss.
> The data must remain valid between invocations of the application and
> rebooting the system.
> 
> Files located under /var/cache may be expired in an application specific
> manner, by the system administrator, or both. The application must
> always be able to recover from manual deletion of these files (generally
> because of a disk space shortage). No other requirements are made on the
> data format of the cache directories."

I have tested unstable's forked-daapd and if I remove cache files they
get recreated but the directory structure is not.

IMO it is unreasonable to think that removing the whole
/var/cache/forked-daapd directory can be deleted and is expected to be
recreated because many services drop root privileges thus can't create
dirs in /var/cache:

total 64
drwxr-xr-x 16 root  root 4096 Oct  6 20:56 .
drwxr-xr-x 11 root  root 4096 Sep  5 23:27 ..
drwxr-xr-x  3 root  root 4096 Sep  7 14:08 app-info
drwxr-xr-x  3 root  root 4096 Oct  6 20:56 apt
drwxr-xr-x  2 root  root 4096 Sep  7 14:08 cracklib
drwxr-xr-x  2 root  root 4096 Oct  5 09:25 debconf
drwxr-xr-x  2 root  root 4096 Sep  5 23:28 dictionaries-common
drwxr-xr-x  2 root  root 4096 Sep  8 20:40 fontconfig
drwxr-xr-x  2 root  root 4096 Feb 22  2016 fonts
drwxr-xr-x  2 daapd root 4096 Oct  6 21:01 forked-daapd
drwxr-xr-x  2 root  root 4096 Aug 31 08:28 gdm
drwx--  2 root  root 4096 Oct  6 20:56 ldconfig
drwx--x--x  3 root  root 4096 Sep  7 15:39 lightdm
drwxr-sr-x 37 man   root 4096 Oct  6 21:00 man
drwxr-xr-x  3 root  root 4096 Sep  7 14:08 PackageKit
drwxr-xr-x  2 root  root 4096 Aug 15 11:17 realmd

In my interpretation of the FHS the _files_ can be removed and are
expected to be recreated, while _directory structures_ need to be kept
for applications to operate.

Cheers,
Balint

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

Wheezy update of mpg123?

[Balint Reczey]

Hello dear maintainer(s),

the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of mpg123:
https://security-tracker.debian.org/tracker/source-package/mpg123

Would you like to take care of this yourself?

If yes, please follow the workflow we have defined here:
https://wiki.debian.org/LTS/Development

If that workflow is a burden to you, feel free to just prepare an
updated source package and send it to debian-...@lists.debian.org
(via a debdiff, or with an URL pointing to the source package,
or even with a pointer to your packaging repository), and the members
of the LTS team will take care of the rest. Indicate clearly whether you
have tested the updated package or not.

If you don't want to take care of this update, it's not a problem, we
will do our best with your package. Just let us know whether you would
like to review and/or test the updated package before it gets released.

You can also opt-out from receiving future similar emails in your
answer and then the LTS Team will take care of mpg123 updates
for the LTS releases. (In case we don't get any answer for months,
we may also take it as an opt-out, too.)

Thank you very much.

Balint Reczey,
  on behalf of the Debian LTS team.

PS: A member of the LTS team might start working on this update at
any point in time. You can verify whether someone is registered
on this update in this file:
https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup

___
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#838519: jack-audio-connection-kit: new upstream release

[Balint Reczey]

Control: fixed -1 1:0.125.0-1

On Wed, 21 Sep 2016 22:30:03 +0200 (CEST)
=?utf-8?q?Jarom=C3=ADr_Mike=C5=A1?=  wrote:
> Package: jack-audio-connection-kit
> Version: 1:0.124.1+20140122git5013bed0-3
> Severity: normal
> 
> Dear Maintainer,
> 
> There is new upstream release 0.125.0 ... please update.
> https://github.com/jackaudio/jack1

Done in latest upload.

Cheers,
Balint

___
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#837566: mjpegtools: FTBFS with bindnow and PIE enabled

[Balint Reczey]

Source: mjpegtools
Version: 2.1.0+debian-4
Severity: important
User: bal...@balintreczey.hu
Usertags: pie-bindnow-20160906
Justification: FTBFS on amd64 with extra hardening

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64 with patched GCC and dpkg.

The rebuild tested if packages are ready for a transition
enabling PIE and bindnow for amd64.

For more information about the changes to sid's dpkg and GCC please
visit:
 https://wiki.debian.org/Hardening/PIEByDefaultTransition

Relevant part (hopefully):
...
gcc -DHAVE_CONFIG_H -I. -I..  -I.. -I../utils -Wdate-time
-D_FORTIFY_SOURCE=2 -fno-PIC -g -O2
-fdebug-prefix-map=/<>/mjpegtools-2.1.0+debian=.
-fstack-protector-strong -Wformat -Werror=format-security -pthread -Wall
-Wunused -c -o yuvscaler-yuvscaler_resample.o `test -f
'yuvscaler_resample.c' || echo './'`yuvscaler_resample.c
gcc -DHAVE_CONFIG_H -I. -I..  -I.. -I../utils -Wdate-time
-D_FORTIFY_SOURCE=2 -fno-PIC -g -O2
-fdebug-prefix-map=/<>/mjpegtools-2.1.0+debian=.
-fstack-protector-strong -Wformat -Werror=format-security -pthread -Wall
-Wunused -c -o yuvscaler-yuvscaler_bicubic.o `test -f
'yuvscaler_bicubic.c' || echo './'`yuvscaler_bicubic.c
/bin/bash ../libtool  --tag=CC   --mode=link gcc -fno-PIC -g -O2
-fdebug-prefix-map=/<>/mjpegtools-2.1.0+debian=.
-fstack-protector-strong -Wformat -Werror=format-security -pthread -Wall
-Wunused  -Wl,-z,relro -Wl,-z,now -o yuvscaler yuvscaler-yuvscaler.o
yuvscaler-yuvscaler_resample.o yuvscaler-yuvscaler_bicubic.o
../utils/libmjpegutils.la  -lm  -lm libtool: link: gcc -fno-PIC -g -O2
-fdebug-prefix-map=/<>/mjpegtools-2.1.0+debian=.
-fstack-protector-strong -Wformat -Werror=format-security -pthread -Wall
-Wunused -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/yuvscaler
yuvscaler-yuvscaler.o yuvscaler-yuvscaler_resample.o
yuvscaler-yuvscaler_bicubic.o  ../utils/.libs/libmjpegutils.so -lm -pthread
/usr/bin/ld: yuvscaler-yuvscaler.o: relocation R_X86_64_32 against
`.rodata.str1.8' can not be used when making a shared object; recompile
with -fPIC
/usr/bin/ld: yuvscaler-yuvscaler_resample.o: relocation R_X86_64_32
against `.rodata.str1.8' can not be used when making a shared object;
recompile with -fPIC
/usr/bin/ld: yuvscaler-yuvscaler_bicubic.o: relocation R_X86_64_32
against `.rodata.str1.8' can not be used when making a shared object;
recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
Makefile:441: recipe for target 'yuvscaler' failed
make[3]: *** [yuvscaler] Error 1
make[3]: Leaving directory '/<>/mjpegtools-2.1.0+debian/yuvscaler'
Makefile:572: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/mjpegtools_2.1.0+debian-4_amd64.build.gz

Thanks,
Balint

___
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#837423: jack-audio-connection-kit: Please build libjack.a with -fPIC

[Balint Reczey]

Source: jack-audio-connection-kit
Version: 1:0.124.1+20140122git5013bed0-3
Severity: important
User: bal...@balintreczey.hu
Usertags: pie-bindnow-20160906
Justification: makes espeakup FTBFS on amd64 with extra hardening
Affects: espeakup

Dear Maintainers,

During a rebuild of all packages in sid, espeakup failed to build on
amd64 with patched GCC and dpkg. The root cause seems to be that
libjack.a is shipped as a non-PIC library.

The rebuild tested if packages are ready for a transition
enabling PIE and bindnow for amd64.

For more information about the changes to sid's dpkg and GCC please
visit:
 https://wiki.debian.org/Hardening/PIEByDefaultTransitio

Relevant part of espeakup's build log:
...
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-secur
ity -Os -MMD -Wall   -c -o stringhandling.o stringhandling.c
cc -u _Unwind_Resume -u __gcc_personality_v0 -u _Unwind_ForcedUnwind -u
_Unwind_GetCFA -u _Unwind_GetB
SP -lgcc_s  espeakup.o cli.o espeak.o queue.o signal.o softsynth.o
stringhandling.o  /usr/lib/x86_64-l
inux-gnu/libespeak.a /usr/lib/x86_64-linux-gnu/libsonic.a
/usr/lib/x86_64-linux-gnu/libportaudio.a /us
r/lib/x86_64-linux-gnu/libjack.a -lm -lpthread -lasound -lrt -o espeakup
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libportaudio.a(pa_front.o):
relocation R_X86_64_32 against `.ro
data.str1.8' can not be used when making a shared object; recompile with
-fPIC
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libportaudio.a(pa_unix_util.o):
relocation R_X86_64_32 against
`.rodata' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libportaudio.a(pa_linux_alsa.o):
relocation R_X86_64_32 against
 `.rodata.str1.8' can not be used when making a shared object; recompile
with -fPIC
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libportaudio.a(pa_jack.o):
relocation R_X86_64_32 against `.rod
ata' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libportaudio.a(pa_unix_oss.o):
relocation R_X86_64_32 against `.rodata.str1.8' can not be used when
making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libportaudio.a(pa_converters.o):
relocation R_X86_64_32S against `.rodata' can not be used when making a
shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libportaudio.a(pa_cpuload.o):
relocation R_X86_64_32 against `.rodata' can not be used when making a
shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libportaudio.a(pa_process.o):
relocation R_X86_64_32 against `.rodata' can not be used when making a
shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libjack.a(libjack_la-client.o):
relocation R_X86_64_32 against `.rodata.str1.1' can not be used when
making a shared object; recompile with -fPIC
/usr/bin/ld:
/usr/lib/x86_64-linux-gnu/libjack.a(libjack_la-messagebuffer.o):
relocation R_X86_64_32S against `.bss' can not be used when making a
shared object; recompile with -fPIC
/u
...

The full build log is available from:
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/espeakup_0.80-1_amd64.build.gz

Thanks,
Balint


diff -u binutils-2.27/debian/changelog binutils-2.27/debian/changelog
--- binutils-2.27/debian/changelog
+++ binutils-2.27/debian/changelog
@@ -1,3 +1,10 @@
+binutils (2.27-8+rbalint0) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Build libbfd with -fPIC
+
+ -- Balint Reczey <bal...@balintreczey.hu>  Sat, 10 Sep 2016 15:53:07 +0200
+
 binutils (2.27-8) unstable; urgency=medium
 
   * Fix diversion updates for 32bit x86 targets.
diff -u binutils-2.27/debian/patches/series binutils-2.27/debian/patches/series
--- binutils-2.27/debian/patches/series
+++ binutils-2.27/debian/patches/series
@@ -12,6 +12,7 @@
 130_gold_disable_testsuite_build.patch
 131_ld_bootstrap_testsuite.patch
 135_bfd_version.patch
+136_bfd_pic.patch
 157_ar_scripts_with_tilde.patch
 #158_ld_system_root.patch
 161_gold_dummy_zoption.diff
only in patch2:
unchanged:
--- binutils-2.27.orig/debian/patches/136_bfd_pic.patch
+++ binutils-2.27/debian/patches/136_bfd_pic.patch
@@ -0,0 +1,25 @@
+Author: Balint Reczey <bal...@balintreczey.hu>
+Description: Build libbfd with -fPIC to allow linking with PIE binaries
+
+--- ./bfd/Makefile.am.bak	2016-09-10 16:26:46.062371030 +0200
 ./bfd/Makefile.am	2016-09-10 16:27:48.913724681 +0200
+@@ -51,7 +51,7 @@
+ 
+ WARN_CFLAGS = @WARN_CFLAGS@
+ NO_WERROR = @NO_WERROR@
+-AM_CFLAGS = $(WARN_CFLAGS) $(ZLIBINC)
++AM_CFLAGS = $(WARN_CFLAGS) $(ZLIBINC) -fPIC
+ AM_CPPFLAGS = -DBINDIR='"$(bindir)"'
+ if PLUGINS
+ bfdinclude_HEADERS += $(INCDIR)/plugin-api.h
+--- ./bfd/Makefile.in.bak	2016-09-10 16:26:53.009857349 +0200
 ./bfd/Makefile.in	2016-09-10 16:27:31.886983240 +0200
+@@ -387,7 +387,7 @@
+ # case both are empty.
+ ZLIB = @zlibdir@ -lz
+ ZLIBINC = @zlibinc@
+-AM_CFLAGS = $(WARN_CFLAGS) $(ZLIBINC)
++AM_CFLAGS = $(W

Bug#820416: kodi: FTBFS in testing (Segmentation fault)

[Balint Reczey]

Control: severity -1 normal
Control: tags -1 upstream confirmed

Hi Santiago,

2016-04-16 18:43 GMT+02:00 Santiago Vila :
> I've put the program kodi-test here:
>
> https://people.debian.org/~sanvila/bug-820416/kodi-test.gz
>
> It was built on a stretch chroot today (for amd64).
>
> To reproduce the segfault, just install the build-dependencies for
> kodi, i.e. on a stretch chroot, please do:
>
> apt-get build-dep kodi
>
> then try to execute kodi-test:
>
> ./kodi-test
>
> This is all you need to reproduce the problem.

Thank you for the bug report and the additional information.

I have just created a chroot for reproducing the issue and even after I
set memory limits it did not crash.
I also built kodi-test myself which did not crash either.

root@stretch:/kodi-16.1~rc2+dfsg1# ulimit -a
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 30616
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) 2048000
open files  (-n) 65536
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 30616
virtual memory  (kbytes, -v) 4096000
file locks  (-x) unlimited

./kodi-test-dloaded
...
[--] Global test environment tear-down
[==] 574 tests from 89 test cases ran. (9800 ms total)
[  PASSED  ] 574 tests.
Clean shutdown of TestGlobalPattern1

Valgrind found a few issues in Google Test, but nothing extraordinary:
...
==21850== Use of uninitialised value of size 8
==21850==at 0xFAF6201: _itoa_word (in /lib/x86_64-linux-gnu/libc-2.22.so)
==21850==by 0xFAF998C: vfprintf (in /lib/x86_64-linux-gnu/libc-2.22.so)
==21850==by 0xFB23258: vsnprintf (in /lib/x86_64-linux-gnu/libc-2.22.so)
==21850==by 0xFB00D11: snprintf (in /lib/x86_64-linux-gnu/libc-2.22.so)
==21850==by 0x130A48A: testing::(anonymous 
namespace)::PrintByteSegmentInObjectTo(unsigned char const*, unsigned long, 
unsigned long, std::ostream*) [clone .constprop.392] (gtest-printers
.cc:72)
==21850==by 0x130E6EC: PrintBytesInObjectToImpl (gtest-printers.cc:90)
==21850==by 0x130E6EC: testing::internal2::PrintBytesInObjectTo(unsigned 
char const*, unsigned long, std::ostream*) (gtest-printers.cc:112)
==21850==by 0x134E4A2: PrintValue (gtest-printers.h:136)
==21850==by 0x134E4A2: operator<<  
(gtest-printers.h:201)
==21850==by 0x134E4A2: DefaultPrintNonContainerTo 
(gtest-printers.h:245)
==21850==by 0x134E4A2: DefaultPrintTo (gtest-printers.h:338)
==21850==by 0x134E4A2: PrintTo (gtest-printers.h:376)
==21850==by 0x134E4A2: Print (gtest-printers.h:600)
==21850==by 0x134E4A2: UniversalPrint (gtest-printers.h:756)
==21850==by 0x134E4A2: Print (gtest-printers.h:684)
==21850==by 0x134E4A2: PrintToString (gtest-printers.h:849)
==21850==by 0x134E4A2: 
testing::internal::ParameterizedTestCaseInfo::RegisterTests() 
(gtest-param-util.h:508)
==21850==by 0x130BC44: RegisterTests (gtest-param-util.h:602)
==21850==by 0x130BC44: 
testing::internal::UnitTestImpl::RegisterParameterizedTests() (gtest.cc:2290)
==21850==by 0x1322ED8: 
testing::internal::UnitTestImpl::PostFlagParsingInit() (gtest.cc:4125)
==21850==by 0x132C034: void 
testing::internal::InitGoogleTestImpl(int*, char**) (gtest.cc:4991)
==21850==by 0x8461B6: main (xbmc-test.cpp:40)
...

OTOH in a VirtualBox VM limited to 2GB of RAM i was able to
reproduce the crash and got a meaningful backtrace:
...
#0  __GI___pthread_mutex_lock (mutex=mutex@entry=0x140) at 
../nptl/pthread_mutex_lock.c:68
__PRETTY_FUNCTION__ = "__pthread_mutex_lock"
type = 
id = 
#1  0x014b08b4 in XbmcThreads::pthreads::RecursiveMutex::lock 
(this=0x140) at 
/home/vagrant/kodi-16.1~rc2+dfsg1/xbmc/threads/platform/pthreads/CriticalSection.h:49
No locals.
#2  XbmcThreads::CountingLockable::lock 
(this=0x140) at /home/vagrant/kodi-16.1~rc2+dfsg1/xbmc/threads/Lockables.h:60
No locals.
#3  XbmcThreads::UniqueLock::UniqueLock (lockable=..., 
this=) at 
/home/vagrant/kodi-16.1~rc2+dfsg1/xbmc/threads/Lockables.h:127
No locals.
#4  CSingleLock::CSingleLock (cs=..., this=) at 
/home/vagrant/kodi-16.1~rc2+dfsg1/xbmc/threads/SingleLock.h:38
No locals.
#5  XbmcThreads::CEventGroup::Set (child=0x7ffc9df57090, this=0xe0) at 
Event.h:122
No locals.
#6  CEvent::Set (this=this@entry=0x7ffc9df57090) at Event.cpp:80
iter =
l = { = 
{ = {}, mutex = @0x7ffc9df57098, owns 
= true}, }
#7  0x014b2d09 in CThread::staticThread (data=0x7ffc9df56fc0) at 
Thread.cpp:137
pThread = 0x7ffc9df56fc0
name = "AlarmClock"
id = 

Bug#820416: kodi: FTBFS in testing (Segmentation fault)

[Balint Reczey]

Control: tags -1 unreproducible
Control: notfound -1 16.1~rc2+dfsg1-1

Hi Santiago,

On Fri, 8 Apr 2016 00:21:34 +0200 (CEST) Santiago Vila 
wrote:
> 
> Dear maintainer: This package fails to build from source in stretch.
> 
> The error happens while doing the tests:
> 
> 
> [--] 1 test from TestAsyncFileCopy
> [ RUN  ] TestAsyncFileCopy.General
> /bin/bash: line 1: 21695 Segmentation fault  
> /<>/kodi-16.1~rc2+dfsg1/$check_program
> Makefile:608: recipe for target 'check' failed
> make[1]: *** [check] Error 139
> make[1]: Leaving directory '/<>/kodi-16.1~rc2+dfsg1'
> dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
> debian/rules:81: recipe for target 'build' failed
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> 

I have just tested building the package in a clean Stretch chroot using
sbuild and it built fine.
The probloblem may not be reliably reproducible or got fixed in an other
package.

Cheers,
Balint

___
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#816251: kodi-pvr-vdr-vnsi: FTBFS: VNSIData.cpp:430:7: error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'

[Balint Reczey]

Control: fixed -1 1.11.15-1

On Mon, 29 Feb 2016 07:53:05 + Chris Lamb  wrote:
> Source: kodi-pvr-vdr-vnsi
> Version: 1.10.10-2
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> kodi-pvr-vdr-vnsi fails to build from source in unstable/amd64:
> 
>   [..]
> 
>dpkg-buildpackage -rfakeroot -D -us -uc -b
>   dpkg-buildpackage: source package kodi-pvr-vdr-vnsi

___
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#816507: kodi: Wait for PVR addon updates with the migration to testing

[Balint Reczey]

Control: notfound -1 16.0+dfsg1-1

Let it migrate since kodiplatform just migrated.

On Wed, 2 Mar 2016 13:31:45 +0100 Balint Reczey <bal...@balintreczey.hu>
wrote:
> Package: kodi
> Version: 16.0+dfsg1-1
> Severity: serious
> 
> Hi,
> 
> This bug is for preventing the migration of kodi to testing before PVR
> addons are also ready.
> 
> Cheers,
> Balint
> 
> 

___
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#816580: kodi-pvr-dvbviewer: FTBFS: DvbData.cpp:301:9: error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'

[Balint Reczey]

Control: fixed -1 1.11.11+git20160220-1


On Thu, 03 Mar 2016 08:33:37 + Chris Lamb  wrote:
...
> Dear Maintainer,
> 
> kodi-pvr-dvbviewer fails to build from source in unstable/amd64:
> 
>   
> /home/lamby/temp/cdt.20160303080342.kJYepBFIIF/kodi-pvr-dvbviewer-1.10.35+git20150717/src/DvbData.cpp:
>  In member function 'bool Dvb::GetTimers(ADDON_HANDLE)':
>   
> /home/lamby/temp/cdt.20160303080342.kJYepBFIIF/kodi-pvr-dvbviewer-1.10.35+git20150717/src/DvbData.cpp:301:9:
>  error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
>tag.bIsRepeating  = (timer->weekdays != 0);
>^
>   CMakeFiles/pvr.dvbviewer.dir/build.make:89: recipe for target 
> 'CMakeFiles/pvr.dvbviewer.dir/src/DvbData.cpp.o' failed
>   make[3]: *** [CMakeFiles/pvr.dvbviewer.dir/src/DvbData.cpp.o] Error 1
>   make[3]: Leaving directory 
> '/home/lamby/temp/cdt.20160303080342.kJYepBFIIF/kodi-pvr-dvbviewer-1.10.35+git20150717/obj-x86_64-linux-gnu'
>   CMakeFiles/Makefile2:102: recipe for target 
> 'CMakeFiles/pvr.dvbviewer.dir/all' failed
>   make[2]: *** [CMakeFiles/pvr.dvbviewer.dir/all] Error 2
>   make[2]: Leaving directory 
> '/home/lamby/temp/cdt.20160303080342.kJYepBFIIF/kodi-pvr-dvbviewer-1.10.35+git20150717/obj-x86_64-linux-gnu'
>   Makefile:152: recipe for target 'all' failed
>   make[1]: *** [all] Error 2
>   make[1]: Leaving directory 
> '/home/lamby/temp/cdt.20160303080342.kJYepBFIIF/kodi-pvr-dvbviewer-1.10.35+git20150717/obj-x86_64-linux-gnu'
>   dh_auto_build: make -j1 returned exit code 2
>   debian/rules:12: recipe for target 'build' failed
>   make: *** [build] Error 2
> 
>   [..]
Thanks, fixed in last upload.

Cheers,
Balint

___
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#816507: kodi: Wait for PVR addon updates with the migration to testing

[Balint Reczey]

Package: kodi
Version: 16.0+dfsg1-1
Severity: serious

Hi,

This bug is for preventing the migration of kodi to testing before PVR
addons are also ready.

Cheers,
Balint

___
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#810224: /usr/bin/avconv: ogg format: unable to use pass and quality? options together

[Balint Reczey]

Hi Carl,

On Thu, 25 Feb 2016 13:55:52 +0100 Carl Eugen Hoyos 
wrote:
> Hi!
> 
> When encoding with FFmpeg, you can either use fixed quality or fixed bitrate 
> (size), if you decide to use fixed bitrate, two-pass encoding improves the 
> output quality.
> It makes no sense to use two-pass constant quality encoding, the result of 
> using two contradicting options is undefined.
> 
> Please close this ticket as invalid.
I think if two options a contradicting then ffmpeg should refuse
accepting them instead of starting the conversion of the file.
IMHO this is a valid upstream bug, but upstream can decide to leave it
unfixed, of course.

What do you think?

Cheers,
Balint

___
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#815673: ffmpeg: VP9 seek broken in ffplay

[Balint Reczey]

Control: reassign -1 libvpx 1.5.0-2
Control: forwarded -1 https://chromium-review.googlesource.com/#/c/329320/
Control: tags -1 upstream

On Thu, 25 Feb 2016 13:52:34 +0100 Carl Eugen Hoyos  wrote:
> On Tuesday 23 February 2016 03:43:50 pm you wrote:
> > I have encoded a video as VP9 using ffmpeg with the following settings
> > and I am unable to seek forward in the video (tested with mpv and
> > ffplay).
> 
> This bug in libvpx is being fixed by setting a more useful default for 
> maximum key frame interval:
> https://chromium-review.googlesource.com/#/c/329320/
> 
> Please reassign this issue to the libvpx package.
Done.

Thanks for the triaging!

Cheers,
Balint

___
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#814026: ITP: dcadec -- DTS Coherent Acoustics decoder - shared library

[Balint Reczey]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: pkg-multimedia-maintainers@lists.alioth.debian.org

* Package name: dcadec
  Version : 0.2.0
* URL : https://github.com/foo86/dcadec
* License : LGPL-2.1
  Programming Lang: C
  Description : DTS Coherent Acoustics decoder - shared library

A free DTS Coherent Acoustics decoder with support for HD extensions.

Supported features:

  Decoding of standard DTS core streams with up to 5.1 channels
  Decoding of DTS-ES streams with discrete back channel
  Decoding of High Resolution streams with up to 7.1 channels and extended
  bitrate
  Decoding of 96/24 core streams
  Lossless decoding of Master Audio streams with up to 7.1 channels, 192 kHz
  Downmixing to stereo and 5.1 using embedded coefficients

Features not implemented:

  Decoding of DTS Express streams
  Applying dynamic range compression and dialog normalization

___
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#810186: kodi: diff for NMU version 15.2+dfsg1-1.1

[Balint Reczey]

Hi Gianfranco,

On Fri, 22 Jan 2016 10:21:59 + (UTC) Gianfranco Costamagna
 wrote:
> Control: tags 810186 + patch
> Control: tags 810186 + pending
> 
> 
> Dear maintainer,
> 
> I've prepared an NMU for kodi (versioned as 15.2+dfsg1-1.1) and
> uploaded it to DELAYED/6. Please feel free to tell me if I
> should delay it longer.
...
> - libpng12-dev | libpng-dev,
> + libpng-dev | libpng12-dev,
I have already prepared the fix in git and I'm waiting for libpng-dev to
become a non-virtual package.

>From Debian Policy 7.5 Virtual packages - Provides:
 To specify which of a set of real packages should be the default to
 satisfy a particular dependency on a virtual package, list the real
 package as an alternative before the virtual one.

Will libpng-deb still stay as a virtual package? I this case the
following change would be a better solution:
> + libpng16-dev | libpng-dev,

I expected libpng-dev to become a normal package and went with
> + libpng-dev,

What is the plan?

Cheers,
Balint

___
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#784578: xbmc: Can't play DVDs from nfs or samba shares

[Balint Reczey]

Control: tags -1 confirmed upstream
Control: forwarded -1 
http://forum.kodi.tv/showthread.php?tid=207088=2196885#pid2196885

Hi,
On Tue, 23 Jun 2015 10:53:41 +0200 Christa Brinkmann 
 wrote:
> Confirm issue:
> 
> Playing ISO DVD on SMB share does not work, while the same ISO on local
> storage plays find. Error in log is always dvdnav related.
> 
> Seems to be an old, "solved" issue:
> 
> http://forum.kodi.tv/showthread.php?tid=157925
It may be solved in Kodi's embedded libdvdread, but at the moment Kodi
tries to make system's libdvdread open the DVD from the URL used by
Kodi's virtual filesystem:
...
/tmp/kodi.trace.10250:open("nfs://1.2.3.4/dir/file.iso")", O_RDONLY) = -1 
ENOENT (No such file or directory)
...

Fixing the issue for system's libdvdread, too, seems to require changes to 
libdvdread's API and Kodi as well.
In the meantime please mount the NFS and Samba shares in fstab which makes 
opening the DVD-s working like opening
them from the local filesystem.

Cheers,
Balint

___
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#777041: xbmc: unable to disable extensive debug logging

[Balint Reczey]

Control: tags -1 + pending - wontfix

Hi Jonathan,

On Sun, 29 Nov 2015 22:48:48 + Jonathan McDowell  wrote:
> On Sun, Nov 29, 2015 at 07:48:42PM +0100, Bálint Réczey wrote:
> > 2015-11-29 19:24 GMT+01:00 Jonathan McDowell :
> > > On Fri, Nov 06, 2015 at 10:14:55AM +0400, Bálint Réczey wrote:
> > >> > Looking at my XBMC which was started less than 2 days ago and breaking
> > >> > down the log entry types I see:
> > >> >
> > >> >   9 WARNING:
> > >> >  78 ERROR:
> > >> > 320 INFO:
> > >> > 390 NOTICE:
> > >> >7366 DEBUG:
> > >> >
> > >> > This debug output is considerable compared to the normal output. I
> > >> > understand the desire to have the debugging enabled by default to ease
> > >> > support, but the GUI configuration should be showing this is the case
> > >> > and it should be possible to turn it off.
> > >
> > >> I think the situation improved a lot with latest kodi packages. Could
> > >> you please test them?
> > >>
> > >> Debugging is not enabled in debian/rules anymore by default.
> > >
> > > I'm running XBMC on a jessie box so I'm a bit wary about updating it
> > > all; are there any plans to update the backport.debian.org packages to
> > > 15.2 final rather than 15.2-rc3?
> 
> > They are practically the same[1] thus I did not find it important, but
> > I'll update it because probably there are numerous users waiting for
> > that.  I was also waiting for feedback on bugs like this one to see if
> > I have to make additional changes before I create the backport.
> 
> > It sould be nice if you could upgrade and test the current version to
> > see if this bug is still open.
> 
> I have upgraded to 15.2~rc3+dfsg1-1~bpo8+1 and I'm still seeing loads of
> debug output, including every keypress:
> 
> 22:34:52 T:140404543895616   DEBUG: OnKey: backspace (0xf008) pressed, action 
> is Back
> 
> All visible debug options in the GUI (System -> Debugging) are disabled.
Debugging was set on by default by upstream, but I have now disabled it by 
default[1].
The next upload will contain the fix.

Thanks for reporting the issue and testing it again!

Cheers,
Balint

[1] 
http://anonscm.debian.org/cgit/pkg-multimedia/kodi.git/commit/?id=fe87a47be53c6bd9cf55b26ff4c2d073156faa6a

___
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#769057: xbmc: using VDPAU, segfault when going full screen while playing certain videos

[Balint Reczey]

Hi Gedalya,

On Mon, 01 Dec 2014 20:32:48 -0500 Gedalya  wrote:
> On 11/30/2014 07:50 AM, Bálint Réczey wrote:
> > To me it looks similar to this Mesa bug:
> > https://bugs.freedesktop.org/show_bug.cgi?id=85613
> >
> > There is a suggestion for using latest firmware.
> > Could you please give the updated firmware a try from:
> > https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/
> >
> > Possibly the one shipped in firmware-linux-nonfree is outdated.
> >
> > Cheers,
> > Balint
> 
> Got a moment to try this just now. Updated /lib/firmware/radeon/* to 
> what is in git master. Same behavior.
> 
> Here are the firmwares I'm using in case that matters.
I have migrated this bug to kodi from xbmc. Are you still having this
issue with kodi from testing/unstable?

Cheers,
Balint

___
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#786989: xbmc: Eject/Load fails to eject my DVD

[Balint Reczey]

Control: tags -1 wontfix upstream
Control: severity -1 minor
Control: forwarded -1 http://forum.kodi.tv/showthread.php?tid=227908

Hi Stefan,

On Mon, 01 Jun 2015 22:35:00 -0400 Stefan Monnier
 wrote:
> >> Have you tried the solution from #709117?
> > I already have dev.cdrom.lock=0 in my sysctl, yes.
> > Also, I don't see anything like
> 
> >19:33:17 T:140173220951968   DEBUG: ExecuteXBMCAction : Translating 
> > EjectTray()
> >19:33:17 T:140173220951968   DEBUG: ExecuteXBMCAction : To EjectTray()
> 
> > in my log.  It seems XBMC is not even trying to eject the disc.
> 
> I found in http://forum.kodi.tv/showthread.php?tid=227908
> a solution to this problem that worked for me: I basically had to remove
> "--lock-media" from udev's 60-cdrom_id.rules.
> 
> I don't know if it qualifies as a real fix, or is just a workaround, but
> hopefully it will be enough for someone else to figure out what is the
> right fix.
Thank you for figuring out the workaround. I think there is no clear
category for this bug, but since you discussed it extensively on a Kodi
forum I set it as forwarded and since it could be fixed upstream I'm
also marking it upstream.
Upstream showed no significant interest in fixing it, hence the wontfix tag.

In case this gets fixed in newer releases please close this bug and mark
it as fixed.

Thanks,
Balint

___
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: Select provider of libav* libraries

[Balint Reczey]

On 05/24/2015 07:13 PM, Bálint Réczey wrote:
 Hi All,
 
 I have contacted Moritz asking him to share his opinion regarding
 FFmpeg/Libav. He is not on the list thus asked me to forward his
 email.
Moritz also suggested asking Mateusz Jurczyk.

Please see his email:

On 05/27/2015 08:21 PM, Mateusz Jurczyk wrote:
 Hi Balint and others,

 Sure, I am happy to share my thoughts. First of all apologies for the
 late reply, I've been quite busy during the last few days.

 Anyway, since I have already expressed my opinion regarding the subject
 several times, let me just quote some of them:

 While the former project [Libav] is doing their best to catch up
 with the latter, the figures speak for themselves again: there are
 “only” 413 commits tagged “Jurczyk” or “Coldwind” in Libav, so even
 though some of the FFmpeg bugs might not apply to Libav, there are
 still many unresolved issues there which are already fixed in
 FFmpeg. Consequently, we advise users to use the FFmpeg upstream
 code where possible, or the latest stable version (currently 2.1.1)
 otherwise.


 Source: http://j00ru.vexillium.org/?p=2211

 [...] it is not just several bugs Libav is lagging behind on - it's
 literally hundreds, or potentially thousands, many of which are
 security problems. Gynvael and I have been fuzzing FFmpeg for ~3
 years now, and Michael has been consistently fixing them in his
 project; so far, this has resulted in a total of 1318 patches in the
 library (git log | grep j00ru | wc -l).



 In the meantime, Libav is at 460 fixes, and the two codebases are
 really not that far off each other (I believe Libav has most of
 FFmpeg's code, and thus, bugs). We have fuzzed Libav independently
 and tried to get their maintainers interested in fixing all those
 issues (or picking patches from FFmpeg), and it has worked, but to
 very little extent. As a result, we now have this gigantic
 discrepancy in the security/reliability posture of the two projects,
 which goes far beyond just a few samples.



 [...]



  I'm looking forward to having Debian switched from Libav to FFmpeg
 - if there is any way I can help with that, let me know.


 Source: one of my previous e-mails sent to Moritz.

 Long story short, both FFmpeg and Libav projects contain a number of
 bugs in the processing of malformed input files, many of which are
 security vulnerabilities which can lead to arbitrary code execution and
 system compromise upon opening a specially crafted multimedia file.
 However, we have been trying to significantly decrease the number of
 such bugs in both projects via automated fuzz-testing, and specifically
 to get many of the low hanging fruits fixed so that it is no longer
 trivial for other people to discover security issues - in other words,
 to raise the bar for adversaries seeking to attack programs and systems
 which depend on multimedia handling.

 We have been quite successful working on the above effort with FFmpeg
 for the last ~3.5 years: every single issue we have found (even the
 least severe ones) has been fixed in a timely manner. As a result, after
 tens of fuzzing iterations, there are currently no bugs in FFmpeg that
 we are able to find using our current input corpus and mutation
 algorithms. The situation is entirely different with Libav, which is
 still affected by hundreds of such bugs, even though we have provided
 the developers with reproducing testcases a number of times in the past.
 Therefore, the security posture of Libav as of today is much, much worse
 than FFmpeg's, and this is the reason I support the transition to the
 latter library.

 I don't know anything about other aspects of the two projects, I can
 only give some insight into the security area. In this field, it is
 quite clear to me what the right choice is.

 Let me know if you have any questions.

 Cheers,
 Mateusz

Cheers,
Balint

___
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#779011: forked-daapd: Playing audio locally is broken

[Balint Reczey]

Package: forked-daapd
Version: 0.22.0-1
Severity: serious
Tags: upstream fixed-upstream security
Control: forwarded -1 https://github.com/ejurgensen/forked-daapd/issues/87

From upstream bug report:

...
In attempting to use local audio with ALSA, I encountered severe quality
problems I believe were being caused by underruns. Commit b7cfb65
Prevent buffer underrun (I think...) completely fixed the issue for me
on Debian with kernel 3.2.

I'd like to suggest merging at least the ALSA portion of this commit. I
do not have access to an OSS setup to test that.

I found this commit attached to pull request #41.
...

Cheers,
Balint

___
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#778995: forked-daapd: Does not work with iTunes 12.1

[Balint Reczey]

Hi Jan,

On 02/23/2015 10:26 AM, Jan Wagner wrote:
 Am 22.02.15 um 21:14 schrieb Bálint Réczey:
 Package: forked-daapd Version: 0.22.0-1 Severity: serious Tags:
 upstream fixed-upstream Control: forwarded -1
 https://github.com/ejurgensen/forked-daapd/issues/100
 
 Latest iTunes can't work with forked-daapd. Upstream has already
 released a fix.
 
 And this bug is why RC-severity?
iTunes is the most notable client of forked-daapd thus I think we should
not release a forked-daapd version which does not work with iTunes.
I plan uploading the fix today.

Cheers,
Balint



signature.asc
Description: OpenPGP digital 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

Bug#778996: forked-daapd: Multiple security issues

[Balint Reczey]

Package: forked-daapd
Version: 0.22.0-1
Severity: serious
Tags: upstream fixed-upstream security

Remotely trigger-able use-after-free and invalid reads causing DOS have
been fixed upstream:
https://github.com/ejurgensen/forked-daapd/commit/4efca3660f7c944071c76cfeca91dc836bd9c8c2
https://github.com/ejurgensen/forked-daapd/commit/cdb004808272cd331f09334fff618a8976e4fb25

Cheers,
Balint

___
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#662125: forked-daapd: scans whole DB on startup which takes ages

[Balint Reczey]

Control: tags -1 moreinfo

Hi Tino,

On Sun, 04 Mar 2012 11:21:48 +0100 Tino Keitel
tino.keitel+debb...@tikei.de wrote:
 Package: forked-daapd
 Version: 0.19gcd-2
 Severity: normal
 
 Hi,
 
 whenever I start forked-daapd it takes several minutes until it gets usable.
 
 When I start it using the command
 
   $ forked -f -d 4 -D db,scan,config
 
 I see thousands of lines like this:
 
 db: Running query 'SELECT f.id, f.db_timestamp FROM files f WHERE f.path =
 '/home/storage2/mp3/music/Tomte/Hinter all diesen Fenstern/08 -
 Insecuritate.mp3';'
 
 It looks like it scans the whole library. There is no high disk usage or CPU
 load during this, but it takes a view minutes.  Forked-daapd does not react
 to ctrl-C or SIGTERM for a while in that situation.  When I try to access
 forked-daapd using rhythmbox, it takes ~30 seconds to get the available
 music.
 
 I expect forked-daapd to be instantly ready when nothing was changed in the
 library, and only scan files that changed since the last DB update, which
 should be fast enough. I also expect forked-daapd to respond to SIGTERM
 within a few seconds.
Could you please test the latest version in testing?
It has quite some improvements and may have improved the situation.

Cheers,
Balint

___
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#767161: With XBMC from debian sid.

[Balint Reczey]

Control: forwarded -1 https://github.com/xbmc/xbmc/pull/5651
Control: tags -1 pending upstream

Hi Karl,

On Wed, 29 Oct 2014 19:21:58 +1300 Karl k...@garagedori.com wrote:
 sudo Apt-get install xbmc xbmc-bin -t sid
 
 ...
 sudo systemctl start xbmc
 less .xbmc/temp/xbmc.log..
 
 19:14:26 T:140388001949760  NOTICE: Starting XBMC from Debian (13.2 Debian
 package version:2:13.2+dfsg1-3). Platform: x86 Linux 64-bit
 19:14:26 T:140388001949760  NOTICE: Using Debug XBMC x64 build, compiled
 Oct 24 2014 by GCC 4.9.1 for x86 Linux 64-bit 3.16.5
 19:14:26 T:140388001949760  NOTICE: Running on Linux 64-bit (Debian
 GNU/Linux jessie/sid, 3.16-3-amd64 x86_64)
 19:14:26 T:140388001949760  NOTICE: Host CPU: Intel(R) Core(TM) i3-4130 CPU
 @ 3.40GHz, 4 cores available
 19:14:26 T:140388001949760  NOTICE: special://xbmc/ is mapped to:
 /usr/share/xbmc
 19:14:26 T:140388001949760  NOTICE: special://xbmcbin/ is mapped to:
 /usr/lib/xbmc
 19:14:26 T:140388001949760  NOTICE: special://masterprofile/ is mapped to:
 /home/karl/.xbmc/userdata
 19:14:26 T:140388001949760  NOTICE: special://home/ is mapped to:
 /home/karl/.xbmc
 19:14:26 T:140388001949760  NOTICE: special://temp/ is mapped to:
 /home/karl/.xbmc/temp
 19:14:26 T:140388001949760  NOTICE: The executable running is:
 /usr/lib/xbmc/xbmc.bin
 19:14:26 T:140388001949760  NOTICE: Local hostname: server
 19:14:26 T:140388001949760  NOTICE: Log File is located:
 /home/karl/.xbmc/temp/xbmc.log
 19:14:26 T:140388001949760  NOTICE:
 ---
 19:14:26 T:140388001949760INFO: Selected UPower as PowerSyscall
 19:14:26 T:140388001949760   ERROR: DBus: Error
 org.freedesktop.DBus.Error.InvalidArgs - No such property CanSuspend
 19:14:26 T:140388001949760   ERROR: DBus: Error
 org.freedesktop.DBus.Error.InvalidArgs - No such property CanHibernate
 -
 
 Suspend and Hibernate are not showing in XBMC menu.
 If remove UPower reboot/shutdown disappears.
 If remove consolekit or polkit (or the custom rules) reboot/shutdown
 disappear too.
 Process 1 is systemd.
 
 Thanks for your work on it. Great to have XBMC back in Debian.
I have proposed a fix upstream and I plan including the patch in next
upload.
It works for systemd only for now,
I would happily support other init systems as well, but I could not find
a good alternate Suspend/Hibernate API which I could rely on in Jessie.

Cheers,
Balint

___
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#762014:

[Balint Reczey]

Hi,
On 09/20/2014 08:29 AM, Dmitry Kadashev wrote:
 Hello,
 
 The same here. Can't try to downgrade to 7.37.1-1 since it's not
 available anymore.
It is a available from http://snapshot.debian.org/package/curl/7.37.1-1/ .

I will look into the problem, but I could not find time for that yet.

Cheers,
Balint

 
 -- 
 Regards,
 Dmitry Kadashev

___
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#756084: confirmed on an ARM server running Jessie

[Balint Reczey]

Hi,
On Fri, 08 Aug 2014 13:24:46 +0200 Luc Maisonobe l...@spaceroots.org wrote:
 I observe the same behavior on a small ARM server running Jessie, where
 forked-daapd version is currently 21.0-1.
 
 Netstat shows the server listening on IPV4 but not IPV6.
 The configuration file does contain a line:
 
   ipv6 = yes
 
 in the general section.
 
 The firewall (here shorewall6) is set up to accept connections on port
 3689 for IPV6 (but anyway since the server does not even listen on this
 port in IPV6, the firewall does nothing here).
Does the version in unstable work for you?

Cheers,
Balint

___
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#756084: confirmed on an ARM server running Jessie

[Balint Reczey]

Hi,
On Fri, 08 Aug 2014 13:24:46 +0200 Luc Maisonobe l...@spaceroots.org wrote:
 I observe the same behavior on a small ARM server running Jessie, where
 forked-daapd version is currently 21.0-1.
 
 Netstat shows the server listening on IPV4 but not IPV6.
 The configuration file does contain a line:
 
   ipv6 = yes
 
 in the general section.
 
 The firewall (here shorewall6) is set up to accept connections on port
 3689 for IPV6 (but anyway since the server does not even listen on this
 port in IPV6, the firewall does nothing here).
Does the version in unstable work for you?

Cheers,
Balint

___
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#672561: Re: Bug#672561: libavcodec-dev: Missing /usr/include/libavcodec/audioconvert.h

[Balint Reczey]

Hi Rogério,

On 05/12/2012 08:46 AM, Reinhard Tartler wrote:
 bug 672561 wishlist
 tags 672561 wontfix
 stop
 
 On Sat, May 12, 2012 at 7:39 AM, Rogério Brito rbr...@ime.usp.br wrote:
 Package: libavcodec-dev
 Severity: important

 Hi.

 The libavcodec-dev package is missing 
 /usr/include/libavcodec/audioconvert.h.

 This file is needed by handbrake. If I clone the libav git tree,
 checkout the v0.8.2 tag and copy that file to /usr/include/avcodec,
 then I am able to successfully compile handbrake with Debian's libav,
 without needing to download things from outside.
 
 The problem with that is that audioconvert.h is not part of the public
 API. Moreover, most of the APIs have already been removed in current
 libav/master in favor of the newly introduced libavresample library.
 Therefore, I do not think it would be a good idea to start shipping
 this header.
 
 The proper long-term solution is to port handbrake to 'libavresample'
 (not yet uploaded to experimental, the packaging needs review, and is
 not going to be included in wheezy). As short-term workaround, I'd
 suggest to copy the parts of audioconvert.h and audioconvert.c to the
 handbrake packaging.
 

 BTW, regarding handbrake, I am down to few packages now that need to
 be taken from outside debian for it to compile, namely:

 * MODULES += contrib/libdvdread
 * MODULES += contrib/libdvdnav
 * MODULES += contrib/mpeg2dec

 Everything else works with packages in Debian *or* with packages in
 the pkg-multimedia git repositories (e.g., libmkv, faac, libmp4v2).
 
 That's excellent news! Thanks for working on it and count me in as
 supporter (i.e., put me to Uploaders).
Handbrake is now in Debian and uses libavresample.
How about closing this bug? The missing header stopped being an issue, I
think.

Cheers,
Balint

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

Joining pkg-multimedia

[Balint Reczey]

Hi,

I'm Balint Reczey [1], and I would like to join the Multimedia Team.

I maintain the xbmc package which depend on many packages maintained by
the team. I also maintain other packages which are less relevant.
While I agree to review other's work I would like to focus on xbmc which
is a quite big package IMO.

I already have an alioth account (rbalint) and I have already subscribed
to pkg-multimedia-maintainers and pkg-multimedia-commits.

Cheers,
Balint

[1] http://qa.debian.org/developer.php?login=bal...@balintreczey.hu



signature.asc
Description: OpenPGP digital 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

Bug#702762: More or less dead upstream

[Balint Reczey]

Hi Reinhard,

On 03/11/2013 06:15 AM, Reinhard Tartler wrote:
 Package: libpostproc
 
 As VLC upstream points out in
 http://mailman.videolan.org/pipermail/vlc-devel/2013-March/092249.html:
 
 http://mailman.videolan.org/pipermail/vlc-devel/2013-March/092249.html
 
 The package is provided as a transitional measure until all reverse
 dependencies have been changed to no longer need it. After this has
 been implemented in all packages in the debian archive, this bug
 should be repurposed to track the phasing out of libpostproc of the
 archive.
Does that still stand? I saw several uploads to this package since
opening this bug.
If if still stands do you have some suggestions for libpostproc
replacements which other packages should transition to?

Cheers,
Balint



signature.asc
Description: OpenPGP digital 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