2017-11-03 11:26 GMT+01:00 Ansgar Burchardt <ans...@debian.org>:
> Julian Andres Klode writes:
> [...]
>>> E: Failed to fetch
>>> store:/var/lib/apt/lists/partial/mirrors.wikimedia.org_debian_dists_unstable_non-free_dep11_Components-amd64.yml.xz
>>> Hash Sum mismatch
>>> Hashes of expected file:
>>> - Filesize:65721 [weak]
>>> -
>>> SHA256:0eb5ea70b4c46a7c0889e9601d16cedf3eb4ff55bf3b77ef2af2bcd3dcf48cec
>>> - MD5Sum:68fdfbc3bc806010ba4c9fc8d4cb133b [weak]
>>> Hashes of received file:
>>> -
>>> SHA256:5fa520cd26eac94e183632f84371643219fdf905dfd351b53bbcd7afa5c3b848
>>> - MD5Sum:875dd6824d698bfa73c6517307f692f5 [weak]
>>> - Filesize:65721 [weak]
>>> Last modification reported: Mon, 30 Oct 2017 21:09:03 +0000
>>> Release file created at: Fri, 03 Nov 2017 02:41:19 +0000
>>> E: Some index files failed to download. They have been ignored, or old ones
>>> used instead.
>>> ```
>>>
>> The archive is broken, .xz contains different content than .gz - writing the
>> .xz file
>> failed. The are several .xz.new files, so I expect some of the other files
>> are broken
>> too.
>
> The appstream generator crashed and left inconsistent output data
> (updates .gz, but old .xz) already on mekeel.d.o... That is really not
> nice: the data synced into the archive should really be in a staging
> location and only be updated once the generator finished successfully.
>
> CC'ed mak@ as he maintains the appstream generator.
Hmm, I didn't know APT would have issues with this - I guess to be
safe it would make sense to rsync the data directory to a place where
dak can fetch it from after appstream-generator has finished
successfully.
Alternatively, I could maybe change the code so the contents of the
.gz/.xz files are ensured to be always identical.
In any case, there is bug#880645 to track this now.
Cheers,
Matthias
--
I welcome VSRE emails. See http://vsre.info/
