-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Image on ghcr.io/unoconv/unoserver-docker
is outdated.
#58
Comments
You'll have to use the version (via docker or pypi) in both places for now. The github action pipeline broke after an update, I've spent hours on resolving it, but I haven't been successful. I don't have an unlimited amount of time to put into this project. Especially, not since I'm not using unoserver anymore myself. I see now that they have released a new major version, so it's worth having a look at it again. @regebro Would you have time to have a look at it? Or is there someone else that can take over? |
@jimisola I haven't got the foggiest idea of anything that is going on in this repository, and I have run out of time trying to understand it. If you don't have time to maintain it, we should mark it as unmaintained. |
Sorry for the delayed response due to sickness. The merge step in pipeline fails due to an issue with the quotation. I'm not sure (tried everything including manipulation with awk and sed) how to fix it other than a workaround that removes some information from the build. I've reported the issue to the github action and they're looking at it. So, when I'm not sick I'll revert to the workaround in order to make a release and then wait for a fix upstreams. |
Trying to revert back to a working workflow while awaiting docker/build-push-action#1200 |
The current image on
ghcr.io/unoconv/unoserver-docker
is outdated (version0.3.21
). The unoserver version used in the image is2.0.1
, while the latest unoserver version is2.2.2
. When I use unoconvert version2.2.2
for file conversion, the following error is reported:As mentioned in this link Issue 130, this error is due to the version mismatch between the two.
The text was updated successfully, but these errors were encountered: