On Wed, Sep 06, 2017 at 02:16:54PM +0200, Ralf Treinen wrote:
>...
> 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 package
On Sat, Sep 09, 2017 at 11:55:26AM +0200, Andreas Beckmann wrote:
> I tried to add sid-debug to my test matrix, but it does not work because
> the Contents file for sid/main is incomplete and for contrib and
> non-free it is empty. Adrian, can you find a reason for this and maybe
> file a bug again
On 2017-09-06 14:16, Ralf Treinen wrote:
>> 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 don
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 con
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 :-)
> I recently went manually through possible file conflicts in -dbgsym packages
> (caused by copies of a binary in several binary packages built by t
Source: piuparts
Severity: normal
Based on https://lintian.debian.org/tags/binaries-have-file-conflict.html
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
source package), and reported these as
6 matches
Mail list logo
