Conflict with luci-base #20
Comments
|
The conflicts are the files in /www/cgi-bin/ Juci tries to add a file named "luci" which of course conflicts with the standard luci. Actually luci-base includes an important set of libraries uses by other packets so it should be compatible with Juci. I think the best solution is to remove the conflicting files from Juci |
|
How do we then deal with case of upgrade from luci to juci and user being
auto redirected from root to cgi-bin/luci which does not exist?
On 19 Feb 2017 04:26, "Pau" <[email protected]> wrote:
The conflicts are the files in /www/cgi-bin/ Juci tries to add a file named
"luci" which of course conflicts with the standard luci.
Actually luci-base includes an important set of libraries uses by other
packets so it should be compatible with Juci. I think the best solution is
to remove the conflicting files from Juci
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AERqiYvqJHMR3dcLKm5rRHsw2MxFsV4gks5rd7ZzgaJpZM4MFUl3>
.
|
|
You can do it from /etc/uci-defaults/40-juci-openwrt-config adding
something like this:
grep -q -i juci /www/cgi-bin/luci || {
mv /www/cgi-bin/luci /www/cgi-bin/luci-original
cat >> /www/cgi-bin/luci << EOF
#!/usr/sbin/bash
echo "Content-type: text/html"
echo
echo "<html><head></head><body><a href="/">Click here to go to new JUCI
webgui.</a></body></html>"
EOF
}
I suppose this file (40-juci-openwrt-config) is executed on first boot
but also after an upgrade, because in any case juci needs to have all
those config options in the system.
…On 19/02/17 07:56, Martin K. Schröder wrote:
How do we then deal with case of upgrade from luci to juci and user being
auto redirected from root to cgi-bin/luci which does not exist?
On 19 Feb 2017 04:26, "Pau" ***@***.***> wrote:
The conflicts are the files in /www/cgi-bin/ Juci tries to add a file named
"luci" which of course conflicts with the standard luci.
Actually luci-base includes an important set of libraries uses by other
packets so it should be compatible with Juci. I think the best solution is
to remove the conflicting files from Juci
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AERqiYvqJHMR3dcLKm5rRHsw2MxFsV4gks5rd7ZzgaJpZM4MFUl3>
.
--
./p4u
|
|
Sounds reasonable. In fact no need for the grep. It is enough to just copy
the redirect script if it doesn't already exist at first boot. Uci defaults
will only run once.
…On 19 Feb 2017 14:43, "Pau" ***@***.***> wrote:
You can do it from /etc/uci-defaults/40-juci-openwrt-config adding
something like this:
grep -q -i juci /www/cgi-bin/luci || {
mv /www/cgi-bin/luci /www/cgi-bin/luci-original
cat >> /www/cgi-bin/luci << EOF
#!/usr/sbin/bash
echo "Content-type: text/html"
echo
echo "<html><head></head><body><a href="/">Click here to go to new JUCI
webgui.</a></body></html>"
EOF
}
I suppose this file (40-juci-openwrt-config) is executed on first boot
but also after an upgrade, because in any case juci needs to have all
those config options in the system.
On 19/02/17 07:56, Martin K. Schröder wrote:
> How do we then deal with case of upgrade from luci to juci and user being
> auto redirected from root to cgi-bin/luci which does not exist?
>
> On 19 Feb 2017 04:26, "Pau" ***@***.***> wrote:
>
> The conflicts are the files in /www/cgi-bin/ Juci tries to add a file
named
> "luci" which of course conflicts with the standard luci.
>
> Actually luci-base includes an important set of libraries uses by other
> packets so it should be compatible with Juci. I think the best solution
is
> to remove the conflicting files from Juci
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#20 (comment)-
280892992>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/
AERqiYvqJHMR3dcLKm5rRHsw2MxFsV4gks5rd7ZzgaJpZM4MFUl3>
> .
>
>
--
./p4u
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AERqiTh4YqVvH20WrhNHbYYDMUu_NRfrks5reEbpgaJpZM4MFUl3>
.
|
|
Right.
…On 19/02/17 17:28, Martin K. Schröder wrote:
Sounds reasonable. In fact no need for the grep. It is enough to just copy
the redirect script if it doesn't already exist at first boot. Uci defaults
will only run once.
On 19 Feb 2017 14:43, "Pau" ***@***.***> wrote:
> You can do it from /etc/uci-defaults/40-juci-openwrt-config adding
> something like this:
>
> grep -q -i juci /www/cgi-bin/luci || {
> mv /www/cgi-bin/luci /www/cgi-bin/luci-original
> cat >> /www/cgi-bin/luci << EOF
> #!/usr/sbin/bash
> echo "Content-type: text/html"
> echo
> echo "<html><head></head><body><a href="/">Click here to go to new JUCI
> webgui.</a></body></html>"
> EOF
> }
>
> I suppose this file (40-juci-openwrt-config) is executed on first boot
> but also after an upgrade, because in any case juci needs to have all
> those config options in the system.
>
>
> On 19/02/17 07:56, Martin K. Schröder wrote:
>> How do we then deal with case of upgrade from luci to juci and user being
>> auto redirected from root to cgi-bin/luci which does not exist?
>>
>> On 19 Feb 2017 04:26, "Pau" ***@***.***> wrote:
>>
>> The conflicts are the files in /www/cgi-bin/ Juci tries to add a file
> named
>> "luci" which of course conflicts with the standard luci.
>>
>> Actually luci-base includes an important set of libraries uses by other
>> packets so it should be compatible with Juci. I think the best solution
> is
>> to remove the conflicting files from Juci
>>
>> —
>> You are receiving this because you are subscribed to this thread.
>> Reply to this email directly, view it on GitHub
>> <#20 (comment)-
> 280892992>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/
> AERqiYvqJHMR3dcLKm5rRHsw2MxFsV4gks5rd7ZzgaJpZM4MFUl3>
>> .
>>
>>
>
> --
> ./p4u
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#20 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AERqiTh4YqVvH20WrhNHbYYDMUu_NRfrks5reEbpgaJpZM4MFUl3>
> .
>
--
./p4u
|
|
Here the pull requests to fix this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
juci and luci-base are not compatible, the compilation process crashes when tries to install files at same directory . Juci must not be selected if luci-base is selected and the other side around.
The text was updated successfully, but these errors were encountered: