Logrotate no longer supports symlinked configuration files not owned by root

[Ben Turner]

We have been using logrotate 3.7.8 (as part of an Ubuntu 12 build) for a long time. When we deploy our application, which has configuration files owned by ubuntu user, we create a symlink from the logrotate configuration directory (/etc/logrotate.d) to this configuration file, which casues our log files to be correctly rotated.

With our new server build, Ubuntu 14 running logrotate 3.8.7, this behaviour has now broken. Running logrotate with the -d flag reveals why:

"Ignoring app-config-file because the file owner is wrong (should be root)."

This appears to be a regression from the 3.7.x release stream of logrotate ?

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: logrotate 3.8.7-1ubuntu1
ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Thu Aug 14 10:43:48 2014
Ec2AMI: ami-43128a79
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: ap-southeast-2a
Ec2InstanceType: m3.large
Ec2Kernel: aki-c362fff9
Ec2Ramdisk: unavailable
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.