Whayn/vesktop

Description

Description not filled in by author. Very likely personal repository for testing purpose, which you should not use.

Installation Instructions

Instructions not filled in by author. Author knows what to do. Everybody else should avoid this repo.

Active Releases

The following unofficial repositories are provided as-is by owner of this project. Contact the owner directly for bugs or issues (IE: not bugzilla).

* Total number of downloaded packages.


This is a companion discussion topic for the original entry at https://copr.fedorainfracloud.org/coprs/whayn/vesktop
1 Like

Untrue, now.

With 91 downloads, it appears trustworthy. Though, does this avoid the undermentioned?

This repository is indeed not for personal use, but it is not of much use since Vesktop is supposed to update itself when installed straight from their rpm release (even though I created the repo at a time when this mechanism was broken and stopped the app from updating).

Since the repo is only repackaging the release rpm (view repo management source code), it doesn’t fix the aforementioned issue. I may look into it and rebuild the app with the correct flags instead of simply repackaging!

1 Like

could you enable building for fedora 43 please?

Doing this asap tomorrow !

Done !

The f43 repo exists now but your builds still only contain rpm files for 41 and 42

vesktop has started distributing full rpm files as updates through the built-in updater. These updates change the vesktop install source and detach it from your repo. Installing an update also causes a duplication of the variables in the startup entry, a mismatch with the metadata xml, and possibly even more than that. due to this change, installing vesktop on fedora from anything other than the official vesktop rpm (or flatpak w/ its limitations) is now problematic. The only way to fix this would be to completely disable vesktop’s inbuilt updater, including removing the user toggle from the settings so it can’t be turned back on. That change would also potentially break some theme compatibility. It may be time to retire this repo.

Seems like the right thing to do, thank you for your help maintaining it ! And I hope it was useful to some!