Bug 30589 - mock reads dnf metadata 2x but fails the second time
Summary: mock reads dnf metadata 2x but fails the second time
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Neal Gompa
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-30 17:28 CEST by papoteur
Modified: 2022-06-30 21:14 CEST (History)
0 users

See Also:
Source RPM: mock-2.9-1.mga8.src.rpm
CVE:
Status comment:


Attachments
log of mock (9.28 KB, text/plain)
2022-06-30 17:29 CEST, papoteur
Details

Description papoteur 2022-06-30 17:28:00 CEST
Description of problem:
Trying to build python-requests for cauldron within Mageia 8 host, a first step installing the chroot successes after downloading the dnf metadata, but a second step trying to install the dependencies fails. It tries again to download the metadata.
Mageia Cauldron - x86_64        2.7 kB/s | 2.5 kB     00:00    
Mageia Cauldron - x86_64        0.0  B/s |   0  B     00:06
Errors during downloading metadata for repository 'mageia-cauldron':

I don't understand if checksum is bad or if filelists file is not found in any repository.
If I try again, the first step successes but the second fails again.
I don't know if the problem is in the metadata, but if this is the case, why the first step successes while the second fails.

How reproducible:
mgarepo co python-requests
cd python-requests
mock  -r mageia-cauldron-x86_64 --source SOURCES/ --spec SPECS/python-requests.spec
Full log will follow
Comment 1 papoteur 2022-06-30 17:29:46 CEST
Created attachment 13317 [details]
log of mock
Comment 2 Lewis Smith 2022-06-30 21:14:35 CEST
Thank you for the report.
Could this be due to a mix of Mageia 8 & Cauldron?

This SRPM is formally with Neal, so assigning to you (even though others have been keeping it up-to-date recently). Please re-assign it if you wish.

Assignee: bugsquad => ngompa13


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