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

Bug#568141: marked as done (release.debian.org: Latest point release hard to follow / confusing)

Your message dated Sat, 14 May 2011 01:31:16 +0200
with message-id <20110513233116.GA32126@radis.liafa.jussieu.fr>
and subject line Re: Bug#568141: release.debian.org: Latest point release hard to follow / confusing
has caused the Debian Bug report #568141,
regarding release.debian.org: Latest point release hard to follow / confusing
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.)


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

Recently a point release was shipped (being installed as I type). At
the time of releasing (i.e. when apt saw it) no notice was available
on www.debian.org to verify what was upgraded and the version.

Now the News is up (News/2010/20100130.wml) and since it unfortunately
as usual does not mention the new version of each software (which is
done in every DSA) I as usual went to http://packages.debian.org/XXX
for each package XXX to look for the latest version but to my suprise
I saw the following:

Package/Version shipped vs. http://packages.debian.org/

python-xml (0.8.4-10.1+lenny1) vs. 0.8.4-10.1   
wireshark (1.0.2-3+lenny8) vs. 1.0.2-3+lenny7   
xfs (1:1.0.8-2.2+lenny1) vs. 1:1.0.8-2.1        
kazehakase (0.5.4-2.2+lenny1) vs. 0.5.4-2.2     
base-files (5lenny5) vs. 5lenny4                
...

Obviously different from previous updates this page is out of date. I
was almost considering stopping the update when I checked
http://packages.qa.debian.org/XXX instead (how am I to know that this
page is correct???). 

Here for all packages fortunately the latest version was printed, but
again confusingly. For example, for dhcp3 in column stable the latest
version was given but not in the column stable-sec, while for wireshare 
it was reversed, i.e. the latest version was in stable-sec not stable
column.

Upgrading a system is a delicate process. Since there is no DSA I've to
rely on www.debian.org that everything is ok. A very basic check is
the version number. For this update it was *hard* to check it.

My suggestion: First update www.debian.org (*with* version numbers)
and then push the update out to the mirrors. And secondly unify the
versions given in http://packages.debian.org/XXX and
http://packages.qa.debian.org/XXX (and in the latter also where the
latest one is printed).

-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.27.10-grsec-cz03
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/bash
-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
On Tue, Feb  2, 2010 at 19:15:01 +0100, Helge Kreutzmann wrote:

> Recently a point release was shipped (being installed as I type). At
> the time of releasing (i.e. when apt saw it) no notice was available
> on www.debian.org to verify what was upgraded and the version.
> 
So don't upgrade until you get the announcement.  Closing this bug.

Cheers,
Julien

--- End Message ---
Reply to: