SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have slackware64-current installed and this morning I installed chrome based on the slackbuild that is in /extra. This installed chrome 45.0.2454.93. I then ran slackpkg upgrade-all and was prompted to upgrade chrome to version 39.0.2171.65. See picture here: https://www.flickr.com/gp/123978416@N06/5yi1rg. Seems I need to add chrome to the /etc/slackpkg/blacklist file now, but I'm curious as to why it thinks that version 39.0.2171.65 is newer than 45.0.2454.93?
Last edited by bassplayer69; 09-19-2015 at 07:56 AM.
Slackware itself does not have Google Chrome 39.0.2171.65. The screenshot shows that you have the Slacky repository for Slackware 14.1 enabled in slackpkg with slackpkg+
You built your own Chrome now, this means you need to blacklist the Chrome package because otherwise it will be pulled from the slacky repository every time you run "slackpkg upgrade-all".
Slackpkg doesn't care for the version number at all. You are using slackpkg+ with "slacky" among the repositories listed, and and a package in any repository listed will have priority over a custom package bearing the same name. So yes, blacklist that package.
EDIT. Too late, sorry.
Last edited by Didier Spaier; 09-19-2015 at 07:51 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
