Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#78353 - [dbeaver] Include '/usr/share/dbeaver/dbeaver.ini' in 'backup' list
Attached to Project:
Community Packages
Opened by Alexey Makhmutov (Lerm) - Monday, 01 May 2023, 15:22 GMT
Last edited by Muflone (muflone) - Monday, 01 May 2023, 21:23 GMT
Opened by Alexey Makhmutov (Lerm) - Monday, 01 May 2023, 15:22 GMT
Last edited by Muflone (muflone) - Monday, 01 May 2023, 21:23 GMT
|
DetailsDescription:
DBevear installation includes a launch configuration file, which is installed at '/usr/share/dbeaver/dbeaver.ini' patch in Arch. User may want/need to edit this file in order to change path to the correct JVM location (e.g. if system is configured to use Java 11 while DBeaver requires Java 17) or to change 'Xmx' value to allocate more memory to the application. However right now this file is just overwritten during the package upgrade, so all the modification to this file are lost without warning. The proposal is to include this file in the 'backup' files list for the package, so that pacman will use pacsave/pacnew approach during the upgrade if the file was modified by the user. Additional info: * Package version: 23.0.3-1 |
This task depends upon
Closed by Muflone (muflone)
Monday, 01 May 2023, 21:23 GMT
Reason for closing: Not a bug
Additional comments about closing: the configuration file lives in your home directory
Monday, 01 May 2023, 21:23 GMT
Reason for closing: Not a bug
Additional comments about closing: the configuration file lives in your home directory
It will always be replaced with the updated version whenever an update will be released.
If you want to customize your variables you have to specify them in the config.ini file
https://github.com/dbeaver/dbeaver/wiki/How-to-set-a-variable-if-dbeaver.ini-is-read-only
see also:
dbeaver -vm <path to vm>