We are preparing an update of rust-nix to version 0.27, the new version has
been uploaded to experlmental.

The new version of nix has a couple of notable changes.

1. The introduction of "io safety". You can read a full description of
    io safety at https://rust-lang.github.io/rfcs/3128-io-safety.html
    but the gist is to treat raw file descriptors in a similar manner to
    pointers and references, with new types and traits.
2. No features are enabled by default, you must enable the features you
    require.

I was fairly easily able to adapt hippotat to the new version of
rust-nix, however unfortunately I was not able to easilly make the
code build with both the old and the new versions.

While I was working on this issue I ran into a couple of other
issues, so I dealt with those too.

1. The package's clean target was not functional, I added manual
    cleanup.
2. The packages cargo dependency on lazy-regex was at 2.2, but
    Debian now has 3.x. I relaxed the dependency.

A debdiff is attatched, if I get no response I will likely NMU this when the
new rust-nix is uploaded to unstable.

Peter Green writes ("Bug#1064487: hippotat - upcoming rust-nix update."):

Thank you for this work.

Ah well.  I do wish upstream would get on with `#[cfg(accessible)]`.

Thanks!

I will incorporate these changes, and that will be a new upstream
version.

Is there any reason I shouldn't upload this to unstable myself right
away?  It won't migrate immediately, obviously but I think that's OK.

One final thing.  Can you formally confirm that you're happy for me to
commit and distribute these changes - specifically, can you confirm
the statements in the Developer Certificate of Origin ?  (attached)

In a situtation like this where a contributor has provided a
portmanteau patch, I would normally split it myself and put the author
in the commits' "author" metadata and myself in the "committer", but I
could leave your name out of the git history if you prefer.

For reference, on you would be welcome to contribute via gitlab MR
instead of BTS and debdiff, but I understand why that isn't likely to
be so convenient when trying to update nix in Debian.

Regards,
Ian.

Peter Green writes ("Bug#1064487: hippotat - upcoming rust-nix update."):

I managed to make a thing that works with both.  I also relaxed quite
a few dependencies, off my own bat.  I'm going to release/upload it
shortly, which should unblock the nix update in sid.

There's a hunk or two of your debdiff that I would like to apply, but
I would still like that DCO signoff.  I'm cloning this bug for that.

Thanks,
Ian.