From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] nsxiv checksum error
Date: Wed, 13 Dec 2023 10:25:06 +0100 [thread overview]
Message-ID: <20231213092506.rUYohwWeXwXG5uxqVY2_f4f7zar12n2OzySmIPVpT7g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47684@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
Closed issue by rickalex21 on void-packages repository
https://github.com/void-linux/void-packages/issues/47684
Description:
### Is this a new report?
Yes
### System Info
Void 6.5.13_1 x86_64 GenuineIntel uptodate rFFF
### Package(s) Affected
nsxiv 32
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
No.
### Expected behaviour
Build the package without errors.
### Actual behaviour
I think the checksum may need to be updated?
template file updated by me to work:
```text
checksum=49ef1eb775ef6c34f55dada7a3f446c9c5c6773c9e208509ffef27a656338a90
# 12/10/2023 They have not updated the checksum?
#checksum=09d1d72b3cbcf17a04e26beb5e81acc9495aaba1f8f1be907bdcd8e4e3007db3
```
ERROR as the template file is right now:
```text
=> ERROR: SHA256 mismatch for 'v32.tar.gz:'
49ef1eb775ef6c34f55dada7a3f446c9c5c6773c9e208509ffef27a656338a90
=> ERROR: nsxiv-32_1: couldn't verify distfiles, exiting...
```
### Steps to reproduce
Try building with xbps-src.
prev parent reply other threads:[~2023-12-13 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 3:07 [ISSUE] " rickalex21
2023-12-11 8:41 ` classabbyamp
2023-12-11 14:55 ` rickalex21
2023-12-11 14:58 ` rickalex21
2023-12-12 20:09 ` rickalex21
2023-12-12 20:11 ` classabbyamp
2023-12-12 20:32 ` rickalex21
2023-12-13 9:18 ` sgn
2023-12-13 9:24 ` sgn
2023-12-13 9:25 ` sgn [this message]
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=20231213092506.rUYohwWeXwXG5uxqVY2_f4f7zar12n2OzySmIPVpT7g@z \
--to=sgn@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).