Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#34293 - [php-memcache] Why is there a beta instead of stable in repository?

Attached to Project: Community Packages
Opened by ... (spider007) - Wednesday, 13 March 2013, 10:17 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 26 March 2013, 08:54 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

We use php-memcache extensively, but cannot use the package in archlinux since 3.0.7 segfaults too often. Why is the stable 2.2.7 not in the repository?
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Tuesday, 26 March 2013, 08:54 GMT
Reason for closing:  None
Additional comments about closing:  Segfaults have been fixed so we'll continue using the 3.0.x branch.
Comment by Jelle van der Waa (jelly) - Wednesday, 13 March 2013, 14:43 GMT
Maybe because it doesn't work with the latest PHP?
Comment by ... (spider007) - Wednesday, 13 March 2013, 14:46 GMT
http://pecl.php.net/package/memcache/2.2.7 lists '- PHP 5.4 compatibility' and is released at the same time as the current beta, so I don't think thats it
Comment by ... (spider007) - Wednesday, 13 March 2013, 14:53 GMT
One documented example of these unfixed segfaults is https://bugs.php.net/bug.php?id=63142
Comment by Evangelos Foutras (foutrelis) - Thursday, 14 March 2013, 20:20 GMT
The switch to the 3.0.x branch was made over three years ago [1]; unfortunately, I don't remember the reason for that.

I also see that both Debian and CentOS have 3.0.x in their stable repositories [2]. This makes me somewhat hesitant to go back to 2.2.x.

[1] https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packages/php-memcache&id=d65b1d4191f39faa852c04aa3d6db1c0675850fe
[2] Albeit slightly older releases; 3.0.4 in Debian Squeeze and 3.0.5 in CentOS 6.4.
Comment by ... (spider007) - Friday, 15 March 2013, 12:46 GMT
I understand your hesitation, since it is impossible to know if users are successfully using 3 who would not like to go back to 2. Regarding the timespan; php-memcache has not had frequent releases, so the '3 years' isn't a very strong argument since it is also just 4 releases ago.

Although I am happy with Archlinux packages being generally the latest available version; in this case php-memcache 3 has not had a stable release and has a known bug for a few months; so I would be in favor of supplying a stable version 2 instead. If you disagree I will happily create a php-memcache2 in the AUR for myself to use.
Comment by Evangelos Foutras (foutrelis) - Tuesday, 19 March 2013, 15:18 GMT
php-memcache 3.0.7-2 should solve the segfaults described in PHP bug #63142.

Can you give it a try and see if it works well with your code base?
Comment by ... (spider007) - Thursday, 21 March 2013, 08:44 GMT
We are currently chasing yet another segfault in php which doesn't seem related to php-memcache; I'll post the results in this bug
Comment by ... (spider007) - Monday, 25 March 2013, 09:39 GMT
Okay we no longer seem to experience these problems with the newest version. Would this mean the 3.0 might be tagged as stable some time in the future?
Comment by Evangelos Foutras (foutrelis) - Monday, 25 March 2013, 09:58 GMT
The stable and beta designations don't seem to mean much in the case of php-memcache, considering the first "beta" of 3.0.x was released over 5 years ago.

I see them as two separate branches, with 3.0.x having more features (and sometimes an additional bug or two).

Glad to hear 3.0.7-2 has been working well for you; I'll go ahead and close this task.

Loading...