Looks like upstream released a new build:
Old build was 6.2.0.201909091348
New build: 6.2.0.201909220738
I've updated the PKGBUILD with the new sha256sums.
Git Clone URL: | https://aur.archlinux.org/dbeaver-ee.git (read-only, click to copy) |
---|---|
Package Base: | dbeaver-ee |
Description: | A universal database tool for developers and database administrators. Enterprise Edition includes NoSQL database support |
Upstream URL: | http://dbeaver.com/ |
Licenses: | Commercial |
Submitter: | jcpst |
Maintainer: | jsivak |
Last Packager: | jsivak |
Votes: | 26 |
Popularity: | 0.080585 |
First Submitted: | 2015-10-06 13:46 (UTC) |
Last Updated: | 2024-04-16 11:38 (UTC) |
Looks like upstream released a new build:
Old build was 6.2.0.201909091348
New build: 6.2.0.201909220738
I've updated the PKGBUILD with the new sha256sums.
sha256sum dbeaver-ee-6.2.0-linux.gtk.x86_64.tar.gz cloud be c8429bab34d41809e0d80b54daed3f32a38154f0ff7acd828dd46e8a4b356c93
Version 6.2.0 migrates the DBeaver config files to a new location: "$HOME/.local/share/DBeaverData".
During my migration, I seemed to have lost access/connection to downloaded JDBC drivers.
After the migration it appears that you may need to re-download and "re-find" your JDBC .jar files for database drivers. You can do this via Main menu->Database->Driver Manager.
For example: I needed to update MySQL's JDBC connector, so I:
went to "Main menu->Database->Driver Manager"
selected MySQL from the list
clicked Edit ...
Downloaded the JDBC driver from the website listed in the dialog box.
un-tar'd the JDBC driver to a location of my choosing
Used the "Add File" button to add/update the Library for the MySQL driver.
This should update all connections that use that driver in DBeaver.
Thanks for finding this; not sure why upstream has updated their files.
As for the 4 sha256sum's in the PKGBUILD; that's being auto-populated when updpkgsums is run; not sure where its getting them from.
I've updated the PKGBUILD for the new sha256sums. Also updated the "License" attribute to indicate this is for a commercially licensed version of DBeaver.
The correct sha256 for source files is:
108f5290232ebb27fc38a7786c0c7b61c79aa80cd1313efbee18a536a9b17c37 dbeaver-ee-5.3.0-linux.gtk.x86_64.tar.gz
98129a97c340691d70533ebd482c245bf8fedd36ed803d23b8f0a3a33419f89c dbeaver-ee-5.3.0-linux.gtk.x86.tar.gz
I noticed that there are 4 sha256sum in PKGBUILD but only 3 sources.
The x86_64 sha256 checksum for dbeaver-ee-5.3.0-linux.gtk.x86_64.tar.gz seems to be wrong
@Ghost93:
It looks like the AUR dbeaver-ce (the Community Edition) package has been 'promoted' to the Community repository, and renamed to be just "dbeaver".
dbeaver-ce was removed for some reason... why?
FYI: It looks like the AUR dbeaver-ce (the Community Edition) package has been 'promoted' to the Community repository.
If you have used the AUR dbeaver-ce, then I believe you can switch to the Community/dbeaver package.
I only use the Enterprise Edition, so I'll continue to maintain the dbeaver-ee package.
In the 5.1.0 update of DBeaver it looks like new MySQL 8.0 drivers require some manual intervention for MySQL connections in DBeaver.
Please see: https://github.com/dbeaver/dbeaver/issues/3599 for info on how to set the serverTimezone for your MySQL connections.
Pinned Comments
jsivak commented on 2021-10-18 15:22 (UTC) (edited on 2021-10-18 15:23 (UTC) by jsivak)
Reminder for people flagging this package as out-of-date: This is for the Commercial Edition of DBeaver. Its release schedule is slower than the Community Edition.
The Community Edition is in the Arch Community repo: https://archlinux.org/packages/community/x86_64/dbeaver/