There's no know reason to set XDG_* variables at least ATM: * PostgreSQL collections don't install any systemtap files (as e.g. ruby does) * we don't install any bash completion scripts (I'm mentioning this because there's theoretical chance that RHEL7's bash completion (epel) could be updated to support XDG_DATA_DIRS). Feel free to reopen if there are some other (new) facts.
Ok, I'll try to switch this to TestOnly bug -> maybe the test could be edited so it would report FAILURE for XDG_DATA_DIRS only if collection installs some stap/bash-completion file.
*** Bug 1473252 has been marked as a duplicate of this bug. ***
Well, XDG_* variables are set in enable scriplet and that is the reason why test complains. At least in rh-postgresql95-runtime-2.2-2.el7.x86_64: # For XMvn to locate its configuration file(s) export XDG_CONFIG_DIRS="/etc/opt/rh/rh-postgresql95/xdg:${XDG_CONFIG_DIRS:-/etc/xdg}" # For systemtap export XDG_DATA_DIRS="/opt/rh/rh-postgresql95/root/usr/share${XDG_DATA_DIRS:+:${XDG_DATA_DIRS}}" Original bug is still present # scl enable rh-postresql95 gedit ... /var/tmp/sclR7PKLx: line 8: 11420 Trace/breakpoint trap gedit So, can we either fix XDG export or remove it if we really don't need it?
Ouch, you are right. This is result of my blindness .. I thought that the XDG_* variables are not set by PostgreSQL collections -- but those apparently (and mistakenly) are. Switching back against PostgreSQL, thanks and sorry. So to the best of my knowledge, the XDG_* variables were added with some wide all-collection sync-up during RHSCL 2.0 development of rh-postgresql94 (commit 627d9568a7dde5). IMO the cleanest fix is to not set XDG_* variables.
Btw. another tool using XDG_DATA_* is xmvn (mentioned by hhorak on irc). Since we don't build java packages against this collection, we should be fine too.
*** Bug 1486089 has been marked as a duplicate of this bug. ***
Upstream fix: https://github.com/sclorg/postgresql-meta/commit/16e8c39585600fa6fff8660674d0e61b0d6f382c
Red Hat does not currently plan to provide any further changes to this collection in a Red Hat Software Collections update release. This software collection is nearing the retirement date (May 2019) after which customers are encouraged to upgrade to a later release. Please contact Red Hat Support if you have further questions, or refer to the support lifecycle page for more information. https://access.redhat.com/support/policy/updates/rhscl/
In accordance with the Red Hat Software Collections Product Life Cycle, the support period for this collection has ended. New bug fix, enhancement, and security errata updates, as well as technical support services will no longer be made available for this collection. Customers are encouraged to upgrade to a later release. Please contact Red Hat Support if you have further questions, or refer to the support lifecycle page for more information. https://access.redhat.com/support/policy/updates/rhscl/