There is now a solution for LP#1983255.
Meanwhile I've noticed that gdcm is now flagged as a new regression for zlib's proposed miration at 'update excuses' (was not the case before).
Found that this happened on Debian too: https://<email address hidden>/msg1863513.html (with exactly the same error: https://ci.debian.net/data/autopkgtest/testing/s390x/g/gdcm/23826805/log.gz) but seems to be solved meanwhile: https://qa.debian.org/excuses.php?package=gdcm So can obviously be solved by an update from (Ubuntu) 3.0.13-2 to (Debian) 3.0.13-3 (sync), ( according to changelog: https://metadata.ftp-master.debian.org/changelogs//main/g/gdcm/gdcm_3.0.13-3_changelog )
Just noticed that it was already synched a few hours ago: "3.0.13-3 release (universe) 19 hours ago" (https://launchpad.net/ubuntu/+source/gdcm)
So I assume it's a matter of time until update-excuses reflects this gdcm update and get's again rid of the regression.
There is now a solution for LP#1983255.
Meanwhile I've noticed that gdcm is now flagged as a new regression for zlib's proposed miration at 'update excuses' (was not the case before).
Found that this happened on Debian too: /msg1863513. html /ci.debian. net/data/ autopkgtest/ testing/ s390x/g/ gdcm/23826805/ log.gz) /qa.debian. org/excuses. php?package= gdcm /metadata. ftp-master. debian. org/changelogs/ /main/g/ gdcm/gdcm_ 3.0.13- 3_changelog )
https://<email address hidden>
(with exactly the same error: https:/
but seems to be solved meanwhile: https:/
So can obviously be solved by an update from (Ubuntu) 3.0.13-2 to (Debian) 3.0.13-3 (sync),
( according to changelog: https:/
Just noticed that it was already synched a few hours ago: /launchpad. net/ubuntu/ +source/ gdcm)
"3.0.13-3 release (universe) 19 hours ago"
(https:/
So I assume it's a matter of time until update-excuses reflects this gdcm update and get's again rid of the regression.