Hm, I don't know what was going on. I thought I reproduced it by reinstalling imagemagick, not realizing that the binaries were provided by imagemagick-6.q16. I just purged that package and reinstalled from the server (a different one than the original), and all is good. Sorry for the noise. You can close this bug report. Obviously PEBKAC of some sort.
Just to be complete here is the output but I don't think its relevant at this point: $ dpkg-statoverride --list geoclue geoclue 755 /var/lib/geoclue root lp 775 /var/log/hp/tmp root games 2755 /usr/games/tuxtype root games 2775 /var/games/tuxtype/words root sasl 660 /etc/sasldb2 root crontab 2755 /usr/bin/crontab root sasl 710 /var/run/saslauthd root Debian-exim 640 /etc/exim4/passwd.client root mlocate 2755 /usr/bin/mlocate root ssl-cert 710 /etc/ssl/private hplip root 755 /var/run/hplip root messagebus 4754 /usr/lib/dbus-1.0/dbus-daemon-launch-helper all the best, Robert On 03/06/15 02:54 AM, Vincent Fourmond wrote: > control: tag -1 unreproducible > > Hello, > > On Wed, Jun 3, 2015 at 7:59 AM, Robert Sohn <[email protected]> wrote: >> The mogrify command does not have the execute bit set so the command >> fails. I purged imagemagick and reinstalled (tried several debian >> servers) and the result was the same. >> >> $ ls -l $(readlink -f /usr/bin/mogrify) >> -rw-r--r-- 1 root root 6320 Jan 5 16:32 >> /usr/lib/x86_64-linux-gnu/ImageMagick-6.8.9/bin-Q16/mogrify > > I can't explain that. > > I have: > > ~ ls -l $(readlink -f /usr/bin/mogrify) > -rwxr-xr-x 1 root root 6320 Jan 5 22:32 > /usr/lib/x86_64-linux-gnu/ImageMagick-6.8.9/bin-Q16/mogrify > > ~ dpkg -c /var/cache/apt/archives/imagemagick-6.q16_8%3a6.8.9.9-5_amd64.deb > | grep mogr > -rwxr-xr-x root/root 6320 2015-01-05 22:32 > ./usr/lib/x86_64-linux-gnu/ImageMagick-6.8.9/bin-Q16/mogrify > > > Maybe you have a long standing statoverride ? What does the > following command say ? > > ~ dpkg-statoverride --list > > Cheers, > > Vincent > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
