[conspire] How to update packages when Deb is behind?

[Paul Zander]

I have now edited sources.list.  Removing all of the lines commented out leaves the following.   All of these lines were previously present, but have been edited.

  deb http://deb.debian.org/debian/ stable main contrib non-free
  deb http://security.debian.org/ stable/updates main contrib non-free
  deb http://deb.debian.org/debian/ stable-updates main contrib non-free
  deb http://www.deb-multimedia.org stable main non-free

BTW, the top of the file has this line generated during the original install.
# deb cdrom:[Debian GNU/Linux testing _Jessie_ - Official Snapshot amd64 lxde-CD Binary-1 20140728-06:13]/ testing mainIf I read the release info correctly July of 2014, Jessie was "testing"
If I use apt-get with the above info, I should hopefully be updating to "stretch".  Or, if I change "stable" to "testing" I would get the current instantiation of buster.
I still want check the versions for a bunch of apps, just to see if I might be headed into a mine field.  

Anything else before I jump off the cliff?

      From: Rick Moen <rick at linuxmafia.com>
 To: conspire at linuxmafia.com 
 Sent: Thursday, June 21, 2018 3:58 PM
 Subject: Re: [conspire] How to update packages when Deb is behind?
   
Quoting Paul Zander (paulz at ieee.org):

> Before I proceed,  can you explain /etc/debian_version and
> /etc/issue.  I expect those are the real cause of my situation.

I expect those are more _effect_ than cause.

I agree, based on the file date, /etc/debian_version seems to have been automatically created.   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxmafia.com/pipermail/conspire/attachments/20180622/9e87c975/attachment.html>