orts and everything is
> rock-solid.
>
> But I am afraid that we have deviated from the original topic. If I
> understood Carl correctly - he was expressing his pain because of
> bureaucratic scrutiny of filing bugs to stable that brings absolutely no
> results.
"
ntioned - backports should be the first option to try
if you run stable. I run a few servers stable + backports and everything is
rock-solid.
But I am afraid that we have deviated from the original topic. If I
understood Carl correctly - he was expressing his pain because of
bureaucratic scr
On Du, 19 apr 20, 13:28:57, Ihor Antonov wrote:
>
> Reporting from Debian Sid, everything is quite stable. I do run ZFS on root
> and make snapshots prior to big upgrades as a pre-caution, but so far
> I did not have a reason to revert anything.
It's just a matter of time. Even if Debian does
reportbug to try a
newer version.
Why is reportbug even in Stable? Why not just replace it with a script that
says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously, that's
literally the Debian policy, that only security fixes are done in Stable.
Actually bugs o
gt; fiddling with pointlessly arcane configuration files that are sort of
> documented
> if you squint.
>
> (Yes, the pun on "bug" is deliberate.)
>
> Why is reportbug even in Stable? Why not just replace it with a script that
> says "Sorry, bugs in Stable are never fi
n the standard request from reportbug to try a
> newer version.
>
>> Why is reportbug even in Stable? Why not just replace it with a script
>> that
>> says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously,
>> that's
>> literally the Debi
> By? I'm guessing you mean the standard request from reportbug to try a
> newer version.
>
> > Why is reportbug even in Stable? Why not just replace it with a script
> > that
> > says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously,
> > th
On Sun, 2020-04-19 at 10:27 -0400, Carl Fink wrote:
> On Sun, Apr 19, 2020 at 09:51:02AM -0400, Jim Popovitch wrote:
>
> > What applications do you feel aren't up-to-date enough for your liking?
> > I'm genuinely curious.
>
> Mr. Heskett's comments made me want to tell him how to lower the CPU
On Sun, 19 Apr 2020 09:51:02 -0400
Jim Popovitch wrote:
> On Sun, 2020-04-19 at 09:43 -0400, Carl Fink wrote:
> > Why is reportbug even in Stable? Why not just replace it with a script that
> > says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously, that's
On Sun, Apr 19, 2020 at 09:51:02AM -0400, Jim Popovitch wrote:
> What applications do you feel aren't up-to-date enough for your liking?
> I'm genuinely curious.
Mr. Heskett's comments made me want to tell him how to lower the CPU usage
of BOINC. However, boinc-manager in Stable, at least on my
.
> Why is reportbug even in Stable? Why not just replace it with a script that
> says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously, that's
> literally the Debian policy, that only security fixes are done in Stable.
Actually bugs of severity "important&
On Sun, 2020-04-19 at 09:43 -0400, Carl Fink wrote:
> Why is reportbug even in Stable? Why not just replace it with a script that
> says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously, that's
> literally the Debian policy, that only security fixes are done
if you squint.
(Yes, the pun on "bug" is deliberate.)
Why is reportbug even in Stable? Why not just replace it with a script that
says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously, that's
literally the Debian policy, that only security fixes are done in Stabl
Bonjour
je m'interroge sur le processus debian qui permet d'intégrer des bugfix
dans 'stable' (en l'occurence Lenny)
certains bugs ont des correctifs connus (genre 2 lignes dans un script)
ou corrigés upstream (3.6.1 - 3.6.3) et ne sont toujours pas dans lenny,
parfois après un délai de
Hello,
I use debian stable on a couple servers,
and testing/unstable on my workstations.
works great.
The security updates are nice on both stable and unstable.
debian-security-announce is wonderful. (did i mention apt-get yet ? ;-)
However, when there is a problem on a package in stable
On Sun, May 02, 2004 at 06:34:18PM -0400, xavier wrote:
However, when there is a problem on a package in stable which
is not important enough to be updated, the package stays
as-is and information about this bug is difficult to retrieve.
That the package doesn't change is fine with me,
On Sun, May 02, 2004 at 11:44:32PM +0100, Colin Watson wrote:
This is being worked on (by me) in the bug tracking system. It's not an
easy task, and not well-solved by tags.
Thanks a lot, I guess you think that's an issue too.
Although I perfectly understand it is a hard problem to solve,
On Sun, May 02, 2004 at 06:59:10PM -0400, xavier wrote:
On Sun, May 02, 2004 at 11:44:32PM +0100, Colin Watson wrote:
This is being worked on (by me) in the bug tracking system. It's not an
easy task, and not well-solved by tags.
Thanks a lot, I guess you think that's an issue too.
18 matches
Mail list logo
