ruro
> > then you have already lost at that point > > This will eventually hit you if you are trying to use old versions of packages on newer versions...
> This is a proposal for a personal version of pip-compile, then? It's clearly not. If you don't like my proposal, and you can't have a polite discussion, put a...
@chichivica, you forgot to remove the stub `.so` symlinks after building in the Dockerfile. I was able to build the current nvtop version with the following Dockerfile: ```Dockerfile FROM nvidia/cuda...
@lminer you don't need the real `libnvidia-ml.so` file, you need the stubs. AFAIK, attempting to use the actual Nvidia shared objects during `docker build` will always fail, because the shared...
@lminer As I already mentioned, `nvidia/cuda:*-base-*` images don't have stubs. You'll have to build with `nvidia/cuda:*-devel-*` or manually add stubs to the base image.
Rebased on top of current master
Inotify is only useful, if you want to monitor the status of files as they change. I don't think, that this is a common use case for repose. If my...
I have 2 problems with manually using `lfs.storage` on a per-repository basis: - You have to set it up manually for each repo instead of configuring it once in a...
> No, my point is that those are now separate repositories and shouldn't share storage. Otherwise, someone can copy the repository to another place on the disk and then run...
Hi, sorry to bother you, but is this still getting worked on? If my understanding is correct, the downstream qmk/lufa#8 PR is blocked in favour of waiting for this PR,...