Your message dated Wed, 1 Apr 2020 18:01:56 +0300
with message-id <[email protected]>
and subject line Re: Bug#955491: puppet-agent: incorrect mkdir path in
rbconfig.rb
has caused the Debian Bug report #955491,
regarding puppet-agent: incorrect mkdir path in rbconfig.rb
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.)
--
955491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955491
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: puppet-agent
Version: 6.12.0-1buster
Severity: normal
Dear Maintainer,
puppet-agent's bundled rbconfig.rb contains the following line:
CONFIG["MAKEDIRS"] = "/usr/bin/mkdir -p"
however there is no /usr/bin/mkdir on a clean Debian system; mkdir
resides in /bin only. This configuration results in failed build of
native Ruby gems, which use mkmf: mkmf generates the following line into
the native Ruby gem Makefile:
MAKEDIRS = /usr/bin/mkdir -p
Following use of such $MAKEDIRS value results in failed installation,
e.g. for the msgpack gem:
make "DESTDIR=" install
make: /usr/bin/mkdir: Command not found
make: *** [Makefile:200: .sitearchdir.-.msgpack.time] Error 12
make install failed, exit code 2
The behavior can be verified on your system by running
/opt/puppetlabs/puppet/bin/gem install --no-document msgpack
My ruby experience level is low, however based on the above I recommend
to fix the value of CONFIG["MAKEDIRS"] in rbconfig.rb. This would avoid
the failed builds of native gems/extensions.
Thank you for handling this issue.
Best regards
Radek Zajic
-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-8-amd64 (SMP w/28 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages puppet-agent depends on:
ii findutils 4.6.0+git+20190209-2
ii tar 1.30+dfsg-6
puppet-agent recommends no packages.
puppet-agent suggests no packages.
-- Configuration Files:
/etc/puppetlabs/puppet/puppet.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mi, 01 apr 20, 14:42:17, Radek Zajic wrote:
> Package: puppet-agent
> Version: 6.12.0-1buster
> Severity: normal
>
> Dear Maintainer,
Hello,
There is no such package in Debian. Please kindly report this issue to
where you obtained it from.
> puppet-agent's bundled rbconfig.rb contains the following line:
> CONFIG["MAKEDIRS"] = "/usr/bin/mkdir -p"
> however there is no /usr/bin/mkdir on a clean Debian system; mkdir
> resides in /bin only.
Actually on new Debian buster installs 'mkdir' is in /usr/bin/.
https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#merged-usr
As far as I understand from reading various discussions packages should
build correctly regardless if the build system is "usrmerged" or not, so
this appears to be a bug in the build system of the package.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
signature.asc
Description: PGP signature
--- End Message ---
