"Exception: No date tag found" in ubuntu-support-status

Bug #622489 reported by Tomas Cassidy
98
This bug affects 19 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
Medium
Robert Roth
Lucid
Won't Fix
Low
Unassigned

Bug Description

Binary package hint: update-manager

I got the following error when running ubuntu-support-status:

$ ubuntu-support-status
Traceback (most recent call last):
  File "/usr/bin/ubuntu-support-status", line 105, in <module>
    (still_supported, support_str) = get_maintenance_status(cache, pkg.name, support_tag)
  File "/usr/bin/ubuntu-support-status", line 37, in get_maintenance_status
    raise Exception("No date tag found")
Exception: No date tag found

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: update-manager-core 1:0.134.10
ProcVersionSignature: Ubuntu 2.6.32-24.41-server 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-server x86_64
Architecture: amd64
Date: Mon Aug 23 10:23:48 2010
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager

Related branches

Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :
Revision history for this message
Krzysztof Klimonda (kklimonda) wrote :

I can confirm that. What seems to be happening is that some packages (in my case linux-image-2.6.32-23-virtual) are not in lucid pocket but only in lucid-updates but ubuntu-support-status checks them all against lucid pocket:
(from /usr/bin/ubuntu-support-status)
    # try to figure out the support dates of the release and make
    # sure to look only for stuff in "Ubuntu" and "distro_codename"
    # (to exclude stuff in ubuntu-updates for the support time
    # calculation because the "Release" file time for that gets
    # updated regularly)
    releasef = get_release_filename_for_pkg(cache, pkgname,
                                            "Ubuntu", CODENAME)

in this case get_release_filename_for_pkg returns None and so does the following call to get_release_date_from_release_file. Because of that time_t is unset and exception raised.

Changed in update-manager (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Anakin Starkiller (sunrider) wrote :

Any workaround ?

Revision history for this message
FooBar (ubuntu-mailinator-deactivatedaccount) wrote :

Workaround:

@@ -30,6 +30,9 @@
     # updated regularly)
     releasef = get_release_filename_for_pkg(cache, pkgname,
                                             "Ubuntu", CODENAME)
+ if not releasef:
+ releasef = get_release_filename_for_pkg(cache, pkgname,
+ "Ubuntu", CODENAME + "-updates")
     time_t = get_release_date_from_release_file(releasef)
     # check the release date and show support information
     # based on this

Revision history for this message
FooBar (ubuntu-mailinator-deactivatedaccount) wrote :

Workaround

tags: added: patch
Robert Roth (evfool)
Changed in update-manager (Ubuntu):
assignee: nobody → Robert Roth (evfool)
status: Triaged → In Progress
Robert Roth (evfool)
Changed in update-manager (Ubuntu):
status: In Progress → Fix Committed
Robert Roth (evfool)
Changed in update-manager (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Jørgen Hermanrud Fjeld (jorgen.fjeld) wrote :

This bug is still found in version 1:0.134.12.1 found in Ubuntu 10.04 LTS (lucid).
Are there any plans for a fix for lucid?

Changed in update-manager (Ubuntu Lucid):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in update-manager (Ubuntu Lucid):
status: Triaged → Won't Fix
Revision history for this message
Kemel Zaidan aka Legendario (kemelzaidan) wrote :

Having this same problem now on trusty 14.04.3

Revision history for this message
Brian Murray (brian-murray) wrote :

@Kemel - That is probably bug 1503979.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Patches

Remote bug watches

Bug watches keep track of this bug in other bug trackers.