Hi guys,
Anybody has any solution? For now I face with this error in package
installation:
```
...
Compiling etebase-python v0.30.0
(/tmp/guix-build-python-etebase-py-0.30.0.drv-0/etebase-0.30.0)
error: unterminated double quote string
--> src/lib.rs:63:44
|
63 |
Hi Efraim,
> I'd add in a substitution here for openssl like this (untested):
>;; Don't depend on vendored sources
>(("0.10.30.*") "0.10.30\" }\n")
>
Thanks, I added it and this step passed and now I don't get the previous error
in building.
Now I faced with
On Wed, Oct 21, 2020 at 05:27:16PM +0330, Hamzeh Nasajpour wrote:
> I'm so sorry I had a mistake in the previous package definition, I was in
> testing. Please remove these lines in the previous definition:
> ```
> (substitute* "Cargo.toml"
> (("0.10.30\"" all)
Hello John,
Thanks for your following up.
I put the `openssl` in `inputs` too and the problem wasn't resolved. I also I
packaged the `openssl-src` and repackage the `openssl-sys` and this is didn't
resolved the problem too.
The point is with the following package definitions the
Hi Hamzeh,
First, make sure openssl is a standard input instead of a native one. I am not
sure that will fix the problem here though. Most likely we will need an
openssl-src package that uses the system source.
Good luck,
John
I'm so sorry I had a mistake in the previous package definition, I was in
testing. Please remove these lines in the previous definition:
```
(substitute* "Cargo.toml"
(("0.10.30\"" all) "0.10.30\"}# "))
```
It means that my package definition is:
```
(define-public
This is my package definition till now. The repository of the package is here:
https://github.com/etesync/etebase-py/
Also I should to say I package these (since they aren't available in the
upstream packages):
* openssl@0.10.30
* cpython@0.3
* etebase-rs
* flapigen-0.6
I didn't attach them
Hello Hamzeh,
It would be preferable if you can avoid using the vendored openssl. Did you add
openssl as an input to the package?
Can you share what you have so far please?
- John
P.s. please avoid bottom quoting on the list
Hello John,
Thanks for your quick reply.
But as you see in `Cargo.toml`, this feature mentioned and I think it's needed.
In the other side setting the `OPENSSL_DIR` didn't resolve my issue.
Do you have any other suggestion?
Can I repackage `rust-openssl-sys-0.9` and remove this line in the
Hello Hamzeh,
Take a look at gnu/packages/crates-io.scm for other examples of rust-openssl.
We try to avoid vendored sources. Recent versions of rust-openssl-sys also
complicate this by requiring particular versions of openssl.While it’s nice
that they are explicit about the
Hi,
I face with an issue in one library that I'm packaging by myself. This library
has one dependency to `rust-openssl@0.10.30`, I updated the `rust-openssl` to
`0.10.30` and now I get this error in the package building:
```
...
patch-cargo-checksums: generate-checksums for
11 matches
Mail list logo
