Update all the way to Fedora 9

[msrinath80]

Hi folks,

I'm a new Fedora user. If I install the latest preview release of Fedora 9 and continue to keep installing the updates as they are dispatched, will I eventually end up with the same packages as Fedora 9 once it is released?

My apologies if I have not searched the forums properly and this question has been addressed elsewhere.

Thanks!

[SlowJet]

yes, but do a yum update first thing after firstboot install, then configure, relabel on reboot.

SJ

[msrinath80]

yes, but do a yum update first thing after firstboot install, then configure, relabel on reboot.

SJ

Hi,

I got the first two parts of what you said. What does 'relabel on reboot' mean?

[Perpetual]

yes, but do a yum update first thing after firstboot install, then configure, relabel on reboot.

SJ

Sorry to step-in but I wondered what you mean by relabel?

[SlowJet]

Do this before the the yum update
#setenforce 0

Do this after the yum update to relabel the SELinux contexts.

#touch /.autorelabel
#reboot

Then configure things
and do a final reboot

SJ

[msrinath80]

Thanks SlowJet!

[ShivaS]

Why is this relabeling required?

[SlowJet]

Because x 7.3 and gdm needed changes.
Relabeling is not a major issue. It is part of SELinux.
Since SELinux is always changing, the policy is changing, the rpm are in error or an error from last time is being fixed, or SELinux is in error, .... the yum update need to be less strick on the execution.
Hence setenfore 0
touch /.autorelabel

setenforce 1 is implied as the SELinux control files is what gets used at boot time.

Also, do not use the gui updater as there is an unsigned package from rawhide that the new updates repo will stop. In yum you can just reply y to accept it.

Lastly, do NOT mess with the repos and insure that the rawhide development repo is enable=0 after the yum updates. The normal fedora repos will be used and the mirror manager will redirect to rawhide until the release switch is thrown.

SJ

[Murrquan]

Okay ... so once Fedora 9 goes into production, what you do is open a terminal, type

#setenforce 0
#yum update
#touch /.autorelabel
#reboot

in order, then restart your system and type some command to set the rawhide development repo to disabled? Sorry, very non-technically savvy Fedora user here, just trying to make sure I've got everything straight.

[SlowJet]

Okay ... so once Fedora 9 goes into production, what you do is open a terminal, type

#setenforce 0
#yum update
#touch /.autorelabel
#reboot

in order, then restart your system and type some command to set the rawhide development repo to disabled? Sorry, very non-technically savvy Fedora user here, just trying to make sure I've got everything straight.

The thread is about updating Alpha,Beta, pre F9 to a state where it can then be updated into the Final release with yum.

However, your command list is what I use every time I do a yum update because it is no fun cleaning up failed yum updates or doing it 2 or 3 times to get it done.

At this point,, I would avise waiting for the release.
I'm doing an online install now and it has been running for 12 hrs. with 200 packages to go.
So it is not worth the effort.

SJ

[ryptyde]

I have installed F9 Preview using a LiveCD to a laptop and have been using the default updater and haven't experienced any "show stoppers". The switch from rawhide.repo to the fedora.repo has already taken place this past week. I did not have to manually edit the yum.repos.d as the changes were automatically set via the updates. So I am expecting a smooth transition from preview to final. :)

[SlowJet]

I have installed F9 Preview using a LiveCD to a laptop and have been using the default updater and haven't experienced any "show stoppers". The switch from rawhide.repo to the fedora.repo has already taken place this past week. I did not have to manually edit the yum.repos.d as the changes were automatically set via the updates. So I am expecting a smooth transition from preview to final. :)


Yes, that's the theme.
How did you get past the unsigned package?

SJ

[ryptyde]

Yes, that's the theme.
How did you get past the unsigned package?

SJ

What package would have been unsigned? I don't recall seeing any alerts during update.
I have a desktop with F9 preview installed and haven't updated it lately so I'll run the updater and see
if it throws a "unsigned package" flag. :confused:

[SlowJet]

from the 27th updates

https://www.redhat.com/archives/fedora-devel-list/2008-April/msg02069.html

gnome-settings-daemon-2.22.1-0.2008.03.26.7.fc9
-----------------------------------------------
* Fri Apr 25 2008 Soren Sandmann <sandmann redhat com> - 2.22.1-2008.03.26.7
- Integrate various fixes from other distributions. Remove xrandr-missingok
patch.

Thread to fix it.
http://forums.fedoraforum.org/showthread.php?t=187088

yum --nogpgcheck update gnome-settings-daemon


The key for the new repo is the reply y from above post.

I think that covers eveything? :)
SJ

[Murrquan]

from the 27th updates

https://www.redhat.com/archives/fedora-devel-list/2008-April/msg02069.html

gnome-settings-daemon-2.22.1-0.2008.03.26.7.fc9
-----------------------------------------------
* Fri Apr 25 2008 Soren Sandmann <sandmann redhat com> - 2.22.1-2008.03.26.7
- Integrate various fixes from other distributions. Remove xrandr-missingok
patch.

Thread to fix it.
http://forums.fedoraforum.org/showthread.php?t=187088

yum --nogpgcheck update gnome-settings-daemon


The key for the new repo is the reply y from above post.

I think that covers eveything? :)
SJ

So we have to type that in manually to update every time? x_X What about installing third-party RPMs? I couldn't install Adobe Reader because the package manager got stuck on checking the signature (I think).

[SlowJet]

I do this every time on regular updates for reasons explained above.
So I need to use cli and yum to do it.

#setenforce 0
#yum update
#touch /.autorelabel
#reboot


If you are referring to the yum --nogpgcheck update, then no, never do it unless you know where it came from and the reason for being unsigned is legit.

rpm's need a key just like they were coming from a repo. See man rpm

DIGITAL SIGNATURE AND DIGEST VERIFICATION
The general forms of rpm digital signature commands are

rpm --import PUBKEY ...

rpm {--checksig} [--nosignature] [--nodigest]
PACKAGE_FILE ...

The --checksig option checks all the digests and signatures contained
in PACKAGE_FILE to ensure the integrity and origin of the package. Note
that signatures are now verified whenever a package is read, and
--checksig is useful to verify all of the digests and signatures asso-
ciated with a package.

SJ

[_Chipwiz_Ben_]

Before reading this thread, I got the error about the unsigned package thing - thought nothing of it, so left it. I tried updating again in a couple of days (F9 is on a laptop I don't use much) and it went through fine, no problems. I've just checked now, and it's using the Fedora repo and the Rawhide one is unchecked. I run with SELinux in permissive mode anyway because it drives me insane if I don't, so perhaps that could explain it, but it wouldn't explain why it wouldn't work one day then did a few days after. So there is a chance that ryptyde didn't see any error at all, like myself the second time.

Ben

[SlowJet]

"Before reading this thread, I got the error about the unsigned package thing - thought nothing of it, so left it. "

By using yum --nogpgcheck update

"I tried updating again in a couple of days (F9 is on a laptop I don't use much) and it went through fine, no problems. I've just checked now, and it's using the Fedora repo and the Rawhide one is unchecked."

And the first time you use those fedora repos. you will need to accept the repo key with a y.

SELinx has nothing to do with the key error, or the new repo keys, or the bug in the new gui updater that will not handle key type messages.
setenforce 0 before a yum update is only a pre cation to lower the chances of the yum update process failure due to the several variables mentioned above..

SJ