>
> Since libciadel is just shared between citadel-server and
> citadel-webcit, whats the obstacle in updating it?
None really, it just needs to be done, but it wasn't mentioned
in your request, and I hit it while trying to test the
current Debian packages, so I firstly wanted to ask for
clarification.
> Its usualy released together with the two server packages
upstream.
Should we also be upgrading citadel-webcit then?
> Yes, some of the bugfixes which are worth updating are in libcitadel,
> and updating to 7.37 doesn't imply any dangers to me.
We have 1.14-1, so that is a huge version number jump, and we are in
feature freeze. Normally a jump like this would indicate huge changes
upstream, but I get the impression it is just to synchronise version
numbers. If it is just a bugfix release then updating is easier than
if we have to apply for a freeze exception.
> Also .36 won't be supported by the pkg-citadelteam anymore, since its
> not used in debian.
That's a good reason.
Thanks,
James
P.S. please reply to the bug report so that everyone can read the
discussion, not just me.
Ok;
Libcitadel had been fresh introduced, so duplicating code between webcit and
citadel could be unified. Thus choosing 1.x was sort of apropriate, but we
decided to sync it with server and client later.
Yes, webcit should be updated too. Most important change was the switch
to vnote format here afair.
We're actualy evaluating .38, citadel and libcitadel; which is primarily
the bugfixes over the summer, if we can do this, this is going to be the
release maintained for lenny.
--
citadel package out of sync
https://bugs.launchpad.net/bugs/274277
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
