Bug 479716 – --cache does not work

Bug 479716 - --cache does not work

Summary:	--cache does not work

Status:	CLOSED UPSTREAM

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	livecd-tools (Show other bugs)
Sub Component:
Version:	10
Hardware:	x86_64 Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Jeremy Katz
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2009-01-12 12:06 EST by Jan Kratochvil
Modified:	2009-01-12 15:19 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2009-01-12 15:19:38 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
+keepcache=1 (440 bytes, patch) 2009-01-12 12:06 EST, Jan Kratochvil	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jan Kratochvil 2009-01-12 12:06:26 EST

Created attachment 328764 [details]
+keepcache=1

Description of problem:
Specifying --cache works if the image creation fails.  It gets reused afterwards.  But if we successfully create an image YUM itself deletes all the rpm files and next run of livecd-creator starts to download it all again.

Version-Release number of selected component (if applicable):
livecd-tools-020-1.fc10.x86_64
yum-3.2.20-5.fc10.noarch

How reproducible:
Always.

Steps to Reproduce:
1. livecd-creator -c psi-i686.ks --cache=./cache

Actual results:
Resulting ./cache is about 500MB.

Expected results:
Resulting ./cache about 2GB.

Additional info:
I did not check how this option behaves without --cache specified.  But as the directory gets deleted completely by livecd-creator it should not be a problem.

Comment 1 Jeremy Katz 2009-01-12 15:19:38 EST

Thanks, applied in git

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