Bug 673206 – app-crypt/johntheripper-1.7.9-r11 : * Failed to set XATTR_PAX markings -mre /var/tmp/portage/app-crypt/johntheripper-1.7.9-r11/image/usr/sbin/john.

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description Toralf Förster 2018-12-15 19:47:49 UTC]

 * XATTR_PAX marking -mr /var/tmp/portage/app-crypt/johntheripper-1.7.9-r11/image/usr/sbin/john with paxctl-ng
 * XATTR_PAX marking -mre /var/tmp/portage/app-crypt/johntheripper-1.7.9-r11/image/usr/sbin/john with setfattr
 * Failed to set XATTR_PAX markings -mre /var/tmp/portage/app-crypt/johntheripper-1.7.9-r11/image/usr/sbin/john.
 * ERROR: app-crypt/johntheripper-1.7.9-r11::gentoo failed (install phase):
 *   (no error message)
 * 

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.0-no-multilib-hardened_20181207-161146

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-7.3.1
 [2] x86_64-pc-linux-gnu-8.2.0 *

Available Python interpreters, in order of preference:
  [1]   python3.7
  [2]   python3.6
  [3]   python2.7 (fallback)
  [4]   pypy (fallback)
Available Ruby profiles:
  [1]   ruby23 (with Rubygems)
  [2]   ruby24 (with Rubygems) *
  [3]   ruby25 (with Rubygems)

java-config:
The following VMs are available for generation-2:


emerge -qpvO app-crypt/johntheripper
[ebuild  N    ] app-crypt/johntheripper-1.7.9-r11  USE="openmp -cuda -custom-cflags -libressl -minimal -mozilla -mpi -opencl" CPU_FLAGS_X86="sse2 (-mmx)"

[Comment 1 Toralf Förster 2018-12-15 19:47:52 UTC]

Created attachment 557846 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2018-12-15 19:47:54 UTC]

Created attachment 557848 [details]
app-crypt:johntheripper-1.7.9-r11:20181215-012548.log

[Comment 3 Toralf Förster 2018-12-15 19:47:57 UTC]

Created attachment 557850 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2018-12-15 19:48:00 UTC]

Created attachment 557852 [details]
environment

[Comment 5 Toralf Förster 2018-12-15 19:48:03 UTC]

Created attachment 557854 [details]
etc.portage.tbz2

[Comment 6 Toralf Förster 2018-12-15 19:48:06 UTC]

Created attachment 557856 [details]
temp.tbz2

[Comment 7 Alexander Bezrukov 2018-12-18 17:39:10 UTC]

I have just faced this bug. Removing the "|| die" part in
pax-mark -mr "${ED}usr/sbin/john" || die
obviously worked around the issue.

[Comment 8 Keith Harrison 2018-12-19 03:45:01 UTC]

This seems to also affect app-crypt/johntheripper-jumbo-1.8.0

[Comment 9 Alexander Bezrukov 2018-12-19 21:08:28 UTC]

(In reply to Keith Harrison from comment #8)
> This seems to also affect app-crypt/johntheripper-jumbo-1.8.0

No, it doesn't. There is no die command in the -jumbo ebuilds in pax-marking.

[Comment 10 Keith Harrison 2018-12-23 06:52:27 UTC]

(In reply to Alexander Bezrukov from comment #9)
> (In reply to Keith Harrison from comment #8)
> > This seems to also affect app-crypt/johntheripper-jumbo-1.8.0
> 
> No, it doesn't. There is no die command in the -jumbo ebuilds in pax-marking.

At the time, it was failing with exactly the same error, so I don't believe you are correct to dismiss it so easily.

Whatever the issue was, it was resolved shortly after my initial comment.

[Comment 11 Alexander Bezrukov 2018-12-23 13:46:30 UTC]

(In reply to Keith Harrison from comment #10)
> (In reply to Alexander Bezrukov from comment #9)
> > (In reply to Keith Harrison from comment #8)
> > > This seems to also affect app-crypt/johntheripper-jumbo-1.8.0
> > 
> > No, it doesn't. There is no die command in the -jumbo ebuilds in pax-marking.
> 
> At the time, it was failing with exactly the same error, so I don't believe
> you are correct to dismiss it so easily.
> 
> Whatever the issue was, it was resolved shortly after my initial comment.

To dismiss it so easily, I checked git history.

[Comment 12 Agostino Sarubbo 2020-09-04 08:09:14 UTC]

*** Bug 685556 has been marked as a duplicate of this bug. ***