This bug was fixed in the package gcab - 1.2-3
---
gcab (1.2-3) unstable; urgency=medium
* Apply upstream patch to fix corruption when extracting.
Closes: #931487. LP: #1835589.
-- Stephen Kitt Sat, 06 Jul 2019 10:18:07 +0200
** Changed in: gcab (Ubuntu)
Status: In
** Changed in: gcab (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835589
Title:
extracted data is corrupted
To manage notifications about this bug go
** Changed in: gcab (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835589
Title:
extracted data is corrupted
To manage notifications about this bug go to:
** Bug watch added: Debian Bug tracker #931487
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931487
** Also affects: gcab (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931487
Importance: Unknown
Status: Unknown
--
You received this bug notification because
The fix for https://bugzilla.redhat.com/show_bug.cgi?id=1608301 is
already present in Disco and Eoan, but it doesn’t fix
https://gitlab.gnome.org/GNOME/msitools/issues/6 — the fix for that is
https://gitlab.gnome.org/GNOME/gcab/commit/5619f4cd2ca3108c8dea17ba656b5ce44a60ca29
** Bug watch added:
