Drop python-influxdb and bigclown-mqtt2influxdb#28049
Drop python-influxdb and bigclown-mqtt2influxdb#28049zpc0 wants to merge 2 commits intoopenwrt:masterfrom
Conversation
It seems this software is no longer maintained. The last upstream commit is 3 years ago, and this software uses obsolete python3-influxdb. Signed-off-by: Yanase Yuki <dev@zpc.st>
This software is no longer maintained. Upstream repository has been locked. Signed-off-by: Yanase Yuki <dev@zpc.st>
Reference: @peci1 Are you using it somehow before going ahead and merging this PR? |
Yes, still using it... What could we do here? Fork the upstream, merge the V2 support and change upstream here to the fork? |
|
While this is a possible solution, I would prefer to avoid it. The forked repository risks becoming outdated if upstream implements further changes, or both repositories could eventually be archived. Implementing InfluxDB2 support as a patch would be a better approach. However, it remains unclear whether |
|
So, it looks like I have some good news. I managed to get in touch with the Hardwario/Bigclown developers, and InfluxDB3 support will be added soon. However, I see that we don't have support for InfluxDB2 in OpenWrt, let alone InfluxDB3. We need to add that. :) So, the blocked label remains for now. I'll take a look at packaging InfluxDB3. |
Very good news! Thank you! |
|
According to hardwario/mqtt2influxdb#27 (comment) (kudos @hubpav), it looks like they now support InfluxDB 3! :) |
4 participants
python-influxdbis no longer maintained, and upstream repo has been archived.bigclown-mqtt2influxdbuses obsoletepython-influxdb, and it seems upstream author does not have interest to move to supported influxdb libs.📦 Package Details
Maintainer: @BKPepe
🧪 Run Testing Details
✅ Formalities