user debian...@lists.debian.org # discodos usertags 966115 + fileconflict affects 966115 + mono-devel # firebird-utils usertags 1040321 + fileconflict affects 1040321 + firebird3.0-server # kodi-addons-dev usertags 1040319 + fileconflict affects 1040319 + kodi-addons-dev-common # libocct-data-exchange-dev usertags 1035009 + fileconflict affects 1035009 + liboce-modeling-dev liboce-visualization-dev # libreoffice-uiconfig-report-builder usertags 1041899 + fileconflict affects 1041899 + libreoffice-report-builder # libsequoia-octopus-librnp usertags 1041832 + fileconflict affects 1041832 + thunderbird # nex usertags 1022957 + fileconflict affects 1022957 + nvi # nfs-ganesha-ceph usertags 1040362 + fileconflict affects 1040362 + nfs-ganesha # python3-notebook usertags 1036996 + fileconflict affects 1036996 + cadabra2 thanks
Hi Andreas and Ralf, On Tue, Jul 18, 2023 at 09:02:08PM +0200, Helmut Grohne wrote: > Is this convincing enough to move forward with the generic > debian...@lists.debian.org usertag fileconflict rather than something > more detailed? Is this also convincing enough to extend it to cover > non-file conflicts or do you want a different tag for that? Should the > tag also cover m-a:same file conflicts? Given the lack of further input, I went ahead and documented the new fileconflict usertag at: https://wiki.debian.org/qa.debian.org/usertagging | fileconflict: bugs identifying a file conflict between packages. Such | bugs can be filed against multiple packages if the causing package is | not known. Otherwise, the other packages should be listed as affected. | This covers all kinds of conflicts including symlink vs directory | conflicts and Multi-Arch: same file conflicts. It also covers file moves | between packages that lack suitable Replaces. Let me know if you want a change to this. The above list of tags is the subset that affects the /usr-merge transition. Helmut
