user debian...@lists.debian.org usertags 1063664 + fileconflict reassign 1063664 gnat-13-aarch64-linux-gnu,gnat-13-arm-linux-gnueabihf,gnat-13-i686-linux-gnu,gnat-13-powerpc64le-linux-gnu,gnat-13-riscv64-linux-gnu,gnat-13-s390x-linux-gnu found 1063664 10.5.0-1cross2 affects 1063664 + gnat-10-aarch64-linux-gnu gnat-10-arm-linux-gnueabihf gnat-10-i686-linux-gnu gnat-10-powerpc64le-linux-gnu gnat-10-riscv64-linux-gnu gnat-10-s390x-linux-gnu gnat-11-aarch64-linux-gnu gnat-11-arm-linux-gnueabihf gnat-11-i686-linux-gnu gnat-11-powerpc64le-linux-gnu gnat-11-riscv64-linux-gnu gnat-11-s390x-linux-gnu gnat-12-aarch64-linux-gnu gnat-12-arm-linux-gnueabihf gnat-12-i686-linux-gnu gnat-12-powerpc64le-linux-gnu gnat-12-riscv64-linux-gnu gnat-12-s390x-linux-gnu gnat-9-aarch64-linux-gnu gnat-9-arm-linux-gnueabihf gnat-9-i686-linux-gnu gnat-9-powerpc64le-linux-gnu gnat-9-riscv64-linux-gnu gnat-9-s390x-linux-gnu tags 1063664 + patch thanks
On Sat, Feb 10, 2024 at 07:55:09PM +0100, Andreas Beckmann wrote: > there are undeclared file conflicts between gnat-13-<triplet> and > gnat-{9,10}-<triplet> in sid. (but not between -9- and -10-). > Maybe it would be sufficient to rebuild the package against gcc-13 > 13.2.0-13 which had some gnat conflict fixes. I confirm. Usually, the higher gnat version declares Conflicts for the lower one. Starting with gcc-14, the unversioned link is no longer provided and gnat is part of gcc-defaults, so this problem will go away in future. I also verified that src:gcc-13 already issues these Conflicts and that a no-change upload of gcc-13-cross adds these Conflicts to the cross toolchain packages. Hence tagging the issue as patch. Matthias, would you do that upload? Helmut