This probably isn't a bug but I want to make sure. I've been running
up2date every day since I installed Fisher and have seen no new package.
Since the release notes indicated that new packages should be available, I
was about to report this as a bug, but my query showed a few others who
needed to be told about up2date -r. I also didn't know about this. (Since
I've been trying that, I've been getting connection refused, but I assume
this is a temporary situation.)
I've never used up2date before, so maybe this is "NOTABUG". I'm just
surprised that running up2date with no arguments never gave any hint that
something was wrong. Is it because it was checking a repository for the
wrong distribution? Anyway, if this is the expected behavior, just close
this out. I wanted to make sure though that something isn't wrong with
There are currently no new packages available in the up2date database
for fisher, so the results you are seeing are correct.
We (Red Hat) should really try to resolve this before next release.
resolve what? up2date is performing correctly in this case.
Assigned QA to jturner
right, we have not made updates publically available for fisher via up2date at
this point, although we once planned to. Updates are available via ftp in the