Bug#851086: [Pkg-citadel-devel] Bug#859789: RFH: citadel/webcit

2017-12-12 Thread Michael Meskes
> We patched some of the sources in an attempt to make it work on the 
> latest Debian, but that effort seems to have missed the mark.  That 
> having been said, we've got everything working with both old and new 
> libical versions now, and it seems to build cleanly on both previous
> and 
> current Debian versions.

I was referring to problems with libssl1.1, that, according to a post
by you Art (I think) is fixed. However, having the same version number
with different code causes more work, for which I don't have the time
atm. This is why the email was a request for help (RFH).

> A new release is forthcoming so if you want to hold tight for a
> little 
> while longer we should be able to smooth things out. Naturally it is
> up 
> to you as package maintainer whether you want to continue to
> volunteer 
> your time -- I totally respect that.

Actually the problem is I run very low on time right now. Let me make
two things clear, I really like citadel despite not using it and
upstream (all of them, not just Art) is very nice to work with and more
than willing to help.

My problem is a very simple lack of time. I'm able to do an upload
every now and then, but not much else. However, since you said there'll
be a release shortly, I won't ask for removal if that release fixes the
RCs.

Michael

-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL



Bug#851086: [Pkg-citadel-devel] Bug#859789: RFH: citadel/webcit

2017-12-11 Thread Art Cancro


On 2017-12-11 7:42 AM, Michael Meskes wrote:


Anyone interested in citadel/webcit? If not I'm going to have it removed I 
guess.

There used to be a team maintaining these packages, but I'm the only one who
worked on it in recent years. Not having used the software myself I don't
really intend to spend more time on it and both packages have an RC bug, that
upstream may or may not have fixed.

To explain the latter, upstream claims to have fixed it and their source is
different from ours but the version number is exactly the same!
We patched some of the sources in an attempt to make it work on the 
latest Debian, but that effort seems to have missed the mark.  That 
having been said, we've got everything working with both old and new 
libical versions now, and it seems to build cleanly on both previous and 
current Debian versions.


A new release is forthcoming so if you want to hold tight for a little 
while longer we should be able to smooth things out. Naturally it is up 
to you as package maintainer whether you want to continue to volunteer 
your time -- I totally respect that.