Bug#689791: #689791 php5-xdebug: modifies conffiles during distupgrade from squeeze (policy 10.7.3): /etc/php5/mods-available/xdebug.ini

2012-11-10 Thread Lior Kaplan 
On Sun, Oct 14, 2012 at 1:05 AM, Stuart Prescott stu...@debian.org wrote:

 * the path in squeeze's xdebug.ini probably should not have been there to
 begin with; it needs to be removed in a policy compliant fashion during the
 squeeze-wheezy upgrade.


I wish this was true, but the full path is an upstream requirement. See
http://xdebug.org/docs/install

Kaplan

Bug#689791: #689791 php5-xdebug: modifies conffiles during distupgrade from squeeze (policy 10.7.3): /etc/php5/mods-available/xdebug.ini

2012-10-13 Thread Stuart Prescott 

Looking at this bug, the following seems to be required:

* the use of ucf should be continued -- the conversion from a configuration 
file 
managed by ucf to a conffile managed by dpkg needs to be done carefully. Most 
of 
squeeze's ucf probably should still be in the wheezy package

* dpkg-maintscript-helper mv_conffile shouldn't be used on ucf-managed 
configuration files

* the path in squeeze's xdebug.ini probably should not have been there to 
begin with; it needs to be removed in a policy compliant fashion during the 
squeeze-wheezy upgrade.

cheers
Stuart


-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprintBE65 FD1E F4EA 08F3 23D4 3C6D 9FE8 B8CD 71C5 D1A8
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB  891D BBC1 7EBB 1396 F2F7


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#689791: #689791 php5-xdebug: modifies conffiles during distupgrade from squeeze (policy 10.7.3): /etc/php5/mods-available/xdebug.ini

2012-10-07 Thread Lior Kaplan 
I guess this is due to this line:

 Preserving user changes to /etc/php5/mods-available/xdebug.ini (renamed
 from /etc/php5/conf.d/xdebug.ini)...


The problem might be bigger than the policy violation, as if the config
file holds the old so file location, the extension won't load - so the
package will be defacto broken.

This might be relevant for more PHP extensions.

It would be a great help if you could provide me the content of both files
before and after the upgrade.

Kaplan