[Bug 1132118] New: Xindy does not run due to incompatible CLISP runtime
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 Bug ID: 1132118 Summary: Xindy does not run due to incompatible CLISP runtime Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: christian-david@web.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- xindy does not run what can be tested with $ xindy --version xindy release: 2.5.1 xindy script version: 1.18 /usr/lib64/clisp-2.49.92/base/lisp.run: initialization file `/usr/lib64/xindy/xindy.mem' was not created by this version of CLISP runtime Same error happens if xindy is used for a “real” task. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 http://bugzilla.opensuse.org/show_bug.cgi?id=1132118#c1 --- Comment #1 from Christian David <christian-david@web.de> --- In the meantime the issue was solved but it returned. Maybe there is some dependency in the spect missing which automatically rebuilds xindy if the CLISP runtime changes? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 http://bugzilla.opensuse.org/show_bug.cgi?id=1132118#c2 Martin Li��ka <martin.liska@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.liska@suse.com --- Comment #2 from Martin Li��ka <martin.liska@suse.com> --- Hm, I noticed the same error, but happens only within a opensuse/tumbleweed container: $ podman run --rm -it opensuse/tumbleweed /bin/bash $ zypper in -y xindy ... $ xindy --version xindy release: 2.5.1 xindy script version: 1.18 /usr/lib64/clisp-2.49.92/base/lisp.run: initialization file `/usr/lib64/xindy/xindy.mem' was not created by this version of CLISP runtime $ zypper info xindy ... Version : 2.5.1-2.15 $ md5sum `which xindy` && md5sum /usr/lib64/clisp-2.49.92/base/lisp.run db0160078250f7753df98b66feb70fc4 /usr/bin/xindy b51f70117c495b7f99b7fc66183be895 /usr/lib64/clisp-2.49.92/base/lisp.run While doing that on my updated TW machine, it's gone: $ xindy --version xindy release: 2.5.1 xindy script version: 1.18 xindy kernel version: 3.0 CLISP version 2.49.92 (2018-02-18) (built on old-cirrus3 [127.0.0.1]) architecture: X86_64 $ md5sum `which xindy` && md5sum /usr/lib64/clisp-2.49.92/base/lisp.run db0160078250f7753df98b66feb70fc4 /usr/bin/xindy b51f70117c495b7f99b7fc66183be895 /usr/lib64/clisp-2.49.92/base/lisp.run -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 http://bugzilla.opensuse.org/show_bug.cgi?id=1132118#c3 --- Comment #3 from Martin Li��ka <martin.liska@suse.com> --- And this file is also identical: md5sum /usr/lib64/xindy/xindy.mem 1ba75fffaad9f0dfdc8c1568e7195487 /usr/lib64/xindy/xindy.mem -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 http://bugzilla.opensuse.org/show_bug.cgi?id=1132118#c4 Jan Engelhardt <jengelh@inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org --- Comment #4 from Jan Engelhardt <jengelh@inai.de> --- Perhaps the xindy package needs to be rebuilt whenever clisp changes. There isn't a good automatism for this as I understand dimstar. Sounds vaguely familiar in spirit: bug 1191150 comment 8. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 http://bugzilla.opensuse.org/show_bug.cgi?id=1132118#c5 --- Comment #5 from Martin Li��ka <martin.liska@suse.com> --- @DimStar: Can you please force rebuilding xindy in Factory in order to verify the theory provided by Jan? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 http://bugzilla.opensuse.org/show_bug.cgi?id=1132118#c6 --- Comment #6 from Martin Li��ka <martin.liska@suse.com> --- (In reply to Jan Engelhardt from comment #4)
Perhaps the xindy package needs to be rebuilt whenever clisp changes. There isn't a good automatism for this as I understand dimstar.
Sounds vaguely familiar in spirit: bug 1191150 comment 8.
Btw. does it explain why I see the problem in a TW container but not on a bare-metal system? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 http://bugzilla.opensuse.org/show_bug.cgi?id=1132118#c7 --- Comment #7 from Martin Li��ka <martin.liska@suse.com> --- Now it's fixed in TW. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 http://bugzilla.opensuse.org/show_bug.cgi?id=1132118#c8 --- Comment #8 from Martin Li��ka <martin.liska@suse.com> --- Well, it fails again when being run in docker: $ zypper info xindy Loading repository data... Reading installed packages... Information for package xindy: ------------------------------ Repository : openSUSE-Tumbleweed-Oss Name : xindy Version : 2.5.1-2.16 ... $ xindy --version xindy release: 2.5.1 xindy script version: 1.18 /usr/lib64/clisp-2.49.92/base/lisp.run: initialization file `/usr/lib64/xindy/xindy.mem' was not created by this version of CLISP runtime -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 http://bugzilla.opensuse.org/show_bug.cgi?id=1132118#c9 Martin Li��ka <martin.liska@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Assignee|jengelh@inai.de |martin.liska@suse.com --- Comment #9 from Martin Li��ka <martin.liska@suse.com> --- I've got the root cause of this issue: [pid 598] execve("/bin/gzip", ["gzip", "-d", "-c"], 0x7fffffffe648 /* 11 vars */) = -1 ENOENT (No such file or directory) [pid 598] exit_group(-1) = ? zypper in -y gzip fixes that! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 http://bugzilla.opensuse.org/show_bug.cgi?id=1132118#c10 --- Comment #10 from Martin Li��ka <martin.liska@suse.com> --- Upstream issue: https://gitlab.com/gnu-clisp/clisp/-/issues/34 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 http://bugzilla.opensuse.org/show_bug.cgi?id=1132118#c11 --- Comment #11 from Martin Li��ka <martin.liska@suse.com> --- SR#1030404 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 http://bugzilla.opensuse.org/show_bug.cgi?id=1132118#c12 --- Comment #12 from OBSbugzilla Bot <bwiedemann+obsbugzillabot@suse.com> --- This is an autogenerated message for OBS integration: This bug (1132118) was mentioned in https://build.opensuse.org/request/show/1031152 Factory / clisp -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 http://bugzilla.opensuse.org/show_bug.cgi?id=1132118#c13 Martin Li��ka <martin.liska@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #13 from Martin Li��ka <martin.liska@suse.com> --- Fixed in devel project. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com