up2date and yum probelms

[phillip]

Having some strange problems with both in fc4. got past the gdm issue, but now my up2date and yum do not work properly.
Up2date will start, see over 300 updates available, but when i select them, they are all 0 bytes and when selected will not allow me to click forward. Selecting all packages only selects the first package, which still doesnt let me click forward. Reading other posts, i have managed to update things one at a time using up2date "updatename" --nosig but dont fancy doing this 300 times! Is there a console command to update them all? or is there a way to fix my up2date? The only channel it uses is development.

As for yum, i downloaded the yum.conf from the fedora faq thinking that would solve my problems but no good.Below is my error message
Cannot open/read repomd.xml file for repository: updates-testing
failure: repodata/repomd.xml from updates-testing: [Errno 256] No more mirrors to try.

and just to be thorough, here is my yum. thanks for any help,im still a noob :)

[main]
cachedir=/var/cache/yum
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=redhat-release
tolerant=1
exactarch=1

# Added this because some mirrors go down and then retying takes forever.
retries=1
obsoletes=1
gpgcheck=0
##################
## Basic Fedora ##
##################

[base]
name=Fedora Core $releasever - $basearch - Base
baseurl=http://mirror.hiwaay.net/redhat/fedora/linux/core/$releasever/$basearch/os
http://rpmfind.net/linux/fedora/core/$releasever/$basearch/os
http://mirror.clarkson.edu/pub/distributions/fedora/linux/core/$releasever/$basearch/os
http://mirrors.usc.edu/pub/linux/fedora/fedora/fedora/$releasever/$basearch/RPMS.os
# http://fedora.redhat.com/releases/fedora-core-$releasever
#gpgcheck=1

#[base-debuginfo]
#name=Fedora Core $releasever - $basearch - Debug Info
#baseurl=http://speakeasy.rpmfind.net/linux/fedora/core/$releasever/$basearch/debug
# http://distro.ibiblio.org/pub/linux/distributions/fedora/linux/core/$releasever/$basearch/debug
# http://mirror.clarkson.edu/pub/distributions/fedora/linux/core/$releasever/$basearch/debug
# http://gulus.usherbrooke.ca/pub/distro/fedora/linux/core/$releasever/$basearch/debug
##gpgcheck=1

[updates-released]
name=Fedora Core $releasever - $basearch - Released Updates
baseurl=http://ftp.ens.utulsa.edu/pub/linux/fedora/core/updates/$releasever/$basearch
http://rpmfind.net/linux/fedora/core/updates/$releasever/$basearch
http://mirror.clarkson.edu/pub/distributions/fedora/linux/core/updates/$releasever/$basearch
http://mirrors.usc.edu/pub/linux/fedora/fedora/fedora/$releasever/$basearch/RPMS.updates
# http://fedora.redhat.com/updates/released/fedora-core-$releasever
#gpgcheck=1

[updates-testing]
name=Fedora Core $releasever - $basearch - Unreleased Updates
baseurl=http://mirrors.usc.edu/pub/linux/fedora/fedora/fedora/$releasever/$basearch/yum/updates-testing
http://distro.ibiblio.org/pub/linux/distributions/fedora/linux/core/updates/testing/$releasever/$basearch
http://mirror.clarkson.edu/pub/distributions/fedora/linux/core/updates/testing/$releasever/$basearch
http://gulus.usherbrooke.ca/pub/distro/fedora/linux/core/updates/testing/$releasever/$basearch
http://fedora.redhat.com/updates/testing/fedora-core-$releasever
#gpgcheck=1

###################
## Fedora Extras ##
###################


###############
## Livna.org ##
###############

[livna-stable]
name=Livna.org Fedora Compatible Packages (stable)
baseurl=http://rpm.livna.org/fedora/$releasever/$basearch/RPMS.stable
http://livna.cat.pdx.edu/fedora/$releasever/$basearch/RPMS.stable
#gpgcheck=1


[livna-unstable]
name=Livna.org - Fedora Compatible Packages (unstable)
baseurl=http://rpm.livna.org/fedora/$releasever/$basearch/RPMS.unstable
http://livna.cat.pdx.edu/fedora/$releasever/$basearch/RPMS.unstable
#gpgcheck=1

[livna-testing]
name=Livna.org - Fedora Compatible Packages (testing)
baseurl=http://rpm.livna.org/fedora/$releasever/$basearch/RPMS.testing
http://livna.cat.pdx.edu/fedora/$releasever/$basearch/RPMS.testing
#gpgcheck=1

############
# Jpackage #
############

# JPackage is a GREAT repository for Java Software.
# However, you may have to compile some SRPMs to use it,
# so it's commented out by default. See
# <http://prdownloads.sourceforge.net/jpackage/direct_download/1.5/generic/SRPMS.non-free>
# For the SRPMs, and <http://www.jpackage.org> for the general details.
#
# Note: JPackage IS compatible with the fedora.us repositories.
# You can use JPackage and fedora.us at the same time, without
# any trouble.

