![]() I would ask apt where each of those updates come from before proceeding, with apt policy package-name. If one or two upgradable packages were listed, it could mean that Ubuntu happened to release some updates while I was working, which is normal. Since I already did an upgrade before making any changes, I don't expect to see any upgradable packages listed here. ![]() That shows me what a system-wide package upgrade would do, without actually doing it. That refreshes the package database, so my Ubuntu system now knows about everything in the Debian archives that I added. I chose the more conservative approach just to be cautious.) sudo apt update I could also have pinned all of the Debian repo at priority 100 that would make any Debian-only dependencies eligible for automatic updates, effectively treating the Debian repo like Ubuntu Backports in manual install mode. (I suppose I could have assigned a much higher priority to Debian's Chromium packages if I needed them to override Ubuntu's, but since they use different package names, no overriding is necessary. The second stanza assigns a very low priority to all other Debian packages, so they will only be automatically installed or updated if necessary to satisfy a dependency. This is called apt pinning, and is described in the apt_preferences manual. The first stanza assigns a below-normal priority to Debian Chromium packages just high enough to allow them to be manually installed and automatically updated, but not high enough to be preferred over Ubuntu packages. It may already be on your system, too, but if not, you should install it: sudo apt install debian-archive-keyringĬreate an /etc/apt/preferences.d/debian-chromium file containing: Explanation: Allow installing chromium from the debian repo.Įxplanation: Avoid other packages from the debian repo. Note: The /usr/share/keyrings/debian-archive-keyring.gpg file referenced above, along with several other Debian keyring files, are already present on my Ubuntu system thanks to the debian-archive-keyring package. However, we're going to add some rules to avoid this problem. This is ordinarily a bad idea, because you don't want hundreds of random Ubuntu packages being replaced with Debian versions, which would very likely break your system. That tells apt to look for packages not only in the Ubuntu archives, but also in the Debian stable archives. That just makes sure that the files I create will be readable by everyone, including the system.Ĭreate an /etc/apt//debian-stable.list file containing: deb stable mainĭeb-src stable mainĭeb stable-security mainĭeb-src stable-security mainĭeb stable-updates mainĭeb-src stable-updates main (You can leave out the chromium-chromedriver part if that package isn't installed on your system.) umask 22 sudo apt purge chromium-browser chromium-chromedriverīye bye, fake Chromium packages. snap remove chromiumīye bye, annoying snap. That brings all my already-installed Ubuntu packages up to date, so it will be easier to see how upgrades are affected after I make my changes. Here's what I did on Ubuntu 19.10: sudo apt update & sudo apt upgrade If you break something, it's your own fault. Obligatory Warning: This is entirely unsupported and could conceivably cause problems either immediately or in the future. There is no need to risk installing software from some random source or telling your system to trust a PPA. This makes sense from a security perspective, since Debian is where Ubuntu already gets most of its packages, and is a very well known high-profile project. We can configure Ubuntu to get it from there, and continue to receive timely security updates along with all of our other OS updates. I am leaving this post in place because it describes general techniques for cherry picking packages from debian-compatible repos for use on different distributions or releases.ĭebian still maintains Chromium as a regular package in their APT repository. Ubuntu 20.04 users will probably still get good results by replacing stable with buster in the file described below, for as long as Debian continues to support their Buster release. ![]() ![]() The exact steps described here might not work on them. Ubuntu and Debian both got new releases since I originally wrote this article.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |