Hi, On Wed, Sep 06, 2017 at 12:07:48PM +0200, Andreas Beckmann wrote: > On 2017-09-01 11:33, Adrian Bunk wrote: > > Based on https://lintian.debian.org/tags/binaries-have-file-conflict.html > > I didn't know about that one :-)
Nor did I. I suppose that this lintian check only recognizes file conflicts between the binary packages generated from the same source package? If that is the case then it will already help a lot. > > I recently went manually through possible file conflicts in -dbgsym packages > > (caused by copies of a binary in several binary packages built by the same > > > Automated piuparts testing of file conflicts should be extended > > to also include -dbgsym, for covering such bugs automatically. > > That's more the domain of the DOSE based checks done by Ralf (sid only) > and me (locally, using piuparts as backend, including cross-distro > tests). I could probably hack -debug into these, too. I don't think that there remains anything to be done from the dose side, the existing tools for finding test candidates should be sufficient. One needs of course a Contents file for the dbgsym packages. Is it is possible to have a file conflict between two -dbgsym packages, without having the same file conflict already between the two binary packages? Do you have a case where this happens? Maybe it can happen when the packages use dpkg-divert, and these diversions are not mimicked by the -dbgsym packages? I have to admit that I don't know anything about the -dbgsym packages. -Ralf. -- Ralf Treinen Institut de Recherche en Informatique Fondamentale Équipe Preuves, Programmes et Systèmes Université Paris Diderot, Paris, France. http://www.irif.fr/~treinen/