Quantcast
Channel: MySQL Forums - MySQL Workbench
Viewing all articles
Browse latest Browse all 3739

Workbench Version Conflict? (5 replies)

$
0
0
Hello, very new user here to MySQl/Workbench, and I seem to have run into a curiousity.

If, in Workbench, I click "About" it notes that I have version 5.2.38. And, if I click, check for updates, it recommends that I update to version 5.2.42.

Attempting to download the update from the MySQL and install it from the downloaded file, leads to an install error:

(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 152385 files and directories currently installed.)
Unpacking mysql-workbench-gpl (from .../mysql-workbench-gpl-5.2.43-1ubu1204-i386(1).deb) ...
dpkg: error processing /home/frigga/Downloads/mysql-workbench-gpl-5.2.43-1ubu1204-i386(1).deb (--install):
trying to overwrite '/usr/lib/mysql-workbench/libmdcanvas.so.0.0.0', which is also in package mysql-workbench 5.2.38+dfsg-3
dpkg-deb (subprocess): data: internal gzip write error: Broken pipe
dpkg-deb (subprocess): failed in write on buffer copy for failed to write to pipe in copy: Broken pipe
dpkg-deb: error: subprocess <decompress> returned error exit status 2
Errors were encountered while processing:
/home/[username changed]/Downloads/mysql-workbench-gpl-5.2.43-1ubu1204-i386(1).deb

If I attempt instead to get the update from terminal via sudo apt-get install mysql-workbench then I encounter the following:

Reading package lists... Done
Building dependency tree
Reading state information... Done
mysql-workbench is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.

So, terminal believes I am already upgraded, however, Workbench itself does not.

How do I fix this conflict?

Viewing all articles
Browse latest Browse all 3739

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>