Re: [SOGo] Domain Address Book doesn't show entries

2024-02-28 Thread Christian Mack

Hello

I do not get a Version 5.10.0.20240227 in nightlies for Debian bullseye.
In fact the last available version seems to be 5.10.0.20240223-1
Is it just me?


Kind regards,
Christian Mack

Am 27.02.24 um 14:46 schrieb Pavel Zheltobryukhov (pave...@gmail.com):

Thanks, I suggested this, but decided to ask one more time
WBR, Pavel

On Tue, Feb 27, 2024 at 12:09 PM smizr...@alinto.eu  wrote:


Dear Pavel,

I apologize this was a confusion on my side, you're right, in the
nightly 5.10.0.20240227 you have to use listRequiresDot = NO as in
5.9.1. SOGoGlobalAddressBookFirstEntries has been removed to keep
only listRequiresDot.
But you can now use also globalAddressBookFirstEntriesCount if you want to
limit the results displayed (in the SOGoUserSources part).

Sorry for this, hope this helps. Let me know if you still have issues.

Sebastien


Le Mardi, Février 27, 2024 09:11 CET, "Pavel Zheltobryukhov" (
pave...@gmail.com)  a écrit:


And those new settings will be removed in 5.10.0.20240227? due 
'fix(addressbook):
Removed SOGoGlobalAddressBookFirstEntries (use listRequiresDot instead)
and move SOGoGlobalAddressBookFirstEntriesCount to
globalAddressBookFirstEntriesCount in source scope. This fixed the broken
listRequiresDot in 5.10'

On Sun, Jan 21, 2024 at 11:53 PM smizr...@alinto.eu  wrote:


Dear Pavel,

You're right, those new settings will be included in the next release.
As the documentation says, if you're using ldap you will need to enable
sslv overlay, otherwise the list will not be sorted.

Sebastien

Le Dimanche, Janvier 21, 2024 21:34 CET, "Pavel Zheltobryukhov" (
pave...@gmail.com)  a écrit:


Search across SOGo gitlab and found two new parameters in sogo.conf
(since Dec 18)

SOGoGlobalAddressBookFirstEntries
Display first entries in Global Address Book. Default value is `NO`. If
source is LDAP, the LDAP overlay `sssvlv` must be enabled on the system for
server side sorting.
SOGoGlobalAddressBookFirstEntriesCount
Number of entries displayed when `SOGoGlobalAddressBookFirstEntries` is
enabled. Default value is `100`.

This parameters affect Domain Address Book too. At least, you need to set
SOGoGlobalAddressBookFirstEntries to 'YES'

WBR, Pavel Zhe

On Sat, Jan 20, 2024 at 4:45 PM Pavel Zheltobryukhov 
wrote:


Hi, I upgraded SOGo from 5.9.1.20231213-1 to 5.9.1.20240120-1 and
discovered that my Domain Address Book doesn't show any entries when
opened. If I type some chars in search field, DAB show me founded entries
correctly. Is this a bug, or something changed in config files?

WBR, Pavel Zhe














--
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung IT-Dienste Forschung, Lehre, Infrastruktur
78457 Konstanz
+49 7531 88-4416



smime.p7s
Description: Kryptografische S/MIME-Signatur


Re: [SOGo] Domain Address Book doesn't show entries

2024-02-28 Thread smizr...@alinto.eu

Hello Christian,

Packages seems to be up to date : 
https://packages.sogo.nu/nightly/5/debian/pool/bullseye/s/sogo/

I have tried with a fresh install with docker, and the version is good :
Setting up libsbjson2.3 (4.9.r1664.20240220) ...
Setting up libsope-core4.9 (4.9.r1664.20240220) ...
Setting up libsope-mime4.9 (4.9.r1664.20240220) ...
Setting up libsope-appserver4.9 (4.9.r1664.20240220) ...
Setting up libsope-ldap4.9 (4.9.r1664.20240220) ...
Setting up sope4.9-libxmlsaxdriver (4.9.r1664.20240220) ...
Setting up libsope-gdl1-4.9 (4.9.r1664.20240220) ...
Setting up sope4.9-gdl1-mysql (4.9.r1664.20240220) ...
Setting up sogo (5.10.0.20240228-1) ...
Can you try to clean your repo and update ?

Sebastien
​

Le Mercredi, Février 28, 2024 10:19 CET, "Christian Mack" 
(christian.m...@uni-konstanz.de)  a écrit:
 Hello

I do not get a Version 5.10.0.20240227 in nightlies for Debian bullseye.
In fact the last available version seems to be 5.10.0.20240223-1
Is it just me?


Kind regards,
Christian Mack

Am 27.02.24 um 14:46 schrieb Pavel Zheltobryukhov (pave...@gmail.com):
> Thanks, I suggested this, but decided to ask one more time
> WBR, Pavel
>
> On Tue, Feb 27, 2024 at 12:09 PM smizr...@alinto.eu  wrote:
>
>> Dear Pavel,
>>
>> I apologize this was a confusion on my side, you're right, in the
>> nightly 5.10.0.20240227 you have to use listRequiresDot = NO as in
>> 5.9.1. SOGoGlobalAddressBookFirstEntries has been removed to keep
>> only listRequiresDot.
>> But you can now use also globalAddressBookFirstEntriesCount if you want to
>> limit the results displayed (in the SOGoUserSources part).
>>
>> Sorry for this, hope this helps. Let me know if you still have issues.
>>
>> Sebastien
>>
>>
>> Le Mardi, Février 27, 2024 09:11 CET, "Pavel Zheltobryukhov" (
>> pave...@gmail.com)  a écrit:
>>
>>
>> And those new settings will be removed in 5.10.0.20240227? due 
>> 'fix(addressbook):
>> Removed SOGoGlobalAddressBookFirstEntries (use listRequiresDot instead)
>> and move SOGoGlobalAddressBookFirstEntriesCount to
>> globalAddressBookFirstEntriesCount in source scope. This fixed the broken
>> listRequiresDot in 5.10'
>>
>> On Sun, Jan 21, 2024 at 11:53 PM smizr...@alinto.eu  wrote:
>>
>>> Dear Pavel,
>>>
>>> You're right, those new settings will be included in the next release.
>>> As the documentation says, if you're using ldap you will need to enable
>>> sslv overlay, otherwise the list will not be sorted.
>>>
>>> Sebastien
>>>
>>> Le Dimanche, Janvier 21, 2024 21:34 CET, "Pavel Zheltobryukhov" (
>>> pave...@gmail.com)  a écrit:
>>>
>>>
>>> Search across SOGo gitlab and found two new parameters in sogo.conf
>>> (since Dec 18)
>>>
>>> SOGoGlobalAddressBookFirstEntries
>>> Display first entries in Global Address Book. Default value is `NO`. If
>>> source is LDAP, the LDAP overlay `sssvlv` must be enabled on the system for
>>> server side sorting.
>>> SOGoGlobalAddressBookFirstEntriesCount
>>> Number of entries displayed when `SOGoGlobalAddressBookFirstEntries` is
>>> enabled. Default value is `100`.
>>>
>>> This parameters affect Domain Address Book too. At least, you need to set
>>> SOGoGlobalAddressBookFirstEntries to 'YES'
>>>
>>> WBR, Pavel Zhe
>>>
>>> On Sat, Jan 20, 2024 at 4:45 PM Pavel Zheltobryukhov 
>>> wrote:
>>>
 Hi, I upgraded SOGo from 5.9.1.20231213-1 to 5.9.1.20240120-1 and
 discovered that my Domain Address Book doesn't show any entries when
 opened. If I type some chars in search field, DAB show me founded entries
 correctly. Is this a bug, or something changed in config files?

 WBR, Pavel Zhe

>>>
>>>
>>>
>>
>>
>>
>>
>

--
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung IT-Dienste Forschung, Lehre, Infrastruktur
78457 Konstanz
+49 7531 88-4416
 

 


[SOGo] SOGo upgrading - some SOPE components was not upgraded

2024-02-28 Thread Pavel Zheltobryukhov
I performed upgrade sogo from
5.9.1.20240120-1 to 5.10.0.20240227-1 and noted that some SOPE components
was not upgraded - dpkg status changes Begin



Upgraded:
libsbjson2.3:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-appserver4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-core4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-gdl1-4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-ldap4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-mime4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-xml4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
sogo-activesync:amd64 5.9.1.20240120-1 => 5.10.0.20240227-1
sogo:amd64 5.9.1.20240120-1 => 5.10.0.20240227-1

-- dpkg status changes End -
But
# dpkg -l|grep sope ii libsope-appserver4.9 4.9.r1664.20240220 amd64 SOPE
application server libraries ii libsope-core4.9 4.9.r1664.20240220 amd64
Core libraries of the SOPE application server ii libsope-gdl1-4.9
4.9.r1664.20240220 amd64 GNUstep database libraries for SOPE ii
libsope-ldap4.9 4.9.r1664.20240220 amd64 SOPE libraries for LDAP access ii
libsope-mime4.9 4.9.r1664.20240220 amd64 SOPE libraries for MIME processing
ii libsope-xml4.9 4.9.r1664.20240220 amd64 SOPE libraries for XML
processing ii sope4.9-gdl1-postgresql 4.9.r1664.20231221 amd64 PostgreSQL
connector for SOPE's fork of the GNUstep database environment ii
sope4.9-libxmlsaxdriver 4.9.r1664.20231221 amd64 XML Parser for SOPE's SAX
engine

sope4.9-gdl1-postgresql and sope4.9-libxmlsaxdriver was not upgraded, but
listed as upgradeable

# apt list --upgradeable|grep sope

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

sope4.9-gdl1-postgresql/unknown 4.9.r1664.20240220 amd64 [upgradable from:
4.9.r1664.20231221]
sope4.9-libxmlsaxdriver/unknown 4.9.r1664.20240220 amd64 [upgradable from:
4.9.r1664.20231221]

Something broken in dependencies, or I should do this upgrade manually?

WBR, Pavel Zh.


Re: [SOGo] Domain Address Book doesn't show entries

2024-02-28 Thread Pavel Zheltobryukhov
Index of /nightly/5/debian/pool/bullseye/s/sogo
[image: [ICO]]Name
Last
modified

Size

Description

--
[image: [PARENTDIR]] Parent Directory
   -
[image: [ ]] sogo-activesync_5.10..>

2024-02-28
09:51 1.2M
[image: [ ]] sogo-dbg_5.10.0.2024..>

2024-02-28
09:51 2.9M
[image: [ ]] sogo-dev_5.10.0.2024..>

2024-02-28
09:51 1.1M
[image: [ ]] sogo_5.10.0.20240228..>

2024-02-28
09:51 5.9K
[image: [TXT]] sogo_5.10.0.20240228..>

2024-02-28
09:51 1.4K
[image: [ ]] sogo_5.10.0.20240228..>

2024-02-28
09:51 25M
[image: [ ]] sogo_5.10.0.20240228..>

2024-02-28
09:51 34M

0228 nightly already available now

On Wed, Feb 28, 2024 at 12:20 PM Christian Mack  wrote:

> Hello
>
> I do not get a Version 5.10.0.20240227 in nightlies for Debian bullseye.
> In fact the last available version seems to be 5.10.0.20240223-1
> Is it just me?
>
>
> Kind regards,
> Christian Mack
>
> Am 27.02.24 um 14:46 schrieb Pavel Zheltobryukhov (pave...@gmail.com):
> > Thanks, I suggested this, but decided to ask one more time
> > WBR, Pavel
> >
> > On Tue, Feb 27, 2024 at 12:09 PM smizr...@alinto.eu 
> wrote:
> >
> >> Dear Pavel,
> >>
> >> I apologize this was a confusion on my side, you're right, in the
> >> nightly 5.10.0.20240227 you have to use listRequiresDot = NO as in
> >> 5.9.1. SOGoGlobalAddressBookFirstEntries has been removed to keep
> >> only listRequiresDot.
> >> But you can now use also globalAddressBookFirstEntriesCount if you want
> to
> >> limit the results displayed (in the SOGoUserSources part).
> >>
> >> Sorry for this, hope this helps. Let me know if you still have issues.
> >>
> >> Sebastien
> >>
> >>
> >> Le Mardi, Février 27, 2024 09:11 CET, "Pavel Zheltobryukhov" (
> >> pave...@gmail.com)  a écrit:
> >>
> >>
> >> And those new settings will be removed in 5.10.0.20240227? due
> 'fix(addressbook):
> >> Removed SOGoGlobalAddressBookFirstEntries (use listRequiresDot instead)
> >> and move SOGoGlobalAddressBookFirstEntriesCount to
> >> globalAddressBookFirstEntriesCount in source scope. This fixed the
> broken
> >> listRequiresDot in 5.10'
> >>
> >> On Sun, Jan 21, 2024 at 11:53 PM smizr...@alinto.eu 
> wrote:
> >>
> >>> Dear Pavel,
> >>>
> >>> You're right, those new settings will be included in the next release.
> >>> As the documentation says, if you're using ldap you will need to enable
> >>> sslv overlay, otherwise the list will not be sorted.
> >>>
> >>> Sebastien
> >>>
> >>> Le Dimanche, Janvier 21, 2024 21:34 CET, "Pavel Zheltobryukhov" (
> >>> pave...@gmail.com)  a écrit:
> >>>
> >>>
> >>> Search across SOGo gitlab and found two new parameters in sogo.conf
> >>> (since Dec 18)
> >>>
> >>> SOGoGlobalAddressBookFirstEntries
> >>> Display first entries in Global Address Book. Default value is `NO`. If
> >>> source is LDAP, the LDAP overlay `sssvlv` must be enabled on the
> system for
> >>> server side sorting.
> >>> SOGoGlobalAddressBookFirstEntriesCount
> >>> Number of entries displayed when `SOGoGlobalAddressBookFirstEntries` is
> >>> enabled. Default value is `100`.
> >>>
> >>> This parameters affect Domain Address Book too. At least, you need to
> set
> >>> SOGoGlobalAddressBookFirstEntries to 'YES'
> >>>
> >>> WBR, Pavel Zhe
> >>>
> >>> On Sat, Jan 20, 2024 at 4:45 PM Pavel Zheltobryukhov <
> pave...@gmail.com>
> >>> wrote:
> >>>
>  Hi, I upgraded SOGo from 5.9.1.20231213-1 to 5.9.1.20240120-1 and
>  discovered that my Domain Address Book doesn't show any entries when
>  opened. If I type some chars in search field, DAB show me founded
> entries
>  correctly. Is this a bug, or something changed in config files?
> 
>  WBR, Pavel Zhe
> 
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >>
> >
>
> --
> Christian Mack
> Universität Konstanz
> Kommunikations-, Informations-, Medienzentrum (KIM)
> Abteilung IT-Dienste Forschung, Lehre, Infrastruktur
> 78457 Konstanz
> +49 7531 88-4416
>
>


Re: [SOGo] Domain Address Book doesn't show entries

2024-02-28 Thread Christian Mack

Hello Sebastien

Now I too see Version 5.10.0.20240228-1.
Thanks for checking.


Kind regards,
Christian Mack

Am 28.02.24 um 10:39 schrieb smizr...@alinto.eu (smizr...@alinto.eu):


Hello Christian,

Packages seems to be up to date : 
https://packages.sogo.nu/nightly/5/debian/pool/bullseye/s/sogo/

I have tried with a fresh install with docker, and the version is good :
Setting up libsbjson2.3 (4.9.r1664.20240220) ...
Setting up libsope-core4.9 (4.9.r1664.20240220) ...
Setting up libsope-mime4.9 (4.9.r1664.20240220) ...
Setting up libsope-appserver4.9 (4.9.r1664.20240220) ...
Setting up libsope-ldap4.9 (4.9.r1664.20240220) ...
Setting up sope4.9-libxmlsaxdriver (4.9.r1664.20240220) ...
Setting up libsope-gdl1-4.9 (4.9.r1664.20240220) ...
Setting up sope4.9-gdl1-mysql (4.9.r1664.20240220) ...
Setting up sogo (5.10.0.20240228-1) ...
Can you try to clean your repo and update ?

Sebastien
​

Le Mercredi, Février 28, 2024 10:19 CET, "Christian Mack" 
(christian.m...@uni-konstanz.de)  a écrit:
  Hello

I do not get a Version 5.10.0.20240227 in nightlies for Debian bullseye.
In fact the last available version seems to be 5.10.0.20240223-1
Is it just me?


Kind regards,
Christian Mack

Am 27.02.24 um 14:46 schrieb Pavel Zheltobryukhov (pave...@gmail.com):

Thanks, I suggested this, but decided to ask one more time
WBR, Pavel

On Tue, Feb 27, 2024 at 12:09 PM smizr...@alinto.eu  wrote:


Dear Pavel,

I apologize this was a confusion on my side, you're right, in the
nightly 5.10.0.20240227 you have to use listRequiresDot = NO as in
5.9.1. SOGoGlobalAddressBookFirstEntries has been removed to keep
only listRequiresDot.
But you can now use also globalAddressBookFirstEntriesCount if you want to
limit the results displayed (in the SOGoUserSources part).

Sorry for this, hope this helps. Let me know if you still have issues.

Sebastien


Le Mardi, Février 27, 2024 09:11 CET, "Pavel Zheltobryukhov" (
pave...@gmail.com)  a écrit:


And those new settings will be removed in 5.10.0.20240227? due 
'fix(addressbook):
Removed SOGoGlobalAddressBookFirstEntries (use listRequiresDot instead)
and move SOGoGlobalAddressBookFirstEntriesCount to
globalAddressBookFirstEntriesCount in source scope. This fixed the broken
listRequiresDot in 5.10'

On Sun, Jan 21, 2024 at 11:53 PM smizr...@alinto.eu  wrote:


Dear Pavel,

You're right, those new settings will be included in the next release.
As the documentation says, if you're using ldap you will need to enable
sslv overlay, otherwise the list will not be sorted.

Sebastien

Le Dimanche, Janvier 21, 2024 21:34 CET, "Pavel Zheltobryukhov" (
pave...@gmail.com)  a écrit:


Search across SOGo gitlab and found two new parameters in sogo.conf
(since Dec 18)

SOGoGlobalAddressBookFirstEntries
Display first entries in Global Address Book. Default value is `NO`. If
source is LDAP, the LDAP overlay `sssvlv` must be enabled on the system for
server side sorting.
SOGoGlobalAddressBookFirstEntriesCount
Number of entries displayed when `SOGoGlobalAddressBookFirstEntries` is
enabled. Default value is `100`.

This parameters affect Domain Address Book too. At least, you need to set
SOGoGlobalAddressBookFirstEntries to 'YES'

WBR, Pavel Zhe

On Sat, Jan 20, 2024 at 4:45 PM Pavel Zheltobryukhov 
wrote:


Hi, I upgraded SOGo from 5.9.1.20231213-1 to 5.9.1.20240120-1 and
discovered that my Domain Address Book doesn't show any entries when
opened. If I type some chars in search field, DAB show me founded entries
correctly. Is this a bug, or something changed in config files?

WBR, Pavel Zhe














--
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung IT-Dienste Forschung, Lehre, Infrastruktur
78457 Konstanz
+49 7531 88-4416
  

  



--
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung IT-Dienste Forschung, Lehre, Infrastruktur
78457 Konstanz
+49 7531 88-4416



smime.p7s
Description: Kryptografische S/MIME-Signatur


[SOGo] Various unknown messages in log

2024-02-28 Thread Raffael

Hi all,

I would like to keep my sogo installation as good as possible. Because 
of this I started to look through the logs and I found several entries 
which are only confusing to me. Can a) someone tell me what they want to 
tell me b) tell me if I can resolve them?


- nil object encountered in autorelease pool

- :65: element div: validity error : ID content_div already defined
  
 ^

- Got incomplete multibyte sequence. ToEncode: UTF-16LE FromEncode: UTF-8
(Here I understand what it means, but is this solvable? If the message 
would give me the ID of the email then at least I could look at the 
problematic email.)


- WARNING(-[NGBufferedStream writeBytes:count:]): got passed in length 
516MB (541591990 bytes, errcode=2147483647) ...


- File NSConcreteMapTable.m: 570. In NSFreeMapTable Null table argument 
supplied


Best regards,

Raffael


Re: [SOGo] SOGo upgrading - some SOPE components was not upgraded

2024-02-28 Thread smizr...@alinto.eu

Hi Pavel,

Can you please open a ticket on bugs.sogo.nu ? I will have a look on that

Sebastien

Le Mercredi, Février 28, 2024 10:37 CET, "Pavel Zheltobryukhov" 
(pave...@gmail.com)  a écrit:
 I performed upgrade sogo from
5.9.1.20240120-1 to 5.10.0.20240227-1 and noted that some SOPE components was 
not upgraded  - dpkg status changes Begin 
 


Upgraded:
libsbjson2.3:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-appserver4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-core4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-gdl1-4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-ldap4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-mime4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-xml4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
sogo-activesync:amd64 5.9.1.20240120-1 => 5.10.0.20240227-1
sogo:amd64 5.9.1.20240120-1 => 5.10.0.20240227-1

-- dpkg status changes End - But  # 
dpkg -l|grep sope ii libsope-appserver4.9 4.9.r1664.20240220 amd64 SOPE 
application server libraries ii libsope-core4.9 4.9.r1664.20240220 amd64 Core 
libraries of the SOPE application server ii libsope-gdl1-4.9 4.9.r1664.20240220 
amd64 GNUstep database libraries for SOPE ii libsope-ldap4.9 4.9.r1664.20240220 
amd64 SOPE libraries for LDAP access ii libsope-mime4.9 4.9.r1664.20240220 
amd64 SOPE libraries for MIME processing ii libsope-xml4.9 4.9.r1664.20240220 
amd64 SOPE libraries for XML processing ii sope4.9-gdl1-postgresql 
4.9.r1664.20231221 amd64 PostgreSQL connector for SOPE's fork of the GNUstep 
database environment ii sope4.9-libxmlsaxdriver 4.9.r1664.20231221 amd64 XML 
Parser for SOPE's SAX engine sope4.9-gdl1-postgresql and 
sope4.9-libxmlsaxdriver was not upgraded, but listed as upgradeable # apt list 
--upgradeable|grep sope WARNING: apt does not have a stable CLI interface. Use 
with caution in scripts. sope4.9-gdl1-postgresql/unknown 4.9.r1664.20240220 
amd64 [upgradable from: 4.9.r1664.20231221]sope4.9-libxmlsaxdriver/unknown 
4.9.r1664.20240220 amd64 [upgradable from: 4.9.r1664.20231221] Something broken 
in dependencies, or I should do this upgrade manually? WBR, Pavel Zh.

 


Re: [SOGo] How many table

2024-02-28 Thread Albert Shih
Le 22/02/2024 à 11:45:14+0100, qhivert a écrit
Hi, 

> 
> Sogo has two modes for database.
> 
> The current one, with only 11 tables
> 
> The legacy one with several tables per user
> Both are ok and once a mode has been chosen, you can’t switch between them.

Ok thanks for the answer, just another question, what's the best way to
clean up the databases when some user leave definitely 


> 
> If you’re setting up a new sogo server, we encourage to use the new mode (by
> setting OCSStoreURL, OCSAclURL and OCSCacheFolderURL).

No our server are very old

Regards.

JAS

-- 
Albert SHIH 🦫 🐸
Observatoire de Paris
France
Heure locale/Local time:
mer. 28 févr. 2024 17:49:11 CET


[SOGo] missing tables in 5.10

2024-02-28 Thread akiba

Hi,
I recently updated to 5.10, but I don't seem to have the sogo_admin 
table.

sogo=> \dt
List of relations
 Schema |  Name  | Type  | Owner
++---+---
 public | sogo_acl   | table | sogo
 public | sogo_alarms_folder | table | sogo
 public | sogo_cache_folder  | table | sogo
 public | sogo_folder_info   | table | sogo
 public | sogo_quick_appointment | table | sogo
 public | sogo_quick_contact | table | sogo
 public | sogo_sessions_folder   | table | sogo
 public | sogo_store | table | sogo
 public | sogo_user_profile  | table | sogo
(9 rows)
Please provide Postgres commands to remedy the situation or some other 
ideas how to approach it.

Thanks,
James


Re: [SOGo] SOGo upgrading - some SOPE components was not upgraded

2024-02-28 Thread Pavel Zheltobryukhov
I replayed command history - upgrade command from 5.9.0 to 5.9.1 was

‘apt-get install sogo sogo-activesync sope4.9-gdl1-postgresql
sope4.9-libxmlsaxdriver’

So, It’s my mistake, not a bug - I simple type
‘apt-get install SOGo’


Ср, 28 февр. 2024 г. в 16:20, smizr...@alinto.eu :

> Hi Pavel,
>
> Can you please open a ticket on bugs.sogo.nu ? I will have a look on that
>
> Sebastien
>
> Le Mercredi, Février 28, 2024 10:37 CET, "Pavel Zheltobryukhov" (
> pave...@gmail.com)  a écrit:
>
>
> I performed upgrade sogo from
> 5.9.1.20240120-1 to 5.10.0.20240227-1 and noted that some SOPE components
> was not upgraded - dpkg status changes Begin
> 
>
>
> Upgraded:
> libsbjson2.3:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> libsope-appserver4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> libsope-core4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> libsope-gdl1-4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> libsope-ldap4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> libsope-mime4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> libsope-xml4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> sogo-activesync:amd64 5.9.1.20240120-1 => 5.10.0.20240227-1
> sogo:amd64 5.9.1.20240120-1 => 5.10.0.20240227-1
>
> -- dpkg status changes End -
> But
> # dpkg -l|grep sope ii libsope-appserver4.9 4.9.r1664.20240220 amd64 SOPE
> application server libraries ii libsope-core4.9 4.9.r1664.20240220 amd64
> Core libraries of the SOPE application server ii libsope-gdl1-4.9
> 4.9.r1664.20240220 amd64 GNUstep database libraries for SOPE ii
> libsope-ldap4.9 4.9.r1664.20240220 amd64 SOPE libraries for LDAP access ii
> libsope-mime4.9 4.9.r1664.20240220 amd64 SOPE libraries for MIME processing
> ii libsope-xml4.9 4.9.r1664.20240220 amd64 SOPE libraries for XML
> processing ii sope4.9-gdl1-postgresql 4.9.r1664.20231221 amd64 PostgreSQL
> connector for SOPE's fork of the GNUstep database environment ii
> sope4.9-libxmlsaxdriver 4.9.r1664.20231221 amd64 XML Parser for SOPE's SAX
> engine
>
> sope4.9-gdl1-postgresql and sope4.9-libxmlsaxdriver was not upgraded, but
> listed as upgradeable
>
> # apt list --upgradeable|grep sope
>
> WARNING: apt does not have a stable CLI interface. Use with caution in
> scripts.
>
> sope4.9-gdl1-postgresql/unknown 4.9.r1664.20240220 amd64 [upgradable from:
> 4.9.r1664.20231221]
> sope4.9-libxmlsaxdriver/unknown 4.9.r1664.20240220 amd64 [upgradable from:
> 4.9.r1664.20231221]
>
> Something broken in dependencies, or I should do this upgrade manually?
>
> WBR, Pavel Zh.
>
>
>
>


