[lotheac]

depending on the libc crate version, target architecture and target libc, timespec may contain private padding fields. on such targets, rust 1.99.0 with libc 0.2.187 hits the following error:

error: cannot construct `timespec` with struct literal syntax due to private fields
   --> /home/buildozer/aports/community/kubie/tmp/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/interprocess-2.4.0/src/os/unix/c_wrappers.rs:435:8
    |
435 |     Ok(libc::timespec { tv_sec, tv_nsec: d.subsec_nanos() as _ })
    |        ^^^^^^^^^^^^^^
    |
    = note: ...and other private field `__pad0` that was not provided
help: consider using the `Default` trait
    |
435 -     Ok(libc::timespec { tv_sec, tv_nsec: d.subsec_nanos() as _ })
435 +     Ok(<libc::timespec as std::default::Default>::default())
    |

so, use timespec::default() to avoid the error. Default was implemented for timespec in libc 0.2.183, so bump the dependency.