Bug 2390252

Summary:	Please branch and build python-pylibmc in epel10
Product:	[Fedora] Fedora EPEL	Reporter:	fedepell <fede>
Component:	python-pylibmc	Assignee:	EPEL Packagers SIG <epel-packagers-sig>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel10	CC:	aurelien, epel-packagers-sig, fzatlouk, metherid, michel, pj.pandit
Target Milestone:	---	Flags:	fede: needinfo? (epel-packagers-sig)
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description fedepell 2025-08-22 04:38:28 UTC

Would it be possible to branch and build python-pylibmc in EPEL10?

I've done some tests locally on 10 and it should be straight forward, a mockbuild of current rawhide succeeded without changes for epel10.

I would be in case glad to help as co-maintainer to help with other standing bug of the package.

Many thanks!
F.

Comment 1 fedepell 2025-12-01 06:39:44 UTC

Friendly ping! Any possibility to have it in EPEL10 or have EPEL branch commit rights?

Comment 2 fedepell 2025-12-17 06:15:27 UTC

Hohoho ping :)

Comment 3 fedepell 2025-12-17 06:24:20 UTC

(just for the record: would be needed for pymemcache on the dependency tree of django5)

Comment 4 fedepell 2026-01-30 03:27:23 UTC

Pinging again if we could have this or get EPEL10 branch access to maintain the branch.