Wrong lsb-release after release upgrade
Today I did a LTS upgrade from trusty to xenial using do-release-upgrade. It went through without an error. But after the upgrade I'm not sure on which version my system is now.
The do-release-upgrade tool said it would upgrade to xenial and my sources.list now points to the xenial package archive. apt claims all packages are fully upgraded (doing update, upgrade and dist-upgrade).
But when I run lsb_release -a I'm still getting this
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty
And when I check the version of base-files (which to my understanding contains the /etc/lsb-release file) with dpkg --list I'm getting version 10.1 which is the most recent package version in the bionic package archive.
Also when I run do-release-upgrade -c it still tries to upgrade to xenial.
I must say I'm pretty confused. Has anyone any idea what's going on?
Update
I think I know what happened here. While updating, the installation process for base-files asks for user confirmation on whether to update the /etc/lsb-release file if it was edited since the last installation.
Configuration file '/etc/lsb-release'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
The file looked like it had the same contents as in the trusty base-file package before updating, so I don't really understand why I got get asked before replacing it. Anyways, I think I might have taken the default action, resulting in a mismatch between the actually installed release and the contents of the file.
Replacing the file with the one from the xenial package allowed me to successfully update to bionic with do-release-upgrade. This time I selected to update the lsb-release while upgrading. Manually messing with the contents of that file before upgrading again didn't seem to have any adverse effects.
apt package-management upgrade dpkg do-release-upgrade
asked Dec 7 at 18:50
heilerich
1083
add a comment |
Today I did a LTS upgrade from trusty to xenial using do-release-upgrade. It went through without an error. But after the upgrade I'm not sure on which version my system is now.
The do-release-upgrade tool said it would upgrade to xenial and my sources.list now points to the xenial package archive. apt claims all packages are fully upgraded (doing update, upgrade and dist-upgrade).
But when I run lsb_release -a I'm still getting this
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty
And when I check the version of base-files (which to my understanding contains the /etc/lsb-release file) with dpkg --list I'm getting version 10.1 which is the most recent package version in the bionic package archive.
Also when I run do-release-upgrade -c it still tries to upgrade to xenial.
I must say I'm pretty confused. Has anyone any idea what's going on?
Update
I think I know what happened here. While updating, the installation process for base-files asks for user confirmation on whether to update the /etc/lsb-release file if it was edited since the last installation.
Configuration file '/etc/lsb-release'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
The file looked like it had the same contents as in the trusty base-file package before updating, so I don't really understand why I got get asked before replacing it. Anyways, I think I might have taken the default action, resulting in a mismatch between the actually installed release and the contents of the file.
Replacing the file with the one from the xenial package allowed me to successfully update to bionic with do-release-upgrade. This time I selected to update the lsb-release while upgrading. Manually messing with the contents of that file before upgrading again didn't seem to have any adverse effects.
apt package-management upgrade dpkg do-release-upgrade
asked Dec 7 at 18:50
heilerich
1083
add a comment |
Today I did a LTS upgrade from trusty to xenial using do-release-upgrade. It went through without an error. But after the upgrade I'm not sure on which version my system is now.
The do-release-upgrade tool said it would upgrade to xenial and my sources.list now points to the xenial package archive. apt claims all packages are fully upgraded (doing update, upgrade and dist-upgrade).
But when I run lsb_release -a I'm still getting this
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty
And when I check the version of base-files (which to my understanding contains the /etc/lsb-release file) with dpkg --list I'm getting version 10.1 which is the most recent package version in the bionic package archive.
Also when I run do-release-upgrade -c it still tries to upgrade to xenial.
I must say I'm pretty confused. Has anyone any idea what's going on?
Update
I think I know what happened here. While updating, the installation process for base-files asks for user confirmation on whether to update the /etc/lsb-release file if it was edited since the last installation.
Configuration file '/etc/lsb-release'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
The file looked like it had the same contents as in the trusty base-file package before updating, so I don't really understand why I got get asked before replacing it. Anyways, I think I might have taken the default action, resulting in a mismatch between the actually installed release and the contents of the file.
Replacing the file with the one from the xenial package allowed me to successfully update to bionic with do-release-upgrade. This time I selected to update the lsb-release while upgrading. Manually messing with the contents of that file before upgrading again didn't seem to have any adverse effects.
apt package-management upgrade dpkg do-release-upgrade
asked Dec 7 at 18:50
heilerich
1083
Today I did a LTS upgrade from trusty to xenial using do-release-upgrade. It went through without an error. But after the upgrade I'm not sure on which version my system is now.
The do-release-upgrade tool said it would upgrade to xenial and my sources.list now points to the xenial package archive. apt claims all packages are fully upgraded (doing update, upgrade and dist-upgrade).
But when I run lsb_release -a I'm still getting this
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty
And when I check the version of base-files (which to my understanding contains the /etc/lsb-release file) with dpkg --list I'm getting version 10.1 which is the most recent package version in the bionic package archive.
Also when I run do-release-upgrade -c it still tries to upgrade to xenial.
I must say I'm pretty confused. Has anyone any idea what's going on?
Update
I think I know what happened here. While updating, the installation process for base-files asks for user confirmation on whether to update the /etc/lsb-release file if it was edited since the last installation.
Configuration file '/etc/lsb-release'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
The file looked like it had the same contents as in the trusty base-file package before updating, so I don't really understand why I got get asked before replacing it. Anyways, I think I might have taken the default action, resulting in a mismatch between the actually installed release and the contents of the file.
Replacing the file with the one from the xenial package allowed me to successfully update to bionic with do-release-upgrade. This time I selected to update the lsb-release while upgrading. Manually messing with the contents of that file before upgrading again didn't seem to have any adverse effects.
apt package-management upgrade dpkg do-release-upgrade
apt package-management upgrade dpkg do-release-upgrade
asked Dec 7 at 18:50
heilerich
1083
asked Dec 7 at 18:50
heilerich
1083
edited Dec 9 at 13:22
asked Dec 7 at 18:50
heilerich
1083
asked Dec 7 at 18:50
heilerich
1083
asked Dec 7 at 18:50
heilerich
1083
1083
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
lsb_release is a Python script that simply reads from the file /etc/lsb-release and dumps output to the screen. You can edit the file using:
sudo -H gedit /etc/lsb-release
Then change the contents to suit your platform. Mine contains:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"
answered Dec 7 at 19:02
WinEunuuchs2Unix
42.2k1071161
I was aware of that, but isn't this strange? Do you have any idea as to how this has happened? Won't just changing the contents of that file leave my system in an even more inconsistent state?
– heilerich
Dec 8 at 16:02
@heilerich I found many instances where this has happened to other users. I didn't find a reason though.
– WinEunuuchs2Unix
Dec 8 at 17:17
Replacing my lsb-release file with yours allowed me to upgrade to bionic. Manually messing with the contents of that file before upgrading again didn't seem to have any adverse effects.
– heilerich
Dec 9 at 13:24
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2faskubuntu.com%2fquestions%2f1099247%2fwrong-lsb-release-after-release-upgrade%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
lsb_release is a Python script that simply reads from the file /etc/lsb-release and dumps output to the screen. You can edit the file using:
sudo -H gedit /etc/lsb-release
Then change the contents to suit your platform. Mine contains:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"
answered Dec 7 at 19:02
WinEunuuchs2Unix
42.2k1071161
I was aware of that, but isn't this strange? Do you have any idea as to how this has happened? Won't just changing the contents of that file leave my system in an even more inconsistent state?
– heilerich
Dec 8 at 16:02
@heilerich I found many instances where this has happened to other users. I didn't find a reason though.
– WinEunuuchs2Unix
Dec 8 at 17:17
Replacing my lsb-release file with yours allowed me to upgrade to bionic. Manually messing with the contents of that file before upgrading again didn't seem to have any adverse effects.
– heilerich
Dec 9 at 13:24
add a comment |
lsb_release is a Python script that simply reads from the file /etc/lsb-release and dumps output to the screen. You can edit the file using:
sudo -H gedit /etc/lsb-release
Then change the contents to suit your platform. Mine contains:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"
answered Dec 7 at 19:02
WinEunuuchs2Unix
42.2k1071161
I was aware of that, but isn't this strange? Do you have any idea as to how this has happened? Won't just changing the contents of that file leave my system in an even more inconsistent state?
– heilerich
Dec 8 at 16:02
@heilerich I found many instances where this has happened to other users. I didn't find a reason though.
– WinEunuuchs2Unix
Dec 8 at 17:17
Replacing my lsb-release file with yours allowed me to upgrade to bionic. Manually messing with the contents of that file before upgrading again didn't seem to have any adverse effects.
– heilerich
Dec 9 at 13:24
add a comment |
lsb_release is a Python script that simply reads from the file /etc/lsb-release and dumps output to the screen. You can edit the file using:
sudo -H gedit /etc/lsb-release
Then change the contents to suit your platform. Mine contains:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"
answered Dec 7 at 19:02
WinEunuuchs2Unix
42.2k1071161
lsb_release is a Python script that simply reads from the file /etc/lsb-release and dumps output to the screen. You can edit the file using:
sudo -H gedit /etc/lsb-release
Then change the contents to suit your platform. Mine contains:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"
answered Dec 7 at 19:02
WinEunuuchs2Unix
42.2k1071161
answered Dec 7 at 19:02
WinEunuuchs2Unix
42.2k1071161
answered Dec 7 at 19:02
WinEunuuchs2Unix
42.2k1071161
answered Dec 7 at 19:02
WinEunuuchs2Unix
42.2k1071161
42.2k1071161
I was aware of that, but isn't this strange? Do you have any idea as to how this has happened? Won't just changing the contents of that file leave my system in an even more inconsistent state?
– heilerich
Dec 8 at 16:02
@heilerich I found many instances where this has happened to other users. I didn't find a reason though.
– WinEunuuchs2Unix
Dec 8 at 17:17
Replacing my lsb-release file with yours allowed me to upgrade to bionic. Manually messing with the contents of that file before upgrading again didn't seem to have any adverse effects.
– heilerich
Dec 9 at 13:24
add a comment |
I was aware of that, but isn't this strange? Do you have any idea as to how this has happened? Won't just changing the contents of that file leave my system in an even more inconsistent state?
– heilerich
Dec 8 at 16:02
@heilerich I found many instances where this has happened to other users. I didn't find a reason though.
– WinEunuuchs2Unix
Dec 8 at 17:17
Replacing my lsb-release file with yours allowed me to upgrade to bionic. Manually messing with the contents of that file before upgrading again didn't seem to have any adverse effects.
– heilerich
Dec 9 at 13:24
I was aware of that, but isn't this strange? Do you have any idea as to how this has happened? Won't just changing the contents of that file leave my system in an even more inconsistent state?
– heilerich
Dec 8 at 16:02
I was aware of that, but isn't this strange? Do you have any idea as to how this has happened? Won't just changing the contents of that file leave my system in an even more inconsistent state?
– heilerich
Dec 8 at 16:02
@heilerich I found many instances where this has happened to other users. I didn't find a reason though.
– WinEunuuchs2Unix
Dec 8 at 17:17
@heilerich I found many instances where this has happened to other users. I didn't find a reason though.
– WinEunuuchs2Unix
Dec 8 at 17:17
Replacing my lsb-release file with yours allowed me to upgrade to bionic. Manually messing with the contents of that file before upgrading again didn't seem to have any adverse effects.
– heilerich
Dec 9 at 13:24
Replacing my lsb-release file with yours allowed me to upgrade to bionic. Manually messing with the contents of that file before upgrading again didn't seem to have any adverse effects.
– heilerich
Dec 9 at 13:24
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2faskubuntu.com%2fquestions%2f1099247%2fwrong-lsb-release-after-release-upgrade%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
