Bug#1017565: crysal: FTBFS everywhere

[Sebastian Ramacher]

Source: crystal
Version: 1.3.2+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sram...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=crystal&arch=amd64&ver=1.3.2%2Bdfsg-1&stamp=1660695991&raw=0

Failures:

1) Crystal::Loader .parse parses file paths
Failure/Error: expect_raises(Crystal::Loader::LoadError, /#{Dir.current}\/foobar\.o.+(No such file or directory|image not found)/) do

Expected Crystal::Loader::LoadError with message matching /\/build\/crystal-oKAM1A\/crystal-1.3.2+dfsg\/foobar\.o.+(No such file or directory|image not found)/, got #<Crystal::Loader::LoadError: /<<PKGBUILDDIR>>/foobar.o: cannot open shared object file: No such file or directory> with backtrace:
# src/compiler/crystal/loader/unix.cr:59:25 in 'parse:search_paths'
# src/spec/expectations.cr:422:12 in '->'
# src/primitives.cr:266:3 in 'internal_run'
# src/spec/example.cr:33:16 in 'run'
# src/spec/context.cr:18:23 in 'internal_run'
# src/spec/context.cr:337:14 in 'run'
# src/spec/context.cr:18:23 in 'internal_run'
# src/spec/context.cr:337:14 in 'run'
# src/spec/context.cr:18:23 in '->'
# src/array.cr:1273:5 in 'main'
# /lib/x86_64-linux-gnu/libc.so.6 in '??'
# /lib/x86_64-linux-gnu/libc.so.6 in '__libc_start_main'
# .build/compiler_spec in '_start'
# ???

# spec/compiler/loader/unix_spec.cr:31

Finished in 14:37 minutes
10296 examples, 1 failures, 0 errors, 15 pending

Failed examples:

crystal spec spec/compiler/loader/unix_spec.cr:30 # Crystal::Loader .parse parses file paths
make[2]: *** [Makefile:108: compiler_spec] Error 1

Cheers
--
Sebastian Ramacher

[Debian Bug Tracking System]

Your message dated Tue, 11 Oct 2022 18:49:36 +0000
with message-id <E1oiKJs-...@fasolo.debian.org>
and subject line Bug#1017565: fixed in crystal 1.6.0+dfsg-1
has caused the Debian Bug report #1017565,
regarding crysal: FTBFS everywhere
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 ow...@bugs.debian.org
immediately.)


--
1017565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems