Hi,

On Thu, May 31, 2018 at 12:58:04PM +0200, Yllman, Jens wrote:
> I do not know for sure what Onur is doing at the moment. I am looking
> into helping with this package as it is important to me. And I really
> want newer libclang support for c++17 and later. But, my time is not
> that available as I was hoping. :( But my view of this is that in
> testing/unstable where default clang now is 4.0, and both 5.0 and 6.0 is
> available. So it should really handle to connect to any of those.

As mentioned in my first mail to this bugreport I have some
work-in-progress updates for ycmd and vim-youcompleteme on salsa [0]
(unfinished, mostly untested, here be dragons, yada yada), which
includes a change to built against clang-6.0 (as its what upstream
builds against currently)… I could do an NMU with that change, but that
would be just a stopgap solution – I would prefer a more longterm
solution by figuring out what the maintenance status is in general as we
"need" newer upstream versions, changes like python3 and ideally patches
in other packages (upstream depends on a so far unreleased version of
pybind11)… that is better done by a maintainer instead of NMUs.

In practice that means we figure out if Onur is still active and has
some freetime available to work on it. If so, great – I and hopefully
others like you will happily support that if we can with patches or
sponsoring uploads. If not it will eventually end in packages being
orphaned – in that case someone (perhaps me) will hopefully adopt it and
patches and stuff flow in that direction instead.


Best regards

David Kalnischkies

[0] https://salsa.debian.org/donkult/ycmd and vim-youcompleteme forked
from Debian/ycmd (and co) which I imported from alioth collab-maint.

Attachment: signature.asc
Description: PGP signature

Reply via email to