issuing the following query select cast (a.rdb$security_class as varchar(50) character set win1251) from rdb$database a results in "CHARACTER SET WIN1251 is not defined." error. the problem is that the server looks for the intl directory in /opt/firebird/ which is installed in /usr/lib/firebird/ Reproducible: Always Steps to Reproduce: 1.install firebird superserver from the dev-db/firebird-2.0.3.12981.0-r4 ebuild 2.create an empty database 3.execute select cast (a.rdb$security_class as varchar(50) character set win1251) from rdb$database a query Actual Results: "CHARACTER SET WIN1251 is not defined." error. Expected Results: a valid SQL cursor To prove that the server looks for the intl directory in /opt/firebird I just created a symlink /opt/firebird/intl pointing to /usr/lib/firebird/intl and everything worked just fine.
The path to that is not modified and is relative to Firebird's base dir set in /etc/conf.d/firebird. Did that file not get updated? Is it still pointing to /opt or etc? That error is not specific to one characterset. I have seen it before and all would have issues with any characterset if the ebuild was off. It's possible, but others would have likely filed bugs by now, and so on. It was moved out of opt long ago. The only recent change was to move from a patch to sed, and changed location from /usr/share/firebird to /usr/lib/firebird. Please check your /etc/conf.d/firebird file, and make sure the FIREBIRD entry is as follows. FIREBIRD=/usr/lib/firebird
Shame on me I completely overlooked the conf.d file, and yes the problem is that FIREBIRD is still pointing to /opt/firebird, changing it to /usr/lib/firebird solves the character sets problem (and some UDF problems), but somehow etc-update did not reported that /etc/conf.d/firebird has an update. Closing the bug ?
etc-update should have caught that. Maybe it was accidentally overlooked. Changes there have always been caught here. But glad you were able to resolve your issue. I wasn't aware of any problems like that with the package. Glad to know they don't really exist :) Closing as invalid.
*** Bug 249614 has been marked as a duplicate of this bug. ***
