Bug 7360 - API breakage
Summary: API breakage
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Guillaume Rousse
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-05 16:24 CEST by Guillaume Rousse
Modified: 2013-03-17 23:12 CET (History)
2 users (show)

See Also:
Source RPM: apache-mod_perl
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Guillaume Rousse 2012-09-05 16:24:13 CEST 
Latest mod_perl package has been patched to build against apache 2.4, but this result into an API breakage for applications. For instance:

/var/log/httpd/error_log.1:[Thu Aug 16 17:00:30.243501 2012] [:error] [pid 13134] [client 127.0.0.1:41776] Can't locate object method "remote_ip" via package "Apache2::Connection" at /usr/lib/perl5/vendor_perl/5.16.0/Lemonldap/NG/Handler/Simple.pm line 1049.\

Fedora uses a different patch, but their package build process is too much different from our own currently to just swap.

As long as there is no official mod_perl release compatible with apache 2.4, this seems quite complex to fix correctly.
Comment 1 Marja Van Waes 2012-09-06 09:17:12 CEST 
assigning to maintainer

CC: (none) => marja11
Assignee: bugsquad => dmorganec

D Morgan 2012-10-12 01:01:07 CEST

Assignee: dmorganec => bugsquad

Comment 2 D Morgan 2012-10-12 01:02:34 CEST 
seems http://marc.info/?l=apache-modperl-dev&m=134846689530740&w=2 can help us

CC: (none) => dmorganec

Comment 3 Manuel Hiebel 2012-10-12 09:55:22 CEST 
dmorgan, please remove you from all package that you don't want maintain to avoid confusion.
Guillaume Rousse 2013-02-06 23:15:45 CET

Status: NEW => ASSIGNED

Comment 4 Guillaume Rousse 2013-02-11 22:30:19 CET 
Should be fixed in incoming 2.0.7-11.mga3.

Assignee: bugsquad => guillomovitch

Comment 5 Guillaume Rousse 2013-03-17 23:12:22 CET 
Fixed now.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.