Update from debian/trixie for apertis/v2025pre

assigned to @not_a_robot

added 204 commits

• 09c04d81...429d4442 - 201 commits from branch apertis/v2025pre
• 1b6a4406 - Merge remote-tracking branch 'origin/apertis/v2025pre' into proposed-updates/debian/trixie/429d4442
• 617b324a - d/patches: Refresh apertis patches
• 054d0f4c - Release u-boot version 2024.01+dfsg-5+apertis1

Compare with previous version

added 1 commit

• 740ff62b - Refresh the automatically detected licensing information

Compare with previous version

added 3 commits

• b994f5f7 - Merge remote-tracking branch 'origin/apertis/v2025pre' into proposed-updates/debian/trixie/429d4442
• 112c4826 - d/patches: Refresh apertis patches
• e0ed5cd2 - Release u-boot version 2024.01+dfsg-5+apertis1

Compare with previous version

added 1 commit

• 85e22f99 - Refresh the automatically detected licensing information

Compare with previous version

mentioned in merge request infrastructure/apertis-image-recipes!684 (merged)

added 3 commits

• 292da4ca - Merge remote-tracking branch 'origin/apertis/v2025pre' into proposed-updates/debian/trixie/429d4442
• 41cfbe30 - d/patches: Refresh apertis patches
• 9e52c170 - Release u-boot version 2024.01+dfsg-5+apertis1

Compare with previous version

added 1 commit

• e3ca4132 - Refresh the automatically detected licensing information

Compare with previous version

@martyn I understand that you have tested this on R-Car and RPi4 both, APT and OSTree images, and you didn't find any regression. The only issue is infrastructure/apertis-issues#644 (closed), but that is already present in v2024 and v2025pre. If that is correct, I am fine about merging this change.

approved this merge request

mentioned in merge request !119 (merged)

resolved all threads

merged