The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped automatically by the mailing list software.
--- Begin Message ---On Friday, January 17th, 2025 at 11:26, Felix Baumann via openwrt-devel <openwrt-devel@lists.openwrt.org> wrote: > Does apk give packages some form of ID so renames don't deter ASU from > choosing the right package for future release updates? Ah, sorry, I misunderstood. No, I haven't seen anything in apk that would give us extra info we need when packages are renamed, so we'll have to continue handling them manually in ASU itself. Here's what we're doing right now, the info in the 'package_changes_list' gets passed to the ASU clients (auc, owut, LuCI app) and they do the replacements before sending the build request back to the ASU server. https://github.com/openwrt/asu/blob/main/asu/config.py#L6 But, a lot of renamings are completely transparent because ASU generally only deals with top-level packages. If you rename a package that's installed as a dependency of one of the top-level ones, the ASU server never even sees it, so the replacement "just happens".
--- End Message ---
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
