Arch Linux

mikairyuu

Member

Registered: 2020-12-05

Posts: 1

What should I do if there's new update to the package?

Hello there,
That question has probably been answered here before, but my attempts to google it have failed, so here I am.

So, there's been a new update to discord, 13.0. The version on arch repo is still 12-2 atm.  Afaik there's no way to update it without being the maintainer. That leaves me with only one option - updating it on my side. But, how should it be done? I can download the latest discord in .deb and .tar.gz. I'm not sure how I can update it without ruining pacman sync and stuff. Like, for example, I can install deb by using debtap, but it explicitly asks not to update packages that are in arch repo already by using it, seems like it will break pacman index databases or something.
What should i do?
Thanks in advance.

Last edited by mikairyuu (2020-12-05 08:30:08)

d_fajardo

Member

Registered: 2017-07-28

Posts: 1,687

Re: What should I do if there's new update to the package?

You can write your own PKGBUILD for it. What you can do is you can download the PKGBUILD that is in the repo, study it, and tweak it for the new package. I would also recommend building it first from a clean chroot just to make sure it builds ok before installing it in your system.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,678

Re: What should I do if there's new update to the package?

https://bbs.archlinux.org/viewtopic.php?id=261415
The linked https://support.discord.com/hc/en-us/co … -available says you can fool it by editing a json file… sigh.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

MountainX

Member

Registered: 2016-02-08

Posts: 371

Re: What should I do if there's new update to the package?

So, there's been a new update to discord, 13.0. The version on arch repo is still 12-2 atm.  Afaik there's no way to update it without being the maintainer. That leaves me with only one option - updating it on my side. ...

What should i do?

In addition to the other suggestions, you should leave a comment on the AUR page and/or flag the package as out of date. You may want to volunteer to be a co-maintainer of this package...

Xyne

Forum Fellow

Registered: 2008-08-03

Posts: 6,965

Website

Re: What should I do if there's new update to the package?

In addition to the other suggestions, you should leave a comment on the AUR page and/or flag the package as out of date. You may want to volunteer to be a co-maintainer of this package...

Discord is in the community repo, not the AUR. The current version has already been updated, but in the future it can be flagged as out-of-date by anyone via the web interface under "Packages" in the navbar above. Only devs and trusted users can (co-)maintain packages in the official repos, but patches or updated PKGBUILDs and be submitted to the maintainer.

It's also unreasonable that discord only accepts connections from the latest version as soon as it's out, especially if a simple edit to a json file can bypass their check. There's obviously no protocol change so that requirement demonstrates a complete disregard for how packaging works across all linux ecosystems (and no, we don't all want to replace everything with flatpak and multifold binary redundancy). Add your voice to the chorus of complains. Maybe they'll reconsider their approach.

---

My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone

MountainX

Member

Registered: 2016-02-08

Posts: 371

Re: What should I do if there's new update to the package?

In addition to the other suggestions, you should leave a comment on the AUR page and/or flag the package as out of date. You may want to volunteer to be a co-maintainer of this package...

Discord is in the community repo, not the AUR.

My bad. Just ignore what I said in that case.

MountainX

Member

Registered: 2016-02-08

Posts: 371

Re: What should I do if there's new update to the package?

(and no, we don't all want to replace everything with flatpak and multifold binary redundancy)

This is a good article on that important topic: Maintainers Matter: The case against upstream packaging (postscript)