Bug#707018: Status of KDE 4.10 transition

[Luk Claes <luk@zomers.be>]

On 08/25/2013 02:25 PM, Pino Toscano wrote:
> Hi,
> 
> Alle lunedì 12 agosto 2013, Adam D. Barratt ha scritto:
>> On Mon, 2013-08-12 at 20:08 +0200, Pino Toscano wrote:
>>> Alle domenica 11 agosto 2013, Adam D. Barratt ha scritto:
>>>> On Sun, 2013-07-21 at 14:10 +0200, Pino Toscano wrote:
>>>>> That said, we are tackling few issues/regressions (mostly in
>>>>> the new pim stack), so could it be possible to hold the
>>>>> kde4libs migration with a block for now? (It should avoid all
>>>>> the rest to migrate too.)
>>>>
>>>> What's the current status here?
>>>
>>> Regarding the rest, I'm sure Sune could give an update of the
>>> status.
>>
>> In terms of RC bugs, the only issues I could see are a couple of
>> FTBFS - tagua and kdenetwork. tagua is leaf, so could be removed
>> until it's fixed. kdenetwork appears to be tied up with another
>> transition but AIUI isn't part of the core transition so shouldn't
>> block the majority of packages from migrating.
> 
> IIRC kdenetwork is tied with kde-workspace.
>
>> We're now hitting a month since the transition started in unstable.
>> I'm wary that we don't let perfect be the enemy of "perfectly
>> reasonable" here. It's early in the cycle and if any remaining
>> issues aren't critical then could we get the current set of packages
>> migrated and work on the final polishing afterwards?
> 
> We had (and still have) regressions (from minor to potentially important 
> as #717040) in kmail. I asked Sune to take a look at bugs, and he did 
> nothing.
> 
> So, given that things are getting stuck because of us, I'm getting 
> prodded in different channels, different new transitions are coming up, 
> and I don't have time/experience to debug the aforementioned issues, I 
> (reluctantly, from my personal POV) ask to unblock kde4libs and let 
> things migrate.
> (You most probably need to either age or remove from testing tagua.)> 

Ok, unblocked kde4libs and aged tagua.

Cheers

Luk