[GH-ISSUE #3907] Could we switch to xtaci/kcp-go and beego/beego?

gitea-mirror commented

2026-05-05 14:00:23 -06:00

Owner

Copy link

Originally created by @yuzibo on GitHub (Dec 30, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3907

Describe the feature request

Hi,
I am packaging the frp into Debian. But there are many packages which were not met.
So may I ask here, could we try to switch fatedier/beego and fatedier/kcp-go to beego/beego&xtaci/kcp-go.
Debian sponsor refers to package the origin upstream than the vendor package. But I am not sure this will reduce your maintainance burden also, like https://github.com/fatedier/beego/pull/1

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @yuzibo on GitHub (Dec 30, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3907 ### Describe the feature request Hi, I am packaging the frp into Debian. But there are many packages which were not met. So may I ask here, could we try to switch fatedier/beego and fatedier/kcp-go to beego/beego&xtaci/kcp-go. Debian sponsor refers to package the origin upstream than the vendor package. But I am not sure this will reduce your maintainance burden also, like https://github.com/fatedier/beego/pull/1 ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [X] Others

gitea-mirror

2026-05-05 14:00:23 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:00:26 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Jan 2, 2024):

Currently, there is no way to directly switch to the original upstream version. The main reason for using the forked version is that the upstream version is not stable enough. There have been unexpected bugs caused by updates in the past. I do not want to invest too much effort in third-party libraries, especially when the current version already fully meets the requirements. Another reason is the need for certain functionalities that the original repository's author may not be willing to support.

https://github.com/fatedier/beego/pull/1 The CVE being fixed here is something we have never used before. We only use the logging library from it and will not make frequent changes due to other content.

Perhaps a better way in the future would be to look for alternative libraries or completely rewrite some of the content, but not now.

@fatedier commented on GitHub (Jan 2, 2024): Currently, there is no way to directly switch to the original upstream version. The main reason for using the forked version is that the upstream version is not stable enough. There have been unexpected bugs caused by updates in the past. I do not want to invest too much effort in third-party libraries, especially when the current version already fully meets the requirements. Another reason is the need for certain functionalities that the original repository's author may not be willing to support. https://github.com/fatedier/beego/pull/1 The CVE being fixed here is something we have never used before. We only use the logging library from it and will not make frequent changes due to other content. Perhaps a better way in the future would be to look for alternative libraries or completely rewrite some of the content, but not now.

gitea-mirror commented

2026-05-05 14:00:27 -06:00

Author

Owner

Copy link

@yuzibo commented on GitHub (Jan 10, 2024):

Thanks for clarifying.
This is reason enough to convince them to use vendor libraries for the project.
btw, please feel free to close the issue if this is not on your plan or to-do list.:)

@yuzibo commented on GitHub (Jan 10, 2024): Thanks for clarifying. This is reason enough to convince them to use vendor libraries for the project. btw, please feel free to close the issue if this is not on your plan or to-do list.:)

gitea-mirror commented

2026-05-05 14:00:28 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Feb 1, 2024):

Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Feb 1, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror commented

2026-05-05 14:00:29 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Feb 20, 2024):

https://github.com/fatedier/frp/pull/4009 The kcp-go package has been switched to the original upstream repository.

@fatedier commented on GitHub (Feb 20, 2024): https://github.com/fatedier/frp/pull/4009 The kcp-go package has been switched to the original upstream repository.

gitea-mirror commented

2026-05-05 14:00:30 -06:00

Author

Owner

Copy link

@yuzibo commented on GitHub (Feb 28, 2024):

#4009 The kcp-go package has been switched to the original upstream repository.

Oh, many thanks. This is really to reduce package work to Debian.

@yuzibo commented on GitHub (Feb 28, 2024): > #4009 The kcp-go package has been switched to the original upstream repository. Oh, many thanks. This is really to reduce package work to Debian.

No Branch/Tag specified