Source: gtk-sharp2
Version: 2.12.40-3
Severity: serious
Tags: upstream
See the discussion on the Debian Rust maintainers list for background:
https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html
While that discussion is about Rust packages that were rejected, the same
situation also applies to gtk-sharp2 unfortunately. For more details how to
solve
this in a way that makes ftp-masters happy, please refer to them.
Affected files are atk/atk-api.raw, gtk/gtk-api.raw and the other */*-api.raw
files. These files were autogenerated from specific versions of the underlying
C libraries and it's not clear which versions were used.
Debian ships these C libraries but certainly in different versions so it's not
possible to regenerate these files with what is available in Debian.
It will be necessary to either include the source code of the C libraries in
the exact version, or regenerate the files at build time with whatever is
available in Debian.
The latter will probably generate different bindings, potentially even with
different API, so is probably not a useful solution.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (700, 'unstable'), (500, 'unstable-debug'), (100,
'experimental'), (1, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
