ffmpeg tainted

[faeychild]

I have ffmpeg untainted installed. To remove it also nukes clipgrab and
kdenlive. They can be reinstalled but it's annoying.

Is there another way?

Regards

[David W. Hodgins]

Post by faeychild
I have ffmpeg untainted installed. To remove it also nukes clipgrab and
kdenlive. They can be reinstalled but it's annoying.

Why? It's only around 10MB?

"rpm -e --nodeps ffmpeg" will uninstall it without uninstalling the packages
that require it, but don't expect them to work without it. kdenlive and clipgrab
use it.

Note. If you install the tainted version, it will uninstall the core version
as part of the process of updating from the core version to the tainted
version. The tainted version also can be used by kdenlive and clipgrab.

There is no need to uninstall the core version to install the tainted version.

Regards, Dave Hodgins

[faeychild]

On Fri, 08 Mar 2024 18:50:46 -0500, faeychild

Post by faeychild
I have ffmpeg untainted installed. To remove it also nukes clipgrab and
kdenlive. They can be reinstalled but it's annoying.

Why? It's only around 10MB?
"rpm -e --nodeps ffmpeg" will uninstall it without uninstalling the packages
that require it, but don't expect them to work without it. kdenlive and clipgrab
use it.
Note. If you install the tainted version, it will uninstall the core version
as part of the process of updating from  the core version to the tainted
version. The tainted version also can be used by kdenlive and clipgrab.
There is no need to uninstall the core version to install the tainted version.

Does it overwrite the untainted? - having the same name and all


mga9 kdenlive just complained about audio codec acc I assume may have
something to do with ffmpeg tainted being absent



regards

[jim whitby]

Post by faeychild

On Fri, 08 Mar 2024 18:50:46 -0500, faeychild

Post by faeychild
I have ffmpeg untainted installed. To remove it also nukes clipgrab
and kdenlive. They can be reinstalled but it's annoying.

Why? It's only around 10MB?
"rpm -e --nodeps ffmpeg" will uninstall it without uninstalling the
packages that require it, but don't expect them to work without it.
kdenlive and clipgrab use it.
Note. If you install the tainted version, it will uninstall the core
version as part of the process of updating from  the core version to
the tainted version. The tainted version also can be used by kdenlive
and clipgrab.
There is no need to uninstall the core version to install the tainted version.

Does it overwrite the untainted? - having the same name and all
mga9 kdenlive just complained about audio codec acc I assume may have
something to do with ffmpeg tainted being absent
regards

Yes.
--
Jim Whitby


... bacteriological warfare ... hard to believe we were once foolish
enough to play around with that.
-- McCoy, "The Omega Glory", stardate unknown
----------------------
Mageia release 9 (Official) for x86_64
6.6.18-server-1.mga9 unknown
----------------------

[Bobbie Sellers]

Post by faeychild

On Fri, 08 Mar 2024 18:50:46 -0500, faeychild

Post by faeychild
I have ffmpeg untainted installed. To remove it also nukes clipgrab and
kdenlive. They can be reinstalled but it's annoying.

Why? It's only around 10MB?
"rpm -e --nodeps ffmpeg" will uninstall it without uninstalling the packages
that require it, but don't expect them to work without it. kdenlive and clipgrab
use it.
Note. If you install the tainted version, it will uninstall the core version
as part of the process of updating from  the core version to the tainted
version. The tainted version also can be used by kdenlive and clipgrab.
There is no need to uninstall the core version to install the tainted version.

Does it overwrite the untainted? - having the same name and all
mga9 kdenlive just complained about audio codec acc  I assume may have
something to do with ffmpeg tainted being absent
regards

A while back when I was getting into Linux something wanted codecs and
I found a package of codecs by doing a Internet search
probably with Google. I don't think DuckDuckGo had gotten off the
pond yet. Anyway i found those codec and added them as directed in
the enclosed file Read.me file. Suddenly a great many things no
longer asked for codecs. Whether this is of help or not I do not
know but maybe...

bliss- Dell Precision 7730- PCLOS 2024.03- Linux 6.6.20- Plasma 5.27.10

[faeychild]

    A while back when I was getting into Linux something wanted codecs
and I found a package of codecs by doing a Internet search
probably with Google.  I don't think DuckDuckGo had gotten off the
pond yet.  Anyway i found those codec and added them as directed in
the enclosed file Read.me file.  Suddenly a great many things no
longer asked for codecs.  Whether this is of help or not I do not
know but maybe...

Probably much to do with it, Bobby
Back with Mandrake and RedHat codec were problematic

[TJ]

Post by faeychild
Does it overwrite the untainted? - having the same name and all

It doesn't exactly have the same name - the tainted version has
"tainted" on the end of the rpm name.

When there are tainted and non-tainted (core) versions of the same rpm,
Mageia's update tools consider the tainted version to be higher than the
core version, and so updates it in the normal fashion, by installing the
update first and removing the old package after.

TJ

[David W. Hodgins]

Post by TJ

Post by faeychild
Does it overwrite the untainted? - having the same name and all

