Please note, this is not a bugreport, more a question aimed for oimprovement. I am very glad, that a package exists at the moment at all (thank you very much for packaging it!).
It is just, that it got in my mind, that the package is not beeing upgraded, but the script is.

If this is not intended for the package or too much work and efforts or just too difficult, I would be happy for a little information, just to know.

Again: Thank you very much for the package!!!

Happy hacking!

Hans

Heya! I've checked our package and the current version is 6.28, which is exactly the same as the latest release in fluxion's github page. Maybe the script you mention downloads the source code that is still not officially released.

So my idea: May it be possible to creaste an automatism, which is packaging a new version, as soon as it is available? Doing so we would have always the newest version in the repo.
We already do that. We have a file called debian/watch in each package that is in charge of checking updates regularly.

I'm closing this report as it's not a bug. But feel free to reopen it

See https://github.com/FluxionNetwork/fluxion/releases as well which is at 6.28 from March this year so all fine it seems.

I see. Hmm, that is strange, because, when I am starting fluxion, which is installed by the script, This is strange, because when you look here https://github.com/FluxionNetwork/fluxion, you can see, it is version 2.30 since a month.

However, in the opposite you may be correct, the official release might be the correst one and the github source not. I think, the script is using the github source, not the release tree. Or sopmthing else is strange.

Maybe we should just close this issue and wait, what time brings by just keeping an eye on it from time to time?