Bug 26346 - mock fails on cauldron on the joe .src.rpm from "mgarepo co joe"
Summary: mock fails on cauldron on the joe .src.rpm from "mgarepo co joe"
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Neal Gompa
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-16 18:09 CET by Shlomi Fish
Modified: 2020-03-21 15:37 CET (History)
1 user (show)

See Also:
Source RPM: mock-1.4.15-3.mga8.src.rpm
CVE:
Status comment:


Attachments
the mock -v output (10.07 KB, application/x-xz)
2020-03-16 18:11 CET, Shlomi Fish
Details
mock for "joe" works fine now after commenting out the "/6/" baseurl= (27.46 KB, application/x-xz)
2020-03-19 16:08 CET, Shlomi Fish
Details

Description Shlomi Fish 2020-03-16 18:09:54 CET
Description of problem:

mock fails on cauldron on the joe .src.rpm from "mgarepo co joe". Here is the output of mock -v:

<<<<<<<<<<<<<<<
INFO: mock.py version 1.4.15 starting (python version = 3.8.2)...
Start: init plugins
DEBUG: ensuring that dir exists: /var/cache/mock/mageia-cauldron-x86_64/dnf_cache/
INFO: selinux disabled
Finish: init plugins

ERROR: Exception(/home/shlomif/Download/unpack/mageia/mgarepos/todel/joe/SRPMS/joe-4.6-3.mga8.src.rpm) Config(mageia-cauldron-x86_64) 0 minutes 33 seconds
INFO: Results and/or logs in: /var/lib/mock/mageia-cauldron-x86_64/result
DEBUG: kill orphans
DEBUG: child environment: None
DEBUG: Executing command: ['/bin/umount', '-n', '/var/lib/mock/mageia-cauldron-x86_64/root/var/cache/dnf/'] with env {'TERM': 'vt100', 'SHELL': '/bin/sh', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'LANG': 'en_GB.UTF-8'} and shell False
DEBUG: Child return code was: 0
ERROR: Command failed: 
 # /usr/bin/systemd-nspawn -q -M 279a200633564b88b1ef40e66ccde43a -D /var/lib/mock/mageia-cauldron-x86_64/root -a --capability=cap_ipc_lock --bind=/tmp/mock-resolv.9qlswwrc:/etc/resolv.conf --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin --setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007" --setenv=PS1=<mock-chroot> \s-\v\$  --setenv=LANG=en_GB.UTF-8 -u mockbuild bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/joe.spec

>>>>

trimmed due to size limit. I'll attach it.
Comment 1 Shlomi Fish 2020-03-16 18:11:02 CET
Created attachment 11550 [details]
the mock -v output
Comment 2 Shlomi Fish 2020-03-16 19:18:17 CET
I should note that on fedora 31 x64 «fedpkg --release f31 clone --anonymous joe» followed by «fedpkg mockbuild» is successful.
David Walser 2020-03-16 22:01:26 CET

Assignee: bugsquad => ngompa13

Comment 3 Jani Välimaa 2020-03-19 15:35:52 CET
It's not related to mock, but perhaps to an outdated mirror? I've no problems to build joe locally with mock.

Build log says it's calling libtoolize. So it means that rpm-mageia-setup(,-build) is outdated as %configure macro was switched to behave like old %configure2_5x did and old %configure was calling libtoolize.

CC: (none) => jani.valimaa

Comment 4 Jani Välimaa 2020-03-19 15:46:38 CET
Mock config for mageia-cauldron repo has two baseurls defined and the latter one is having mga6's url for core media.

Cauldron's %configure macro doesn't work as expected with mga6. See comment 3.
Comment 5 Shlomi Fish 2020-03-19 16:08:30 CET
Created attachment 11558 [details]
mock for "joe" works fine now after commenting out the "/6/" baseurl=

Thanks Jani! Good call! Commenting out the second "baseurl=" line with the "/6/" in /etc/mock/mageia-cauldron-x86_64.cfg fixed the issue. Here is the successful log.
Comment 6 Jani Välimaa 2020-03-21 15:12:56 CET
Closing as INVALID. Feel free to reopen if needed.

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

Comment 7 Shlomi Fish 2020-03-21 15:37:25 CET
(In reply to Jani Välimaa from comment #6)
> Closing as INVALID. Feel free to reopen if needed.

Ah, I understand it was caused by a stale / old configuration file on my machine.  Thanks for the help!

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