Skip to content

Docs: oooenv cmd-link -a raises FileNotFoundError: Uno Source Dir not found. on Fedora 43 #711

@langemar

Description

@langemar

Hi,

I've just tried to follow the the Guide to manually setup a venv on Linux (Fedora 43).
Based on the Steps provided the oooenv cmd-link -a command should be run within the active venv. By doing so the following stacktrace is printed:

$ oooenv cmd-link -a
Traceback (most recent call last):
  File "/home/...venv.../bin/oooenv", line 6, in <module>
    sys.exit(main())
             ~~~~^^
  File "/home/...venv.../lib64/python3.14/site-packages/oooenv/cli/main.py", line 268, in main
    _args_process_cmd(a_parser=parser, args=args)
    ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/...venv.../lib64/python3.14/site-packages/oooenv/cli/main.py", line 29, in _args_process_cmd
    _args_action_cmd_link(a_parser=a_parser, args=args)
    ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/...venv.../lib64/python3.14/site-packages/oooenv/cli/main.py", line 77, in _args_action_cmd_link
    uno_lnk.add_links(args.src_dir)
    ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
  File "/home/...venv.../lib64/python3.14/site-packages/oooenv/cmds/uno_lnk.py", line 34, in add_links
    p_uno_dir = uno_paths.get_uno_path()
  File "/home/...venv.../lib64/python3.14/site-packages/oooenv/utils/uno_paths.py", line 193, in get_uno_path
    raise FileNotFoundError("Uno Source Dir not found.")
FileNotFoundError: Uno Source Dir not found.

In order to solve this error it was necessary to set the environment variable OOOENV_LO_UNO_PATH to the path of to system-wide site-packages folder. For my setup the following command worked:

OOOENV_LO_UNO_PATH=/usr/lib64/python3.14/site-packages/ oooenv cmd-link -a
Created system link: /usr/lib64/python3.14/site-packages/uno.py -> /home/...venv.../lib/python3.14/site-packages/uno.py
Created system link: /usr/lib64/python3.14/site-packages/unohelper.py -> /home/...venv.../lib/python3.14/site-packages/unohelper.py

It would be helpful if a hint would be added to the documentation as oooenv does not search within the system-wide python installation(s).

Best regards,
Markus

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions