From: xtraeme <xtraeme@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] xtools misbehaves with out of date bootstrap packages.
Date: Tue, 25 Feb 2020 10:51:56 +0100 [thread overview]
Message-ID: <20200225095156.YFBqQ0M8adbUk4L5Ktz-gWtxb3N1TunVnoiOQz-di_k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12907@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
Closed issue by knusbaum on void-packages repository
https://github.com/void-linux/void-packages/issues/12907
Description:
### System
* xuname:
Void 4.19.50_1 x86_64 GenuineIntel notuptodate rmFFFFFFFFFFFFFFFF
* package:
xbps-src, xtools
### Expected behavior
xgensum and others generate useful messages on error
### Actual behavior
```
$ xgensum -i srcpkgs/cri-tools/template
/usr/bin/xgensum: line 32: [: too many arguments
/usr/bin/xgensum: line 36: Bootstrap: command not found
/usr/bin/xgensum: line 49: Bootstrap: command not found
```
The behavior comes as a result (i think) of these lines here:
https://github.com/void-linux/void-packages/blob/a47c2dfb5068a9cfb798df67e129b07eba97b22d/xbps-src#L260-L262
Combined with this:
https://git.vuxu.org/xtools/tree/xgensum?id=e697287c4cad3122ba4fd0efdb1a6f5966395324#n16
```
$ xdistdir
Bootstrap packages must be updated with 'xbps-src bootstrap-update'
```
`xgensum` seems to expect xdistdir to succeed and doesn't check. What's more, the error output from xbps-src goes out on stdout rather than stderr, so the error messages get swallowed.
### Steps to reproduce the behavior
1. Have an out-of-date masterdir in void-packages.
2. try running xgensum.
next prev parent reply other threads:[~2020-02-25 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 15:43 [ISSUE] " voidlinux-github
2019-07-08 21:40 ` voidlinux-github
2019-07-08 21:50 ` voidlinux-github
2019-07-08 21:59 ` voidlinux-github
2019-07-08 21:59 ` voidlinux-github
2020-02-25 9:51 ` xtraeme
2020-02-25 9:51 ` xtraeme [this message]
2020-02-25 9:52 ` 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=20200225095156.YFBqQ0M8adbUk4L5Ktz-gWtxb3N1TunVnoiOQz-di_k@z \
--to=xtraeme@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).