Bug 350377 - Build should explicitly set umask (to 0022 probably)
Summary: Build should explicitly set umask (to 0022 probably)
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.7.2
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-19 14:27 UTC by Martin Nicholas
Modified: 2021-03-27 14:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Nicholas 2015-07-19 14:27:42 UTC
No assumption should be made about umask when building and it should be set explicitly, probably to 0022.
An example problem is that generated files in  /usr/share/mime/ are made readable only by root if umask is set to a tighter value

Reproducible: Always

Steps to Reproduce:
1. set umask to 0077
2. Build
3. Install

Actual Results:  
Many mimetypes not found in KDE as files mentioned above cannot be read
Comment 1 Justin Zobel 2021-03-10 00:16:15 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 2 Jack 2021-03-10 01:06:43 UTC
I'd say that if you are building from source, you have responsibility to understand your build environment and set things accordingly.  I have built KMM from source for many years, and never had a problem, but I've probably kept my umask at the default 0022.  Do you know of any other build systems which explicitly change umask or file permissions?
Comment 3 Bug Janitor Service 2021-03-25 04:33:38 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!