From: Timothy Sample <samplet@ngyro.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: 69609@debbugs.gnu.org
Subject: bug#69609: Missing Disarchive info for isl-0.19.tar.bz2
Date: Fri, 22 Mar 2024 16:53:34 -0600 [thread overview]
Message-ID: <875xxdzxn5.fsf@ngyro.com> (raw)
In-Reply-To: <87sf125is3.fsf@inria.fr> ("Ludovic Courtès"'s message of "Thu, 07 Mar 2024 13:27:24 +0100")
[-- Attachment #1: Type: text/plain, Size: 1746 bytes --]
Hello,
Ludovic Courtès <ludovic.courtes@inria.fr> writes:
> We have an empty Disarchive spec here:
>
> https://disarchive.ngyro.com/sha256/d59726f34f7852a081fbd3defd1ab2136f174110fc2e0c8d10bb122173fa9ed8
> https://disarchive.guix.gnu.org/sha256/d59726f34f7852a081fbd3defd1ab2136f174110fc2e0c8d10bb122173fa9ed8
>
> Thoughts?
This is due to a bug that is fixed as of Disarchive 0.6.0 (see the NEWS
file or commit c669e1c for details). This bug interacted badly with the
PoG code resulting in a handful of corrupt Disarchive specifications.
I found four corrupt specifications in the set that we synchronized:
• 095f4b5 isl-0.11.1.tar.bz2
• 6b8b0fd isl-0.18.tar.bz2
• 881f238 libass-0.14.0.tar.xz
• d59726f isl-0.19.tar.bz2
The three isl ones are due to a typo in the Guix source. The libass one
likely comes from when I was testing XZ support.
I have three more corrupt bzip2 specifications from the set that we have
not yet synchronized:
• 3f66bce mingw-w64-v11.0.1.tar.bz2
• 0cd846c nsis-3.09-src.tar.bz2
• bd0ea16 mingw-w64-v11.0.0.tar.bz2
They are likely due to testing bzip2 support.
Of all of these, Disarchive can only produce specifications for the isl
sources. I’ve attached their specifications; they should replace the
corrupt ones. The corrupt libass specification should be deleted.
If possible, could you run something like
find . -exec zgrep -H -F '(version 0) #f' '{}' ';'
over the specifications at disarchive.guix.gnu.org? If there are more
broken specifications (unlikely but possible) we should fix them. Just
post the hashes (i.e. filenames) of any that you find, and I can
investigate further.
-- Tim
[-- Attachment #2: 095f4b54c88ca13a80d2b025d9c551f89ea7ba6f6201d701960bfe5c1466a98d.gz --]
[-- Type: application/octet-stream, Size: 11516 bytes --]
[-- Attachment #3: 6b8b0fd7f81d0a957beb3679c81bbb34ccc7568d5682844d8924424a0dadcb1b.gz --]
[-- Type: application/octet-stream, Size: 14184 bytes --]
[-- Attachment #4: d59726f34f7852a081fbd3defd1ab2136f174110fc2e0c8d10bb122173fa9ed8.gz --]
[-- Type: application/octet-stream, Size: 14617 bytes --]
prev parent reply other threads:[~2024-03-22 22:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 12:27 bug#69609: Missing Disarchive info for isl-0.19.tar.bz2 Ludovic Courtès
2024-03-22 22:53 ` Timothy Sample [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
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=875xxdzxn5.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=69609@debbugs.gnu.org \
--cc=ludovic.courtes@inria.fr \
/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).