-
Notifications
You must be signed in to change notification settings - Fork 15
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
New version available. #132
Comments
If you check the PR page you will see that the bot already updated the manifest but owner of the repo haven't merged it yet. Idk why they don't use a Github Action for this. In my case I had to rebuild it myself locally. |
@bilelmoussaoui Please look into this, @Psycomentis06 would you be interested in maintaining? |
owner was in need of new maintainer: |
Nevermind, I see that there's 12.2.0 now. |
I think this issue can just be pinned and kept open perpetually, for use by both users and maintainers. If someone wants to say "Hey, there's a new version," they can just do so in this Issue instead of creating new ones. Same with if the maintainers ARE trying to update the package, they can post any problem here or link the PR here so that people don't need to ask, they can already see it's being worked on. Saves everyone's time. |
@mlawson27 is the current maintainer. I'm pinning this in any case to reduce duplicates. |
Finally logging back in after quite a while and see I've missed a few things. I don't really think I'm the right person to be the long-term maintainer (and I must have missed how/where I was designated the primary maintainer; that's probably on me for just not paying close enough attention). I just assumed I got contribute permissions since I was pushing a bunch of PRs and it was just easier to allow me to push them myself. A few months ago, I was using a really old PC with pretty low specs, and keeping the 21.08 runtime around just for WPS Office was a problem for me in terms of storage, so I really wanted to get up to the 23.08 runtime. I've since switched to a primarily Arm workflow now, and since WPS Office doesn't have an Arm build (unless I'm mistaken), I don't really use WPS Office anymore. Not sure what the right process is for finding a new maintainer, but if I need to do something, somebody please let me know. I don't mind merging PRs, etc. in the interim (and I'll pay better attention), but somebody who actually uses WPS Office on a regular basis is probably better suited to be the primary maintainer here. |
Hello guys, I clone this repo and build it myself, but only to get: Error: Extra data missing in detached metadata
error: Failed to install bundle com.wps.Office: Extra data missing in detached metadata The commands I used are: flatpak-builder --repo=wps_repo wps_build com.wps.Office.yml
flatpak build-bundle wps_repo wps.flatpak com.wps.Office
flatpak install wps.flatpak Anyone has ideas? Yours, |
WPS 12 is out, lets have an update! |
Where did you find it? I looked at the official site (https://www.wps.com/office/linux/ - tried looking at both deb and rpm filenames) and the changelog (https://www.wps.com/whatsnew/linux/), it's still in WPS 11?
|
|
A new version of wpc office has been released on the official website.
The text was updated successfully, but these errors were encountered: