Bug 135547
| Summary: | "Your system is fully updated" but updates available | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andrew <alphastar> | ||||
| Component: | up2date | Assignee: | Bret McMillan <bretm> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2006-04-22 15:23:59 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 123268, 136451 | ||||||
| Attachments: |
|
||||||
|
Description
Andrew
2004-10-13 12:47:13 UTC
Created attachment 105142 [details]
Last entries in /var/log/up2date
Up to a couple minutes ago I was getting the same "fully updated" message described above. I have noticed (yesterday as well) that if I wait some hours and do in /var/spool/up2date # rm -rf fedora-core-rawhide* that it seems to 'jumpstart' the process, and it proceeds to downloading the individual package headers. I have also been getting this same problem however the packages are random (most recently firefox) I removed firefox-1.0-2.fc3.i386.hdr from /var/spool/up2date and it kicked off the updates. Not sure if I should have removed that file but it certainly did the trick. up2date is no longer shipped with Fedora Core; it's functionality has been replaced by pup, found in the pirut package. The only fixes likely to be made to up2date in RedHat Linux and earlier Fedora Core versions are security fixes by Fedora Legacy. This does not seem to be a security bug, so I'm closing it. If the problem is appropriate to RHEL and occurs to a user there, it can be filed as such. |