Comment 25 for bug 1871268

Although this is marked as "Invalid" for 20.04, this problem has somehow started happening in GitHub Actions Ubuntu 20.04 virtual environment since today (2020-07-24), even though it worked correctly before. I don't know if attaching the entire build log is desirable, but as the result of running these commands

2020-07-24T22:46:28.8786226Z sudo dpkg --add-architecture i386
2020-07-24T22:46:28.8786352Z sudo apt-get update
2020-07-24T22:46:28.8786474Z sudo apt-get --assume-yes install \
2020-07-24T22:46:28.8786604Z automake bc bsdmainutils bzip2 curl cvs default-jre \
2020-07-24T22:46:28.8786724Z g++-mingw-w64-i686 g++-multilib git jing libarchive-tools \
2020-07-24T22:46:28.8786866Z libtool libxml2-utils libxslt1-dev make patch pkg-config rsync \
2020-07-24T22:46:28.8787006Z shellcheck sudo trang unzip wine32 wget xsltproc

I get, after many snipped lines, the following error:

2020-07-24T22:50:38.3418072Z Processing triggers for libc-bin (2.31-0ubuntu9) ...
2020-07-24T22:50:38.4346359Z Processing triggers for libgdk-pixbuf2.0-0:i386 (2.40.0+dfsg-3) ...
2020-07-24T22:50:38.4858494Z Processing triggers for wine (5.0-3ubuntu1) ...
2020-07-24T22:50:40.0498037Z E: Could not configure 'libc6:i386'.
2020-07-24T22:50:40.0499968Z E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
2020-07-24T22:50:40.0526698Z ##[error]Process completed with exit code 100.

and there don't seem to be any other errors in the output until these lines, so I have no idea why does this happen.

FWIW the same step of this workflow succeeds when run in Ubuntu 18.04-based GitHub virtual environment, but it doesn't have sufficiently up-to-date packages for building this software, so I can't use it and would really appreciate any workaround for this problem under 20.04.