Bug#753542: Bug#753444: Bug#753542: perl-base - Segfaults in libperl.so.5.18
On 05/07/14 08:48, Niko Tyni wrote:
> On Sat, Jul 05, 2014 at 02:27:02AM +0200, Emilio Pozuelo Monfort wrote:
>> Although I would prefer to wait a bit and do 5.20 directly, I'm not affected by
>> this breakage as I don't have any s390x machines. So if you think this is
>> important enough, we could go ahead and do it now. The only conflict I see right
>> now is gdal with the poppler transition, but that one should be finished in two
>> or three days if everything goes well.
>
> Thanks. I don't use s390x either, but clearly there are people who do, and
> broken upgrades for a few weeks don't seem acceptable to me.
>
> So do I wait until poppler is done? Please ping me when it's OK to upload.
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.
> What do we do with packages that fail to build? Remove the old s390x
> binaries from testing? The source packages are going to cause trouble
> for the 5.20 transition too, of course...
For leaf packages, we could possibly remove them. But why not just fix them
wherever possible? Do you expect many FTBFS?
Emilio
Reply to: