- User Since
- Nov 28 2016, 3:58 AM (174 w, 18 h)
Feb 25 2020
Feb 22 2020
Feb 21 2020
Rebase on master and add a patch to fix github issue 1038.
Feb 19 2020
Remove unused patches
Feb 13 2020
Feb 2 2020
@DataDrake I am working on updating tensorflow to a newer version. It would be good it this patch can be landed before that.
@DataDrake Do you have some time to review this patch?
Jan 29 2020
@JoshStrobl Yes I can confirm that it still happens on 0.58.3.
@JoshStrobl Can you take a look at this request and see whether it's worth re-evaluating its inclusion in the repo?
Jan 27 2020
You can set the python version you want to use by setting things like PYTHON_EXECUTABLE, PYTHON_INCLUDE_DIR, and PYTHON_LIBRARY when building root: https://root.cern.ch/building-root. One tricky thing about root is that it comes with a lot of packages that might have been installed on the system. So ideally one wants to use the system version rather than the version comes with ROOT if possible.
Jan 22 2020
@JoshStrobl Could you provide your thoughts regarding our feedback? It is not really good for us to keep giving our perspectives while seeing no response from the core team.
Jan 8 2020
@Girtablulu libsplit only keeps the library file (lib*.so) from entering the devel subpackage, but it does nothing to the header files. I think you will need to use the patterns key to require the headers also go to the main package. You can look at the eigen3 package as a template.
Dec 19 2019
Dec 12 2019
Dec 11 2019
@DataDrake No push here. Just wondering when you plan to land this patch. Thanks.
Nov 29 2019
As mentioned in the summary, if this patch gets into the repo, we should deprecate nvidia-docker and nvidia-container-runtime.
Abandoning since I made a mistake. This is corrected and re-submitted in D7736.
Remove empty abi_used_libs
Nov 19 2019
Make the rm command applicable to all python 3 versions.
Nov 12 2019
Nov 6 2019
Oct 23 2019
@JoshStrobl Can you take a look at the patch again to see whether it is good now?
Oct 22 2019
This issue has happened again since the update of libvte to 0.58.0. Kindly ping @JoshStrobl to look at it since he is the maintainer of libvte.
Oct 18 2019
Let ypkg decide the component for devel subpackage
-devel subpackage belongs to programming.devel component
@JoshStrobl Can you review this patch again?
Oct 11 2019
Rebase against master branch
Oct 9 2019
@joebonrichie The build finishes successfully for me against llvm 9 with solbuild after removing the following line from FindLLVM.cmake:
Oct 8 2019
@joebonrichie First thanks for the effort on updating llvm as well as other toolchains for us. I really appreciate your work.
@DonHugo I updated the documentation according to your suggestion. Can you take a look and see whether that is better?
Oct 7 2019
@DonHugo I created a pull request to add the documentation for enabling fzf command-line autocompletion and key-bindings to the Solus help center here: https://github.com/getsolus/help-center-docs/pull/230. Can you try to see if it works correctly for you?
Oct 4 2019
Update the test plan. Tested against latest network manager now.
Oct 3 2019
Rebase on master branch
Oct 1 2019
python3 is enough for my use case.
Sep 12 2019
Sep 10 2019
The keybindings are not enabled by default. If you want to enable it, you can add the source statement in your shell init script. For example, I have this in .bashrc:
Aug 28 2019
Aug 23 2019
Add MAINTAINERS.md file
Add MAINTAINERS.md file
Aug 20 2019
I can confirm the problem exists
Aug 13 2019
pytorch-devel belongs to programming.library now
Aug 11 2019
Max memory usage I saw was 3.5GB which is actually pretty crazy.
I actually can't build it due to ld.bfd sucking all my memory, and, can't build it with clang + lld due to --copy-needed-dt-entries being inherited.
@joebonrichie Are you referring to pytorch here? That would be weird since D6912 built with opencv 4.1.1 successfully as it is right now. My machine has plenty of memory though. I will test it on another machine with 16 GB memory and see how it goes.
Add patch to build with opencv-4
Aug 10 2019
I found a solution to this problem after some research.
Aug 9 2019
Now that pytorch 1.2.0 is available, I will abandon this patch and submit another one for 1.2.0
Aug 7 2019
I am happy to maintain it.