Re: Invalid Argument?
Hunter Matthews <[email protected]>
| Newsgroups | gmane.network.up2date.current.devel |
|---|---|
| Message-ID | <1012603562.9684.194.camel@jade> |
If I'm not mistaken, "5" means that the md5 checksum did _not_ pass. Try rpm -e current rm -rf /usr/share/current rpm -Uvh current-0.9.4-1.noarch.rpm And see if that improves matters. On Fri, 2002-02-01 at 17:41, Brian Lalor wrote: > On 1 Feb 2002, Hunter Matthews wrote: > > > Do a rpm -V on current. Either that file is corrupted, or something. > > S.5....T c /etc/current/current.conf > S.5....T /usr/share/current/ConstructParser.pyc > S.5....T /usr/share/current/auth.pyc > S.5....T /usr/share/current/channel.py > S.5....T /usr/share/current/channel.pyc > S.5....T /usr/share/current/errata.pyc > S.5....T /usr/share/current/logger.pyc > S.5....T /usr/share/current/misc.pyc > S.5....T /usr/share/current/packagedb.pyc > S.5....T /usr/share/current/registration.pyc > S.5....T /usr/share/current/standalone.pyc > S.5....T /usr/share/current/up2date.pyc > > > If cadmin can do an info, then current _should_ be able to open it. They > > are both calling channel.py:open() > > I had the same thing happen with tarballs for 0.9.2 and 0.9.4... > > -- > Brian Lalor > [email protected] > > _______________________________________________ > Current-server mailing list > [email protected] > http://lists.dulug.duke.edu/mailman/listinfo/current-server > > -- Hunter Matthews Unix / Network Administrator Office: BioScience 145/244 Duke Univ. Biology Department Key: F0F88438 / FFB5 34C0 B350 99A4 BB02 9779 A5DB 8B09 F0F8 8438 Never take candy from strangers. Especially on the internet.