From: reback00 <reback00@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: Sunflower 0.4 (62)
Date: Wed, 07 Oct 2020 21:56:10 +0200 [thread overview]
Message-ID: <20201007195610.FrKYaxMA5y3MSH_LiSielcLYbIllmmCVSb_9G0JHfs8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25062@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
New comment by reback00 on void-packages repository
https://github.com/void-linux/void-packages/issues/25062#issuecomment-705160052
Comment:
> I had to change the checksum.
That's kind of expected. The checksum will change when there is a new commit in `devel`. The distfile url just downloads what's in devel. So whenever there's an update on that branch, it changes checksum with it. I added an `@` as suggested by [Manual.md](https://github.com/void-linux/void-packages/blob/master/Manual.md#optional-variables):
> If a distfile changes its checksum for every download because it is packaged on the fly on the server, like e.g. snapshot tarballs from any of the https://*.googlesource.com/ sites, the checksum of the archive contents can be specified by prepending a commercial at (@). For tarballs you can find the contents checksum by using the command tar xf <tarball.ext> --to-stdout | sha256sum.
I thought it would pass it as being ok even if it changes because I added the @. But I guess it doesn't work that way.
next prev parent reply other threads:[~2020-10-07 19:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 22:49 [ISSUE] " gorkawien
2020-10-03 17:57 ` reback00
2020-10-03 20:56 ` gorkawien
2020-10-04 8:04 ` gorkawien
2020-10-05 10:06 ` reback00
2020-10-05 11:07 ` gorkawien
2020-10-05 11:39 ` reback00
2020-10-06 16:39 ` gorkawien
2020-10-06 16:53 ` gorkawien
2020-10-07 19:56 ` reback00 [this message]
2020-10-08 10:39 ` gorkawien
2020-10-09 5:19 ` reback00
2021-06-08 0:56 ` bugcrazy
2023-05-10 17:00 ` niels0n
2023-05-10 21:07 ` bugcrazy
2023-05-10 23:05 ` niels0n
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=20201007195610.FrKYaxMA5y3MSH_LiSielcLYbIllmmCVSb_9G0JHfs8@z \
--to=reback00@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).