Description of Problem:
If up2date is configured to not install packages after downloading them,
then an unresolved dependency should not be a fatal error - the packages
should still be downloaded.
Version-Release number of selected component (if applicable):
How Reproducible: always
Steps to Reproduce:
1. Install a package that depends on a particular version of a
2. Run up2date-config, and set it to only download packages, not install them.
3. Run up2date and select to update the package that the external package
An unresolved dependencies dialog appears, and it is impossible to continue
with the download.
A warning should be shown, but the user should have the option to download
the package anyway.
For the time being, this is "working as designed". Basically, the intention
is that up2date only installs/fetches package sets if they can be installed
correctly. Downloading a partial set of packages cant provide that guarantee.
It could be argued that up2date should let you download only any
given package regardless of what dep errors it might cause. We'll
take a look at maybe changing that spec and possiblly adding the
ability to support that mode of operations
A couple people have asked for the ability to directly download
a package or packages even if it cant be installed properly, so
marking this as an request for enhancement.
added in 3.1.35
*** Bug 84546 has been marked as a duplicate of this bug. ***