Closed ThomasWaldmann closed 7 years ago
Shorter log showing the issue (done after the above steps):
$ sudo apt-get install -f
[sudo] password for tw:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
zlib1g-dev:i386
The following NEW packages will be installed:
zlib1g-dev:i386
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
173 not fully installed or removed.
Need to get 0 B/167 kB of archives.
After this operation, 403 kB of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 332533 files and directories currently installed.)
Preparing to unpack .../zlib1g-dev_1%3a1.2.8.dfsg-2ubuntu4_i386.deb ...
Unpacking zlib1g-dev:i386 (1:1.2.8.dfsg-2ubuntu4) ...
dpkg: error processing archive /var/cache/apt/archives/zlib1g-dev_1%3a1.2.8.dfsg-2ubuntu4_i386.deb (--unpack):
trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
/var/cache/apt/archives/zlib1g-dev_1%3a1.2.8.dfsg-2ubuntu4_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Known bug in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1512992
Suggested workaround there:
sudo apt-get -o Dpkg::Options::="--force-overwrite" install zlib1g-dev:i386
Thanks, I added this to a trouble shooting page in wiki
At least not using Ubuntu 16.04 64bit. Their setup wants to install conflicting packages.
In a previous try, i tried to "fix" the conflict by explicitly installing zlib1g-dev:386 and I didn't notice that it wanted to remove a ton of stuff - that almost destroyed my system and it took me an hour to manually repair the damage again.
Of course this is not u2f-zero project's fault, but I thought I give feedback in case other users run into the same issues.
My first try was with SimplicityStudio v4 and after I read in the issues tracker that v3 works better, I had quite similar issues with v3 (see log above).