ffmpeg is required to be the tainted version and I suspect that this not it.
This could all be coincidental but it is a bit suspicious.
I have "tainted" selected in the media list.
MCC lists no tainted version of ffmpeg in the repository list. It used to. Has there been some policy change?
On Sun, 12 Jul 2020 18:09:42 +1000, faeychild wrote:07:57
ffmpeg is required to be the tainted version and I suspect that this not it.
This could all be coincidental but it is a bit suspicious.
I have "tainted" selected in the media list.
MCC lists no tainted version of ffmpeg in the repository list. It used to. >> Has there been some policy change?
You might post on the dev mail list that maybe someone needs to do
a 4.1.6 tainted update/release.
$ grep ^ffmpeg- *_*-0007.0.x86_64.idx | grep -vE "32_|java" core_release-0007.0.x86_64.idx:ffmpeg-4.1.3-1.mga7.x86_64.rpm 2M 02-Apr-2019
core_updates-0007.0.x86_64.idx:ffmpeg-4.1.4-1.mga7.x86_64.rpm 2M 11-Jul-201916:24
core_updates-0007.0.x86_64.idx:ffmpeg-4.1.5-1.mga7.x86_64.rpm 2M 15-Jan-202003:07
core_updates-0007.0.x86_64.idx:ffmpeg-4.1.6-1.mga7.x86_64.rpm 2M 07-Jul-202021:55
tainted_release-0007.0.x86_64.idx:ffmpeg-4.1.3-1.mga7.tainted.x86_64.rpm 2M02-Apr-2019 08:14
tainted_updates-0007.0.x86_64.idx:ffmpeg-4.1.4-1.mga7.tainted.x86_64.rpm 2M11-Jul-2019 16:19
tainted_updates-0007.0.x86_64.idx:ffmpeg-4.1.5-1.mga7.tainted.x86_64.rpm 2M15-Jan-2020 03:13
Tonight I am getting error from kdenlive about an unsupported codec
"Unsupported video codec: libx264"
Yesterday all was fine.
Today there was an update which included a new ffmpeg v 4.1.6.
Kdenlive uses MLT which probably uses ffmpeg for libx264
ffmpeg
ffmpeg version 4.1.6 Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 8.4.0 (Mageia 8.4.0-1.mga7)
configuration: --prefix=/usr --enable-shared --enable-pic --libdir=/usr/lib64 --shlibdir=/usr/lib64 --incdir=/usr/include --disable-stripping --enable-postproc --enable-gpl --enable-pthreads --enable-libtheora --enable-libvorbis --disable-encoder=vorbis --enable-libvpx --enable-runtime-cpudetect --enable-libaom --enable-libdc1394 --enable-librtmp --enable-libspeex
--enable-libfreetype --enable-libgsm --enable-libcelt --enable-libopus --enable-libopencv --enable-libopenjpeg --enable-libtwolame
--enable-libxavs --enable-frei0r --enable-libmodplug --enable-libass --enable-gnutls --enable-libcdio --enable-libpulse --enable-libv4l2 --enable-avresample --enable-opencl --enable-libmp3lame --enable-sndio --enable-libdav1d --disable-decoder=aac --disable-encoder=aac
libavutil 56. 22.100 / 56. 22.100
libavcodec 58. 35.100 / 58. 35.100
libavformat 58. 20.100 / 58. 20.100
libavdevice 58. 5.100 / 58. 5.100
libavfilter 7. 40.101 / 7. 40.101
libavresample 4. 0. 0 / 4. 0. 0
libswscale 5. 3.100 / 5. 3.100
libswresample 3. 3.100 / 3. 3.100
libpostproc 55. 3.100 / 55. 3.100
I see no mention of libx264 in the update version.
ffmpeg is required to be the tainted version and I suspect that this not
it.
This could all be coincidental but it is a bit suspicious.
I have "tainted" selected in the media list.
MCC lists no tainted version of ffmpeg in the repository list. It used to. Has there been some policy change?
regards
When the latest ffmpeg update was pushed, the tainted version was
mistakenly not sent with it. The situation should be corrected soon.
TJ
On 12/7/20 6:53 pm, Bit Twister wrote:
That would require a new career move, Bits. Spending a large part of
the night finding out just how to do that..
$ grep ^ffmpeg- *_*-0007.0.x86_64.idx | grep -vE "32_|java"PS that is an interesting command esp the second grep piped to java.
That lost me!! :-)
On 12/7/20 6:53 pm, Bit Twister wrote:
On Sun, 12 Jul 2020 18:09:42 +1000, faeychild wrote:
ffmpeg is required to be the tainted version and I suspect that this not it.
This could all be coincidental but it is a bit suspicious.
I have "tainted" selected in the media list.
MCC lists no tainted version of ffmpeg in the repository list. It used to. >>> Has there been some policy change?
You might post on the dev mail list that maybe someone needs to do
a 4.1.6 tainted update/release.
$ grep ^ffmpeg- *_*-0007.0.x86_64.idx | grep -vE "32_|java"
core_release-0007.0.x86_64.idx:ffmpeg-4.1.3-1.mga7.x86_64.rpm 2M 02-Apr-2019 07:57
core_updates-0007.0.x86_64.idx:ffmpeg-4.1.4-1.mga7.x86_64.rpm 2M 11-Jul-2019 16:24
core_updates-0007.0.x86_64.idx:ffmpeg-4.1.5-1.mga7.x86_64.rpm 2M 15-Jan-2020 03:07
core_updates-0007.0.x86_64.idx:ffmpeg-4.1.6-1.mga7.x86_64.rpm 2M 07-Jul-2020 21:55
tainted_release-0007.0.x86_64.idx:ffmpeg-4.1.3-1.mga7.tainted.x86_64.rpm 2M 02-Apr-2019 08:14
tainted_updates-0007.0.x86_64.idx:ffmpeg-4.1.4-1.mga7.tainted.x86_64.rpm 2M 11-Jul-2019 16:19
tainted_updates-0007.0.x86_64.idx:ffmpeg-4.1.5-1.mga7.tainted.x86_64.rpm 2M 15-Jan-2020 03:13
That would require a new career move, Bits. Spending a large part of
the night finding out just how to do that..
PS that is an interesting command esp the second grep piped to java.
That lost me!! :-)
Anyway, you know that cauldron is buggy. It is supposed to be buggy. If
it were not it would be called Mageia 8 not Mageia cauldron.
All Bit is
saying is to report that the tainted version is not included in the
current cauldron, presumable by error.
You can see the dev mailing list at
https://ml.mageia.org/l/arc/dev
I use my Mageia bugzilla id/pw for posting if not using Thunerbird.
My THunderbird email address book has dev@ml.mageia.org
On 12/7/20 10:56 pm, Bit Twister wrote:
You can see the dev mailing list at
https://ml.mageia.org/l/arc/dev
I use my Mageia bugzilla id/pw for posting if not using Thunerbird.
My THunderbird email address book has dev@ml.mageia.org
The page requires a login which I assume requires a registration procedure.
A superficial search didn't uncover a registering process.
I have yet to read the FAQ and docs.
Once the id has been created, wait about 10 minutes to ensure the new id
has
been synced to all of the Mageia systems, then use https://ml.mageia.org/l/home
to subscribe to the desired mailing lists.
On 12/7/20 10:56 pm, Bit Twister wrote:
You can see the dev mailing list at
https://ml.mageia.org/l/arc/dev
I use my Mageia bugzilla id/pw for posting if not using Thunerbird.
My THunderbird email address book has dev@ml.mageia.org
The page requires a login which I assume requires a registration procedure.
On 13/7/20 12:17 pm, David W. Hodgins wrote:
Once the id has been created, wait about 10 minutes to ensure the new id
has
been synced to all of the Mageia systems, then use
https://ml.mageia.org/l/home
to subscribe to the desired mailing lists.
AH less grievous than expected.
before I delve into how to post-
who to post too
etc
I wait a few days as TJ inferred.
It is kinda like Usenet. and the dev mail list is just a group like alt.os.linux.mageia. Instead of looking via Usenet, it is done vial Email.
Do go back and take a look at some of the messages/threads at
https://ml.mageia.org/l/arc/dev
to see if you really want the eamil traffic.
The dev maillist is usually for Developers helping otherdevelopers/Packagers.
I only post there when I want to know if they want a problem report
or a little time to work the problem.
I wait a few days as TJ inferred.
Yep, I saw that David had posted your problem to the sysadmain maillist
which should get the problem to someone's attention.
Tonight I am getting error from kdenlive about an unsupported codec
"Unsupported video codec: libx264"
Yesterday all was fine.
Today there was an update which included a new ffmpeg v 4.1.6.
Kdenlive uses MLT which probably uses ffmpeg for libx264
https://bugs.mageia.org/show_bug.cgi?id=26941
This also doesn't just affect the tainted version of FFmpeg by the looks
of it, I don't have tainted FFmpeg on my sytem. I noticed this problem
too over the past few days. I thought I did something wrong, because Kdenlive does screw up its configuration files occasionally for no good reason.
I believe that if your are encoding h264 video most of the "video" programs in Linux use "ffmpeg tainted" because it contains the codec.
And when kdenlive fell over with that complaint and it coincided with
the update of ffmpeg which was not the tainted version, the clues fell
into place.
But to be sure I can pull all the kdenlive config files and check it
out, but I am currently recording so it will have to wait
On 13/7/20 6:02 pm, Ar wrote:
I don't have an FFmpeg in the tainted showing in the package manager,
other codecs are normal and tainted versions. I don't recall if I was
using FFmpeg tainted version in the first place. It's difficult to
remember everything, and too much hassle to create a list.
I am not totally marooned though. I could switch to M6 if I need too. Fortunately it is not an emergency.
On Mon, 13 Jul 2020 03:08:58 -0400, faeychild
<faeychild@nomail.afraid.org> wrote:
I am not totally marooned though. I could switch to M6 if I need too.
Fortunately it is not an emergency.
The mistake has been fixed. The tainted update for ffmpeg is now on the princeton
mirror, so should be on the others soon, if not already present.
Regards, Dave Hodgins
On 14/7/20 9:29 am, David W. Hodgins wrote:
On Mon, 13 Jul 2020 03:08:58 -0400, faeychild
<faeychild@nomail.afraid.org> wrote:
I am not totally marooned though. I could switch to M6 if I need too.
Fortunately it is not an emergency.
The mistake has been fixed. The tainted update for ffmpeg is now on the
princeton
mirror, so should be on the others soon, if not already present.
Regards, Dave Hodgins
OK I checked princeton
2020-07-07 18:04 1.6M
It is definitely there - One week old.??
I checked my mirror aarnet. It still has version 4.1.5 tainted Which was removed from my system and replaced with untainted version 4.1.6
Well I'm baffledWhy are you baffled?
I'll wait until the updates flow through
It is definitely there - One week old.??
It was presumably created a week ago and transfered yest. via rsync,
which preserves mtime for the file. It has not been on princeton for a
week.
Why are you baffled?
I checked my mirror aarnet. It still has version 4.1.5 tainted Which was
removed from my system and replaced with untainted version 4.1.6
Well I'm baffled
I'll wait until the updates flow through
Or use princeton.
Baffled by a week old date that hadn't flowed through on my last update
The same thing happens with all packages that sit in qa testing for a
long period,
either do to difficulty in testing (learning how to test rarely used packages), or
just due to the qa team being overloaded.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 481 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 18:55:17 |
| Calls: | 9,542 |
| Calls today: | 2 |
| Files: | 13,653 |
| Messages: | 6,139,975 |