On Mon 20 Apr 2020 at 00:11:08 (-0700), Ihor Antonov wrote:
> On Sunday, 19 April 2020 23:30:43 PDT Andrei POPESCU wrote:
> > 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
On Sunday, 19 April 2020 23:30:43 PDT Andrei POPESCU wrote:
> 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
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
quest 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 Debian policy, that only security fixes are done in Stable.
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 nev
ng 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,
>> that's
>> lit
>
> 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,
&g
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 us
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&#
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 s
er 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 of severity &
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
ed
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 i
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.
>
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 sol
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,
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 whic
17 matches
Mail list logo
