Anyone messing with Core3 yet?
 

Just checking to see if anyone wants to share any experiences with their install. i.e. up2date not updating.

Does the Source file need to be patched as in core2?

core3 Source file:
************************************************************************************************
### this describes the various package repos up2date will look into
### for packages. It currently supports apt-rpm repos, yum repos,
### and "dir" repos


### format is one repo entry per line, # starts comments, the
### first word on each line is the type of repo.

### the default rhn (using "default" as the url means
### use the one in the up2date config file
#up2date default

### When a channel-label is required for the non up2date repo's,
### the label is solely used as an internal identifier and is not
### based on the url or any other info from the repo.

### an apt style repo, this time arjanv's 2.6 kernel repo
### format is:
### type channel-label service:server path repo name

#apt arjan-2.6-kernel-i386 h**p://people.redhat.com ~arjanv/2.5/ kernel

### Note that for apt repos, there can be multiple repo names specified
### space seperated.

### an yum style repo
### format:
### type channel-label url

yum fedora-core-rawhide h**p://download.fedora.redhat.com/pub/fedora/linux/core/development/$ARCH/
yum-mirror fedora-core-rawhide h**p://fedora.redhat.com/download/up2date-mirrors/fedora-core-rawhide
#yum fedore-core-2-test1-updates h**p://fedora.redhat.com/updates/released/fedora-core-1
#yum-mirror fedora-core-1 h**p://fedora.redhat.com/download/up2date-mirrors/fedora-core-1
#yum-mirror updates-released h**p://fedora.redhat.com/download/up2date-mirrors/updates-released
#yum updates-testing h**p://fedora.redhat.com/updates/testing/fedora-core-$releasever
#yum-mirror updates-testing h**p://fedora.redhat.com/download/up2date-mirrors/updates-testing



### a local directory full of packages
### format
#dir my-favorite-rpms-i386-9 /var/spool/RPMS/


# multiple versions of all repos except "up2date" can be used. Deps
# can be resolved "cross-repo" if need be.
**************************************************************************************************

or, does up2date need to be updated?

Thanks.

I have mine set like you posted, but I also keep a line in for the base test distribution, in case some update might need something from there to work. I don't know if it is smart emough to look there on its own, so you might add this:

yum fedora-core-3-t1 http://download.fedora.redhat.com/pu.../2.90/i386/os/

It has been working, but there have been A LOT of updates that have had dependency issues, so you need to grab a few things at a time rather than all at once as there are some packages that it won't be able to get until they fix the dependency problems. One bad package in the bunch stops the whole set from proceeding, so there is some trial and error involved to find the bad guys out, and skip over them.

Thanks jr. I added that line, but get an error:

The applet has been unable to access the following information sources in its last attempt:
fedora-core-3-t1 h**p://download.fedora.redhat.com/p...t/2.90/i386/os/

I've started adding updates to the ignore list. 478 updates available. I'll let you know if there's any change when I finish and attempt an update on a non-dependant package.

Thank you for your suggestion.

The ignore list is a little mis-named..... It ignores those items from the number of available updates but they are still on the list and it will still will try to get them if you check the "select all" box. You need to put a check mark for other ones but not those to get it to do what you want.

I'm curious why the added line doesn't work for you..... Are you running a 386-ish machine or a 64-bit? If you are on a 386 one, then the site might have been overloaded when you tried to update. Or, maybe you didn't get the full line in because of the way this message board handles links.... It should read like this:

With 400 something updates, I would try to get 4 or 5 at a time to begin with just to see that it will work at all.

yeah. the code was displayed improperly from the board. It's late now, so I'm going home for the weekend. I'll try it on Monday. Thanks again jr.