rommeswi
rommeswi
I fixed the error by outsourcing the commands to a bash script. I think it was just a syntax problem in the .yml of the form: ``` name: bla type:...
I think that decision is a real pity. It is completely standard that pip install uv will complain about externally managed environments in most Linux distros. pipx is a user...
Still relevant!
I noticed that the behavior is in some sense even worse. Specifically, when clicking or touching "outside" the window, it will actually register as a click in that application. This...
On the Alpine image: ``` $ find / -name "libgs*" /usr/lib/libgssrpc.so.4 /usr/lib/libgssrpc.so.4.2 /usr/lib/libgssapi_krb5.so.2.2 /usr/lib/libgssapi_krb5.so.2 ``` On the slim image: ``` $ find / -name "libgs*" /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2.2 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 /usr/share/doc/libgssapi-krb5-2 /var/lib/dpkg/info/libgssapi-krb5-2:amd64.postinst /var/lib/dpkg/info/libgssapi-krb5-2:amd64.md5sums...
Now after proper installation on the slim image the following are installed: ``` /usr/lib/x86_64-linux-gnu/libgs.so.10 /usr/lib/x86_64-linux-gnu/libgs.so.10.00 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2.2 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 /usr/share/doc/libgs10-common /usr/share/doc/libgs10 /usr/share/doc/libgs-common /usr/share/doc/libgssapi-krb5-2 /var/lib/dpkg/info/libgs-common.md5sums /var/lib/dpkg/info/libgs10:amd64.symbols /var/lib/dpkg/info/libgs10:amd64.md5sums /var/lib/dpkg/info/libgs10:amd64.triggers /var/lib/dpkg/info/libgs-common.list /var/lib/dpkg/info/libgs10-common.list /var/lib/dpkg/info/libgs10-common.md5sums /var/lib/dpkg/info/libgs10:amd64.shlibs /var/lib/dpkg/info/libgs10:amd64.list...
For alpine: ``` $ find / -name "libgs*" /usr/lib/libgs.so.10 /usr/lib/libgs.so.10.04 /usr/lib/libgssrpc.so.4 /usr/lib/libgssrpc.so.4.2 /usr/lib/libgssapi_krb5.so.2.2 /usr/lib/libgssapi_krb5.so.2 ``` Here it is properly installed in /usr/lib but I still get an error "Warning: libgs...
Yes, it worked for me. Sorry for the late reply!
I guess the main request is to add a variable SHELL to the vso config with which you can decide which shell to use in vso. Secondary issue is that...