Debian 9.5 seems to have automatically updated itself to Debian 9.6
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
We have several Debian 9.5 servers.
However, just a few days after the officially release of Debian 9.6, I noticed that one of our servers had already automatically updated itself to Debian 9.6.
We have neither initiated any upgrades, nor have installed and do not use unattended-upgrades. All our Debian servers are cloned copies of the same server.
None of our other Debian servers have ever updated themselves before and indeed all our other Debian 9.5 servers still are Debian 9.5 servers.
How is this possible?
debian upgrade unattended-upgrades
New contributor
|
show 3 more comments
up vote
0
down vote
favorite
We have several Debian 9.5 servers.
However, just a few days after the officially release of Debian 9.6, I noticed that one of our servers had already automatically updated itself to Debian 9.6.
We have neither initiated any upgrades, nor have installed and do not use unattended-upgrades. All our Debian servers are cloned copies of the same server.
None of our other Debian servers have ever updated themselves before and indeed all our other Debian 9.5 servers still are Debian 9.5 servers.
How is this possible?
debian upgrade unattended-upgrades
New contributor
Are you absolutely sure you did not run an update between the release of 9.6 and now? Please edit your post to include the output ofHISTTIMEFORMAT="%d/%m/%y %T " history | grep 'apt upgrade'
you can change it toapt-get
oraptitude
depending on which one you use.
– kemotep
2 days ago
Thanks for quick response. No, nothing shows up in history.
– user321321
2 days ago
I did wonder if lsb_release -a was mis-reporting the version. uname -r says 4.9.0-5-amd64
– user321321
2 days ago
Is there anything in/var/log/apt/history.log*
or/var/log/dpkg.log*
referring to an upgrade ofbase-files
, specifically to version 9.9+deb9u6?
– Stephen Kitt
2 days ago
Hi Stephen. No, both log files contain the most recent entry on 24 September 2018 long before 10 November 2018 release date of Debian 9.6. Even then they only contain an entry for the removal of a redundant package. My source.list is: deb ftp.uk.debian.org/debian stretch main contrib non-free deb-src ftp.uk.debian.org/debian stretch main contrib non-free deb security.debian.org/debian-security stretch/updates main contrib non-free deb-src security.debian.org/debian-security stretch/updates main contrib non-free
– user321321
2 days ago
|
show 3 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We have several Debian 9.5 servers.
However, just a few days after the officially release of Debian 9.6, I noticed that one of our servers had already automatically updated itself to Debian 9.6.
We have neither initiated any upgrades, nor have installed and do not use unattended-upgrades. All our Debian servers are cloned copies of the same server.
None of our other Debian servers have ever updated themselves before and indeed all our other Debian 9.5 servers still are Debian 9.5 servers.
How is this possible?
debian upgrade unattended-upgrades
New contributor
We have several Debian 9.5 servers.
However, just a few days after the officially release of Debian 9.6, I noticed that one of our servers had already automatically updated itself to Debian 9.6.
We have neither initiated any upgrades, nor have installed and do not use unattended-upgrades. All our Debian servers are cloned copies of the same server.
None of our other Debian servers have ever updated themselves before and indeed all our other Debian 9.5 servers still are Debian 9.5 servers.
How is this possible?
debian upgrade unattended-upgrades
debian upgrade unattended-upgrades
New contributor
New contributor
edited 2 days ago
Rui F Ribeiro
38.2k1475123
38.2k1475123
New contributor
asked 2 days ago
user321321
1
1
New contributor
New contributor
Are you absolutely sure you did not run an update between the release of 9.6 and now? Please edit your post to include the output ofHISTTIMEFORMAT="%d/%m/%y %T " history | grep 'apt upgrade'
you can change it toapt-get
oraptitude
depending on which one you use.
– kemotep
2 days ago
Thanks for quick response. No, nothing shows up in history.
– user321321
2 days ago
I did wonder if lsb_release -a was mis-reporting the version. uname -r says 4.9.0-5-amd64
– user321321
2 days ago
Is there anything in/var/log/apt/history.log*
or/var/log/dpkg.log*
referring to an upgrade ofbase-files
, specifically to version 9.9+deb9u6?
– Stephen Kitt
2 days ago
Hi Stephen. No, both log files contain the most recent entry on 24 September 2018 long before 10 November 2018 release date of Debian 9.6. Even then they only contain an entry for the removal of a redundant package. My source.list is: deb ftp.uk.debian.org/debian stretch main contrib non-free deb-src ftp.uk.debian.org/debian stretch main contrib non-free deb security.debian.org/debian-security stretch/updates main contrib non-free deb-src security.debian.org/debian-security stretch/updates main contrib non-free
– user321321
2 days ago
|
show 3 more comments
Are you absolutely sure you did not run an update between the release of 9.6 and now? Please edit your post to include the output ofHISTTIMEFORMAT="%d/%m/%y %T " history | grep 'apt upgrade'
you can change it toapt-get
oraptitude
depending on which one you use.
– kemotep
2 days ago
Thanks for quick response. No, nothing shows up in history.
– user321321
2 days ago
I did wonder if lsb_release -a was mis-reporting the version. uname -r says 4.9.0-5-amd64
– user321321
2 days ago
Is there anything in/var/log/apt/history.log*
or/var/log/dpkg.log*
referring to an upgrade ofbase-files
, specifically to version 9.9+deb9u6?
– Stephen Kitt
2 days ago
Hi Stephen. No, both log files contain the most recent entry on 24 September 2018 long before 10 November 2018 release date of Debian 9.6. Even then they only contain an entry for the removal of a redundant package. My source.list is: deb ftp.uk.debian.org/debian stretch main contrib non-free deb-src ftp.uk.debian.org/debian stretch main contrib non-free deb security.debian.org/debian-security stretch/updates main contrib non-free deb-src security.debian.org/debian-security stretch/updates main contrib non-free
– user321321
2 days ago
Are you absolutely sure you did not run an update between the release of 9.6 and now? Please edit your post to include the output of
HISTTIMEFORMAT="%d/%m/%y %T " history | grep 'apt upgrade'
you can change it to apt-get
or aptitude
depending on which one you use.– kemotep
2 days ago
Are you absolutely sure you did not run an update between the release of 9.6 and now? Please edit your post to include the output of
HISTTIMEFORMAT="%d/%m/%y %T " history | grep 'apt upgrade'
you can change it to apt-get
or aptitude
depending on which one you use.– kemotep
2 days ago
Thanks for quick response. No, nothing shows up in history.
– user321321
2 days ago
Thanks for quick response. No, nothing shows up in history.
– user321321
2 days ago
I did wonder if lsb_release -a was mis-reporting the version. uname -r says 4.9.0-5-amd64
– user321321
2 days ago
I did wonder if lsb_release -a was mis-reporting the version. uname -r says 4.9.0-5-amd64
– user321321
2 days ago
Is there anything in
/var/log/apt/history.log*
or /var/log/dpkg.log*
referring to an upgrade of base-files
, specifically to version 9.9+deb9u6?– Stephen Kitt
2 days ago
Is there anything in
/var/log/apt/history.log*
or /var/log/dpkg.log*
referring to an upgrade of base-files
, specifically to version 9.9+deb9u6?– Stephen Kitt
2 days ago
Hi Stephen. No, both log files contain the most recent entry on 24 September 2018 long before 10 November 2018 release date of Debian 9.6. Even then they only contain an entry for the removal of a redundant package. My source.list is: deb ftp.uk.debian.org/debian stretch main contrib non-free deb-src ftp.uk.debian.org/debian stretch main contrib non-free deb security.debian.org/debian-security stretch/updates main contrib non-free deb-src security.debian.org/debian-security stretch/updates main contrib non-free
– user321321
2 days ago
Hi Stephen. No, both log files contain the most recent entry on 24 September 2018 long before 10 November 2018 release date of Debian 9.6. Even then they only contain an entry for the removal of a redundant package. My source.list is: deb ftp.uk.debian.org/debian stretch main contrib non-free deb-src ftp.uk.debian.org/debian stretch main contrib non-free deb security.debian.org/debian-security stretch/updates main contrib non-free deb-src security.debian.org/debian-security stretch/updates main contrib non-free
– user321321
2 days ago
|
show 3 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
user321321 is a new contributor. Be nice, and check out our Code of Conduct.
user321321 is a new contributor. Be nice, and check out our Code of Conduct.
user321321 is a new contributor. Be nice, and check out our Code of Conduct.
user321321 is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f482170%2fdebian-9-5-seems-to-have-automatically-updated-itself-to-debian-9-6%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Are you absolutely sure you did not run an update between the release of 9.6 and now? Please edit your post to include the output of
HISTTIMEFORMAT="%d/%m/%y %T " history | grep 'apt upgrade'
you can change it toapt-get
oraptitude
depending on which one you use.– kemotep
2 days ago
Thanks for quick response. No, nothing shows up in history.
– user321321
2 days ago
I did wonder if lsb_release -a was mis-reporting the version. uname -r says 4.9.0-5-amd64
– user321321
2 days ago
Is there anything in
/var/log/apt/history.log*
or/var/log/dpkg.log*
referring to an upgrade ofbase-files
, specifically to version 9.9+deb9u6?– Stephen Kitt
2 days ago
Hi Stephen. No, both log files contain the most recent entry on 24 September 2018 long before 10 November 2018 release date of Debian 9.6. Even then they only contain an entry for the removal of a redundant package. My source.list is: deb ftp.uk.debian.org/debian stretch main contrib non-free deb-src ftp.uk.debian.org/debian stretch main contrib non-free deb security.debian.org/debian-security stretch/updates main contrib non-free deb-src security.debian.org/debian-security stretch/updates main contrib non-free
– user321321
2 days ago