Arch Linux User Repository

As discussed, smassh has been turned into a source package. The pyinstaller binary can be installed with the smassh-bin package. If you want the binary released on GitHub, you should install smassh-bin instead. But normally, these two make no difference.

@kraanzu Nice, confirm all fixed now.

Hi again @jaxvanyang,

Can you recheck? I pushed a fix!

Found the issue. I am an idiot lol

Hi @jaxvanyang, yes I can replicate the behaviour as well. Looking into it

Current version (3.1.5-1) has to be built in a clean root on my machine, or else it'll lack some files. Crash log:

$ smassh                                                          13:12:47
Traceback (most recent call last):
  File "/usr/bin/smassh", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/lib/python3.12/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/click/core.py", line 1666, in invoke
    rv = super().invoke(ctx)
         ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/click/decorators.py", line 33, in new_func
    return f(get_current_context(), *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/smassh/__main__.py", line 22, in main
    from smassh.ui.tui import Smassh
  File "/usr/lib/python3.12/site-packages/smassh/ui/__init__.py", line 1, in <module>
    from .tui import Smassh
  File "/usr/lib/python3.12/site-packages/smassh/ui/tui.py", line 8, in <module>
    from smassh.ui.screens import *  # noqa
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/smassh/ui/screens/__init__.py", line 5, in <module>
    from .result import ResultScreen
  File "/usr/lib/python3.12/site-packages/smassh/ui/screens/result.py", line 7, in <module>
    from smassh.ui.widgets.result import ValueContainer, Value, ResultStrip
ModuleNotFoundError: No module named 'smassh.ui.widgets.result'

It's really weird, don't know how to inspect it. Maybe it's just a problem of my environment, please let me know if you have the same problem.

Yes I updated the readme on github as well!

Thanks :)

As discussed, smassh has been turned into a source package. The pyinstaller binary can be installed with the smassh-bin package. If you want the binary released on GitHub, you should install smassh-bin instead. But normally, these two make no difference.

@jaxvanyang

I updated the code and it works!!! Thanks a lot <3

@jaxvanyang

Oh oops, my bad. It was not the themes Yea, we can move it no worries!

I should probably use the cache folder (~/.cache/smassh/style.css). What do you think?

@kraanzu

No need to rush, I also get busy sometimes. The option you mention is probably --add-data for pyinstaller. There is no need to do that for the source package, because it includes all source file like PyPI package. The problem is that when you install it as a system package, all files are owned by root.

Problem code is in css_generator.py, only the write code crash, read is fine. If this file can be moved to the config directory, I can try to fix it.