Why is my Jessie system trying to upgrade to Stretch AGAIN!

[Head_on_a_Stick]

^ & ^^ the OP claims to have already checked /etc/apt/sources.list.d/

This will show APT's current repository status:

Code: Select all

apt policy

I would blame VirtualBox for this — their emulator software is complete crap so it stands to reason that the packaging will be of similar quality

[sunrat]

This will show APT's current repository status:

Code: Select all

apt policy

In Jessie? I don't have Jessie to check but apt had less functions back then.

[L_V]

Code: Select all

apt-cache policy


[Head_on_a_Stick]

^ & ^^ yes, that's just my lazy typing again, anything to save a few characters

[sunrat]

apt policy works in sid. That's all I can check atm.

[No_windows]

Code: Select all

apt-cache policy


Code: Select all

Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages
     release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main
     origin dl.google.com
 500 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_8.0/  Packages
     release o=obs://build.opensuse.org/home:stevenpusser/Debian_8.0,n=Debian_8.0,l=home:stevenpusser,c=
     origin download.opensuse.org
 500 http://deb.debian.org/debian/ jessie-backports/non-free Translation-en
 500 http://deb.debian.org/debian/ jessie-backports/main Translation-en
 500 http://deb.debian.org/debian/ jessie-backports/contrib Translation-en
 100 http://deb.debian.org/debian/ jessie-backports/non-free amd64 Packages
     release o=Debian Backports,a=jessie-backports,n=jessie-backports,l=Debian Backports,c=non-free
     origin deb.debian.org
 100 http://deb.debian.org/debian/ jessie-backports/contrib amd64 Packages
     release o=Debian Backports,a=jessie-backports,n=jessie-backports,l=Debian Backports,c=contrib
     origin deb.debian.org
 100 http://deb.debian.org/debian/ jessie-backports/main amd64 Packages
     release o=Debian Backports,a=jessie-backports,n=jessie-backports,l=Debian Backports,c=main
     origin deb.debian.org
 500 http://deb.debian.org/debian/ jessie-updates/non-free Translation-en
 500 http://deb.debian.org/debian/ jessie-updates/main Translation-en
 500 http://deb.debian.org/debian/ jessie-updates/contrib Translation-en
 500 http://deb.debian.org/debian/ jessie-updates/non-free amd64 Packages
     release o=Debian,a=oldstable-updates,n=jessie-updates,l=Debian,c=non-free
     origin deb.debian.org
 500 http://deb.debian.org/debian/ jessie-updates/contrib amd64 Packages
     release o=Debian,a=oldstable-updates,n=jessie-updates,l=Debian,c=contrib
     origin deb.debian.org
 500 http://deb.debian.org/debian/ jessie-updates/main amd64 Packages
     release o=Debian,a=oldstable-updates,n=jessie-updates,l=Debian,c=main
     origin deb.debian.org
 500 http://deb.debian.org/debian/ jessie/non-free Translation-en
 500 http://deb.debian.org/debian/ jessie/main Translation-en
 500 http://deb.debian.org/debian/ jessie/contrib Translation-en
 500 http://deb.debian.org/debian/ jessie/non-free amd64 Packages
     release v=8.11,o=Debian,a=oldstable,n=jessie,l=Debian,c=non-free
     origin deb.debian.org
 500 http://deb.debian.org/debian/ jessie/contrib amd64 Packages
     release v=8.11,o=Debian,a=oldstable,n=jessie,l=Debian,c=contrib
     origin deb.debian.org
 500 http://deb.debian.org/debian/ jessie/main amd64 Packages
     release v=8.11,o=Debian,a=oldstable,n=jessie,l=Debian,c=main
     origin deb.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=oldstable,n=jessie,l=Debian-Security,c=main
     origin security.debian.org
Pinned packages:



Anything telling here?

[L_V]

What happen if you disable backports ?
Same ?

[No_windows]

What happen if you disable backports ?
Same ?

I didn't get a chance to try anything. I ran Synaptic again to verify the problem before attempting to change anything and there were no updates anymore. This was several hours after I noticed the problem again. I think this may not be a problem on my end.

Would backports have any deb9 (or whatever the abbreviation is) files?

[L_V]

Don't know "deb9", but I really wonder what you can expect from ... Jessie-backports

[stevepusser]

I updated Pale Moon to 28.0.0 in my repo listed there a week or so ago, but that would be only one package. We'll need to see the other 49 or so to see what the heck is really going on.

[No_windows]

I updated Pale Moon to 28.0.0 in my repo listed there a week or so ago, but that would be only one package. We'll need to see the other 49 or so to see what the heck is really going on.

Yes, I remember someone (maybe you) asking that last time, but I couldn't figure out how to capture that info. Synaptic doesn't let me highlight and copy, and I couldn't find how to do the same in a terminal with apt and feel safe that it wouldn't start the upgrade.... looks like the -s would have done that for me.

The 49 were new packages, there were well over 100 that it wanted to update on top of that.

[No_windows]

I updated Pale Moon to 28.0.0 in my repo listed there a week or so ago, but that would be only one package.

Yes several times

I don't even use Palemoon on this system, but it's up to date! Its my main browser on my laptop (Stretch). It may be a good idea to switch from Firefox, on Jessie, since I'm not sure if it's updated much anymore.

[stevepusser]

Well, what does their versioning look like overall? Do you see a lot of "bpo8" versioning tacked onto the end, which means they are coming from jessie-backports, or maybe "8u1" in there, which would mean a security update from jessie-security?

[No_windows]

Well, what does their versioning look like overall? Do you see a lot of "bpo8" versioning tacked onto the end, which means they are coming from jessie-backports, or maybe "8u1" in there, which would mean a security update from jessie-security?

I saw a couple of deb9s or whatever Stretch uses.... it wasn't bpo8 or bpo9. Everything was a major version jump, Though.

[No_windows]

Would there be some dependencies that are needed for the stable version of Chrome that Jessie can't accommodate? Perhaps that is leading to the "newer" files?
It would be interesting to see if that might be the case.


Cheers
Chris

I just saw your post. I would think Google would have to have the files in their repo then, since I don't have any Stretch repos in my sources.list to pull from... unless maybe that would pull from backports if the needed files were there? I wish I could have grabbed the list of changes Synaptic was asking to make.