oh and after copying over the .rpmnew files, I get:
Error: Missing Dependency: yum >= 3.2.19 is needed by package yum-utils-1.1.16-1.fc9.noarch (updates-newkey)
Error: Missing Dependency: yum >= 3.2.19 is needed by package yum-utils-1.1.16-1.fc9.noarch (updates-newkey)
On Wed, Sep 10, 2008 at 9:32 AM, Ahmed Kamal <email.ahmedkamal@xxxxxxxxxxxxxx> wrote:
Um, just did the update now and I got:
Updating : fedora-release [ 1/10]
warning: /etc/yum.repos.d/fedora-updates.repo created as /etc/yum.repos.d/fedora-updates.repo.rpmnew
warning: /etc/yum.repos.d/fedora.repo created as /etc/yum.repos.d/fedora.repo.rpmnew
That's probably because I once edited those files. I suppose I need to copy over the .rpmnew ones onto the original ones. Would it not have made more sense in this case to overwrite the repos anywayOn Wed, Sep 10, 2008 at 9:22 AM, Warren Togami <wtogami@xxxxxxxxxx> wrote:Ralf Corsepius wrote:Yeah, LiveCD kickstart files, and ltsp-client chroot kickstart files need updating as well.
On Tue, 2008-09-09 at 23:34 -0700, Jesse Keating wrote:
In a few hours, updates for Fedora 8 and Fedora 9 will start hittingHow about mock setups?
mirrors. These updates are designed to transition users from our old
repo locations to new locations that have all our updates re-signed with
a new set of keys.
Most users will simply need to apply the offered updates, and later
apply any further updates, and verify/import the new GPG key.
The process to getting new updates is two stage.
The current default mock-configs don't know anything about the
"*.newkey" repos, nor do I see mock update-packages pending.
Ralf
Warren
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
