| Git Clone URL: | https://aur.archlinux.org/zoom.git (read-only, click to copy) |
|---|---|
| Package Base: | zoom |
| Description: | Video Conferencing and Web Conferencing Service |
| Upstream URL: | https://zoom.us/ |
| Keywords: | call conference meeting video |
| Licenses: | LicenseRef-zoom |
| Submitter: | edh |
| Maintainer: | edh |
| Last Packager: | edh |
| Votes: | 670 |
| Popularity: | 6.68 |
| First Submitted: | 2015-08-15 13:18 (UTC) |
| Last Updated: | 2024-11-25 17:39 (UTC) |
I looked through some of the recent comments and didn't see anything about this.. after a recent update, Zoom is now adjusting the volume of my microphone down to near-zero each time I join a call. It is driving me absolutely crazy.
I am using zoom-firejail.. combined with recent updates, I'm thinking it may have introduced a bug?
Yes! Finally! I have been patiently waiting for a new release to free me from the current situation! :)
Zoom 5.8.0 has arrived - https://zoom.us/download#client_4meeting Appreciate, that available at Arch!
@alerque, why wouldn't that fix it? When this issue arose, the checksum could have just been updated (for the new binary), along with a pkgrel bump, and all of this drama would have been averted. Marking it version 5.7.6.a is less semantically correct because it implies an upstream version number change, which did not occur.
@bulletmark Bumping the pkgrel would not fix this, nor would it be semantically correct.
@edh Marking this as 5.7.6.a isn't a bad option actually. I don't think many who have already built this will care about doing so again, most are going to be using AUR helpers anyway that will just take care of it.
But the upstream binary package has changed, thus everybody should update! It is odd and undesirable when upstream packagers do this but it is not unprecedented and in cases where I have seen this before, the AUR maintainer just bumps the pkgrel without any of the ongoing confusion and dialog we have seen here.
The current version number is not the issue here! Zoom released a new binary package under the same seemingly unique URL thereby breaking this package. To correct for this I introduced an artificial version bump. During this step I did a mistake in updating the pkgver and appended an a instead of an .a. Thus, I did not force a rebuild but actually decreased the version number.
For the time being please update manually (e.g. by uninstalling and then re-installing zoom again). The seemingly lower version is actually the most recent version.
Note, while I could still "fix" this by appending the .a, doing so would force everybody who already manually upgrade to rebuild the package as well. In my opinion this bother people unnecessarily who already put in the effort.
@darose I think you're missing the fact that this is a two part problem. There is a general issue of the upstream releases updates without changing the build number and there is a current temporary issue in that this a business missed the necessary segment separator.
Your scheme would be a viable scheme, but it would not solve the problem that upstream keeps changing their package without changing versions. Neither the "5.7.6" version nor the "31753.0818" build data changed when the package was updated last. In other words following your scheme would still have required a .a version bump on the part of this PKGBUILD.
There are ways out of the current mishapp with a instead of the .a that it should have been, but those are temporary and introduce other problems down the road (switching to build numbers means we can't go back to chis schemed when they don't add them properly, and adding an epoch is ugly and confusing).
Just "downgrade" your package to 5.7.6a-1 and move on. The next time around I doubt @edh will make the same mistake.
@edh At your suggestion I went back and read old comments about the versioning. But I still don't understand what the issue is here.
I am currently running zoom 5.7.6 (31753.0818). Current build is 31792.0820. Would it not be possible to change the versioning scheme you're using to change the version number from 5.7.6 to 5.7.6.31753.0818? Then an update to the new build version of 5.7.6.31792.0820 would force an upgrade. Instead I see this:
warning: zoom: local (5.7.6-1) is newer than chaotic-aur (5.7.6a-1)
What am I missing here? Why would that not work?
Sorry for setting the "outdated" flag. I only now read all the discussion :( For reference in case someone stumbles upon this: Uninstalling zoom (5.7.6) and reinstalling zoom (to 5.7.6a) gives you the latest version.
Pinned Comments
erbrecht commented on 2024-11-19 13:06 (UTC)
@Rhinoceros - I finally got screen sharing to work under KDE with Wayland. Looks like I'm using the same versions as you:
I followed the Screen share section on the Zoom wiki page:
https://wiki.archlinux.org/title/Zoom_Meetings
The only thing I didn't need to do was set XDG_CURRENT_DESKTOP=gnome. I followed the other steps, and now I can choose my desktop/window to share. Prior to following the wiki I couldn't stop screen sharing without the hanging issue, which I was experiencing prior to 6.2.10.
edh commented on 2016-08-26 11:03 (UTC) (edited on 2017-03-09 10:48 (UTC) by edh)