YunoHost 4.0 (Buster) release / Sortie de YunoHost 4.0 (Buster)

17 posts were split to a new topic: Probleme avec rspamd et vpnclient après migration à Buster

J’ai fait la mise à jour sans erreur sur un VPS OVH mais ensuite j’avais un message comme quoi l’API Yunohost ne répondait pas. J’ai fait un apt install yunohost --reinstall et cela semble avoir résolu le problème.
Merci à tous

Salutations,
J’ai tenté la migration 015 to buster
Pour info je suis sur un conteneur lxc dans proxmox 6 (buster)
Le résultat de la mise à jour est ici https://paste.yunohost.org/raw/ejeqofevac
La migration stoppe ici sur ce timecode 2020-08-21 14:06:28,442
Le reste à l’air de ce passer normalement à part des messages warning…
J’ai des fichiers modifiés .bashrc , sshd_config
Je pense avoir un problème avec le resolve.conf car je suis dans le conteneur proxmox.
Ca peut aussi être un problème sur la conf reseau, le conteneur a une configuration spécifique (fichier de conf réseau spécial)
Avez vous une idée les copains ?
Merci d’avance.

Aprés reboot j’avais les services dovecot, redis-server et mysql impossible a démarrer.
Du coup j’ai fait un rollback sur le snapshot de mon conteneur dans proxmox.
Et j’ai retrouver mon instance comme auparavant.
J’ai laissé les mises à jour mais je ne lancerai pas le script de migration pour l’instant.

A mon avis pour le passage à Buster il faut que tu ai l’option nesting activé sur le conteneur (ce qui est lié à l’erreur que tu obtiens a la fin de la migration à propos de systemd-resolvedtruc)

Hello Aleks, merci de ton aide.
J’ai également posé la question @Sango sur un autre post qui a validé sa migration lxc proxmox.
Merci encore, je tiens la file au courant.

1 Like

Ok merci l’option nesting du conteneur à corriger ce problème. La migration est terminé.
Je dois voir pour la migration 0017_postgresql_9p6_to_11 err : target cluster 11/main already exists qui n’est pas passée
La migration 018 xtables to nftable est passée
Mastodon est peertube sont hs… je crois que c’est du postgresql

Ok j’ai trouvé 3 services le premier était inactif… je l’ai démarré et j’ai retrouvé mastodon et peertube
service postgresql
postgresql postgresql@11-main postgresql@9.6-main

J’ai tenté à nouveau la migration 0017 mais j’ai la même erreur https://paste.yunohost.org/raw/ecunijowoh

Et si tu fais pg_dropcluster --stop 11 main ça raconte quoi ?

The migration was so smooth thank you very much !! :kissing_heart: :kissing_heart:

It took 1 hour, and everything is working now, good job !

1 Like

Salut,
La migration s’est bien faite. Quelques soucis à la fin :

  • j’ai du relancer yunohost-api en ligne de commande pour pouvoir m’y reconnecter (le service était en failed)
  • mattermost ne marchait pas : ok après relance du service
  • lufi ne marchait pas : ok après relance de nginx
  • I hate money : ne marche plus, mais je ne crois pas que l’app ait été portée sur buster pour le moment, et elle est notée en basse qualité.
    Merci beaucoup pour le développement !
1 Like

I will write in this thread hoping this would be the right one.

I have a very well working yunohost server stable version 3.8.5.7 coming from a original debian install.

I tried to migrate to buster but I found a stopping error as the log here https://paste.yunohost.org/raw/fomegetire

I think the relevant line is

  - 2020-08-25 20:16:39,875: INFO - +  dpkg : Breaks: libapt-pkg5.0 (< 1.7\~b) but 1.4.10 is to be installed

Regarding the libapt-pkg5.0 package this the policy

apt policy libapt-pkg5.0
libapt-pkg5.0:
  Installed: 1.4.10
  Candidate: 1.8.2.1
  Version table:
     1.8.2.1 500
        500 https://deb.debian.org/debian buster/main amd64 Packages
        500 https://deb.debian.org/debian-security buster/updates/main amd64 Packages
 *** 1.4.10 100
        100 /var/lib/dpkg/status

Mokey and what if you try to apt install libapt-pkg5.0=1.8.2.1 ?

This is what happens:

root@cybervalley:~# apt install libapt-pkg5.0=1.8.2.1
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 unattended-upgrades-ynh-deps : Depends: apticron but it is not going to be installed
                                Depends: unattended-upgrades but it is not going to be installed
                                Depends: apt-listchanges but it is not going to be installed
 yunohost : Depends: apt but it is not going to be installed
            Recommends: unattended-upgrades but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

Hello !

A small message to report another successful migration to Yunohost 4.0.4

After migration, diagnosis said that yunohost-admin was not up to date. I restarted server and everything was OK.
But then Synapse was not restarting. I applied advices found at https://github.com/YunoHost-Apps/synapse_ynh/issues/208 and everything went fine again.
Synapse, FreshRSS, Monica, Nextcloud, Wallabag, Yourls, Zerobin and Adguard survived to the migration.

A big big hurray to all dev that made that possible!
Thanks girls and guys!!

1 Like

Hello, i migrate from 3.8.5.7 to 4.0.4
all is working fine. Nextcloud, Piwigo,.

In my diagnose i have a massege.
Configuration file /etc/nslcd.conf appears to have been manually modified.
This is probably OK if you know what you’re doing! YunoHost will stop updating this file automatically…
But beware that YunoHost upgrades could contain important recommended changes.
If you want to, you can inspect the differences with yunohost tools regen-conf nslcd --dry-run --with-diff and
force the reset to the recommended configuration with yunohost tools regen-conf nslcd --force

Configuration file /etc/nsswitch.conf appears to have been manually modified.
This is probably OK if you know what you’re doing! YunoHost will stop updating this file automatically…
But beware that YunoHost upgrades could contain important recommended changes.
If you want to, you can inspect the differences with yunohost tools regen-conf nsswitch --dry-run --with-diff and
force the reset to the recommended configuration with yunohost tools regen-conf nsswitch --force
I fix it with regen-conf nslcd --force
and regen-conf nsswitch --force

In DNS a have a new issue,
Some DNS records are missing or incorrect for domain s-grabisch.de (category xmpp) IgnorierenDetails

  • Please check the documentation at https://yunohost.org/dns_config if you need help about configuring DNS records.
  • According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: SRV
    Name: _xmpp-client._tcp
    Value: 0 5 5222 s-grabisch.de.
  • According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: SRV
    Name: _xmpp-server._tcp
    Value: 0 5 5269 s-grabisch.de.
    I think my DNS is like this, and i havent before this message. `

A new message is
The reverse DNS is not correctly configured in IPv4. Some emails may fail to get delivered or may get flagged as spam.
Current reverse DNS: public-gprs700653.centertel.pl
Expected value: s-grabisch.de
You should first try to configure the reverse DNS with s-grabisch.de in your internet router interface or your hosting provider interface. (Some hosting provider may require you to send them a support ticket for this).
Some providers won’t let you configure your reverse DNS (or their feature might be broken…). If you are experiencing issues because of this, consider the following solutions:

  • Some ISP provide the alternative of using a mail server relay though it implies that the relay will be able to spy on your email traffic.
  • A privacy-friendly alternative is to use a VPN with a dedicated public IP to bypass this kind of limits. See https://yunohost.org/#/vpn_advantage
  • Or it’s possible to switch to a different provider

I will try to fix it.
Thank for the good job oft the migration

Migration from 3.8.7.5 to 4.0 failed…

here’s the logs:
https://paste.yunohost.org/raw/ujimukajiy

If anyone can help…

EDIT: ok, had to remove a lot of stuff, reinstall … and modify the script… duh.

En forçant la mise à jour de l’application après la migration c’est revenu dans l’ordre !
yunohost app upgrade ihatemoney -u https://github.com/YunoHost-Apps/ihatemoney_ynh/tree/master

1 Like

Effectivement ça marche, merci !

1 Like

Half succes on my side: Buster OK / Yuno 4.x.x KO

Finally it was my fault (a config file had been edited) → perfect migration.

Thanks a lot to all contributors!!