Hi!

Launchpad is the canonical source. There are some patches I have pushed 
recently and there will probably be a release in the near future. 

        β€” Brian

乌



> On Apr 22, 2021, at 11:26 AM, Dylan Thacker-Smith <[email protected]> 
> wrote:
> 
> 
> Is this supposed to be the source of truth for libmemcached development? The 
> README says project information is on https://libmemcached.org/ 
> <https://libmemcached.org/> but "Source Code" link on that page links to 
> https://code.launchpad.net/libmemcached 
> <https://code.launchpad.net/libmemcached> which doesn't mention this repo. 
> The launchpad project also has its own bug tracking 
> (https://bugs.launchpad.net/libmemcached 
> <https://bugs.launchpad.net/libmemcached>) which is linked to from the "Bug 
> Tracking" link on https://libmemcached.org/ <https://libmemcached.org/> . The 
> README refers contributors to README.FIRST which also references launchpad 
> and the bazaar repo.
> 
> There is also a mention of a mailing list on the README which I didn't find.
> 
> On the other hand, the README says to report bugs here 
> (https://github.com/libmemcached/libmemcached/issues 
> <https://github.com/libmemcached/libmemcached/issues>), so it does look like 
> there was an intention of moving development here.
> 
> It looks like there was some work somewhat recently to keep this project 
> building, which seemed to previously be a blocker for development (#3 
> (comment) 
> <https://github.com/libmemcached/libmemcached/issues/3#issuecomment-526861248>).
>  However, there is still no CI setup and tests aren't passing locally with 
> the latest memcached server version (e.g. #12 
> <https://github.com/libmemcached/libmemcached/pull/12>), which should be 
> prioritized to more confidently make and accept changes.
> 
> Ubuntu had also decided this library wasn't being maintained when trying to 
> address https://bugs.launchpad.net/libmemcached/+bug/1381160 
> <https://bugs.launchpad.net/libmemcached/+bug/1381160> as seen from the 
> discussion on 
> https://bugs.launchpad.net/ubuntu/+source/libmemcached/+bug/1573594 
> <https://bugs.launchpad.net/ubuntu/+source/libmemcached/+bug/1573594>
> Upstream seems pretty quiet since 2014
> Unfortunately, because the project seems more or less dead ... it seems like 
> we won't be able submit anything upstream and go straight to fixing Debian 
> and Ubuntu.
> 
> It looks like that security bug still hasn't been fixed here. That means that 
> distributions are having to maintain their own set of patches. For instance, 
> it looks like Ubuntu focal has 8 patches for libmemcached.
> 
> @BrianAker <https://github.com/BrianAker> are you looking for help 
> maintaining the library? If so, there is a more actively maintained fork made 
> by @m6w6 <https://github.com/m6w6> at https://github.com/m6w6/libmemcached 
> <https://github.com/m6w6/libmemcached> which is supposed to be a 
> "Resurrection of libmemcached https://launchpad.net/libmemcached 
> <https://launchpad.net/libmemcached>". Were you aware of that fork? The fact 
> that the fork started from the code on launchpad (first commit after forking 
> <https://github.com/m6w6/libmemcached/commit/d169e8c62f8ca4fe7d058d8e2254426105032b7e>)
>  after development started in git (commit that introduced .gitignore 
> <https://github.com/libmemcached/libmemcached/commit/eda2becbec24363f56115fa5d16d38a2d1f54775>)
>  is another indication that it should be clearer if this github repo should 
> be the source of truth.
> 
> Note that https://github.com/m6w6/libmemcached 
> <https://github.com/m6w6/libmemcached> has a test suite that passes with the 
> latest memcached, it has CI setup to test PRs and has fixed the above 
> mentioned security issue. I would like to help (e.g. #12 
> <https://github.com/libmemcached/libmemcached/pull/12>) but it seems like 
> doing the work here is redundant when I see the same issue already fixed 
> there. @BrianAker <https://github.com/BrianAker> do you have any concerns 
> with the direction that the fork is taking? Since ideally we could align our 
> efforts and work together in a single clear official repo of libmemcached 
> development.
> 
> β€”
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub 
> <https://github.com/libmemcached/libmemcached/issues/13>, or unsubscribe 
> <https://github.com/notifications/unsubscribe-auth/AAACDXZK2KJGGHNO3VEYUFLTKBS4VANCNFSM43NBONEA>.
> 

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/memcached/75DEE970-26AB-4D75-9FA7-1A50C0B77F62%40tangent.org.

Reply via email to