On Mon, 2025-12-08 at 08:47 +0100, Christian Kastner wrote: > the tracker page for ggml [1] says it's blocked, but the "issues > preventing migration" point is empty.
The cron log for the most recent britney run includes: I: [2025-12-08T16:04:14+0000] - signer mismatch for libggml0-backend-cuda (ggml 0.9.4-5) on amd64: [email protected], while [email protected] already listed I: [2025-12-08T16:04:14+0000] - signer mismatch for libggml0-backend-vulkan (ggml 0.9.4-5) on amd64: [email protected], while [email protected] already listed What appears to have happened is that you uploaded binary packages for amd64, including the two listed above. A binNMU was then scheduled so as not to block migration, but which did _not_ build the listed packages. There are thus amd64 binary packages from the 0.9.4-5 source in unstable built from two different uploads, one signed by you and one by the buildd. That situation seems to be confusing britney (not unreasonably). A new source upload would resolve that issue, but I've not checked the packaging in terms of what the expected outcome for the two packages listed above is. Regards, Adam
