apache2 php7.0 conf.d links

Hello and thank you for this bug report!

What version of php7.0 do you see this with (`apt-cache policy libapache2-mod-php7.0`). With a fresh LXC container and 7.0.4-7ubuntu2, here is what I see:

lrwxrwxrwx 1 root root 39 May 4 15:42 10-opcache.ini -> /etc/php/7.0/mods-available/opcache.ini
lrwxrwxrwx 1 root root 35 May 4 15:42 10-pdo.ini -> /etc/php/7.0/mods-available/pdo.ini
lrwxrwxrwx 1 root root 40 May 4 15:42 20-calendar.ini -> /etc/php/7.0/mods-available/calendar.ini
lrwxrwxrwx 1 root root 37 May 4 15:42 20-ctype.ini -> /etc/php/7.0/mods-available/ctype.ini
lrwxrwxrwx 1 root root 36 May 4 15:42 20-exif.ini -> /etc/php/7.0/mods-available/exif.ini
lrwxrwxrwx 1 root root 40 May 4 15:42 20-fileinfo.ini -> /etc/php/7.0/mods-available/fileinfo.ini
lrwxrwxrwx 1 root root 35 May 4 15:42 20-ftp.ini -> /etc/php/7.0/mods-available/ftp.ini
lrwxrwxrwx 1 root root 39 May 4 15:42 20-gettext.ini -> /etc/php/7.0/mods-available/gettext.ini
lrwxrwxrwx 1 root root 37 May 4 15:42 20-iconv.ini -> /etc/php/7.0/mods-available/iconv.ini
lrwxrwxrwx 1 root root 36 May 4 15:42 20-json.ini -> /etc/php/7.0/mods-available/json.ini
lrwxrwxrwx 1 root root 36 May 4 15:42 20-phar.ini -> /etc/php/7.0/mods-available/phar.ini
lrwxrwxrwx 1 root root 37 May 4 15:42 20-posix.ini -> /etc/php/7.0/mods-available/posix.ini
lrwxrwxrwx 1 root root 40 May 4 15:42 20-readline.ini -> /etc/php/7.0/mods-available/readline.ini
lrwxrwxrwx 1 root root 37 May 4 15:42 20-shmop.ini -> /etc/php/7.0/mods-available/shmop.ini
lrwxrwxrwx 1 root root 39 May 4 15:42 20-sockets.ini -> /etc/php/7.0/mods-available/sockets.ini
lrwxrwxrwx 1 root root 39 May 4 15:42 20-sysvmsg.ini -> /etc/php/7.0/mods-available/sysvmsg.ini
lrwxrwxrwx 1 root root 39 May 4 15:42 20-sysvsem.ini -> /etc/php/7.0/mods-available/sysvsem.ini
lrwxrwxrwx 1 root root 39 May 4 15:42 20-sysvshm.ini -> /etc/php/7.0/mods-available/sysvshm.ini
lrwxrwxrwx 1 root root 41 May 4 15:42 20-tokenizer.ini -> /etc/php/7.0/mods-available/tokenizer.ini

Did you happen to install 16.04 before release? There might have been version of php7.0 during the development cycle that had broken symlinks and the upgrade path during development cycle may not have fixed them up.

Hi Nish,

sure, I had first beta. I installed it today, but they were purged some weeks ago (I always clean all settings).
I did purge again today (both php and apache) and the files I sent you are still there.

Probably, the purge should have cleaned also
10-opcache.ini -> /etc/php/mods-available/opcache.ini
20-gd.ini -> /etc/php/mods-available/gd.ini
20-intl.ini -> /etc/php/mods-available/intl.ini
20-json.ini -> /etc/php/mods-available/json.ini
20-ldap.ini -> /etc/php/mods-available/ldap.ini
20-pdo_pgsql.ini -> /etc/php/mods-available/pdo_pgsql.ini
20-pgsql.ini -> /etc/php/mods-available/pgsql.ini
20-readline.ini -> /etc/php/mods-available/readline.ini

Thanks and cheers! Petr

So what I'm guessing has happend is that these were busted symlinks from sometime ago. And since the links point outside the currently supported inidir (which is /etc/php/7.0/mods-available as you noted), the purge/remove scripts are refusing to delete them. The packaging is basically treating those links like user-local customization, correctly.

I am unable to reproduce the issue with 16.04 release, can you confirm that? On purge, I do get a warning:

dpkg: warning: while removing libapache2-mod-php7.0, directory '/etc/php/7.0/apache2/conf.d' not empty so not removed

which might be the problem you are seeing too (and dpkg is doing its best to tell you manual intervention is necessary).

Thanks, I understand. They were fragments. When I purge those packages at the moment, everything is correct.