The chromium package in Debian testing broke a few days ago. After I ran “apt-get update” and “apt-get upgrade”, chromium disappeared from my Xfce menu, and the executable was gone from my system. Nothing like that has ever happened to me before. Odd!<\/p>\n
When I tried to re-install it by running “apt-get install chromium”, I got the following error:<\/p>\n
Indeed, there is no package called libudev0 (there is, however, a libudev1, which I already had installed). Mysterious.<\/p>\n Being fairly new to Debian testing, I was at a loss as to what to do. After some googling, I discovered some information that’s useful to users trying to troubleshoot broken packages.<\/p>\n I already knew that Debian has a searchable package database<\/a> on their website. If you search for ‘chromium’<\/a> in the testing distribution, you’ll get to a page<\/a> for it.<\/p>\n What I’d never noticed before were the links on the right-hand side. Every package apparently has its own mailing list archive and QA page.<\/p>\n The QA page isn’t the easily thing in the world to make sense of. I couldn’t find a simple listing of bugs in reverse chronological order, which would let me quickly see the newest bugs filed. The closest thing is the list of all open bugs<\/a>. There is also a dashboard<\/a> page which is vaguely reverse chronological, though it may be sorted by priority; it’s not clear.<\/p>\n In any event, this was good enough. I could see the bug<\/a> for the error message I was getting. Turns out an update had mistakenly built the package for stable, which is why the unmet dependency was coming up.<\/p>\n It’s yet to be fixed, but at least now I know exactly what the problem is.<\/p>\n","protected":false},"excerpt":{"rendered":" The chromium package in Debian testing broke a few days ago. After I ran “apt-get update” and “apt-get upgrade”, chromium disappeared from my Xfce menu, and the executable was gone from my system. Nothing like that has ever happened to me before. Odd! When I tried to re-install it by running “apt-get install chromium”, I … Continue reading “Where To Find Info When Packages Break in Debian Testing”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,9],"tags":[],"class_list":["post-352","post","type-post","status-publish","format-standard","hentry","category-admin","category-software"],"_links":{"self":[{"href":"https:\/\/codefork.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/352","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/codefork.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/codefork.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/codefork.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/codefork.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=352"}],"version-history":[{"count":6,"href":"https:\/\/codefork.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/352\/revisions"}],"predecessor-version":[{"id":375,"href":"https:\/\/codefork.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/352\/revisions\/375"}],"wp:attachment":[{"href":"https:\/\/codefork.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=352"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/codefork.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=352"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/codefork.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=352"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}The following packages have unmet dependencies:
\n chromium : Depends: libudev0 (>= 146) but it is not installable
\nE: Unable to correct problems, you have held broken packages.
\n<\/code><\/p>\n