[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#873411: kdevelop: Please update to llvm-toolchain 4.0 or, better, 5.0



Control: severity -1 serious

On Wed, 06 Sep 2017 21:34:47 +0200 Pino Toscano <pino@debian.org> wrote:
> Hi,
> 
> In data domenica 27 agosto 2017 16:01:25 CEST, Sylvestre Ledru ha scritto:
> > Source: kdevelop
> > Severity: normal
> > 
> > Hello,
> > 
> > Currently, we have 6 versions of the llvm toolchain in the archive.
> > I would like to move to 3 versions (4.0, 5.0 and snapshot, aka 6.0)
> > 
> > Could you please update your package to use 4.0 (or, better, 5.0 which will be released very 
> > soon)?
> 
> Sure, but only after the versions available build and work at least on
> all the release architectures.  So far, llvm 3.9 is still affected by
> #866354, since it did not build fine again since then -- this is
> holding kdevelop in unstable for more than 2 months, and I really would
> like to get it into testing.
> 
> I see that each of the llvm sources has various bugs, FTBFSes, cmake
> issues, and so forth... as a suggestion from a bystander, what about
> focusing on at most 3 versions of llvm in the archive, instead of
> upload every version available (and then have to cleanup llvm users
> periodically, like with bugs like this)?
> 
> > I will update the severity of this bug at the end of September
> 
> Doing that with the current state of llvm versions would be a bad idea.

It should be fine now with 4.0. Would be good if this could move to either
unversioned llvm/clang (which defaults to 4.0 now) or to versioned 4.0. Bumping
to serious as we want to remove 3.8 soon to reduce the high number of llvm
versions that we currently ship.

Cheers,
Emilio


Reply to: