From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc3) Gecko/20020523
Description of problem:
For some reason, the source packages corresponding to some of the binary rpms
appear to be missing, e.g., glibc-2.2.90-2.src.rpm. When up2date attempts to
download these, it cannot find them. I've been working around it by linking a
dummy .src.rpm under the name, but this requires restarting up2date. It would
be preferable to have an option to ignore this particular error. But why are
the packages not there?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.up2date --nosig --src -u
Actual Results: Dies when a required source rpm is not found. Updating from the
original null install, the following are missing:
Expected Results: All source rpms ought to be present. Failing that, the program
should be able to proceed gracefully.
I tried to update up2date first, but it kept generating an (unrelated)
backtrace, so I downgraded back to the version from the iso.
beta issue. The src rpms werent pushed along with the bin rpms to
Generally, I consider 404's as fatal errors, since it means that
what the user requested be done can not be accomplished.
It still seems to me that one ought to attempt to download all the packages,
total up the number of errors, and die with a count of the missing packages.
It's a UI bug: if I ask up2date to download a gigabyte of data while I go to
dinner, and I come back to find that's it only retrieved 1% of said data when
99+% was available, I'm greatly annoyed. How about a simple flag to continue