Wiki source code of Upgrading from the Debian package
Last modified by Thomas Mortagne on 2025/02/05
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
2.1 | 1 | * Update packages index:((( |
| |
1.1 | 2 | {{code language="bash"}} |
 |
3.1 | 3 | sudo apt update |
| |
1.1 | 4 | {{/code}} |
| 5 | ))) | ||
| |
2.1 | 6 | * Package upgrade:((( |
| |
1.1 | 7 | {{code language="bash"}} |
| |
3.1 | 8 | sudo apt upgrade |
| |
1.1 | 9 | {{/code}} |
| 10 | |||
| |
4.1 | 11 | This will upgrade all packages, not just XWiki. If you want to avoid all the other packages and only update XWiki, you can use {{code}}sudo apt install xwiki-tomcat9-mariadb{{/code}} (change ##xwiki-tomcat9-mariadb## for the top level package you installed if you installed something else). |
| |
1.1 | 12 | |
| |
4.5 | 13 | ==== Troubleshooting |
| |
4.2 | 14 | |
| |
4.5 | 15 | ===== apt upgrade won't upgrade xwiki packages |
| |
4.2 | 16 | |
| 17 | Sometimes (especially in case of new cycle), apt upgrade might report that it refuse to upgrade some xwiki packages. | ||
| 18 | |||
| 19 | This is generally the sign that either: | ||
| |
4.3 | 20 | * a new dependency cannot be found: it generally means that XWiki starts requiring a more recent version of Java and the Debian repository you have don't have any implementation of this Java versions. See [[No package can be found for Java>>Documentation.AdminGuide.Installation.InstallationViaAPT||anchor="HNopackagecanbefoundforJava"]] for more details on how to resolve this situation. |
| |
4.2 | 21 | * some xwiki package name changed: this generally happen when XWiki stops supporting some version of Tomcat and you need to install a different xwiki-tomcat* package (for example XWiki 17 does not support tomcat9 and requires the tomcat10 package) |
| |
1.1 | 22 | ))) |
| |
2.1 | 23 | * Pages upgrade:((( |
| |
1.1 | 24 | However after upgrading you still need to install the new UI; see next step [[Upgrading the flavor>>.||anchor="HPart2Upgradingtheflavor"]] below. |
| 25 | ))) |
