Bug#891872: transition: curl
Control: tags -1 confirmed
On 28/05/18 15:59, Alessandro Ghedini wrote:
> On Mon, May 28, 2018 at 01:09:14PM +0200, Emilio Pozuelo Monfort wrote:
>> Control: tags -1 - confirmed
>>
>> On 23/05/18 13:07, Emilio Pozuelo Monfort wrote:
>>> On 23/04/18 20:38, Emilio Pozuelo Monfort wrote:
>>>> On 01/03/18 22:31, Alessandro Ghedini wrote:
>>>>> Package: release.debian.org
>>>>> Severity: normal
>>>>> User: release.debian.org@packages.debian.org
>>>>> Usertags: transition
>>>>>
>>>>> Hello,
>>>>>
>>>>> I'd like to request a transition for curl in order to unblock the migration
>>>>> to OpenSSL 1.1 (#871056). This is necessary due to the fact that the curl ABI
>>>>> exposes a structure inherited from libssl itself, which was changed in the 1.1
>>>>> update (see #844018 for more information).
>>>>
>>>> I was looking at this in order to ack it. However I've noticed that libcurl4
>>>> conflicts against libcurl3. Why is that? That's going to make the transition
>>>> hard, can it be removed?
>>>>
>>>> Hmm, I just realised libcurl3 ships libcurl.so.4, so that explains the conflict.
>>>> I just found the rationale for this in
>>>> https://salsa.debian.org/debian/curl/merge_requests/2. That means this will have
>>>> to wait until there are no conflicting ongoing transitions. I will ack this when
>>>> that time comes.
>>>
>>> Please go ahead now.
>>>
>>> Since all packages need to migrate at the same time, some NMUs may be needed to
>>> fix potential FTBFS in rdeps. I will notify this bug when the binNMUs are done
>>> and we have a list of failing packages.
>>
>> I've acked the R transition, so let's wait for that now.
>
> Ugh, sorry for the big delay. curl 7.60.0-2 just got accepted (it was stuck in
> NEW due to the fact I had to upload a new version to sid last week to fix
> security issues so the experimental upload got removed, and I didn't make it in
> time to clear 7.60.0 with the migration changes through experimental).
>
> This is totally my fault, I should have notified you about that when I did the
> upload. I hope this doesn;t cause you too much of a pain. Is there anything I
> can do to fix this?
No problem, I didn't notice that it was back in NEW, otherwise I would have
asked for fast processing.
Thankfully we didn't end up with both this and the R transition starting at the
same time, which would have caused me quite some headaches.
Let's go with this. I'll schedule the binNMUs soon.
Cheers,
Emilio
Reply to: