Bug 35856
Summary: | --whatprovides breaks for invalid param | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | James Manning <jmm> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED NOTABUG | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-04-13 03:29:36 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
James Manning
2001-04-13 03:29:32 UTC
This is an issue with the beta server and not with up2date itself. I am able to run 'up2date --whatprovides dcopserver' against the internal test machines (which have the same code base as the live servers) and get back a null list. so what are we supposed to file against with up2date server problems? FWIW, Adrian wanted me to create this bugzilla entry, although I'm not sure why |