Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] xbps-src binary-bootstrap fails
Date: Mon, 13 Jan 2020 06:01:47 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18282@inbox.vuxu.org> (raw)

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

New issue by ruegerjr on void-packages repository

https://github.com/void-linux/void-packages/issues/18282

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
Void 5.4.10_2 x86_64 AuthenticAMD
* package:  
xbps-0.57.1_8  (xbps-src ->glic-locales, ca-certificates)
### Expected behavior
xbps-src binary-bootstrap should complete without error
### Actual behavior
For the last 2 weeks or more, with newly git-cloned void-packages, I find that ./xbps-src binary-bootstrap fails with errors in the INSTALL scripts for glibc-locales and ca-certificates as follows:

    ERROR: glibc-locales: [configure] INSTALL script failed to execute the post ACTION: No such file or directory

    Failed to reconfigure `glibc-locales': No such file or directory

    ca-certificates: configuring ...

    ERROR: ca-certificates: [configure] INSTALL script failed to execute the post ACTION: No such file or directory

    Failed to reconfigure `ca-certificates': No such file or directory

It seems the missing file may be a useable /tmp directory.  I have created a temporary work-around by creating a void-packages/masterdir/tmp directory:

```
cd void-packages
./xbps-src zap
mkdir masterdir/tmp
./xbps-src binary-bootstrap
```
This succeeds as expected.

             reply	other threads:[~2020-01-13  5:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13  5:01 voidlinux-github [this message]
2020-01-13 18:01 ` voidlinux-github
2020-01-13 20:01 ` voidlinux-github
2020-01-24 13:00 ` voidlinux-github
2020-01-24 16:58 ` voidlinux-github
2020-01-24 17:05 ` voidlinux-github
2020-01-24 17:08 ` voidlinux-github
2020-01-24 17:11 ` voidlinux-github
2020-01-24 17:11 ` voidlinux-github
2020-01-24 20:10 ` voidlinux-github
2020-01-24 20:12 ` voidlinux-github
2020-01-24 20:12 ` voidlinux-github
2020-01-26  0:13 ` voidlinux-github
2020-01-26  2:05 ` voidlinux-github
2020-01-26  2:12 ` voidlinux-github
2020-01-26 13:29 ` voidlinux-github
2020-01-26 13:38 ` voidlinux-github
2020-01-26 19:35 ` voidlinux-github
2020-02-17  4:45 ` xtraeme
2020-02-17  4:45 ` [ISSUE] [CLOSED] " xtraeme

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18282@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).