FS#47626 - [dwarffortress] new keybind is broken (solution included)

Attached to Project: Community Packages
Opened by Pierre Vidal (the_pumpkin) - Tuesday, 05 January 2016, 00:43 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 12 May 2016, 07:16 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Look, I'm french, I'm tired, and I just registered to let you know I found a bug (and the solution). So sorry for my bad English and my informal bug report.

Here is the problem: new features like defining locations (like libraries etc) have some keybinding problems.
http://dwarffortresswiki.org/index.php/DF2014:Locations

I think the problem comes from the fact that the upgrade from 40.24 to 42.* didn't upgraded the config files in ~/.dwarffortress/*
So the file at ~/.dwarffortress/data/init/interface.txt lacks the new keybinds. I managed to override the bug by downloading the bay12game's version (www.bay12games.com/dwarves/df_42_04_linux.tar.bz2) and copied the interface.txt over mine. It is possible to edit the keybind from the game (I discovered it tonight) but it would be tedious to do so. However, player may have a custom interface.txt so ovewritting it would be a bad idea, but you have a better grasp on that kind of linux package maintaining than me. Maybe happending the new keybinds with the default values?

Additional info:
* package version(s) : dwarffortress 0.42.04-1
* config and/or log files etc.


Steps to reproduce:
Install the old version (40.24), create a new world and game, save, upgrade to version 40.*, relaunch the game, reload the save, try to define a new location (library, tavern, temple).


Well, thanks for reading. I hope I helped, despite my informal bug report.
Let me know if you manage to work through this.
Oh, wait. Never mind: see you in my next pacman -Syu ;)
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Thursday, 12 May 2016, 07:16 GMT
Reason for closing:  Implemented
Additional comments about closing:  Added a warning to the install file.
Comment by Doug Newgard (Scimmia) - Tuesday, 05 January 2016, 01:10 GMT
If it's in the home dir, there's really nothing we can do. Packages don't touch the home dir.
Comment by Pierre Vidal (the_pumpkin) - Tuesday, 05 January 2016, 01:21 GMT
Meh! Really? Well, I understand, but... Can't there be some sort of warning in the upgrade process? Or some sort of .pacnew somewhere? Or a note in the wiki! Anything! People will get caught by this bug.

Loading...