#[jpackage-generic]
#name=JPackage Cross-Platform Packages
#baseurl=http://aleron.dl.sourceforge.net/sourceforge/jpackage/direct_download/1.5/generic/free
# http://heanet.dl.sourceforge.net/sourceforge/jpackage/direct_download/1.5/generic/free
# http://umn.dl.sourceforge.net/sourceforge/jpackage/direct_download/1.5/generic/free
#failovermethod=priority
##gpgcheck=1

#[jpackage-fedora]
#name=JPackage Fedora Packages
#baseurl=http://aleron.dl.sourceforge.net/sourceforge/jpackage/direct_download/1.5/fedora-$releasever/free
# http://heanet.dl.sourceforge.net/sourceforge/jpackage/direct_download/1.5/fedora-$releasever/free
# http://umn.dl.sourceforge.net/sourceforge/jpackage/direct_download/1.5/fedora-$releasever/free
#failovermethod=priority
##gpgcheck=1

############################
## Alternate Repositories ##
############################

# Uncomment these to use them -- note that some packages
# from these repositories may conflict with the fedora.us
# packages. If you use these repositories, you may wish to
# comment-out the fedora.us and livna.org repositories.

[freshrpms]
name=FreshRPMs
baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/freshrpms/
http://ftp.us2.freshrpms.net/linux/freshrpms/ayo/fedora/linux/$releasever/$basearch/freshrpms/
gpgcheck=1

#[dag]
#name=Dag APT Repository
#baseurl=http://dag.freshrpms.net/fedora/$releasever/en/$basearch/dag
# http://dag.atrpms.net/fedora/$releasever/en/$basearch/dag/
# http://ftp.heanet.ie/pub/freshrpms/pub/dag/fedora/$releasever/en/$basearch/dag
##gpgcheck=1

#[dries]
#name=Dries APT/YUM Repository
#baseurl=http://dries.studentenweb.org/yum/fedora/linux/$releasever/$basearch/dries
##gpgcheck=1

#[spc-production]
#name=Subpop.net (Production)
#baseurl=http://rpms.subpop.net/fedora/linux/$releasever/$basearch/production
##gpgcheck=1

[newrpms]
name=NewRPMs
baseurl=http://newrpms.sunsite.dk/apt/redhat/en/$basearch/fc$releasever
http://newrpms.atrpms.net/apt/redhat/en/$basearch/fc$releasever
gpgcheck=1

#[atrpms-stable]
#name=ATrpms - Stable (Most Stable)
#baseurl=http://apt.physik.fu-berlin.de/fedora/$releasever/en/$basearch/at-stable
# http://ftp-stud.fht-esslingen.de/atrpms/download.atrpms.net/fedora/$releasever/en/$basearch/at-stable
# http://wftp.tu-chemnitz.de/pub/linux/ATrpms/fedora/$releasever/en/$basearch/at-stable
##gpgcheck=1

#[atrpms-good]
#name=ATrpms - Good (2nd Most Stable)
#baseurl=http://ftp-stud.fht-esslingen.de/atrpms/download.atrpms.net/fedora/$releasever/en/$basearch/at-good
# http://apt.physik.fu-berlin.de/fedora/$releasever/en/$basearch/at-good
# http://wftp.tu-chemnitz.de/pub/linux/ATrpms/fedora/$releasever/en/$basearch/at-good
##gpgcheck=1

#[atrpms-testing]
#name=ATrpms - Testing (3rd Most Stable)
#baseurl=http://wftp.tu-chemnitz.de/pub/linux/ATrpms/fedora/$releasever/en/$basearch/at-testing
# http://apt.physik.fu-berlin.de/fedora/$releasever/en/$basearch/at-testing
# http://ftp-stud.fht-esslingen.de/atrpms/download.atrpms.net/fedora/$releasever/en/$basearch/at-testing
##gpgcheck=1

#[atrpms-bleeding]
#name=ATrpms - Bleeding (Least Stable)
#baseurl=http://apt.physik.fu-berlin.de/fedora/$releasever/en/$basearch/at-bleeding
# http://ftp-stud.fht-esslingen.de/atrpms/download.atrpms.net/fedora/$releasever/en/$basearch/at-bleeding
# http://wftp.tu-chemnitz.de/pub/linux/ATrpms/fedora/$releasever/en/$basearch/at-bleeding
##gpgcheck=1

###################
## Miscellaneous ##
###################

[macromedia.mplug.org]
name=macromedia.mplug.org - Flash Plugin
baseurl=http://macromedia.mplug.org/apt/fedora/$releasever
http://sluglug.ucsc.edu/macromedia/apt/fedora/$releasever
http://ruslug.rutgers.edu/macromedia/apt/fedora/$releasever
http://macromedia.rediris.es/apt/fedora/$releasever
#gpgcheck=1

[foolish]

If you're using FC4 test1 you can't use this yum.conf, as it's configured for Core 3 only.

[phillip]

and can someone be so helpful as to post one for fc4?
thanking you
phill

[foolish]

FC4 isn't out yet, you're using a test release. You have to undestand what a test release is to use one. Here's the short version: It will eat all the cheese in your house!

You see, the fedora development process includes releasing early test-releases, that are filled with bugs and sometimes doesn't work at all, this to allow developers and testers to more efficiently test the upcoming release. There are tree test releases, each representing a level of progress in the development process. We're currently at test1, which means pretty much everything is broken.

Do not use test releases for any other purpose than to test and report on bugs. Test releases are not to be used as your primary workstation, as they will crash and behave weirdly.

As test releases are intended for testers and developers only, there are no third party repositories for test releases. If you want something that works, something that's usable, use a stable Core release. The current stable core release is Core 3.

[phillip]

I only use it for recreation, had just been trying to get it working.thanks anyway

[jrittvo]

The problems you are having with up2date are a reported bug in the current test release. Sooner or later they will fix it.

As noted above, the repositories in your yum.conf are all for FC3. The repo for the running test version is should be something like this (I don't use yum but I think this will work) :

[Rawhide]
name=Fedora Development - Rawhide
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386
gpgcheck=1

Make this the only repo listing in your yum.conf by pasting it in and commenting the other ones out with # at the beginning of each line.

You might need to play with the gpgcheck=1 setting because rawhide packages are usually not signed, so it might need to be gpgcheck=0 instead?

Also, as noted above, getting your feet wet with a testing version is not a great idea. There are a few broken things at any given point in time in these packages.

[jery_wang2002]

Having some strange problems with both in fc4. got past the gdm issue, but now my up2date and yum do not work properly.
Up2date will start, see over 300 updates available, but when i select them, they are all 0 bytes and when selected will not allow me to click forward. Selecting all packages only selects the first package, which still doesnt let me click forward. Reading other posts, i have managed to update things one at a time using up2date "updatename" --nosig but dont fancy doing this 300 times! Is there a console command to update them all? or is there a way to fix my up2date? The only channel it uses is development.


Yes, I encountered the same problem like the above using FC4 TEst 2 I downloaded (4 CDs) and install them yesterday.

I finally resort to command line:

yum update

But here, I have different problem where it complains that some packages do not have signature/key and it just stops.



As for yum, i downloaded the yum.conf from the fedora faq thinking that would solve my problems but no good.Below is my error message
Cannot open/read repomd.xml file for repository: updates-testing
failure: repodata/repomd.xml from updates-testing: [Errno 256] No more mirrors to try.

and just to be thorough, here is my yum.

I had that problem too.

[plsclickme]

i got this work by edit the /etc/yum.conf

$su
$gedit /etc/yum.conf

look for the line: -
gpgcheck
change the value "1" to "0"

if you still encounter some other problem, try patching the latest kernel first, then only yum update the rest.

hope this help for the time being

[gmike]

[root@mikel ~]# yum check-update
Traceback (most recent call last):
File "/usr/bin/yum", line 22, in ?
import yummain
ImportError: Bad magic number in /usr/share/yum/yummain.pyc
[root@mikel ~]#

i recieved this error trying yum my way around fedora t2. i have also edited ''gpgcheck'' from 1 to 0 with different result

[flebber]

i got this work by edit the /etc/yum.conf

$su
$gedit /etc/yum.conf

look for the line: -
gpgcheck
change the value "1" to "0"

if you still encounter some other problem, try patching the latest kernel first, then only yum update the rest.

hope this help for the time being

If i change gpgcheck to =0 in yum.conf then do update it will state that ¨No Packages marked for Update/Obsoletion¨

if it is at gpgcheck=1 it will see the updates but will download the packages but end with ¨unsigned package initscripts-8.08-2.i386.rpm¨......and as known up2date all updates show as 0kb in up2date..

[flebber]

[Rawhide]
name=Fedora Development - Rawhide
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386
gpgcheck=1

Make this the only repo listing in your yum.conf by pasting it in and commenting the other ones out with # at the beginning of each line.



I have inserted this in to my yum.conf haven commented out existing at moment and it appears to be allowing me to update with gpg=1

And it worked for me i have been able to successfully update :)

[Finalzone]

Add this line "enabled=1". It allows to enable (1) or disable (0) the repository.

[badsykes]

any way to update my system....I can't listen to a banal mp3 when i install all this stuff..I want to update the up2date program myself and i get an error.I think the update protocol is critical because u can correct some bugs by downloading new versions

[mad_pheonix]

I've had moderate success using the FC3 repositories. You can use the yum.conf posted on the forum (like in the first post on this thread) as long as you change $releasever to 3. The problem I found was that when it was trying to look those repo's up it was using version 3.91, whereas repositories generally just have folders for FC 1, 2, and 3. Some other repositories have testing branches too. Good luck.

[Ug]

I've had moderate success using the FC3 repositories.
You shouldn't be using any FC3 repositories with the FC4 Test edition. It defeats the entire objective of testing FC4T2. Your not supposed to be looking for compatibility with FC3 packages...