AUR (en) - zoom

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: zoom 6.4.6-1

Package Actions

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:	686
Popularity:	9.15
First Submitted:	2015-08-15 13:18 (UTC)
Last Updated:	2025-04-22 04:41 (UTC)

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:

Zoom 6.2.10
pipewire 1.2.6

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)

I contacted the zoom support on 13th July 2016 and tried to lure them into creating a proper PKGBUILD respectively adopting this one, considering they are providing a package over very none standard ways to the Arch Linux community (downloading via a *foreign* site) and not through the official repo or the AUR. However there was little to no progress so far.

Latest Comments

« First ‹ Previous 1 .. 37 38 39 40 41 42 43 44 45 46 47 .. 82 Next › Last »

zeroconf commented on 2021-09-22 14:52 (UTC)

Zoom 5.8.0 has arrived - https://zoom.us/download#client_4meeting Appreciate, that available at Arch!

bulletmark commented on 2021-09-21 22:23 (UTC) (edited on 2021-09-21 22:26 (UTC) by bulletmark)

@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.

alerque commented on 2021-09-21 22:05 (UTC)

@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.

bulletmark commented on 2021-09-21 21:59 (UTC)

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.

edh commented on 2021-09-21 18:38 (UTC)

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.

alerque commented on 2021-09-21 18:36 (UTC)

@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.

darose commented on 2021-09-21 18:26 (UTC)

@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?

nursoda commented on 2021-09-20 09:39 (UTC) (edited on 2021-09-20 09:45 (UTC) by nursoda)

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.

edh commented on 2021-09-13 15:44 (UTC)

@dack Thank you for you comment. I am aware of the problem. Please read the previous comments. This issue has been extensively discussed. Touching pkgrel is the wrong thing to do here in my opinion.

dack commented on 2021-09-13 15:40 (UTC)

@edh Appending "a" to the version is a bit of a problem - it results in the wrong version ordering. For example, 1.0.0a is considered earlier than 1.0.0 (you can see this in man vercmp). For AUR helpers like yay, this will cause them to see the "new" version as a downgrade and not upgrade them. I think a better workaround would be to just bump pkgrel. That way it's treated as a newer package, and the upstream version number is kept as-is.