[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#916333: ITP: dav1d -- fast and small AV1 video stream decoder



Hi Sebastian!

At the moment, kodi 18.7.1 is not blocked. Also, if there is no package the dav1d support is disabled in 19 either.
However, I referred to the whole situation: the maintainers come to bring new packages and improve the existing ones,
not waiting months & years without a feedback.

FYI, kodi 19 benefits much from enabling dav1d on streams like Netflix, so I build Kodi for my testing repo with dav1d packaged.
Same applies to shairplay & libudfread (I ITP'ed and packaged these under Mattia's mentorship and even persuaded the upstream
lead developer Jean-Baptiste Kempf to make a new tag for libudfread after three years since the packaged tag was released)

Jean-Baptiste expressed big wish to have dav1d and libudfread in Debian during our conversation related to udfread tagging,
so I feel obliged to do everything I can to make it happen.
-- 
Vasyl Gello
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.gello@gmail.com

Skype: vasek.gello
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

July 2, 2020 8:41:38 AM UTC, Sebastian Ramacher <sramacher@debian.org> написав(-ла):
Hi Vasyl

On 2020-07-02 08:20:11 +0000, Vasyl Gello wrote:
Hi Jonas!

I also can volunteer uploading 0.7.1 as part of my kodi work.

How is dav1d blocking kodi work? Once dav1d is in the archive in ffmpeg
is uploaded with dav1d support enabled, won't kodi also automatically
have dav1d support? If they kodi is using it directly, is there no
option to disable it until it is available?

Cheers

Also, is it a good idea to reach Joerg Jaspert directly and kindly ask for review?

Why am I asking this: I have two pending packages (libudfread & shairplay).
At the same time, I am preparing full Kodi binary addon archive (84 source packages).

I am carefully investigating copyrights and perform builds and tests in the publuc unofficial repo
(see relevant d-multimedia discussiob). However, I don't want to wait YEARS after Kodi reaches
release. Instead, I am using my sparevtime to keep packaging ready as development of Kodi upstream
progresses.

With such enormous waiting times and no understandingbof how to solve it gracefully, the whole project
might become a waste of time and I obviously try avoiding it.
-- 
Vasyl Gello
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.gello@gmail.com

Skype: vasek.gello
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

July 2, 2020 8:11:03 AM UTC, Jonas Smedegaard <jonas@jones.dk> написав(-ла):
Quoting Dylan Aïssi (2020-07-02 09:29:51)
On Tue, 30 Jun 2020 03:38:20 +0000 Vasyl Gello <vasek.gello@gmail.com> wrote:
There is a new upstream release 0.7.1 for a week or so.
Can you please package it?

dav1d is in the NEW queue since 1,5 years. It was rejected after 1
year in the NEW queue and I still don't have news about the last
attempt. I am losing motivation for this package, I will probably
convert this ITP to RFP...

I guess the rejection is what you quoted in
https://bugs.debian.org/916333#25

Thanks, btw, for quoting like that to make conversations with ftpmasters
more transparent. Much appreciated!

Did you try re-upload since the rejection? If not, why not?

If that was the only reason given by ftpmasters for rejecting, then I
would suggest to simply a) make sure that the licensing/patenting
situation as you understand it is explicitly laid out in
debian/copyright file, and then b) re-release the package.

When re-uploaded, I can suggest to try nudge ftpmasters by logging into
irc channel #debian-ftp and kindly request a review of the package.

If you haven't given up yet, then would you be interesting in
maintaining the package collaboratively? I can offer to help if you
would be interested in doing so e.g. in the Multimedia team.

If you have given up already, then I can offer to take over.

Kind regards,

- Jonas

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

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


Attachment: signature.asc
Description: PGP signature


Reply to: