We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As reported by Alexandre Detiste in Debian Bug #948727 for QGIS 3.4.14:
when run, /var/lib/dpkg/info/qgis-providers.postinst will create these files /root/.local/share/crssync /root/.local/share/crssync/profiles /root/.local/share/crssync/profiles/default /root/.local/share/crssync/profiles/default/palettes or these (worse): /.local/share/crssync /.local/share/crssync/profiles /.local/share/crssync/profiles/default /.local/share/crssync/profiles/default/palettes Would it be possible to overide this behaviour to keep the system clean ?
when run, /var/lib/dpkg/info/qgis-providers.postinst will create these files
/var/lib/dpkg/info/qgis-providers.postinst
/root/.local/share/crssync /root/.local/share/crssync/profiles /root/.local/share/crssync/profiles/default /root/.local/share/crssync/profiles/default/palettes
or these (worse):
/.local/share/crssync /.local/share/crssync/profiles /.local/share/crssync/profiles/default /.local/share/crssync/profiles/default/palettes
Would it be possible to overide this behaviour to keep the system clean ?
These empty directories serve no purpose, and should indeed not be created by default.
The text was updated successfully, but these errors were encountered:
crssync: put profile to temporary directory (fixes qgis#33743)
e1fb52b
be4f45e
94312ac
crssync: put profile to temporary directory (fixes #33743)
db8073b
thanks
Sorry, something went wrong.
jef-n
No branches or pull requests
As reported by Alexandre Detiste in Debian Bug #948727 for QGIS 3.4.14:
These empty directories serve no purpose, and should indeed not be created by default.
The text was updated successfully, but these errors were encountered: