Bug 2332076 - bind PDF documentation does not rebuild on s390x
Summary: bind PDF documentation does not rebuild on s390x
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: texlive-base
Version: 41
Hardware: s390x
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
 
Reported: 2024-12-12 14:08 UTC by Petr Menšík
Modified: 2025-12-16 18:06 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-12-16 18:06:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Petr Menšík 2024-12-12 14:08:38 UTC
My bind f41 branch has failed to build
- https://koji.fedoraproject.org/koji/taskinfo?taskID=126723399

Scratch build on rawhide passed recently.
- https://koji.fedoraproject.org/koji/taskinfo?taskID=126728357

Latexmk: calling xindy( -L english -C utf8  -M sphinx.xdy  -o "Bv9ARM.ind" "Bv9ARM.idx" )
/usr/lib64/clisp-2.49.95+/base/lisp.run: initialization file `/usr/bin/xindy.mem' was not created by this version of CLISP runtime

I am not able to tell which component is responsible exactly. Please change the component as required. But the problem is reproducible.

Reproducible: Always

Steps to Reproduce:
1. fedpkg clone -a rpms/bind
2. cd bind
3. git checkout 0dcd8bfd6d2e5f56a07889f3018a74f8736664f6
4. fedpkg --release f41 mockbuild
Actual Results:  
Only on s390x, it fails reliably.
https://koji.fedoraproject.org/koji/taskinfo?taskID=126723399

Running 'internal xindy -L english -C utf8  -M sphinx.xdy  -o "Bv9ARM.ind" "Bv9ARM.idx"'
------------
Latexmk: calling xindy( -L english -C utf8  -M sphinx.xdy  -o "Bv9ARM.ind" "Bv9ARM.idx" )
/usr/lib64/clisp-2.49.95+/base/lisp.run: initialization file `/usr/bin/xindy.mem' was not created by this version of CLISP runtime
Latexmk: Sometimes, the -f option can be used to get latexmk
  to try to force complete processing.
  But normally, you will need to correct the file(s) that caused the
  error, and then rerun latexmk.
  In some cases, it is best to clean out generated files before rerunning
  latexmk after you've corrected the files.
Latexmk: Errors, so I did not complete making targets
Collected error summary (may duplicate other messages):
  makeindex Bv9ARM.idx: Command for 'makeindex Bv9ARM.idx' gave return code 256
      Refer to 'Bv9ARM.ilg' for details
make[3]: Leaving directory '/builddir/build/BUILD/bind-9.18.31-build/bind-9.18.31/

Expected Results:  
Build passes like on rawhide and f41.

Output written on Bv9ARM.pdf (955 pages).
Transcript written on Bv9ARM.log.
Latexmk: Missing input file 'Bv9ARM.toc' (or dependence on it) from following:
  No file Bv9ARM.toc.
Latexmk: Missing input file 'Bv9ARM.ind' (or dependence on it) from following:
  No file Bv9ARM.ind.
Latexmk: Getting log file 'Bv9ARM.log'
Latexmk: Examining 'Bv9ARM.fls'
Latexmk: Examining 'Bv9ARM.log'
Latexmk: Index file 'Bv9ARM.idx' was written
Latexmk: References changed.
Latexmk: References changed.
Latexmk: References changed.
Latexmk: Log file says output to 'Bv9ARM.pdf'
Have index file 'Bv9ARM.idx', Bv9ARM.ind Bv9ARM
Latexmk: applying rule 'makeindex Bv9ARM.idx'...
Rule 'makeindex Bv9ARM.idx':  Reasons for rerun
Category 'other':
  Rerun of 'makeindex Bv9ARM.idx' forced or previously required:
    Reason or flag: 'Initial set up of rule'
------------
Run number 1 of rule 'makeindex Bv9ARM.idx'
------------
------------
Running 'internal xindy -L english -C utf8  -M sphinx.xdy  -o "Bv9ARM.ind" "Bv9ARM.idx"'
------------
Latexmk: calling xindy( -L english -C utf8  -M sphinx.xdy  -o "Bv9ARM.ind" "Bv9ARM.idx" )
/usr/lib64/clisp-2.49.95+/base/lisp.run: initialization file `/usr/bin/xindy.mem' was not created by this version of CLISP runtime
Latexmk: Sometimes, the -f option can be used to get latexmk
  to try to force complete processing.
  But normally, you will need to correct the file(s) that caused the
  error, and then rerun latexmk.
  In some cases, it is best to clean out generated files before rerunning
  latexmk after you've corrected the files.
Latexmk: Errors, so I did not complete making targets
Collected error summary (may duplicate other messages):
  makeindex Bv9ARM.idx: Command for 'makeindex Bv9ARM.idx' gave return code 256
      Refer to 'Bv9ARM.ilg' for details
make[3]: Leaving directory '/builddir/build/BUILD/bind-9.18.31-build/bind-9.18.31/build/doc/arm/_build/latex'
make[3]: *** [Makefile:29: Bv9ARM.pdf] Error 12
make[2]: *** [Makefile:785: pdf-local] Error 2
make[2]: Leaving directory '/builddir/build/BUILD/bind-9.18.31-build/bind-9.18.31/build/doc/arm'
make[1]: *** [Makefile:452: doc-recursive] Error 1
make[1]: Leaving directory '/builddir/build/BUILD/bind-9.18.31-build/bind-9.18.31/build/doc'
make: *** [Makefile:629: doc-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.Y2DlLz (%build)
RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.Y2DlLz (%build)
Child return code was: 1
EXCEPTION: [Error('Command failed: \n # /usr/bin/systemd-nspawn -q -M f6a2e09ae01841aa826c955c8730d7c4 -D /var/lib/mock/f41-build-side-101920-55537310-6536519/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.rxfgetsy:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin \'--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"\' \'--setenv=PS1=<mock-chroot> \\s-\\v\\$ \' --setenv=LANG=C.UTF-8 --resolv-conf=off bash --login -c \'/usr/bin/rpmbuild -bb --noclean --target s390x --nodeps /builddir/build/SPECS/bind.spec\'\n', 1)]
Traceback (most recent call last):
  File "/usr/lib/python3.13/site-packages/mockbuild/trace_decorator.py", line 93, in trace
    result = func(*args, **kw)
  File "/usr/lib/python3.13/site-packages/mockbuild/util.py", line 610, in do_with_status
    raise exception.Error("Command failed: \n # %s\n%s" % (cmd_pretty(command, env), output), child.returncode)
mockbuild.exception.Error: Command failed: 
 # /usr/bin/systemd-nspawn -q -M f6a2e09ae01841aa826c955c8730d7c4 -D /var/lib/mock/f41-build-side-101920-55537310-6536519/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.rxfgetsy:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin '--setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007"' '--setenv=PS1=<mock-chroot> \s-\v\$ ' --setenv=LANG=C.UTF-8 --resolv-conf=off bash --login -c '/usr/bin/rpmbuild -bb --noclean --target s390x --nodeps /builddir/build/SPECS/bind.spec'

Comment 1 Dan Horák 2024-12-12 14:23:00 UTC
perhaps it's matter of rebuilding xindy somehow, I am going to look ...

Comment 2 Adam Williamson 2025-12-02 01:56:42 UTC
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '41'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 41 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Samyak Jain (RedHat) 2025-12-16 18:06:19 UTC
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.