roma
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
roma [2021/12/26 17:23] team |
roma [2022/07/01 11:55] (current) team |
||
|---|---|---|---|
| Line 56: | Line 56: | ||
| Let's begin! | Let's begin! | ||
| - | First of all we open synaptic and look for the upgradeufficiozero package and install it. | + | First of all we open Synaptic and look for the upgradeufficiozero package and install it. |
| - | Before closing synaptic we must check if there are any updates to be done, if there are any updates We must update all proposed packages. | + | Before closing Synaptic we must check if there are any updates to be done, if there are any updates We must update all proposed packages. |
| In menu "system tools" click on "upgrade-ufficiozero" which will replace the sources list in order to pass from Roma to Portofino, from Devuan Beowulf to Devuan Chimaera and to start the upgrade process. | In menu "system tools" click on "upgrade-ufficiozero" which will replace the sources list in order to pass from Roma to Portofino, from Devuan Beowulf to Devuan Chimaera and to start the upgrade process. | ||
| Line 67: | Line 67: | ||
| Here are some pictures that offer a better understanding. | Here are some pictures that offer a better understanding. | ||
| + | {{ :roma-to-portofino-6.png |}} | ||
| + | {{ :roma-to-portofino-5.png |}} | ||
| + | {{ :roma-to-portofino-4.png |}} | ||
| + | {{ :roma-to-portofino-3.png |}} | ||
| + | {{ :roma-to-portofino-2.png |}} | ||
| {{ :roma-to-portofino-1.png |}} | {{ :roma-to-portofino-1.png |}} | ||
| + | In some cases the upgrade process may hang on the first part after the sources.list update and the terminal may close. If so, open Synaptic and perform a reload and apply the changes to the proposed packages. At this stage, the various windows inserted above will appear. | ||
| + | |||
| + | If ArubaSign installed on Roma doesn't start on Portofino, after the system has been upgraded, You must create a symbolic link for Python as below: | ||
| + | <code>sudo ln -s /usr/bin/python2.7 /usr/bin/python</code> | ||
| + | or if you first cleaned the system of packages no longer used with: | ||
| + | <code>sudo apt autoremove</code> | ||
| + | you may create a symbolic link for Python as below: | ||
| + | <code>sudo ln -s /usr/bin/python3.9 /usr/bin/python</code> | ||
| + | |||
| + | because python2.7 is old and no longer required. | ||
| + | |||
| + | ===== How to solve problem with our repository ===== | ||
| + | |||
| + | On June 2nd We updated the signature on our repositories therefore the keyring package update was released before June 28th automatically on the PCs that have performed the updates. However, it can happen that after June 28, if users have not performed system updates, the same can report signature problems on our repository. In this case, to remedy the problem, you can download and install the keyring package from this link: https://ufficiozero.mirror.garr.it/uzl-deb/roma/pool/main/u/ufficiozero-keyring/ufficiozero-keyring_2022.06%2Bnmu2_all.deb to solve this problem. | ||
roma.1640535802.txt.gz ยท Last modified: 2021/12/26 17:23 by team
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution 4.0 International
