github-starred/newt
2
0
Fork 0
mirror of https://github.com/fosrl/newt.git synced 2026-05-06 07:59:04 -05:00
Code Issues 227 Packages Projects Releases 40 Wiki Activity

[GH-ISSUE #198] Newt Installscript fails #2045

New Issue
Closed
opened 2026-05-03 05:44:13 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-05-03 05:44:13 -05:00
Owner
Copy Link

Originally created by @legionGer on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/198

Describe the Bug

Hey,

I tried installing newt on both Alpine and Debian 13, the install script will fail on both ... xxx@newt:~# curl -fsSL https://pangolin.net/get-newt.sh | bash [INFO] Installing latest version of newt... [INFO] Fetching latest version from GitHub... [ERROR] Failed to fetch latest version information

curl -fsSL https://api.github.com/repos/fosrl/newt/releases/latest returns a 404.

Installing newt manually will also fail to fetch information about the latest version.

Environment

  • Alpine latest and Debian 13
  • Newt Version: latest

To Reproduce

Try installing newt on a fresh OS.

Expected Behavior

To download newt-

Originally created by @legionGer on GitHub (Dec 10, 2025). Original GitHub issue: https://github.com/fosrl/newt/issues/198 ### Describe the Bug Hey, I tried installing newt on both Alpine and Debian 13, the install script will fail on both ... `xxx@newt:~# curl -fsSL https://pangolin.net/get-newt.sh | bash [INFO] Installing latest version of newt... [INFO] Fetching latest version from GitHub... [ERROR] Failed to fetch latest version information` curl -fsSL https://api.github.com/repos/fosrl/newt/releases/latest returns a 404. Installing newt manually will also fail to fetch information about the latest version. ### Environment - Alpine latest and Debian 13 - Newt Version: latest ### To Reproduce Try installing newt on a fresh OS. ### Expected Behavior To download newt-
GiteaMirror commented 2026-05-03 05:44:14 -05:00
Author
Owner
Copy Link

@HubEight commented on GitHub (Dec 10, 2025):

I have this error too.

<!-- gh-comment-id:3636507499 --> @HubEight commented on GitHub (Dec 10, 2025): I have this error too.
GiteaMirror commented 2026-05-03 05:44:15 -05:00
Author
Owner
Copy Link

@gshomelab commented on GitHub (Dec 10, 2025):

Getting the same error

<!-- gh-comment-id:3638209353 --> @gshomelab commented on GitHub (Dec 10, 2025): Getting the same error
GiteaMirror commented 2026-05-03 05:44:16 -05:00
Author
Owner
Copy Link

@Tilvisun commented on GitHub (Dec 10, 2025):

I suspect the new RC version as the reason.

As workaround, you could download the installer script and hardcode the latest normal version:

replace this:
1271e8235e/get-newt.sh (L33-L60)
with:
echo "1.6.0"

<!-- gh-comment-id:3638832068 --> @Tilvisun commented on GitHub (Dec 10, 2025): I suspect the new RC version as the reason. As workaround, you could download the installer script and hardcode the latest normal version: replace this: https://github.com/fosrl/newt/blob/1271e8235e91c2d28b024339ad4092a60a092886/get-newt.sh#L33-L60 with: `echo "1.6.0"`
GiteaMirror commented 2026-05-03 05:44:17 -05:00
Author
Owner
Copy Link

@bbe123 commented on GitHub (Dec 10, 2025):

Same issue here, deb 13

<!-- gh-comment-id:3639243985 --> @bbe123 commented on GitHub (Dec 10, 2025): Same issue here, deb 13
GiteaMirror commented 2026-05-03 05:44:17 -05:00
Author
Owner
Copy Link

@Malith-Rukshan commented on GitHub (Dec 11, 2025):

Since this repository removed the latest version (Release ID) from GitHub, the default installation script no longer works. The script relies on the https://api.github.com/repos/fosrl/newt/releases/latest endpoint to fetch the latest version, which now returns a 404 error.

Image

Workaround:

You can directly specify the version number you want by replacing the get_latest_version() function with:

get_latest_version() {    
    echo "1.6.0" 
}

As mentioned in https://github.com/fosrl/newt/issues/198#issuecomment-3638832068

✅ Alternative Solution:

Alternatively, you can use this modified script that already includes the fix:

curl -fsSL https://gist.github.com/Malith-Rukshan/9b9c8183f8a5e4151bdf1df40a4e5a3b/raw/3c2d9feff840d8ae0449e181e53ca819f2cb3aa9/get-newt.sh | bash
Image
<!-- gh-comment-id:3639751106 --> @Malith-Rukshan commented on GitHub (Dec 11, 2025): Since this repository removed the latest version (Release ID) from GitHub, the default installation script no longer works. The script relies on the `https://api.github.com/repos/fosrl/newt/releases/latest` endpoint to fetch the latest version, which now returns a 404 error. <img width="404" height="206" alt="Image" src="https://github.com/user-attachments/assets/612d287c-8bd7-45fe-bdbb-ff85e7379ef7" /> **Workaround:** You can directly specify the version number you want by replacing the `get_latest_version()` function with: ```shell get_latest_version() { echo "1.6.0" } ``` As mentioned in https://github.com/fosrl/newt/issues/198#issuecomment-3638832068 **✅ Alternative Solution:** Alternatively, you can use [this modified script](https://gist.github.com/Malith-Rukshan/9b9c8183f8a5e4151bdf1df40a4e5a3b) that already includes the fix: ```bash curl -fsSL https://gist.github.com/Malith-Rukshan/9b9c8183f8a5e4151bdf1df40a4e5a3b/raw/3c2d9feff840d8ae0449e181e53ca819f2cb3aa9/get-newt.sh | bash ``` <img width="2512" height="540" alt="Image" src="https://github.com/user-attachments/assets/380701ba-fd33-4d04-b765-d864910f6682" />
GiteaMirror commented 2026-05-03 05:44:18 -05:00
Author
Owner
Copy Link

@mkadrlik commented on GitHub (Dec 11, 2025):

Can confirm that this works; after updating the script and executing it, newt is now properly getting its' config file, and handling connections properly. Much appreciated for the fix!

<!-- gh-comment-id:3639792284 --> @mkadrlik commented on GitHub (Dec 11, 2025): Can confirm that this works; after updating the script and executing it, `newt` is now properly getting its' config file, and handling connections properly. Much appreciated for the fix!
GiteaMirror commented 2026-05-03 05:44:19 -05:00
Author
Owner
Copy Link

@marcschaeferger commented on GitHub (Dec 11, 2025):

@legionGer @HubEight @gshomelab @bbe123

Fixed now. I just verified it in a fresh VM.

@Tilvisun @Malith-Rukshan It’s not related to the RC release, but to the patch release 1.6.1, which was created only to fix the Nix package / failing go test.
When 1.6.1 was published, the latest tag was moved from 1.6.0 to 1.6.1, but the 1.6.1
release was withdrawn in the release progress for a few reasons. We will re-release 1.6.1 soon.

But for now i added the latest tag back to 1.6.0

See #194 for details.

Image
<!-- gh-comment-id:3639986196 --> @marcschaeferger commented on GitHub (Dec 11, 2025): @legionGer @HubEight @gshomelab @bbe123 Fixed now. I just verified it in a fresh VM. @Tilvisun @Malith-Rukshan It’s not related to the RC release, but to the patch release 1.6.1, which was created **only** to fix the Nix package / failing go test. When 1.6.1 was published, the latest tag was moved from 1.6.0 to 1.6.1, but the [1.6.1](https://github.com/fosrl/newt/releases/tag/1.6.1) release was withdrawn in the release progress for a few reasons. We will re-release 1.6.1 soon. But for now i added the latest tag back to 1.6.0 See #194 for details. <img width="687" height="244" alt="Image" src="https://github.com/user-attachments/assets/34433943-4976-436f-9837-56ae545b52c3" />
GiteaMirror commented 2026-05-03 05:44:20 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Dec 11, 2025):

Thank you @marcschaeferger!!

<!-- gh-comment-id:3642566934 --> @oschwartz10612 commented on GitHub (Dec 11, 2025): Thank you @marcschaeferger!!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
dependencies
enhancement
good first issue
help wanted
Improvement
needs investigating
pull-request
Mirrored from GitHub Pull Request
 stale
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/newt#2045
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?