On Wednesday 01 July 2020, ellie timoney wrote:
> Yes, please. If you don't, I will, but then you won't get
> automatic notifications of updates.
https://github.com/cyrusimap/cyrus-imapd/issues/3090
> Are they appearing in a log somewhere, or is this output
> from an analysis tool you're runni
On Tue, Jun 30, 2020, at 10:10 PM, Sergey wrote:
> On Monday 22 June 2020, ellie timoney wrote:
>
> > The Cyrus team is proud to announce the immediate availability
> > of a new version of Cyrus IMAP: 3.2.2
>
> There was a problem with AC_SYS_LARGEFILE. Most likely it was
> there before, but I
On Monday 22 June 2020, ellie timoney wrote:
> The Cyrus team is proud to announce the immediate availability
> of a new version of Cyrus IMAP: 3.2.2
There was a problem with AC_SYS_LARGEFILE. Most likely it was
there before, but I was no need to use AC_SYS_LARGEFILE.
Programs for x32 cannot wo
On Tuesday 30 June 2020, ellie timoney wrote:
> > > The Cyrus team is proud to announce the immediate availability of
> > > a new version of Cyrus IMAP: 3.2.2
> >
> > Tests have issued a new warning compared to 3.0.x (building in Linux):
> > verify-elf: WARNING: ./usr/lib64/libcyrus.so.0.0.0:
I have no idea what this refers to or where it comes from. Any further
information you could provide would be greatly appreciated!
Thanks
On Tue, Jun 30, 2020, at 5:14 AM, Sergey wrote:
> On Monday 22 June 2020, ellie timoney wrote:
>
> > The Cyrus team is proud to announce the immediate avail
On Monday 22 June 2020, ellie timoney wrote:
> The Cyrus team is proud to announce the immediate availability of a new
> version of Cyrus IMAP: 3.2.2
Tests have issued a new warning compared to 3.0.x (building in Linux):
verify-elf: WARNING: ./usr/lib64/libcyrus.so.0.0.0: found executable STACK
