Bug#1050989: firmware-carl9170: undeclared file conflict with firmware-linux-free

2023-11-24 Thread Helmut Grohne
User: helm...@debian.org
Usertags: dep17p1

On Fri, Sep 01, 2023 at 07:13:13AM +0200, Helmut Grohne wrote:
> firmware-carl9170 installs /lib/firmware/carl9170-1.fw, which is also
> currently installed by firmware-linux-free. I see that this is quite
> intentional as this piece of firmware is being split out from the larger
> firmware package. On a packaging level, this needs to be addressed with
> Replaces, Conflicts or diversions. Failing to do so, results in an
> unpack error from dpkg. I understand that getting the firmware removed
> from firmware-linux-free may take a bit and you can only then set up the
> correct Breaks+Replaces. That's fine. Just keep this bug open until that
> matter is resolved.

As linux-firmware-free moves from / to /usr. This will become a DEP17 P1
file loss problem (the one that spurred the original file move
moratorium). Situations like this is exactly why dumat is also reporting
file conflicts: The resulting Breaks+Replaces may become insufficient.
As you resolve this conflict, please do not use Breaks+Replaces and use
versioned Conflicts instead. I suggest that you add a comment
referencing "DEP17 P1 M7". https://subdivi.de/~helmut/dep17.html has
sections explaining the problem and the chosen mitigation.

Helmut



Bug#1050989: firmware-carl9170: undeclared file conflict with firmware-linux-free

2023-08-31 Thread Helmut Grohne
Package: firmware-carl9170
Version: 1.9.9-399-gcd480b9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + firmware-linux-free

firmware-carl9170 installs /lib/firmware/carl9170-1.fw, which is also
currently installed by firmware-linux-free. I see that this is quite
intentional as this piece of firmware is being split out from the larger
firmware package. On a packaging level, this needs to be addressed with
Replaces, Conflicts or diversions. Failing to do so, results in an
unpack error from dpkg. I understand that getting the firmware removed
from firmware-linux-free may take a bit and you can only then set up the
correct Breaks+Replaces. That's fine. Just keep this bug open until that
matter is resolved.

Helmut