Difference between revisions of "Migrating from ROSA Desktop Fresh R3 to R4"
From Rosalab Wiki
m |
(separate 32/64bit sections) |
||
| Line 1: | Line 1: | ||
| − | ROSA Desktop Fresh R4 uses repositories different from the ones of Fresh R1/R2/R3, so your R3 system will not be updated automatically to R4 by means of usual updates. In order to perform such distribution upgrade, one should do the | + | {{Note|Updating from Desktop Fresh R3 to Desktop Fresh R4 is possible but can take significant time (from several hours to a day). When possible, we recommend to install Desktop Fresh R4 from installation media instead of R3 with reuse of /home and other folders located on separate partitions. |
| + | }} | ||
| + | |||
| + | ROSA Desktop Fresh R4 uses repositories different from the ones of Fresh R1/R2/R3, so your R3 system will not be updated automatically to R4 by means of usual updates. In order to perform such distribution upgrade, one should do the steps described below. | ||
| + | = 32bit systems= | ||
* update the system to the latest R3 state: | * update the system to the latest R3 state: | ||
| Line 12: | Line 16: | ||
* add release repositories of Fresh R4: | * add release repositories of Fresh R4: | ||
| − | |||
# urpmi.addmedia --distrib http://mirror.rosalab.ru/rosa/rosa2014.1/repository/i586/ | # urpmi.addmedia --distrib http://mirror.rosalab.ru/rosa/rosa2014.1/repository/i586/ | ||
# urpmi.update --ignore updates | # urpmi.update --ignore updates | ||
| − | ** | + | |
| + | Note that we have disabled "updates" repositories for now, since we only tested update to release repositories of Desktop Fresh R4. | ||
| + | |||
| + | * update all packages to R4 state; preliminary download all necessary packages (the latter is important, since the network connection can go down during update): | ||
| + | |||
| + | # urpmi --no-install --auto-update --auto | ||
| + | # urpmi --auto-update --auto | ||
| + | |||
| + | Note that depending on Internet connection speed and number of packages installed in the system, the update time may vary significantly. Average update time is about several hours. In some very special cases update can take about a day or even more. | ||
| + | |||
| + | * Turn back repositories with R4 updates and update your system to be sure that it is up to date: | ||
| + | # urpmi.update --no-ignore updates | ||
| + | # urpmi --auto-update --auto | ||
| + | |||
| + | = 64bit systems= | ||
| + | |||
| + | * update the system to the latest R3 state: | ||
| + | |||
| + | # urpmi --auto-update | ||
| + | |||
| + | (in order to guarantee that we have the latest versions of all packages; update from Fresh R1 or R2 to R4 directly is theoretically possible, but we didn't test this scenario thoroughly). | ||
| + | |||
| + | * remove all Fresh R3 repositories. If you don't have any repositories except official ROSA Desktop Fresh R3 ones, then you can simply remove all software sources: | ||
| + | |||
| + | # urpmi.removemedia -a | ||
| + | |||
| + | * add release repositories of Fresh R4: | ||
# urpmi.addmedia --distrib http://mirror.rosalab.ru/rosa/rosa2014.1/repository/x86_64/ | # urpmi.addmedia --distrib http://mirror.rosalab.ru/rosa/rosa2014.1/repository/x86_64/ | ||
# urpmi.addmedia main32_release http://mirror.rosalab.ru/rosa/rosa2014.1/repository/i586/main/release | # urpmi.addmedia main32_release http://mirror.rosalab.ru/rosa/rosa2014.1/repository/i586/main/release | ||
| Line 21: | Line 50: | ||
# urpmi.update --ignore updates | # urpmi.update --ignore updates | ||
| − | + | 32bit main/release and main/updates repositories are necessary in 64bit systems in order to make 32bit-only applications such as Skype available. Note that we have disabled "updates" repositories for now, since we only tested update to release repositories of Desktop Fresh R4. | |
* update all packages to R4 state; preliminary download all necessary packages (the latter is important, since the network connection can go down during update): | * update all packages to R4 state; preliminary download all necessary packages (the latter is important, since the network connection can go down during update): | ||
| Line 33: | Line 62: | ||
# urpmi.update --no-ignore updates | # urpmi.update --no-ignore updates | ||
# urpmi --auto-update --auto | # urpmi --auto-update --auto | ||
| + | |||
[[ru:Миграция_с_ROSA_Desktop_Fresh_R3_на_R4]] | [[ru:Миграция_с_ROSA_Desktop_Fresh_R3_на_R4]] | ||
Revision as of 09:33, 1 October 2014
Note
Updating from Desktop Fresh R3 to Desktop Fresh R4 is possible but can take significant time (from several hours to a day). When possible, we recommend to install Desktop Fresh R4 from installation media instead of R3 with reuse of /home and other folders located on separate partitions.
Updating from Desktop Fresh R3 to Desktop Fresh R4 is possible but can take significant time (from several hours to a day). When possible, we recommend to install Desktop Fresh R4 from installation media instead of R3 with reuse of /home and other folders located on separate partitions.
ROSA Desktop Fresh R4 uses repositories different from the ones of Fresh R1/R2/R3, so your R3 system will not be updated automatically to R4 by means of usual updates. In order to perform such distribution upgrade, one should do the steps described below.
32bit systems
- update the system to the latest R3 state:
# urpmi --auto-update
(in order to guarantee that we have the latest versions of all packages; update from Fresh R1 or R2 to R4 directly is theoretically possible, but we didn't test this scenario thoroughly).
- remove all Fresh R3 repositories. If you don't have any repositories except official ROSA Desktop Fresh R3 ones, then you can simply remove all software sources:
# urpmi.removemedia -a
- add release repositories of Fresh R4:
# urpmi.addmedia --distrib http://mirror.rosalab.ru/rosa/rosa2014.1/repository/i586/ # urpmi.update --ignore updates
Note that we have disabled "updates" repositories for now, since we only tested update to release repositories of Desktop Fresh R4.
- update all packages to R4 state; preliminary download all necessary packages (the latter is important, since the network connection can go down during update):
# urpmi --no-install --auto-update --auto # urpmi --auto-update --auto
Note that depending on Internet connection speed and number of packages installed in the system, the update time may vary significantly. Average update time is about several hours. In some very special cases update can take about a day or even more.
- Turn back repositories with R4 updates and update your system to be sure that it is up to date:
# urpmi.update --no-ignore updates # urpmi --auto-update --auto
64bit systems
- update the system to the latest R3 state:
# urpmi --auto-update
(in order to guarantee that we have the latest versions of all packages; update from Fresh R1 or R2 to R4 directly is theoretically possible, but we didn't test this scenario thoroughly).
- remove all Fresh R3 repositories. If you don't have any repositories except official ROSA Desktop Fresh R3 ones, then you can simply remove all software sources:
# urpmi.removemedia -a
- add release repositories of Fresh R4:
# urpmi.addmedia --distrib http://mirror.rosalab.ru/rosa/rosa2014.1/repository/x86_64/ # urpmi.addmedia main32_release http://mirror.rosalab.ru/rosa/rosa2014.1/repository/i586/main/release # urpmi.addmedia main32_updates http://mirror.rosalab.ru/rosa/rosa2014.1/repository/i586/main/updates # urpmi.update --ignore updates
32bit main/release and main/updates repositories are necessary in 64bit systems in order to make 32bit-only applications such as Skype available. Note that we have disabled "updates" repositories for now, since we only tested update to release repositories of Desktop Fresh R4.
- update all packages to R4 state; preliminary download all necessary packages (the latter is important, since the network connection can go down during update):
# urpmi --no-install --auto-update --auto # urpmi --auto-update --auto
Note that depending on Internet connection speed and number of packages installed in the system, the update time may vary significantly. Average update time is about several hours. In some very special cases update can take about a day or even more.
- Turn back repositories with R4 updates and update your system to be sure that it is up to date:
# urpmi.update --no-ignore updates # urpmi --auto-update --auto
