Outdated opal and ptlib

opencode · 2016-10-27 00:22:06

The opal package is currently using version 3.10.11. According to the upstream site listed in the package (http://www.opalvoip.org), the latest stable release is "Stable 2" of 3.16 (3.16.2).

Similarly, ptlib is currently version 2.10.11, but upstream's latest stable release is 2.16.2.

I tried flagging both packages out-of-date per the documentation:
"If you notice that a package is out-of-date (i.e., there is a newer *stable* release available), then please notify us by using the Flag button in the Package Details screen. This will notify the maintainer(s) responsible for that package so they can update it."

I had noticed the "stable" qualification and made sure to check that first - upstream explicitly labels the new release as "Stable".

However, it looks like the flag was removed from both packages and they're still on the older versions. I'm guessing there's some additional context I'm missing - could someone here help?

The reason I ask is that I'm working on an AUR package for FreeSWITCH 's mod_opal, and it requires at least version 3.12.8 of opal.

Thanks,

David

Last edited by opencode (2016-10-27 00:22:20)

headkase · 2016-10-27 02:36:07

You could always use the Arch Build System to build a newer version yourself. Get a PKGBUILD out of it, and often all you have to do is to change the version numbers in there to successfully create a new package.

basica · 2016-10-27 03:02:42

To get some more context, I'd probably try sending an email to the mailing list, or potentially just contacting the maintainer directly to find out what's going on.

arojas · 2016-10-27 05:03:37

I suppose it's being held back by ekiga. That wouldn't justify unflagging it though, since it is indeed out of date. IMO in these cases (package update being deliberately held back and third party software requiring a newer version) it should be acceptable to add an AUR package (opal3.12) with the newer version.

JGC · 2016-10-28 13:39:22

The only reason why we have opal and ptlib in extra is because of ekiga. Ekiga cannot work with a newer version, so we cannot and will not upgrade opal/ptlib.

If we decide to drop ekiga from the repositories because upstream doesn't care about releases, we'll drop opal/ptlib with it.

opencode · 2016-10-28 16:18:14

Thanks for the context - that makes sense.

What would you think about naming the packages opal310 and ptlib210 to reflect the fact that they intentionally provide an older version? That could help clarify when you'd want them to be flagged as out-of-date.
https://wiki.archlinux.org/index.php/Ar … age_naming
https://wiki.archlinux.org/index.php/Py … d_versions

Then I could create opal and ptlib packages in AUR as dependencies for freeswitch, and they could float with the latest stable version as normal. (And if anything were added to community or extra that needs either of these packages, the naming would work out like it does for packages like qtlib or python.)

Thanks,

David

Arch Linux

#1 2016-10-27 00:22:06

Outdated opal and ptlib

#2 2016-10-27 02:36:07

Re: Outdated opal and ptlib

#3 2016-10-27 03:02:42

Re: Outdated opal and ptlib

#4 2016-10-27 05:03:37

Re: Outdated opal and ptlib

#5 2016-10-28 13:39:22

Re: Outdated opal and ptlib

#6 2016-10-28 16:18:14

Re: Outdated opal and ptlib

Board footer