Thanks for the feedback on the blog post, I'll update it.
Regarding the last error: there might be a feature you need to patch out or some benchmarks
On Mon, 4 Sept 2023, 14:36 Axel Kittenberger, <
axel.kittenberger@univie.ac.at> wrote:
Hello thanks for the heads up.
In the meantime you can try to get the other missing dependencies for authenticator into debian. scrypt, search-provider and aes-gcm seem
like good starting points. I can recommend reading https://blog.hackeriet.no/packaging-a-rust-project-for-debian/ to get started. Feel free to ask on the #debian-rust IRC channel on the OFTC network if you run into any questions.
This is getting more out of hand than I expected :)
Anyway, I tried to go with scrypt: Issues with said instructions I
encounter:
1) CHROOT
It tells me to set CHROOT=unstable-amd64-sbuild but later at 9) it
builds debcargo-unstable-amd64-sbuild I guess it should be rather that?
4) ./update.sh crate-name
yields
./update.sh: abort: debcargo not found, run `cargo install debcargo` or
set DEBCARGO to point to it
fixable by putting in exactly that command (or should rather a matching debian package be installed?)
13) Push your branch to your fork
Well if I follow the instructions there is no fork. (I registered for
salsa and awaiting approval to create a fork). While I can redirect git remotes later on, would be more practical to clone the fork right away.
10) ./build.sh scrypt
Gets me this error:
E: The value 'unstable' is invalid for APT::Default-Release as such a
release is not available in the sources
./build.sh: abort: couldn't generate dpkg-dummy/status, is Debian
unstable in your APT sources?
Wait I have to put unstable in /etc/apt/sources.list of the building
system? (Its a trixie VM I thought that would be enough)
10) ./build.sh salsa20 (a dependency of scrypt)
Gets me an error of quilt not been installed (yes fixable with apt
install quilt)
Fixing that I get:
error[E0554]: `#![feature]` may not be used on the stable release channel
--> benches/mod.rs:1:12
|
1 | #![feature(test)]
| ^^^^
So this is from upstream. Honestly I don't understand enough of Rust to
say if the build did something wrong, or upstream ought to fix this. (I
wrote a Rust script as git extension a while ago, but that's about it)
Kind regards, Axel
<div dir="auto">Thanks for the feedback on the blog post, I'll update it.<div dir="auto"><br></div><div dir="auto">Regarding the last error: there might be a feature you need to patch out or some benchmarks</div></div><br><div class="gmail_quote"><
div dir="ltr" class="gmail_attr">On Mon, 4 Sept 2023, 14:36 Axel Kittenberger, <<a href="mailto:
axel.kittenberger@univie.ac.at">
axel.kittenberger@univie.ac.at</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:
1px #ccc solid;padding-left:1ex">Hello thanks for the heads up.<br>
> In the meantime you can try to get the other missing dependencies for <br> > authenticator into debian. scrypt, search-provider and aes-gcm seem <br> > like good starting points. I can recommend reading <br>
> <a href="
https://blog.hackeriet.no/packaging-a-rust-project-for-debian/" rel="noreferrer noreferrer" target="_blank">
https://blog.hackeriet.no/packaging-a-rust-project-for-debian/</a> to get <br>
> started. Feel free to ask on the #debian-rust IRC channel on the OFTC <br> > network if you run into any questions.<br>
This is getting more out of hand than I expected :)<br>
Anyway, I tried to go with scrypt: Issues with said instructions I <br> encounter:<br>
1) CHROOT<br>
It tells me to set CHROOT=unstable-amd64-sbuild but later at 9) it <br>
builds debcargo-unstable-amd64-sbuild I guess it should be rather that?<br>
4) ./update.sh crate-name<br>
yields<br>
./update.sh: abort: debcargo not found, run `cargo install debcargo` or <br> set DEBCARGO to point to it<br>
fixable by putting in exactly that command (or should rather a matching <br> debian package be installed?)<br>
13) Push your branch to your fork<br>
Well if I follow the instructions there is no fork. (I registered for <br> salsa and awaiting approval to create a fork). While I can redirect git <br> remotes later on, would be more practical to clone the fork right away.<br>
10) ./build.sh scrypt<br>
Gets me this error:<br>
E: The value 'unstable' is invalid for APT::Default-Release as such a <br>
release is not available in the sources<br>
./build.sh: abort: couldn't generate dpkg-dummy/status, is Debian <br> unstable in your APT sources?<br>
Wait I have to put unstable in /etc/apt/sources.list of the building <br> system? (Its a trixie VM I thought that would be enough)<br>
10) ./build.sh salsa20 (a dependency of scrypt)<br>
Gets me an error of quilt not been installed (yes fixable with apt <br>
install quilt)<br>
Fixing that I get:<br>
error[E0554]: `#![feature]` may not be used on the stable release channel<br> --> benches/mod.rs:1:12<br>
|<br>
1 | #![feature(test)]<br>
| ^^^^<br>
So this is from upstream. Honestly I don't understand enough of Rust to <br>
say if the build did something wrong, or upstream ought to fix this. (I <br> wrote a Rust script as git extension a while ago, but that's about it)<br>
Kind regards, Axel<br>
</blockquote></div>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)