2017-07-11 10:46 GMT+02:00 Andreas Beckmann <a...@debian.org>:
> [...]
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch' via 'buster' to 'sid'.
> It installed fine in 'stretch' and upgraded successfully to 'buster',
> then the upgrade to 'sid' fails.
>
> >From the attached log (scroll to the bottom...):
>
> 0m17.2s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmphZCQmo',
> 'apt-get', 'update']
> 0m22.4s DUMP:
> Get:1 http://ftp.de.debian.org/debian sid InRelease [255 kB]
> Get:2 http://ftp.de.debian.org/debian sid/main amd64 Packages [7550 kB]
> Get:3 http://ftp.de.debian.org/debian sid/main Translation-en [5731 kB]
> Get:4 http://ftp.de.debian.org/debian sid/main amd64 DEP-11 Metadata [3147
> kB]
> AppStream system cache was updated, but problems were found: Metadata files
> have errors:
> /var/lib/app-info/yaml/ftp.de.debian.org_debian_dists_sid_main_dep11_Components-amd64.yml.gz
> Fetched 16.7 MB in 4s (4071 kB/s)
> Reading package lists...
> E: Problem executing scripts APT::Update::Post-Invoke-Success 'if
> /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then
> appstreamcli refresh-cache > /dev/null; fi'
> E: Sub-process returned an error code
> 0m22.4s ERROR: Command failed (status=100): ['chroot',
> '/srv/piuparts/tmp/tmphZCQmo', 'apt-get', 'update']
This is not a bug in the package, but in the metadata - the package
itself updates properly (it has to, these errors are ignored in
postinst).
I wonder whether it makes sense to make this not a hard failure, but
just print something on stderr in case of and error and have the apt
update command succeed.
I will look into that.
Cheers,
Matthias
