Arch Linux

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 12,926

[Solved] libfakeroot internal error: payload not recognized!

While building an older version of sane for troubleshooting I noticed the above error during the strip part of the build process. .

I cloned the repo from https://gitlab.archlinux.org/archlinux/ … kages/sane to verify this was still present in latest package.

Both extra-x86_64-build -c and pkgctl build -c give similar output

  -> Stripping unneeded symbols from binaries and libraries...
libfakeroot internal error: payload not recognized!
libfakeroot internal error: payload not recognized!
libfakeroot internal error: payload not recognized!
libfakeroot internal error: payload not recognized!
libfakeroot internal error: payload not recognized!
  -> Compressing man and info pages...

These messages are only visible in terminal output and not in any logs .

Disabling debug-build by adding options=(!debug) to the PKGBUILD gets rid of the messages .

In https://bbs.archlinux.org/viewtopic.php … 8#p2190698 about building libivirt arojas mentioned this was a packaging bug caused by a missing dependency .

I would like to file a bug report for archlinux sane package , but unfortunately I have no idea which dep is missing.

Build log is at http://0x0.st/XYGw.txt

Last edited by Lone_Wolf (2024-09-27 09:21:40)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

loqs

Member

Registered: 2014-03-06

Posts: 18,032

Re: [Solved] libfakeroot internal error: payload not recognized!

Please see https://gitlab.archlinux.org/archlinux/ … ote_205205.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 12,926

Re: [Solved] libfakeroot internal error: payload not recognized!

So the message is caused by upstream changes in fakeroot and appears to be a harmless waning.

Thank you for pointing to the relevant bug report.
Declaring Solved.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky