Re: Kodi 18 (Leia)

[Bálint Réczey]

Hi,

2018-01-15 21:10 GMT+01:00 Matteo F. Vescovi :
> Hi!
>
> On 2018-01-14 at 15:53 (+0100), Benjamin Benziger wrote:
>
> [...]
>
>> Is this your way of telling me that unstable will get Kodi 18 when
>> it's in beta phase?
>
> Well, kodi is not one of my packages.
> You'd probably ask Balint for some info on it.

In addition to Kodi many addons are also packaged in Debian. Usually I
upload betas to experimental and when the addons are updated as well I
upload the final version to unstable.
Most likely some addons will lag a bit behind, thus Kodi 18 will most
likely enter unstable shortly after the final release.

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#883851: kodi: Crash Loop when inserting Audio CD

[Bálint Réczey]

Control: tags -1 confirmed

Hi Sebastian,

2017-12-08 11:16 GMT+01:00 Sebastian Bachmann :
> Package: kodi
> Version: 2:17.3+dfsg1-5+b3
> Severity: important
>
> Dear Maintainer,
>
> I noticed today that inserting any Audio CD (I tried a few) results in a crash
> loop. Kodi will constantly crash and restart.
>
> I collected the outputs in /var/log/daemon.log and the kodi crashlog.
>
> If you need any more information, I would be glad to help!

I hoped the crash would go away with recompiling with latest libcdio,
but i can still reproduce it with kodi 17.6. :-(
This needs more investigation.

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: Bug#877799: groovy: GCJ java.lang.ArrayIndexOutOfBoundsException

[Bálint Réczey]

Hi Aaron,

2017-10-05 22:05 GMT+02:00 Aaron M. Ucko :
> Emmanuel Bourg  writes:
>
>> versioned dependency on default-jre-headless to avoid this situation,
>> I'll fix that in the next upload.
>
> Great, thanks!
>
>> Regarding Kodi I suggest compiling the Groovy files in the arch indep
>> part of the build, such that hppa doesn't have to deal with the Java
>> stuff, only the native part.
>
> Copying Kodi's maintainers per this advice.

I see that it may be possible to work around the problem of hppa not
having a working Groovy in kodi, but I'm focusing on architectures
which have kodi users. I would still accept a reasonably small patch
for kodi if someone else finds solving this issue interesting.

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#877798: kodi: FTBFS on alpha: tests don't start

[Bálint Réczey]

Control: fixed -1 2:17.3+dfsg1-5

Hi Aaron,

2017-10-05 21:11 GMT+02:00 Aaron M. Ucko :
> Source: kodi
> Version: 2:17.3+dfsg1-3
> Severity: important
> Tags: upstream
> Justification: fails to build from source (but built successfully in the past)
> User: debian-al...@lists.debian.org
>
> The latest build of kodi for alpha (admittedly not a release
> architecture) failed:
>
>   [==] Running 582 tests from 91 test cases.
>   [--] Global test environment set-up.
>   E: Build killed with signal TERM after 150 minutes of inactivity
>
> Judging from other architectures' and versions' build logs, the test
> suite normally reports detailed progress, so I gather that in this
> case, it hanged at startup for some reason.  Could you please take a
> look?

The issue seems to be gone now, most likely it was not an issue in kodi itself.

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#863925: kodi not work

[Bálint Réczey]

Control: tags -1 unreproducible moreinfo

Hi Susu,

2017-06-02 3:54 GMT+02:00 susu <0x73757...@gmail.com>:
> Package: kodi
> Version: version 2:17.1+dfsg1-3
> Severity: important
>
> Dear Maintainer,
>
> Dear Maintainer,
>
> oh ,my kodi not work.
> $kodi
> /usr/lib/x86_64-linux-gnu/kodi/kodi.bin: error while loading shared libraries:
> libmariadbclient.so.18: cannot open shared object file: No such file or
> directory
> $sudo apt install libmariadbclient18
> $ dpkg -L libmariadbclient18
> /.
> /usr
> /usr/lib
> /usr/lib/libmysqlclient.so.18.0.0
> /usr/lib/mysql
> /usr/lib/mysql/plugin
> /usr/lib/mysql/plugin/dialog.so
> /usr/lib/mysql/plugin/mysql_clear_password.so
> /usr/share
> /usr/share/doc
> /usr/share/doc/libmariadbclient18
> /usr/share/doc/libmariadbclient18/changelog.Debian.gz
> /usr/share/doc/libmariadbclient18/copyright
> /usr/lib/libmysqlclient.so.18
> /usr/lib/libmysqlclient_r.so.18
> /usr/lib/libmysqlclient_r.so.18.0.0

This looks interesing and does not match my system's files:

rbalint@sid-test:~$ dpkg -L libmariadbclient18
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libmariadbclient.so.18.0.0
/usr/lib/x86_64-linux-gnu/mariadb18
/usr/lib/x86_64-linux-gnu/mariadb18/plugin
/usr/lib/x86_64-linux-gnu/mariadb18/plugin/client_ed25519.so
/usr/lib/x86_64-linux-gnu/mariadb18/plugin/dialog.so
/usr/lib/x86_64-linux-gnu/mariadb18/plugin/mysql_clear_password.so
/usr/share
/usr/share/doc
/usr/share/doc/libmariadbclient18
/usr/share/doc/libmariadbclient18/changelog.Debian.gz
/usr/share/doc/libmariadbclient18/copyright
/usr/lib/x86_64-linux-gnu/libmariadbclient.so.18

rbalint@sid-test:~$ dpkg -l libmariadbclient18 |
catDesired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version  Architecture Description
+++----=
ii  libmariadbclient18:amd64 10.1.24-6amd64MariaDB
database client library

Could you please upgrade all your packages and if kodi still does not
work copy the output of "dpkg -l libmariadbclient18 | cat" ?

Thanks,
Balint

>
> i don't know why it is not work.
>
>
>
> -- System Information:
> Debian Release: 9.0
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
> Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
> LANGUAGE=zh_CN.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages kodi depends on:
> ii  init-system-helpers  1.48
> ii  kodi-bin 2:17.1+dfsg1-3
> ii  kodi-data2:17.1+dfsg1-3
>
> Versions of packages kodi recommends:
> ii  kodi-visualization-spectrum  1.1.1-1
>
> kodi suggests no packages.

___
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#853476: kodi: ftbfs with GCC-7

[Bálint Réczey]

Control: reassign -1 libiso9660-dev 0.83-4.3
Control: affects -1 kodi

Hi Matthias,

2017-01-31 10:32 GMT+01:00 Matthias Klose :
> Package: src:kodi
> Version: 2:17.0~rc3+dfsg1-2
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-7
>
> Please keep this issue open in the bug tracker for the package it
> was filed for.  If a fix in another package is required, please
> file a bug for the other package (or clone), and add a block in this
> package. Please keep the issue open until the package can be built in
> a follow-up test rebuild.
>
> The package fails to build in a test rebuild on at least amd64 with
> gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
> severity of this report may be raised before the buster release.
> There is no need to fix this issue in time for the stretch release.
>
> The full build log can be found at:
> http://people.debian.org/~doko/logs/gcc7-20170126/kodi_17.0~rc3+dfsg1-2_unstable_gcc7.log
> The last lines of the build log are at the end of this report.
>
> To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
> or install the gcc, g++, gfortran, ... packages from experimental.
>
>   apt-get -t=experimental install g++
>
> Common build failures are new warnings resulting in build failures with
> -Werror turned on, or new/dropped symbols in Debian symbols files.
> For other C/C++ related build failures see the porting guide at
> http://gcc.gnu.org/gcc-7/porting_to.html
>
> [...]


The build failed a bit earlier, with:

CPP xbmc/dbwrappers/mysqldataset.o
In file included from
/<>/kodi-17.0~rc3+dfsg1/xbmc/filesystem/iso9660.h:35:0,
 from DetectDVDType.cpp:30:
/usr/include/cdio/iso9660.h:277:45: error: flexible array member
'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
   char filename[EMPTY_ARRAY_SIZE];
 ^
/usr/include/cdio/iso9660.h:310:20: note: next member 'char
iso9660_pvd_s::root_directory_filename' declared here
   char root_directory_filename;  /**< Is '\\0' or root
^~~
/usr/include/cdio/iso9660.h:283:8: note: in the definition of 'struct
iso9660_pvd_s'
 struct iso9660_pvd_s {
^
/usr/include/cdio/iso9660.h:277:45: error: flexible array member
'iso9660_dir_s::filename' not at end of 'struct iso9660_svd_s'
   char filename[EMPTY_ARRAY_SIZE];
 ^
/usr/include/cdio/iso9660.h:424:20: note: next member 'char
iso9660_svd_s::root_directory_filename' declared here
   char root_directory_filename;  /**< Is '\\0' or root
^~~
/usr/include/cdio/iso9660.h:392:8: note: in the definition of 'struct
iso9660_svd_s'
 struct iso9660_svd_s {
^
...

The problem is in the structure definitions of iso9660.h

The easies way of reproducing the issue is running:
$ sudo apt-get install libiso9660-dev g++-7
$ echo '#include ' | g++-7 -x c++ -
In file included from :1:0:
...

...
> debian/rules:131: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 2
> make[1]: Leaving directory '/<>/kodi-17.0~rc3+dfsg1'
> debian/rules:79: recipe for target 'build' failed
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2

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#855225: kodi: CVE-2017-5982: Unrestricted file download

[Bálint Réczey]

Hi Antoine,


Thanks for the detailed analysis!

2017-04-26 19:05 GMT+02:00 Antoine Beaupre :
> affects 85225 xbmc
> package xbmc
> found 85225 2:11.0~git20120510.82388d5-1
> thanks
>
> I can confirm this affects both jessie-backports and wheezy. I've been
> able to access random files on my Kodi install using:
>
> http://localhost:8080/image/image%3A%2F%2F%2e%2e%252f%2e%2e%252f%2e%2e%252f%2e%2e%252fetc%252fpasswd
>
> Just add more %2e%2e%252f in there if that's not deep enough for you. :)
>
> In wheezy, it's even worse - there's a /vfs/ layer that gives you plain
> access to any given path, as bam discovered. But you don't even need any
> "special://" protocol, this just works:
>
> http://localhost:8080/vfs/etc/passwd
>
> Given that XBMC 11 (wheezy) and 16 (jessie-backports) are vulnerable, I
> would be very surprised if XBMC 13 had any reasonable protections in
> place.
>
> As I explained in this post on debian-lts, I'm really unsure how to fix
> this issue:
>
> https://lists.debian.org/87zif33oxf@curie.anarc.at
>
> Should we consider this part of the design that there's basically an
> open file manager in the Kodi web browser? That may sound ludicrous, but
> that's the way this thing is built right now. There's *some* password
> protection as well, although the password is empty by default and is
> therefore disabled. A possible workaround would be to force
> authentication, even if there are no passwords set. This would require
> commenting out this line:
>
>   m_needcredentials = !password.IsEmpty();
>
> in CWebServer::SetCredentials (WebServer.cpp). That way attackers would
> be presented with an authentication dialog at least. There's a default
> username and password, but at this point we may somehow shift the blame
> to the user...
>
> The alternative here is to start enforcing path restrictions on the
> requested files in the webserver. This is a difficult operation because,
> right now, files can be specified with arbitrary paths, including
> relative paths with `../` or absolute paths, and there aren't clear
> boundaries to where Kodi "can look": Kodi is designed to take over a
> media station and serve contents from all sorts of sources...
>
> So if we change the webserver, we also need to change the callers, and
> that could prove more difficult...

I have forwarded this info to upstream bug tracker but I have no high hopes in
getting the issue solved.

I plan blogging about Kodi 17.1 being in both Stretch and Zesty and mention
this issue as a reason for people to not trust any installation too much.

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#857784: Missing build dependency on asciidoc

[Bálint Réczey]

Hi Ola,

2017-03-15 12:13 GMT+01:00 Ola Lundqvist :
> Hi
>
> Thank you.
>
> Odd that I stumbled on that then. For some reason I could not get the build
> through without that.

Do you have some logs?
I tried triggering timestamp related issues with the following command:
sbuild -As -j6 --add-depends=ccache --arch=amd64 -d wheezy
--starting-build-commands='find %SBUILD_BUILD_DIR -type f -exec bash
-c "touch --date \"- \$RANDOM seconds\" {}" ";" ; ls --full-time
%SBUILD_BUILD_DIR' audiofile

, but found no build problem.

Cheers,
Balint

>
> / Ola
>
> Sent from a phone
>
> Den 15 mar 2017 11:43 skrev "James Cowgill" :
>>
>> Control: retitle -1 audiofile: rebuild documentation at build time
>> Control: severity -1 wishlist
>>
>> Hi,
>>
>> On 14/03/17 21:39, Ola Lundqvist wrote:
>> > Package: audiofile
>> > Severity: important
>> > Version: 0.3.4-2
>> >
>> > Hi
>> >
>> > While working on the oldstable security update for a number of CVEs I
>> > noticed that the package was not possible to build in a (relatively)
>> > clean wheezy chroot. The reason was that I had not installed asciidoc.
>> > It looks like this dependency is missing also in latest revision even
>> > though I have not explicitly tried to build it in a sid chroot.
>> >
>> > Please add this build dependency.
>>
>> I tried to reproduce this in a wheezy and sid chroot and audiofile
>> builds fine in both cases.
>>
>> I don't think asciidoc is required if you don't modify things in docs/.
>> It's probably a good idea to rebuild the documentation at build time,
>> but audiofile doesn't require this dependency at the moment.
>>
>> James

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

Bug#856815: kodi FTBFS on Alpha due to Intel assembler that is easily worked around

[Bálint Réczey]

Control: tags -1 confirmed moreinfo

Hi Michael,

2017-03-05 2:29 GMT+01:00 Michael Cree :
> Source: kodi
> Version: 2:17.0+dfsg1-3
> Severity: wishlist
> Tags: patch
> User: debian-al...@lists.debian.org
> Usertags: alpha
>
> kodi FTBFS on alpha due to Intel specific code [1].
>
> I attach a patch that enables generic code to be built rather
> than Intel specific code and with that kodi builds to completion
> on Alpha.

Thanks!

I am generally happy to receive patches from porters and would be open
to accepting it, but before I do so I have two questions:

Can kodi run on any alpha machine?

The kodi package is quite big. Would building the package worth it
considering the space needed on snapshot.d.o, on mirrors, etc?

Cheers,
Balint

>
> Cheers
> Michael.
>
> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=kodi=alpha=2%3A17.0%2Bdfsg1-3=1487892844=0

___
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#857309: kodi: 'kodi' user does not exist

[Bálint Réczey]

Control: severity -1 wishlist
Control: tags -1 confirmed

Hi Moritz,

2017-03-09 21:55 GMT+01:00 Moritz Schmidt :
> Package: kodi
> Version: 2:17.0+dfsg1-3
> Severity: important
>
> Dear maintainer,
>
> I installed the kodi package on a fresh installed debian testing and enabled 
> the kodi systemd-service which should start kodi in standalone mode.
> The service file (/lib/systemd/system/kodi.service) is configured to run as 
> 'kodi' user, but this user doesn't exist after installation.
> I think automatically adding the user when using him would make sense.

It would make sense if every installation used the kodi user, but
there are many people who start kodi from their normal session or set
up automatic logging in in the display manager to start kodi [1].

I was thinking about adding a debconf question about adding the kodi
user and enabling  the standalone mode during package configuration
but this is about the same amount of added complexity as the current
manual addition of the kodi user.

I think if someone sets up a system for kodi only the first added user
is usually the user which runs kodi anyway.

AFAIK the kodi-systemd-service way is preferred on constrained systems
where running even lightdm would waste too much memory,
but I have just found nodm [2] which could also help here.

> After adding the user everything works as expected.

Great!

I will consider adding the debconf question and creating the kodi
user, but not by default.

>
> Thanks for your work and have a nice day,
> Moritz Schmidt

Thanks!

Cheers,
Balint

[1] http://kodi.wiki/view/HOW-TO:Autostart_Kodi_for_Linux
[2] https://packages.qa.debian.org/n/nodm.html

___
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#856100: libav-tools : concat Protocol not found

[Bálint Réczey]

Control: fixed -1 ffmpeg/7:3.2-2
Control: tags -1 - wontfix


2017-03-07 12:13 GMT+01:00 Carl Eugen Hoyos :
> Hi!
>
> Several similar bugs (features missing from avconv in Debian) were closed
> as "fixed" when Debian switched to FFmpeg: How is this report different?

OK, closing it marking it fixed in ffmpeg. My idea was keeping it open
for libav to
let users find it but it won't be archived for some time and what you recommend
is the right thing to do.

Cheers,
Balint

>
> As an alternative, this could be reassigned to "libav-doc".
>
> Thank you, Carl Eugen

___
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#839941: whishlist ffmpeg

[Bálint Réczey]

Control: tags -1 wontfix

Hi Carl,

2017-03-07 12:07 GMT+01:00 Carl Eugen Hoyos :
> Hi!
>
> I wonder if "confirmed" is really the right status:
> There is absolutely no way that this can be fixed within
> Debian, the license of the necessary header files is
> certainly not compatible with any open-source license.
>
> I suggest to close as wont-fix or invalid.

I added the 'confirmed' tags since decklink support is missing indeed.
The 'wontfix' tag also makes sense since we can't fix the issue due
the the license.
I usually don't like closing bugs which still exist, because people would
report them again and again because the archived bugs are not shown by default
on BTS. I consider those bugs to be part of the documentation.

However if you strongly dislike this bug kept open feel free to close it. :-)

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#691763: Wish: Please support some low res (SDTV) skin

[Bálint Réczey]

Control: tags -1 moreinfo

Hi Philippe,

2014-01-06 17:49 GMT+01:00 Balint Reczey :
> tags 691763 wontfix
> thanks
>
> Dear Philippe,
>
> On 10/29/2012 02:22 PM, Philippe Coval wrote:
>> Package: xbmc
>> Version: 2:11.0~git20120510.82388d5-1
>> Severity: wishlist
>>
>> Dear Maintainer,
>>
>> I suppose that one can be forwarded upstream, I will do if needed
>>
>> Please support by default a SDTV (PAL/NTSC) skin if display is not large 
>> enough...
>>
>> There is a Project Mayem skin
>> but I am unsure it is supported or can be packaged separately ?
> XBMC from Debian supports all the skins which can be downloaded from
> XBMC's skin repository. You can download them at
> System->Settings->Appearance->Skin->Skin->Get More... .
>
> The Project Mayhem skin has been replaced by PM3.HD from the same team
> but it is optimized for high resolutions.
>
> If you find a suitable skin and you think that is should be packaged in
> Debian then please file and RFP bug for it. IMHO there would be little
> value in packaging additional skins since they are just XML files with
> images.
>
> If you don't find any suitable skin please ask upstream/skin developers
> to provide one, I can't help too much in this case.

The new default skin in Kodi 17 seems to work better on low-res devices.
What do you think? Is the new skin good enough to consider this problem solved?

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: [SCM] libquicktime/master: Fix integer overflow in the quicktime_read_pascal function (CVE-2016-2399)

[Bálint Réczey]

Hi Alexander,

2017-03-01 0:54 GMT+01:00 Alexander Strasser :
> Hi!
>
> On 2017-02-27 22:54 +, rbal...@users.alioth.debian.org wrote:
>> The following commit has been merged in the master branch:
>> commit f6bb364af6a2bc65eab832614afb578c5740a0cc
>> Author: Balint Reczey 
>> Date:   Mon Feb 27 23:13:47 2017 +0100
>>
>> Fix integer overflow in the quicktime_read_pascal function 
>> (CVE-2016-2399)
>>
>> Closes: #855099
>>
>> diff --git a/debian/patches/CVE-2016-2399.patch 
>> b/debian/patches/CVE-2016-2399.patch
>> new file mode 100644
>> index 000..dfa8180
>> --- /dev/null
>> +++ b/debian/patches/CVE-2016-2399.patch
>> @@ -0,0 +1,22 @@
>> +diff --git a/src/util.c b/src/util.c
>> +index d8dc3c3..9422fc5 100644
>> +--- a/src/util.c
>>  b/src/util.c
>> +@@ -340,9 +340,14 @@ int64_t quicktime_byte_position(quicktime_t *file)
>> +
>> + void quicktime_read_pascal(quicktime_t *file, char *data)
>> + {
>> +-char len = quicktime_read_char(file);
>> +-quicktime_read_data(file, (uint8_t*)data, len);
>> +-data[(int)len] = 0;
>> ++int len = quicktime_read_char(file);
>> ++if ((len > 0) && (len < 256)) {
>> ++  /* data[] is expected to be 256 bytes long */
>> ++  quicktime_read_data(file, (uint8_t*)data, len);
>> ++  data[len] = 0;
>> ++} else {
>> ++  data[0] = 0;
>> ++}
>> + }
>
>
> I might be missing something, so please check my words and the code carefully.
>
> Could the len ever get bigger than 255 ?

First, thank you for checking the patch.

You are right, at the moment quicktime_read_char() does return values 0..255,
in int which type can hold values from a much bigger range including
negative values.
To clearly check for those I have added the range check which makes sure that
the code indexes the valid indices of data[].

>
> If my assumption is true and that security issue only happens with signed char
> and the problem is therefore writing in front of the array, I would think that
> there is a simpler fix while still supporting strings larger than 127 bytes.
>
> E.g. by changing the type of the variable at src/util.c : 820 to uint8_t
> and the type of len at src/util.c : 343 to int or uint8_t .

This would be a possible solution, but I don't like narrowing conversions
without clear markers and I like storing return values to the same type
because it leaves less opportunities for hidden problems.
Sometimes the return type's range is wider than the valid values in order
to signal error using a value which is not 'valid'.

See fgetc() for example which returns 0..255, or EOF (-1) in case of an error.

If quicktime_read_char() ever starts returning -1 on error this part
of code stays
correct in a sense that 0..255 values will be handled correctly, but simply
using uint8_t would then convert -1 to 255 which may mess up other things.

>
> I am sorry if I am misunderstanding the issue, the fix just made me curious to
> dig a little deeper. However I can't see how your commit would not fix the
> security issue or introduce new issues.
>
>
>
> Apart from this issue in particular I think there can be more trouble with
> quicktime_read_char and for example quicktime_read_pascal :
>
> In quicktime_read_pascal (src/util.c : 820) the variable output is not

This would be quicktime_read_char(), I guess.

> initialized and following call to quicktime_read_data could return without
> writing into output and thus another line below we would return an
> uninitialized value.
>
> For example in quicktime_read_pascal this could lead to making up strings
> full strings (max size 256 bytes) of uninitialized data.
>
> If and how this can become a security problem is a different story and
> I did not investigate the code any further.

This could cause an information leak, but this is much less severe than
CVE-2016-2399 IMO. You are right, there are other issues in the code
and I actually spotted this one and started fixing it, but I found new
problems everywhere I looked and had to focus on this CVE.

The article about the original issue contains this part:
http://www.nemux.org/2016/02/23/libquicktime-1-2-4/
...
 Disclosure part

 Let me make a little introduction... i'm sure this is not the only
issue of this library. I suppose libquicktime needs refactoring
process (IMHO)
...

I would say libquicktime could use an audit and it would benefit from
more extensive error checking at several places.

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: Wheezy update of libquicktime?

[Bálint Réczey]

Hi,

I'll take care of that wearing both my Multimedia Team and LTS hats.

Cheers,
Balint

2017-02-25 16:29 GMT+01:00 Thorsten Alteholz :
> Hello dear maintainer(s),
>
> the Debian LTS team would like to fix the security issues which are
> currently open in the Wheezy version of libquicktime:
> https://security-tracker.debian.org/tracker/CVE-2016-2399
>
> 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 libquicktime updates
> for the LTS releases.
>
> Thank you very much.
>
> Thorsten Alteholz,
>   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#856100: libav-tools : concat Protocol not found

[Bálint Réczey]

Control: tags -1 wontfix confirmed
Control: reopen -1
Control: found -1 6:11.8-1~deb8u1

Hi,

2017-02-25 2:09 GMT+01:00 Bálint Réczey <bal...@balintreczey.hu>:
> Control: notfound -1 6:11.8-1~deb8u1
>
> Hi,
>
> 2017-02-25 1:58 GMT+01:00 ça vaaa <n...@sfr.fr>:
>> Package: libav-tools
>> Version: 6:11.8-1~deb8u1
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> I'm trying to concatenate mp3 files using avconv (from libav-tools) with
>> this line :
>>
>> $ avconv -i
>> concat:./The_Beach_Boys_-_God_Only_Knows.mp3\|./Order_Of_Era_-_one_is_the_loneliest_number.mp3
>> -c copy /tmp/mix.mp3
> You need to put the '|' (pipe) between apostrophes because it has
> special meaning in shell:
> avconv -i 
> 'concat:./The_Beach_Boys_-_God_Only_Knows.mp3\|./Order_Of_Era_-_one_is_the_loneliest_number.mp3'
> -c copy /tmp/mix.mp3

Sorry, I missed the backslash protecting the pipe already.

I have reproduced the problem with the exact same version.

FFmpeg has replaced Libav in Debian and this command works with avconv
provided by ffmpeg 7:3.2.2-1~bpo8.

I suggest switching to libav-tools provided in jessie-backports if you
would like
to concat files.

Sorry for closing the bug so quickly.

Cheers,
Balint

>
> Cheers,
> Balint
>
>
>> avconv version 11.8-6:11.8-1~deb8u1, Copyright (c) 2000-2016 the Libav
>> developers
>>   built on Oct  1 2016 07:16:29 with gcc 4.9.2 (Debian 4.9.2-10)
>>
>> and I get :
>>
>> concat:./The_Beach_Boys_-_God_Only_Knows.mp3|./Order_Of_Era_-_one_is_the_loneliest_number.mp3:
>> Protocol not found
>>
>> this protocol is listed in the manpage, but not showed by
>>
>> $ avconv -protocols
>>
>> thank you.
>>
>> --
>>
>> -- System Information:
>> Debian Release: 8.7
>>   APT prefers stable-updates
>>   APT policy: (500, 'stable-updates'), (500, 'stable')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
>> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages libav-tools depends on:
>> ii  dpkg 1.17.27
>> ii  libavcodec56 6:11.8-1~deb8u1
>> ii  libavdevice556:11.8-1~deb8u1
>> ii  libavfilter5 6:11.8-1~deb8u1
>> ii  libavformat566:11.8-1~deb8u1
>> ii  libavresample2   6:11.8-1~deb8u1
>> ii  libavutil54  6:11.8-1~deb8u1
>> ii  libc62.19-18+deb8u7
>> ii  libsdl1.2debian  1.2.15-10+b1
>> ii  libswscale3  6:11.8-1~deb8u1
>> ii  libvdpau10.8-3+deb8u2
>> ii  libx11-6 2:1.6.2-3
>>
>> libav-tools recommends no packages.
>>
>> Versions of packages libav-tools suggests:
>> pn  frei0r-plugins  
>>
>> -- no debconf 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#854985: kodi.service spamming the logs due to xinit being missing

[Bálint Réczey]

Control: severity -1 serious
Control: tags -1 confirmed

Hi Gabor,

2017-02-12 22:24 GMT+01:00 Gábor :
> Package: kodi
> Version: 2:17.0+dfsg1-2
> Severity: normal
>
> Dear Maintainer,
>
> Since the latest round of updates, kodi.service spams syslog with:
>
> Feb 12 22:14:35 zephyr systemd[1]: kodi.service: Service hold-off time over, 
> scheduling restart.
> Feb 12 22:14:35 zephyr systemd[1]: Stopped Kodi Open Source Home Theatre.
> Feb 12 22:14:35 zephyr systemd[1]: Started Kodi Open Source Home Theatre.
> Feb 12 22:14:35 zephyr systemd[17588]: kodi.service: Failed at step USER 
> spawning /usr/bin/xinit: No such process
> Feb 12 22:14:35 zephyr systemd[1]: kodi.service: Main process exited, 
> code=exited, status=217/USER
> Feb 12 22:14:35 zephyr systemd[1]: kodi.service: Unit entered failed state.
> Feb 12 22:14:35 zephyr systemd[1]: kodi.service: Failed with result 
> 'exit-code'.
>
> If Kodi really needs xinit, then the package should depend on it. xinit
> is rather old-fashioned, and is no longer generally useful if one runs
> one of the "big" desktop environments, so nothing should assume it just
> exists.
>
> Actually, I don't think this service should be automatically enabled at
> all. I do not want to run kodi in stand-alone mode.

Yes, this is indeed the problem.
I'll disable it by default in the next upload.

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#855225: kodi: CVE-2017-5982: Unrestricted file download

[Bálint Réczey]

Control: tags -1 confirmed
Control: found -1 15.1+dfsg1-1


2017-02-15 19:03 GMT+01:00 Salvatore Bonaccorso :
> Source: kodi
> Severity: important
> Tags: upstream security
> Forwarded: http://trac.kodi.tv/ticket/17314
>
> Hi,
>
> the following vulnerability was published for kodi. I did not had the
> time to verify if 17.0 is affected. Could you please check and add
> according found versions to this bug please or otherwise close after
> checking?

Done.

Cheers,
Balint

>
> CVE-2017-5982[0]:
> local file inclusion
>
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
>
> For further information see:
>
> [0] https://security-tracker.debian.org/tracker/CVE-2017-5982
>
> Please adjust the affected versions in the BTS as needed.
>
> Regards,
> Salvatore

___
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: libva-dmo_1.7.3-2~bpo8+1.0_i386.changes ACCEPTED into stable-backports, stable-backports

[Bálint Réczey]

Hi Christian,

You would be welcome to work in jessie-backports on adding kodi 17's
dependencies.
I plan backporting kodi 17 as well and I think there is very little
difference between
kodi 17 provided by dmo servers and kodi 17 to be provided by jessie-backports.

Cheers,
Balint

2017-02-12 17:52 GMT+01:00 Christian Marillat :
> On 12 févr. 2017 17:43, James Cowgill  wrote:
>
>> Hi,
>>
>> On 12/02/17 16:00, DMO Archive Installer wrote:
>>> Accepted:
>>>
>>> Format: 1.8
>>> Date: Sun, 12 Feb 2017 16:26:21 +0100
>>> Source: libva-dmo
>>> Binary: libva-dev libva1 libva-x11-1 libva-glx1 libva-tpi1
>>> libva-egl1 libva-drm1 libva-wayland1 vainfo va-driver-all
>>> Architecture: source i386
>>> Version: 1.7.3-2~bpo8+1.0
>>> Distribution: stable-backports
>>> Urgency: medium
>>> Maintainer: Debian Multimedia Maintainers
>>> 
>>> Changed-By: Christian Marillat 
>>
>> Wrong maintainer address?
>
> Yes. Fixed.
>
> Christian
>
> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

___
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#853103: a52dec: FTBFS [i386]: Test failure in "globals"

[Bálint Réczey]

2017-01-29 23:52 GMT+01:00 James Cowgill <jcowg...@debian.org>:
> Control: severity -1 serious
> Control: tags -1 - moreinfo
>
> Hi,
>
> On 29/01/17 22:33, Bálint Réczey wrote:
>> Control: severity -1 normal
>> Control: tags -1 moreinfo
>>
>> Hi Daniel,
>>
>> It does build fine with sbuild:
>>
>> $ sbuild --arch-all --dist=unstable a52dec_0.7.4-18
>> ...
>> Status: successful
>> ...
>>
>> This seems to be a local/pbuilder issue.
>
> I can reproduce this issue using sbuild.
>
> $ sbuild --arch=i386 -A a52dec_0.7.4-18
> [...]
> FAIL: globals
> =
>
> BAD GLOBAL SYMBOLS:
> __x86.get_pc_thunk.di
> __x86.get_pc_thunk.cx
> __x86.get_pc_thunk.dx
> __x86.get_pc_thunk.ax
> __x86.get_pc_thunk.bx
> __x86.get_pc_thunk.ax
> __x86.get_pc_thunk.bx
> __x86.get_pc_thunk.di
> __x86.get_pc_thunk.si
> FAIL globals (exit status: 1)
>
> Are you sure you're building with i386 (the issue does not occur on amd64).

