bash upgraded but its version doesn't change
Clash Royale CLAN TAG#URR8PPP up vote
7
down vote
favorite
I'm working on Ubuntu 14.04 and I found something that I can't understand.
I execute the commands as below:
apt update && apt list --upgradable
I've found that bash is in the upgradable list.
For now the output of bash --version tells me that the version of bash is 4.3.11(1).
Then I do apt upgrade.
To my surprise, I do bash --version again and the output doesn't change at all. The version of bash is still 4.3.11(1).
So is this normal?, Some package can be upgradable while its version doesn't change?
apt bash package-management upgrade
edited Feb 1 at 8:52
muru
131k19275472
asked Feb 1 at 8:46
Yves
345316
add a comment |Â
up vote
7
down vote
favorite
I'm working on Ubuntu 14.04 and I found something that I can't understand.
I execute the commands as below:
apt update && apt list --upgradable
I've found that bash is in the upgradable list.
For now the output of bash --version tells me that the version of bash is 4.3.11(1).
Then I do apt upgrade.
To my surprise, I do bash --version again and the output doesn't change at all. The version of bash is still 4.3.11(1).
So is this normal?, Some package can be upgradable while its version doesn't change?
apt bash package-management upgrade
edited Feb 1 at 8:52
muru
131k19275472
asked Feb 1 at 8:46
Yves
345316
5
Does the same thing happen after you logout and login again?
– karel
Feb 1 at 8:50
@karel asked because if you didn't open a new instance of bash, the old one would still be running and report the old version number. Linux keeps things around and alive when they are running even if the underlying files are changed (by hanging on to the original inode and sometimes keeping things in memory). I see this when one of my browsers gets an update while it's running. It still reports (and is) the old version until I close and reopen it.
– Joe
Feb 8 at 4:58
add a comment |Â
up vote
7
down vote
favorite
up vote
7
down vote
favorite
I'm working on Ubuntu 14.04 and I found something that I can't understand.
I execute the commands as below:
apt update && apt list --upgradable
I've found that bash is in the upgradable list.
For now the output of bash --version tells me that the version of bash is 4.3.11(1).
Then I do apt upgrade.
To my surprise, I do bash --version again and the output doesn't change at all. The version of bash is still 4.3.11(1).
So is this normal?, Some package can be upgradable while its version doesn't change?
apt bash package-management upgrade
edited Feb 1 at 8:52
muru
131k19275472
asked Feb 1 at 8:46
Yves
345316
I'm working on Ubuntu 14.04 and I found something that I can't understand.
I execute the commands as below:
apt update && apt list --upgradable
I've found that bash is in the upgradable list.
For now the output of bash --version tells me that the version of bash is 4.3.11(1).
Then I do apt upgrade.
To my surprise, I do bash --version again and the output doesn't change at all. The version of bash is still 4.3.11(1).
So is this normal?, Some package can be upgradable while its version doesn't change?
apt bash package-management upgrade
apt bash package-management upgrade
edited Feb 1 at 8:52
muru
131k19275472
asked Feb 1 at 8:46
Yves
345316
edited Feb 1 at 8:52
muru
131k19275472
asked Feb 1 at 8:46
Yves
345316
edited Feb 1 at 8:52
muru
131k19275472
edited Feb 1 at 8:52
muru
131k19275472
edited Feb 1 at 8:52
muru
131k19275472
131k19275472
asked Feb 1 at 8:46
Yves
345316
asked Feb 1 at 8:46
Yves
345316
asked Feb 1 at 8:46
Yves
345316
345316
5
Does the same thing happen after you logout and login again?
– karel
Feb 1 at 8:50
@karel asked because if you didn't open a new instance of bash, the old one would still be running and report the old version number. Linux keeps things around and alive when they are running even if the underlying files are changed (by hanging on to the original inode and sometimes keeping things in memory). I see this when one of my browsers gets an update while it's running. It still reports (and is) the old version until I close and reopen it.
– Joe
Feb 8 at 4:58
add a comment |Â
5
Does the same thing happen after you logout and login again?
– karel
Feb 1 at 8:50
@karel asked because if you didn't open a new instance of bash, the old one would still be running and report the old version number. Linux keeps things around and alive when they are running even if the underlying files are changed (by hanging on to the original inode and sometimes keeping things in memory). I see this when one of my browsers gets an update while it's running. It still reports (and is) the old version until I close and reopen it.
– Joe
Feb 8 at 4:58
5
5
Does the same thing happen after you logout and login again?
– karel
Feb 1 at 8:50
Does the same thing happen after you logout and login again?
– karel
Feb 1 at 8:50
@karel asked because if you didn't open a new instance of bash, the old one would still be running and report the old version number. Linux keeps things around and alive when they are running even if the underlying files are changed (by hanging on to the original inode and sometimes keeping things in memory). I see this when one of my browsers gets an update while it's running. It still reports (and is) the old version until I close and reopen it.
– Joe
Feb 8 at 4:58
@karel asked because if you didn't open a new instance of bash, the old one would still be running and report the old version number. Linux keeps things around and alive when they are running even if the underlying files are changed (by hanging on to the original inode and sometimes keeping things in memory). I see this when one of my browsers gets an update while it's running. It still reports (and is) the old version until I close and reopen it.
– Joe
Feb 8 at 4:58
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
13
down vote
accepted
You should also check the package version:
$ bash --version
GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
$ apt-cache policy bash | head -n3
bash:
Installed: 4.4-5ubuntu1~16.04.york0
Candidate: 4.4-5ubuntu1~16.04.york0
As can be seen, the package and bash version strings have differences, as they're set by different people. In your case it might well be the case that nothing changed upstream, and changes were entirely by the package maintainer, so bash --version remains unchanged, but the package version changed.
edited Feb 1 at 8:52
dessert
20k55795
answered Feb 1 at 8:51
muru
131k19275472
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
13
down vote
accepted
You should also check the package version:
$ bash --version
GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
$ apt-cache policy bash | head -n3
bash:
Installed: 4.4-5ubuntu1~16.04.york0
Candidate: 4.4-5ubuntu1~16.04.york0
As can be seen, the package and bash version strings have differences, as they're set by different people. In your case it might well be the case that nothing changed upstream, and changes were entirely by the package maintainer, so bash --version remains unchanged, but the package version changed.
edited Feb 1 at 8:52
dessert
20k55795
answered Feb 1 at 8:51
muru
131k19275472
add a comment |Â
up vote
13
down vote
accepted
You should also check the package version:
$ bash --version
GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
$ apt-cache policy bash | head -n3
bash:
Installed: 4.4-5ubuntu1~16.04.york0
Candidate: 4.4-5ubuntu1~16.04.york0
As can be seen, the package and bash version strings have differences, as they're set by different people. In your case it might well be the case that nothing changed upstream, and changes were entirely by the package maintainer, so bash --version remains unchanged, but the package version changed.
edited Feb 1 at 8:52
dessert
20k55795
answered Feb 1 at 8:51
muru
131k19275472
add a comment |Â
up vote
13
down vote
accepted
up vote
13
down vote
accepted
You should also check the package version:
$ bash --version
GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
$ apt-cache policy bash | head -n3
bash:
Installed: 4.4-5ubuntu1~16.04.york0
Candidate: 4.4-5ubuntu1~16.04.york0
As can be seen, the package and bash version strings have differences, as they're set by different people. In your case it might well be the case that nothing changed upstream, and changes were entirely by the package maintainer, so bash --version remains unchanged, but the package version changed.
edited Feb 1 at 8:52
dessert
20k55795
answered Feb 1 at 8:51
muru
131k19275472
You should also check the package version:
$ bash --version
GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
$ apt-cache policy bash | head -n3
bash:
Installed: 4.4-5ubuntu1~16.04.york0
Candidate: 4.4-5ubuntu1~16.04.york0
As can be seen, the package and bash version strings have differences, as they're set by different people. In your case it might well be the case that nothing changed upstream, and changes were entirely by the package maintainer, so bash --version remains unchanged, but the package version changed.
edited Feb 1 at 8:52
dessert
20k55795
answered Feb 1 at 8:51
muru
131k19275472
edited Feb 1 at 8:52
dessert
20k55795
edited Feb 1 at 8:52
dessert
20k55795
edited Feb 1 at 8:52
dessert
20k55795
20k55795
answered Feb 1 at 8:51
muru
131k19275472
answered Feb 1 at 8:51
muru
131k19275472
answered Feb 1 at 8:51
muru
131k19275472
131k19275472
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1002010%2fbash-upgraded-but-its-version-doesnt-change%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
5
Does the same thing happen after you logout and login again?
– karel
Feb 1 at 8:50
@karel asked because if you didn't open a new instance of bash, the old one would still be running and report the old version number. Linux keeps things around and alive when they are running even if the underlying files are changed (by hanging on to the original inode and sometimes keeping things in memory). I see this when one of my browsers gets an update while it's running. It still reports (and is) the old version until I close and reopen it.
– Joe
Feb 8 at 4:58