Wonderful, thanks Don! It is fixed now (actually been quite a while).
Best,
Hörmet
He who is worthy to receive his days and nights is worthy to receive all
else from you (and me).
-- The Prophet, Gibran
Kahlil
On Sun, Dec
On Fri, 01 Dec 2017, Hörmetjan Yiltiz wrote:
> Thanks! I missed that email on that page. I think we can discuss this
> in the community with them here (forwarding here to them).
> On Fri, Dec 1, 2017 at 9:19 AM, Jonathan Dowland wrote:
> > On Thu, Nov 30, 2017 at 10:48:26PM -0500, Hörmetjan Yilt
Thanks! I missed that email on that page. I think we can discuss this in
the community with them here (forwarding here to them).
Best,
Hörmet
He who is worthy to receive his days and nights is worthy to receive all
else from you (and me).
On Thu, Nov 30, 2017 at 10:48:26PM -0500, Hörmetjan Yiltiz wrote:
However, I think we should be consistent in the text, text's color, and the
graphs. The current set of colors doesn't look impressive as the blueish
green and cyan look quite close. Maybe we can do better [2]?
You raise great poi
we can do better [2]?
> *Total number of release-critical bugs:* 2111
> *Number that have a patch:* 257
> *Number that have a fix prepared and waiting to upload:* 41
> *Number that are being ignored:* 40
> *Number concerning the current stable release:* 480
> *Number concerning
On Tue, 27 Oct 2015, Hörmetjan Yiltiz wrote:
> I am now in a habit of checking the release-critical graph before doing
> upgrade (I don't upgrade very often) along with apt-list-bugs.
>
> We have a bug graphs for the past month, all history and the default. Do we
> also have one for the past year?
Hi all,
I am now in a habit of checking the release-critical graph before doing
upgrade (I don't upgrade very often) along with apt-list-bugs.
We have a bug graphs for the past month, all history and the default. Do we
also have one for the past year? Inferring from the month link then trying
sim
On Fri, 19 Sep 2008 13:19:06 -0400
Eric Gerlach <[EMAIL PROTECTED]> wrote:
...
> And kudos and thanks to Daniel Baumann for his work on open-vm-tools and
> about 150 other packages (wow). Had I looked harder at who the
> maintainer was and how many packages he maintained, I probably wouldn't
> h
Sven Joachim wrote:
P.S. If the maintainer of the package in question is reading this
right now, and you just haven't had a chance to get a
freeze-exception yet, that's okay! I just want to know that it
will make it for release! Thanks for your hard work!
You're being rather vague, mentioning
On 7/20/08, Jochen Schulz <[EMAIL PROTECTED]> wrote:
> Gerhard Horecky:
>>
>> I want to produce charts from time series like the rc bug graph in
>> http://bugs.debian.org/release-critical/.
>> I think the same tool is used for the popcon graphics.
>>
>> Can anybody give me please a hint which debia
Gerhard Horecky:
>
> I want to produce charts from time series like the rc bug graph in
> http://bugs.debian.org/release-critical/.
> I think the same tool is used for the popcon graphics.
>
> Can anybody give me please a hint which debian package is used for that?
It's most probably gnuplot.
J
Dear *,
I want to produce charts from time series like the rc bug graph in
http://bugs.debian.org/release-critical/.
I think the same tool is used for the popcon graphics.
Can anybody give me please a hint which debian package is used for that?
Many thanks in advance
Gerhard
P.S. Please CC me a
On Tue, Dec 20, 2005 at 09:05:12AM +0100, Johannes Wiedersich wrote:
> I have a question regarding the way bugs are dealt in debian stable.
>
> Will or should a package in sarge be updated, if it is unusable or has a
> serious bug, BEFORE etch becomes stable.
>
> Let's consider an example: say a
I have a question regarding the way bugs are dealt in debian stable.
Will or should a package in sarge be updated, if it is unusable or has a
serious bug, BEFORE etch becomes stable.
Let's consider an example: say an editor programme has a bug and crashes
regularly, loosing all text entered s
On Sun, 05 May 2002, Richard Kimber wrote:
> Can anyone point me to a definition of what a "release critical bug" is
> and who can determine whether a bug is one? I tried Google and Debian
aj, the release manager for woody is the only one who can determine whether
a bug is one. Others can follow t
gt; and who can determine whether a bug is one?
Determine whether it qualifies for one of those severities; see
http://www.debian.org/Bugs/Developer#severities .
> The number of release critical bugs has gone up by about 20 in the last
> week, yet some of these do not seem to me to be so important
On Sun, 5 May 2002 13:48:18 +0100
"Richard Kimber" <[EMAIL PROTECTED]> wrote:
> Can anyone point me to a definition of what a "release critical bug" is
http://www.debian.org/Bugs/Developer
Near the end of the "Severity levels" section.
--
Jamin W. Collins
--
To UNSUBSCRIBE, email to [EMAIL
Can anyone point me to a definition of what a "release critical bug" is
and who can determine whether a bug is one? I tried Google and Debian
searches, but couldn't find anything.
The number of release critical bugs has gone up by about 20 in the last
week, yet some of these do no
18 matches
Mail list logo
