Skip to content
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

zoom-us 5.6.13632.0328 -> 5.6.16775.0418 #120032

Merged
merged 1 commit into from Apr 21, 2021
Merged

Conversation

LutzCle
Copy link
Contributor

@LutzCle LutzCle commented Apr 21, 2021

Motivation for this change

zoom-us currently is in a broken state.

Version 5.6.13632.0328 is blocked from participating in calls, and fails with a "please upgrade to the latest version" message. At the same time, the tar file that is supposed to be version 5.6.16775.0418 is bit-identical to the previous version.

Thus, no upgrade path to fix the issue is currently available using a tar file.

In consequence, this PR upgrades to the current version using the .deb file provided by Zoom for Debian/Ubuntu.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@Mic92
Copy link
Member

Mic92 commented Apr 21, 2021

backport: #120038

@LutzCle LutzCle deleted the zoom-5.6.3 branch April 21, 2021 10:04
@LutzCle
Copy link
Contributor Author

LutzCle commented Apr 22, 2021

Update: Yesterday I submitted a ticket with Zoom. The tar file has now been fixed, and I have verified that upgrading via the tar works again.

@doronbehar
Copy link
Contributor

Update: Yesterday I submitted a ticket with Zoom. The tar file has now been fixed, and I have verified that upgrading via the tar works again.

Thanks for the update. Using the tarball again in #120243 - targeting master and in #120242 a backport + fix for the stable channel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants