[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#611372: marked as done (qa.debian.org: Wrong version display in new upstream todo summary)

Your message dated Wed, 25 Jan 2012 17:41:15 +0100
with message-id <CA+7wUswaugo8K5oT=x=6ORmKOGMWGtvnFapayadPWFWtLmPsbQ@mail.gmail.com>
and subject line 
has caused the Debian Bug report #611372,
regarding qa.debian.org: Wrong version display in new upstream todo summary
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
611372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611372
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qa.debian.org
Severity: normal


hi,


for some reason the version number display on the todo section from page:

http://packages.qa.debian.org/d/dicom3tools.html

displays :

A new upstream version is available: 1.0~20100815, you should consider packaging it.

while if one click on the link, the next page properly display the new upstream version:

http://dehs.alioth.debian.org/report.php?package=dicom3tools

Name: dicom3tools
Pop Inst:
Upstream version: 1.0~20101204
Source download: dicom3tools_1.00.snapshot.20101204.tar.bz2
Debian version: 1.0~20100510-1
Last time checked: 2011-01-26 06:43:43
Last time found up to date: 2010-08-15 06:28:27

Thanks !

-- System Information:
Debian Release: 6.0
  APT prefers testing
  APT policy: (200, 'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
Closing bug. Seems to be fixed now.

-- 
Mathieu

--- End Message ---
Reply to: