Your message dated Thu, 10 Sep 2020 01:04:31 +0000 with message-id <[email protected]> and subject line Bug#966353: fixed in lilypond 2.20.0-2 has caused the Debian Bug report #966353, regarding FTBFS: guile segfaults when run to collect docs to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 966353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966353 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: lilypond Version: 2.20.0-1 Severity: serious Justification: FTBFS Dear Maintainer, When trying to rebuild lilypond (before investigating whether the build could be ported to Python 3), I found that the package currently FTBFS. Appropriate section of the log file is as follows: cat alist.doc arbiters.doc async.doc backtrace.doc boolean.doc chars.doc continuations.doc debug.doc deprecation.doc deprecated.doc discouraged.doc dynl.doc dynwind.doc environments.doc eq.doc error.doc eval.doc evalext.doc extensions.doc feature.doc fluids.doc fports.doc futures.doc gc.doc goops.doc gsubr.doc gc-mark.doc gc-segment.doc gc-malloc.doc gc-card.doc guardians.doc hash.doc hashtab.doc hooks.doc i18n.doc init.doc ioext.doc keywords.doc lang.doc list.doc load.doc macros.doc mallocs.doc modules.doc numbers.doc objects.doc objprop.doc options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc properties.doc random.doc rdelim.doc read.doc root.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc stackchk.doc stacks.doc stime.doc strings.doc srfi-4.doc srfi-13.doc srfi-14.doc strorder.doc strports.doc struct.doc symbols.doc threads.doc throw.doc values.doc variable.doc vectors.doc version.doc vports.doc weaks.doc ramap.doc unif.doc dynl.doc filesys.doc posix.doc net_db.doc socket.doc regex-posix.doc | GUILE="/build/lilypond-jv5Dao/lilypond-2.20.0/guile18/pre-inst-guile" ../scripts/snarf-check-and-output-texi > guile-procedures.texi || { rm guile-procedures.texi; false; } /bin/bash: line 1: 15186 Broken pipe cat alist.doc arbiters.doc async.doc backtrace.doc boolean.doc chars.doc continuations.doc debug.doc deprecation.doc deprecated.doc discouraged.doc dynl.doc dynwind.doc environments.doc eq.doc error.doc eval.doc evalext.doc extensions.doc feature.doc fluids.doc fports.doc futures.doc gc.doc goops.doc gsubr.doc gc-mark.doc gc-segment.doc gc-malloc.doc gc-card.doc guardians.doc hash.doc hashtab.doc hooks.doc i18n.doc init.doc ioext.doc keywords.doc lang.doc list.doc load.doc macros.doc mallocs.doc modules.doc numbers.doc objects.doc objprop.doc options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc properties.doc random.doc rdelim.doc read.doc root.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc stackchk.doc stacks.doc stime.doc strings.doc srfi-4.doc srfi-13.doc srfi-14.doc strorder.doc strports.doc struct.doc symbols.doc threads.doc throw.doc values.doc variable.doc vectors.doc version.doc vports.doc weaks.doc ramap.doc unif.doc dynl.doc filesys.doc posix.doc net_db.doc socket.doc regex-posix.doc 15187 Segmentation fault | GUILE="/build/lilypond-jv5Dao/lilypond-2.20.0/guile18/pre-inst-guile" ../scripts/snarf-check-and-output-texi > guile-procedures.texi make[5]: *** [Makefile:2689: guile-procedures.texi] Error 1 make[5]: Leaving directory '/build/lilypond-jv5Dao/lilypond-2.20.0/guile18/libguile' make[4]: *** [Makefile:799: all] Error 2 make[4]: Leaving directory '/build/lilypond-jv5Dao/lilypond-2.20.0/guile18/libguile' make[3]: *** [Makefile:668: all-recursive] Error 1 make[3]: Leaving directory '/build/lilypond-jv5Dao/lilypond-2.20.0/guile18' make[2]: *** [Makefile:511: all] Error 2 make[2]: Leaving directory '/build/lilypond-jv5Dao/lilypond-2.20.0/guile18' make[1]: *** [debian/rules:102: override_dh_auto_configure] Error 2 make[1]: Leaving directory '/build/lilypond-jv5Dao/lilypond-2.20.0' make: *** [debian/rules:94: build] Error 2 guile segfaults as soon as it is started (with or without docs on stdin). The backtrace is as follows in case the problem jumps out. /build/lilypond-jv5Dao/lilypond-2.20.0/guile18/libguile/.libs$ LD_LIBRARY_PATH=. gdb ./guile Reading symbols from ./guile... (gdb) r Starting program: /build/lilypond-jv5Dao/lilypond-2.20.0/guile18/libguile/.libs/guile Program received signal SIGSEGV, Segmentation fault. scm_mark_locations (x=0x7fffffffe948, n=18446744073709551562) at gc-mark.c:435 435 SCM obj = * (SCM *) &x[m]; (gdb) bt #0 scm_mark_locations (x=0x7fffffffe948, n=18446744073709551562) at gc-mark.c:435 #1 0x00007ffff7f5edcd in scm_threads_mark_stacks () at threads.c:1408 #2 0x00007ffff7f178a8 in scm_mark_all () at gc-mark.c:82 #3 0x00007ffff7f171cb in scm_i_gc (what=what@entry=0x7ffff7f7a43f "cells") at gc.c:596 #4 0x00007ffff7f173a9 in scm_gc_for_newcell ( freelist=0x7ffff7fadd60 <scm_i_master_freelist2>, free_cells=0x555555559300) at gc.c:507 #5 0x00007ffff7f48e1c in scm_double_cell (cdr=140737348583488, ccr=7051895308, cbr=93824992284640, car=5) at ../libguile/inline.h:201 #6 scm_i_c_make_symbol (name=name@entry=0x7ffff7f7e3ff "caaadr", len=len@entry=6, flags=flags@entry=0, hash=hash@entry=7051895308, props=0x7ffff7ab4040) at strings.c:436 #7 0x00007ffff7f5d83a in scm_i_c_mem2symbol (name=name@entry=0x7ffff7f7e3ff "caaadr", len=6) at symbols.c:150 #8 0x00007ffff7f5dc45 in scm_from_locale_symbol (sym=sym@entry=0x7ffff7f7e3ff "caaadr") at symbols.c:388 #9 0x00007ffff7f3afac in scm_c_make_subr (name=0x7ffff7f7e3ff "caaadr", type=type@entry=93, fcn=<optimized out>) at procs.c:69 #10 0x00007ffff7f3b047 in scm_c_define_subr (name=<optimized out>, type=type@entry=93, fcn=<optimized out>) at procs.c:80 #11 0x00007ffff7f34da2 in scm_init_pairs () at pairs.c:197 #12 0x00007ffff7f25119 in scm_i_init_guile (base=base@entry=0x7fffffffe948) at init.c:485 #13 0x00007ffff7f5eb90 in scm_i_init_thread_for_guile (parent=0x0, base=0x7fffffffe948) at threads.c:590 #14 scm_i_init_thread_for_guile (base=0x7fffffffe948, parent=0x0) at threads.c:573 #15 0x00007ffff7f5ebfb in scm_i_with_guile_and_parent ( func=func@entry=0x7ffff7f24ea0 <invoke_main_func>, data=data@entry=0x7fffffffe970, parent=<optimized out>) at threads.c:732 #16 0x00007ffff7f5ec4c in scm_with_guile (func=func@entry=0x7ffff7f24ea0 <invoke_main_func>, data=data@entry=0x7fffffffe970) at threads.c:721 #17 0x00007ffff7f24fb5 in scm_boot_guile (argc=<optimized out>, argv=<optimized out>, main_func=<optimized out>, closure=<optimized out>) at init.c:350 #18 0x0000555555555072 in main (argc=<optimized out>, argv=<optimized out>) at guile.c:63 regards Stuart
--- End Message ---
--- Begin Message ---Source: lilypond Source-Version: 2.20.0-2 Done: Anthony Fok <[email protected]> We believe that the bug you reported is fixed in the latest version of lilypond, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anthony Fok <[email protected]> (supplier of updated lilypond package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Wed, 09 Sep 2020 15:41:38 -0600 Source: lilypond Architecture: source Version: 2.20.0-2 Distribution: unstable Urgency: medium Maintainer: Anthony Fok <[email protected]> Changed-By: Anthony Fok <[email protected]> Closes: 966353 968993 969723 Changes: lilypond (2.20.0-2) unstable; urgency=medium . * Patch Guile-1.8 to the latest branch_release-1-8 branch found in Guile git repository on Savannah, see patches 1801 to 1825. In particular, 1812-Fix-stack-growth-direction-check.patch, originally written for Autoconf by Paul Eggert for Autoconf and pulled into Guile-2.0 in 2011, fixed a build error with -O3 back then, and fixes FTBFS with gcc-10 nowadays, due to a bug in find_stack_direction() code in configure.in. See http://lists.gnu.org/archive/html/bug-autoconf/2011-06/msg00035.html for the whole story. (Closes: #966353) * Call /usr/share/dh-python/dh_python2 directly in debian/rules since /usr/bin/dh_python2 was removed * This rebuild allows dh_python2 to generate the now correct dependency on python2:all instead of python:all (Closes: #969723) * Add debian/patches/.gitignore to re-include *.patch files which were excluded by upstream .gitignore file * scm: disable embedded-ps and embedded-svg in -dsafe mode, CVE-2020-17353. This is a cherry-pick of upstream's fix, see http://git.savannah.gnu.org/cgit/lilypond.git/commit/?id=b84ea47 (Closes: #968993) * Take over as Maintainer from Don Armstrong as suggested by Don. Thank you Don for your many years of great work, and we look forward to your continued contributions as co-maintainer for many years to come! Checksums-Sha1: dd6ae02f1927e17fc6b035778ef711586de07164 4232 lilypond_2.20.0-2.dsc 4e8aeaa83c3d93512fe123c3be48c58474092f91 78576 lilypond_2.20.0-2.debian.tar.xz 89568c4fd1ce8964625b09fa95ca565818daba5d 22259 lilypond_2.20.0-2_amd64.buildinfo Checksums-Sha256: bf3afa1df413d87d6e18601b202288b882552a3675eaa3c87e90f8d78c686c45 4232 lilypond_2.20.0-2.dsc 0163362634c2b95bc2d38b92d7076f91993306051c63f31ab6962018751d7ff6 78576 lilypond_2.20.0-2.debian.tar.xz bf4f7fcf8160481916bf2198dbf878bb298a7b4e40a944a58af02a768a5ebf5b 22259 lilypond_2.20.0-2_amd64.buildinfo Files: fb24ebf0ff02c889187ef45d43006cbf 4232 tex optional lilypond_2.20.0-2.dsc b9367e2287985e28896aa628c32906f4 78576 tex optional lilypond_2.20.0-2.debian.tar.xz a5e4f3a4cc4e4469eb8d6e00b9bf406b 22259 tex optional lilypond_2.20.0-2_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAl9ZdmAACgkQ6iUAtBLF ms97+w/+P/Qb3ZneY4ZAbpqa4EOmq1rmYE7OPryPakqCG2BwmxtSahc58mN11Se1 M//YWxFwpklX1cwvgCFS2sh/1gQsWRwVPDqs3a1v/axHZBBBaoPCT1utxpLu51WR NvY5oQPsu14HL6XLDTD+7b7Kw2wHeKw+lj2rXYmLwdCmfuWxKhGBpBTlL65Gq5Ll kRTSmkBdLeV/Actfk1hoieww5+EUfs+4YswqOeprsj7QIASWKAt7I0kNQQ/w6JbO vSeaGJkS8HiINR3OZWP8rD9NzZdiS/k6KWP+aOiDXSd6TbANKpGhWUAeI5Ues8aR yUq7JI6hMT/hWLDgQ6Ywm48APX9YopEpWPph+EHnEQUDeunOr7ABtULTrlZpDJ7G Ti87EpndSV4tAOVyqN7oWt6+9XOQUEdVrcdOjbXui9eEgc/Y8qpwCsP8hAMayhmG KY10WIt/pInUDBAUk4fjcTywvZcyylT31tsaR0dHzsfhz/pJKG2b7XR7v12Q1u7S UOXbSZP8SYqviANiB/iqbFMlN4q/PYaeYKGk7WXad0zQ12Es7a1hcIWp/BS0J2KY 2hpWnwVypXXMB0Ncvdl4ZvqgottjW6AYAO6qp/tXSeSGISUh4HTDqmhGJWR3iZj3 4AQ4GS5HyAwrqnBW4JiuOXJd8n0H4JhKZ1HJcX0kHAF49+yGwYw= =w6A8 -----END PGP SIGNATURE-----
--- End Message ---
