Re: [Davical-general] External bindings are lost when upgrading to Debian 13

[<sou...@pa...>]

On 11/2/25 08:02, Julien Métairie via Davical-general - davical-general 
at lists.sourceforge.net wrote:
> Hello,
>
> I upgraded from Debian 12 to Debian 13 (Trixie). AWL and Davical
> versions do not change across migration (respectively 0.64 and 1.1.12),
> but Postgres cluster was upgraded from 15 to 17 as part of the process.
>
> Before migration, I had an external binding for official holidays.
>
> However this external binding disappeared during the process. My DAV
> client now gets a 404 response when trying to get it.
> It appears that the "dav_binding" table is now empty. I found the
> following in /var/log/apt/term.log:
>
> pg_restore: erreur : COPY échoué pour la table « dav_binding » : ERREUR:
>    la relation « collection » n'existe pas
> [...]
> REQUÊTE : SELECT TRUE          FROM collection WHERE dav_name = in_path
> CONTEXTE : fonction PL/pgSQL public.real_path_exists(text), ligne 16 à
> instruction SQL
> COPY dav_binding, ligne 1 : « 43806     43805   \N      1001
> /ruliane/       /ruliane/joursferies/   Jours fériés
> https://etalab.github.io/jours-fe... »
> pg_restore: attention : erreurs ignorées lors de la restauration : 1
>
>
> I'm not sure why the automatic Postgres upgrade process didn't manage to
> fully restore the content of DAViCal database. Is somebody aware of this
> issue ?
>
> Regards
> Julien

Hello Julien,

I've found that upgrading from Debian 12 to 13 using just aptitude, 
results in problems.

So I have created a minimal KVM image and a KDE image and use these as 
'cardinal' images and am flanging each of my VMs into these as I have time.

In Davical I have all US holidays using this method.  With a major 
upgrade it's usually best to just reinstall, with as much time as that 
takes.

Carl