Bug 1045539

Summary:	FedUp should have option to download RPMs into /var/cache/yum and preserve them there
Product:	[Fedora] Fedora	Reporter:	Jonathan Kamens <jik>
Component:	fedup	Assignee:	Will Woods <wwoods>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	tflink, udovdh, wwoods
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 10:48:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jonathan Kamens 2013-12-20 16:50:51 UTC

I keep copies of all the RPMs installed on my system on the local hard disk for disaster recovery (the local hard disk is mirrored to a second hard disk nightly, which means that if my primary hard disk fails, I can reinstall the RPMs from the second disk without having to re-download everything). I can't imagine that I'm the only person that does this.

When I upgrade with FedUp, it downloads all the packages, then does the upgrade, then deletes them. Then I have to download them all again, which is ridiculous.

There should be an option to FedUp to download the RPMs into the standard paths beneath /var/cache/yum and leave them there after the upgrade.

Comment 1 Fedora End Of Life 2015-05-29 10:04:40 UTC

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Jonathan Kamens 2015-05-29 12:37:30 UTC

Still an issue, as far as I know.

Comment 3 Fedora End Of Life 2016-07-19 10:48:38 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.