Bug#1146517: libipc-shareable-perl: FTBFS on ppc64el and ppc64: shm_segments() reads the wrong field of struct shmid_ds

Niko Tyni ntyni at debian.org
Sat Oct 24 08:48:59 BST 2026


On Wed, Oct 21, 2026 at 09:00:59PM +0200, gregor herrmann wrote:
> On Mon, 19 Oct 2026 15:55:21 +0200, Edmund Lodewijks wrote:
> 
> > On 2026/10/18 16:31, Niko Tyni wrote:
> > > FWIW I think the IPC::SharedMem approach looks like the right thing to do here.
> > > I also agree with Gregor that the 'IPC::SharedMem::stat'->new->unpack($data)
> > > part in the patch looks a bit out of place and should probably be replaced
> > > with a call to IPC::SharedMem::stat() that does the same thing.
> > As for the Debian situation, I am not sure what should be done. Gregor
> > feels for taking the one patch idea (minimal), you think the other one
> > would be the right thing to do, but perhaps only after a change.
> 
> If Niko suggests to go the IPC::SharedMem path (and if we have one clear
> upstream pull request that can be converted to a clean Debian patch) I'm
> happy to go this way -- that's why I asked for additional opinions from
> people who understand the situation better than me :)

Yeah we don't really disagree on anything here :)

Perhaps a way forward would be

- minimal changes in unstable: add the special case struct offsets for ppc

- try out the IPC::SharedMem approach in experimental

- if /when all goes well in experimental, make an upstream PR for the
  IPC::SharedMem changes

- hopefully switch to IPC::SharedMem in unstable too later, preferably via an
  upstream release of course

I don't think this will be all that hard, Edmund has done the heavy lifting
already. But yeah some attention to details will be needed.

I'll try to tackle this eventually if Gregor (or someone else) doesn't beat
me to it.  Unfortunately my availability is rather limited nowadays and
I've got some other things on my plate as well.
-- 
Niko



More information about the pkg-perl-maintainers mailing list