On 14/07/14 09:05, Niko Tyni wrote:
> On Sun, Jul 13, 2014 at 01:27:37PM +0200, Emilio Pozuelo Monfort wrote:
>> On 13/07/14 13:04, Julien Cristau wrote:
>>> On Sat, Jul 5, 2014 at 11:45:16 +0200, Emilio Pozuelo Monfort wrote:
>>>
>>>> I have thought a bit more about this. I was hesitant as there are lots of
>>>> packages involved, but thinking more about it, this should be pretty
>>>> smooth. You
>>>> add perlapi-5.18.2d to perl-base's Provides, but you won't remove
>>>> perlapi-5.18.1
>>>> or perlapi-5.18.2. Then perl-base can migrate immediately, and all the
>>>> rebuilds
>>>> can migrate as well. Then after the rebuilds are done, you can remove
>>>> perlapi-5.18.1 and perlapi-5.18.2 from Provides.
>>>>
>>> perl 5.18.2-6 is now in jessie, so AFAICT it should be fine to drop the
>>> old Provides on s390x at this point.
>>
>> Yes, but the seven packages that haven't been rebuilt will be a problem,
>> unless
>> we can drop them from testing. So fixing those or checking if they can be
>> dropped will be good.
>
> libapache2-mod-perl2 is OK in sid now, and we have a fix for xacobeo.
>
> So can I go ahead with dropping perlapi-5.18.2 or do we need to dig in
> the libimager-perl/libpng problem first?
If you're ok with removing libimager-perl, libimager-qrcode-perl and
libmojomojo-perl from testing if those don't get fixed in time, then yes.
As for sereal, we'd need to remove libsereal-{en,de}coder-perl,
libsession-storage-secure-perl and libdancer-session-cookie-perl.
Emilio
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
