Thanks Kevin.
I just manually verified fedora-update.repo enabled and the updates-debuginfo repository
disabled. Then executed:"yum -y update --skip-broken". The execution failed
with the message:
"Could not parse metalink
https://mirrors.fedoraproject.org/metalink?repo=updates-released-debug-f1...
error was
No repomd file
Error: File /var/cache/yum/x86_64/15/updates-debuginfo/metalink.xml does not exist"
This problem started after last night update. following a listing of the last two updates
made:
110515
Removed:
kernel.x86_64 0:2.6.38.4-20.fc15
Installed:
im-chooser.x86_64 0:1.4.2-2.fc15kernel.x86_64 0:2.6.38.6-26.rc1.fc15
Updated:
dracut.noarch 0:009-10.fc15
fedora-release.noarch 0:15-1
fedora-release-notes.noarch 0:15.0.0-1.fc15
fedora-release-rawhide.noarch 0:15-1
imsettings.x86_64 0:1.2.2-3.fc15
imsettings-gnome.x86_64 0:1.2.2-3.fc15
imsettings-libs.x86_64 0:1.2.2-3.fc15
kdelibs.x86_64 6:4.6.2-5.fc15
kdelibs-common.x86_64 6:4.6.2-5.fc15
perf.x86_64 0:2.6.38.6-26.rc1.fc15
Replaced:
im-chooser-gnome3.x86_64 0:1.4.2-1.fc15
Complete!
110514
Installed:
testdisk.x86_64 0:6.12-1.fc15
Dependency Installed:
opencv.x86_64 0:2.2.0-3.fc15
Updated:
abrt.x86_64 0:2.0.2-5.fc15
abrt-addon-ccpp.x86_64 0:2.0.2-5.fc15
abrt-addon-kerneloops.x86_64 0:2.0.2-5.fc15
abrt-addon-python.x86_64 0:2.0.2-5.fc15
abrt-desktop.x86_64 0:2.0.2-5.fc15
abrt-gui.x86_64 0:2.0.2-5.fc15
abrt-libs.x86_64 0:2.0.2-5.fc15
abrt-plugin-bugzilla.x86_64 0:2.0.2-5.fc15
abrt-plugin-logger.x86_64 0:2.0.2-5.fc15
apr-util.x86_64 0:1.3.11-2.fc15
apr-util-ldap.x86_64 0:1.3.11-2.fc15
elinks.x86_64 0:0.12-0.25.pre5.fc15
file.x86_64 0:5.07-1.fc15
file-libs.x86_64 0:5.07-1.fc15
gnome-python2-desktop.x86_64 0:2.32.0-4.fc15
gnome-python2-gnomedesktop.x86_64 0:2.32.0-4.fc15
gnome-python2-gnomekeyring.x86_64 0:2.32.0-4.fc15
gnome-python2-libwnck.x86_64 0:2.32.0-4.fc15
gnome-python2-rsvg.x86_64 0:2.32.0-4.fc15
gnome-shell-extensions-alternative-status-menu.noarch 0:3.0.1-3.03660fgit.fc15
gnome-shell-extensions-common.noarch 0:3.0.1-3.03660fgit.fc15
gstreamer.x86_64 0:0.10.33-1.fc15
gstreamer-debuginfo.x86_64 0:0.10.33-1.fc15
gstreamer-plugins-bad-free.x86_64 0:0.10.22-1.fc15
gstreamer-plugins-bad-free-extras.x86_64 0:0.10.22-1.fc15
gstreamer-plugins-base.x86_64 0:0.10.33-1.fc15
gstreamer-plugins-good.x86_64 0:0.10.29-1.fc15
gstreamer-tools.x86_64 0:0.10.33-1.fc15
gutenprint.x86_64 0:5.2.7-1.fc15
gutenprint-cups.x86_64 0:5.2.7-1.fc15
gutenprint-plugin.x86_64 0:5.2.7-1.fc15
hpijs.x86_64 1:3.11.5-1.fc15
hplip.x86_64 0:3.11.5-1.fc15
hplip-common.x86_64 0:3.11.5-1.fc15
hplip-gui.x86_64 0:3.11.5-1.fc15
hplip-libs.x86_64 0:3.11.5-1.fc15
ibus-hangul.x86_64 0:1.3.1-3.fc15
js.x86_64 1:1.8.5-4.fc15
libmodplug.x86_64 1:0.8.8.3-3.fc15
libmx.x86_64 0:1.1.12-1.fc15
libreport.x86_64 0:2.0.2-5.fc15
libreport-gtk.x86_64 0:2.0.2-5.fc15
libsane-hpaio.x86_64 0:3.11.5-1.fc15
lohit-kannada-fonts.noarch 0:2.4.6-1.fc15
microcode_ctl.x86_64 1:1.17-14.fc15
plymouth.x86_64 0:0.8.4-0.20110510.2.fc15
plymouth-core-libs.x86_64 0:0.8.4-0.20110510.2.fc15
plymouth-graphics-libs.x86_64 0:0.8.4-0.20110510.2.fc15
plymouth-plugin-label.x86_64 0:0.8.4-0.20110510.2.fc15
plymouth-plugin-two-step.x86_64 0:0.8.4-0.20110510.2.fc15
plymouth-scripts.x86_64 0:0.8.4-0.20110510.2.fc15
plymouth-system-theme.x86_64 0:0.8.4-0.20110510.2.fc15
plymouth-theme-charge.x86_64 0:0.8.4-0.20110510.2.fc15
pygtk2.x86_64 0:2.24.0-3.fc15
pygtk2-libglade.x86_64 0:2.24.0-3.fc15
quota.x86_64 1:4.00-0.12.pre1.fc15
quota-nls.noarch 1:4.00-0.12.pre1.fc15
telepathy-mission-control.x86_64 1:5.7.11-1.fc15
time.x86_64 0:1.7-39.fc15
yum.noarch 0:3.2.29-5.fc15
Replaced:
testdisk-doc.x86_64 0:6.11-9.fc15
Complete!
Regards,
Manny
----- "Kevin Fenzi" <kevin(a)scrye.com> wrote:
On Mon, 16 May 2011 13:00:01 -0400 (EDT)
ergodic <gmml(a)embarqmail.com> wrote:
> Interesting. My since alpha came out I have had in
/etc/yum/repos.d
> fedora-update.repo enabled and the updates-debuginfo repository
> disabled.
That would have to have been done manually. :)
The config is:
- at branch time: enable updates-testing, disable updates.
- at very very close to release time (this time it was a few days
ago):
enable updates, disable updates-testing.
If you have updated in the last few days you should have the final
fedora-release that has updates enabled and updates-testing disabled.
You can of course change those, or if you did change them at some
point, you probibly have .rpmnew files with the default config.
There was an issue with debuginfo repos. They were not created for
'updates'. Hopefully they will be soon and will be next cycle.
Updates should start populating with 0 day updates as soon as the
"go"
decision is made for release.
kevin
--
test mailing list
test(a)lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test