Package Details: linphone-desktop-appimage 5.2.1-3

Git Clone URL: (read-only, click to copy)
Package Base: linphone-desktop-appimage
Description: A free VoIP and video softphone based on the SIP protocol (AppImage version)
Upstream URL:
Keywords: voip
Licenses: GPL2
Conflicts: linphone-desktop-all, linphone-desktop-all-git, linphone-desktop-git, linphone-git
Provides: linphone, linphone-desktop
Submitter: lynix
Maintainer: lynix
Last Packager: lynix
Votes: 12
Popularity: 0.008056
First Submitted: 2020-04-19 07:00 (UTC)
Last Updated: 2024-02-12 13:46 (UTC)

Dependencies (1)

Required by (2)

Sources (2)

Latest Comments

1 2 3 4 5 Next › Last »

bossi commented on 2024-02-12 14:08 (UTC) (edited on 2024-02-13 09:49 (UTC) by bossi)

@jsimon0: Out of interest: Is another bump of both .PKGBUILD's and .SRCINFO's pkgrel to 3 strictly necessary or would it suffice to only bring PKGBUILD's pkgrel up to 2 to be in sync with .SRCINFO? No client should have 3.2.1-2 installed, so the only (hypothetical) reason I can think of is that a(nother) bump of .SRCINFO would be required if that's what is necessary for the package managers to pull master again (which I'd tend to doubt - I'd guess that AUR repos always get pulled before the build but that's a guess).

jsimon0 commented on 2024-02-12 13:43 (UTC)

Just bump them both to 3 and then reset on the next pkgver change. Short term pain vs long term pain

bossi commented on 2024-02-12 13:25 (UTC)

All good, thanks for looking into it; that was my understanding and it does at least confirm that I'm not mistaken in my assumptions.

It looks like to me that you might want to bump PKGBUILD's pkgrel to 2 again for it to be in sync with .SRCINFO's pkgrel if you want to satisfy Arch upgrade and stop it from reinstalling the package over and over again (on systems that have 5.2.1-1 installed).

Your intention to reset PKGINFO's pkgrel to 1 again for each next version bump makes a lot of sense, however, the two definitions are out of sync as they currently stand, causing indefinite reinstallations.

lynix commented on 2024-02-12 13:15 (UTC)

pkgrel=2 sticking around was an oversight during the release of v5.2.0, I should have reset it to 1 back then.

I have committed the change to set pkgrel=1 in preparation to not forget it for the next upstream release. I couldn't sync it to SRCINFO though as that would be a downgrade and AUR does not allow that.

Sorry for causing confusion, I just tried to fix the pkgrel issue upfront.

bossi commented on 2024-02-12 13:10 (UTC)

Looking at your wiki link it sounds like pkgrel should be used to denote subsequent releases of a package for the same version (as is the case here), while epoch being a precedence override only to be used in edge-cases where strictly needed and I can't see it being used in the PKGBUILD, so we're probably talking past each other (?).

Observation: Arch says 5.2.1-2 is available and builds the package but it keeps installing as 5.2.1-1, thus keeps on repeating itself with every system upgrade.

Assumed cause: AUR database has been bumped to -2 but PKGINFO is still at 1 (has been reverted from 2 to 1 post release I believe, not sure if this might be a factor). I'm assuming, if this is how it works, that the local update system reads the database, which claims there's a -2 available, builds and installs, which, however, keeps on (re)installing to -1, causing it to repeat itself.

Correct me if I'm wrong, I might be mistaken in how the versions are communicated; the above is just an assumption of why it's stuck in a loop.

pschichtel commented on 2024-02-12 12:14 (UTC)

@bossi: I think you are confusing pkgrel with epoch.

bossi commented on 2024-02-12 12:08 (UTC)

This package keeps trying to update itself to 5.2.1-2 even though the PKGBUILD specifies a pkgrel of 1. A brief look master looks like it's been reverted to 1 from a previous -2 release but is now out of sync with the version specified in the package database here; I'm assuming this is either an oversight.

I'm not familiar with standard conventions of AUR versioning but I'd presume (pkgrel) versions should not get decreased once publicly released but rather strictly incremented only. So probably bump it to 2 in PKGBUILD (again) and reset to 1 on next release, both in PKGBUILD and in the package database.

zapata commented on 2024-02-04 18:08 (UTC)

Should pkgrel be reset to 1 when a new release is published? Thanks.

lynix commented on 2023-12-23 10:17 (UTC)

Can you please add linphone=${pkgver} to the provides array?

Done :)

And if there is no /usr/bin/linphone, can you create one, as it has been in the past?

That should already be present.

dreieck commented on 2023-12-22 15:04 (UTC)

Can you please add linphone=${pkgver} to the provides array?

And if there is no /usr/bin/linphone, can you create one, as it has been in the past?

There are packages that depend on linphone.

Thanks for maintaining!