Github messages for voidlinux
 help / color / mirror / Atom feed
From: lane-brain <lane-brain@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Signal-Desktop: update to 5.0.0.
Date: Wed, 05 May 2021 22:14:08 +0200	[thread overview]
Message-ID: <20210505201408.NAloYHpDNki-6v5PL8MmLnVUCHAwYDwHtsOHMFIpu44@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30696@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 3854 bytes --]

New comment by lane-brain on void-packages repository

https://github.com/void-linux/void-packages/pull/30696#issuecomment-832976856

Comment:
> `chmod -R +wX $HOME` works, but that's starting to sound like they build Go stuff in the middle of the build process??? Where do they even get the Go executable?

No idea here. But unfortunately no this mktemp method runs into another issue:
```
=> Signal-Desktop-5.0.0_1: skipping check (XBPS_CHECK_PKGS is disabled) ...
=> Signal-Desktop-5.0.0_1: running pre-install hook: 00-libdir ...
=> Signal-Desktop-5.0.0_1: running pre-install hook: 02-script-wrapper ...
=> Signal-Desktop-5.0.0_1: running pre-install hook: 98-fixup-gir-path ...
=> Signal-Desktop-5.0.0_1: running do_install ...
=> Signal-Desktop-5.0.0_1: running post_install ...
=> Signal-Desktop-5.0.0_1: running post-install hook: 00-compress-info-files ...
=> Signal-Desktop-5.0.0_1: running post-install hook: 00-fixup-gir-path ...
=> Signal-Desktop-5.0.0_1: running post-install hook: 00-libdir ...
=> Signal-Desktop-5.0.0_1: running post-install hook: 00-uncompress-manpages ...
=> Signal-Desktop-5.0.0_1: running post-install hook: 01-remove-misc ...
=> Signal-Desktop-5.0.0_1: running post-install hook: 02-remove-libtool-archives ...
=> Signal-Desktop-5.0.0_1: running post-install hook: 02-remove-perl-files ...
=> Signal-Desktop-5.0.0_1: running post-install hook: 02-remove-python-bytecode-files ...
=> Signal-Desktop-5.0.0_1: running post-install hook: 03-remove-empty-dirs ...
=> Signal-Desktop-5.0.0_1: running post-install hook: 04-create-xbps-metadata-scripts ...
mktemp: failed to create file via template ‘/tmp/tmp.XXXXXXXXXX’: No such file or directory
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 27: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 203: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 307: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 314: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 315: $tmpf: ambiguous redirect
   Added trigger 'gtk-icon-cache' for the 'INSTALL' script.
   Added trigger 'update-desktopdb' for the 'INSTALL' script.
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 333: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 334: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 341: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 342: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 341: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 342: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 345: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 346: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 347: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 361: $tmpf: ambiguous redirect
/void-packages/common/hooks/post-install/04-create-xbps-metadata-scripts.sh: line 362: $tmpf: ambiguous redirect
mv: missing destination file operand after '/destdir//Signal-Desktop-5.0.0/INSTALL'
Try 'mv --help' for more information.
=> ERROR: Signal-Desktop-5.0.0_1: failed to write INSTALL metadata file!
```

  parent reply	other threads:[~2021-05-05 20:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-05 17:52 [PR PATCH] " lane-brain
2021-05-05 17:54 ` lane-brain
2021-05-05 17:55 ` ericonr
2021-05-05 18:03 ` ericonr
2021-05-05 18:45 ` lane-brain
2021-05-05 19:13 ` [PR REVIEW] " ericonr
2021-05-05 19:14 ` ericonr
2021-05-05 19:27 ` [PR REVIEW] " lane-brain
2021-05-05 19:46 ` lane-brain
2021-05-05 19:58 ` lane-brain
2021-05-05 20:14 ` lane-brain [this message]
2021-05-05 22:43 ` [PR PATCH] [Updated] " lane-brain
2021-08-01 13:03 ` notthewave
2021-08-27 17:33 ` [PR PATCH] [Closed]: " ericonr
2021-08-27 17:33 ` ericonr
  -- strict thread matches above, loose matches on Subject: below --
2021-04-26  3:21 [PR PATCH] " ScrelliCopter
2021-05-02 23:13 ` kwshi
2021-06-24 22:34 ` ScrelliCopter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210505201408.NAloYHpDNki-6v5PL8MmLnVUCHAwYDwHtsOHMFIpu44@z \
    --to=lane-brain@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).