Your message dated Sat, 25 Jan 2025 14:36:51 +0100
with message-id <[email protected]>
and subject line Re: Bug#1094002: shutdown: restarts under openrc
has caused the Debian Bug report #1094003,
regarding gworkspace: FTBFS with the GNUstep multiarch layout: configure error
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.)
--
1094003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094003
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gworkspace
Version: 1.0.0-4
Severity: important
Tags: sid trixie ftbfs pending
Control: block 1093620 with -1
Control: block -1 with 1093950 1093995
User: [email protected]
Usertags: gnustep-multiarch
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --enable-gwmetadata
--with-sh=/bin/sh --with-unzip=unzip
checking for gcc... x86_64-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether x86_64-linux-gnu-gcc accepts -g... yes
checking for x86_64-linux-gnu-gcc option to enable C11 features... none needed
checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E
configure: error: You are running configure with the compiler
(x86_64-linux-gnu-gcc) set to a different value from that used by gnustep-make
(gcc). Please run configure again with your environment set to match your
gnustep-make
--- End Message ---
--- Begin Message ---
On Fri, 24 Jan 2025 16:42, Mark Hindley <[email protected]> wrote:
Control: tags -1 moreinfo
Matthias,
Thanks for this.
On Fri, Jan 24, 2025 at 03:41:03PM +0100, Matthias Geiger wrote:
Package: sysvinit-core
Version: 3.13-1
Severity: normal
X-Debbugs-Cc: [email protected]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear maintainer,
running sudo /sbin/shutdown now with openrc as service mamanger does not
shut down the machine as expected, but bails out because /etc/inittab.d
does not exist.
Do you have evidence that this is causative?
=======
2025-01-24T15:31:26.820456+01:00 midgard shutdown[4570]: shutting down for
system reboot
2025-01-24T15:31:26.837905+01:00 midgard init: Switching to runlevel: 1
2025-01-24T15:31:26.838058+01:00 midgard init: No inittab.d directory found
To me it looks informational.
I have to admit to finding shutdown(8) less than intuitive and badly named.
For that reason (and habit) I prefer to use poweroff(8) or reboot(8).
But I *think* shutdown is behaving here as intended. If you want to switch off
with shutdown, you have to specify the -h flag.
I have just tried and both of shutdown's -h and -r options seem to do what is
expected.
Hi Mark,
indeed, shutdown -h works as intended. Sorry for the confusion. Maybe a
notice would clarify things better.
best,
werdahias
--- End Message ---