Re: [SOGo] SOGo upgrading - some SOPE components was not upgraded

2024-02-28 Thread Pavel Zheltobryukhov
I have read-only account at bugs.sogo.nu - 'pavelzh'
Can you promote me?


On Wed, Feb 28, 2024 at 4:20 PM smizr...@alinto.eu  wrote:

> Hi Pavel,
>
> Can you please open a ticket on bugs.sogo.nu ? I will have a look on that
>
> Sebastien
>
> Le Mercredi, Février 28, 2024 10:37 CET, "Pavel Zheltobryukhov" (
> pave...@gmail.com)  a écrit:
>
>
> I performed upgrade sogo from
> 5.9.1.20240120-1 to 5.10.0.20240227-1 and noted that some SOPE components
> was not upgraded - dpkg status changes Begin
> 
>
>
> Upgraded:
> libsbjson2.3:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> libsope-appserver4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> libsope-core4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> libsope-gdl1-4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> libsope-ldap4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> libsope-mime4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> libsope-xml4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
> sogo-activesync:amd64 5.9.1.20240120-1 => 5.10.0.20240227-1
> sogo:amd64 5.9.1.20240120-1 => 5.10.0.20240227-1
>
> -- dpkg status changes End -
> But
> # dpkg -l|grep sope ii libsope-appserver4.9 4.9.r1664.20240220 amd64 SOPE
> application server libraries ii libsope-core4.9 4.9.r1664.20240220 amd64
> Core libraries of the SOPE application server ii libsope-gdl1-4.9
> 4.9.r1664.20240220 amd64 GNUstep database libraries for SOPE ii
> libsope-ldap4.9 4.9.r1664.20240220 amd64 SOPE libraries for LDAP access ii
> libsope-mime4.9 4.9.r1664.20240220 amd64 SOPE libraries for MIME processing
> ii libsope-xml4.9 4.9.r1664.20240220 amd64 SOPE libraries for XML
> processing ii sope4.9-gdl1-postgresql 4.9.r1664.20231221 amd64 PostgreSQL
> connector for SOPE's fork of the GNUstep database environment ii
> sope4.9-libxmlsaxdriver 4.9.r1664.20231221 amd64 XML Parser for SOPE's SAX
> engine
>
> sope4.9-gdl1-postgresql and sope4.9-libxmlsaxdriver was not upgraded, but
> listed as upgradeable
>
> # apt list --upgradeable|grep sope
>
> WARNING: apt does not have a stable CLI interface. Use with caution in
> scripts.
>
> sope4.9-gdl1-postgresql/unknown 4.9.r1664.20240220 amd64 [upgradable from:
> 4.9.r1664.20231221]
> sope4.9-libxmlsaxdriver/unknown 4.9.r1664.20240220 amd64 [upgradable from:
> 4.9.r1664.20231221]
>
> Something broken in dependencies, or I should do this upgrade manually?
>
> WBR, Pavel Zh.
>
>
>
>


Re: [SOGo] SOGo upgrading - some SOPE components was not upgraded

2024-02-28 Thread smizr...@alinto.eu

I have upgraded your account.

Sebastien

Le Mercredi, Février 28, 2024 14:48 CET, "Pavel Zheltobryukhov" 
(pave...@gmail.com)  a écrit:
 I have read-only account at bugs.sogo.nu - 'pavelzh'Can you promote me?  On 
Wed, Feb 28, 2024 at 4:20 PM smizr...@alinto.eu  wrote:Hi Pavel,

Can you please open a ticket on bugs.sogo.nu ? I will have a look on that

Sebastien

Le Mercredi, Février 28, 2024 10:37 CET, "Pavel Zheltobryukhov" 
(pave...@gmail.com)  a écrit:
 I performed upgrade sogo from
5.9.1.20240120-1 to 5.10.0.20240227-1 and noted that some SOPE components was 
not upgraded  - dpkg status changes Begin 
 


Upgraded:
libsbjson2.3:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-appserver4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-core4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-gdl1-4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-ldap4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-mime4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
libsope-xml4.9:amd64 4.9.r1664.20231221 => 4.9.r1664.20240220
sogo-activesync:amd64 5.9.1.20240120-1 => 5.10.0.20240227-1
sogo:amd64 5.9.1.20240120-1 => 5.10.0.20240227-1

-- dpkg status changes End - But  # 
dpkg -l|grep sope ii libsope-appserver4.9 4.9.r1664.20240220 amd64 SOPE 
application server libraries ii libsope-core4.9 4.9.r1664.20240220 amd64 Core 
libraries of the SOPE application server ii libsope-gdl1-4.9 4.9.r1664.20240220 
amd64 GNUstep database libraries for SOPE ii libsope-ldap4.9 4.9.r1664.20240220 
amd64 SOPE libraries for LDAP access ii libsope-mime4.9 4.9.r1664.20240220 
amd64 SOPE libraries for MIME processing ii libsope-xml4.9 4.9.r1664.20240220 
amd64 SOPE libraries for XML processing ii sope4.9-gdl1-postgresql 
4.9.r1664.20231221 amd64 PostgreSQL connector for SOPE's fork of the GNUstep 
database environment ii sope4.9-libxmlsaxdriver 4.9.r1664.20231221 amd64 XML 
Parser for SOPE's SAX engine sope4.9-gdl1-postgresql and 
sope4.9-libxmlsaxdriver was not upgraded, but listed as upgradeable # apt list 
--upgradeable|grep sope WARNING: apt does not have a stable CLI interface. Use 
with caution in scripts. sope4.9-gdl1-postgresql/unknown 4.9.r1664.20240220 
amd64 [upgradable from: 4.9.r1664.20231221]sope4.9-libxmlsaxdriver/unknown 
4.9.r1664.20240220 amd64 [upgradable from: 4.9.r1664.20231221] Something broken 
in dependencies, or I should do this upgrade manually? WBR, Pavel Zh.

 

 


Re: [SOGo] missing tables in 5.10

2024-02-28 Thread smizr...@alinto.eu

Hi James, 

Did you add the OCSAdminURL in your configuration ? (if yes, the table shall be 
automatically created)

Sebastien

Le Mercredi, Février 28, 2024 18:40 CET, "akiba" (ak...@east-central.eu) 
 a écrit:
 Hi,
I recently updated to 5.10, but I don't seem to have the sogo_admin
table.
sogo=> \dt
List of relations
Schema | Name | Type | Owner
++---+---
public | sogo_acl | table | sogo
public | sogo_alarms_folder | table | sogo
public | sogo_cache_folder | table | sogo
public | sogo_folder_info | table | sogo
public | sogo_quick_appointment | table | sogo
public | sogo_quick_contact | table | sogo
public | sogo_sessions_folder | table | sogo
public | sogo_store | table | sogo
public | sogo_user_profile | table | sogo
(9 rows)
Please provide Postgres commands to remedy the situation or some other
ideas how to approach it.
Thanks,
James

 


Re: [SOGo] How many table

2024-02-28 Thread "Rouven Seifert"
Hi there,

>
> Sogo has two modes for database.
>
> The current one, with only 11 tables
>
> The legacy one with several tables per user
> Both are ok and once a mode has been chosen, you can’t switch between them.
>
> If you’re setting up a new sogo server, we encourage to use the new mode (by 
> setting OCSStoreURL, OCSAclURL and OCSCacheFolderURL).
>

I was reading this and wondering if this recommendation is actually documented 
somewhere?
The current installation guide (found at [0]) still seems to recommend the old 
scheme per default 
and just references the 3 new options alongside others in that one big table.

Another question:
We currently run our SOGo instance in legacy mode. What would happen if we 
would set the three options (OCSStoreURL, OCSAclURL and OCSCacheFolderURL) now?
The Docs mention no breaking behaviour at this point.

Best regards,
Rouven

--
Rouven Seifert
Co-Admin im Fachschaftsrat Informatik der TU Dresden
https://ifsr.de

[0] 
https://www.sogo.nu/files/docs/SOGoInstallationGuide.html#_database_configuration


[SOGo] BTS activities for Wednesday, February 28 2024

2024-02-28 Thread SOGo reporter
Title: BTS activities for Wednesday, February 28 2024





  
BTS Activities

  Home page: https://bugs.sogo.nu
  Project: SOGo
  For the period covering: Wednesday, February 28 2024

  
  
idlast updatestatus (resolution)categorysummary
	
	
	  
	
5793
	2024-02-28 16:44:49
	acknowledged (open)
	Web General
	SOGo pages fail to load, generating 404 errors
	
	  
	
5932
	2024-02-28 16:57:59
	resolved (fixed)
	Documentation
	Restriction of SOGoGlobalAddressBookFirstEntriesCount not documented
	
	  
	
5931
	2024-02-28 16:48:34
	resolved (fixed)
	Web Address Book
	Global address book does not display field descriptions and persons like groups