knxd: bump to version 0.14.75

[tru7]

📦 Package Details

Maintainer: @tru7
_{(You can find this by checking the history of the package Makefile.)}

Description:

new upstream release 0.14.75

---

🧪 Run Testing Details

• OpenWrt Version: snapshot
• OpenWrt Target/Subtarget: ath79/generic, ramips/mt7620a
• OpenWrt Device: tplink_archer-c7-v4

---

✅ Formalities

• I have reviewed the CONTRIBUTING.md file for detailed contributing guidelines.

If your PR contains a patch:

• It can be applied using git am
• It has been refreshed to avoid offsets, fuzzes, etc., using

  make package/<your-package>/refresh V=s

• It is structured in a way that it is potentially upstreamable
  _{(e.g., subject line, commit description, etc.)
  We must try to upstream patches to reduce maintenance burden.}

[tru7]

@commodo @hnyman @neheb
Sorry to ping you - I need some expert help here, please.
All Builds (suddenly) fail on "Dirty patches detected, please refresh and review the diff". These patches have been used since years and never made problems. In the 0100-version.patch I need to change the version number - that's all I change on patches.
I also don't understand the mechanism how the patches are applied within these Builds and in what aspect there are dirty.

[hnyman]

Just do make package/knxd/refresh V=s . And see what changes. (Possibly a make clean for that package needed earlier)

Likely it is just about missing context at the @@ line or something like that.

[tru7]

Thank you @hnyman - you are right - unfortunately I overlooked a change in the upstream file after the @@
I must have overlooked a hint in my local environment - and when I tried to reproduce I didn't realize that the patch was obviously changed.
Now I tried to update my commit but I guess I messed it up. The content is still OK but there are now two commits. I'm just too unexperienced to resolve this in a clean way myself.
Can that still be resolved or should I close the PR and start over?

[hnyman]

It is actually pretty easy to fix with git rebase. (Squash the two commits)
Read the advice from CONTRIBUTING.md