Your post was moved to a more appropriate category. The topic you posted in was very old and you are unlikely to receive a response there.
For a brief guide on using categories and tags, see here.
Some quick tips:
For general posting guidelines, including using descriptive titles, see here.
When adding terminal or script output, please wrap with code tags by highlighting the text and using either </> in the composer or pressing Ctrl + E on the keyboard.
Note that even though that discussion may appear old, as some packages were added then automatically as they were required dependencies, they may not have been requested manually as nobody realized they were missing.
As those dependencies change over time, we may find ourselves needing to request packages to be added manually, as was the case here.
That documentation only works for Archive Administrators, which are a select group of Ubuntu developers that can add or remove packages from the archive (hence “maintainers/AA” in the URL).
Basically, there’s nothing you can do as a regular user.
This was the right thing to do, but incorrect in filing it against ubuntu-meta as that’s just the metapackages. Best thing to do would have been to file it against fuse requesting addition to the i386-allowlist.
As a member of the bug squad, I went ahead and triaged it by invalidating the ubuntu-meta package as part of the bug but adding fuse to it, subscribed the Archive Admins, and alerted them in their development channel.
Please edit the bug description to make a strong case for 32-bit builds in the bug report, otherwise it will likely not happen.
Probably, but that would only solve it for me. There is quite many other people (and CI systems) who need the package as it is currently needed by some of our tools.