Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] common/hooks/do-fetch/00-distfiles.sh: contents checksum broken
Date: Mon, 06 Jan 2020 15:12:50 +0100	[thread overview]
Message-ID: <20200106141250.dF3KTqBdS6m1hNzRcGFSMmVJPUpgLrPiVkKvemwOWG0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18070@inbox.vuxu.org>

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

Closed issue by pullmoll on void-packages repository

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

Description:
With the switch to `bsdtar` the evaluation of contents checksums (i.e. the ones starting with `@`) is broken. One example is `libaom`. Trying to build it gives the error:
```
=> libaom-1.0.0.1_2: verifying contents checksum for distfile 'v1.0.0-errata1.tar.gz'... bsdtar: Can't specify both -t and -x
```

`bsdtar` as opposed to `tar` does not support `-x extract` together with `-t list`, yet the commands are like `$TAR_CMD xf $filename $TAR_CMD_STDOUT`.

I think we need to get rid of the `TAR_CMD_STDOUT="--list"` vs. `TAR_CMD_STDOUT="--to-stdout"` and rather have the type of command (extract or list) for `bsdtar` and `tar` as part of some `TAR_CMD_STDOUT`

For `bsdtar` that could be `TAR_CMD_STDOUT="bsdtar --list"`, and for GNU `tar` that could be `TAR_CMD_STDOUT="tar --extract --to-stdout"`.

For the single case where there is no redirection from the tar output to stdout, in line 98, then `TAR_CMD="bsdtar"` or `TAR_CMD="tar"` should be defined.

I could try to fix that but perhaps @xtraeme knows better how to fix this and beats me to it?

  parent reply	other threads:[~2020-01-06 14:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 13:57 [ISSUE] " voidlinux-github
2020-01-06 14:04 ` voidlinux-github
2020-01-06 14:05 ` voidlinux-github
2020-01-06 14:06 ` voidlinux-github
2020-01-06 14:06 ` voidlinux-github
2020-01-06 14:12 ` voidlinux-github [this message]
2020-01-06 14:13 ` voidlinux-github
2020-01-06 14:14 ` [ISSUE] [CLOSED] " voidlinux-github

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=20200106141250.dF3KTqBdS6m1hNzRcGFSMmVJPUpgLrPiVkKvemwOWG0@z \
    --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).