On Sat, Feb 10, 2018 at 08:10:18AM -0500, Stephen P. Molnar wrote: > > Thanks for the reply. > > root@AbNormal:/home/comp# apt-get clean > root@AbNormal:/home/comp# > > Just before I read your reply I edited sources-list for a different > source, debian.uchicago.edu father than debian.org, and the synaptic > function was partially restored. > > # deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD > Binary-1 20171209-12:11]/ stretch contrib main > > # deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD > Binary-1 20171209-12:11]/ stretch main contrib > > deb http://debian.uchicago.edu/debian/ stretch contrib non-free main > deb-src http://debian.uchicago.edu/debian/ stretch contrib non-free > main > > # deb http://security.debian.org/debian-security/ stretch/updates main > contrib non-free > # deb-src http://security.debian.org/debian-security/ stretch/updates > main contrib non-free > > # stretch-updates, previously known as 'volatile' > deb http://debian.uchicago.edu/debian/ stretch-updates non-free contrib > main > deb-src http://debian.uchicago.edu/debian/ stretch-updates non-free > contrib main > > # stretch-backports, previously on backports.debian.org > deb http://debian.uchicago.edu/debian/ stretch-backports non-free > contrib main > deb-src http://debian.uchicago.edu/debian/ stretch-backports non-free > contrib main > > For some reason synaptic didn't like Debian security entries, but > worked when they were commented out. However, I am not happy about not > being able to receive security updates. Are those entries correct? >
I think the answer to that is no. On Stretch here I have deb http://security.debian.org/ stretch/updates main contrib non-free deb-src http://security.debian.org/ stretch/updates main contrin non-free ie no /debian-security Mark