Bug 24376

Summary:	When adding media from MCC, 32-bit core_release and 32-bit core_updates repositories aren't enabled by default, but 32-bit nonfree and tainted are enabled.
Product:	Mageia	Reporter:	Thomas Andrews <andrewsfarm>
Component:	RPM Packages	Assignee:	Mageia tools maintainers <mageiatools>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia, marja11, thierry.vignaud, tmb
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
See Also:	https://bugs.mageia.org/show_bug.cgi?id=23927
Whiteboard:
Source RPM:	urpmi (?), rpmdrake	CVE:
Status comment:

Description Thomas Andrews 2019-02-16 23:31:20 CET

Description of problem:

When using the MCC tool to add online media, the 32-bit core_release and 32-bit core_updates repositories are not automatically enabled as they have been with past releases. This happens whether the Mirror List or a specific mirror is used. The repositories are easily enabled by checking the boxes in the gui, indicating that the problem is not one of a bad download from the mirror.

The 32-bit nonfree_release and nonfree_updates repositories ARE enabled by default, as has been done with past releases.

It would seem to me that, to be consistent we should either enable the 32-bit core and update repositories by default, or disable all of the 32-bit repositories by default. 

This has been an ongoing situation, so there may be a bug on it already, but I don't seem to have the skill to find it. Or, I suppose this could be a new policy and I missed the discussion. I thought this was a good way to ask, either way.

Marja Van Waes 2019-02-17 09:33:38 CET

Source RPM: (none) => urpmi (?), rpmdrake
Assignee: bugsquad => mageiatools
CC: (none) => marja11, thierry.vignaud
Summary: When adding media from MCC, 32-bit core_release and 32-bit core_updates repositories not enabled by default => When adding media from MCC, 32-bit core_release and 32-bit core_updates repositories not enabled by default, but 32-bit nonfree is enabled.

Comment 1 Thomas Backlund 2019-02-17 10:08:01 CET

It's intentional to not enable 32bit medias anymore, but there is a bug in drakx that enables the 32bit nonfree if 64bit nonfree gets enabled

CC: (none) => tmb

Martin Whitaker 2019-02-17 18:41:46 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=23927
CC: (none) => mageia

Comment 2 Marja Van Waes 2019-02-28 19:23:34 CET

In bug 24438, "PC LX" showed that 32bit tainted is enabled by default, too, so adding that to the summary of this report.

Summary: When adding media from MCC, 32-bit core_release and 32-bit core_updates repositories not enabled by default, but 32-bit nonfree is enabled. => When adding media from MCC, 32-bit core_release and 32-bit core_updates repositories aren't enabled by default, but 32-bit nonfree and tainted are enabled.

Comment 3 Rémi Verschelde 2019-04-02 16:10:26 CEST

Confirmed in current Cauldorn.

(In reply to Thomas Backlund from comment #1)
> It's intentional to not enable 32bit medias anymore, but there is a bug in
> drakx that enables the 32bit nonfree if 64bit nonfree gets enabled

Do you know what commit introduce the change to not enable 32bit medias? The culprit is likely there, where nonfree and tainted were probably missed.

Comment 4 Thomas Andrews 2019-04-02 17:13:41 CEST

I just had occasion to do an install from the round 1 beta3 M7 Classical iso. I did not go after updates with the installer, partly because the wifi on that laptop can't be started until after the first boot.

After the first boot and starting the wifi, I used the MCC tool to add a speecific mirror, in this case the math.princeton mirror. When finished, the only 32-bit repositories that were activated by default were Nonfree_release and Nonfree_updates. None of the tainted repositories were activated by default, 64-bit OR 32-bit. As is my custom, I activated tainted_release, tainted_updates, 32-bit Core_Release, 32-bit Core_Updates, and the 32-bit tainteds manually.

I have noticed in past Mageias where, if you add additional media or replace MIRRORLIST with a specific mirror, whatever repositories were active before the addition or replacement were also automatically activated in the addition or replacement. I just checked that with that "fresh" laptop install, and while the 64-bit and 32-bit tainted repositories on the new mirror had been activated, as they are on the original mirror, 32-bit Core_Release and 32-bit Core_Updates were not.

Comment 5 Martin Whitaker 2019-05-27 16:01:51 CEST

Fixed in urpmi-8.116-1.

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

Comment 6 Thomas Andrews 2019-05-28 17:02:49 CEST

Confirmed as of the Mageia 7 RC Round 4 isos.