No, sorry, it was my mistake. I built with amd64.

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#853103: a52dec: FTBFS [i386]: Test failure in "globals"

[Bálint Réczey]

Control: severity -1 normal
Control: tags -1 moreinfo

Hi Daniel,

It does build fine with sbuild:

$ sbuild --arch-all --dist=unstable a52dec_0.7.4-18
...
Status: successful
...

This seems to be a local/pbuilder issue.

Cheers,
Balint


2017-01-29 20:00 GMT+01:00 Daniel Schepler :
> Source: a52dec
> Version: 0.7.4-18
> Severity: serious
>
> From my pbuilder build log:
>
> ...
> Making check in test
> make[2]: Entering directory '/build/a52dec-0.7.4/test'
> make  check-TESTS
> make[3]: Entering directory '/build/a52dec-0.7.4/test'
> make[4]: Entering directory '/build/a52dec-0.7.4/test'
> SKIP: regression
> SKIP: compile
> FAIL: globals
> ===
>   : test/test-suite.log
> ===
>
> # TOTAL: 3
> # PASS:  0
> # SKIP:  2
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> SKIP: regression
> 
>
> SKIP regression (exit status: 77)
>
> SKIP: compile
> =
>
> SKIP compile (exit status: 77)
>
> FAIL: globals
> =
>
> BAD GLOBAL SYMBOLS:
> __x86.get_pc_thunk.di
> __x86.get_pc_thunk.cx
> __x86.get_pc_thunk.dx
> __x86.get_pc_thunk.ax
> __x86.get_pc_thunk.bx
> __x86.get_pc_thunk.ax
> __x86.get_pc_thunk.bx
> __x86.get_pc_thunk.di
> __x86.get_pc_thunk.si
> FAIL globals (exit status: 1)
>
> 
> Testsuite summary for
> 
> # TOTAL: 3
> # PASS:  0
> # SKIP:  2
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See test/test-suite.log
> 
> Makefile:656: recipe for target 'test-suite.log' failed
> make[4]: *** [test-suite.log] Error 1
> make[4]: Leaving directory '/build/a52dec-0.7.4/test'
> Makefile:762: recipe for target 'check-TESTS' failed
> make[3]: *** [check-TESTS] Error 2
> make[3]: Leaving directory '/build/a52dec-0.7.4/test'
> Makefile:849: recipe for target 'check-am' failed
> make[2]: *** [check-am] Error 2
> make[2]: Leaving directory '/build/a52dec-0.7.4/test'
> Makefile:389: recipe for target 'check-recursive' failed
> make[1]: *** [check-recursive] Error 1
> make[1]: Leaving directory '/build/a52dec-0.7.4'
> dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
> debian/rules:4: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 2
> dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
> --
> Daniel Schepler
>
> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

___
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#852635: kodi: Does not play DVD iso from remote location when libdvdcss is installed

[Bálint Réczey]

Package: kodi
Version: 2:17.0~rc3+dfsg1-2
Severity: minor
Tags: confirmed

When libdvdcss is installed opening DVDs from remote locations fails,
but playing DVDs from local filesystem still works.

Without libdvdcss now Kodi plays DVDs from remote and local locations.

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#851026: ffmpeg: FTBFS: ffconf.bVIjAhhQ.c:2: undefined reference to `dlopen'

[Bálint Réczey]

Hi Andreas,

2017-01-22 13:05 GMT+01:00 Andreas Cadhalpun <andreas.cadhal...@googlemail.com>:
> Hi Bálint.
>
> On 22.01.2017 10:48, Bálint Réczey wrote:
>> 2017-01-22 0:05 GMT+01:00 Andreas Cadhalpun 
>> <andreas.cadhal...@googlemail.com>:
>>> The next FFmpeg upstream release will probably not be in time for the 
>>> freeze,
>>> so I've just cherry-picked this patch.
>>
>> Thanks!
>>
>> I see you have finalized the changelog. Is it ready for upload?
>
> Yes. Sorry for not being clear about that.

No problem, I just want to be sure that the package is 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

Re: Bug#851026: ffmpeg: FTBFS: ffconf.bVIjAhhQ.c:2: undefined reference to `dlopen'

[Bálint Réczey]

Hi Andreas,

2017-01-22 0:05 GMT+01:00 Andreas Cadhalpun <andreas.cadhal...@googlemail.com>:
> Hi,
>
> On 19.01.2017 00:05, Bálint Réczey wrote:
>> 2017-01-14 23:54 GMT+01:00 Adrian Bunk <b...@debian.org>:
>>> No, you should only look at the first compile error in that file:
>>>
>>> src/libavformat/chromaprint.c:42:24: error: field 'ctx' has incomplete type
>>>  ChromaprintContext ctx;
>>> ^~~
>>> This is the actual error.
>>>
>>> Whatever the compiler comes up with for cpr->ctx in the place you quoted
>>> might be garbage, but at that point it is already game over.
>>>
>>> Upstream fix:
>>>   
>>> http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=581f93f37ef2e7a00662828ed0348d1edb9041fe
>>>
>>
>> Is there a new FFmpeg upstream release on the horizon or I should just
>> update the package with a cherry-picked patch?
>
> The next FFmpeg upstream release will probably not be in time for the freeze,
> so I've just cherry-picked this patch.

Thanks!

I see you have finalized the changelog. Is it ready for 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

Re: ffmpeg & fdk aac

[Bálint Réczey]

Hi Rob,

2017-01-19 15:04 GMT+01:00 Rob Ekl :
> Hi. I just upgraded to ffmpeg-7:3.2.2-1~bpo8+1 on jessie, and the FDK AAC
> encoder seems to be missing. Do I need to do something to see it? Can it be
> added?
>
> $ ffmpeg -encoders | grep -i aac
> ffmpeg version 3.2.2-1~bpo8+1 Copyright (c) 2000-2016 the FFmpeg developers
>   built with gcc 4.9.2 (Debian 4.9.2-10)

Please use the embedded encoder.

https://trac.ffmpeg.org/wiki/Encode/AAC :
...
libvo_aacenc

VisualOn AAC encoding library. Support for this library has been
removed. Use the native FFmpeg encoder instead: it provides better
quality and supports more than 2 channels.
...

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: Bug#851026: ffmpeg: FTBFS: ffconf.bVIjAhhQ.c:2: undefined reference to `dlopen'

[Bálint Réczey]

Hi,

2017-01-14 23:54 GMT+01:00 Adrian Bunk :
> Control: retitle -1 ffmpeg: ChromaprintContext FTBFS
> Control: forwarded -1 https://trac.ffmpeg.org/ticket/5997
> Control: tags -1 fixed-upstream
>
> On Sat, Jan 14, 2017 at 06:47:02AM +0100, Carl Eugen Hoyos wrote:
>> The relevant lines in the build log are afaict:
>>
>> src/libavformat/chromaprint.c: In function 'write_packet':
>> src/libavformat/chromaprint.c:113:1: error: control reaches end of non-void
>> function [-Werror=return-type]
>>  }
>>  ^
>>
>> The function looks like this:
>>
>> static int write_packet(AVFormatContext *s, AVPacket *pkt)
>> {
>> ChromaprintMuxContext *cpr = s->priv_data;
>> return chromaprint_feed(cpr->ctx, pkt->data, pkt->size / 2) ? 0 :
>> AVERROR(EINVAL);
>> }
>>
>> I guess this is a compiler bug.
>
> No, you should only look at the first compile error in that file:
>
> src/libavformat/chromaprint.c:42:24: error: field 'ctx' has incomplete type
>  ChromaprintContext ctx;
> ^~~
> This is the actual error.
>
> Whatever the compiler comes up with for cpr->ctx in the place you quoted
> might be garbage, but at that point it is already game over.
>
> Upstream fix:
>   
> http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=581f93f37ef2e7a00662828ed0348d1edb9041fe
>
>> Carl Eugen

Is there a new FFmpeg upstream release on the horizon or I should just
update the package with a cherry-picked patch?

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#842651: skip empty files

[Bálint Réczey]

Control: tags -1 upstream

Hi Antoine,

2016-10-31 4:00 GMT+01:00 Antoine Beaupré :
> Source: kodi
> Severity: wishlist
> Tags: patch
>
> Hi,
>
> I am a heavy user of git-annex. In case you are unfamiliar with the
> software, it's a tool to allow easier archiving of large files, using
> git as a backend. Files are not stored directly in git, but rather, as
> symlinks to real object files.
>
> https://git-annex.branchable.com/
>
> On my laptop, i have a part of my main video library that resides on
> another machine. This means that some of those symlinks (the majority
> of them, in fact) are broken symlinks.
>
> Yet Kodi happily parses those files as if they were present, and shows
> them as real movies when I try to select them. When I do, Kodi says
> that the file is missing from the library and oh, do I want to remove
> it?
>
> This is a bit annoying. It seems to me empty files are obviously
> invalid and should just not show up in the interface.
>
> I looked at implementing a workaround for this by patching Kodi to
> ignore empty file sets. I am not very familiar with the internals of
> Kodi, but I hope I have found the right place to make such a change. I
> am in the process of rebuilding a backport with the patch to test this
> (which takes a long time!) but I thought I would share the patch here
> to get more feedback.
>
> I am hesitant in sharing directly with upstream because I am afraid
> they will refuse supporting my exotic (git-annex) configuration: I
> have in the past been told that my video library wasn't curated the
> right way and their parser was expecting certain things to be stored
> in a certain way (e.g. movie file titles in a certain ways, and so
> on). The problem is changing the way git-annex works is even harder:
> there is an issue opened on that side as well, but it's unfortunately
> not seeing a lot of movement either, being a major architectural
> change:

I think the approach of skipping empty files is reasonable and I
suggest sharing the patch with upstream. They seem to be open
to patches improving the user experience.

Regarding the Debian package I would like to keep the code as
close to upstream's state as possible and while I would like to
please users, too, I'm hesitant to applying the patch only in
Debian.

>
> https://git-annex.branchable.com/todo/hide_missing_files/
>
> So I figured a 2-line patch in Kodi would fix my immediate problem
> provided that, of course, it works at all. :)
>
> I'll give more information when my tests are complete.

I hope the tests went well. :-)

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#849272: kodi: Don't restore geometry

[Bálint Réczey]

Control: forwarded -1 http://forum.kodi.tv/showthread.php?tid=304356

2017-01-14 12:16 GMT+01:00 Vladimir Stavrinov <vstavri...@gmail.com>:
> On Sat, Jan 14, 2017 at 10:29:02AM +0100, Bálint Réczey wrote:
>
>> I'm not sure if it is a bug or a design decision since switching to
>> native resolution also makes sense.
>
> What that sense is? I never see similar behavior of other
> applications. But with this I can't switch to size what I need. This
> is something ridiculous.

Maybe if the user set the resolution to one that does not work
with her/his screen this reset can be helpful.

>
>> I'm marking the bug as wontfix since I don't want to diverge from
>> upstream in this behavior and the current one makes sense.
>> Feel free to discuss that question with upstream and if they change
>> how switching to fullscreen works it will be available in the package,
>> too.
>
> I think You should forward this bug report to upstream.

Done, let's see how it goes.

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#798054: kodi: http header "Location:" is wrong handled

[Bálint Réczey]

Control: fixed -1 2:17.0~rc2+dfsg1-1

2017-01-14 12:03 GMT+01:00 Vladimir Stavrinov <vstavri...@gmail.com>:
> On Sat, Jan 14, 2017 at 10:15:43AM +0100, Bálint Réczey wrote:
>
>
>> There were many changes in this area in Kodi. Could you please check
>> if the issue is still present in 17.x?
>
> I couldn't find URL I have used for testing before do this bug
> report. But some others ones, that returns different hostname than
> what in request  are working. So, I think , You can close this
> issue.

Thanks for testing!

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#849272: kodi: Don't restore geometry

[Bálint Réczey]

Control: severity -1 minor
Control: tags -1 confirmed upstream wontfix

Hi Vladmimir,

2016-12-24 15:33 GMT+01:00 Vladmimir Stavrinov :
> Package: kodi
> Version: 2:17.0~beta6+dfsg1-1
> Severity: normal
>
> When toggle full screen it doesn't restore previous geometry, but creates 
> window in size of the full screen instead.

I have successfully reproduced the issue:
1. Start Kodi with default configuration
2. Change resolution in settings to lower resolution than the screen
(successful)
3. Exit kodi
4. Start Kodi again (lower resolution restored)
5. Switch to windowed mode in settings
6. Switch back to fullscreen
Here the resolution is set to the native screen resolution which I had
in step 1.

I'm not sure if it is a bug or a design decision since switching to
native resolution also makes sense.
I'm marking the bug as wontfix since I don't want to diverge from
upstream in this behavior and the current one makes sense.
Feel free to discuss that question with upstream and if they change
how switching to fullscreen works it will be available in the package,
too.

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#798054: kodi: http header "Location:" is wrong handled

[Bálint Réczey]

Control: tags -1 moreinfo

Hi Vladmimir,

2015-09-04 23:14 GMT+02:00 Vladmimir Stavrinov :
> Package: kodi
> Version: 14.2+dfsg1-2
> Severity: normal
>
> Dear Maintainer,
>
> If You try to play MRL like this:
>
> http://host-1/uri-1
>
> and it returns http header:
> Location: http://host-2/uri-2/playlist.m3u8
>
> that in turn return somthing like chunklist.m3u8, then kodi trying to play 
> MRL like this:
>
> http://host-1/uri-1/chunklist.m3u8
>
> that is wrong. It should be
>
> http://host-2/uri-2/chunklist.m3u8
>

There were many changes in this area in Kodi. Could you please check
if the issue is still present in 17.x?

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#770358: xbmc: streams working with any player but xbmc

[Bálint Réczey]

Control: tags -1 moreinfo

Hi Vladmimir,

2014-11-20 18:15 GMT+01:00 Vladmimir Stavrinov :
> Package: xbmc
> Version: 2:13.2+dfsg1-4
> Severity: normal
>
> Dear Maintainer,
>
> Again, the problem like one reported before. The core issue is that those 
> streams below are working any with players, e.g. avplay, mplayer, vlc and 
> others, but xbmc won't play:
>
> #EXTM3U
> #EXT-X-TARGETDURATION:
> #EXTINF:0,NBC
> http://livestream-f.akamaihd.net/6396556_2598510_16987314_1_678@190588
> #EXTINF:0,CBS
> http://livestream-f.akamaihd.net/6907826_2706756_432cc990_1_678@181732

There were many changes in this area in Kodi. Could you please check
if the issue is still present in 17.x?

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#847701: kodi: Movie player unusable with libva error

[Bálint Réczey]

Control: reassign -1 libgl1-mesa-dri 13.0.3-1
Control: affects -1 kodi

