Bug 193615

Summary:	[RFE] it would be nice to be able to use local (file:///) URLs in mock's yum config
Product:	[Fedora] Fedora	Reporter:	Alexandre Oliva <oliva>
Component:	mock	Assignee:	Seth Vidal <skvidal>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	extras-qa
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-06-01 17:32:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alexandre Oliva 2006-05-31 06:36:05 UTC

I have a local mirror of rawhide, which is available over NFS or on my local
main server, but not over ftp or http.  Mock currently makes it impossible
AFAICT to use this local copy for builds.  It would be possible to get it to use
them by introducing support for bind mounts in the mock build tree.

Also, it would be nice if chroot config files didn't have to be in /etc/mock,
such that I could set up mock config files and build roots as a regular user,
after adding my regular user to the group mock.

Is any such thing planner or even in the works?

Comment 1 Seth Vidal 2006-06-01 17:32:25 UTC

mock for the buildsys and for my own personal box uses file:// repos just fine.
Have you actaully tested it?

example:

[holding]
name=holding
baseurl=file:///rpmbuild/holding/c4/x86_64/

works a treat.

Comment 2 Alexandre Oliva 2006-06-02 09:25:18 UTC

Yes, I tried it in the mock config, and I just copied the entries from my
yum.conf, but mock wouldn't find the pathnames within the chroot, for reasons
that seemed obvious to me.  I'll try again and see if I made any obvious
mistakes, if this is actually expected to work.

Comment 3 Seth Vidal 2006-06-02 11:53:22 UTC

keep in mind that the file:/// are for paths OUTSIDE of the chroot.

but yes, it is not only expected it is KNOWN to work.

the fedora extras buildsys uses it this way.

You did create the repodata in your local file dir, right?