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

Bug#760050: transition: llvm-toolchain-3.5



On 21/09/2014 13:39, Emilio Pozuelo Monfort wrote:
> On 19/09/14 20:15, Sylvestre Ledru wrote:
>> On 19/09/2014 19:43, Jonathan Wiltshire wrote:
>>> On 2014-09-19 18:22, Jonathan Wiltshire wrote:
>>>> On 2014-09-19 18:03, Sylvestre Ledru wrote:
>>>>> Control: forwarded -1
>>>>> https://release.debian.org/transitions/html/llvm-defaults-3.html
>>>>> On 16/09/2014 19:58, Emilio Pozuelo Monfort wrote:
>>>>>> On 05/09/14 17:47, Emilio Pozuelo Monfort wrote:
>>>>>> Ping? I'm mostly interested in whether the affected packages are in
>>>>>> the tracker, i.e. we don't have 200 packages to transition but less
>>>>>> than a handful.
>>>>> Sorry about the lag.
>>>>> That seems wrong to me.
>>>>> apt-rdepends -r libllvm3.4
>>>>> suggests more packages like mesa, python-llvm, gambas, etc
>>>>>
>>>>> However, I am not a specialist of transition. So, it might be just
>>>>> me :)
>>>> I think the problem is here:
>>>>
>>>> /lib(clang1-3.5|libllvm3.5)/
>>>>
>>>> i.e. liblibllvm3.5
>>>>
>>>> I'll play with the tracker and see what happens.
>>> Ok, this seems to come out with sensible results:
>>>
>>> is_good = .depends ~ /lib(clang1-3.5|llvm3.5)/ | .depends ~
>>> /python-clang-3.5/;
>>> is_bad = .depends ~ /lib(clang1-3.4|llvm3.4)/ | .depends ~
>>> /python-clang-3.4/;
>>>
>>> How does it look to you?
>>>
>> Much better, thanks :)
>>
>>> Some things left on that list is going to need a source upload to fix
>>> dependencies on -3.4 packages, plus llvm-dev switching default
>>> version, if you want 3.4 removing.
>>>
>> yep, business as usual :/
> You initially said you wanted to keep 3.4 for jessie, no? So this is a matter of
> changing the defaults, and then getting a few packages rebuilt and some others
> updating their (build-)dependencies. Isn't that the case anymore? Can you
> explain the plan here in detail?
>
>
I haven't change my plan but I would like as many as possible packages
to switch to 3.5 :)

Sorry for the confusion, that is probably my fault!

S


Reply to: