Bug 56441
Summary: | up2date bombs out if it cannot download associated source RPM for a selected package | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Ray Price <dohrayme> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED NOTABUG | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | cturner, gafton, mihai.ibanescu, pjones, srevivo, taw |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-04-29 23:01:05 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
Ray Price
2001-11-18 15:00:47 UTC
Well, if you cant download the src rpms the user asked for, I think throwing up an error message is the correct thing to do for now. Ideally we would throw up an error message and have some way to ignore it if we like, but that will have to wait for the next version. The real question is "why are source rpm downloads failing?" The problem with ignoring missing source packages is: what status code do you return when up2date exits? It would need to be non-zero to be useful for testing. Admittedly, this is only a problem for testers, and a testers problem shouldn't really be made a users problem. So is it a bug or ain't it a bug? not a bug... if the download fails: a). up2date didnt do what the user wanted. Thats a failure and shouldnt be ignore. b) It means something is wrong with the server, and should be fixed. |