It doesn't exactly have the same name - the tainted version has
"tainted" on the end of the rpm name.
When there are tainted and non-tainted (core) versions of the same rpm,
Mageia's update tools consider the tainted version to be higher than the
core version, and so updates it in the normal fashion, by installing the
update first and removing the old package after.

Installing an update, which includes switching from the core to the tainted
version, replaces (writes new temp, unlinks old, renames temp to the proper
name) any files that have the same path and file name, and may write additional
files. Any files that were present in the old version, that are not in the
update, are unlinked and the info about the package including which files it
owns (aka package meta data) is then deleted from the rpm database in
/var/lib/rpm.

It's the unlinking and renaming of files, as well database updates that are
the "uninstalling" part of a package update.

urpmi groups package installations into transactions, at the end of each
transaction. The urpmi database in /var/cache/urpmi which stores info about
which installed packages are required by other packages, is updated after the
end of each transaction

Unlinking (aka deleting) is removing the name and inode entry from from the
directory file in the file system, and freeing all inodes in use by the file.
The data in the file is still present until the part of the storage area
containing it is overwritten.

Regards, Dave Hodgins

[TJ]

Post by David W. Hodgins

Post by TJ

Post by faeychild
Does it overwrite the untainted? - having the same name and all

It doesn't exactly have the same name - the tainted version has
"tainted" on the end of the rpm name.
When there are tainted and non-tainted (core) versions of the same rpm,
Mageia's update tools consider the tainted version to be higher than the
core version, and so updates it in the normal fashion, by installing the
update first and removing the old package after.

Installing an update, which includes switching from the core to the tainted
version, replaces (writes new temp, unlinks old, renames temp to the proper
name) any files that have the same path and file name, and may write additional
files. Any files that were present in the old version, that are not in the
update, are unlinked and the info about the package including which files it
owns (aka package meta data) is then deleted from the rpm database in
/var/lib/rpm.
It's the unlinking and renaming of files, as well database updates that are
the "uninstalling" part of a package update.
urpmi groups package installations into transactions, at the end of each
transaction. The urpmi database in /var/cache/urpmi which stores info about
which installed packages are required by other packages, is updated after the
end of each transaction
Unlinking (aka deleting) is removing the name and inode entry from from the
directory file in the file system, and freeing all inodes in use by the file.
The data in the file is still present until the part of the storage area
containing it is overwritten.
Regards, Dave Hodgins

I never claimed to know all the nuts and bolts of the process. All I
knew was what I saw in the GUI for every update:

Downloading xxxxnew
Installing xxxxnew
Removing xxxxold

And that's all I as a non-technical user really thought I needed to
know, as long as it works.

TJ

[David W. Hodgins]

Post by TJ
And that's all I as a non-technical user really thought I needed to
know, as long as it works.

I like to know how things work. When something does not work properly, it makes
it easier to figure out why it isn't working and how it should be fixed. Some
things I can fix myself, others giving the extra detail helps to get it fixed
properly and quicker.

Once the details have been at least read, it helps in the future to find the
details when needed, without the need to memorize all of them.

Regards, Dave Hodgins

[faeychild]

Post by David W. Hodgins
Note. If you install the tainted version, it will uninstall the core version
as part of the process of updating from  the core version to the tainted
version. The tainted version also can be used by kdenlive and clipgrab.
There is no need to uninstall the core version to install the tainted version.
Regards, Dave Hodgins

I bit the bullet a little before your post

before and after

[***@unmatrix ~]$ rpm -qa |grep ffmpeg
ffmpegthumbs-23.04.1-1.mga9
ffmpeg-5.1.3-3.mga9
[***@unmatrix ~]$ rpm -qa |grep ffmpeg
ffmpegthumbs-23.04.1-1.mga9
ffmpeg-5.1.3-3.mga9.tainted
[***@unmatrix ~]$


Now xine is blasting through mp4's at speed, probably codecs also.
never mind I have work arounds

regards

[faeychild]

Post by faeychild

Post by David W. Hodgins
Note. If you install the tainted version, it will uninstall the core version
as part of the process of updating from  the core version to the tainted
version. The tainted version also can be used by kdenlive and clipgrab.
There is no need to uninstall the core version to install the tainted version.
Regards, Dave Hodgins

I bit the bullet a little before your post
before and after
ffmpegthumbs-23.04.1-1.mga9
ffmpeg-5.1.3-3.mga9
ffmpegthumbs-23.04.1-1.mga9
ffmpeg-5.1.3-3.mga9.tainted
Now xine is blasting through mp4's at speed, probably codecs also.
 never mind I have work arounds

xine needed a reboot, probably to pickup the new ffmpeg


All fine

[David W. Hodgins]

On Sat, 09 Mar 2024 01:34:18 -0500, faeychild <***@nomail.afraid.org> wrote:
<snip>

Post by faeychild

Post by faeychild
I bit the bullet a little before your post
before and after
ffmpegthumbs-23.04.1-1.mga9
ffmpeg-5.1.3-3.mga9
ffmpegthumbs-23.04.1-1.mga9
ffmpeg-5.1.3-3.mga9.tainted
Now xine is blasting through mp4's at speed, probably codecs also.
never mind I have work arounds

xine needed a reboot, probably to pickup the new ffmpeg
All fine

Glad it's working.

Regards, Dave Hodgins

[faeychild]

Post by David W. Hodgins

Post by faeychild
All fine

Glad it's working.
Regards, Dave Hodgins

Well yes and no

That is old work, I have reinstalled since then and found a deal of the
quirkiness has gone
But some anomalies remain. During the media setup all tainted media were
checked


[***@unimatrix ~]# urpmq --list-media active
Core Release (distrib1)
Core Updates (distrib3)
Nonfree Release (distrib11)
Nonfree Updates (distrib13)
Tainted Release (distrib21)
Tainted Updates (distrib23)
Core 32bit Release (distrib31)
Core 32bit Updates (distrib32)
Nonfree 32bit Release (distrib36)
Nonfree 32bit Updates (distrib37)
Tainted 32bit Release (distrib41)
Tainted 32bit Updates (distrib42)

Yet despite this I found that while task-codec-audio/video tainted were
installed, ffmpeg wasn't.

I discovered this when trying to run kdenlive - now corrected

And not even a breath of a problem with xine, it's flawless

Regards

[David W. Hodgins]

Post by faeychild
Yet despite this I found that while task-codec-audio/video tainted were
installed, ffmpeg wasn't.
I discovered this when trying to run kdenlive - now corrected

$ rpm -q --requires kdenlive|grep ffm
ffmpeg

ffmpeg should have been included during the install of kdenlive.

If this was from an m9 install, /root/drakx should contain the logs that show
what happened. If it was installed after Mageia 9 was installed, it may still
be in the journal.

What does "urpmq --list-url" show for the mirror being used?

Regards, Dave Hodgins

[TJ]

On Sun, 17 Mar 2024 02:41:03 -0400, faeychild

Post by faeychild
Yet despite this I found that while task-codec-audio/video tainted were
installed, ffmpeg wasn't.
I discovered this when trying to run kdenlive - now corrected

$ rpm -q --requires kdenlive|grep ffm
ffmpeg
ffmpeg should have been included during the install of kdenlive.

It's dangerous to assume something that was not said, but I believe he
meant that the core version of ffmpeg was installed, but the tainted
version was not.

Kdenlive is a core package, so therefore cannot require any tainted
packages to install and run, but that doesn't mean all the features are
available without the appropriate tainted packages.

As to why ffmpeg core wasn't updated to ffmpeg tainted with the other
core-to-tainted packages, I don't have a clue.

TJ

[David W. Hodgins]

Post by TJ

On Sun, 17 Mar 2024 02:41:03 -0400, faeychild

Post by faeychild
Yet despite this I found that while task-codec-audio/video tainted were
installed, ffmpeg wasn't.
I discovered this when trying to run kdenlive - now corrected

$ rpm -q --requires kdenlive|grep ffm
ffmpeg
ffmpeg should have been included during the install of kdenlive.

It's dangerous to assume something that was not said, but I believe he
meant that the core version of ffmpeg was installed, but the tainted
version was not.
Kdenlive is a core package, so therefore cannot require any tainted
packages to install and run, but that doesn't mean all the features are
available without the appropriate tainted packages.
As to why ffmpeg core wasn't updated to ffmpeg tainted with the other
core-to-tainted packages, I don't have a clue.

If that's the case, see if "urpmi --auto-update --auto" installs the tainted
version. If not, run it again with "urpmi --auto-update --auto --debug".,
and post the results.

Regards, Dave Hodgins

[William Unruh]

Post by faeychild

Post by David W. Hodgins

Post by faeychild
All fine

Glad it's working.
Regards, Dave Hodgins

....
Not everythng in tainted, or in any of the other repositories, are
installed. That would end you up with probably with 100GB or so of
installed stuff. ffmpeg is file with somewhat dubious legality in many
parts of the world, and Mageia would not want to be arrested for
encouraging lawbreaking in some corner of the world. Thus it is almost
certainly not on the list of stuff installed automaticall. You need to
install it specially yourself, so that only you would get arrested if it
happened to be illegal in your neck of the woods.
So, just install it.

Post by faeychild
Yet despite this I found that while task-codec-audio/video tainted were
installed, ffmpeg wasn't.
I discovered this when trying to run kdenlive - now corrected
And not even a breath of a problem with xine, it's flawless
Regards

[faeychild]

Post by William Unruh

Post by David W. Hodgins

Post by faeychild
All fine

Glad it's working.
Regards, Dave Hodgins

....
Not everythng in tainted, or in any of the other repositories, are
installed. That would end you up with probably with 100GB or so of
installed stuff. ffmpeg is file with somewhat dubious legality in many
parts of the world, and Mageia would not want to be arrested for
encouraging lawbreaking in some corner of the world. Thus it is almost
certainly not on the list of stuff installed automaticall. You need to
install it specially yourself, so that only you would get arrested if it
happened to be illegal in your neck of the woods.
So, just install it.

\
Then that would suggest that while task-codec-audio/video tainted are
not as tainted as ffmpegg, one just has to be on one's toes in this regard
A note in the brain file regarding this anomaly

Thanks William