Bug#753542: Bug#753444: Bug#753542: perl-base - Segfaults in libperl.so.5.18
On Sat, Jul 05, 2014 at 02:27:02AM +0200, Emilio Pozuelo Monfort wrote:
> On 03/07/14 19:50, Aurelien Jarno wrote:
> > On Thu, Jul 03, 2014 at 07:43:57PM +0300, Niko Tyni wrote:
> >> I could make a sourceful perl upload incrementing perlapi-5.18.2 to
> >> for instance perlapi-5.18.2d (and removing perlapi-5.18.1) on s390x
> >> only. This would make ~500 reverse dependencies of perlapi-5.18.*
> >> uninstallable and require a new binNMU round for them. As libperl5.18
> >> has a tight dependency on perl-base, I don't think we'd need to
> >> do anything on the libperl side.
> >
> > I think this would work fine. From the buildds point of view, the 500
> > binNMUs should not pose any problem, we have enough build power there.
> >
> >> I think this would be the right way fix this, but I suppose it would
> >> affect ongoing transitions and the like. I'm cc'ing the release team
> >> for advice.
>
> I have come up with:
>
> https://release.debian.org/transitions/html/perlapi-5.18.2d-s390x.html
>
> 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.
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...
--
Niko Tyni ntyni@debian.org
Reply to: