Public bug reported:
Release: Artful Aardvark 17.10
Package Version: 0.7.1-2
As far as I can tell (after creating a local patch and building and
installing them as Multi-Arch: same) libxkbcommon-dev and
libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no
additional changes. Note that in order to cross-build the package, I
also patched the build dependency x11-xkb-utils as Multi-Arch: allowed,
and then used an :any dep. The use of :any as a dep is possibly
appropriate, as I successfully built the package this way, I think only
the tests depend on it, and they seem to call the binaries at runtime
rather than compiling against them.
** Affects: libxkbcommon (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
+ Release: Artful Aardvark 17.10
+ Package Version: 0.7.1-2
+
As far as I can tell (after creating a local patch and building and
installing them as Multi-Arch: same) libxkbcommon-dev and
libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no
additional changes. Note that in order to cross-build the package, I
also patched the build dependency x11-xkb-utils as Multi-Arch: allowed,
and then used an :any dep. The use of :any as a dep is possibly
appropriate, as I successfully built the package this way, I think only
the tests depend on it, and they seem to call the binaries at runtime
rather than compiling against them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu.
https://bugs.launchpad.net/bugs/1720692
Title:
Add multiarch metadata to libxkbcommon*dev packages
Status in libxkbcommon package in Ubuntu:
New
Bug description:
Release: Artful Aardvark 17.10
Package Version: 0.7.1-2
As far as I can tell (after creating a local patch and building and
installing them as Multi-Arch: same) libxkbcommon-dev and
libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no
additional changes. Note that in order to cross-build the package, I
also patched the build dependency x11-xkb-utils as Multi-Arch:
allowed, and then used an :any dep. The use of :any as a dep is
possibly appropriate, as I successfully built the package this way, I
think only the tests depend on it, and they seem to call the binaries
at runtime rather than compiling against them.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1720692/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp