Bug 31434 - attempting to install packages from *tainted* or *non-free* repos via Mageia Welcome fails: "no package named tainted" or "no package named non-free"
Summary: attempting to install packages from *tainted* or *non-free* repos via Mageia ...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker normal
Target Milestone: ---
Assignee: papoteur
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-19 07:31 CET by Ben McMonagle
Modified: 2023-01-26 11:20 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Ben McMonagle 2023-01-19 07:31:05 CET
Description of problem: after enabling *tainted* repos, attempting to install audio and video codecs via Mageia Welcome fails: "no package named tainted".

install offers task-video-codec & tainted
or
install offers task-audio-codec & tainted

Mageia-9-beta1-i586.iso
DATE.txt: Mon Jan 16 09:57:50 PM CET 2023

Version-Release number of selected component (if applicable):
mageiawelcome-2.19-1.mga9

How reproducible:always


Steps to Reproduce:
1.install mate DE from above .iso
2.attempt to install video and audio codecs via Mageia Welcome
3.
Comment 1 Ben McMonagle 2023-01-19 07:37:15 CET
install offers task-video-codec & tainted
or
install offers task-audio-codec & tainted

should read

install offers task-codec-video & tainted
or
install offers task-codec-audio & tainted

attempting to install command line gives:

root@localhost ~]# urpmi task-codec-audio task-codec-video
Packages task-codec-video-9-1.mga9.i586, task-codec-audio-9-1.mga9.i586 are already installed

so Mageia Welcome is offering to install packages that are already installed
Comment 2 Ben McMonagle 2023-01-19 09:59:22 CET
seems that non-free packages are also affected.


changing title to reflect this

Summary: attempting to install audio and video codecs via Mageia Welcome fails: "no package named tainted" => attempting to packages from *tainted* or *none-free* via Mageia Welcome fails: "no package named tainted" or "no package named non-free"

Ben McMonagle 2023-01-19 10:00:03 CET

Summary: attempting to packages from *tainted* or *none-free* via Mageia Welcome fails: "no package named tainted" or "no package named non-free" => attempting to install packages from *tainted* or *none-free* repos via Mageia Welcome fails: "no package named tainted" or "no package named non-free"

Ben McMonagle 2023-01-19 10:00:23 CET

Summary: attempting to install packages from *tainted* or *none-free* repos via Mageia Welcome fails: "no package named tainted" or "no package named non-free" => attempting to install packages from *tainted* or *non-free* repos via Mageia Welcome fails: "no package named tainted" or "no package named non-free"

Comment 3 Ben McMonagle 2023-01-19 10:06:42 CET
(In reply to Ben McMonagle from comment #1)

> 
> so Mageia Welcome is offering to install packages that are already installed.

if packages are installed via commandline, Mageia Welcome is not updating even when restarted, the *install* button remains.
papoteur 2023-01-19 10:10:46 CET

CC: (none) => yves.brungard_mageia
Assignee: bugsquad => yves.brungard_mageia

Comment 4 Dave Hodgins 2023-01-19 23:33:58 CET
Changing /usr/share/mageiawelcome/mw-ui.qml
-                                                        launch.command(["/usr/bin/gurpmi",name,repo,])}
+                                                        launch.command(["/usr/bin/gurpmi",name])}

allows it to work, but then there is no point to listing the release and
tainted versions in mageiawelcome as it will always install the tainted
version, if the tainted repos have been enabled (as it should).

I tested with vlc from the applications menu, as that was not already installed.

CC: (none) => davidwhodgins

Comment 5 Thomas Andrews 2023-01-19 23:35:03 CET
I just installed Plasma from the fourth round of beta CI isos, and 64-bit is affected too, but the symptoms I see are different, if I am reading correctly.

I used MCC to set up the repos from the math.princeton mirror, activated 64-bit tainted release and updates but none of the 32-bit repos, then went to Mageia Welcome. I used the Update tab to get updates, including the tainted versions of task-codec-audio, task-codec-video, and VLC.Going to the "Applications" tab, I see the audio and video codecs listed twice, once indicating they were already installed, another offering to install the tainted version. If I click on "install," a box pops up:

"You are about to install the following packages on your computer:

-task-codec-video (or audio)
-tainted

Proceed?"

VLC is also listed twice, once with a box marked "Launch" and once offering to install the tainted version.

Smplayer wasn't installed on the system. Clicking on "Install" asks for the root password, then a box pops up saying "No package named..."

So it would appear that the user can't install anything that is on the "Applications" page.
Comment 6 Dave Hodgins 2023-01-19 23:36:49 CET
I consider this bug to be a release blocker for the beta iso images. It's too
high profile, and the type of bug that reviewers will notice.

Priority: Normal => release_blocker

Comment 7 Thomas Andrews 2023-01-20 16:51:47 CET
For what it's worth, the install from Comment 5 is on an EFI machine. I wouldn't think that would make a difference, but...

I just looked at another 64-bit Cauldron Plasma install, this one from an older round of isos, but fully updated. It is on an HP Probook 6550b, an MBR machine.

