Open gerroon opened 5 years ago
Hi @gerroon,
I faced the same. It have been answered by @benhutchins in #16 :
It looks like you are building, but didn't pull down the submodules. Try running:
git submodule update --init
Thanks but not sure, I still have issues with the compose :(
}'
void X509_get0_signature(const ASN1_BIT_STRING psig,
^~~~~~~
build/temp.linux-x86_64-3.5/_openssl.c:62516:29: warning: passing argument 2 of 'X509_get0_signature' from incompatible pointer type [-Wincompatible-pointer-types]
{ X509_get0_signature(x0, x1, x2); }
^~
In file included from /usr/include/openssl/cms.h:16:0,
from build/temp.linux-x86_64-3.5/_openssl.c:545:
/usr/include/openssl/x509.h:552:6: note: expected 'const X509_ALGOR {aka const struct X509_algor_st }' but argument is of type 'X509_ALGOR {aka struct X509_algor_st }'
void X509_get0_signature(const ASN1_BIT_STRING *psig,
^~~~~~~
At top level:
build/temp.linux-x86_64-3.5/_openssl.c:3426:13: warning: '_ssl_thread_locking_function' defined but not used [-Wunused-function]
static void _ssl_thread_locking_function(int mode, int n, const char file,
^~~~~~~~
error: command 'gcc' failed with exit status 1
----------------------------------------
Command "/usr/local/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-install-vs2kqvkg/cryptography/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-record-oiw67hj1/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-install-vs2kqvkg/cryptography/
Yeah sorry, faced this one too. We're following the exactly same path ^^
This error comes from Taiga Back and seems to be versions incompatibility between openssl and cryptography (source: https://github.com/taigaio/taiga-back/issues/1003). Thanks to new requirements this issue had been fixed in Taiga Back so my quick fix was to update submodules with latest versions with #70.
Ideally, the process would only require you to run:
git submodule update --init --remote
However, based on some other issues I think updating Nginx and some other aspects of this project may be required. I'm going through issues and pull requests now, but you will likely need to pull the newer image. That was the solution for me to overcome this issue.
Now I get no more error (hoorray), but I face the taiga "an issue occurred" page (shame). Perhaps a configuration forgot. I'll look at it this later today. Hope you'll can bring a fresh look on this.
I encountered exact same issues when setting up taiga, thank you @BiBzz ...
For the issue mentioned at the end with the "an issue occured" page. If you are using https, make sure your docker-compose configuration, contains:
TAIGA_SSL: 'True' # To enable SSL, uncomment this line
TAIGA_SSL_BY_REVERSE_PROXY: 'True' # To enable SSL, handling by a reverse proxy, uncomment this
Also, make sure the values are "True" not lowercase "true" - that doesnt work.
Thanks @zgec for having pointing this!
I deleted TAIGA_SSL_BY_REVERSE_PROXY
by mistake when I merge docker-compose.yml
Hi
Trying to set this up on Debian Buster but I keep hitting errors, one of it is below.