Bug 31245

Summary:	Mageia 8 to Mageia 9/cauldron upgrade results in error "detecting looping forever while trying to resolve dependencies"
Product:	Mageia	Reporter:	PC LX <mageia>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	major
Priority:	Normal	CC:	davidwhodgins
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	Output of "urpmi --split-length 0 --auto-update --auto -vv --debug"

Description PC LX 2022-12-08 14:56:02 CET

Description of problem:

In testing an upgrade from my workstation's Mageia 8 system to Mageia 9/cauldron using the following commands:
"""
ROOT_CAULDRON='/mnt/tmp'
URL='http://ftp.free.fr/mirrors/mageia.org/distrib/cauldron/x86_64/'
urpmi.removemedia --urpmi-root "$ROOT_CAULDRON" -a
urpmi.addmedia --urpmi-root "$ROOT_CAULDRON" --distrib "$URL"
urpmi --split-length 0 --auto-update --auto
"""
results in the following error message being displayed:
"""
detecting looping forever while trying to resolve dependencies.
Aborting... Try again with '-vv --debug' options at /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm line 1288.
"""
and the actual upgrade not starting.

This upgrade is being tested in a overlay FS over the root and run in a systemd-nspawn container.
I have used this setup multiple times before so it probably is not the unusual setup that is causing the issue.

The upgrade log is in attachment.


How reproducible:

Always.



Steps to Reproduce:
1. Start with a Mageia 8 system.
2. Create overlayfs over the root.
3. Start a systemd-nspawn container with the overlayfs as root (systemd-nspawn --network-veth --network-bridge=br0 -D "$ROOT_CAULDRON" --boot).
4. Remove old repositories (urpmi.removemedia -a).
5. Add cauldron repositories (urpmi.addmedia --distrib "$URL").
6. Run update (urpmi --split-length 0 --auto-update --auto)
7. See aborted update and error message.

Comment 1 PC LX 2022-12-08 14:58:18 CET

Created attachment 13551 [details]
Output of "urpmi --split-length 0 --auto-update --auto -vv --debug"

Comment 2 Dave Hodgins 2022-12-08 18:36:32 CET

Is glibc in /etc/urpmi/skip.list ?

CC: (none) => davidwhodgins

Comment 3 PC LX 2022-12-08 19:06:38 CET

(In reply to Dave Hodgins from comment #2)
> Is glibc in /etc/urpmi/skip.list ?

Yes, it is (/^glibc/).

After clearing the skip.list, the upgrade continued without problems.

Marking this bug as invalid, caused by user incompetence!

Thanks.

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