Control: tag -1 +confirmed Ralf Treinen <trei...@free.fr> writes:
> > automatic installation tests of packages that share a file and at the > same time do not conflict by their package dependency relationships has > detected the following problem: > > > Selecting previously unselected package fonts-droid. > (Reading database ... 10934 files and directories currently installed.) > Preparing to unpack .../fonts-droid_1%3a4.4.4r2-7_all.deb ... > Unpacking fonts-droid (1:4.4.4r2-7) ... > Selecting previously unselected package fonts-droid-fallback. > Preparing to unpack .../fonts-droid-fallback_1%3a6.0.0r26-1_all.deb ... > Unpacking fonts-droid-fallback (1:6.0.0r26-1) ... > dpkg: error processing archive > /var/cache/apt/archives/fonts-droid-fallback_1%3a6.0.0r26-1_all.deb > (--unpack): > trying to overwrite > '/usr/share/fonts/truetype/droid/DroidSansFallbackFull.ttf', which is also in > package fonts-droid 1:4.4.4r2-7 > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) > Errors were encountered while processing: > /var/cache/apt/archives/fonts-droid-fallback_1%3a6.0.0r26-1_all.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) Oops I put wrong version in Breaks and Replaces! > > > This is a serious bug as it makes installation fail, and violates > sections 7.6.1 and 10.1 of the policy. An optimal solution would > consist in only one of the packages installing that file, and renaming > or removing the file in the other package. Depending on the > circumstances you might also consider Replace relations or file > diversions. If the conflicting situation cannot be resolved then, as a > last resort, the two packages have to declare a mutual > Conflict. Please take into account that Replaces, Conflicts and > diversions should only be used when packages provide different > implementations for the same functionality. > > Here is a list of files that are known to be shared by both packages > (according to the Contents file for sid/amd64, which may be > slightly out of sync): > > /etc/fonts/conf.avail/69-droid-sans-fallback.conf > /etc/fonts/conf.d/69-droid-sans-fallback.conf > /usr/share/fonts/truetype/droid/DroidSansFallbackFull.ttf > > This bug has been filed against both packages. If you, the maintainers of > the two packages in question, have agreed on which of the packages will > resolve the problem please reassign the bug to that package. You may then > also register in the BTS that the other package is affected by the bug. fonts-droid will be removed from archive as its no longer shipped as part of fonts-android. This happened only because of wrong version in Breaks, Replaces relation. I will fix this and request for new upload soon.