Uploaded image for project: 'Funtoo Linux'
  1. Funtoo Linux
  2. FL-10687

[media-kit] media-sound/spotify-tui-0.25.0 Rust 1.64.0 and 1.65.0 broken due to upstream

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Severe (Ebuild) Severe (Ebuild)
    • None
    • None
    • emerge -av1 media-sound/spotify-tui-0.25.0

      During the recent upgrade of Rust 1.65.0 I re-discovered another broken Rust crate due to upstream breakage, media-sound/spotify-tui-0.25.0 is failing with this Rust compilation error:

       

      error[E0512]: cannot transmute between types of different sizes, or dependently-sized types
         --> /var/tmp/portage/media-sound/spotify-tui-0.25.0/work/cargo_home/gentoo/socket2-0.3.12/src/sockaddr.rs:176:9
          |
      176 |         mem::transmute::<SocketAddrV4, sockaddr_in>(v4);
          |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
          |
          = note: source type: `SocketAddrV4` (48 bits)
          = note: target type: `sockaddr_in` (128 bits)
      warning: build failed, waiting for other jobs to finish...
       * ERROR: media-sound/spotify-tui-0.25.0::media-kit failed (compile phase):
       *   cargo build failed
       *
       * Call stack:
       *     ebuild.sh, line   93:  Called src_compile
       *   environment, line 1327:  Called cargo_src_compile
       *   environment, line  470:  Called die
       * The specific snippet of code:
       *       "${@}" || die "cargo build failed"
      

      This is already being tracked upstream in this GitHub Issue here: https://github.com/Rigellute/spotify-tui/issues/1025

      There is also a PR actually already available with the fix, it just needs to be merge and a new version of the upstream Rust crate needs to be released: https://github.com/Rigellute/spotify-tui/pull/990

      I have commented on the upstream GitHub Issue and asked the upstream maintainer to me

       

            siris siris
            siris siris
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: