Peter Green writes ("Bug#1064487: hippotat - upcoming rust-nix update."):
> We are preparing an update of rust-nix to version 0.27, the new version has
> been uploaded to experlmental.
Thank you for this work.
> 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.
Ah well. I do wish upstream would get on with `#[cfg(accessible)]`.
> 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.
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.
Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
