Aren't CB repos frozen from one release to the other?Got an update in today:apt-cache policy openssl
Candidate: 1.0.1e-2+deb7u6https://security-tracker.debian.org/tra … -2014-0160
Have had this one for a couple of days, figured it would have cleared up by now, after a yum clean all:
Error: Package: python3-sleekxmpp-1.1.11-2.fc18.noarch (updates)
There is apparently no python3-dns package in the main repos, but it is in testing so either it's a spurious dependency or it's supposed to be in the release re
I've just installed the latest version of #! and have run an update.Some of the packages are a little old such as chromium. I've been looking through some of the postings in the forum trying to figure out if I can switch to using the Mint LMDE repos in place of the standard #! repos.Will this work? I'm thinking that they are both Debian based??Thanks
Anyone else see this error when executing KGet?Plugin loader could not load the plugin: kget_bittorrentfactory.This just started happening today after an update.I know that libktorrent was updated today.Should I report this error.Will rolling back this update fix the error until the update is fixed?
hiI've been looking everywhere without finding an answer, so let me try to get some help...I'm discovering #! 9.04 today. the versions of the usual applications that I get after upgrade/update are really old, like expected when retrieving them from jaunty repos. I'm trying to switch to the maverick repos, whithout much success.