From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Leo Famulari <leo@famulari.name>
Cc: 46706-done@debbugs.gnu.org
Subject: bug#46706: asciidoc 8.6.10: source hash mismatch
Date: Wed, 24 Feb 2021 00:05:44 +0100 [thread overview]
Message-ID: <20210224000544.255aed83@alma-ubu.fritz.box> (raw)
In-Reply-To: <YDPzpERXmJtQZc1l@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
On Mon, 22 Feb 2021 13:10:44 -0500
Leo Famulari <leo@famulari.name> wrote:
> On Mon, Feb 22, 2021 at 06:03:09PM +0100, Björn Höfling wrote:
> > Note: we also have asciidoc@9.0.1 (package asciidoc-py3). It might
> > be possible to use v9 instead of the old asciidoc@8?
> >
> > Björn
> >
> > $ ./pre-inst-env guix build -S asciidoc --no-substitutes
> >
> > [..]
> >
> > r:sha256 hash mismatch
> > for /gnu/store/925a6d936ihbqc7vaf9qkim4f4myjm0r-asciidoc-8.6.10-checkout:
> > expected hash: 1hrqkgjmp1gq3f9rkbr8l0y62fzvwb9n8ys35s25bg2ld04y4g4y
> > actual hash: 1wwxm789iqanqfabbhm29vma0cfv0kp02srkxhi6vyr752m8i3mg
> > hash mismatch for store item
> > '/gnu/store/925a6d936ihbqc7vaf9qkim4f4myjm0r-asciidoc-8.6.10-checkout'
>
> For comparison, I've attached a tarball that unpacks the "expected"
> source checkout.
Hi Leo,
thanks for this package. This information was quite useful when
diffing. This is "interesting": We referenced the git-checkout not
by commit, but by version-tag. They redirected the repository to
https://github.com/asciidoc-py/asciidoc-py
And they rewrote the old commits (!) to use python3. The "original"
Python2 version is here:
https://github.com/asciidoc-py/asciidoc-py2
Fixed with commit
53c40b3c77492740458a7b52723128c12c53d55b
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-02-23 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 17:03 bug#46706: asciidoc 8.6.10: source hash mismatch Björn Höfling
2021-02-22 18:10 ` Leo Famulari
2021-02-23 23:05 ` Björn Höfling [this message]
2021-02-24 0:09 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210224000544.255aed83@alma-ubu.fritz.box \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=46706-done@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).