Johannes Schauer Marin Rodrigues <josch@debian.org> (2025-12-12): > Package: keyboard-configuration > Version: 1.244 > Severity: serious > > Hi, > > steps to reproduce: > > $ mmdebstrap --include=keyboard-configuration unstable /dev/null > [...] > I: installing remaining packages inside the chroot... > done > Reading package lists... > Building dependency tree... > debconf is already the newest version (1.5.91). > libpam-runtime is already the newest version (1.7.0-5). > mawk is already the newest version (1.3.4.20250131-1). > libpam-modules is already the newest version (1.7.0-5). > libpam-modules-bin is already the newest version (1.7.0-5). > Solving dependencies... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > keyboard-configuration : Depends: xkb-data (< 2.42A) but 2.46-1 is to be installed > E: Unable to correct problems, you have held broken packages. > E: The following information from --solver 3.0 may provide additional context: > Unable to satisfy dependencies. Reached two conflicting decisions: > 1. keyboard-configuration:arm64=1.244 is selected for install > 2. keyboard-configuration:arm64 Depends xkb-data (< 2.42A) > but none of the choices are installable: > [no choices] > > > Debian unstable has src:xkeyboard-config with xkb-data version 2.46-1 since > yesterday (2025-12-11). Looking at preparing an src:console-setup upload, it fails to build because xkb-data apparently got totally reshuffled, which I can't really understand by looking at its changelog? /usr/share/X11/xkb/* seems to have moved to /usr/share/xkeyboard-config-2/ without any kind of documentation or heads-up to reverse (build-)depends? There's still an empty directory left behind though. Checking the source debdiff on the xkeyboard-config side, the upstream side is pretty obvious: +## Build system + +### Breaking changes + +- Switched to versioned install directories and files, to enable installing + multiple versions of xkeyboard-config to be installed in parallel. + + - Moved the keyboard keymap data to a namespace dedicated to xkeyboard-config: + `<prefix>/<datadir>/xkeyboard-config-2`. + - Created symbolic link to maintain backward-compatibility with the X11 namespace: + `<prefix>/<datadir>/X11/xkb` → `<prefix>/<datadir>/xkeyboard-config-2`. + - Renamed `pkg-config`, translation and manual files to include a version: + - `<prefix>/<datadir>/pkgconfig/xkeyboard-config-2.pc` + - `<prefix>/<mandir>/man7/xkeyboard-config-2.7` + - `<prefix>/<localedir>/**/xkeyboard-config-2.mo` + - Created unversioned symbolic links to the previous files for backward-compatibility: + - `<prefix>/<datadir>/pkgconfig/`: `xkeyboard-config.pc` → `xkeyboard-config-2.pc` + - `<prefix>/<mandir>/man7/`: `xkeyboard-config.7` → `xkeyboard-config-2.7` + - `<prefix>/<localedir>/**/`: `xkeyboard-config.mo` → `xkeyboard-config-2.mo` + + See [our versioning documentation](VERSIONING.md) for further information. as in: - There *is* a(n intended) breaking change. - They are trying to limit the scope via a symlink. The first part was not communicated, the second part isn't reflected in the packaging. Both of those should have appeared in a binary debdiff though… (as can be checked right now by diffing xkb-data between testing and unstable). Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature