Bug#829742: dpkg-maintscript-helper fails to convert directory to symlink on upgrade

[Tobias Hansen]

Hi Jerome,

ok, if you think it does not need to be fixed, you can close the bug.

I should mention that a workaround to get the package configured is to
just delete the folder /usr/share/doc/libmpfi-dev.

Best,
Tobias

On 07/05/2016 07:42 PM, Jerome BENOIT wrote:
> Hi Tobias, thanks for the report.
> 
> 
> 
> On 05/07/16 18:46, Tobias Hansen wrote:
>> Source: mpfi
>> Version: 1.5.1+ds-4
>> Severity: grave
>> Justification: prevents package upgrade
> 
>> Hi Jerome,
> 
>> When upgrading from version 1.5.1+ds-2, I get the following error:
> 
>> Preparing to unpack .../libmpfi-dev_1.5.1+ds-4_amd64.deb ...
>> dpkg-query: no packages found matching libmpfi-dev:amd64
>> dpkg-query: package 'libmpfi-dev' is not installed
>> Use dpkg --info (= dpkg-deb --info) to examine archive files,
>> and dpkg --contents (= dpkg-deb --contents) to list their contents.
>> dpkg-maintscript-helper: error: directory '/usr/share/doc/libmpfi-dev'
>> contains files not owned by package libmpfi-dev:amd64, cannot switch to
>> symlink
>> dpkg: error processing archive
>> /var/cache/apt/archives/libmpfi-dev_1.5.1+ds-4_amd64.deb (--unpack):
>>  subprocess new pre-installation script returned error exit status 1
>> Errors were encountered while processing:
>>  /var/cache/apt/archives/libmpfi-dev_1.5.1+ds-4_amd64.deb
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
>> The directory contains the following files
> 
>> ls /usr/share/doc/libmpfi-dev
>> changelog.Debian.gz  changelog.gz  copyright
> 
> Indeed the migration part of the story had been messed up for a while:
> a couple of fixes has been done to fix it. Tests via piuparts and the absence
> of any piuparts bugreport let me think that is now working with the current
> distributed versions:  1.5.1-1, 1.5.1-3, and 1.5.1+ds-4 .
> Your former version, according to the report is 1.5.1+ds-2, a buggy one
> that was for a short while in testing or unstable: my guess is that we
> can consider it as over. Otherwise, I am not sure if it is relevant
> to fix this very migration as it is quite unlikely while I am not sure
> how to reproduce it.
> 
> Thanks,
> Jerome
> 
> 
> 
>> Best,
>> Tobias
> 
> 
>