Apt says there is 1 not updated, but there are no updates
Clash Royale CLAN TAG#URR8PPP up vote
4
down vote
favorite
I am using Ubuntu 17.10. apt says there is 1 package not updated, but there are no updates.
These are the commands that I ran:
$ sudo apt update
1 package can be upgraded. Execute 'apt list --upgradable' to see them.
$ apt list --upgradable
gtk-communitheme/artful,artful 18.04~wip1+201803130047+0c20cd0~ubuntu17.10.1 all
$ sudo apt upgrade
0 upgraded, no errors.
$ sudo apt dist-upgrade
0 upgraded, no errors.
apt package-management upgrade updates
asked Mar 13 at 16:54
Yoran Jansen
5121520
add a comment |Â
up vote
4
down vote
favorite
I am using Ubuntu 17.10. apt says there is 1 package not updated, but there are no updates.
These are the commands that I ran:
$ sudo apt update
1 package can be upgraded. Execute 'apt list --upgradable' to see them.
$ apt list --upgradable
gtk-communitheme/artful,artful 18.04~wip1+201803130047+0c20cd0~ubuntu17.10.1 all
$ sudo apt upgrade
0 upgraded, no errors.
$ sudo apt dist-upgrade
0 upgraded, no errors.
apt package-management upgrade updates
asked Mar 13 at 16:54
Yoran Jansen
5121520
You may want to try runningapt clean && apt autoclean...
– NerdOfCode
Mar 13 at 17:51
@WinEunuuchs2Unix Fixed it
– Yoran Jansen
Mar 17 at 12:02
add a comment |Â
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I am using Ubuntu 17.10. apt says there is 1 package not updated, but there are no updates.
These are the commands that I ran:
$ sudo apt update
1 package can be upgraded. Execute 'apt list --upgradable' to see them.
$ apt list --upgradable
gtk-communitheme/artful,artful 18.04~wip1+201803130047+0c20cd0~ubuntu17.10.1 all
$ sudo apt upgrade
0 upgraded, no errors.
$ sudo apt dist-upgrade
0 upgraded, no errors.
apt package-management upgrade updates
asked Mar 13 at 16:54
Yoran Jansen
5121520
I am using Ubuntu 17.10. apt says there is 1 package not updated, but there are no updates.
These are the commands that I ran:
$ sudo apt update
1 package can be upgraded. Execute 'apt list --upgradable' to see them.
$ apt list --upgradable
gtk-communitheme/artful,artful 18.04~wip1+201803130047+0c20cd0~ubuntu17.10.1 all
$ sudo apt upgrade
0 upgraded, no errors.
$ sudo apt dist-upgrade
0 upgraded, no errors.
apt package-management upgrade updates
apt package-management upgrade updates
asked Mar 13 at 16:54
Yoran Jansen
5121520
asked Mar 13 at 16:54
Yoran Jansen
5121520
edited Mar 17 at 12:02
asked Mar 13 at 16:54
Yoran Jansen
5121520
asked Mar 13 at 16:54
Yoran Jansen
5121520
asked Mar 13 at 16:54
Yoran Jansen
5121520
5121520
You may want to try runningapt clean && apt autoclean...
– NerdOfCode
Mar 13 at 17:51
@WinEunuuchs2Unix Fixed it
– Yoran Jansen
Mar 17 at 12:02
add a comment |Â
You may want to try runningapt clean && apt autoclean...
– NerdOfCode
Mar 13 at 17:51
@WinEunuuchs2Unix Fixed it
– Yoran Jansen
Mar 17 at 12:02
You may want to try running
apt clean && apt autoclean...– NerdOfCode
Mar 13 at 17:51
You may want to try running
apt clean && apt autoclean...– NerdOfCode
Mar 13 at 17:51
@WinEunuuchs2Unix Fixed it
– Yoran Jansen
Mar 17 at 12:02
@WinEunuuchs2Unix Fixed it
– Yoran Jansen
Mar 17 at 12:02
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
0
down vote
Best guess
My best guess is you suffered a bug fix for this bug: Want to update from 17.04 to 18.04, but do-release-upgrade fails.
Essentially the OP was using 17.04, wanted to upgrade to 17.10 but it took him/her to 18.04 which is invalid because it's not an officially sanctioned version yet.
It would appear rather than taking away the upgrade to 18.04 option the programmers simply suppressed the option from upgrading to 18.04. That said I would only upgrade to 18.04 in a quarantined environment (separate partition / non production) and extensive testing. Some ideas:
- Create a 18.04 Live USB with persistent storage.
- Boot from the USB and select "Try before Installing".
- Install your mission critical applications to the USB's persistent storage.
- Test your applications with a COPY of your data.
Do not test the programs on the real live data onsdX.- Try out your USB keyboards and mice.
- Try out your printer(s).
- Access your favorite websites and download files.
- Test suspend and resume.
- Test Fn keys for volume and brightness.
- Make a keyboard shortcut and ensure it works ok.
- Test
systemd,cronand other system utilities. - If you've written scripts, copy them over and test them.
- Test
xrandrfunctions you have used before. - Run CPU & RAM stress tests. System benchmarks might be helpful too.
- Remember 18.04 uses Unity 7.5 but 16.04 uses Unity 7.4 I think.
- Of course you should test Anything else you can think of
answered Mar 14 at 1:56
WinEunuuchs2Unix
36k759134
This will not work because the update has nothing to do with ubuntu but with a theme, and ubuntu 18.04 is BETA so it would NEVER need that for an update.
– Yoran Jansen
Mar 17 at 12:01
add a comment |Â
up vote
0
down vote
accepted
Answer:
I used a ppa that was no longer there, but had an update. For some reason it didn't update that into the cache, however after removing the ppa it did not longer have an 'impossible' update.
answered Apr 28 at 12:37
Yoran Jansen
5121520
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Best guess
My best guess is you suffered a bug fix for this bug: Want to update from 17.04 to 18.04, but do-release-upgrade fails.
Essentially the OP was using 17.04, wanted to upgrade to 17.10 but it took him/her to 18.04 which is invalid because it's not an officially sanctioned version yet.
It would appear rather than taking away the upgrade to 18.04 option the programmers simply suppressed the option from upgrading to 18.04. That said I would only upgrade to 18.04 in a quarantined environment (separate partition / non production) and extensive testing. Some ideas:
- Create a 18.04 Live USB with persistent storage.
- Boot from the USB and select "Try before Installing".
- Install your mission critical applications to the USB's persistent storage.
- Test your applications with a COPY of your data.
Do not test the programs on the real live data onsdX.- Try out your USB keyboards and mice.
- Try out your printer(s).
- Access your favorite websites and download files.
- Test suspend and resume.
- Test Fn keys for volume and brightness.
- Make a keyboard shortcut and ensure it works ok.
- Test
systemd,cronand other system utilities. - If you've written scripts, copy them over and test them.
- Test
xrandrfunctions you have used before. - Run CPU & RAM stress tests. System benchmarks might be helpful too.
- Remember 18.04 uses Unity 7.5 but 16.04 uses Unity 7.4 I think.
- Of course you should test Anything else you can think of
answered Mar 14 at 1:56
WinEunuuchs2Unix
36k759134
This will not work because the update has nothing to do with ubuntu but with a theme, and ubuntu 18.04 is BETA so it would NEVER need that for an update.
– Yoran Jansen
Mar 17 at 12:01
add a comment |Â
up vote
0
down vote
Best guess
My best guess is you suffered a bug fix for this bug: Want to update from 17.04 to 18.04, but do-release-upgrade fails.
Essentially the OP was using 17.04, wanted to upgrade to 17.10 but it took him/her to 18.04 which is invalid because it's not an officially sanctioned version yet.
It would appear rather than taking away the upgrade to 18.04 option the programmers simply suppressed the option from upgrading to 18.04. That said I would only upgrade to 18.04 in a quarantined environment (separate partition / non production) and extensive testing. Some ideas:
- Create a 18.04 Live USB with persistent storage.
- Boot from the USB and select "Try before Installing".
- Install your mission critical applications to the USB's persistent storage.
- Test your applications with a COPY of your data.
Do not test the programs on the real live data onsdX.- Try out your USB keyboards and mice.
- Try out your printer(s).
- Access your favorite websites and download files.
- Test suspend and resume.
- Test Fn keys for volume and brightness.
- Make a keyboard shortcut and ensure it works ok.
- Test
systemd,cronand other system utilities. - If you've written scripts, copy them over and test them.
- Test
xrandrfunctions you have used before. - Run CPU & RAM stress tests. System benchmarks might be helpful too.
- Remember 18.04 uses Unity 7.5 but 16.04 uses Unity 7.4 I think.
- Of course you should test Anything else you can think of
answered Mar 14 at 1:56
WinEunuuchs2Unix
36k759134
This will not work because the update has nothing to do with ubuntu but with a theme, and ubuntu 18.04 is BETA so it would NEVER need that for an update.
– Yoran Jansen
Mar 17 at 12:01
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Best guess
My best guess is you suffered a bug fix for this bug: Want to update from 17.04 to 18.04, but do-release-upgrade fails.
Essentially the OP was using 17.04, wanted to upgrade to 17.10 but it took him/her to 18.04 which is invalid because it's not an officially sanctioned version yet.
It would appear rather than taking away the upgrade to 18.04 option the programmers simply suppressed the option from upgrading to 18.04. That said I would only upgrade to 18.04 in a quarantined environment (separate partition / non production) and extensive testing. Some ideas:
- Create a 18.04 Live USB with persistent storage.
- Boot from the USB and select "Try before Installing".
- Install your mission critical applications to the USB's persistent storage.
- Test your applications with a COPY of your data.
Do not test the programs on the real live data onsdX.- Try out your USB keyboards and mice.
- Try out your printer(s).
- Access your favorite websites and download files.
- Test suspend and resume.
- Test Fn keys for volume and brightness.
- Make a keyboard shortcut and ensure it works ok.
- Test
systemd,cronand other system utilities. - If you've written scripts, copy them over and test them.
- Test
xrandrfunctions you have used before. - Run CPU & RAM stress tests. System benchmarks might be helpful too.
- Remember 18.04 uses Unity 7.5 but 16.04 uses Unity 7.4 I think.
- Of course you should test Anything else you can think of
answered Mar 14 at 1:56
WinEunuuchs2Unix
36k759134
Best guess
My best guess is you suffered a bug fix for this bug: Want to update from 17.04 to 18.04, but do-release-upgrade fails.
Essentially the OP was using 17.04, wanted to upgrade to 17.10 but it took him/her to 18.04 which is invalid because it's not an officially sanctioned version yet.
It would appear rather than taking away the upgrade to 18.04 option the programmers simply suppressed the option from upgrading to 18.04. That said I would only upgrade to 18.04 in a quarantined environment (separate partition / non production) and extensive testing. Some ideas:
- Create a 18.04 Live USB with persistent storage.
- Boot from the USB and select "Try before Installing".
- Install your mission critical applications to the USB's persistent storage.
- Test your applications with a COPY of your data.
Do not test the programs on the real live data onsdX.- Try out your USB keyboards and mice.
- Try out your printer(s).
- Access your favorite websites and download files.
- Test suspend and resume.
- Test Fn keys for volume and brightness.
- Make a keyboard shortcut and ensure it works ok.
- Test
systemd,cronand other system utilities. - If you've written scripts, copy them over and test them.
- Test
xrandrfunctions you have used before. - Run CPU & RAM stress tests. System benchmarks might be helpful too.
- Remember 18.04 uses Unity 7.5 but 16.04 uses Unity 7.4 I think.
- Of course you should test Anything else you can think of
answered Mar 14 at 1:56
WinEunuuchs2Unix
36k759134
answered Mar 14 at 1:56
WinEunuuchs2Unix
36k759134
answered Mar 14 at 1:56
WinEunuuchs2Unix
36k759134
answered Mar 14 at 1:56
WinEunuuchs2Unix
36k759134
36k759134
This will not work because the update has nothing to do with ubuntu but with a theme, and ubuntu 18.04 is BETA so it would NEVER need that for an update.
– Yoran Jansen
Mar 17 at 12:01
add a comment |Â
This will not work because the update has nothing to do with ubuntu but with a theme, and ubuntu 18.04 is BETA so it would NEVER need that for an update.
– Yoran Jansen
Mar 17 at 12:01
This will not work because the update has nothing to do with ubuntu but with a theme, and ubuntu 18.04 is BETA so it would NEVER need that for an update.
– Yoran Jansen
Mar 17 at 12:01
This will not work because the update has nothing to do with ubuntu but with a theme, and ubuntu 18.04 is BETA so it would NEVER need that for an update.
– Yoran Jansen
Mar 17 at 12:01
add a comment |Â
up vote
0
down vote
accepted
Answer:
I used a ppa that was no longer there, but had an update. For some reason it didn't update that into the cache, however after removing the ppa it did not longer have an 'impossible' update.
answered Apr 28 at 12:37
Yoran Jansen
5121520
add a comment |Â
up vote
0
down vote
accepted
Answer:
I used a ppa that was no longer there, but had an update. For some reason it didn't update that into the cache, however after removing the ppa it did not longer have an 'impossible' update.
answered Apr 28 at 12:37
Yoran Jansen
5121520
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Answer:
I used a ppa that was no longer there, but had an update. For some reason it didn't update that into the cache, however after removing the ppa it did not longer have an 'impossible' update.
answered Apr 28 at 12:37
Yoran Jansen
5121520
Answer:
I used a ppa that was no longer there, but had an update. For some reason it didn't update that into the cache, however after removing the ppa it did not longer have an 'impossible' update.
answered Apr 28 at 12:37
Yoran Jansen
5121520
answered Apr 28 at 12:37
Yoran Jansen
5121520
answered Apr 28 at 12:37
Yoran Jansen
5121520
answered Apr 28 at 12:37
Yoran Jansen
5121520
5121520
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%2f1014643%2fapt-says-there-is-1-not-updated-but-there-are-no-updates%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
You may want to try running
apt clean && apt autoclean...– NerdOfCode
Mar 13 at 17:51
@WinEunuuchs2Unix Fixed it
– Yoran Jansen
Mar 17 at 12:02