Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RedHat Enterprise Linux



I've been investigating this update issue and have a couple of
comments.

1) yum does not seem to be installed on my system. My system
basically has been a rolling upgrade of red hat for the past
3 years. My last os upgrade was from red hat 9 to fedora core
1. So unless I have to install yum as a separate rpm, then
either fedora core 1 does not come with yum, or the upgrade
from red hat 9 to fedora core 1 left out yum.  So for now
I'll just ignore yum, although I should understand why I
don't have yum on my system.

2) As for up2date, I think the e-mail is a bit missleading
since /etc/sysconfig/rhn/sources.list does not exist on my
system either. There does exist the file /etc/sysconfig/rhn/sources
(i.e. no .list in the file name). After modifying that by
adding the lines

yum fedora-core-1
http://download.fedora.redhat.com/pub/fedora/linux/core/1/i386/os
yum updates-released
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/1/i386
yum mozilla-yum-site
http://ftp.mozilla.org/pub/mozilla.org/mozilla/yum/SeaMonkey/releases/1.5/redhat/0.95

and commenting out all the other yum entries, I was able to bring
my system up to date and also install the latest version of
Mozilla (1.5). The Mozilla rpm packages were not pgp signed which
is of course bad news and I could have just downloaded a trojaned
version of mozilla. (oh well...)

I hope this info helps others out there.

Cheers. Steve.

P.S. Several times, up2date crashed while doing the updates,
but from reading the trash dumps, it looks like up2date does
not handle http errors properly. Restarting up2date and continuing
from where it left off, I'm able to get all the packages updated
and installed. So if up2date crashes, just hit the up arrow and
try again. That seems to work. (Not a good thing tho...)


On Mon, 2003-11-17 at 10:31, eric wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> hi, i haven't done it myself yet but i got this info in an email and
> thought it may be of assistance concerning fedora updates.  eric.
> 
> "Just in case people haven't bottomed out all the threads in which this
> is mentioned, the Fedora Core 1 yum (+ up2date) repositories shipped
> with FC1 are not working.  This is most likely due to a web server
> misconfiguration on fedora.redhat.com.
> 
> So you will get "File not found" errors when using the RHN applet,
> up2date, and/or yum.  You can do one of two things:
> 
> 1) EASIEST: wait until the problem is fixed (see
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=110194).  You can
> do this if you don't want to install any new software in the next 24
> hours (or however long it takes to fix the problem).  YOu can ignore any
> errors.
> 
> 2) SLIGHTLY HARDER: change your /etc/yum.conf and
> /etc/sysconfig/rhn/sources.list to these two files temporarily:
> 
> http://www.xades.com/proj/yum.conf.bugfix
> http://www.xades.com/proj/sources.bugfix
> 
> Of course, you can also perform substitutions by hand to your
> /etc/yum.conf and sources.list files; check out the above two links for
> examples."
> 
> gboyce at badbelly.com wrote:
> | On Mon, 17 Nov 2003, Stephen Adler wrote:
> |
> |
> |>Does anyone know or have some comments on how Fedora users are
> |>supposed to deal with the updates? I've heard stuff about yum,
> |>but I'm not familiar with it.
> |
> |
> | "yum update" should in theory be the method I believe.  I know that for a
> | while I was using yum install to install new packages.
> |
> | The past few days, it stopped working though with a 404 error.  It
> appears
> | they moved the repository.  They havent' released a new yum package with
> | the new path built in either, and I haven't spent enough time figuring
> out
> | the appropriate path to change it to.
> 
> 
> - --
> loki_the_doppelganger
> http://home.comcast.net/~235u/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQE/uOnSMb0VvwEIaEsRAkC9AJ9/9eOgr1PVKI8gMsDpYQCpr7NEVgCfaGnW
> 903YqvzpGefoLRi7offH6Yw=
> =T118
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss
-- 
Stephen Adler <adler at bnl.gov>





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org