I've been putting off the request to modernization request for customized (personally added) repositories for some time. With a few extra minutes to spare, I read up on whether the act of non-modernized sources will affect the system moving forward or not. Frankly, it doesn't affect the system but to get rid of that annoyance every time I run updates via the terminal, I finally did it sometime last week. This week, while running updates, I'm presented with a new issue. Some of the entries such as Google Chrome and virtualbox now throw out some warning messages of not supporting i386. I'm certain Virtualbox did specify in the source file
However, it is exempted or removed with the modernized version and I've tried entering it on the first and second line (each try done separately) with NO success. Before modernization, it was on the uri line
(There's no repository for Plucky. Uses the same deb package for Oracular). Apt throws a warning that there's malformed entry and won't update unless I remove the addition.
Question is, how, with the new modernization of the sources list can the entry be fixed? Here's the modernized version of Virtualbox (Chrome is almost identical of course)
Code:
deb [arch=amd64]
Code:
deb [arch=amd64 signed-by=/usr/share/keyrings/oracle-virtualbox-2016.gpg] https://download.virtualbox.org/virtualbox/debian oracular contrib
Question is, how, with the new modernization of the sources list can the entry be fixed? Here's the modernized version of Virtualbox (Chrome is almost identical of course)
Types: deb
URIs: https://download.virtualbox.org/virtualbox/debian/
Suites: oracular
Components: contrib
Signed-By:/usr/share/keyrings/oracle-virtualbox-2016.gpg
URIs: https://download.virtualbox.org/virtualbox/debian/
Suites: oracular
Components: contrib
Signed-By:/usr/share/keyrings/oracle-virtualbox-2016.gpg
Comment