The current version of the page includes hardcoded, obsolete references
to e.g. Fedora 28, 30, and 31, which can be confusing.
Replace references with attributes, and add a new one, `{NEXTNEXTVER}`
for the branched example.
Signed-off-by: Michel Alexandre Salim <salimma@fedoraproject.org>
This is now the second time when rpmconf reverted me
google-chrome-stable.repo file back to version where I have `enabled=0`.
It looks like this package generates the repo file in the post scriplet
and does not mention it in the list of installed files, this probably
tricks rpmconf to do an incorrect action. I would love to investigate
further and maybe file a bug for chrome/chromium, but now that I
finished my upgrade I can't look back why rpmconf thought this file
needs updating - scriplet looks like this:
YUM_REPO_FILE="/etc/yum.repos.d/google-chrome.repo"
install_yum() {
install_rpm_key
if [ ! "$REPOCONFIG" ]; then
return 0
fi
if [ -d "/etc/yum.repos.d" ]; then
cat > "$YUM_REPO_FILE" << REPOCONTENT
[google-chrome]
name=google-chrome
baseurl=$REPOCONFIG/$DEFAULT_ARCH
enabled=1
gpgcheck=1
gpgkey=https://dl.google.com/linux/linux_signing_key.pub
REPOCONTENT
fi
}
It was likely some older version of the package. Anyway, I thought I'd
drop a warning note for others, because I accidentally disabled this
repo which left my Chrome on an old version for about a year until it
websites started warning me about an unsupported version. This is
dangerous, my main browser is Firefox but this could be a security
problem for others.
Use "reboot" consistently, emphasize the immediate no-prompt reboot, mention it's a console terminal, then a second reboot, and clean up step 6 language. This fixes issue #294 and I think is an improvement.
This is a personal preference, but the `fixfiles` command is a
convenient binary in Fedora that ships with SELinux to handle relabels.
It does the same thing, but note the use of the `-B` flag.
From the man pages:
> -B:
> If specified with onboot, this fixfiles will record the current date
> in the /.autorelabel file, so that it can be used later to speed up
> labeling. If used with restore, the restore will only affect files
> that were modified today.
I thought I would share this improvement upstream since I use this page
often, but I prefer this way of running more lean SELinux checks.
Signed-off-by: Justin W. Flory <git@jwf.io>
Add information on cleaning old symlinks in /usr in dnf-system-upgrade.adoc.
Fedora includes the symlinks utility, so it is easy to clean the old cruft.
Add information on cleaning old symlinks in /usr in dnf-system-upgrade.adoc.
Fedora includes the symlinks utility, so it is easy to clean the old cruft.
* Remove the unreviewed wiki content admonintion
* Remove unnecessary DNF arguments
* Remove references to 'Atomic Host' and replace with Fedora CoreOS and Fedora Silverblue
