You are not logged in.
Hi,
I have two different Arc h installations. I have installed Zoom on both boxes. While the version reads on both 5.0.399860.0429 they are different versions of it. I am pretty certain that they both have been installed using yay (at different dates though) but I have ran yay -Syyu since and hence would expect the same program to appear on either machine. On both boxes,a right click on the tray icon followed by selecting "About..." shows version 5.0.399860.0429 but while one offers me a Settings... option Open Zoom and Logout option, they are missing from the other instance. One looks newer than the other one and offers addition of a virtual back ground e.g. while the other doesn't have such an option.
Does anyone know what might have happened here? It confuses me, that they both display the same version number.
Offline
Compare the checksums of the downloaded makepkg "sources", they should still be present in your yay cache under ~/.cache/yay
Last edited by V1del (2020-05-04 06:29:05)
Offline
Mod note: moving to AUR Issues
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Compare the checksums of the downloaded makepkg "sources", they should still be present in your yay cache under ~/.cache/yay
Oh yes, there's the difference:
System A:
$ md5sum zoom-5.0.399860.0429-1-x86_64.pkg.tar.xz
a24a0fa257684f57e6ed52345fa2a5e1 zoom-5.0.399860.0429-1-x86_64.pkg.tar.xz
System B:
$ md5sum zoom-5.0.399860.0429-1-x86_64.pkg.tar.xz
57fc856fbd1259d74d3064d2f3e709ed zoom-5.0.399860.0429-1-x86_64.pkg.tar.xz
How can this be???
Offline
Did you somehow skip the integrity checks when you built the packages?
As it's an opaque source, zoom could very easily change what is available for download, but if you really did use the same PKGBUILD (with the same checksum) then at least one of the builds would have failed the checksum.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
@stdcerr, you are checksumming the built package file there, not the source download file.
$ sha512sum zoom-5.0.399860.0429_orig_x86_64.pkg.tar.xz
985d0ff7ff4aad9d75f1bd56318c77065c25b9572d4e05f74aa5916bc83c85210ab09bc4c3b58e0350d48aefd2db40079e03da1544ff2e640d2625e4aee43a34 zoom-5.0.399860.0429_orig_x86_64.pkg.tar.xz
$ grep sha512 PKGBUILD
sha512sums=('985d0ff7ff4aad9d75f1bd56318c77065c25b9572d4e05f74aa5916bc83c85210ab09bc4c3b58e0350d48aefd2db40079e03da1544ff2e640d2625e4aee43a34')
Offline
@stdcerr, you are checksumming the built package file there, not the source download file.
Yes, you are right, looking at the PKGBUILD files, they actually do match up:
System A:
$ grep sha512 PKGBUILD
sha512sums=('985d0ff7ff4aad9d75f1bd56318c77065c25b9572d4e05f74aa5916bc83c85210ab09bc4c3b58e0350d48aefd2db40079e03da1544ff2e640d2625e4aee43a34')
System B:
$ grep sha512 PKGBUILD
sha512sums=('985d0ff7ff4aad9d75f1bd56318c77065c25b9572d4e05f74aa5916bc83c85210ab09bc4c3b58e0350d48aefd2db40079e03da1544ff2e640d2625e4aee43a34')
which still does not explain the difference....
Offline
The md5sum of the built packages will be different as they have embedded date+time but the byte size should be the same. Are they?
Offline
The md5sum of the built packages will be different as they have embedded date+time but the byte size should be the same. Are they?
Yes/ usr/bin/zoom links to /opt/zoom/ZoomLauncher which both are 219392B in size
Offline
There can be a plethora of reason why a particular GUI might not show certain information, I'd say we've proven sufficiently that there's no difference in the binary files you've installed. FWIW since you are talking about the tray, is libappindicator-gtk3 installed? are both environments setup the same way? which environment are you talking about? terminal output of the "broken" zoom?
Last edited by V1del (2020-05-06 06:59:01)
Offline
There can be a plethora of reason why a particular GUI might not show certain information, I'd say we've proven sufficiently that there's no difference in the binary files you've installed. FWIW since you are talking about the tray, is libappindicator-gtk3 installed? are both environments setup the same way? which environment are you talking about? terminal output of the "broken" zoom?
I totally missed to mention that one of the systems is Manjaro and the other one is Arch - hence no, they are not setup the same way. libappindicator-gtk3 is installed yes. I don't want to call it "broken" as it functions fine, the version on my Arch box just seems to be lacking at least one feature that the version on Manjaro has....
Offline