<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/125352>125352</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            No i386 packages in APT repository for Ubuntu for LLVM 19
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            new issue
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          eloj
      </td>
    </tr>
</table>

<pre>
    I hesitate to open this linux packaging issue, but I found #113438 which is similar so here we go.

The Ubuntu LLVM repos (at least for Noble) lack i386 support.

```console
$ cat /etc/apt/sources.list.d/llvm-clang.list 
deb http://apt.llvm.org/noble/ llvm-toolchain-noble-19 main
$ apt update
...
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://apt.llvm.org/noble llvm-toolchain-noble-19 InRelease' doesn't support architecture 'i386'
```

This recently caused the Linux Mint 22.1 Xia[^ver] automatic updater ("Update Manager") to uninstall Steam from my system.

[^ver]: which is derived from Ubuntu 24.04 Noble.

This is because they're releasing a suite of new mesa packages (mesa=24.2.8-1ubuntu1~24.04.1), multiple of which depend on `libllvm19`. This probably wouldn't be a problem, if it wasn't for the fact that Steam infamously depends on a lot of 32-bit libraries.

I don't have the whole dependency chain, but one specific example that my system pointed to after being broken was "mesa-libgallium:i386 : Depends: libllvm19:i386 but it is not installable"

The way this was resolved by `apt` is to basically uninstall 40'ish packages, including 'steam-libs', and with it went Steam.

Unless I'm wrong in my analysis, the only way forward is for the repos to have i386 packages, or for me to stop using them, because having them enabled will likely continue to break Steam/mesa going forward. I'm just glad my whole desktop environment didn't go poof[^sec].

**Obviously this isn't the fault of the LLVM project**, but I wanted to make the greater cosmos aware of this interaction.

[^sec]: Seems to me a package maintainer with bad intentions could really do some damage!
</pre>
<img width="1" height="1" alt="" src="http://email.email.llvm.org/o/eJyEVk2P2zgS_TX0pdCCTMlfBx96t9dAA0k22CSLvZaoksSYIrX8sKPL_PZBUXJ35zAYwAebchVfvfeqShiC7i3RWez-IXYvG0xxcP5Mxv3cNK6dz68wUNARI0F04CayEAcdwGibfsGE6oq9tj3oEBIJ-U9oUoRX6FyyLQhZbbdVXR3hPmg1gA4Q9KgNeggOBvIEd4LeFaJ8FuXz94HgR5NsTPDp038_g6fJBRDyiBEMYYjQOQ9fXGNIyBMYVFfQ1XEPIU2T83FNI_bl8lHOBmeIj2QNCiMIeaGohLzgFIW8BJe8olAYHWLRCnkx5jY-KYO2z2cgyueWGhhinET1LORlCS34f4XzvZAXu8C5QI6Nzhk1oLZP-fxpe4IRtV0h4BQhTS1GxlQUjPeLqJ7h21VPE7OI6v9JewLXgXK2033y1EKnDYGQh5xJXhpt0c9PXLmQl69ZAgpCHgDDwpmOzs8c8bfA_xL1q_0PMefEeVtHwQp5iA-mAb0adCQVk8_QFjCHj-w_NNUMSpGNZgaFKVALcSD4lA30WdsIUhZb-J_G7MF_3ciL3Qtgim7EqNXKmGcjCCl_5F_wGS325IWUbIXoIFltQ0Rj4FskHKHzboRxhjCHSOPDGh9uYOLfbNmS1zemmqNWD8q6KOvFbsWHYnSAhnIhXMcs5MET-ExWlhBC0jFLaOkOIwVc24Syl_lAVC-yLmRxfNqmfNf2j3xZsRXyxE00JhP1ZHKWBWNLE9kWnAWxL41uWLftSezLAjKqybsGGzPD3SXTLmI1BJgfGBo5q-5AR7jjqiU3EyvRoYoQB4wrc9p2OLoUzLzeGvhaBOMi46nkU6MjGN149JrCys0rtG7JO-AtUwP3wRlac5BVM2SPPYaEswRhIqU7rYB-4cj1ZhhvqsHktI1sGAfYsQcaYo4b765kuRIQUjKjT0Y3PRqj0yiq5zwUWN-XBT9_fedsfc4YdGQ5rYuwmgdzM8v3eXTHeRl499xcwRm2STOzDDxE9iVniA4aDFqhMfMHJ9Ylt0YY3gyQVbDKpJbLEPIQmHEGz_3LT9G2cNdxyEqRXTVZOf5hDYUArzwL4O4dz13LdKFFMwed8zPzzrITcGaN7-hbxviQe5mq0S06ZSo-wnM-_3PM8z5EN0HKvo7DYqKH9we8PY6BLPPGwI0Bo6_Ere5s1DblNI0nvC6VCHnJLdE7jl7hFWtJP1OI0BtsuaaHe8KVQZC9ae_syJS0ejV472Byrlu6OpASu5dHo0v-_Lu56cXIcencJWwxfTLZznkW8baZvPtJKi6R75vsjg8HjnhdfN17ygNJuTC6AHjHZWQvl9hIHlXUzv42dBZ4edoTjVmAMffnwn1eExG1Jb_o32Cbc1nOFEBxW4On7LDWQXAjQYsj9iTkdtOeq_ZUnXBD5-2hOtbV7rirN8N5r_bHWu27puzqnapqdWz3paxOHe0PXbtvNvosS7krZbndHnflri7UrqxkW8oOa3VoylbUJY2ozdvq2ORVf97KXbWTG4MNmZBfH6Tkgbe-CEh-m_DnvF6a1AdRl7xRw3uaqKOh8xf3uwXZ0M9fv3_cY2zHdSTz1yzW9rRJ3px5v4W3BdfrOKSmUG5cV_ljo79Je8nogpCXFf7tLP8MAAD__8hF_po">