Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 645442 - stage3-amd64-systemd-20180121.tar.bz2 is corrupt
Summary: stage3-amd64-systemd-20180121.tar.bz2 is corrupt
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-23 10:25 UTC by Liam Dawson
Modified: 2018-01-25 09:36 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Liam Dawson 2018-01-23 10:25:01 UTC
stage3-amd64-systemd-20180121.tar.bz2 as downloaded from two separate mirrors validates the checksum correctly, but fails to extract with an unexpected EOF.
File size is 105MB, which is significantly smaller than the previous autobuild (stage3-amd64-systemd-20180118.tar.bz2) (263MB).

stage3-amd64-systemd-20180118.tar.bz2 extracted successfully.
Comment 1 Anthony Basile gentoo-dev 2018-01-23 10:54:42 UTC
(In reply to Liam Dawson from comment #0)
> stage3-amd64-systemd-20180121.tar.bz2 as downloaded from two separate
> mirrors validates the checksum correctly, but fails to extract with an
> unexpected EOF.
> File size is 105MB, which is significantly smaller than the previous
> autobuild (stage3-amd64-systemd-20180118.tar.bz2) (263MB).
> 
> stage3-amd64-systemd-20180118.tar.bz2 extracted successfully.

this is the second time this has happened.  the tarball is fine on the build server, but it get truncated on the mirrors.  i can't check beyond the staging server, but i'll make sure the checksums are correct up to that point.

please check back in about 24 hours and see if the problem is fixed.  if it is, close this bug, else i'll contact gentoo-infra and see what might be happening beyond the staging server.
Comment 2 Liam Dawson 2018-01-25 09:36:37 UTC
I haven't verified it, but the new stage3 tarball (for the same timestamp) is much larger now, so presumably it hasn't truncated.