2017-01-12 17:42 GMT+01:00 Leandro sullo sgorbio <lnofe...@cybervalley.org>:
> Il giorno mer, 11/01/2017 alle 20.54 +0100, Bálint Réczey ha scritto:
>
>> >> I don't think that your GPU is supported by i965-va-driver. So using the 
>> >> VA API
>> >> rendering engine won't work for you.
>> >
>> > Yes, the module is the i915. Also disabling all the acceleration engines
>> > the player does not work.
>>
>> Please disable both VDPAU and VAAPI and try playing a low resolution video
>> file. If it does not work please attach kodi's log and detail how it failed.
>
> I tried again with VDPAU and VAAPI disabled and again, the reproduction
> of a "low resolution video" :-) did not work.
>
> These are the relevant (I hope) lines of log:
>
> 17:29:33.623 T:139943960140672  NOTICE: VideoPlayer:
> Opening: /dati/Film/Serie TV/Star Trek TNG/StarTrek.TNG-s01e03-The Naked
> Now (Contaminazione).avi
> 17:29:33.623 T:139943960140672 WARNING: CDVDMessageQueue(player)::Put
> MSGQ_NOT_INITIALIZED
> 17:29:33.624 T:139940386023168  NOTICE: Creating InputStream
> 17:29:33.631 T:139940386023168  NOTICE: Creating Demuxer
> 17:29:33.845 T:139940386023168  NOTICE: Opening stream: 0 source: 256
> 17:29:33.845 T:139940386023168  NOTICE: Creating video codec with codec
> id: 13
> 17:29:33.845 T:139940386023168  NOTICE: CDVDVideoCodecFFmpeg::Open()
> Using codec: MPEG-4 part 2
> 17:29:33.846 T:139940386023168  NOTICE: Creating video thread
> 17:29:33.846 T:139940386023168  NOTICE: Opening stream: 1 source: 256
> 17:29:33.846 T:139940180850432  NOTICE: running thread: video_thread
> 17:29:33.846 T:139940386023168  NOTICE: Finding audio codec for: 86017
> 17:29:33.847 T:139940386023168  NOTICE: Creating audio thread
> 17:29:33.847 T:139940147287808  NOTICE: running thread:17:29:33.623
> T:139943960140672  NOTICE: VideoPlayer: Opening: /dati/Film/Serie
> TV/Star Trek TNG/StarTrek.TNG-s01e03-The Naked Now (Contaminazione).avi
...
> 17:30:17.611 T:139940180850432 WARNING: Previous line repeats 226 times.
> 17:30:17.611 T:139940180850432 WARNING: CRenderManager::WaitForBuffer -
> timeout waiting for buffer
> 17:30:21.925 T:139943960140672 WARNING: Previous line repeats 2 times.
> 17:30:21.925 T:139943960140672  NOTICE: CVideoPlayer::CloseFile()
> 17:30:21.925 T:139943960140672  NOTICE: VideoPlayer: waiting for threads
> to exit
> 17:30:21.931 T:139940386023168  NOTICE: CVideoPlayer::OnExit()
> 17:30:21.931 T:139940386023168  NOTICE: Closing stream player 1
> 17:30:21.931 T:139940386023168  NOTICE: Waiting for audio thread to exit
> 17:30:22.085 T:139940147287808  NOTICE: thread end:
> CVideoPlayerAudio::OnExit()
...
> The file is:
>
> StarTrek.TNG-s01e03-The Naked Now (Contaminazione).avi: RIFF
> (little-endian) data, AVI, 640 x 480, 25.00 fps, video: DivX 5, audio:
> MPEG-1 Layer 3 (stereo, 48000 Hz)
>
>> > So with this GPU this version of kodi is unusable?
>>
>> Most likely kodi is usable but video decoding will be slow thus you
>> can watch only low resolution videos (max ~720p) or videos which can use 
>> fast codecs for
>> decoding.

It looks like the system is really slow for the video. I have
reinstalled a similar system and playing videos was very slow on it,
indeed.

The system:
$ cat /proc/cpuinfo
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 28
model name: Intel(R) Atom(TM) CPU N270   @ 1.60GHz
stepping: 2
microcode: 0x208
cpu MHz: 1067.000
cache size: 512 KB
physical id: 0
siblings: 2
core id: 0
cpu cores: 1
...

# lspci -v -s 00:02.1
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME,
943/940GML Express Integrated Graphics Controller (rev 03)
Subsystem: Fujitsu Technology Solutions Mobile 945GM/GMS/GME,
943/940GML Express Integrated Graphics Controller
Flags: bus master, fast devsel, latency 0
Memory at f818 (32-bit, non-prefetchable) [size=512K]
Capabilities: [d0] Power Management version 2


I have collected some profiling data by running:

$ perf record -g kodi

Which shows that ~70% of the time is spent in intel's mesa driver:

$ perf report --sort comm,dso | cat
Failed to open /tmp/perf-6001.map, continuing without symbols
# To display the perf.data header info, please use
--header/--header-only options.
#
#
# Total Lost Samples: 0
#
# Samples: 406K of event 'cycles:p'
# Event count (approx.): 4725363215008
#
# Children  Self  Command  Shared Object
#     ...  ..
#
72.68%71.68%  kodi.bin i915_dri.so
|
|--18.88%--0
| 

Bug#772517: xbmc crashes with sigabrt or sigsegv while playing music with visualizer enabled

[Bálint Réczey]

Control: fixed -1 2:17.0~rc2+dfsg1-1

2014-12-28 10:37 GMT+01:00 Bálint Réczey <bal...@balintreczey.hu>:
> Hi Mike,
>
> 2014-12-08 1:30 GMT+01:00 Mike Edwards <pf-debian-b...@mirkwood.net>:
>> Package: xbmc
>> Version: 2:13.2+dfsg1-4
>> Severity: important
>>
>> Dear Maintainer,
>>
>>* What led up to the situation?
>> Playing music in xbmc with visualizer enabled.
>>* What exactly did you do (or not do) that was effective (or
>>  ineffective)?
>> Setting visualizer to 'none' appears to avoid the crash.
> Does it happen with all visualizer plugins or with just one particular?
> Could you please install xbmc-dbg and libav-dbg to have both XBMC and
> Libav debug symbols as well when creating coredumps?
>
> From the logs it looks like a memory handling problem.
> Could you please run xbmc in Valgrind like and collect the errors?:
> valgrind valgrind --trace-children=yes -- xbmc

Many memory handling issues have been fixed in Kodi since then, most
likely this is gone, too.
Please reopen if it still occurs.

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#847701: kodi: Movie player unusable with libva error

[Bálint Réczey]

Control: tags -1 moreinfo

Hi Leandro,

2016-12-10 23:40 GMT+01:00 Leandro Noferini :
> Sebastian Ramacher  writes:
>
>
> [...]
>
>>>00:02.0 VGA compatible controller: Intel Corporation Atom Processor
>>>D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller (rev 02) (prog-if
>>>00 [VGA controller])
>>>Subsystem: Intel Corporation Atom Processor
>>> D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
>>> Flags: bus master, fast devsel, latency 0, IRQ 29
>>> Memory at e020 (32-bit, non-prefetchable) [size=512K]
>>>I/O ports at 20c0 [size=8]
>>>Memory at d000 (32-bit, prefetchable) [size=256M]
>>>Memory at e010 (32-bit, non-prefetchable) [size=1M]
>>> [virtual] Expansion ROM at 000c [disabled] [size=128K]
>>>Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
>>>Capabilities: [d0] Power Management version 2
>>>Kernel driver in use: i915
>>>Kernel modules: i915
>>
>> I don't think that your GPU is supported by i965-va-driver. So using the VA 
>> API
>> rendering engine won't work for you.
>
> Yes, the module is the i915. Also disabling all the acceleration engines
> the player does not work.

Please disable both VDPAU and VAAPI and try playing a low resolution video
file. If it does not work please attach kodi's log and detail how it failed.

>
> So with this GPU this version of kodi is unusable?

Most likely kodi is usable but video decoding will be slow thus you
can watch only
low resolution videos (max ~720p) or videos which can use fast codecs for
decoding.

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#850467: kodi: Wrong "device" path for lirc

[Bálint Réczey]

Hi,

2017-01-06 21:27 GMT+01:00 Alec Leamas :
> On Fri, 06 Jan 2017 20:27:05 +0100 Thomas Renard  wrote:
>
>>
>> kodi is hard coded to the wrong "device" path to lirc.
>> The binary tries /dev/lircd but the "device" (which is a socket!)
>> can be found at /var/run/lirc/lircd.
>
> Hi!
>
> lirc maintainer speaking... note that the /var/run/lirc/lircd path just is a
> default configuration value from a lirc user's point of view. Specifically,
> in scenarios with several remotes (e. g., one doing ir blasting) the path
> could be something else. So, even if changing the hardcoded default will
> solve Thomas's  problem, it will not solve all users.

Thanks for the comments!
I plan syncing the default device with lirc in the next upload to at leas cover
users with default configuration.

>
> A proper fix for this needs to be something accepted by upstream, I guess.

Kodi's build system allows setting the default device through a
./configure option
thus I think this does not have to be upstreamed.

Do you mean upstreaming a more complex device detection logic?

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#845859: kodi: switch to build depend on the metapackage default-libmysqlclient-dev

[Bálint Réczey]

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

Hi Otto,

2016-11-26 23:08 GMT+01:00  :
> Package: kodi
> Severity: important
>
> Hi!
>
> This package build depends on libmysqlclient-dev. It should instead
> build-depend on default-libmysqlclient-dev metapackage, and end up
> having the run-time dependency of the libmysqlclient implementation
> Debian has chosen to use, currently MariaDB instead of Oracle MySQL.
>
> Announcement of new default-mysql-* metapackages:
> https://lists.debian.org/debian-devel-announce/2016/09/msg0.html
>
> Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server
>
> MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html
>
> Please update the depencies accordingly. In most cases the required
> change is:
>
> * BEFORE: Build-Depends: libmysqlclient-dev
>
> * AFTER: Build-Depends: default-libmysqlclient-dev

This looks fixed for some time.

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: remove xbmc from Debian testing/unstable?

[Bálint Réczey]

2016-10-26 13:12 GMT+02:00 Bálint Réczey <bal...@balintreczey.hu>:
> Hi James,
>
> 2016-10-26 12:48 GMT+02:00 James Cowgill <jcowg...@debian.org>:
>> On 26/10/16 11:00, Bálint Réczey wrote:
>>> Hi Paul,
>>>
>>> 2016-09-21 4:28 GMT+02:00 Paul Wise <p...@debian.org>:
>>>> On Tue, 2016-09-20 at 18:14 +0200, Bálint Réczey wrote:
>>>>
>>>>> I have changed kodi 17.x to provide xbmc*.
>>>>> The next upload to experimental will contain the fix.
>>>>
>>>> Excellent, thanks for that!
>>>
>>> It seems it is too much hassle to maintain the xbmc packages
>>> generated from kodi source, see #842141.
>>>
>>> I could append the current version to the xbmc package versions,
>>> but that would just confuse users.
>>
>> This is normal for transitional packages.
>>
>>> If you have any good idea please share it, otherwise I'm revert to
>>> provide the transitional packages from xbmc.
>>
>> This is what I'm about to upload to do the mplayer2 -> mpv transition:
>> https://anonscm.debian.org/cgit/pkg-multimedia/mpv.git/commit/?id=1ef5c58015019a414bd89c98b1de215c3fcbcca5
>>
>> That allows me to not epoch the whole of mpv.
>
> Thanks, let's try this then.

For the record somehow the 2: epoch sneaked in for kodi and I had to
adopt it everywhere in the 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

Re: [SCM] ffmpeg/jessie: Disable AVX optimization

[Bálint Réczey]

Hi Andreas,

2016-11-10 21:08 GMT+01:00 Andreas Cadhalpun <andreas.cadhal...@googlemail.com>:
> Hi Bálint,
>
> On 10.11.2016 09:57, Bálint Réczey wrote:
>> I guess there is a better way of fixing that upstream.
>
> It is already fixed in nasm in unstable.
> For jessie-backports you could either backport nasm or simply
> switch back to yasm. (yasm used to be better, but isn't actively
> developed anymore, while nasm improved recently.)

Thanks! I will try yasm. There is another build breakage in
jessie-backports for the record:
https://buildd.debian.org/status/fetch.php?pkg=ffmpeg=i386=7%3A3.2-2~bpo8%2B1=1478791165
...
gcc -I. -Isrc/ -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=2 -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC
-DOPJ_STATIC -DZLIB_CONST -DHAVE_AV_CONFIG_H -g -O2
-fstack-protector-strong -Wformat -Werror=format-security
-fno-strict-overflow -fstack-protector-all -fPIE   -std=c99
-fomit-frame-pointer -fPIC -pthread -I/usr/include/p11-kit-1
-I/usr/include/harfbuzz -I/usr/include/freetype2
-I/usr/include/fribidi -I/usr/include/freetype2  -I/usr/include/bs2b
-I/usr/include/freetype2 -I/usr/include/freetype2
-I/usr/include/fribidi  -I/usr/include/opus -D_REENTRANT
-I/usr/include/schroedinger-1.0 -I/usr/include/orc-0.4
-D_REENTRANT -I/usr/include/SDL2  -g -Wdeclaration-after-statement
-Wall -Wdisabled-optimization -Wpointer-arith -Wredundant-decls
-Wwrite-strings -Wtype-limits -Wundef -Wmissing-prototypes
-Wno-pointer-to-int-cast -Wstrict-prototypes -Wempty-body
-Wno-parentheses -Wno-switch -Wno-format-zero-length -Wno-pointer-sign
-O3 -fno-math-errno -fno-signed-zeros -fno-tree-vectorize
-Werror=format-security -Werror=implicit-function-declaration
-Werror=missing-prototypes -Werror=return-type -Werror=vla -Wformat
-fdiagnostics-color=auto -Wno-maybe-uninitialized  -MMD -MF
libavformat/asfenc.d -MT libavformat/asfenc.o -c -o
libavformat/asfenc.o src/libavformat/asfenc.c
In file included from src/libpostproc/postprocess.c:539:0:
src/libpostproc/postprocess_template.c: In function 'postProcess_MMX':
src/libpostproc/postprocess_template.c:3184:5: error: 'asm' operand
has impossible constraints
 __asm__ volatile(
 ^
src/libpostproc/postprocess_template.c:3101:5: error: 'asm' operand
has impossible constraints
 __asm__ volatile(
 ^

Cheers,
Balint

>
> Best regards,
> Andreas
>

___
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: [SCM] ffmpeg/jessie: Disable AVX optimization

[Bálint Réczey]

Hi Andreas,

I guess there is a better way of fixing that upstream.

Cheers,
Balint

2016-11-10 9:54 GMT+01:00  :
> The following commit has been merged in the jessie branch:
> commit a83c0818def5f87f50d786e52c84155addc0ecf9
> Author: Balint Reczey 
> Date:   Thu Nov 10 09:27:10 2016 +0100
>
> Disable AVX optimization
>
> It causes an error on jessie:
> nasm -f elf64  -DPIC -g -F dwarf -I./ -Isrc// -Pconfig.asm \
> -I /<>/libavcodec/x86/ -o libavcodec/x86/imdct36.o \
> src/libavcodec/x86/imdct36.asm
> src/libavcodec/x86/imdct36.asm:393: error: operation size not specified
> ...
>
> diff --git a/debian/rules b/debian/rules
> index b56ac70..8685750 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -51,6 +51,7 @@ CONFIG := --prefix=/usr \
> --disable-decoder=libschroedinger \
> --enable-avresample \
> --enable-avisynth \
> +   --disable-avx \
> --enable-gnutls \
> --enable-ladspa \
> --enable-libass \
>
> --
> ffmpeg packaging
>
> ___
> pkg-multimedia-commits mailing list
> pkg-multimedia-comm...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-commits

___
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#843169: xbmc-eventclients-j2me: uninstallable in unstable

[Bálint Réczey]

Control: tags -1 pending confirmed


2016-11-10 9:34 GMT+01:00 Andreas Beckmann :
> On Fri, 4 Nov 2016 14:34:09 + James Cowgill  wrote:
>> The xbmc-eventclients-j2me cannot be installed in unstable.
>> The kodi-eventclients-j2me package does not exist.
>
> since kodi-eventclients-j2me has been dropped, the transitional
> xbmc-eventclients-j2me package needs to be removed as well

Hi Andreas,

The fix is ready in git and will be uploaded soon.

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#813940: forked-daapd: Fails to scrobble plays to lastfm

[Bálint Réczey]

Control: forwarded -1
https://github.com/ejurgensen/forked-daapd/commit/d66a130064f4c9f7f4b02f586a67d4e1f3a470de
Control: tags -1 upstream fixed-upstream confirmed

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.
The fix will be in Stretch as part of the next upstream release of as
a cherry-picked patch.

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

[Bálint Réczey]

Hi Andreas,

2016-11-03 23:06 GMT+01:00 Andreas Cadhalpun <andreas.cadhal...@googlemail.com>:
> Hi Bálint,
>
> On 03.11.2016 13:00, Bálint Réczey wrote:
>> 2016-11-03 12:54 GMT+01:00 Balint Reczey <bal...@balintreczey.hu>:
>>> 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.
>
> The patch looks good, thanks for forwarding it upstream. (Even though
> one of the upstream developers has some peculiar ideas about correct
> code.)
>
>> If someone having the test file could test latest kodi in unstable
>> that  would be geat.
>
> There is a test file[1] in one of the merged bugs.
> However, testing the latest kodi in unstable is of limited use, since
> it was built against the same ffmpeg version currently in unstable.
>
> If you want to verify that the problem is fixed, you'd have to recompile
> kodi against 3.0.1 and test it with the current ffmpeg libraries (or
> the ones from 3.1.1).

Thank you for pointing to the test file. Proper testing would involve
a recompilation indeed, but since upstream does not want to
merge the patch anyway I don't feel this kind of testing necessary.

Cheers,
Balint

>
> Best regards,
> Andreas
>
>
> 1: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=832364;filename=test2.ts.gz;msg=67

___
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

[Bálint Réczey]

Hi Felipe,

2016-11-04 15:50 GMT+01:00 Felipe Sateler :
> On 4 November 2016 at 11:21, Balint Reczey  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.

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

[Bálint Réczey]

2016-11-03 12:54 GMT+01:00 Balint Reczey :
...
> On Fri, 14 Oct 2016 01:27:47 +0200 Andreas Cadhalpun
>  wrote:
> ...
>
>>
>> Hi,
>>
>> The relevant backtrace from the kodi_crashlog is:
...
>> 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.


If someone having the test file could test latest kodi in unstable
that  would be geat.

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

kodi mini transition 16.* -> 17.*

[Bálint Réczey]

Dear Release Team,

I would like to update kodi in unstable to the 17.x branch and this involves
updating reverse dependencies, too.

The following source packages need source updates:
kodi-pvr-argustv
kodi-pvr-dvbviewer
kodi-pvr-hdhomerun
kodi-pvr-iptvsimple
kodi-pvr-mediaportal-tvserver
kodi-pvr-mythtv
kodi-pvr-nextpvr
kodi-pvr-njoy
kodi-pvr-vdr-vnsi
kodi-pvr-vuplus
kodi-pvr-wmc
kodi-visualization-spectrum
kodiplatform

Most of the packages are maintained by me under Multimedia Team's umbrella.

In terms of 'ben' lingo, the transition has the following parameters:

Affected: .build-depends ~ /kodi-addons-dev/
Good: .build-depends ~ /kodi-addons-dev[^,]*17[^,]*,/
Bad: .build-depends ~ /kodi-addons-dev[^7^,]*,/

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: remove xbmc from Debian testing/unstable?

[Bálint Réczey]

Hi James,

2016-10-26 12:48 GMT+02:00 James Cowgill <jcowg...@debian.org>:
> On 26/10/16 11:00, Bálint Réczey wrote:
>> Hi Paul,
>>
>> 2016-09-21 4:28 GMT+02:00 Paul Wise <p...@debian.org>:
>>> On Tue, 2016-09-20 at 18:14 +0200, Bálint Réczey wrote:
>>>
>>>> I have changed kodi 17.x to provide xbmc*.
>>>> The next upload to experimental will contain the fix.
>>>
>>> Excellent, thanks for that!
>>
>> It seems it is too much hassle to maintain the xbmc packages
>> generated from kodi source, see #842141.
>>
>> I could append the current version to the xbmc package versions,
>> but that would just confuse users.
>
> This is normal for transitional packages.
>
>> If you have any good idea please share it, otherwise I'm revert to
>> provide the transitional packages from xbmc.
>
> This is what I'm about to upload to do the mplayer2 -> mpv transition:
> https://anonscm.debian.org/cgit/pkg-multimedia/mpv.git/commit/?id=1ef5c58015019a414bd89c98b1de215c3fcbcca5
>
> That allows me to not epoch the whole of mpv.

Thanks, let's try this then.

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: remove xbmc from Debian testing/unstable?

[Bálint Réczey]

2016-10-26 12:28 GMT+02:00 Paul Wise :
> On Wed, 2016-10-26 at 12:19 +0200, Fabian Greffrath wrote:
>
>> I'd suggest to re-apply (and maybe even increment) xbmc's epoch for kodi.
>
> That isn't going to fix the RC bug.
>
> The only options are:
>
>  * Generate the xbmc versions in a different way.

Using 2:17.x version for kodi and providing the transitional packages with
this version would solve the problem, but I don't like that solution.

>  * Move the xbmc transitional packages back to xbmc

This will result nicer versions for Stretch and later thus I plan
implementing that.

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: remove xbmc from Debian testing/unstable?

[Bálint Réczey]

2016-10-26 12:19 GMT+02:00 Fabian Greffrath :
> Bálint Réczey wrote:
>> Are you suggesting some other solution? I'm not sure I understand it then.
>> Xbmc has epoch which I got rid of with kodi.
>
> I'd suggest to re-apply (and maybe even increment) xbmc's epoch for kodi.
> What's the point in getting rid of an epoch, why is it even important?

It is ugly and confusing for many users.
The renaming of XBMC to Kodi is a good opportunity for getting rid of it.

___
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: remove xbmc from Debian testing/unstable?

[Bálint Réczey]

Hi Fabian,

2016-10-26 12:06 GMT+02:00 Fabian Greffrath <fab...@greffrath.com>:
> Bálint Réczey wrote:
>> If you have any good idea please share it, otherwise I'm revert to
>> provide the transitional packages from xbmc.
>
> Epochs have been invented for this exact use case.

Are you suggesting some other solution? I'm not sure I understand it then.
Xbmc has epoch which I got rid of with 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

Re: remove xbmc from Debian testing/unstable?

[Bálint Réczey]

Hi Paul,

2016-09-21 4:28 GMT+02:00 Paul Wise <p...@debian.org>:
> On Tue, 2016-09-20 at 18:14 +0200, Bálint Réczey wrote:
>
>> I have changed kodi 17.x to provide xbmc*.
>> The next upload to experimental will contain the fix.
>
> Excellent, thanks for that!

It seems it is too much hassle to maintain the xbmc packages
generated from kodi source, see #842141.

I could append the current version to the xbmc package versions,
but that would just confuse users.

If you have any good idea please share it, otherwise I'm revert to
provide the transitional packages from xbmc.

Cheers,
Balint

>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise

___
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

[Bálint Réczey]

Hi Dominik,

2016-10-06 23:15 GMT+02:00 Dominik George :
> Hi,
>
>> 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:
>
>> 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.
>
> I do not quite agree.
>
> The same would be true for /var/run, but there, the application or the
> init system is expected to create the relevant directories before
> dropping privileges.

/var/run is different, see very different wording in FHS.

http://www.pathname.com/fhs/2.2/fhs-5.13.html#FN37

5.13 /var/run : Run-time variable data

5.13.1 Purpose

This directory contains system information data describing the system
since it was booted. Files under this directory must be cleared
(removed or truncated as appropriate) at the beginning of the boot
process. Programs may have a subdirectory of /var/run; this is
encouraged for programs that use more than one run-time file.[footnote
37]

...

[37] /var/run should be unwritable for unprivileged users (root or
users running daemons); it is a major security problem if any user can
write in this directory. Process identifier (PID) files, which were
originally placed in /etc, must be placed in /var/run. The naming
convention for PID files is .pid. For example, the crond
PID file is named /var/run/crond.pid.

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#839941: whishlist ffmpeg

[Bálint Réczey]

Hi Marc,

2016-10-06 17:28 GMT+02:00 Struminski, Marc :
> Package: ffmpeg
> Severity: wishlist
>
> Hi maintainers,
>
> Is it possible to add libfreetype, nvenc, decklink and libmfx to ffmpeg in
> Debian.

Libfreetype seems to be possible.
nvenc is problematic because due to its license, but may be OK:
http://ffmpeg.org/pipermail/ffmpeg-devel/2016-April/193467.html

libmfx is not packaged.
decklink is not packaged either and seems to be non-free.

> When it is also possible libebur128.

libebur128 is already used.

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

[Bálint Réczey]

Control: tags -1 patch

2016-09-11 15:44 GMT+02:00 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/PIEByDefaultTransition

I have added the patch fixing the issue to the packaging repository:
https://anonscm.debian.org/gitweb/?p=pkg-multimedia/jack-audio-connection-kit.git


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#822555: ffmpeg: please compile with --enable-libtesseract

[Bálint Réczey]

Hi Sebastian,

2016-09-24 21:56 GMT+02:00 Sebastian Ramacher <sramac...@debian.org>:
> Hi
>
> On 2016-09-07 03:33:38, Bálint Réczey wrote:
>> Control: tags -1 confirmed patch
>>
>> Hi Jan,
>>
>> 2016-04-25 12:43 GMT+02:00 Jan Gerber <j...@mailb.org>:
>> > Package: ffmpeg
>> > Version: 7:3.0.1-3
>> > Severity: wishlist
>> >
>> > Dear Maintainer,
>> >
>> > FFmpeg 3.0 introduced a new ocr filter that depends on libtesseract.
>> > Would be nice to see this enabled in Debian.
>>
>> I have prepared a patch which may be enough.
>> It needs testing however. Sebastian, what do you think?
>
> I'm not a huge fan of adding more -extra flavors [1], but the patch looks 
> okayish.
> The dh_auto_build-arch override may need to be updated, though.

It seems to still work well since libavfilter is recompiled properly.
The package also works, it performs OCR.

I have tested it using the image and script from here:
http://ffmpeg-users.933282.n4.nabble.com/How-to-use-ocr-filter-td4672454.html

ffprobe -show_entries frame_tags=lavfi.ocr.text -f lavfi -i "movie=img.png,ocr"

One also need to install tesseract-ocr-eng to make it work.

Pushing the commit to ffmpeg.git.

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

[Bálint Réczey]

Hi Wookey,

2016-09-25 0:49 GMT+02:00 Wookey <woo...@wookware.org>:
> 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 <woo...@debian.org>:
>
>> > 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 <ste...@saraev.ca>
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(-)


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

[Bálint Réczey]

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 :
> Package: kodi
> Severity: normal
>
> Dear Maintainer,
>
> kodi contains an embedded copy of libsquish:
> in tools/depends/native/libsquish-native
>
> I have recently packaged libsquish, and it is now avilable in the archive:
> https://tracker.debian.org/pkg/libsquish
>
> In doing this I examined all the embedded copies, checking them for
> changes, and have merged all the extra features into the Debian
> package. Thus it should be straighforward to start using the system
> library instead of the embedded copy, without any API changes.
>
> The changes have also been sent upstream and will hopefully appear
> in libsquish 1.14 at some point.
>
> The kodi version was forked around v1.10 and has some 1.13 features
> backported as well as some entirely new functionality (BC4 and BC5
> compression format support, BGRA as well as RGBA testure source format
> support, pkconfig support, independent pitch and cell size in
> textures, and BlockMSE calculation). As all of these are included
> as-is in this version.
>
> Debian policy 
> https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles
> say that embedded copies should not be used if the library is available in 
> Debian, and
> https://wiki.debian.org/EmbeddedCodeCopies gives a bit more background.
>
> I am not familiar with the kodi build system, so have not attempted to
> provide a patch as that should be much easier for you, but of course
> I'll help if you need some.
>
> The full set of packages affected is:
>- nvidia-texture-tools 1.7 (src/nvtt/squish)
>- 0ad 1.7 (libraries/source/nvtt/src/src/nvtt/squish/)
>- spring  1.10  (rts/lib/squish)
>- openimageio 1.10+ (1.10+metric) (src/dds.imageio/squish)
>- xbmc1.10+ (1.10+metric/BC45) (lib/libsquish)
>- kodi1.10+ (1.10+metric/BC45) 
> (tools/depends/native/libsquish-native)
>- mame1.13+ (BC45) (3rdparty/bgfx/3rdparty/libsquish)
>
> Hope this is useful.

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.

I'll close this bug when Kodi 17.x enters 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#831591: ffmpeg: kodi crash

[Bálint Réczey]

Control: fixed -1 7:3.1.3-1

Hi Carl,

2016-09-07 20:21 GMT+02:00 Carl Eugen Hoyos :
> Hi Bálint!
>
>> I went throught the unclassified bugs and set the
>> proper state to help tracking them.
>
> This bug (#831591) and #832364 contain neither backtrace
> nor bisect. Note that they most likely have to be fixed
> in Kodi, FFmpeg will (afaict) not break ABI once more
> for the 3.1 release series to work-around bugs in other
> projects.
> (This analysis may of course be wrong but we cannot
> know better so far.)

I'm marking this bug fixed and close it because it does not affect
any package in unstable/testing.

I believe there was an unintended ABI breakage in FFmpeg and
it caused the kodi crash but since no one is really interested in
debugging that after recompiling solved it there is little value in
keeping it open.

>
> Bug #797965 contains no sample, I cannot reproduce.
> (Same for #833722 and #797963 which are marked as
> needs-more-info.)

In #797965 Christoph provided a way of reproducing it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797965#126

Andreas even provided a patch thus I believe it is a valid bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797965#116

If I ever find time I'll create a reproducer based on Christoph's
guide, but it is unlikely to happen before Stretch's release.

>
> Bug #810224 is invalid: Behaviour is exactly as
> requested by you, my original analysis was wrong.

Closed that one, thanks.

>
> I do not understand why it makes sense to keep #493705
> and #528080 open: I believe Debian decided many years
> ago that they will not be fixed, FFmpeg has repeated
> its opinion that there is no bug last year (when
> Google stopped allowing such binaries in Android).
> (If you want you can fix both bugs anytime by adding
> --disable-asm to the configure options for x86_32.)

Those are known limitations of the Debian package and the bugs'
state reflects that.

> I have fixed #785690 upstream today, don't know how
> you proceed with the report here.
> http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=3e886e7

Marked accordingly, thanks.
It can be closed with uploading a new upstream release containing the fix.
I don't think that this issue warrants a back-port.

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: remove xbmc from Debian testing/unstable?

[Bálint Réczey]

Hi Paul,

2016-09-01 8:21 GMT+02:00 Paul Wise <p...@debian.org>:
> On Thu, 2016-09-01 at 08:17 +0200, Bálint Réczey wrote:
>
>> Because this way we can get rid of the epoch.
>
> You can have different version numbers between source and binary
> packages. So src:kodi 16.1+dfsg1-2 can build xbmc 2:13.2+dfsg1-6.
>
> You may also want to drop the orig.tar.gz from xbmc too.

I have changed kodi 17.x to provide xbmc*.
The next upload to experimental will contain the fix.

Thanks for the hints.

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#822555: ffmpeg: please compile with --enable-libtesseract

[Bálint Réczey]

Control: tags -1 confirmed patch

Hi Jan,

2016-04-25 12:43 GMT+02:00 Jan Gerber :
> Package: ffmpeg
> Version: 7:3.0.1-3
> Severity: wishlist
>
> Dear Maintainer,
>
> FFmpeg 3.0 introduced a new ocr filter that depends on libtesseract.
> Would be nice to see this enabled in Debian.

I have prepared a patch which may be enough.
It needs testing however. Sebastian, what do you think?

Maybe we could enable some other features as well.

Cheers,
Balint
From 72f545c2900bf65ea44e4f9465b08332c4b0610e Mon Sep 17 00:00:00 2001
From: Balint Reczey 
Date: Tue, 6 Sep 2016 14:34:25 +0200
Subject: [PATCH] Enable OCR using Tesseract in libavfilter-extra*

Closes: 822555
---
 debian/control  | 54 -
 debian/libavfilter-extra6.install   |  1 +
 debian/libavfilter-extra6.install.powerpc   |  2 ++
 debian/libavfilter-extra6.lintian-overrides |  9 +
 debian/rules| 19 +-
 5 files changed, 74 insertions(+), 11 deletions(-)
 create mode 100644 debian/libavfilter-extra6.install
 create mode 100644 debian/libavfilter-extra6.install.powerpc
 create mode 100644 debian/libavfilter-extra6.lintian-overrides

diff --git a/debian/control b/debian/control
index e7bf9d7..2841992 100644
--- a/debian/control
+++ b/debian/control
@@ -68,6 +68,8 @@ Build-Depends:
  libavc1394-dev [linux-any],
 # autodetected: indev 'jack'
  libjack-jackd2-dev,
+# missing dependency of libtesseract-dev #836849
+ libleptonica-dev,
 # autodetected for the tiff decoder
  liblzma-dev,
 # --enable-libmodplug
@@ -108,6 +110,8 @@ Build-Depends:
  libspeex-dev,
 # --enable-libssh
  libssh-gcrypt-dev,
+# --enable-libtesseract (used only in -extra flavor)
+ libtesseract-dev,
 # --enable-libtheora
  libtheora-dev,
 # --enable-libtwolame
@@ -370,13 +374,61 @@ Description: FFmpeg library containing media filters - runtime files
  .
  This package contains the runtime files.
 
+Package: libavfilter-extra6
+Architecture: any
+Section: libs
+Priority: extra
+Multi-Arch: same
+Conflicts: libavfilter6
+Provides: libavfilter-extra
+Pre-Depends:
+ ${misc:Pre-Depends}
+Depends:
+ ${shlibs:Depends},
+ ${misc:Depends}
+Description: FFmpeg library with extra media filters - runtime files
+ FFmpeg is the leading multimedia framework, able to decode, encode, transcode,
+ mux, demux, stream, filter and play pretty much anything that humans and
+ machines have created. It supports the most obscure ancient formats up to the
+ cutting edge.
+ .
+ This library provides a generic audio/video filtering framework containing
+ several filters, sources and sinks.
+ .
+ This package replaces the libavfilter6 package and contains the
+ following additional filters:
+ .
+  * Optical Character Recognition (uses Tesseract)
+ .
+ Because this package links against libraries that are licensed under
+ Apache License 2.0, the resulting binaries are distributed under the
+ GPL version 3 or later.
+
+Package: libavfilter-extra
+Architecture: all
+Section: metapackages
+Priority: extra
+Multi-Arch: foreign
+Depends:
+ libavfilter-extra6,
+ ${misc:Depends}
+Description: FFmpeg library with extra filters (metapackage)
+ FFmpeg is the leading multimedia framework, able to decode, encode, transcode,
+ mux, demux, stream, filter and play pretty much anything that humans and
+ machines have created. It supports the most obscure ancient formats up to the
+ cutting edge.
+ .
+ This metapackage depends on the latest version of the libavfilter variant
+ that offers additional filter support. Application packages can depend
+ on it if they require or suggest this variant in a robust manner.
+
 Package: libavfilter-dev
 Architecture: any
 Section: libdevel
 Multi-Arch: same
 Depends:
  libavcodec-dev (= ${binary:Version}),
- libavfilter6 (= ${binary:Version}),
+ libavfilter6 (= ${binary:Version}) | libavfilter-extra6 (= ${binary:Version}),
  libavformat-dev (= ${binary:Version}),
  libavresample-dev (= ${binary:Version}),
  libavutil-dev (= ${binary:Version}),
diff --git a/debian/libavfilter-extra6.install b/debian/libavfilter-extra6.install
new file mode 100644
index 000..1b2648c
--- /dev/null
+++ b/debian/libavfilter-extra6.install
@@ -0,0 +1 @@
+usr/lib/*/libavfilter.so.*
diff --git a/debian/libavfilter-extra6.install.powerpc b/debian/libavfilter-extra6.install.powerpc
new file mode 100644
index 000..628ec8f
--- /dev/null
+++ b/debian/libavfilter-extra6.install.powerpc
@@ -0,0 +1,2 @@
+usr/lib/*/libavfilter.so.*
+usr/lib/*/*/libavfilter.so.*
diff --git a/debian/libavfilter-extra6.lintian-overrides b/debian/libavfilter-extra6.lintian-overrides
new file mode 100644
index 000..5e6db9b
--- /dev/null
+++ b/debian/libavfilter-extra6.lintian-overrides
@@ -0,0 +1,9 @@
+# According to Debian policy [1], non position independent code is permitted
+# in a shared library on i386 and position independent code may have a
+# performance penalty, especially on i386.
+# 

Bug#831591: ffmpeg: kodi crash

[Bálint Réczey]

Hi Carl,

2016-09-06 12:41 GMT+02:00 Carl Eugen Hoyos :
> Hi!
>
>> Knowing what broke could be
>> interesting for FFmpeg devs
>
> It would most likely be even more interesting
> for the Kodi developers: We currently assume
> that there is an unknown bug in Kodi...

Well, the first suspect is ffmpeg because updating ffmpeg
broke kodi while there were no planned ABI change.

>
>> > Slightly related: More that half of the open tickets
>> > concerning FFmpeg in Debian either contain no samples to
>> > reproduce or will not be fixed or were never reproducible.
>> > If another FFmpeg developer were interested in fixing
>> > bugs reported here it would be very difficult for him to
>> > find something useful due to the low snr.
>>
>> Those can be marked with the moreinfo tag and IMO it is
>> OK to close them after a reasonable amount of time if
>> the originator is asked to provide a test file but she/he
>> did not.
>
> Are five months enough?

Generally I use a few years if I'm not pretty sure the bug is gone.
I agree with the concept that bugs are part of the documentation
thus closing possibly valid bugs is decreasing the quality of the
documentation, thus the software.

Note that there are way more users of stable and a bug not
reproducible on unstable may show up in stable later.

I went throught the unclassified bugs and set the proper state
to help tracking them.

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#832364: kodi: Crashes on trying to play any TV recording

[Bálint Réczey]

Hi Tobias,

2016-08-19 19:54 GMT+02:00 Tobias Grimm :
> Hello Balint,
>
>> Tobias, could you please share the test file or test kodi again?
>
> I've just tested it. It crashes when playing a VDR TS recording with
> 16.1+dfsg1-1 and after upgrading to 16.1+dfsg1-2 it works fine for the
> same recording.

Could you please share the recording with Carl instead? He is an FFmpeg
dev thus probably can find the problem very quickly and maybe other
devs are interested as well.

>
> So I think 832364 can be closed.

I think merging with an other very similar bug reflects the situation
better (thus I did so).

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

[Bálint Réczey]

Hi Carl,

2016-09-06 11:39 GMT+02:00 Carl Eugen Hoyos :
> Hi Bálint!
>
>> I don't have the test file.
>
> In this case I suggest to close the relevant tickets:
> We cannot reproduce, there is no backtrace and no bisect.

Tobias has test files as he wrote in #832364 and he would
share it privately.

>
> Since FFmpeg has made three point releases with the ABI
> that is apparently incompatible with (old) Kodi, it is
> very unlikely that it will be changed again (we would
> likely brake mpv that intentionally uses the invalid API).

From practical POV I'm OK with closing this bug since it does
not affect unstable nor testing. Knowing what broke could be
interesting for FFmpeg devs and in case the change is reverted
I could update ffmpeg in jessie-backports without recompiling
kodi. This is why I have not back-ported latest ffmpeg yet.


>
> Slightly related: More that half of the open tickets
> concerning FFmpeg in Debian either contain no samples to
> reproduce or will not be fixed or were never reproducible.
> If another FFmpeg developer were interested in fixing
> bugs reported here it would be very difficult for him to
> find something useful due to the low snr.

Those can be marked with the moreinfo tag and IMO it is
OK to close them after a reasonable amount of time if
the originator is asked to provide a test file but she/he
did not.

Thanks for helping in managing the FFmpeg bugs in Debian!

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: remove xbmc from Debian testing/unstable?

[Bálint Réczey]

Hi Paul,

2016-09-01 4:43 GMT+02:00 Paul Wise :
> Hi,
>
> Now that kodi is in Debian, should xbmc get removed?
>
> If you agree, please file a removal bug report:
>
> https://wiki.debian.org/ftpmaster_Removals
>
> If I don't hear back in 2 weeks I will file one.

Xbmc packages are empty now helping the migration to kodi. I think
they should be
released with stretch.

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

[Bálint Réczey]

Hi,

2016-08-27 15:48 GMT+02:00 Carl Eugen Hoyos :
> Hi!
>
>> 2016-08-24 22:55 GMT+02:00 Carl Eugen Hoyos :
>> >
>> > First, please understand that so far, no ABI breakage between
>> > FFmpeg 3.0 and FFmpeg 3.1 was found, only the usage of
>> > non-public api (that we decided to work-around for 3.1.1).
>>
>> OK, then assume that Kodi uses non-public API and the rebuild
>> made kodi use the latest ABI.
>
> I don't know!
> I just wanted to point out that so far, the "bugs" that were
> worked-around in FFmpeg 3.1.1 were bugs in other applications.
>
> I still do not understand completely: Is the crash still reproducible
> after recompiling Kodi or not?

Sorry for not being clear on this. In #832364 the test did show that
the crash is gone with the rebuild. My only assumption was that
it used to be caused by the ABI change.
Latest kodi works well with latest ffmpeg.


>
>> Can I somehow find easily the places where the non-public API is used?
>
> I don't know but...
>
>> > Am I correct that no backtrace was provided for this issue?
>>
>> Yes, AFAIK.
>
> ... adding a backtrace should work fast, no?
> If another developer looks at the backtrace, he might know what the
> issue is.

I don't have the test file. This has been discussed in #832364.

>
>> > But even with a backtrace, I fear a bisect may be necessary.
>
> Bisecting FFmpeg takes less than 20 minutes here, I know it would take
> you longer but if the backtrace does not help, this is the only way to
> find out what the issue is.
> I can try helping to create a specific configure line to speed up the
> backtrace.

___
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#820416: kodi: FTBFS in testing (Segmentation fault)

[Bálint Réczey]

Hi Santiago,

2016-08-24 17:36 GMT+02:00 Santiago Vila :
> Hi.
>
> Any progress on this? This is still reproducible. I'm attaching a
> build log for the version which has just entered testing.

I have uploaded a new version to experimental with two related changes.

One is not failing the build when the test fails. This is not nice,
but the tests
were completely broken while kodi ran fine on my test system.

The second is running the tests with Valgrind when it is installed to have
better chance at finding allocation errors. I also proposed the change at
upstream listing an error which could mess up mutex handling:
https://github.com/xbmc/xbmc/pull/10334

>
> On Sun, 17 Apr 2016, Balint Reczey wrote:
>
>> It suggests there is something wrong with the mutex handling and TSAN seems 
>> to confirm that:
>> [...]
>> I need to test if the problem still exists in upstream master and verify if
>> it is not a false positive TSAN warning and the root cause is indeed here.
>
> Could you translate that into a language that a non-programmer
> could understand?
>
>> I'm setting the bug's severity to normal because while it is reproducible
>> the FTBFS does not happen on Debian's buildds [...]
>
> Hmm. I'm not going to enter into a severity war, but you should be
> aware that the theory that a FTBFS is not RC because "it does not
> happen" in Debian's buildds has many flaws.
>
> For example, for a package which FTBFS randomly, it is completely
> useless, as a successful build just means that we were lucky that
> time.

I'm trying to apply definitions from here:
https://www.debian.org/Bugs/Developer#severities

I don't like having this bug, but if a program fails to build 50% of
the time but runs fine it can be released IMO since users are not
affected.

>
> We should better not care too much about what happened in the
> autobuilders the last time it was tried, we should care more about
> what could happen the next time.
>
> I'm using sbuild and the autobuilders are using sbuild as well
> (or a variant of it).
>
> If you think this may not happen in official autobuilders, could you
> please explain why?

I don't think that it may not happen, but I say that it did not seem to
happen so far which makes me think it won't happen often and when
it happens autobuilders will try again anyway.

I understand that having this issue is painful for people like you doing the
hard work of rebuilding many packages and I'm trying to help.

Starting with 17.x the tests won't make the build fail until they run
reliably thus
you'll be able to rebuild kodi. Valgrind will also help upstream in catching
bugs earlier.

>
> (Because my machine does not have enough memory? How would I know that
> in advance when we don't have a Build-Memory control field?)
>
>> thus does not prevent rebuilding the package when needed.
>
> It does prevent me from rebuilding the package, which makes the
> software non-free for me and apparently anybody who does not have a
> machine with 32 GB of RAM (which is still a lot of people).

I guess you can build it with "DEB_BUILD_OPTIONS=nocheck", thus
this seems to be a bit of exaggeration.

>
> I would say that would deserve important severity at least.

I think the bug does not fit "important"'s definition [1] but feel free
to raise it.
I agree with you on this bug being valid and needs to be fixed
no matter what the severity is.

Cheers,
Balint

>
> (I said 32 GB just as an example, but if that's a more or less
> accurate summary of this bug, I'd like to know the exact figure).
>
> Thanks.


[1] "important: a bug which has a major effect on the usability of a
package, without rendering it completely unusable to everyone."

___
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

[Bálint Réczey]

Hi,

2016-08-18 17:59 GMT+02:00 Bálint Réczey <bal...@balintreczey.hu>:
> Hi,
>
> 2016-07-17 23:17 GMT+02:00 Sebastian Ramacher <sramac...@debian.org>:
>> Control: severity -1 serious
>>
>> On 2016-07-17 21:38:13, Carl Eugen Hoyos wrote:
>>> Kodi reports "FFmpeg version: 3.0.1-3":
>>> Could somebody test if the crash disappears after Kodi gets recompiled 
>>> against
>>> current FFmpeg?
>>
>> Wasn't 3.1.1 supposed to revert all the ABI breakage? Raising the severity 
>> until
>> this is resolved.
>
> I have just uploaded a new kodi package to unstable thus this problem
> can be easily tested.

Apparently the ABI breakage is still present in 7:3.1.2-1.
See #832364 for details.

Carl, it would be important to track the breakage.
http://abi-laboratory.pro/tracker/timeline/ffmpeg/ may give some help.

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: [SCM] xwax/master: Add bindnow hardening, disable pie for performance reasons

[Bálint Réczey]

Hi,

2016-08-16 15:46 GMT+02:00  :
> The following commit has been merged in the master branch:
> commit 48ef7795f583e619765180452bb7d3b6976e96a6
> Author: Daniel James 
> Date:   Tue Aug 16 14:45:48 2016 +0100
>
> Add bindnow hardening, disable pie for performance reasons
>

Do you have some good tests/results for measuring the performance differences?

I'm interested because I'm working on enabling those archive-wide.

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

[Bálint Réczey]

Hi,

2016-07-17 23:17 GMT+02:00 Sebastian Ramacher :
> Control: severity -1 serious
>
> On 2016-07-17 21:38:13, Carl Eugen Hoyos wrote:
>> Kodi reports "FFmpeg version: 3.0.1-3":
>> Could somebody test if the crash disappears after Kodi gets recompiled 
>> against
>> current FFmpeg?
>
> Wasn't 3.1.1 supposed to revert all the ABI breakage? Raising the severity 
> until
> this is resolved.

I have just uploaded a new kodi package to unstable thus this problem
can be easily tested.

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#832364: kodi: Crashes on trying to play any TV recording

[Bálint Réczey]

Hi,

2016-08-01 18:23 GMT+02:00 James Cowgill <jcowg...@debian.org>:
> Hi,
>
> On 01/08/16 13:25, Bálint Réczey wrote:
>> 2016-07-31 17:44 GMT+02:00 Tobias Grimm <tobias.gr...@e-tobi.net>:
>>> I can confirm this. Running 16.1+dfsg1-1 worked, then I've updated the
>>> system and it crashes when playing TS recordings (playing via a PVR addon
>>> works fine).
>>>
>>> I've rebuilt the package (had to apply some fixes to do so) and now it
>>> runs fine.
>>
>>
>> This sounds like a result of an unhandled ABI breakage.
>> Could you please find the library causing this from the crash dump or
>> by selectively downgrading them?
>
> Could this be cause by bug #831591 in ffmpeg?

I think it could. I have just uploaded a new kodi version to unstable
which should work with the new ABI if it changed.

Tobias, could you please share the test file or test kodi again?

Unstable and testing has the same ffmpeg. If you run kodi from testing
(16.1+dfsg1-1) it should crash but kodi from unstable (16.1+dfsg1-2)
should work fine if the root cause is ABI breakage and it is not fixed
yet in ffmpeg.

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#832364: kodi: Crashes on trying to play any TV recording

[Bálint Réczey]

Hi Tobias,

2016-07-31 17:44 GMT+02:00 Tobias Grimm :
> I can confirm this. Running 16.1+dfsg1-1 worked, then I've updated the
> system and it crashes when playing TS recordings (playing via a PVR addon
> works fine).
>
> I've rebuilt the package (had to apply some fixes to do so) and now it
> runs fine.


This sounds like a result of an unhandled ABI breakage.
Could you please find the library causing this from the crash dump or
by selectively downgrading them?

I don't have the video files for testing. :-(

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: kodi: Jasper removal

[Bálint Réczey]

Hi Mattia,

2016-06-27 15:51 GMT+02:00 Mattia Rizzolo <mat...@debian.org>:
> Hi Balint,
>
> On Tue, Mar 15, 2016 at 02:45:43PM +0100, Bálint Réczey wrote:
>> > Hi, jasper will be removed from Debian for the stretch release (and
>> > following that, the archive in general).
>> Kodi 17 wil not use jasper [1] and is expected to be release before
>> Stretch's freeze.
>> I plan fixing this bug with the 17.0 upstream release.
>
> Can you please fix it before?
> I see there is an alpha release avaialbe that should already contain
> that fix, or maybe backport the patch.
>
> In a few days kodi is going to be the very last blocker for jasper
> removal (as today I NMUed a bunch, and paved the way for the others).

The new alpha releases are fixed indeed, but the fix is not simple and I'm
not comfortable with either back-porting it either with uploading 17.0
alphas to unstable. There are many add-on packages depending on Kodi's
API and they need to be updated as well with each major Kodi update
and I'm not sure if all the addon upstreams are ready for Kodi 17 already.

I'm uploading a fixed kodi 17 to experimental soon, but please keep jasper in
testing for kodi for a few short months.

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: Making Kodi installable again in testing

[Bálint Réczey]

HI Pander,

2016-06-09 13:54 GMT+02:00 Pander :
> Dear all,
>
> Kodi (version 15.2 and version 16.1) isn't installable at the moment in
> Debian testing. Could someone please fix the dependencies for this so
> testing on this can move forward?
>
> Thanks,
>
> Pander
>
>
> Details with Raspbian on an Raspberry Pi are:
>
>
>
> # cat /etc/apt/sources.list
> deb [arch=armhf] http://mirrordirector.raspbian.org/raspbian/ testing
> main contrib non-free rpi
> deb [arch=armhf] http://archive.raspberrypi.org/debian/ jessie main ui

Please note that you use a Debian derivative distro (Raspbian), not Debian.
While we help them in creating derivatives by integrating many patches we
don't support those packages directly.

Please contact them to fix the installation problem.

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#825873: kodi-data depends on font unavailable in jessie/jessie-backports

[Bálint Réczey]

Control: notfound -1 16.1+dfsg1-1~bpo8+1


2016-05-31 3:34 GMT+02:00 Jesse Rhodes :
> Package: kodi
> Version: 16.1+dfsg1-1~bpo8+1
> Severity: important
>
> Dear Maintainer,
>
> When installing kodi from jessie-backports on a my media player running
> jessie, I noticed that kodi-data depends on the 'fonts-roboto-hinted'
> package, which only exists in sid and stretch at present.
>
> Thus the current kodi in jessie-backports is not installable.
>
> I self-backported fonts-roboto and installing that resolved the problem,
> so my suggestion is that fonts-roboto should be maintained as a backport
> as well.
>
> Please let me know if you need anything else,

Thank you for reporting the issue. This should be fixed by
16.1+dfsg1-1~bpo8+2 I have uploaded.

Please don't open bugs affecting package versions in jessie-backports,
use the backports mailing list for reporting such issues:
https://backports.debian.org/Instructions/#index6h2

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_16.0+dfsg1-1_source.changes ACCEPTED into unstable

[Bálint Réczey]

Hi Tobias,

I have updated kodi (to 16.x) and kodiplatform in jessie-backports and
I plan updating
the PVR addons I usually upload, too.

Do you plan updating the VNSI and hts addons?

Cheers,
Balint

2016-03-03 15:52 GMT+01:00 Bálint Réczey <bal...@balintreczey.hu>:
> Hi Tobias,
>
> 2016-03-03 0:06 GMT+01:00 Tobias Grimm <tobias.gr...@e-tobi.net>:
>> I've updated kodi-pvr-vnsi-vdr and kodi-pvr-hts to build with Kodi 16 and
>> p8-platform. kodi-pvr-vnsi-vdr seems to work fine.
> I have updated all the other PVR addons in git and uploaded kodiplatform
> to unstable. Please go ahead with the uploads.
>
>>
>> In both cases I've used upstreams 'Jarvis' branch for a new upstream
>> version, which does not yet contain p8 support, so I had to update the
>> patch one more time.
> I did the same to all the other addons, cherry-picking upstream patches.
>
> Cheers,
> Balint
>
>>
>> Tobias
>>
>> On 02.03.2016 03:48, Tobias Grimm wrote:
>>
>>> Hi Balint!
>>>
>>> Makes sense. I'll test the vnsi addon with the new version of kodiplatform
>>> today and update the hts addon as well.
>>>
>>> bye,
>>>
>>> Tobias
>>>
>>> On 01.03.2016 21:31, Bálint Réczey wrote:
>>>
>>>> Hi Tobias,
>>>>
>>>> I have uploaded kodiplatform to experimental.
>>>> I plan uploading it to unstable when all the PVR addons are ready in git
>>>> and then we can upload the addons next day.
>>>> I'm thinking about blocking the migration of kodi to not break testing's
>>>> addons while preparing the the updates in unstable.
>>>> What do you think?
>>>>
>>>> Cheers,
>>>> Balint
>>>>
>>>> 2016-02-26 23:38 GMT+01:00 Tobias Grimm <tobias.gr...@e-tobi.net>:
>>>>> Ok!
>>>>>
>>>>> On 26.02.2016 23:19, Bálint Réczey wrote:
>>>>>
>>>>>> Hi Tobias,
>>>>>>
>>>>>> 2016-02-26 23:09 GMT+01:00 Tobias Grimm <tobias.gr...@e-tobi.net>:
>>>>>>> Hello Balint!
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> I think, I'm going to update and test the vnsi/hts addons over the 
>>>>>>> weekend.
>>>>>> Great!
>>>>>>
>>>>>> I plan updating kodiplatform to use p8-platform and schedule
>>>>>> libcec-platform for removal.
>>>>>> Please make the upload when kodiplatform is updated to migrate to
>>>>>> p8-platform with
>>>>>> every 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
>>>
>>
>>
>>
>> ___
>> pkg-multimedia-maintainers mailing list
>> pkg-multimedia-maintainers@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

___
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#825078: Audio over HDMI not working

[Bálint Réczey]

Control: notfound -1 16.1+dfsg1-1

Hi,

2016-05-30 10:15 GMT+02:00 Erik de Castro Lopo <er...@mega-nerd.com>:
> Bálint Réczey wrote:
>
>> Would you like to share some info about the HW?
>
> Its just a standard Intel NUC with a Core i5 CPU and 16Gig RAM.

As you would probably guess correctly this is not enough information
to give any meaningful help. There are many related issues and some of
them have been resolved by fixing the kernel/upgrading ALSA:
https://www.google.hu/search?q=Intel+NUC+hdmi+sound+linux

I assume when you upgraded kodi you also upgraded other packages
and one of them broke HDMI sound.

I'm closing this bug for now since there is not enough information for
triaging, but feel free to reopen it if you would like to try finding the proper
package to fix.

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#825078: Audio over HDMI not working

[Bálint Réczey]

2016-05-29 23:03 GMT+02:00 Erik de Castro Lopo <er...@mega-nerd.com>:
> Bálint Réczey wrote:
>
>> Have you checked the suggestions listed here?:
>> http://kodi.wiki/view/PulseAudio
>
> Yes, I did. The problem was not at the PusleAudio level, because ALSA
> did not find the HDMI audio device either.

This sounds like an ALSA/PulseAudio/kernel problem rather than a Kodi one.

Can't do too much when the audio device is not found.

Would you like to share some info about the HW?

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#809488: kodi does not suspend anymore

[Bálint Réczey]

Control: notfound -1 15.2+dfsg1-1

Hi Johannes,

2015-12-31 16:35 GMT+01:00 Johannes Schauer :
> Hi,
>
> Quoting Johannes Schauer (2015-12-31 10:29:22)
>> I used to run Debian Jessie with Mate as a DM with Kodi from backports.
>> With that setup Kodi used to suspend just fine.
>>
>> Now I updated my base system to Squeeze and Kodi doesn't automatically
>> suspend anymore.
>>
>> Maybe connected: the "power" menu at the lower left of the home screen
>> now only shows the options "Exit" and "Inhibit idle shutdown". Before
>> the upgrade I had more options there.
>>
>> Additionally, even when I try to use the Mate automatic suspend on idle
>> options in the power menu, my system will not suspend while Kodi is
>> still running.
>>
>> How can I make my system suspend automatically again with Kodi running
>> in the foreground?
>
> I have no clue about polkit but after searching in the internet it seems that
> doing the following fixes this problem:
>
> $ cat << END | sudo tee 
> /var/lib/polkit-1/localauthority/50-local.d/custom-actions.pkla
> [Actions for kodi user]
> Identity=unix-user:kodi
> Action=org.freedesktop.login1.*;org.freedesktop.udisks2.*
> ResultAny=yes
> ResultInactive=no
> ResultActive=yes
> END
>
> Maybe this helps!
>
> In the worst case I now have documented a solution/workaround for others who
> might also stumble over this problem :)

Thank you for collecting the info here.
It can also be found on Kodi's wiki:
http://kodi.wiki/view/HOW-TO:Suspend_and_wake_in_Ubuntu

I'm closing the bug since there is documentation available for
enabling suspend when it does not work out of the box.

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#825078: Audio over HDMI not working

[Bálint Réczey]

Control: tags -1 moreinfo

Hi Erik,

2016-05-23 14:17 GMT+02:00 Erik de Castro Lopo :
> Source: kodi
> Version: 16.1+dfsg1-1
> Severity: normal
>
> After upgrading from kodi-15 to kodi-16, audio over HDMI stopped working
> on my dedicated kodi box.
>
> I spent a *lot* of time debugging this and in the end installed a kodi
> specific linux distro (http://wiki.libreelec.tv/) and everything works.

Have you checked the suggestions listed here?:
http://kodi.wiki/view/PulseAudio

There can be many configuration combinations, thus knowing more
about your setup/audio stream could help in resolving the issue.

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#825760: kodi: Crash on startup when connecting to CEC adapter

[Bálint Réczey]

Hi Torsten,

2016-05-29 21:17 GMT+02:00 Torsten Crass :
> OK,
>
> maybe I was a little dumb... The crash symptoms I described in my initial
> report resulted from an attempt to reproduce the problem by remotely calling
> kodi through an ssh connection. I don't know how cec actually interacts with
> an application, but maybe it just didn't feel comfortable with the UI
> running on a different physical machine.
>
> Anyway, when firing up kodi locally on the actual HTPC, the crash on launch
> is caused by an
>
> 21:06:38 T:140259291035840   ERROR: SQL: SQL error or missing database
> Query: SELECT idVersion FROM
> version
>
> So... should I vote for closing this bug and open a new one, or shall we
> proceed under #825760?

I have just uploaded kodi 16.1+dfsg1-1~bpo8+1 to jessie-backports which
is built with latest libcec thus fixes the crash due to the ABI breakage and
probably other bugs.

Please don't open bugs affecting package versions in jessie-backports,
use the backports mailing list for reporting such issues:
https://backports.debian.org/Instructions/#index6h2

OTOH if you can reproduce an issue with packages from testing/unstable only,
please open a bug report in the BTS like this one.

Also note that the packages from deb-multimedia can interfere with packages
from Debian, thus systems having those installed are not supported here.

The kodi-pvr-mythtv package will be available from jessie-backports in
the next weeks.

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#825768: libavcodec-ffmpeg56 : Depends: libx265-59 (>= 1.7) but it is not installable [home.experiatis.com]

[Bálint Réczey]

Dear Jaoued,

2016-05-29 19:02 GMT+02:00 Jaoued ZAHRAOUI :
> Package: libavcodec-ffmpeg56
> Version: 2.8.6-1~bpo8+1
> Severity: important
>
> Dear Maintainer,
>
> impossible to install this package due to dependencie libx265-59 missing.
> by the way, libx265-79 is avalaible.

Please report bugs that you found in the jessie-backports packages to the
backports mailing list and _not_ to the Debian BTS:
https://backports.debian.org/Instructions/#index6h2

FFmpeg 3.x just been accepted to jessie-backports and I have already
uploaded Kodi 16.1 which package most probably pulled the uninstallable
libavcodec for you.

Everything will install properly when the latest kodi package gets accepted.

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#774038: xbmc: When going fullscreen watching through xbmc-pvr-tvheadend-hts makes video stays black

[Bálint Réczey]

Control: notfound -1 14.0+dfsg1-1
Control: fixed -1 14.0+dfsg1-1

Hi Bernhard,

This has been fixed in Kodi AFAIK I just forgot closing the 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#823206: gb: armhf kodi_16.1+dfsg1-1

[Bálint Réczey]

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

Hi,

Build of kodi failed on buildd, but I have successfully rebuilt it
on debomatic from the same source:
http://debomatic-armhf.debian.net/distribution#unstable/kodi/16.1+dfsg1-1/buildlog

Please trigger a rebuild to have official builds for the package.

 gb kodi_16.1+dfsg1-1 . armhf

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: kodi-pvr-hdhomerun_1.0.4+git20151120-1_amd64.changes REJECTED

[Bálint Réczey]

Hi Thorsten,

I'm sorry, I completely missed your previous email about the package.
I'll fix the issue in next upload.

Thanks,
Balint

2016-04-14 4:00 GMT+02:00 Thorsten Alteholz :
>
> Hi Balint,
>
> as there seems to be no progress, I am rejecting the package for now.
>
> Please reupload after the carriage-return-issue in the path has been resolved.
>
> Thanks!
>  Thorsten
>
> ===
>
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
>

___
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: gcc 5 internal error, building supercollider 3.7.0

[Bálint Réczey]

Hi Dan,

2016-03-17 10:13 GMT+01:00 Dan S :
> Hi all,
>
> I'm importing the new version of SuperCollider (3.7.0).
> http://anonscm.debian.org/cgit/pkg-multimedia/supercollider.git/log/
>
> However, current status on my debian box is that GCC 5.3.1 dies on an
> internal error while trying to compile supernova.
>
> g++: internal compiler error: Killed (program cc1plus)
>
> I can submit a compiler bug report, yes, but is there any advice about
> how to progress with the supercollider packages? I haven't been able
> to find any documentation about, e.g., setting the rules to ensure
> build with GCC 4 (which I think will work fine).
I suggest going for GCC 6 instead using a versioned dependency an uploading
supercollider to experimental.
Another option is changing the code to not hit ICE, but gcc-5 is also
updated frequently
and if there is a patch available the GCC maintainer would probably
apply it in a few weeks.

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: kodi: Jasper removal

[Bálint Réczey]

Control: tags -1 confirmed pending upstream

Hi Moritz,

2016-03-14 20:19 GMT+01:00  :
> Source: kodi
> Severity: important
> User: j...@debian.org
> Usertags: jasper-rm
>
> Hi, jasper will be removed from Debian for the stretch release (and
> following that, the archive in general).
>
> It's been unmaintained for nearly a decade, please als see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812630
>
> Your package uses jasper, so please either remove the JPEG2000
> functionality or move to a supported implementation (e.g. openjpeg or
> ffmpeg).
>
> A removal tracker has been setup by the release team at
> https://release.debian.org/transitions/html/jasper-rm.html
>
> This bug will be bumped to release-critical status in a few weeks.
Kodi 17 wil not use jasper [1] and is expected to be release before
Stretch's freeze.
I plan fixing this bug with the 17.0 upstream release.

Cheers,
Balint

[1] https://github.com/xbmc/xbmc/commit/00724eb109a702f0098089d849f7c02ea173a4a9

___
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_16.0+dfsg1-1_source.changes ACCEPTED into unstable

[Bálint Réczey]

Hi Tobias,

2016-03-03 0:06 GMT+01:00 Tobias Grimm <tobias.gr...@e-tobi.net>:
> I've updated kodi-pvr-vnsi-vdr and kodi-pvr-hts to build with Kodi 16 and
> p8-platform. kodi-pvr-vnsi-vdr seems to work fine.
I have updated all the other PVR addons in git and uploaded kodiplatform
to unstable. Please go ahead with the uploads.

>
> In both cases I've used upstreams 'Jarvis' branch for a new upstream
> version, which does not yet contain p8 support, so I had to update the
> patch one more time.
I did the same to all the other addons, cherry-picking upstream patches.

Cheers,
Balint

>
> Tobias
>
> On 02.03.2016 03:48, Tobias Grimm wrote:
>
>> Hi Balint!
>>
>> Makes sense. I'll test the vnsi addon with the new version of kodiplatform
>> today and update the hts addon as well.
>>
>> bye,
>>
>> Tobias
>>
>> On 01.03.2016 21:31, Bálint Réczey wrote:
>>
>>> Hi Tobias,
>>>
>>> I have uploaded kodiplatform to experimental.
>>> I plan uploading it to unstable when all the PVR addons are ready in git
>>> and then we can upload the addons next day.
>>> I'm thinking about blocking the migration of kodi to not break testing's
>>> addons while preparing the the updates in unstable.
>>> What do you think?
>>>
>>> Cheers,
>>> Balint
>>>
>>> 2016-02-26 23:38 GMT+01:00 Tobias Grimm <tobias.gr...@e-tobi.net>:
>>>> Ok!
>>>>
>>>> On 26.02.2016 23:19, Bálint Réczey wrote:
>>>>
>>>>> Hi Tobias,
>>>>>
>>>>> 2016-02-26 23:09 GMT+01:00 Tobias Grimm <tobias.gr...@e-tobi.net>:
>>>>>> Hello Balint!
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> I think, I'm going to update and test the vnsi/hts addons over the 
>>>>>> weekend.
>>>>> Great!
>>>>>
>>>>> I plan updating kodiplatform to use p8-platform and schedule
>>>>> libcec-platform for removal.
>>>>> Please make the upload when kodiplatform is updated to migrate to
>>>>> p8-platform with
>>>>> every 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
>>
>
>
>
> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

___
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_16.0+dfsg1-1_source.changes ACCEPTED into unstable

[Bálint Réczey]

Hi Tobias,

I have uploaded kodiplatform to experimental.
I plan uploading it to unstable when all the PVR addons are ready in git
and then we can upload the addons next day.
I'm thinking about blocking the migration of kodi to not break testing's
addons while preparing the the updates in unstable.
What do you think?

Cheers,
Balint

2016-02-26 23:38 GMT+01:00 Tobias Grimm <tobias.gr...@e-tobi.net>:
> Ok!
>
> On 26.02.2016 23:19, Bálint Réczey wrote:
>
>> Hi Tobias,
>>
>> 2016-02-26 23:09 GMT+01:00 Tobias Grimm <tobias.gr...@e-tobi.net>:
>>> Hello Balint!
>>>
>>> Thanks!
>>>
>>> I think, I'm going to update and test the vnsi/hts addons over the weekend.
>> Great!
>>
>> I plan updating kodiplatform to use p8-platform and schedule
>> libcec-platform for removal.
>> Please make the upload when kodiplatform is updated to migrate to
>> p8-platform with
>> every 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

Re: kodi_16.0+dfsg1-1_source.changes ACCEPTED into unstable

[Bálint Réczey]

Hi Tobias,

2016-02-26 23:09 GMT+01:00 Tobias Grimm :
> Hello Balint!
>
> Thanks!
>
> I think, I'm going to update and test the vnsi/hts addons over the weekend.
Great!

I plan updating kodiplatform to use p8-platform and schedule
libcec-platform for removal.
Please make the upload when kodiplatform is updated to migrate to
p8-platform with
every 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#813497: closed by Bálint Réczey <bal...@balintreczey.hu> (reply to bal...@balintreczey.hu) (Re: Bug#813497: kodi: Segfault on Startup)

[Bálint Réczey]

Control: fixed -1 15.2+dfsg1-3

2016-02-11 1:53 GMT+01:00 Alessio Treglia :
> Please close again this bug by specifying the version it is no longer
> reproducible.
Most probably it was current version.
Please change it if that's not the case.

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#813497: kodi: Segfault on Startup

[Bálint Réczey]

Hi Stephen,

2016-02-02 19:48 GMT+01:00 Stephen Allen :
> More information and potentially solved:
>
> Since this issue only started this morning after using Kodi last
> evening, and subsequent 'apt upgrade' I think it was the
> libbasicusageenvironment1 update and removal of
> libbasicusageenvironment0. I re-installed the latter, logged out and
> motion video works as before. They seem to be happy side by side too.
Kodi does not depend on libbasicusageenvironment{0,1} thus I think it was
something else which is gone.

There are a few errors but no stack trace in the logs thus I can't
tell what went wrong:

...
### STACK TRACE #
gdb not installed, can't get stack trace.
...
09:19:14 T:140537751083520   ERROR: CWinSystemX11::XErrorHandler:
BadAtom (invalid Atom parameter), type:0, serial:43, error_code:5,
request_code:18 minor_code:0
09:19:15 T:140537751083520  NOTICE: Using visual 0x2da
09:19:15 T:140537751083520  NOTICE: GL_VENDOR = X.Org
--
09:19:15 T:140537751083520   ERROR: Unable to load libcec.so.3,
reason: libcec.so.3: cannot open shared object file: No such file or
directory
09:19:15 T:140537751083520   ERROR: Initialise - failed to initialise bus cec
09:19:15 T:140536914220800  NOTICE: Thread PeripBusUSBUdev start, auto
delete: false
09:19:15 T:140537751083520  NOTICE: Running database version Addons19
--
09:19:15 T:140537751083520   ERROR: Couldn't load font name:
font10(roboto-regular.ttf), trying to substitute arial.ttf
09:19:15 T:140537751083520   ERROR: Couldn't load font name:
font12(roboto-regular.ttf), trying to substitute arial.ttf
...
09:19:15 T:140537751083520 WARNING: JSONRPC: Could not parse type
"PVR.Details.Channel"
09:19:15 T:140537751083520 WARNING: JSONRPC: Could not parse type
"PVR.Details.ChannelGroup.Extended"
--
09:19:15 T:140537751083520   ERROR: ExecuteAsync - Not executing
non-existing script
/home/stephen/.kodi/addons/service.xbmc.icanuckwallpapers/service.py
09:19:15 T:140536278173440  NOTICE: Thread LanguageInvoker start, auto
delete: false
09:19:15 T:140537751083520  NOTICE: Previous line repeats 20 times.
--
09:19:18 T:140535348061952   ERROR:
/home/stephen/.kodi/addons/service.dbus.notify/xbmcnotify.py:23:
PyGIWarning: Notify was imported without specifying a version first.
Use gi.require_version('Notify', '0.7') before import to ensure that
the right version gets loaded.
  from gi.repository import Notify
09:19:18 T:140534031030016  NOTICE: Thread LanguageInvoker start, auto
delete: false

I'll check the font errors, they seem to be new and related to packaging.

I'm closing the bug since it seems to be unreproducible as I
understand or not related to Kodi.
Please re-open it if it appears again and please attach a crash log
with gdb and debug symbols for kodi installed.

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

[Bálint Réczey]

2016-01-23 4:13 GMT+01:00 Jonas Smedegaard :
> Quoting Balint Reczey (2016-01-22 22:29:30)
>> On Fri, 22 Jan 2016 10:21:59 + (UTC) Gianfranco Costamagna
>>  wrote:
>> ...
>>> - 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.
>
> That section of policy talks about _dependencies_ whereas the change
> done above is a _build-dependency_.
>
> It is a common pattern in Debian to provide a virtual library
> development package.  Purpose of the section above is to ensure
> deterministic install (non-random install) but that is ensured by the
> maintainer of the library package only having a single package available
> in any suite at a time providing the virtual package.
I assumed this section covers build-dependencies to help determinism,
in case there happens to be two packages providing the virtual package.

There is a long thread on debian-devel starting here:
https://lists.debian.org/debian-devel/2016/01/msg00133.html
referencing the following transition bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650601

My takeaway was the expected build dependency is the following:
...
 libpng-dev,
...
Would not it be OK?

Gianfranco, please cancel your NMU, I'll upload an updated kodi package
right after libpng is updated in unstable adapting to the libpng binary
package structure whatever it ends to be.

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: Kodi out from debian stable

[Bálint Réczey]

Hi Alessandro,

2016-01-10 22:15 GMT+01:00 Alessandro :
> Dear debian-multimedia and pkg-multimedia-maintainers,
>
> I write this e-mail for asking you because Kodi and related packages present
> in the main repo of debian stable (Jessie) until 2 days ago, today they are
> not present. They are partly present only in backports.
>
> Excuse for my English and thak you.
AFAIK kodi wasn't part of stable (Jessie). Maybe you saw it in a
repository which
is not maintained as part of the Debian project?

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#810011: nmu: Please try building kodi-pvr-hts again

[Bálint Réczey]

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

Hi,

I have updated libcec-platform which is a transitive build-dependency
of kodi-pvr-hts and now kodi-pvr-hts builds fine on mipsel.

Please trigger a rebuild to have official builds for the package.

 gb kodi-pvr-hts . mips mipsel mips64el

Thanks,
Balint

PS: Is there any automatism to try building packages with updated
transitive build-dependencies?

___
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#808750: Package does not have a description

[Bálint Réczey]

Control: tags -1 moreinfo

Hi Max,

2015-12-22 14:04 GMT+01:00 Max Kellermann :
> Package: kodi-pvr-njoy
> Version: 1.10.7+git20150717-1
>
> "NJOY PVR Addon for Kodi" is the same as the package name, but I still
> don't know what it is.
Do you have a better suggestion?

Cheers,
Baling

___
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-pvr-hts_2.1.18-1_amd64.changes is NEW

[Bálint Réczey]

Hi Thorsten,

2015-11-25 22:27 GMT+01:00 Thorsten Alteholz <alteh...@debian.org>:
>
>
> On Tue, 24 Nov 2015, Bálint Réczey wrote:
>>
>> OK, I always handled ITP-s as a must but in seems to be just a strong
>> recommendation to have one.
>
>
> If there is any kind of dispute, the one who filed an ITP will win.
> The Debian Developer's Reference 5.1 [1] explains why ITPs are useful, but a
> missing one is not a reason for a REJECT.
Thank you for the clarification. It will save some time for me!
I'll still file ITP-s for bigger packages. :-)

Cheers,
Balint

> [1]https://www.debian.org/doc/manuals/developers-reference/pkgs.html#newpackage

___
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-pvr-hts_2.1.18-1_amd64.changes is NEW

[Bálint Réczey]

Hi Tobias,

OK, I always handled ITP-s as a must but in seems to be just a strong
recommendation to have one.
If FTP Masters are happy happy with that I'll skip filing ITP-s for
the rest of the PVR addons.

Cheers,
Balint

2015-11-24 16:38 GMT+01:00 Tobias Grimm <tobias.gr...@e-tobi.net>:
> Hello Bálint,
>
> I'm not sure if an ITP makes sense here - it's an replacement for the old
> xbmc-pvr-addons package which was split into multiple packages by upstream.
> So it's not exactly something completely new.
> (And I didn't create an ITP for kodi-pvr-vdr-vnsi either.)
>
> BR,
>
> Tobias
>
>
> Am 24.11.2015 um 15:37 schrieb Bálint Réczey:
>
>> Hi Tobias,
>>
>> I think ITP will be missing from the changelog.
>>
>> Cheers,
>> Balint
>>
>> 2015-11-23 23:48 GMT+01:00 Debian FTP Masters
>> <ftpmas...@ftp-master.debian.org>:
>>>
>>> binary:kodi-pvr-hts is NEW.
>>> source:kodi-pvr-hts is NEW.
>>>
>>> Your package has been put into the NEW queue, which requires manual
>>> action
>>> from the ftpteam to process. The upload was otherwise valid (it had a
>>> good
>>> OpenPGP signature and file hashes are valid), so please be patient.
>>>
>>> Packages are routinely processed through to the archive, and do feel
>>> free to browse the NEW queue[1].
>>>
>>> If there is an issue with the upload, you will receive an email from a
>>> member of the ftpteam.
>>>
>>> If you have any questions, you may reply to this email.
>>>
>>> [1]: https://ftp-master.debian.org/new.html
>>>
>>> ___
>>> pkg-multimedia-maintainers mailing list
>>> pkg-multimedia-maintainers@lists.alioth.debian.org
>>>
>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
>>
>>
>> ___
>> pkg-multimedia-maintainers mailing list
>> pkg-multimedia-maintainers@lists.alioth.debian.org
>>
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
>>
>

___
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-pvr-hts_2.1.18-1_amd64.changes is NEW

[Bálint Réczey]

Hi Tobias,

I think ITP will be missing from the changelog.

Cheers,
Balint

2015-11-23 23:48 GMT+01:00 Debian FTP Masters :
> binary:kodi-pvr-hts is NEW.
> source:kodi-pvr-hts is NEW.
>
> Your package has been put into the NEW queue, which requires manual action
> from the ftpteam to process. The upload was otherwise valid (it had a good
> OpenPGP signature and file hashes are valid), so please be patient.
>
> Packages are routinely processed through to the archive, and do feel
> free to browse the NEW queue[1].
>
> If there is an issue with the upload, you will receive an email from a
> member of the ftpteam.
>
> If you have any questions, you may reply to this email.
>
> [1]: https://ftp-master.debian.org/new.html
>
> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

___
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: [SCM] kodi-pvr-hts packaging branch, master, created. 42c0d9c951bd3e376a417754fee5dd05763fcd89

[Bálint Réczey]

Hi Tobias,

Do you plan uploading the package to unstable?
Since Kodi seems to be working properly I'm thinking about packaging
the addons replacing the ones provided by xbmc-pvr-addons.

Cheers,
Balint


2015-10-03 0:27 GMT+02:00  :
> The branch, master has been created
> at  42c0d9c951bd3e376a417754fee5dd05763fcd89 (commit)
>
> - Shortlog 
> commit 42c0d9c951bd3e376a417754fee5dd05763fcd89
> Author: Tobias Grimm 
> Date:   Sat Oct 3 00:19:57 2015 +0200
>
> Added homepage and vcs fields
>
...
> kodi-pvr-hts packaging

___
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#803831: kodi: FTBFS with FFmpeg 2.9

[Bálint Réczey]

Control: tags -1 confirmed pending
Control: forwarded -1
https://github.com/xbmc/xbmc/pull/8112#issuecomment-154432878

Hi Andreas,

2015-11-03 1:07 GMT+04:00 Andreas Cadhalpun :
> Package: kodi
> Version: 15.2~rc3+dfsg1-1
> Severity: important
> Tags: patch
> User: pkg-multimedia-maintainers@lists.alioth.debian.org
> Usertags: ffmpeg2.9
>
> Dear Maintainer,
>
> your package fails to build with the upcoming ffmpeg 2.9.
> This bug will become release-critical at some point when the
> ffmpeg2.9 transition gets closer.
>
> Attached is a patch replacing the deprecated functionality.
> It also works with ffmpeg 2.8.
> Please apply this patch and forward it upstream, if necessary.
>
> These changes have little regression potential.
Thanks for the patch. I will update kodi soon.

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