FedoraProject - Changes related to "Upgrading Fedora using yum" [en]

FedUp

2013-05-23T15:21:59Z

--debuglog -> /var/log/fedup.log

Upgrading Fedora using yum/it

2013-05-19T10:15:35Z

‎Fedora 18 -> Fedora 19 (pre release branched):

Releases/Branched

2013-05-18T20:24:53Z

‎Questions and Answers: recommend mock over rpmbuild

Releases/Branched

2013-05-18T20:18:16Z

Note the empty updates repo available for convenience

Releases/Branched

2013-05-18T19:41:38Z

replace old horrible page with a new shiny one.

Show changes

Upgrading Fedora using yum/it

2013-05-18T19:12:28Z

‎Fedora 17 -> Fedora 18:

Show changes

@@ Line 68: / Line 68: @@
 # Start the upgrade prep by executing following command
-#* {{command|sudo fedup-cli --network 18 --debuglog fedupdebug.log}}
+#* {{command|sudo fedup-cli --network 18}}
-# Once the preparations have completed, check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}}
+# Once the preparations have completed, check the {{filename|/var/log/fedup.log}} file if any errors show up in the output from {{command|fedup-cli}}
 === ISO File ===
@@ Line 77: / Line 77: @@
 #* For the sake of example, we will assume that the ISO exists at {{filename|/home/user/fedora-18.iso}} but it can be anwhere in the filesystem as long as you alter the path below to reflect the actual location of the ISO.
 # Start the upgrade prep by executing the following command
-#* <nowiki>sudo fedup-cli --iso /home/user/fedora-18.iso --debuglog=fedupdebug.log</nowiki>
+#* <nowiki>sudo fedup-cli --iso /home/user/fedora-18.iso</nowiki>
-# Once the preparations have completed, check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}}
+# Once the preparations have completed, check the {{filename|/var/log/fedup.log}} file if any errors show up in the output from {{command|fedup-cli}}
 === Other Device ===

@@ Line 188: / Line 188: @@
-<pre>
+Installare la nuova chiave gpg Fedora 19 ed aggiornare:
-##Installare la nuova chiave gpg Fedora 19:
-−
-rpm --import https://fedoraproject.org/static/FB4B18E6.txt
-yum update yum
+ # rpm --import https://fedoraproject.org/static/FB4B18E6.txt
-yum --releasever=19 distro-sync --nogpgcheck
+ # yum update yum
-</pre>
+ # yum --releasever=19 distro-sync --nogpgcheck
 {{Anchor|17-18}}

@@ Line 138: / Line 138: @@
 A: No. Mixing releases like this is a very bad idea. Your better options are:
-* Obtain the src.rpm for the package you wish and try and rpmbuild --rebuild it (which may or may not work depending on dependencies)
+* Obtain the src.rpm for the package you wish and try and "mock rebuild" it (which may or may not work depending on dependencies)
 * Ask the Fedora maintainer in a bug report to update the stable version if permitted by policy.

@@ Line 108: / Line 108: @@
 Branched goes through several phases:
-The Branched compose runs every day starting at 09:15UTC. All branched builds at that time that are stable are composed and sycned out. Note that during freezes there will be many days where 0 packages are added to the compose. Branched is under "development/VERSION" on the mirrors. You can find a local "VERSION" mirror [http://mirrors.fedoraproject.org/publiclist/Fedora/VERSION/ on the public mirror list]. Compose time varies depending on number of changes but is typically between 5 and 8 hours.
+The Branched compose runs every day starting at 09:15UTC. All branched builds at that time that are stable are composed and sycned out. Note that during freezes there will be many days where 0 packages are added to the compose. Branched is under "development/VERSION" on the mirrors. You can find a local "{{FedoraVersionNumber|next}}" mirror [http://mirrors.fedoraproject.org/publiclist/Fedora/{{FedoraVersionNumber|next}}/ on the public mirror list]. Compose time varies depending on number of changes but is typically between 5 and 8 hours.
 Right after branching off from rawhide, but before alpha change freeze, Branched is much like Rawhide. All packages built the previous day are composed and synced out. Bodhi is not used yet.
-At alpha change freeze, Bodhi (the Fedora updates system) is enabled. All builds must now use it. Builds are pushed to updates-testing repository and after meeting critera for stable are added to the base package repository, which is still composed once a day. During the Alpha change freeze, only updates that fix accepted blocker bugs or freeze exceptions are allowed to go stable.
+At alpha change freeze, Bodhi (the Fedora updates system) is enabled. All builds must now use it. Builds are pushed to updates-testing repository and after meeting critera for stable are added to the base package repository, which is still composed once a day. During the Alpha change freeze, only updates that fix accepted blocker bugs or freeze exceptions are allowed to go stable. There is also an empty updates repository, so that you can leave stable updates configured during the branch period and not have to change this after the release.
 As soon as Alpha is set to "go", the Alpha change freeze is lifted and packages can once again go to the base repository when marked stable.
@@ Line 126: / Line 126: @@
 Package maintainers should read and follow the [[Updates_Policy#Branched_release|Branched release updates policy]] for building any packages in Branched.
 Branched packages are not 100% signed until the Alpha Change freeze milestone.
 == Questions and Answers ==