FS#43616 - [colord] directory ownership differs - add explanation howto to package update message
Attached to Project:
Arch Linux
Opened by Patcom (Patcom) - Wednesday, 28 January 2015, 19:31 GMT
Last edited by Eli Schwartz (eschwartz) - Wednesday, 03 January 2018, 17:05 GMT
Opened by Patcom (Patcom) - Wednesday, 28 January 2015, 19:31 GMT
Last edited by Eli Schwartz (eschwartz) - Wednesday, 03 January 2018, 17:05 GMT
|
Details
During the update of colord (1.2.7-2 -> 1.2.8-1) a
warning is shown:
warning: directory ownership differs on /var/lib/colord/icc/ This seems to be related to https://bugs.archlinux.org/task/43189 . There is also the suggested fix (chown). Please save all colord users searching in the package history to find out why they have a differing ownership on their system by just adding a update message which is shown by pacman. E.g. this: > If you are updating and get a "directory ownership differs" warning: There was a bug in this package which caused a wrong directory ownership. Please fix the ownership of the icc directory manually: chown colord:colord /var/lib/colord/icc |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Wednesday, 03 January 2018, 17:05 GMT
Reason for closing: Not a bug
Wednesday, 03 January 2018, 17:05 GMT
Reason for closing: Not a bug
chown colord:colord /var/lib/colord/icc
or directly in the PKGBUILD
That could be saved if the package update would just say "WE messed up, please fix it". Of course, if fixing it automatically (what patrick means, I guess) is safe, that would even be better.
For me, this is a pair: break something and if you broke it, fix it. Here we have just a break. The fact that there is a break is reported by pacman. To me it is just natural to investigate why there is a unexpected(!) break.
Is that causing any trouble somewhere else to show a message? I mean, what are the downsides (except of some lines of terminal space of "cavaliers")?
This happens for some packages every few months, sometimes triggered by upstream (often?) or downstream (seldom?).
Possible causes are initally wrong permissions or newly added files by the package, which where formerly maybe created by the software and vice versa.
Pacman itself is acting here correct, it looks after clean and consistend of all packages on the filesystem.
The new package itself is also correct.
If some owner or mode permissions differs, the root user has to care about. Especially because sometimes files could be created by the software itself but later be provided by the package.
I answer here because this happened within 24 hours for libvirt and colord and searched for this unusual accumulation (few months...).
I would be appreciate it, if maintainers of a package handle the individual cases automatically if this is possible without risking breakage. If this is not possible, a short notice which is no merely a warning would be very nice.
A terse and concise message is enough.
I think this bug could be closed?
So, in essence, it just would be beneficial if packagers could take more care of such situations in future, as Peter said, and this bug can be closed as there is nothing useful to do.