Skip to Content.
Sympa Menu

en - Re: [en@sympa] problem duplicated data in Postgresql sympa

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: "Stefan Hornburg (Racke)" <address@concealed>
  • To: address@concealed
  • Subject: Re: [en@sympa] problem duplicated data in Postgresql sympa
  • Date: Sun, 4 May 2025 12:35:20 +0200

On 03/05/2025 18:38, Stefan Hornburg (Racke) wrote:
On 02/05/2025 17:18, Daniel Viñar Ulriksen wrote:
Hello,

I'm doing tests for the upgrade from sympa 6.2.16 I mentionned in my last
mail.

Using cielito.sympa ansible collection (which takes advantage of
sympa-community.sympa role), I installed a sympa server, with a main mail
domains and three other as sympa robots. I create two lists with the same
name, but not under the same mail domain, and I subscribe to them. Lists
work. When re-running ansible role to test enhancements, it triggers a
re-installation of sympa, and then the upgrade process fails, arguing
duplicated data in table composed keys. If I cancel one subscription, the
error is slightly different, and after closing one of the lists, the upgrade
process succeeds.

Here are the reports:
https://git.interior.edu.uy/cielito/sympa/-/merge_requests/1#note_13592

Any idea? Are the postgres upgrade script updated and maintained?

Thanks in advance, daniel


Hello Daniel,

seen this problem as well. The from value is missing: "Upgrading from  to
6.2.72"

I will take a look.

Regards
  Racke -


This should be fixed with the commit 41c160ee6779ad3452f394e075768bf61791c15b
in the sympa-community.sympa role.

Regards
Racke

--
Automation expert - Ansible and friends
Linux administrator & Debian maintainer
Perl Dancer & conference hopper




Archive powered by MHonArc 2.6.19+.

Top of Page