| Line 78: | Line 78: | ||
| [[User: satellit|satellit]] | | [[User: satellit|satellit]] | ||
| Tested fedup/0.9.2/1.fc21/noarch/fedup-0.9.2-1.fc21.noarch.rpm on Fedora workstation-netinstall 21 (Virtualbox 15GB HD) (x86_64). Met {{bz|1209941}} <ref>firefox is mistagged as f21: http://wiki.sugarlabs.org/go/File:Dnf_update.JPG</ref> | | Tested fedup/0.9.2/1.fc21/noarch/fedup-0.9.2-1.fc21.noarch.rpm on Fedora workstation-netinstall 21 (Virtualbox 15GB HD) (x86_64). Met {{bz|1209941}} <ref>firefox is mistagged as f21: http://wiki.sugarlabs.org/go/File:Dnf_update.JPG</ref> | ||
|- | |||
| [[User: satellit|satellit]] | |||
| Tested Fedup_0.9.1-1.fc21 on Fedora workstation-netinstall 21 (Virtualbox 15GB HD) (x86_64). Met {{bz|1209941}} <ref>http://wiki.sugarlabs.org/go/File:Fedup_0.9.1-1.fc21.JPG</ref> | |||
|} | |} | ||
<references/> | <references/> | ||
[[Category:Fedora 22 Test Days]] | [[Category:Fedora 22 Test Days]] | ||
Revision as of 23:14, 21 April 2015
| Fedora Test Days | |
|---|---|
| |
| FedUp | |
| Date | 2015-04-21 |
| Time | all day |
| Website | QA/Fedora_22_test_days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
Today's instalment of Fedora Test Day will focus on FedUp, the Fedora system upgrade tool.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Will Woods (wwoods)
- Quality Assurance - Adam Williamson (adamw), Petr Schindl (pschindl)
Prerequisite for Test Day
A system with Fedora 20 or 21 you can use for test purposes (i.e. you don't mind if it all goes wrong and you lose the system)! Testing with a virtual machine will be useful for many cases, and will let you run multiple tests easily.
How to test?
The test procedure is simply to take a Fedora 20 or Fedora 21 installation and upgrade it to Fedora 22. To ensure you get the latest fedup for testing, run one of these two commands (depending on whether it's already installed):
yum --enablerepo=updates-testing install fedup yum --enablerepo=updates-testing update fedup
The newest build of fedup - 0.9.2-1 - was pushed to the mirrors only recently. The above command should install it, but please make sure that fedup-0.9.2-1 is installed after running it. If you got an older version (perhaps because of a mirror that has not yet synced) please download and install the updated version directly:
- fedup-0.9.2-1.fc20.noarch.rpm (Fedora 20)
- fedup-0.9.2-1.fc21.noarch.rpm (Fedora 21)
To upgrade, run (F21):
fedup --network 22 --instrepo https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC3/Server/(arch)/os
or (F20):
fedup --network 22 --product (product) --instrepo https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC3/Server/(arch)/os
where (arch) is the appropriate architecture (armhfp, x86_64, or i386) and (product) is the most appropriate 'product' for the install - see this note.
The idea is to test upgrades from as many different starting situations as possible - particularly with different package sets, languages, keyboard layouts, and storage configurations.
If the upgrade completes successfully, test the upgraded system to ensure it works correctly.
Test Results
If any of your upgrades fails (or leads to a broken system), report a bug to Bugzilla. The correct component will depend on the exact nature of the bug - ask in IRC if you're unsure. If you can't find out what component to file against, file the bug against usually for the component fedup. Include any useful details about the system's configuration, and note that your result is part of this Test Day and mention that you followed the instructions on this page.
If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. In the 'Results' column, you can link to bug reports of any failed tests, and very briefly summarize your results. Please don't post long comments here, it will make the table hard to read: anything longer than a few words is likely fodder for a bug report, or mailing list post, or you can use <ref>comment</ref> to make the comment appear as a footnote below the table.
| User | Results |
|---|---|
| Sample User | 2 pass 2 fail, RHBZ #12345 RHBZ #54321 |
| Petr Schindler | tested UEFI/BIOS, encrypted/non-encrypted, Server/Workstation 21, works fine - found RHBZ #1213868, met RHBZ #1209941 |
| langdon | tested UEFI, encrypted, Workstation 21, works fine - met RHBZ #1209941 and attached screenshot, although evo-data-server just threw an error |
| Matthew Bunt | tested UEFI, non-encrypted, Workstation 21, real install with many packages. Found RHBZ #1209941 but upgrade was successful |
| juliuxpigface | Tested FedUp (version 0.9.0) on Fedora 'Non-Product' 21 (x86_64). Met RHBZ #1209941, but after ctrl+alt+del everything worked. |
| satellit | Tested fedup/0.9.2/1.fc21/noarch/fedup-0.9.2-1.fc21.noarch.rpm on Fedora workstation-netinstall 21 (Virtualbox 15GB HD) (x86_64). Met RHBZ #1209941 [1] |
| satellit | Tested Fedup_0.9.1-1.fc21 on Fedora workstation-netinstall 21 (Virtualbox 15GB HD) (x86_64). Met RHBZ #1209941 [2] |
- ↑ firefox is mistagged as f21: http://wiki.sugarlabs.org/go/File:Dnf_update.JPG
- ↑ http://wiki.sugarlabs.org/go/File:Fedup_0.9.1-1.fc21.JPG
