Search Criteria
Package Details: open-webui-no-venv 0.7.2-2
Package Actions
| Git Clone URL: | https://aur.archlinux.org/open-webui-no-venv.git (read-only, click to copy) |
|---|---|
| Package Base: | open-webui-no-venv |
| Description: | Web UI and OpenAI API for various LLM runners, including Ollama, built without creating virtualenv |
| Upstream URL: | https://github.com/open-webui/open-webui |
| Licenses: | BSD-3-Clause |
| Conflicts: | open-webui, open-webui-git |
| Provides: | open-webui |
| Submitter: | mistersmee |
| Maintainer: | mistersmee |
| Last Packager: | mistersmee |
| Votes: | 8 |
| Popularity: | 0.47 |
| First Submitted: | 2025-01-05 15:58 (UTC) |
| Last Updated: | 2026-01-11 15:34 (UTC) |
Dependencies (109)
- python
- python-accelerateAUR
- python-aiocacheAUR
- python-aiofiles
- python-aiohttp
- python-alembic
- python-anyio
- python-asgiref
- python-authlib
- python-azure-coreAUR
- python-azure-identityAUR
- python-azure-search-documentsAUR
- python-azure-storage-blobAUR
- python-bcrypt
- python-beautifulsoup4
- python-black (python-black-gitAUR)
- python-boto3 (python-boto3-gitAUR)
- python-botocore (python-botocore-gitAUR)
- python-certifi
- python-chromadbAUR
- Show 89 more dependencies...
Required by (1)
- open-webui-dinit (requires open-webui)
Latest Comments
1 2 3 Next › Last »
sashank commented on 2026-01-14 06:02 (UTC)
P.S. I reported the issue and linked to the upstream bug fix on gitlab with the package maintainers.
sashank commented on 2026-01-13 21:08 (UTC) (edited on 2026-01-13 21:12 (UTC) by sashank)
Does anybody else have python-tensorflow installed and getting the following error:
ValueError: The field annotations for StructuredTensor are invalid. Field FieldName is missing a type annotation.Apparently the bug was fixed in November, but it has not been released yet https://github.com/tensorflow/tensorflow/pull/104620
The current version is from back in August 2025.
Anyways, thank you evorster and MarekZ for the hints/help, I actually stepped away from all this for a bit until now, so I think the bugs were fixed in that time, but I appreciate the help.
evorster commented on 2025-11-30 10:06 (UTC) (edited on 2025-11-30 10:09 (UTC) by evorster)
I got this running on my system without downgrading.
Ever helpful ChatGPT summarizes the fix like this:
Open WebUI 0.6.40 currently fails to start on Arch due to upstream LangChain 1.x module restructuring. The AUR package depends on the newer split python-langchain-* packages, but the code still imports old monolithic LangChain paths such as:
These modules no longer exist in LangChain ≥1.0, causing:
Temporary workaround (working fix)
Patch the following imports to support both old and new layouts:
In /usr/lib/python3.13/site-packages/open_webui/routers/retrieval.py:
In /usr/lib/python3.13/site-packages/open_webui/retrieval/utils.py:
This allows Open WebUI to run normally with the Arch python-langchain-* packages.
Other notes
The warning about huggingface-hub>=0.34.0,<1.0 is non-fatal and does not stop the service.
MarekCZ commented on 2025-11-25 10:11 (UTC)
Hi sashank, I hit the same issue as you did. The problem came with python-langchain 1.0, since the internal structure of the package(s) changed. I downgraded packages python-langchain, python-langchain-core, python-langchain-text-splitters and python-langchain-community to the last available version before 1.0 and everything works as expected. Hope it helps, at least for now. Cheers.
sashank commented on 2025-10-20 19:09 (UTC)
Well, whatever they changed just broke everything, lol. Can't figure out if its a database error (which I get when I run
/bin/open-webui serve --port 8080or if it's this:ModuleNotFoundError: No module named 'langchain.text_splitter'which what I get when I check the systemd logs. But I have to focus on other stuff. I just got a new AMD APU machine for this sort of stuff, and I have to work on a couple of other things before I get distracted by this again, haha. Anyways, thank you again for keeping up on all this. This has been such a great linux learning experience beyond basic shell scripts and whatnot.sashank commented on 2025-10-17 07:53 (UTC) (edited on 2025-10-17 07:54 (UTC) by sashank)
P.P.S I checked your dependency_discover.py script, and I trust it more than namecap, haha.
Edit: I just saw that you replied. So yes, I agree with you.
mistersmee commented on 2025-10-17 07:49 (UTC)
@sashank, the potentially unnecessary packages that namcap lists out isn't always accurate 100% of the time, it doesn't consider some things, and upstream doesn't list all the packages it depends upon most probably because they're transitive dependencies or something. To see exactly what open-webui depends upon, you can go through the necessary_dependencies.txt file I've included. I've always kept track of the dependencies using that. python-pytest and python-git-python are only used in the unit tests, which we don't use, because I'm pretty sure upstream doesn't enable them, or if they are enabled, they don't enable them properly, in pyproject.toml.
As for python 3.13, open-webui has been running fine on it since basically python 3.13 came out, there was a little bit of time where some of the dependencies hadn't caught up, but all of them have now. I don't know why upstream refuses to move to 3.13, the main python version on Arch has been 3.13 since a while, and 3.14 also came out recently. 3.12 isn't EOL, but still.
And yeah, not sure about what exactly caused the problems, but I'm satisfied with the fact that they're fixed.
sashank commented on 2025-10-17 07:17 (UTC)
But yeah, looking at everything, I just don't see how any of the difference would have caused the problems that they did. Just sharing everything for both your curiosity and learning and mine.
Also, in regards to potentially unnecesary packages, they list python-accelerate, python-importlib-metadata, python-opentelemetry-exporter-otlp-proto-grpc, python-opentelemetry-exporter-otlp-proto-http, python-python-multipart, python-urllib3 as unneeded dependencies...
The only one I see in pyproject.toml is python-multipart and accelerate. I don't see importlib-metadata or urllib3, but we do have python-requests, which I guess depends on urllib3, and I'll trust something in there requires importlib_metadata. So I'm guessing they're saying that other packages we require probably already require those.
Not sure what's going on with the python-pytest and python-git-python errors.
sashank commented on 2025-10-17 06:39 (UTC)
Here's the second command (new package):
sashank commented on 2025-10-17 06:38 (UTC)
So here's the first command,
1 2 3 Next › Last »