Description of problem: mod_magnet doesn't work, if enabled. Version-Release number of selected component (if applicable): lighttpd-1.4.31-1.fc17.x86_64 How reproducible: always Steps to Reproduce: 1. uncomment include "conf.d/magnet.conf" in /etc/lighttpd/modules.conf 2. start the server Actual results: 2013-02-18 18:34:14: (plugin.c.217) mod_magnet plugin init failed 2013-02-18 18:34:14: (server.c.676) loading plugins finally failed Expected results: mod_magnet should work. Additional info: Apparently if you compile lighttpd without lua support, mod_magnet is still built, it is just #ifdef'ed down to an init routine that errors out. It turns out the Fedora package is passing --without-lua to configure [1]. I looked in lighttpd.spec and the build conditionals for lua are correct for RHEL but not Fedora. I suggest: --- a/lighttpd.spec +++ b/lighttpd.spec @@ -25,17 +25,17 @@ %bcond_with memcache # No poweredby.png image in EL5 and earlier (it's in Fedora and EL6+) -%if 0%{?rhel} <= 5 -%bcond_with systemlogos -%else +%if 0%{?rhel} >= 6 || 0%{?fedora} %bcond_without systemlogos +%else +%bcond_with systemlogos %endif # LUA support requires lua >= 5.1 but EPEL4 provides only 5.0, so disable -%if 0%{?rhel} <= 4 -%bcond_with lua -%else +%if 0%{?rhel} >= 5 || 0%{?fedora} %bcond_without lua +%else +%bcond_with lua %endif # The /var/run/lighttpd directory uses tmpfiles.d when mounted using tmpfs [1] http://kojipkgs.fedoraproject.org//packages/lighttpd/1.4.31/1.fc17/data/logs/x86_64/build.log
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Problem still applies to lighttpd-1.4.31-3.fc18 and nothing has changed in dist-git so it would apply in F19 and Rawhide also.
Ping, are you even maintaining this package anymore? This bug is very annoying and the fix is straight-forward, any reason you can't apply the patch?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still not fixed.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Ping, now that lighttpd is being maintained again could you please fix this bug? The patch in comment 0 is no longer applicable since the spec has been cleaned up, all it needs is to flip the lua support to enabled.
lighttpd-1.4.34-4.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/lighttpd-1.4.34-4.fc20
lighttpd-1.4.34-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/lighttpd-1.4.34-4.fc19
Package lighttpd-1.4.34-4.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing lighttpd-1.4.34-4.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-2893/lighttpd-1.4.34-4.fc20 then log in and leave karma (feedback).
lighttpd-1.4.34-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
lighttpd-1.4.34-4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.