Skip to content

Conversation

@molBR
Copy link
Contributor

@molBR molBR commented Oct 18, 2025

  • Motivation *
    This PR is made because Netdata used has a memory leak bug and affects currently projects that use caprover latest versions

Netdata memory leak issue:
netdata/netdata#12839

  • Upgrade Netdata from v1.34.1 to v1.47.5
  • Migrate from Debian Stretch (EOL) to Debian Bullseye
  • Update repository URLs to use current Debian mirrors
  • Replace Python 2 dependencies with Python 3 equivalents
  • Add bullseye-updates repository for better package availability

Debian Stretch reached end-of-life and its repositories are no longer available, causing build failures. This update ensures the build process works with currently supported Debian releases.

Generated by Coding Giang Codes - molBR

- Upgrade Netdata from v1.34.1 to v1.47.5
- Migrate from Debian Stretch (EOL) to Debian Bullseye
- Update repository URLs to use current Debian mirrors
- Replace Python 2 dependencies with Python 3 equivalents
- Add bullseye-updates repository for better package availability

Debian Stretch reached end-of-life and its repositories are no longer available, causing build failures. This update ensures the build process works with currently supported Debian releases.

Generated by Coding Giang Codes - molBR
@githubsaturn
Copy link
Contributor

Thanks! Just to confirm, have you tested these changes?

@molBR
Copy link
Contributor Author

molBR commented Oct 18, 2025

Yes, do you need me to provide any report?

@githubsaturn
Copy link
Contributor

As long as it's tested and confirmed to.be working, we're good! Thanks!

@githubsaturn githubsaturn merged commit 271cec0 into caprover:master Oct 19, 2025
@githubsaturn
Copy link
Contributor

It looks like the build is failing. Can you please check the failure and suggest a fix?

@githubsaturn
Copy link
Contributor

@molBR
Copy link
Contributor Author

molBR commented Oct 20, 2025

Hey, I had to change A LOT of things, used static binaries. Didnt want to, but couldnt resolve it without really changing a lot.

#11

@molBR
Copy link
Contributor Author

molBR commented Oct 20, 2025

Also added a issue, I don't know if what I did is somehow wrong in you guys perspective

#10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants