Massimiliano Torromeo (3a9502fc) at 25 Oct 13:31
upgpkg: 7.2.2-3: OpenSSL 4 rebuild
Massimiliano Torromeo (233057f9) at 25 Oct 13:31
upgpkg: 7.2.2-3: OpenSSL 4 rebuild
During the last two update from pcp I got the following information:
(26/33) upgrading pcp [########################################################################################################################] 100% warning: directory permissions differ on /var/log/pcp/pmcd/ filesystem: 775 package: 755
After the update I fixed the issue with chmod 755 /var/log/pcp/pmcd/. But with the next update I got the information again. I could not find the reason, why it is incorrect.
package version(s): upgraded pcp (7.0.2-1 -> 7.0.3-1)
config and/or log files:
link to upstream bug report, if any:
Install an older version and make an update with pacman -Syu
`etc/pcp/pmcd/rc.local` seems to be a symlink to `../../../usr/lib/pcp/services/local` and it always seems to generate a pacnew when upgraded. Is it necessary for this file to be backed up?
Massimiliano Torromeo (1f66e283) at 22 Oct 22:09
upgpkg: 7.2.2-2: Removed rc.local from backup array (Fixes #16)
Massimiliano Torromeo (10071c33) at 22 Oct 22:09
upgpkg: 7.2.2-2: Removed rc.local from backup array (Fixes #16)
... and 1 more commit
@mtorromeo, while looking into #16 (closed), I noticed that the issue in this ticket is still present. It could be "fixed" by setting 775 on /var/log/pcp/pmcd/ in the PKGBUILD. Are you interested in implementing this? If not, then I suggest we close the ticket due to lack of interest.. then users will just have to accept the anomaly. Thanks.
it always seems to generate a pacnew when upgraded
Hmm, yeah that's mildly annoying.. can repro. It almost seems like a possible pacman bug? I don't see why it should do that.. It being a symlink seems to confuse pacman.. This "upstream" pacman issue seems related: pacman/pacman#97
@mtorromeo, any thoughts? Would you be amenable to removing it from the backup array?
`etc/pcp/pmcd/rc.local` seems to be a symlink to `../../../usr/lib/pcp/services/local` and it always seems to generate a pacnew when upgraded. Is it necessary for this file to be backed up?
{
"pkgbase": "pcp",
"status": "success",
"message": null,
"local_version": "7.2.1",
"upstream_version": "7.2.2",
"out_of_date": true
}Upstream URL: https://pcp.io
Package URL: https://archlinux.org/packages/?name=pcp
Nvchecker URL: https://github.com/performancecopilot/pcp
Massimiliano Torromeo (103b735f) at 19 Oct 10:17
upgpkg: 7.2.2-1
Massimiliano Torromeo (5d77bf26) at 19 Oct 10:17
upgpkg: 7.2.2-1
Antonio Rojas (666d25a1) at 17 Oct 18:00
upgpkg: 7.2.1-2: perl 5.44 rebuild
Antonio Rojas (3da7da31) at 17 Oct 18:00
upgpkg: 7.2.1-2: perl 5.44 rebuild
{
"pkgbase": "pcp",
"status": "success",
"message": null,
"local_version": "7.2.1",
"upstream_version": "7.2.2",
"out_of_date": true
}Upstream URL: https://pcp.io
Package URL: https://archlinux.org/packages/?name=pcp
Nvchecker URL: https://github.com/performancecopilot/pcp
Current version 7.2.1 is latest, closing the issue.
{
"pkgbase": "pcp",
"status": "success",
"message": null,
"local_version": "7.2.0",
"upstream_version": "7.2.1",
"out_of_date": true
}Upstream URL: https://pcp.io
Package URL: https://archlinux.org/packages/?name=pcp
Nvchecker URL: https://github.com/performancecopilot/pcp
Massimiliano Torromeo (c6e90956) at 16 Sep 10:07
upgpkg: 7.2.1-1
Massimiliano Torromeo (5a79e1fc) at 16 Sep 10:07
upgpkg: 7.2.1-1
{
"pkgbase": "pcp",
"status": "success",
"message": null,
"local_version": "7.2.0",
"upstream_version": "7.2.1",
"out_of_date": true
}Upstream URL: https://pcp.io
Package URL: https://archlinux.org/packages/?name=pcp
Nvchecker URL: https://github.com/performancecopilot/pcp