- User Since
- Jul 14 2017, 10:42 AM (143 w, 7 h)
Jan 24 2020
If it helps to know, my Navi setup was tested with GPT, UEFI, 144 Hz monitor (although I set it to run at 120 Hz), CSM disabled.
Jan 23 2020
Booted all the ISOs successfully on my Ryzen 5 3600 and RX 5700 setup. I didn't test installation with Gnome and Mate. Everything seems to run fine in the live environment, not much to report compared to Budgie.
Jan 22 2020
I just booted the ISO on the computer at work (Intel Coffeelake and RTX 2080 Ti). It boots without issue both when using integrated graphics and the dedicated GPU with Nouveau. I didn't need to use nomodeset.
Jan 21 2020
Ran first tests on a computer with a Ryzen 5 3600 and RX 5700.
Jan 9 2020
Neat. Congrats! So is it testing time? If the Navi tests are needed, I can do them this evening.
Dec 13 2019
This status update is very appreciated, thanks. By the way, I'm polomi on Flarum, I'm not using the same name here so I thought that I'd clarify. For Navi support testing, I'll be happy to provide any required assistance when the time comes. Is there a list of things that should be tested? Or just run of the mill check if the installer works, and that graphical programs such as games run properly?
Aug 31 2019
Aug 24 2019
Jan 12 2019
Alright just installed both godot and godot-mono, and everything seems to be in order. I was able to export my projects in both cases. EDIT: And the appropriate templates were used should I add.
Jan 10 2019
I'll be able to try it over the weekend if the need is still there by then!
Jan 8 2019
I don't think Godot considers this as a "feature" so to speak. So technically you are right. However I don't think that anything will change with 3.1, given that they will still offer a "Classical build". There would be no reason to keep maintaining a classical build at all if the Mono build could export games that don't require Mono.
Jan 6 2019
Nov 8 2018
I moved to a new place again. And on this wifi, the issue is back!
Oct 27 2018
The public iso linked in one of the recent blog posts.
It was not. Installing it fixed it. I suspected that it was a dep, but I couldn't find it by name. Thank you.
Oct 23 2018
Unfortunately for debugging, I don't experience this issue anymore. I recently moved to another place where I connect to a new network, and it is pretty much instant at boot. Could be a mere correlation, but we can also make the hypothesis that the issue happens on some networks and not others (while it didn't happen at all with Budgie on any networks).
Aug 31 2018
May 9 2018
Mar 16 2018
I am currently on a tight schedule (finishing my PhD) and I will only be available from mid-april to work on this again. If someone wants to take over in the meantime feel free, otherwise I'll only get back to it after I'm done with the PhD.
Mar 12 2018
Yes it seems to work now. Thanks!
Feb 21 2018
JupyterLab just released, but it's not 1.0 yet so I don't think that it satisfies Solus inclusion policy. Version 1.0 is scheduled for 2018 though and it will replace Jupyter Notebook. Still seems to use Notebook as a dep though.
Feb 17 2018
Update to version 1.5.0.
Feb 15 2018
I have the same issue. The workaround is to create ~/.fonts.conf containing
<fontconfig> <match target="font"> <edit name="rgba" mode="assign"> <const>none</const> </edit> </match> </fontconfig>
Feb 13 2018
If/when cuda gets included in Solus, it can then be included in Tensorflow too. In the meantime I don't see any other way, it's CPU only or just wait for cuda. The only downside to include it with CPU only is that I'd expect uninformed users to be tempted to report issues about it.
Feb 4 2018
Remove unnecessary builddeps that are only rundeps. The comment I refer to in
the previous revision actually is for rundeps, so all was fine already.
Remove unnecessary builddeps that are only rundeps.
Thanks for the useful explanation, @EP01 !
Remove unnecessary builddeps that are only rundeps.
The package.yml has all the officially required dependencies. However some of them pull each other, if you want to trim it to the minimum list of dependencies, the commented ones below can be removed.
builddeps : - pkgconfig(python3) - git - nodejs-devel # - python-ipykernel # - python-ipython_genutils # - python-jinja # - python-jupyter_client # - python-jupyter_core - python-nbconvert # - python-nbformat - python-send2trash - python-setuptools - python-terminado # - python-tornado # - python-traitlets rundeps : # - python-ipykernel # - python-ipython_genutils # - python-jinja # - python-jupyter_client # - python-jupyter_core - python-nbconvert # - python-nbformat - python-send2trash - python-terminado # - python-tornado # - python-traitlets
I included them all because the jupyter packages already in Solus do the same. Let me know if it is the right approach.
Please note that I used the tarball from the Python Package Index, not from GitHub. The releases at GitHub don't have a setup.py file, but rather a project.toml file, which I don't know how to handle with the available Python macros.
I am able to run notebooks with Python 2 and Python 3 with the commands jupyter notebook and jupyter notebook3 respectively. The issue is that I can not change kernels between Python 2 and Python 3 at runtime, through the widget in the notebook. It shows no errors and the widget indicates the change of kernel, but regardless it always keeps running the Python version corresponding to the command used to start the notebook.
Feb 3 2018
The Jupyter developers answered here.
For sure, pytest and mock are required for testing only.
I agree that it is actually not obvious. I am asking upstream: https://github.com/jupyter/jupyter_client/issues/350
I have an eopkg that I'm able to install locally. However if I run the notebook and select a Python 2 kernel, it still runs with Python 3.
Feb 2 2018
Thanks for trying. It looks far beyond my knowledge as well unfortunately or I would have helped.
Jan 31 2018
Added scipy, matplotlib and pandas as build deps.
It seems to work fine without, but I just noticed this comment in
setup.py: `Just make sure dependencies exist, I haven't rigorously
tested what the minimal versions that will work are`. So better to
take no risk I believe.
Jan 30 2018
Use fixes keyword
Initial inclusion of python-seaborn, for T5655
Jan 29 2018
Jan 11 2018
Dec 25 2017
Sep 23 2017
Yes, thanks. I installed it myself and it works fine with it!
Sep 21 2017
Sep 12 2017
The source link provided in the request is for Zotero version 4, but Zotero version 5 is released now. Unlike with version 4, there exist no standalone Firefox addon version anymore. Currently the only version of Zotero is the desktop version. Hence it became more important to include it in Solus.