Gluon: Gluon v2019.1.3 Tracking Issue

Created on 22 Aug 2020  路  15Comments  路  Source: freifunk-gluon/gluon

The last release to v2019.1.x has been in Feb. 2020, we've backported a few fixes from master and updated it's 18.06 base. I think we can do roughly one more release after this, because v2019.1.x will be EOL after 2020.

Release-Notes: https://md.darmstadt.ccc.de/gluon-v2019.1.3

279fb88c Revert "tplink-safeloader: expand support list for TP-Link CPE210 v3"
ddb54248 Revert "kernel: mtd: add support for EN25QH64 in spi-nor.c"
46482156 refresh patches
f0a2da5b modules: update routing
b863bb89 fastd: fix buffer leak when receiving invalid packets
845d8ebd Merge pull request #2136 from SmithChart/v2019.1.x/cpe210-3.20
1268fda2 tplink-safeloader: expand support list for TP-Link CPE210 v3
ee4ec4da kernel: mtd: add support for EN25QH64 in spi-nor.c
c8d708e5 Merge pull request #2132 from freifunk-gluon/v2019.1.x-openwrt-bump-build-fix
e4241c0c patches: packages: perl: backport GCC10 build fix
0b45624b patches: refresh routing
7afbba32 modules: update OpenWrt
14501b41 modules: update routing
ff0c72f7 modules: update packages
d05e22fc modules: update OpenWrt
8bd179a6 modules: update routing
c2f0d9e0 modules: update packages
ab9c0ad0 module: update OpenWrt
3cd3bf0f gluon-core: fix handling of 'disabled' site.conf attributes for mesh interfaces
69badbc2 gluon-config-mode-outdoor, gluon-web-wifi-config: commit network config
2e1abda6 patches: refresh openwrt & packages
2b142233 mac80211: ath10k: increase rx buffer size to 2048
45ac73a5 gluon-web-model: update inputs on form reset
70990f67 gluon-respondd: allow queries from extra_prefix6
52b3ec7b modules: update routing
c9c97778 modules: update packages
b1cdebd6 modules: update OpenWrt
12221d44 gluon-mesh-vpn-tunneldigger: only search for exactly the tunneldigger binary in watchdog (#1953)

pull request:

2137

All 15 comments

i've asked for testing the branch on the forum, no feedback yet, i think we should wait for feedback as we ourselves don't test the branch, especially not with IBSS or batman-adv compat14 (legacy)

Poking a few v2019.1.x communites. Maybe one of you can testdrive the current v2019.1.x state?

  • Aachen: @mmalte @yayachiken
  • Bremen: @genofire @corny @SimJoSt @mablae
  • Rhein-Neckar: @herbetom
  • Braunschweig: @SmithChart

image

is there already a git tag? Or should i build with commitid? (maybe this ff0c72f74ba3771499b9cab2966524334d627420)

@genofire The current HEAD you mentioned is what should be tested, yes.

is there already a git tag? Or should i build with commitid? (maybe this ff0c72f)

it would be better to have testing before tagging it ;) and the gluon devs dont have the need and resources to test this old branch with deprecated things like IBSS or batman-adv-legacy (compat14), therefore @mweinelt asked affected communities to test the branch before tagging it.

While Rhein-Neckar currently uses v2019.1.2 as stable it's not because of stuff like IBSS or batman-adv-legac but rather that we haven't decided yet if we want to upgrade tiny devices to 2020.x (but lately I tend to update to 2020.x in the near future, because tiny devices seem to work reasonably well with it).
We currently do have 32 nodes on 3cd3bf0f86b541694597d1f533b9169fe6ec89c0 which seem to run fine. But that's of course not the current HEAD https://github.com/freifunk-gluon/gluon/compare/3cd3bf0f86b541694597d1f533b9169fe6ec89c0...v2019.1.x

but lately I tend to update to 2020.x in the near future, because tiny devices seem to work reasonably well with it).

in this case we recommend to go directly to v2020.2.x and skip v2020.1.x, as there are some improvements also for tiny devices and v2020.1.x will be EOL soon because there is no known reason at all to use it anymore.

i think we should bump this again.
for the current state someone reported this as working with 802.11s and batman-adv compat14

It's a never ending circle :laughing:

It's a never ending circle laughing

about bumping/testing? no, there was just a security fix added recently, and no one tested IBSS so far anyway.

oh, okay. But i don't really have hope that somebody will test ibss anytime soon. The communities that haven't changed yet are probably not the ones who care about using the latest patches anyway. :shrug:

maybe, but that's the reason this branch is still supported, IBSS and batman-adv compat14, so these are the things which definitely need to work in this branch ;)

the v2019.1.x branch has been updated again, including a fix for building the branch on systems with GCC10

Poking a few v2019.1.x communites. Maybe one of you can testdrive the current v2019.1.x state?

* Aachen: @mmalte @yayachiken

* Bremen: @genofire @corny @SimJoSt @mablae

* Rhein-Neckar: @herbetom

* Braunschweig: @SmithChart

image

sorry for the wait. It seems I have to upgrade my mail-sorting workflow so that mentions don't go into the pile of all the other Github Notifications.

Today I finally found the time to bring my continous testing up again. Tests for b863bb89e7d3c7bb9efc7c94cf61bc3c17660089 look good on ar71xx-tiny for our community (BATMAN_IV_LEGACY and 11s-mesh).

release tag and release announce mail done, ticket close.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

lephisto picture lephisto  路  5Comments

lemoer picture lemoer  路  3Comments

lcb01a picture lcb01a  路  3Comments

rubo77 picture rubo77  路  5Comments

mweinelt picture mweinelt  路  3Comments