fails to install in nobara linux(fedora 39)
kevin01523 opened this issue · 8 comments
Versions
- Pi-hole: n/a
- AdminLTE: n/a
- FTL: n/a
Platform
- OS and version:
NAME="Nobara Linux"
VERSION="39 (KDE Plasma)"
- Platform: Baremetal
Expected behavior
pihole installs successfully
A clear and concise description of what you expected to happen.
Actual behavior / bug
`curl -sSL https://install.pi-hole.net | sudo bash
[sudo] password for sette:
[✓] Root user check
.;;,.
.ccccc:,.
:cccclll:. ..,,
:ccccclll. ;ooodc
'ccll:;ll .oooodc
.;cll.;;looo:.
.. ','.
.',,,,,,'.
.',,,,,,,,,,.
.',,,,,,,,,,,,....
....''',,,,,,,'.......
......... .... .........
.......... ..........
.......... ..........
......... .... .........
........,,,,,,,'......
....',,,,,,,,,,,,.
.',,,,,,,,,'.
.',,,,,,'.
..'''.
[✓] Default SELinux: disabled
[✓] Current SELinux: disabled
[i] Enabling EPEL package repository (https://fedoraproject.org/wiki/EPEL)
expressvpn 614 B/s | 833 B 00:01
[MIRROR] epel-release-latest-39.noarch.rpm: Status code: 404 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-39.noarch.rpm (IP: 38.145.60.23)
[MIRROR] epel-release-latest-39.noarch.rpm: Status code: 404 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-39.noarch.rpm (IP: 38.145.60.23)
[MIRROR] epel-release-latest-39.noarch.rpm: Status code: 404 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-39.noarch.rpm (IP: 38.145.60.23)
[MIRROR] epel-release-latest-39.noarch.rpm: Status code: 404 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-39.noarch.rpm (IP: 38.145.60.23)
[FAILED] epel-release-latest-39.noarch.rpm: Status code: 404 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-39.noarch.rpm (IP: 38.145.60.23)
Status code: 404 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-39.noarch.rpm (IP: 38.145.60.23)
`
A clear and concise description of what the bug is.
Steps to reproduce
Steps to reproduce the behavior:
run the install script on terminal
curl -sSL https://install.pi-hole.net | sudo bash
Debug Token
- URL:
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
This is an OS level issue.
The message is saying Fedora server is answering with error 404 (not found).
This is an OS level issue.
The message is saying Fedora server is answering with error 404 (not found).
more like the script pointing to the wrong package
its saying epel 39 when the latest epel package is epel 9
i think it has to do more with os recognition issue etc
404 for EPEL on Fedora is valid behavior as EPEL is not required for Fedora.
The issue here is that the install script is detecting it as an rpm based distro but failing the fedora check and treating the install as a RHEL/CentOS/etc.
@kevin01523 can you please provide the contents of /etc/redhat-release on your nobora install?
Looks like the contents of /etc/redhat-release is causing the issue:
Nobara release 39 (Thirty Nine)
Here is a quick workaround for you in hope to get your installation completed:
curl -sSL https://install.pi-hole.net/ | sed -e 's/fedberry/fedberry|nobara/' | sudo bash
I will discuss this further with the team as to whether we want to push a quick fix to the installer in next release or if we want to re-imagine the logic in the installer to better handle derivatives of officially supported distros.
same issue even if i use the command below
curl -sSL https://install.pi-hole.net/ | sed -e 's/fedberry/fedberry|nobora/' | sudo bash
Oops, I have a typo in that command. Update nobora -> nobara.
My apologies, I will update it in my above comment for future users.
failing with os check but ill try to continue the install with this command
curl -sSL https://install.pi-hole.net/ | sed -e 's/fedberry/fedberry|nobara/' | sudo PIHOLE_SKIP_OS_CHECK=true bash
it seems to continue
ill update later if it succeeds with a complete install later
its fully working now had to tweak dnsmasq etc and fix ftl not running but its trivial
i'll let the dev decide when to close this issue orthey can close it when they added a fix for better handling derivatives of officially supported distros
thanks @bcambl
This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.
so this not gonna be fixed?