On Fri, Dec 30, 2016 at 04:43:09PM +0100, Pascal Hambourg wrote: > Le 30/12/2016 à 16:25, John Naggets a écrit : > > >And here would be the output of apt-cache policy: > > > >Package files: > > 100 /var/lib/dpkg/status > > release a=now > > 500 > > http://download.gluster.org/pub/gluster/glusterfs/3.7/3.7.16/Debian/jessie/apt/ > >jessie/main amd64 Packages > > origin download.gluster.org > > 500 http://ftp.ch.debian.org/debian/ jessie-updates/main Translation-en > > 500 http://ftp.ch.debian.org/debian/ jessie-updates/main amd64 Packages > > release o=Debian,a=stable-updates,n=jessie-updates,l=Debian,c=main > > origin ftp.ch.debian.org > > 500 http://security.debian.org/ jessie/updates/main Translation-en > > 500 http://security.debian.org/ jessie/updates/main amd64 Packages > > release v=8,o=Debian,a=stable,n=jessie,l=Debian-Security,c=main > > origin security.debian.org > >Pinned packages: > > As I suspected, the jessie/main section on ftp.ch.debian.org is missing, > although the line is present is sources.list : > > >>>deb http://ftp.ch.debian.org/debian jessie main > > Maybe try to add another mirror and run apt-get update ? > Or comment out the glusterfs repository and run apt-get update. >
Quick followup question -- what would have been the equivalent command to apt-cache policy if aptitude (from command line) were the preferred tool instead of apt-get? Will apt-cache still work in that situation? I am always confused about which tools play nice together and which don't. Mark
