libapache2-mod-rpaf has wrong name in conf file

libapache2-mod-rpaf (0.6-3) unstable; urgency=low

   * Fixed module naming stuff in rpaf.conf (Thanks to Alexander
     Kuznetsov). Closes: #653330.
[...]

This fix is in The Quantal Quetzal (current stable release).

Status changed to 'Confirmed' because the bug affects multiple users.

debdiff of the backported quantal fix for precise

Uploaded to precise-proposed.

Hello Kurt, or anyone else affected,

Accepted libapache2-mod-rpaf into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libapache2-mod-rpaf/0.6-2ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Inspecting the .deb at https://launchpad.net/ubuntu/precise/i386/libapache2-mod-rpaf/0.6-2ubuntu1 it doesn't seem to be fixed per the bug description. The full /etc/apache2/mods-available/rpaf.conf in that package is:

<IfModule rpaf_module>
RPAFenable On
RPAFsethostname On
RPAFproxy_ips 127.0.0.1 ::1
</IfModule>

Either the test case is wrong or the package is wrong.

@scott:

What appears in the debdiff is what is present in Saucy. The existing modification is slightly different from what was proposed in the patch and it does indeed fix the problem, just like it does in saucy.

 Maybe that should have been verified before pulling the package out of -proposed as this has been tested by at least two different person including myself.

It hasn't been removed.

Please correct the test case and mark it verification-done then.

This is the change as it appears in Saucy :

http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/libapache2-mod-rpaf/saucy/view/head:/debian/rpaf.conf

Can this package please be released into -updates ?

Then I must be missing the obvous : The test case above says :

The file /etc/apache2/mods-available/rpaf.conf should contain the following :

<IfModule rpaf_module>
RPAFenable On
RPAFsethostname On
RPAFproxy_ips 127.0.0.1 ::1
</IfModule>

Testing it on Precise-proposed a minute ago gives me :

$ cat /etc/apache2/mods-available/rpaf.conf
<IfModule rpaf_module>
RPAFenable On
RPAFsethostname On
RPAFproxy_ips 127.0.0.1 ::1
</IfModule>

This is coherent with the content of the debdiff. What am I missing here ?

My mistake. I misread the test case. I read it as this being the relevant bit:

... so it must be

<IfModule mod_rpaf-2.0.c>

It's fine. Sorry for the confusion.

This bug was fixed in the package libapache2-mod-rpaf - 0.6-2ubuntu1

---------------
libapache2-mod-rpaf (0.6-2ubuntu1) precise; urgency=low

  * debian/conf/rpaf.conf : Fixes invalid module name
    by backporting existing fix from Quantal (LP: #1126233)
 -- Louis Bouchard <email address hidden> Wed, 28 Aug 2013 16:09:47 +0200

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.