From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Multimedia Libs
Date: Sat, 23 May 2020 12:08:18 +0200 [thread overview]
Message-ID: <3d8fcc0d-aa2e-6603-dbb5-a30cc793429b@ipfire.org> (raw)
In-Reply-To: <ac3f57d0-b44e-52ff-7de8-4a6a7ecf3700@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Hi,
On 25.03.2020 21:55, Matthias Fischer wrote:
> On 27.02.2020 12:27, Michael Tremer wrote:
>> [...could you look for some multimedia libs...?]>
>> ...
Something new has come up - "They just came my way..." ;-)
And a few questions.
While working on updates for:
krb5 1.15.2 => 1.18.1
tcl 8.6.6 => 8.6.10
ffmpeg 4.2.2 => 4.2.3
1. I found 'minidlna 1.1.3' - dated 2014. It depends on ffmpeg, flac,
libexif, libid3tag and libogg. Arne already bumped the PAK_VER.
But I found a newer version of 'minidlna' in cache (1.2.1 dated 2017).
Is there a reason why we are using the older version?
2. Similar to 'nettle 3.6', I found a lot of dependencies (sigh). Should
I still upload the updates above, so we can take a look at them or
should I wait? I don't want to make unnecessary noise.
3. Should I try to update 'minidlna'?
Best,
Matthias
next prev parent reply other threads:[~2020-05-23 10:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5C7D0AAC-730A-40BA-B398-8AED49A4867D@ipfire.org>
2020-03-25 20:55 ` Matthias Fischer
2020-03-25 21:11 ` Stephan Mending
2020-03-26 7:24 ` Matthias Fischer
2020-03-26 9:10 ` Michael Tremer
2020-03-26 9:30 ` Matthias Fischer
2020-03-28 4:54 ` Matthias Fischer
2020-03-28 7:41 ` Michael Tremer
2020-03-26 9:47 ` Stephan Mending
2020-03-30 5:08 ` Matthias Fischer
2020-03-30 5:17 ` Matthias Fischer
2020-03-30 9:10 ` Matthias Fischer
2020-03-30 9:31 ` Michael Tremer
2020-04-02 17:07 ` Matthias Fischer
2020-04-03 10:22 ` Michael Tremer
2020-05-23 10:08 ` Matthias Fischer [this message]
2020-05-25 9:29 ` Michael Tremer
2020-05-25 11:05 ` Matthias Fischer
2020-05-26 10:15 ` Michael Tremer
2020-05-26 17:13 ` Matthias Fischer
2020-05-28 11:54 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d8fcc0d-aa2e-6603-dbb5-a30cc793429b@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox