Your message dated Fri, 25 Apr 2025 06:48:29 +0000
with message-id <e1u8crn-003den...@fasolo.debian.org>
and subject line Bug#1095937: Removed package(s) from unstable
has caused the Debian Bug report #1097825,
regarding ruby3.1: ftbfs with GCC-15
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.)
--
1097825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby3.1
Version: 3.1.2-8.5
Severity: important
Tags: sid forky
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-15
[This bug is NOT targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-15/g++-15, but succeeds to build with gcc-14/g++-14. The
severity of this report will be raised before the forky release.
The full build log can be found at:
http://qa-logs.debian.net/2025/02/16/amd64exp/ruby3.1_3.1.2-8.5_unstable_gccexp.log.gz
The last lines of the build log are at the end of this report.
To build with GCC 15, either set CC=gcc-15 CXX=g++-15 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
GCC 15 now defaults to the C23/C++23 standards, exposing many FTBFS.
Other Common build failures are new warnings resulting in build failures
with -Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-15/porting_to.html
[...]
| |
| VALUE (*)(VALUE, VALUE) {aka
long unsigned int (*)(long unsigned int, long unsigned int)}
file.c:6512:52: note: expected ‘VALUE (*)(void)’ {aka ‘long unsigned int
(*)(void)’} but argument is of type ‘VALUE (*)(VALUE, VALUE)’ {aka ‘long
unsigned int (*)(long unsigned int, long unsigned int)’}
6512 | define_filetest_function(const char *name, VALUE (*func)(ANYARGS), int
argc)
| ~~~~~~~~^~~~~~~~~~~~~~
file.c:2121:1: note: ‘rb_file_suid_p’ declared here
2121 | rb_file_suid_p(VALUE obj, VALUE fname)
| ^~~~~~~~~~~~~~
file.c:6731:41: error: passing argument 2 of ‘define_filetest_function’ from
incompatible pointer type [-Wincompatible-pointer-types]
6731 | define_filetest_function("setgid?", rb_file_sgid_p, 1);
| ^~~~~~~~~~~~~~
| |
| VALUE (*)(VALUE, VALUE) {aka
long unsigned int (*)(long unsigned int, long unsigned int)}
file.c:6512:52: note: expected ‘VALUE (*)(void)’ {aka ‘long unsigned int
(*)(void)’} but argument is of type ‘VALUE (*)(VALUE, VALUE)’ {aka ‘long
unsigned int (*)(long unsigned int, long unsigned int)’}
6512 | define_filetest_function(const char *name, VALUE (*func)(ANYARGS), int
argc)
| ~~~~~~~~^~~~~~~~~~~~~~
file.c:2140:1: note: ‘rb_file_sgid_p’ declared here
2140 | rb_file_sgid_p(VALUE obj, VALUE fname)
| ^~~~~~~~~~~~~~
file.c:6732:41: error: passing argument 2 of ‘define_filetest_function’ from
incompatible pointer type [-Wincompatible-pointer-types]
6732 | define_filetest_function("sticky?", rb_file_sticky_p, 1);
| ^~~~~~~~~~~~~~~~
| |
| VALUE (*)(VALUE, VALUE) {aka
long unsigned int (*)(long unsigned int, long unsigned int)}
file.c:6512:52: note: expected ‘VALUE (*)(void)’ {aka ‘long unsigned int
(*)(void)’} but argument is of type ‘VALUE (*)(VALUE, VALUE)’ {aka ‘long
unsigned int (*)(long unsigned int, long unsigned int)’}
6512 | define_filetest_function(const char *name, VALUE (*func)(ANYARGS), int
argc)
| ~~~~~~~~^~~~~~~~~~~~~~
file.c:2159:1: note: ‘rb_file_sticky_p’ declared here
2159 | rb_file_sticky_p(VALUE obj, VALUE fname)
| ^~~~~~~~~~~~~~~~
file.c:6734:44: error: passing argument 2 of ‘define_filetest_function’ from
incompatible pointer type [-Wincompatible-pointer-types]
6734 | define_filetest_function("identical?", rb_file_identical_p, 2);
| ^~~~~~~~~~~~~~~~~~~
| |
| VALUE (*)(VALUE, VALUE,
VALUE) {aka long unsigned int (*)(long unsigned int, long unsigned int, long
unsigned int)}
file.c:6512:52: note: expected ‘VALUE (*)(void)’ {aka ‘long unsigned int
(*)(void)’} but argument is of type ‘VALUE (*)(VALUE, VALUE, VALUE)’ {aka
‘long unsigned int (*)(long unsigned int, long unsigned int, long unsigned
int)’}
6512 | define_filetest_function(const char *name, VALUE (*func)(ANYARGS), int
argc)
| ~~~~~~~~^~~~~~~~~~~~~~
file.c:2188:1: note: ‘rb_file_identical_p’ declared here
2188 | rb_file_identical_p(VALUE obj, VALUE fname1, VALUE fname2)
| ^~~~~~~~~~~~~~~~~~~
In file included from ./include/ruby/ruby.h:26,
from ./include/ruby/encoding.h:19,
from encindex.h:14,
from file.c:156:
./include/ruby/internal/anyargs.h:287:135: error: passing argument 3 of
‘rb_define_method_m3’ from incompatible pointer type
[-Wincompatible-pointer-types]
287 | #define rb_define_method(klass, mid, func, arity)
RBIMPL_ANYARGS_DISPATCH_rb_define_method((arity), (func))((klass), (mid),
(func), (arity))
|
^~~~~~
|
|
|
__attribute__((noreturn)) VALUE (*)(int, const VALUE *, VALUE, VALUE) {aka
__attribute__((noreturn)) long unsigned int (*)(int, const long unsigned int
*, long unsigned int, long unsigned int)}
file.c:6926:5: note: in expansion of macro ‘rb_define_method’
6926 | rb_define_method(rb_cStat, "birthtime", rb_stat_birthtime, 0);
| ^~~~~~~~~~~~~~~~
./include/ruby/internal/anyargs.h:276:21: note: expected ‘VALUE (*)(void)’ {aka
‘long unsigned int (*)(void)’} but argument is of type
‘__attribute__((noreturn)) VALUE (*)(int, const VALUE *, VALUE, VALUE)’ {aka
‘__attribute__((noreturn)) long unsigned int (*)(int, const long unsigned int
*, long unsigned int, long unsigned int)’}
276 | RBIMPL_ANYARGS_DECL(rb_define_method, VALUE, const char *)
| ^~~~~~~~~~~~~~~~
./include/ruby/internal/anyargs.h:251:41: note: in definition of macro
‘RBIMPL_ANYARGS_DECL’
251 | RBIMPL_ANYARGS_ATTRSET(sym) static void sym ## _m3(__VA_ARGS__,
VALUE(*)(ANYARGS), int); \
| ^~~
In file included from ./include/ruby/internal/anyargs.h:77:
./include/ruby/internal/intern/vm.h:403:7: note: ‘rb_f_notimplement’ declared
here
403 | VALUE rb_f_notimplement(int argc, const VALUE *argv, VALUE obj, VALUE
marker);
| ^~~~~~~~~~~~~~~~~
make[2]: *** [Makefile:434: file.o] Error 1
make[2]: Leaving directory '/build/reproducible-path/ruby3.1-3.1.2'
dh_auto_build: error: make -j8 main V=1 returned exit code 2
make[1]: *** [debian/rules:114: override_dh_auto_build-arch] Error 25
make[1]: Leaving directory '/build/reproducible-path/ruby3.1-3.1.2'
make: *** [debian/rules:92: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Version: 3.1.2-8.5+rm
Dear submitter,
as the package ruby3.1 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1095937
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