When I run Mageia Welcome on this machine, and go to the Applications tab, I do not see two instances of the packages that have core and tainted versions, just the one that is currently installed, if it is installed. The "launch" button on installed packages works, but if I click on any "install" button, whether from tainted or core, I get the "no package named" box after entering the root password.

And I just booted the install from Comment 5 again, and it looks just like the one on the 6550b. Only one instance (tainted) of the installed audio/video codecs and VLC, so it looks like it had been updated sometime in the course of rebooting. And, the inability to install anything not already installed is still there.

CC: (none) => andrewsfarm

Comment 8 papoteur 2023-01-21 10:14:34 CET
Release 2.20 is building. It should solve the problem of installation of selected application.
On another side, it adds isodumper and remove k9copy.
Comment 9 papoteur 2023-01-21 10:17:49 CET
(In reply to Thomas Andrews from comment #7)
> When I run Mageia Welcome on this machine, and go to the Applications tab, I
> do not see two instances of the packages that have core and tainted
> versions, just the one that is currently installed, if it is installed.
When there is two versions of the same package, from Core and from Tainted, and that Tainted one is installed, only the tainted one is displayed.
Comment 10 Thomas Andrews 2023-01-21 14:29:58 CET
(In reply to Dave Hodgins from comment #4)
> allows it to work, but then there is no point to listing the release and
> tainted versions in mageiawelcome as it will always install the tainted
> version, if the tainted repos have been enabled (as it should).

I can see the point of listing both in the situation where the core version is already installed, to let the user know that there is a tainted version available, but for whatever reason isn't installed. It's possible that the user wouldn't *want* the tainted versions of some packages but does want it of another.
Comment 11 Dave Hodgins 2023-01-21 21:01:15 CET
Unlike backports, tainted was never intended as a pick and choose media.
Either the system has the versions that may violate patent laws or it
doesn't.

If the admin chooses to enable (install any) tainted, then tainted should
always be selected in preference to core.
Comment 12 Thomas Andrews 2023-01-22 17:21:46 CET
(In reply to papoteur from comment #8)
> Release 2.20 is building. It should solve the problem of installation of
> selected application.
> On another side, it adds isodumper and remove k9copy.

Just got a new horde of Cauldron updates on the install from comment 5, including mageiawelcome, urpmi, gurpmi, a new kernel, and more. I rebooted after the dust settled, and Mageia Welcome now installs packages with no problems.

One niggle... I had not checked the list of games from Mageia Welcome when I went looking at things. We should be aware that some of those games may not play on older, limited, real 32-bit hardware. 0ad is one example that will not run on a GPU that isn't capable of at least OpenGL 2.0. (See bug 31434)

Other applications are affected by this limitation, and they can crop up anywhere. For example, Foolishness, my Dell Inspiron 5100, cannot run Plasma or a number of Plasma applications because of it. There's nothing that can be done about it, it's just the way things are.

This is not a big enough issue to continue to block the beta release of Mageia 9, but perhaps there should be a brief warning somewhere, maybe in the yellow box at the top of the Mageia Welcome Applications screen, that "Some applications may not function on older 32-bit hardware, due to limitations of that hardware."

Just a thought...
Comment 13 Thomas Andrews 2023-01-22 17:47:47 CET
I just checked out Cauldon's Mageia Welcome on my Dell 32-bit hardware, and I do see one problem that should be addressed.

In "Applications" under the "System" tab, there is a listing for VirtualBox. We haven't had a functioning 32-bit version of VirtualBox since, what, Mageia 7? Clicking on "Install" does install our 32-bit package, but because it's just a "placeholder," it doesn't do anything. 

We have an advisory in Mageia Welcome that Steam needs the 32-bit repos to be enabled; at the very least we need one for VirtualBox that warns it won't function on any 32-bit systems.
Comment 14 Ben McMonagle 2023-01-23 08:46:26 CET
just updated my 64 multiDE system
Mageia Welcome is ok
Handbrake (tainted) install no longer offers *tainted* as well. 
install proceeds.

*Install* updates / refreshes to *Launch* 

(In reply to Thomas Andrews from comment #13)

> We have an advisory in Mageia Welcome that Steam needs the 32-bit repos to
> be enabled; at the very least we need one for VirtualBox that warns it won't
> function on any 32-bit systems.

suggest a M/W note that advises that 32bit Virtualbox is no longer supported:

*Virtualbox* Virtualisation software (for installation into 64bit systems only)
or
*Virtualbox* Virtualisation software (installation into 32bit systems is no longer supported)

recommend a new bug report/enhancement request for this.



marking as resolved - fixed

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 15 papoteur 2023-01-26 11:20:57 CET
(In reply to Ben McMonagle from comment #14)
> > We have an advisory in Mageia Welcome that Steam needs the 32-bit repos to
> > be enabled; at the very least we need one for VirtualBox that warns it won't
> > function on any 32-bit systems.
> 
> suggest a M/W note that advises that 32bit Virtualbox is no longer supported:
> 
> *Virtualbox* Virtualisation software (for installation into 64bit systems
> only)
> or
> *Virtualbox* Virtualisation software (installation into 32bit systems is no
> longer supported)
Done

Note You need to log in before you can comment on or make changes to this bug.