extension: build(deps): bump setuptools from 80.10.2 to 82.0.1

[dependabot]

Summary

Bumps setuptools from 80.10.2 to 82.0.0 and fixes the resulting U-Boot build breakage.

setuptools 82.0.0 removed the deprecated pkg_resources module. U-Boot's binman (tools/binman/control.py) uses import pkg_resources for reading package resources in all versions prior to v2025.10. The upstream fix landed in U-Boot v2025.10 (commit 538719cb6a), but most U-Boot versions used by Armbian (v2022.07 through v2025.04) are affected.

Approach: runtime extension instead of patch files

A new extension uboot-binman-fix-pkg-resources patches tools/binman/control.py at build time via the pre_config_uboot_target hook. This approach was chosen over adding patch files to BOOTPATCHDIR because:

• BOOTPATCHDIR varies across ~15 board families
• control.py differs between U-Boot versions (would need 2+ patch variants)
• A single idempotent extension covers ALL versions in one file
• The pre_config_uboot_target hook is already included in artifact hash computation (H-part)

What the extension does

1. Checks if tools/binman/control.py exists and contains import pkg_resources (idempotency)
2. Patches the file via inline Python script:
   • Old U-Boot (<=v2023.x): no importlib.resources present — adds try/except import block (matching upstream pattern)
   • Intermediate U-Boot (v2024.01+): has both imports — aliases import importlib.resources as importlib_resources, updates existing usage
   • New U-Boot (>=v2025.10): no import pkg_resources — extension is a no-op
3. Replacements:
   • pkg_resources.resource_string(__name__, X) → importlib_resources.files(__package__).joinpath(X).read_bytes()
   • pkg_resources.resource_listdir(__name__, X) → [r.name for r in importlib_resources.files(__package__).joinpath(X).iterdir() if r.is_file()]

Self-removal

Can be removed once all BOOTBRANCH versions in Armbian are >= v2025.10.

Test results

All three code paths verified with real builds on an ARM64 host:

Code path	Board	U-Boot	Patch applied	Build result
Old (only pkg_resources)	odroidc4 (meson-sm1)	v2022.07	Yes — try/except block added	OK
Intermediate (both imports)	tritium-h5 (sunxi/allwinner)	v2024.01	Yes — alias added	OK
No-op (already migrated)	odroidm2 (rk3588)	v2025.10	No (skipped)	OK

Key files

• extensions/uboot-binman-fix-pkg-resources.sh — the extension
• lib/functions/configuration/main-config.sh — enable_extension call
• lib/functions/compilation/uboot.sh:94-98 — pre_config_uboot_target hook invocation (cwd = U-Boot sources)
• lib/functions/artifacts/artifact-uboot.sh:74-79 — hook hashing for artifact versioning

Summary by CodeRabbit

Release Notes

• Chores
  • Updated setuptools dependency to version 82.0.0
  • Ensured U-Boot support remains compatible with setuptools versions 82 and later

[iav]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes address pkg_resources deprecation in setuptools 82+ by introducing a new shell script that patches U-Boot's binman control.py to migrate from pkg_resources to importlib.resources. Configuration enablement is added to activate this patch, and setuptools is upgraded to version 82.0.0.

Changes

Cohort / File(s)	Summary
U-Boot Binman Compatibility Fix extensions/uboot-binman-fix-pkg-resources.sh	New shell script that patches binman control.py to migrate from deprecated pkg_resources to importlib.resources API, with compatibility handling for varying U-Boot versions.
Configuration & Dependency Updates lib/functions/configuration/main-config.sh, requirements.txt	Enables the binman pkg_resources fix in the configuration initialization chain and bumps setuptools from 80.10.2 to 82.0.0.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 A hop and a skip, we've patched it just right,
From pkg_resources to importlib—what a delight!
Our setuptools upgraded, version eighty-two,
U-Boot's binman dancing in compatibility true.

🚥 Pre-merge checks | ✅ 2 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Merge Conflict Detection	⚠️ Warning	❌ Merge conflicts detected (2 files): ⚔️ lib/functions/configuration/main-config.sh (content) ⚔️ requirements.txt (content) These conflicts must be resolved before merging into main.	Resolve conflicts locally and push changes to this branch.
Title check	⚠️ Warning	The title focuses on the setuptools version bump but omits the critical runtime extension that fixes U-Boot incompatibility caused by that upgrade.	Revise the title to reflect both the setuptools upgrade and the new uboot-binman-fix-pkg-resources extension that enables the change, e.g., 'chore: upgrade setuptools to 82.0.0 and add U-Boot binman pkg_resources compatibility fix'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependabot/pip/setuptools-82.0.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

Verify each finding against the current code and only fix it if needed.


In `@extensions/uboot-binman-fix-pkg-resources.sh`:
- Around line 33-34: The current re.sub call that removes the import line is too
strict and can miss variants like trailing whitespace or comments; update the
re.sub invocation that operates on the content variable so its pattern allows
optional leading whitespace, matches the import keyword and pkg_resources as a
whole word, permits any trailing characters (comments/whitespace) up to the line
ending (including optional CR), and still uses the MULTILINE flag — replace the
existing strict pattern in the re.sub call with a more resilient line-matching
pattern that covers these cases.

[rpardini]

Hmm -- what is the point of the major 80 -> 82 upgrade to begin with? Yes, we can work-around it, but... why?

[iav]

Right now, urgent — there is no point.
In the long run, getting stuck on the "latest acceptable version" of something sooner or later becomes a source of security problems, found errors and/or compatibility with something else that we need to update, but the fixed version does not work.
And then it may turn out that now it is much more difficult to upgrade than it was before, because a lot of places have already accumulated a big difference, and no one has simply tested or created such upgrade paths anywhere.

[iav]

Let me rephrase it briefly: this will prevent the formation of "technical debt" and will eliminate the need to start thinking about the fact that we have dependencies somewhere that require special treatment.

[dependabot]

A newer version of setuptools exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[igorpecovnik]

@iav How reliable is this fix?

[iav]

It does nothing if tools/binman/control.py doesn't exist or doesn't contain import pkg_resources.
The replacement code (importlib.resources.files()) is exactly what upstream U-Boot adopted in commit 538719cb6a (v2025.10) u-boot/u-boot@538719cb6a

Tested on all 3 code paths with real builds:

• Old U-Boot (v2022.07, odroidc4)
• Intermediate U-Boot (v2024.01, tritium-h5)
• New U-Boot (v2025.10, odroidm2) — no-op

It only touches tools/binman/control.py and only replaces two pkg_resources API calls (resource_string and resource_listdir) which are the only ones binman uses.

It will be possible to simply throw away after all BOOTBRANCH versions in Armbian reach v2025.10+ 😆

Tested on all 3 code paths with real builds:

• Old U-Boot (v2022.07, odroidc4)
• Intermediate U-Boot (v2024.01, tritium-h5)
• New U-Boot (v2025.10, odroidm2) — no-op

I hope it will be reliable enough.