On Fri, 2024-01-19 at 11:08 +, Ralph Corderoy wrote:
> Say my first install of a package creates /etc/p.conf. I don't edit it.
> Then the package is upgraded; upstream provide an altered p.conf.
> I'd expect p.conf to be changed and I think that's what happens.
>
> Similarly, if the package m
Hi Ralf,
> > why doesn't pacman change the permissions at package upgrade?
...
> Custom, unusual permissions may be required for a user's system.
Yes.
> IMO permissions are similar to configurations. New configurations are
> required from time to time, but you don't want that a package upgrade
PS:
Have you never been bitten by an /etc/foo.d/99.conf that made other
configurations null and void?
The *.pacnew approach fails when a package introduces a new
configuration through a drop-in file.
The advantage of a drop-in file is that it can automatically add
something new, but the disadvan
On Thu, 2024-01-18 at 22:21 +0100, deMaio wrote:
> why doesn't pacman change the permissions at package upgrade?
Hi,
I am not an Arch developer, just another Arch user.
Custom, unusual permissions may be required for a user's system.
If upstream or an Arch developer sees reasons to change the p
Am Thu, Jan 18, 2024 at 08:01:45PM +0100 schrieb Jan Alexander Steffens
(heftig):
> The permissions were recently changed to conform to upstream expectations.
> You can correct them on your system using:
>
> install -d -o root -g root -m 0755 /usr/share/polkit-1/rules.d
Not OP but thanks for you
On Thu, Jan 18, 2024 at 5:51 PM Jude DaShiell wrote:
> warning: directory permissions differ on /usr/share/polkit-1/rules.d/
> filesystem: 750 package: 755
> (5/6) upgrading polkit
> []
> 100%warning: directory permissions d
On Thu, 2024-01-18 at 10:32 -0500, Jude DaShiell wrote:
> What are correct permissions for these directories and has the upgrade
> corrected permissions that neede correction?
Hi,
the correct permissions are those, that are correct from your point of
view. No, the upgrade does not change your ind
