On Tue, Mar 26, 2019 at 06:42:03PM +0000, Jon deps wrote:
> On 3/26/19 4:17 AM, haaber wrote:
> > 
> > 
> > On 3/26/19 2:33 PM, Jon deps wrote:
> > > On 3/26/19 12:17 AM, unman wrote:
> > > > On Tue, Mar 26, 2019 at 10:48:08AM +1100, haaber wrote:
> > > > > On 3/26/19 10:42 AM, Jon deps wrote:
> > > > > > Err:7 https://cdn-aws.deb.debian.org/debian jessie-backports Release
> > > > > >     404  Not Found
> > > > > > Reading package lists... Done
> > > > > > E: The repository 'https://deb.debian.org/debian jessie-backports
> > > > > > Release' does no longer have a Release file.
> > > > > > N: Updating from such a repository can't be done securely, and is
> > > > > > therefore disabled by default.
> > > > > > N: See apt-secure(8) manpage for repository creation and user
> > > > > > configuration details.
> > > > > > 
> > > > > a test run inside an app vm (with direct sys-firewall access, to avoid
> > > > > tor-related false errors) does confirm your observation for me. Is 
> > > > > this
> > > > > qubes-related or debian-related ? If the second one applies, we 
> > > > > discuss
> > > > > it in the wrong mailing list :)
> > > > 
> > > > It's not a Qubes issue.
> > > > jessie-backports was deprecated since June last year. The Release file
> > > > signing expired last month and it was removed from mirrors last week.
> > > > 
> > > > The packages can still be found at archive.debian.org, and you can
> > > > change your sources list to use this, but the Release file is still
> > > > expired.
> > > > You can work round this by getting a new copy of the signing key (if you
> > > > can) and updating with apt-key.
> > > > 
> > > 
> > > 
> > > so do I need  ?
> > > deb https://deb.debian.org/debian jessie-backports main
> > > 
> > > (  I don't even know what it is, I'm guessing it is the default
> > > /etc/apt/sources.list
> > > 
> > > so maybe I missed a memo? )
> > > 
> > > 
> > > 
> > > if not then just  #comment it out  and problem solved  ?
> > 
> > As we just learned, Unman is quite busy (thank you unman!). What I would
> > do, is to try it out in an AppVM : comment it out and run apt-get update
> >   and then apt-get upgrade. If somethings messes, just shutdown the
> > AppVM (thereby taking all the mess into nirvana) : thats a short play
> > coming with no risk! If upgrading without that line works easily (I
> > guess so), do the same in the template.   Bernhard
> > 
> > 
> > Bernhard
> > 
> 
> Sorry I don't see the point of doing it in an AppVM,  myself. I understand
> you think it might brake the  package list, but I can always just comment it
> back in  and apt-get update,  in my case Debian-9  is not my main  Template
> ......though it seems from reading here recently maybe it should be .... ?
> :)
> 
> My question is , If this is the default  /sources.list       and users don't
> regularly  go and change  their  sources.list     isn't this going to break
> on everyone's   systems    and  hence  some attention  should be paid to it.
> 
> 
> 
> This posting is meant for the group,  not any  one user  , be it  Mr. Unman
> or anyone
> 
> 
> 
> 
> My 2nd question is simply  what is backports  anyway , and what would be a
> suggested  fix  if  #commenting it out ......  isn't a great  idea ?
> 

Debian provides a relatively long lived stable release. Unfortunately
this means that the software can get somewhat dated. Backports is a way
of working round this by taking packages from the next release and back
porting them so that they work with stable. (Contrast this with the 9
monthly cycle of Fedora or 6 months for Ubuntu)
It wont add anything, and you would not (I think) never have installed
from that repository. You will lose nothing by commenting it out.

That line was included in error in a build of the Debian-9 template, and
has now been removed.
Sorry that I missed this - I overlooked the bit where you said it was
Debian-9.

unman

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20190326232426.xuwhguzwrwozc2ah%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to