Summary: | Core Update 156 Testing - Internal server error when selecting wio after upgrade | ||
---|---|---|---|
Product: | IPFire | Reporter: | Adolf Belka <adolf.belka> |
Component: | --- | Assignee: | Stephan Feddersen <s.feddersen> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | Major Usability | ||
Priority: | - Unknown - | CC: | alexander.marx, jonatan.schlag, michael.tremer |
Version: | 2 | ||
Hardware: | unspecified | ||
OS: | Unspecified | ||
Attachments: | http_error_log |
Description
Adolf Belka
2021-04-20 21:43:06 UTC
Confirmed that the same effect occurs with themes darkdos and maniac in addition to ipfire-legacy. The problem does not occur with themes ipfire or ipfire-rounded. Hi, https://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=config/rootfiles/core/156/filelists;h=956cbc99a82899ca0f2ddb5965c10184120b5573;hb=refs/heads/master missies wio. So the files get not updated and are not hardcoded to the ipfire theme. Shipping wio should be enough so to solve this. Jonatan So if wio needs to be in the Core Update 156 filelists how do I make that happen. Do I just create a patch with a file that contains a wio link in the same format as the other filelist entries? (In reply to Adolf Belka from comment #3) > So if wio needs to be in the Core Update 156 filelists how do I make that > happen. WIO is an add-on package and those files do not belong in the core update. What is required is to increment the package release number and that is it. @Adolf: Stephan is the maintainer for WIO and therefore this ticket is assigned to him. Stephan asked for his account to be closed which is why I will close this ticket, too. If anyone else wants to work on this, feel free to assign it to yourself. I missed that I still had this open. It is no longer a problem. It looks like when the themes were removed so that only the one theme is available it solved the problem. So I am perfectly happy for it to be closed. Okay. Thank you for the feedback :) |