snooze: malformed installation path

  • Done
  • quality assurance status badge
Details
3 participants
  • Christopher Howard
  • jgart
  • Tobias Geerinckx-Rice
Owner
unassigned
Submitted by
Christopher Howard
Severity
normal

Debbugs page

Christopher Howard wrote 3 years ago
(name . bug-guix)(address . bug-guix@gnu.org)
a3e7b60abcd46d1ac4e09168b52ae5f337f81c2b.camel@librehacker.com
Hi, I was just trying out the "snooze" package. On my system, the
snooze package does not become available in PATH after installation. On
my system, the path to the binary is malformed:

```
christopher@theoden ~$ guix build snooze
/gnu/store/dvzyb6ya4679hqvrkz955gp7zs4dlclx-snooze-0.5
christopher@theoden ~$ ls /gnu/store/dvzyb6ya4679hqvrkz955gp7zs4dlclx-
snooze-0.5/gnu/store/dvzyb6ya4679hqvrkz955gp7zs4dlclx-snooze-0.5/bin/
snooze
```

The binary does work if you call it using the malformed path.

My system information:

```
christopher@theoden ~$ neofetch --stdout
christopher@theoden
-------------------
OS: Guix System c6adc0947396daa6d85ab08837f9cbc86f4d8722 x86_64
Host: OptiPlex 9020 00
Kernel: 5.14.8-gnu
Uptime: 34 mins
Packages: 95 (guix-system), 129 (guix-user)
Shell: bash 5.0.16
Resolution: 1920x1080
DE: GNOME
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: .gnome-terminal
CPU: Intel i5-4570 (4) @ 3.600GHz
GPU: Intel HD Graphics
GPU: AMD ATI Radeon HD 8490 / R5 235X OEM
Memory: 1907MiB / 7869MiB
```

--
Christopher Howard
Gemini capsule: gemini://gem.librehacker.com
Tobias Geerinckx-Rice wrote 3 years ago
(name . Christopher Howard)(address . christopher@librehacker.com)
87a6ivl8u0.fsf@nckx
Christopher, jgart, Nicolas,

Christopher Howard 写道：
Toggle quote (2 lines)
> the path to the binary is malformed:

Indeed it was.

DESTDIR does not mean ‘final destination’; it's meant as a
temporary install-time ‘staging’ directory whose contents are
expected to move back to / later. For example, ‘make install
DESTDIR=/tmp/my-package-manager-output && cd
/tmp/my-package-manager-output && tar cf foo.pkg .’. Guix does
not use this packaging method.

Setting DESTDIR in Guix is almost always a bug. The few places in
Guix where it is used are using it as a hack around buggy build
systems. It just happens to work (because, well, the build
system's buggy).

When reviewing patches, I find the ‘tree’ command very useful to
immediately spot such weirdness. Much more so than ‘ls -R’.
YMMV.

Fixed in commit 89d8417b371f3918f0508bbc561675ec100a6add.

Thanks!

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCYXiBBw0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15/ToBAJ3U9FOfWPmJV6XU2d5P/nEIpIL8yc6flqYYyBS4
/VR+APwPjRMOfR4OzxYDAtIDRwqc6FsQI2ZHv/kZvqGOe1GsDA==
=B9PA
-----END PGP SIGNATURE-----

Closed
jgart wrote 3 years ago
(name . Tobias Geerinckx-Rice)(address . me@tobias.gr)
20211026200322.GB9051@gac.attlocal.net
On Wed, 27 Oct 2021 00:13:47 +0200 Tobias Geerinckx-Rice <me@tobias.gr> wrote:
Toggle quote (29 lines)
> Christopher, jgart, Nicolas,
>
> Christopher Howard 写道：
> > the path to the binary is malformed:
>
> Indeed it was.
>
> DESTDIR does not mean ‘final destination’; it's meant as a
> temporary install-time ‘staging’ directory whose contents are
> expected to move back to / later. For example, ‘make install
> DESTDIR=/tmp/my-package-manager-output && cd
> /tmp/my-package-manager-output && tar cf foo.pkg .’. Guix does
> not use this packaging method.
>
> Setting DESTDIR in Guix is almost always a bug. The few places in
> Guix where it is used are using it as a hack around buggy build
> systems. It just happens to work (because, well, the build
> system's buggy).
>
> Fixed in commit 89d8417b371f3918f0508bbc561675ec100a6add.
>
> Thanks!
>
> T G-R

> When reviewing patches, I find the ‘tree’ command very useful to
> immediately spot such weirdness. Much more so than ‘ls -R’.
> YMMV.

I use nnn or another file manager like broot sometimes but this one escaped me.

Thanks for fixing that. I was actually going to send a patch fix for it but had
not found the time. I noticed it after the patch was accepted.

Thanks!

all best,

jgart
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 51424@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 51424
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help