Hello sicherha,
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 14 2021
Mar 1 2021
Hello sicherha,
Feb 25 2021
Umm, yeah, the docs are somewhat outdated because the build pipeline appears to be broken (T6055)...
Is there a release date for Kolab for Debian Buster?
https://docs.kolab.org/installation-guide/index.html does not mention anything.
Jan 24 2021
Sep 3 2020
I see Debian 10 has been added in OBS, is anyone working on adding CentOS 8?
Dec 3 2019
I've updated my kolab installation from Debian 9 to 10. All in all nothing major. Highlights:
Nov 25 2019
If you feel courageous enough, I would say it's ready for field testing. Should you encounter any remaining rough edges, please report them so they can be ironed out.
Nov 23 2019
I've seen in OBS that we now build packages for Debian 10.
What's your opinion: Is it probably ready to upgrade my instance?
The only package failing to build is chwala - where I could possiby use the old package...
Oct 4 2019
I'm working on providing Debian 10 packages for Kolab 16.
Oct 2 2019
According to https://obs.kolabsys.com/project/show/Kolab:Winterfell
RHEL_8 and Debian_10.0 have been added to Winterfell.
So my most pressing wishes have been granted :-)
Jul 25 2019
Jun 2 2019
Mar 22 2019
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Apr 21 2018
Apr 17 2018
We don't support Ubuntu 14.04.
We don't support Ubuntu 14.04.
Sep 18 2017
Winterfell seems to use newest boot now:
Aug 20 2017
Done.
Looks like some manual interaction is necessary:
https://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks#Removing_disabled_but_built_packages_from_a_repository
Jul 21 2017
In T1543#38255, @machniak wrote:@vanmeeuwen Does https://git.kolab.org/rP0e8a8276f60b4cf99ef37d9e3b413153d80bcd98 fix this or we plan another solution?
Jul 20 2017
@vanmeeuwen Does https://git.kolab.org/rP0e8a8276f60b4cf99ef37d9e3b413153d80bcd98 fix this or we plan another solution?
Jul 19 2017
Jul 18 2017
@vanmeeuwen, this is still broken. Could you take a look?
May 16 2017
Apr 5 2017
As a workaround I used nvm to install an appropriate version for npm:
export NODE_VERSION=0.12.8 && \ curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.1/install.sh | bash && \ export NVM_DIR="/root/.nvm" && \ source $NVM_DIR/nvm.sh && \ nvm install v$NODE_VERSION && \ ln -s /root/.nvm/versions/node/v0.12.8/bin/npm /usr/bin/npm
This bug also occurs in Kolab 16. Why does Kolab package Node JS and don't use the official Node JS packages?
Dec 13 2016
Nov 22 2016
Nov 19 2016
Oct 17 2016
Sep 29 2016
The headers are indeed added by smtp access policy and come from:
[kolab_smtp_access_policy] delegate_sender_header = True alias_sender_header = True sender_header = True xsender_header = True
Problem is that Roundcube already set X-Sender and Sender headers.
Sep 28 2016
Sep 21 2016
Sep 11 2016
Aug 22 2016
Aug 16 2016
Aug 8 2016
Jul 28 2016
Jul 25 2016
Jul 11 2016
Jul 8 2016
Jul 4 2016
Jun 29 2016
Jun 27 2016
Jun 20 2016
From what I see Debian/testing (stretch) contains a newer phantomjs:
Jun 17 2016
We installed new guam version guam.x86_64 0:0.7.3-4.1.el6.kolab_14 and get an init script but this is not executable by default. After chmod 555 it's executable but complains about some "erlexec: HOME must be set".
Jun 13 2016
Jun 6 2016
May 30 2016
May 23 2016
May 18 2016
@toru Can you please sugget this as a differential: https://docs.kolab.org/contributor-guide/peer-review.html
May 16 2016
May 11 2016
May 9 2016
May 2 2016
Apr 25 2016
Apr 19 2016
Are we likely to see SPECIAL-USE (RFC 6154) working and enabled on Kolab Now, as it is currently not enabled. This would definitely make email client setup easier and there would be no effort required for the non-technically inclined user. I reckon this would add some value to Kolab Now.