Prompted about New Release for 13.04 again after dist-upgrade and a restart

Refering to the link:

http://ubuntuforums.org/showthread.php?t=2138991

multible users are affected.

In respect to this the status of the report switched to confirmed.

Normally I would ask you to provide the logs for ubuntu-release-upgrader and set the status of the report in meantime to incomplete, but in this case it semms to be not so much necessary.

@ Kyle

If you want to help you may follow this text:

Hi Kyle,

sorry for the inconvenience. Those problems are verry neasty.

Unfortunately, a little more help from you ins needed.

Please use

apport-collect 1173209

from command line to bring up all needed informations/logs here.

If apport collect is disclaiming about missing libraries, please install them and rerun the command until all works.

greetings

melchiaros

P.S:

 If and only if it not possible to get it managed with apport-collect you can also bring up the logs manually from

/var/log/dist-upgrade

folder.

Please attach them one by one here. For the apt-clone file in the log folder you need root proviledges to upload it. This is one of the causes why it is better to use apport-collect.

BTW: It is recommend for futhur reports to use the command

ubuntu-bug <PACKAGENAME>

for reporting. This will bring up all needed information up in the first reporting step. -> Less work for all.

Attaching my logs as indicated. Since my ubuntu server is running with a GUI, lynx will not run the apport-collect command to completion; fyi.

grrrrr,

Kyle here are more reports arround than hands. I was not jocking as I ask you to attach one by one.

Anyway, this time I do the job.

Thanks for providing

Sorry for the inconvenience; I would have been happy to make it right.

o.K Kyle,

may be you are willing to make a time invest in a other part of Ubuntu. Help out where it is needed.

greetings and nice evening if this is correct for your timezone

Check to see if the file '/var/lib/ubuntu-release-upgrader/release-upgrade-available' exists. If so you can remove it with no harm. However, it'd be interesting to know if running '/usr/lib/ubuntu-release-upgrader/release-upgrade-motd' removes the release-upgrade-available file.

Does the file exist? Yes
> file /var/lib/ubuntu-release-upgrader/release-upgrade-available
/var/lib/ubuntu-release-upgrader/release-upgrade-available: ASCII text

Does release-upgrade-motd remove this file?
> /usr/lib/ubuntu-release-upgrader/release-upgrade-motd
New release '13.04' available.
Run 'do-release-upgrade' to upgrade to it.

> file /var/lib/ubuntu-release-upgrader/release-upgrade-available
/var/lib/ubuntu-release-upgrader/release-upgrade-available: ASCII text

SO, running release-upgrade-motd doesn't not remove the file; BUT, manually removing that file removes the message at startup

Perhaps the release upgrader should remove the file /var/lib/ubuntu-release-upgrader/release-upgrade-available after the upgrade has completed.

Yeah, looking at /usr/lib/ubuntu-release-upgrader/release-upgrade-motd, it never expires the cache if it's non-zero-length, which could also pose a problem if we want to allow people to skip releases in the future, as it would never update from, say, 12.10 to 13.04 or whatever.

Definitely an issue in this case, though, as it will never go back to zero-length after an upgrade, so it should definitely be either deleted or emptied on upgrade.

Okay, I've committed a couple of fixes for this issue to ubuntu-release-upgrader/trunk.

I'd like Adam to eyeball and release them.

This bug was fixed in the package ubuntu-release-upgrader - 1:0.195

---------------
ubuntu-release-upgrader (1:0.195) saucy; urgency=low

  [ Dustin Kirkland ]
  * debian/release-upgrade-motd: LP: #1173209
    - recheck release upgrade once-a-day, even if stamp file is
      already populated
    - this partially fixes the sticky "upgrade available" message,
      after successfully upgrading, even if the stamp is not removed
  * DistUpgrade/DistUpgradeController.py: LP: #1173209
    - remove the upgrade-available flag, on upgrade completion
  * debian/ubuntu-release-upgrader-core.postinst: LP: #1173209
    - clear the upgrade-available flag, on postinst; it will automatically
      repopulate, if necessary

  [ Brian Murray ]
  * DistUpgradeCache.py: encode error message as UTF-8 (LP: #1177821)
  * DistUpgradeCache.py: double size estimate need in boot (LP: #1173468)
 -- Brian Murray <email address hidden> Fri, 17 May 2013 09:09:01 -0700

Hello Kyle, or anyone else affected,

Accepted ubuntu-release-upgrader into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:0.192.11 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of ubuntu-release-upgrader from raring-proposed was performed and bug 1185581 was found. Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the "verification-failed" tag from this bug report and tag 1185581 "bot-stop-nagging". Thanks!

Bug 1185581 is unrelated to being prompted to upgrade after having just upgraded.

As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of ubuntu-release-upgrader from raring-proposed was performed and bug 1187648 was found. Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the "verification-failed" tag from this bug report and tag 1187648 "bot-stop-nagging". Thanks!

I performed a distribution upgrade from 12.10 to 13.04 and confirm that I was not present with a dialog indicating that 13.04 was available. Additionally, the file /var/lib/ubuntu-release-upgrader/release-upgrade-available was empty.

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

This bug was fixed in the package ubuntu-release-upgrader - 1:0.192.11

---------------
ubuntu-release-upgrader (1:0.192.11) raring-proposed; urgency=low

  [ Dustin Kirkland ]
  * debian/release-upgrade-motd: LP: #1173209
    - recheck release upgrade once-a-day, even if stamp file is
      already populated
    - this partially fixes the sticky "upgrade available" message,
      after successfully upgrading, even if the stamp is not removed
  * DistUpgrade/DistUpgradeController.py: LP: #1173209
    - remove the upgrade-available flag, on upgrade completion
 -- Brian Murray <email address hidden> Mon, 20 May 2013 09:58:36 -0700