Personally all the add-ons and pluggins such as Snyckolab and SoGo, as nice as it was for the programmers to come up with a way to get sync with thunderbird just don't do justice to Citadel and Thunderbird. I just don't feel like they are true solutions to syncing the Citadel calendar, tasks and contacts.   As much as I like Citadel and use the web version on the run tp get info or a quick glance, when I get back to the office, I rather open up Thunderbird.  I wish the Citadel dev team would come up with a native sync method to pull and push to Thunderbird.   Is this possible guys?

-SF-

Sun Jul 20 2014 13:33:59 EDT from shadowfire @ Uncensored Subject: Citadel native syc connection to Thunderbird (Address/Cal/Task)

Dev's or others,

I have used Citadel going on 6+  years.  I have been pleased with it's performance and stability.  It is a rock solid Groupware solution internally to itself (browser/webclient).   I understand the use of Bynari client that has to be used by Outlook users to allow Citadel to become a fully functioning Exchange buster.   I know I can use SyncKolab to sync the Addresses, Calendars and Tasks (I have had mixed experiences with it), I also have heard SoGo connector for Thunderbird can be supposedly used with Thunderbird for the same solution (I will admit that I have be less then successful at getting it to work with calendars - and not sure if it will allow address and tasks sync).  but I guess I am perplex that their has not been made inroutes into Citadel to Thunderbird native syncing.  Am I the only one having issues in connectivity between Thunderbird and Citadel?  Or can someone put together their document method - a line by line instructions on how they sync Thunderbird with their Production Citadel server.

Thanks,

-SF-

Hi,

Looks like uncensored is running 8.29 version?

I tried easyinstall but after going through it, it still shows 8.24.

Is 8.29 released?

Also, quite often I get "Not found" error message while moving a message from one room to another. But after you refresh the webcit page in the browser it seems to complete the move.

the master branch always has a version number in the end of the current release cycle- so if you install .debs for testing they don't get overridden.

If you like bleeding edge, go ahead and install from git.

I have used the citadel server over a year now on a CentOS-6 platform with updates working without any problem. For a while now, the updates for citadel are being blocked by an unsatisfied dependency in perl-Net-Citadel-0.20-4.3.x86_64 requiring perl = %{perl_version}. I think this was supposed to be a variable defined at build time but has instead been used as a literal which cannot be satisfied.

I wonder why this has not already been fixed. Am I the only one using citadel on CentOS or is this a situation that an environment variable needs to be set for yum to update correctly.

Thanks for attentioon to the problem.

I'm thinking of setting this up on a centOS VM and was wondering will it work on CentOS7 yet?

if not then is CentOS6.5 good?

I rebuilt perl-Net-Citadel from src.rpm, modifying .spec file to list perl dependency as:
   Requires: perl >= 5.10
Rpm built and installed without problem.

Then tried yum update to finish citadel update - fails with error:
Downloading Packages:
citadel-8.24-1.2.x86_64.rpm                          | 388 kB     00:01    
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Updating   : citadel-8.24-1.2.x86_64                              1/2
Error unpacking rpm package citadel-8.24-1.2.x86_64
error: unpacking of archive failed: cpio: lstat
citadel-8.20-1.2.x86_64 was supposed to be removed but is not!
  Verifying  : citadel-8.20-1.2.x86_64                              1/2
  Verifying  : citadel-8.24-1.2.x86_64                              2/2

Failed:
  citadel.x86_64 0:8.20-1.2              citadel.x86_64 0:8.24-1.2         

There appears to be a corrupt file in the repository.

This also needs to be attended to.  

Sat Jul 26 2014 11:56:57 EDT from Steve Willoughby @ Uncensored 

For a while now, the updates for citadel are being blocked by an unsatisfied dependency in perl-Net-Citadel-0.20-4.3.x86_64 requiring perl = %{perl_version}. I think this was supposed to be a variable defined at build time but has instead been used as a literal which cannot be satisfied.

The first issue is why it's in the dependency chain at all.  There needs to be a Citadel system somewhere within reach of the network in order for the module to be useful but that doesn't mean there's a package type dependency in either direction.

Secondly;   the module itself doesn't have a dependency on any particular version of Perl as yet, so I'm curious as to why it's in there at all...

Btw; what repository are you using, where that comes up? I'd like to take a look at that srpm...  

I wonder why this has not already been fixed

I wasn't even aware that an RPM was being created for it...   I am the maintainer for the Perl module but do the development for it primarily on Debian and haven't gotten around to working on an SRPM for it (though it is on my todo list...);  only have it for testing on one CentOS system so far (the Perl module, not citadel; I'll have citadel on  a separate system) and there I installed it from CPAN..

Jame

Would it be possible for someone to build a Citadel VM with ESXi 5.5 (with VMware tools) and using CentOS 6.5 (or 7)

using UEFI boot and a VMXNET3 nic

If someone could do this that would be awesome

(BTW I'm only posting like this because I'm hesitant to build it myself (I've had issues with some other Linux packages namely ICTfax and CentOS6.4)

I am a Linux noob but CentOS is my preferred, I realize 7 is very new and 6.5 is only a little less.

I have used the citadel server over a year now on a CentOS-6 platform with
updates working without any problem. For a while now, the updates for
citadel are being blocked by an unsatisfied dependency in
perl-Net-Citadel-0.20-4.3.x86_64 requiring perl = %{perl_version}. I think
this was supposed to be a variable defined at build time but has instead
been used as a literal which cannot be satisfied.

I wonder why this has not already been fixed. Am I the only one using
citadel on CentOS or is this a situation that an environment variable needs
to be set for yum to update correctly.

Thanks for attentioon to the problem.