mirror of
https://github.com/YunoHost/doc.git
synced 2024-09-03 20:06:26 +02:00
Add empty issues_faq about bookworm migration
This commit is contained in:
parent
eade845c04
commit
8ee4517251
1 changed files with 56 additions and 0 deletions
|
@ -0,0 +1,56 @@
|
||||||
|
---
|
||||||
|
title: Bookworm migration isues FAQ
|
||||||
|
template: docs
|
||||||
|
taxonomy:
|
||||||
|
category: docs
|
||||||
|
routes:
|
||||||
|
default: '/bookworm_migration_issues_faq'
|
||||||
|
---
|
||||||
|
|
||||||
|
This page lists all the known issues encountered after a migration from YunoHost 11 to 12.
|
||||||
|
|
||||||
|
## Python apps
|
||||||
|
|
||||||
|
After upgrading, your python apps should be unavailable because their virtual environment (venv) needs to be rebuilt.
|
||||||
|
|
||||||
|
To do that you can run the pending migrations in `Webadmin > Update`.
|
||||||
|
|
||||||
|
The apps below won't be automatically repaired, you need to force-upgrade them manually instead with `yunohost app upgrade -F APP`.
|
||||||
|
|
||||||
|
Apps which won't be automatically repaired and need a force upgrade:
|
||||||
|
|
||||||
|
TODO: list those apps
|
||||||
|
|
||||||
|
FIXME:??!!! If needed, you can disable the automatic rebuild for a specific python app, by removing the dedicated file ending with `.requirements_backup_for_bullseye_upgrade.txt` before applying the migration. You can find this file near the venv (Python virtual environment) of your app inside `/var/www`.
|
||||||
|
|
||||||
|
|
||||||
|
<!-- ### Can't run the migration due to `libc6-dev : Breaks: libgcc-8-dev issue`
|
||||||
|
|
||||||
|
Note: This issue should be resolved in `yunohost_version`: `4.4.2.13`
|
||||||
|
You have an app that depends on the `build-essential` package.
|
||||||
|
|
||||||
|
See this [solution](https://forum.yunohost.org/t/migration-to-11-wont-start-libc6-dev-breaks-libgcc-8-dev/20617/42) to fix it manually
|
||||||
|
|
||||||
|
### DNSmasq is not running anymore
|
||||||
|
|
||||||
|
We haven't yet found solution for this issue.
|
||||||
|
|
||||||
|
### No ethernet connexion after rebooting following a migration on a Raspberry Pi 4
|
||||||
|
|
||||||
|
! If you have not yet rebooted your server, don't do it (we are looking for a solution). This will avoid you the use of a keyboard and screen.
|
||||||
|
|
||||||
|
We found this in the Raspberry Pi documentation
|
||||||
|
|
||||||
|
> when the dhcpcd5 package is updated to the latest version (1:8.1.2-1+rpt1 -> 1:8.1.2-1+rpt2), the Raspberry Pi will fail to obtain a DHCP IP address following the next reboot or startup. This problem can be avoided by disabling and re-enabling the "System Options -> Network at Boot" option using the latest raspi-config after the dhcpcd5 package has been updated and prior to the system being shutdown or rebooted
|
||||||
|
|
||||||
|
If you are using a Raspberry Pi 4 (or maybe 3), see this [solution](https://forum.yunohost.org/t/aucun-acces-a-internet-suite-a-migration-4-4-to-11-depuis-raspberry-pi-4-pi-400/20652/17)
|
||||||
|
|
||||||
|
### Restore ynh4 backup onto a fresh ynh11
|
||||||
|
|
||||||
|
If you can't restore your app but your system has been restored, you probably should use the regen conf to fix the nginx issues:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
yunohost tools regenconf nginx --force
|
||||||
|
```
|
||||||
|
|
||||||
|
After that you should be able to restore your apps. Don't forget to force upgrade them if you have 502 errors. -->
|
Loading…
Reference in a new issue