Your message dated Sat, 14 Apr 2018 15:26:31 +0200
with message-id
<CAKNHny_d=T4xnjXMETUA0zHn6=wJ9jdJ2tPfmjp-=8y_qdu...@mail.gmail.com>
and subject line Re: Bug#895671: appstream-generator,ftp.debian.org: broken
sid/non-free/Components-amd64.yml.xz
has caused the Debian Bug report #895671,
regarding appstream-generator,ftp.debian.org: broken
sid/non-free/Components-amd64.yml.xz
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
895671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: appstream-generator,ftp.debian.org
Severity: grave
dists/unstable/non-free/dep11/Components-amd64.yml.xz doesn't match
dists/unstable/non-free/dep11/Components-amd64.yml.gz, and the former
also doesn't match the expected hash from InRelease for the uncompressed
file. It appears appstream-generator or mekeel died in some way and fed
bogus data to dak, which failed to detect it.
Cheers,
Julien
--- End Message ---
--- Begin Message ---
2018-04-14 13:25 GMT+02:00 Julien Cristau <jcris...@debian.org>:
> Package: appstream-generator,ftp.debian.org
> Severity: grave
>
> dists/unstable/non-free/dep11/Components-amd64.yml.xz doesn't match
> dists/unstable/non-free/dep11/Components-amd64.yml.gz, and the former
> also doesn't match the expected hash from InRelease for the uncompressed
> file. It appears appstream-generator or mekeel died in some way and fed
> bogus data to dak, which failed to detect it.
Hmm, there wasn't any crash when the thing was running on its own, but
I did run a lot of manual tests with asgen, and at least one of those
crashed. So, I think what happened is that that error left files
behind, and appstream-generator did not update them because the
non-free archive had not changed compared to the previous run. So the
incomplete files were synced.
I've fixed this issue now, and will think of maybe adding another
sanity check for the publish step. This is an issue though that I
don't think will happen again - it requires a suite that isn't updated
much, as well as a crash at just the right time. In this case, due to
manual action.
Thanks for noticing!
--
I welcome VSRE emails. See http://vsre.info/
--- End Message ---
