1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.RC

  • Bug#1101487: libkokkos-dev: file conflict as vendered in libtrilinos-ko

    From Jochen Sprickerhof@21:1/5 to All on Fri Mar 28 11:40:01 2025
    Source: libkokkos-dev
    Version: 4.5.01-1.2
    Severity: serious
    X-Debbugs-Cc: Graham Inggs <[email protected]>, Alex Myczko <[email protected]>, Nils Schild <[email protected]>
    User: [email protected]
    Usertags: fileconflict
    Control: affects -1 + libtrilinos-kokkos-dev

    Hi,

    I have NMUed src:kokkos with the intention to get it into trixie. As
    part of it I fixed the multi arch problem by moving the cmake files from /usr/lib/cmake to usr/lib/${DEB_HOST_MULTIARCH}/. Now libkokkos-dev has
    a undeclared file conflict as both provide KokkosConfig.cmake. Even
    more, libtrilinos-kokkos-dev seems to vendor kokkos 3.0 whereas
    libkokkos-dev contains kokkos 4.0. This bug is to block the file
    conflict from migrating to testing and to discuss how to resolve the
    duplicated packaging.

    As I have no deeper insights on both packages nor their downstreams, I
    would be happy to get comments from both maintainers.

    Cheers Jochen

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Nils Schild@21:1/5 to All on Thu Apr 3 19:50:01 2025
    Hi,

    Trilinos can be build with an external Kokkos package if the version
    matches.
    The current required version for Kokkos to be compatible with Trilinos
    in Debian would be 4.1.0 (https://salsa.debian.org/science-team/trilinos/-/blob/master/packages/tpetra/CMakeLists.txt?ref_type=heads#L27).
    In the latest Trilinos version Kokkos would requires the latest release
    4.6.0.

    Searching a bit in the Trilinos documentation I found -D
    TPL_ENABLE_KOKKOS=ON as a CMake configuration flag to build with an
    external Kokkos package.
    I am not yet sure how to point Trilinos to the external Kokkos install.
    Usually Kokkos_ROOT or Kokkos_DIR should be set in the cmake configuration.
    If Kokkos can be found in the default paths maybe cmake is capable to
    find the install without specifying the path.

    This might solve the issue.

    Best regards,
    Nils

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)