ChrisTitusTech / linutil

Chris Titus Tech's Linux Toolbox - Linutil is a distro-agnostic toolbox designed to simplify everyday Linux tasks.
https://christitus.com
MIT License
2.77k stars 226 forks source link

apt error after installing vscodium on Debian Bookworm #870

Open bsmith149810 opened 3 weeks ago

bsmith149810 commented 3 weeks ago

Describe the bug

A clear and concise description of what the bug is. Updating apt package manager ends with error message after installing VScodium via linutl.

To Reproduce

Install VScodium from linutil's interface. Using Debian 12 Bookworm open bash terminal. run sudo apt update Command ends with error message:

N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://download.vscodium.com/debs vscodium InRelease' doesn't support architecture 'i386'

To Resolve

Using Debian 12 Bookworm open bash terminal run sudo apt edit-sources vscodium.list

Original /etc/apt/sources.list.d/vscodium.list opens:

deb [signed-by=/usr/share/keyrings/vscodium-archive-keyring.gpg] https://download.vscodium.com/debs vscodium main

add "arch=amd64" at beginning & inside of square brackets:

deb [arch=amd64 signed-by=/usr/share/keyrings/vscodium-archive-keyring.gpg] https://download.vscodium.com/debs vscodium main

Save and exit vscodium.list.

Additional context

Apologies if I missed this being resolved elsewhere or if the issue is outside of linutil. I'm not a developer at all, and this is the first bug report I've sent after Three years of using Linux so this may be completely wrong, but it looks like changing line 11 in /applications/Developer-tools/vscodium-setup.sh could resolve it.

See https://askubuntu.com/questions/741410/skipping-acquire-of-configured-file-main-binary-i386-packages-as-repository-x for more detailed solutions.

cartercanedy commented 3 weeks ago

In a terminal, run uname -a and add a comment with the output, please.

cartercanedy commented 3 weeks ago

Just read your fix. Please submit a PR with your change. If you're not familiar with the contributing workflow on GitHub, though, either I or one of the other maintainers can submit the fix for you. Thanks for the bug report

adamperkowski commented 3 weeks ago

If you're not familiar with the contributing workflow on GitHub

... then read the Contributing Guidelines :)