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

Bug#631119: marked as done (release.debian.org: make it possible to view why a transition is happening)

Your message dated Mon, 20 May 2013 21:14:29 +0100
with message-id <1369080869.11930.14.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#631119: release.debian.org: make it possible to view why a transition is happening
has caused the Debian Bug report #631119,
regarding release.debian.org: make it possible to view why a transition is happening
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.)


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

*** Please type your report below this line ***

Hi all,
As a user curious about transition I find it hard to find information
about why a particular transition happens.
http://release.debian.org/transitions/ . While
release.debian.org/transitions just tracks the transition, I wish it
could also take if any transition bugs are filed so users do know why
a transition is taking .

I know one could track
http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=release.debian.org#_0_6_4
but it feels like a long-winded way of doing things. I wish the bug
about 'x' package transition could also be shown alongwith the
transition progress.

For e.g. let's say libnotify 0.7 gives an idea about libnotify 0.7
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622363

while the page http://release.debian.org/transitions/html/libnotify.html
gives progress of the same.

If the page also includes the bug involved it would be nicer.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'),
(1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17

--- End Message ---
--- Begin Message --- 
On Mon, 2011-06-20 at 19:44 +0530, shirish शिरीष wrote:
> As a user curious about transition I find it hard to find information
> about why a particular transition happens.
> http://release.debian.org/transitions/ . While
> release.debian.org/transitions just tracks the transition, I wish it
> could also take if any transition bugs are filed so users do know why
> a transition is taking .

This has been implemented for a while - see
http://release.debian.org/transitions/html/libcogl12.html for example.

Regards,

Adam

--- End Message ---
Reply to: