Well, so i just did a test where i upload my custom made deb through the web ui and that actually just works, which explains why i felt like i have seen this working somehow.
Not entirely sure if it’s related to this bug: Upload deb package through hammer results in empty/invalid packages in repo - #9 by Macley
but it seems uploading the same deb through the api gives a different result then uploading it through the UI.
Infact, uploading it through the UI actually fixes the:
N: Skipping acquire of configured file ‘all/binary-amd64/Packages’ as repository ‘katello://server.foreman.lan/pulp/deb/acme/Production/CV_UBUNTU_22-04/custom/Ubuntu_22-04/Today_I_Patched_Package default InRelease’ doesn’t support architecture ‘amd64’
May i ask if you also experience the same behavior on your side?