v1.5.0 fails to build on i686

[lsm5]

Compiling mozim v0.1.0
error[E0277]: the trait bound `i32: From<u32>` is not satisfied
   --> /builddir/build/BUILD/netavark-1.5.0/vendor/mozim/src/socket.rs:289:17
    |
289 |         tv_sec: timeout.into(),
    |                 ^^^^^^^ ---- required by a bound introduced by this call
    |                 |
    |                 the trait `From<u32>` is not implemented for `i32`
    |
    = help: the following other types implement trait `From<T>`:
              <i32 as From<NonZeroI32>>
              <i32 as From<bool>>
              <i32 as From<i16>>
              <i32 as From<i8>>
              <i32 as From<nix::time::ClockId>>
              <i32 as From<nix::unistd::Pid>>
              <i32 as From<socket2::Domain>>
              <i32 as From<socket2::Protocol>>
            and 5 others
    = note: required for `u32` to implement `Into<i32>`
For more information about this error, try `rustc --explain E0277`.
error: could not compile `mozim` due to previous error
warning: build failed, waiting for other jobs to finish...
make: *** [Makefile:50: build] Error 101
error: Bad exit status from /var/tmp/rpm-tmp.sLYjfo (%build)
RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.sLYjfo (%build)
Child return code was: 1

Looks like an issue in a dependency crate, but that's blocking i686 rpm build.

[Luap99]

Yes this is caused by the mozim crate which is imported by the dhcp proxy.

[Luap99]

@baude PTAL

[baude]

where are we building i686?

[dacioromero]

I cross compile NixOS for my armv7l SBC and I'm having the exact same error after NixOS/nixpkgs#214293 was merged into nixos-unstable.

[lsm5]

where are we building i686?

it's still one of the main arches on Fedora. Let me know if you wanna exclusivearch it, but then we'll likely need to do the same for podman, buildah etc.

[Luap99]

I think exclusive arch for fedora is fine, https://fedoramagazine.org/in-fedora-31-32-bit-i686-is-86ed/
There is no i686 kernel so I do not see why anyone would want to run i686 netavark on fedora.

As for actually fixing this needs to be done in the mentioned crate, the only thing we could do in netavark is to revert the dhcp changes which is not something I want to do.

[lsm5]

I'll probably need to check with fedora people but I think exclusivearch-ing all of podman family should be doable.

[lsm5]

F38 has now been branched. I have disabled i686 and I realized it also fails on armhfp like it did for @dacioromero so I will not update our packages for f36 anymore unless people demand or there are CVEs.

@dacioromero no idea about nixos, but looks like fedora is giving up armhfp support altogether once Fedora 36 goes EOL requiring users to switch to something else come May/June. I can't speak for everyone, but looks like there won't be a ton of time spent on fixing 32-bit issues going forward.

I'm good to close this..

[Luap99]

I reported it upstream (nispor/mozim#11) so I close this one here.
Once fixed we will update the dep here.

[cathay4t]

Please use mozim 0.2.1 which contains the fix.