The Winterfell project is a build project in the Kolab build system.
It is the canonical place through which continuous delivery is realized, after continuous integration has completed (successfully).
The Winterfell project is a build project in the Kolab build system.
It is the canonical place through which continuous delivery is realized, after continuous integration has completed (successfully).
Hello sicherha,
Hello sicherha,
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.
I see Debian 10 has been added in OBS, is anyone working on adding CentOS 8?
I've updated my kolab installation from Debian 9 to 10. All in all nothing major. Highlights:
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.
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...
I'm working on providing Debian 10 packages for Kolab 16.
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 :-)
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
We don't support Ubuntu 14.04.
We don't support Ubuntu 14.04.
Winterfell seems to use newest boot now:
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
In T1543#38255, @machniak wrote:@vanmeeuwen Does https://git.kolab.org/rP0e8a8276f60b4cf99ef37d9e3b413153d80bcd98 fix this or we plan another solution?
@vanmeeuwen Does https://git.kolab.org/rP0e8a8276f60b4cf99ef37d9e3b413153d80bcd98 fix this or we plan another solution?
@vanmeeuwen, this is still broken. Could you take a look?
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?
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.