Learn more about these different git repos.
Other Git URLs
It appears I somehow uploaded a corrupt artifact to the lookaside.
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/orca-47.beta.tar.xz /usr/bin/xz: /builddir/build/SOURCES/orca-47.beta.tar.xz: Unexpected end of input /usr/bin/tar: Unexpected EOF in archive /usr/bin/tar: Unexpected EOF in archive
Thank you!
When do you need this? (YYYY/MM/DD) before 41 beta freeze ; 2024-08-27
When is this no longer needed or useful? (YYYY/MM/DD) after upstream releases a final version
If we cannot complete your request, what is the impact? cannot address https://pagure.io/fedora-qa/blocker-review/issue/1620
Tarballs in the lookaside cache are stored in a directory of their hash, e.g.
https://src.fedoraproject.org/lookaside/pkgs/orca/orca-47.beta.tar.xz/sha512/51beb00b4dd1b62569dff05e67274a8403d0c483c9bc121d91c03ef8e42c96b55a0ce822089200f54b8e41ee8950a533200bca0665d5568d19c484a04bcdaa8a/orca-47.beta.tar.xz
This means if you end up uploading a corrupted or incorrect tarball, you can just upload the correct one to fix it. It will get stored in a different path if the hash is different, which it should be if you're changing to a non-corrupted tarball in this case. The build will use whichever tarball is referenced by hash in the sources file.
It looks like someone else has already uploaded a working copy of orca-47.beta.tar.xz as
As long as your sources file references that hash, a build shouldn't be blocked. That said, I'm just commenting from the peanut gallery here with general information, and I'm not sure if releng would prefer to remove the corrupted tarball for good measure or not.
heh, yeah that was me.. I forgot to also update the sources file.
I need more coffee and/or sleep.
Will keep open in case releng wants to remove, but @salimma mentioned it might get garbage collected anyways. From my perspective this can be closed.
Edit:
Thank you Carl!
Metadata Update from @kevin: - Issue assigned to kevin
I removed the corrupt archive.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.