Package Details: zoom 6.2.11-1

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.81
First Submitted: 2015-08-15 13:18 (UTC)
Last Updated: 2024-11-25 17:39 (UTC)

Dependencies (31)

Sources (1)

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 .. 36 37 38 39 40 41 42 43 44 45 46 .. 78 Next › Last »

daniel_shub commented on 2021-08-25 13:36 (UTC)

@hellojack upstream provides the Arch package that this PKGBUILD is based on. That upstream package lists ibus as a dependency. Not obvious to me why it is a dependency, but generally I believe the upstream developers when they say something is a dependency. You can always remove it from your PKGBUILD.

alerque commented on 2021-08-25 08:47 (UTC)

@roper I can see from your error message that you are not using the latest version of this package. The current version saves the source with an extra a in there that does not show in your error message. Please update to the latest commit of this packaging repository.

roper commented on 2021-08-25 08:29 (UTC) 

==> Validating source files with sha512sums...
    zoom-5.7.6_orig_x86_64.pkg.tar.xz ... FAILED
==> ERROR: One or more files did not pass the validity check!

hellojack commented on 2021-08-25 04:42 (UTC) (edited on 2021-08-25 04:45 (UTC) by hellojack)

Hello, are there reason for ibus being dependency? It is one of the input methods, not needed for people who use another ime.

spsf64 commented on 2021-08-24 14:26 (UTC)

@daniel_shub thanks for the tip (¨.a¨)!

daniel_shub commented on 2021-08-24 13:51 (UTC)

@edh first, thanks for maintaining the package. I maintain the rememberthemilk package and they pull the same crap of updating the binary without changing the version number. I want to say that I think your approach was almost spot on and what I am going to do in the future. Bumping the pkgrel for a change in the upstream binary is not what pkgrel is designed for while updating the pkgver to trigger a new download and rebuild is the way to go. Had you set pkgver to be 5.7.6.a instead of 5.7.6a, then vercmp would detect the change and everything would be fine. Of course no one should expect a maintainer to nail all the nuances of vercmp and the package build process every time. Again, thanks for maintaining this package.

edh commented on 2021-08-23 22:53 (UTC)

@bulletmark

Sorry, I forgot about the vercmp specifics here. I indeed intended to make the new version large than the one before. However, since the checksum was in a sense outdated, users who did not adapt the PKGBUILD could not upgrade anyways and those who did, do not need upgrade now.

No, this is simply not what pkgrel is for. Upstream updating the binary package is not the same as a mere rebuild with different configuration flags or changes to the PKGBUILD. See @aditya comment on the definition of pkgrel.

The reason why I was reluctant to change the pkgrel is because it does not force users to re-download the binary file. Of course I could have included pkgrel in the target filename but this did not seem proper to me.

bulletmark commented on 2021-08-23 22:10 (UTC)

Adding that 'a' doesn't trigger an update. Upstream has published a new binary so I would say an update is required, i.e. the pkgrel should be updated.

edh commented on 2021-08-23 19:01 (UTC)

@aditya

The PKGBUILD really did not change, i.e. it is not a consecutive build. It is zoom that pushed a new binary package to the same URL.

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