Discord wont update to newest version 1.0.0.116

[grizzled flower]

Tried updating it since yeaterday and nada, even uninstalled the package and reinstalled. Anyone else having this issue?

[pallid crown]

its not updated on the mirror. Question is when the Mirrors are synced.

Because its already updated upstream here: https://archlinux.org/packages/extra/x86_64/discord/

[unique token]

did you installed it on terminal? cause I just do sudo nano /opt/discord/resources/build_info.json then I change the number base on the update

[grizzled flower]

that did it, thanks!

[unique token]

Always welcome

[grizzled flower]

would you be willing to explain to me what mirrors are? i'm new to linux and to arch especially, but i'm also head strong which is why i went with arch in the first place lmao

[unique token]

If you don't want to manually do that, you can just install discord in that packages inside install in omarchy menu

And it will automatically update later(idk if im correct but I hope so)

[grizzled flower]

next time there's a Discord update (more than likely monday next week it feels like lmao) i'll try that instead of through the terminal

[pallid crown]

First up: welcome to the dark side of the force!

[pallid crown]

Basically its a copy from the main baseline arch linux repository which holds all the packages

[plain cosmos]

https://wiki.archlinux.org/title/Discord#Discord_asks_for_an_update_not_yet_available_in_the_repository

[grizzled flower]

ah i c, is there an advantage in doing that vs just pulling straight from the arch linux repository?

[proven frigate]

Their fix didn’t work for me unfortunately

[pallid crown]

Usually you do it, for having more origin endpoints in more geolocations. That’s why you see in the official mirror list a lot of entries from all over the world.

In Omarchys Case is that they are hosting another repository, next to core, extra and multilab

[plain cosmos]

Try using Vesktop (vesktop-bin from the AUR). Works perfectly out of the box

And has no update issues

[pallid crown]

And they could hold off updates to not push broken packages, f.e.

I hope this mirror explanation helped

[pallid crown]

Against Discord ToS. Wouldn’t do it

[plain cosmos]

Fair enough, though I've never heard any reports of bans for using them

But it's your account, not mine

[pallid crown]

Better safe than sorry

[plain cosmos]

I know we had a Discord dev in the server a while back, not sure he's still here

[sage vessel]

How to get it updated, should we wait for official repo update?

[plain cosmos]

Did you try the fix listed here?

[sage vessel]

Ill try it

[pallid crown]

you need to bump the version in build_info.json in /opt/discord/resources

that’s what worked for me as a temporary fix

[sage vessel]

It worked!
Just added this to the config ~/.config/discord/settings.json

{
"SKIP_HOST_UPDATE": true
}

[proven frigate]

Oh you put a start and end bracket?

I must have misread the wiki article