Your message dated Wed, 24 Dec 2025 16:31:19 +0100
with message-id <[email protected]>
and subject line Re: sogo: calendar sharing is not working
has caused the Debian Bug report #862862,
regarding sogo: calendar sharing is not working
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
862862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862862
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sogo
Version: 3.2.6-2
Severity: important

It took me a while to setup this. In the end I went for postgresql as
database including auth backend. I tried very hard to share a calendar
between two users. It just won't happen. If I click on a calendar,
preferences, share then there is almost nothing there. Which means the
other user can't subscribe nor does he see something by default.

Shortly before I decided to purge sogo and try something else I upgraded
to the version in experimental. And see there, it works. I am sure that
the test path was:
   restart sogo, tried => didn't work, upgraded to exp, tried => worked.

I even purge the database and tried from scratch with the same result.
The version in exp is similar to what I see in the live demo at [0]
(click on calendar's preferences, share and there are things to click
(private, public, confidation, authenticated user and so on) which is
missing in the version in unstable.

My question here: am I simply too $attribute to configure it properly or
is this something that works perfectly with the LDAP auth-backend but
not with SQL?
If not, wouldn't it be material for testing _or_ at least document it?

[0] http://demo.sogo.nu

Sebastian

--- End Message ---
--- Begin Message ---
I think this bug has long be solved, therefore in an effort to clean up
the bug list closing this bug. If the bug is still there, please reopen
the bug.

-- 
tobi

--- End Message ---

Reply via email to