NN_il_Confusionario on 14/04/08 11:55, wrote:
On Mon, Apr 14, 2008 at 10:27:02AM +0100, Adam Hardy wrote:
NN_il_Confusionario on 13/04/08 17:11, wrote:
On Sun, Apr 13, 2008 at 01:16:37PM +0100, Adam Hardy wrote:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464402
Tags: moreinfo;
I don't
On Mon, Apr 14, 2008 at 10:27:02AM +0100, Adam Hardy wrote:
> NN_il_Confusionario on 13/04/08 17:11, wrote:
> >On Sun, Apr 13, 2008 at 01:16:37PM +0100, Adam Hardy wrote:
> >>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464402
> > Tags: moreinfo;
> I don't see how you know this person is the m
Sven Joachim on 14/04/08 10:51, wrote:
On 2008-04-14 11:19 +0200, Adam Hardy wrote:
Paul Johnson on 13/04/08 18:43, wrote:
On Sunday 13 April 2008 05:16:37 am Adam Hardy wrote:
How do I do that - where do I look?
Email [EMAIL PROTECTED]
That gives me the following reply:
<[EMAIL PROTEC
On 2008-04-14 11:19 +0200, Adam Hardy wrote:
> Paul Johnson on 13/04/08 18:43, wrote:
>> On Sunday 13 April 2008 05:16:37 am Adam Hardy wrote:
>>
>>> How do I do that - where do I look?
>>
>> Email [EMAIL PROTECTED]
>>
>
> That gives me the following reply:
>
> <[EMAIL PROTECTED]>
>
> SMTP error
NN_il_Confusionario on 13/04/08 17:11, wrote:
On Sun, Apr 13, 2008 at 01:16:37PM +0100, Adam Hardy wrote:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464402
From that page:
Tags: moreinfo;
[snip]
Works for me.
[snip]
Of course, if we *do* find out which package is at fault w
Paul Johnson on 13/04/08 18:43, wrote:
On Sunday 13 April 2008 05:16:37 am Adam Hardy wrote:
How do I do that - where do I look?
Email [EMAIL PROTECTED]
That gives me the following reply:
<[EMAIL PROTECTED]>
SMTP error from remote server after RCPT command:
host bugs.debian.org[140.211
On Sunday 13 April 2008 05:16:37 am Adam Hardy wrote:
> How do I do that - where do I look?
Email [EMAIL PROTECTED]
--
Paul Johnson
[EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part.
Adam Hardy wrote:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464402
>
> I can do bugreport emails, but I really would like to find out more about
> this bug in openoffice, mainly whether it's fixed.
>
> How do I do that - where do I look?
Look at the picture on the right hand side which
On Sun, Apr 13, 2008 at 01:16:37PM +0100, Adam Hardy wrote:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464402
>From that page:
Tags: moreinfo;
[snip]
Works for me.
[snip]
Of course, if we *do* find out which package is at fault we should fix
OOos dependencies, but...
Which m
On 13 Sep 2003 16:30:11 -0600,
Andreas J. Guelzow wrote:
>
> On Fri, 2003-09-12 at 18:29, csj wrote:
> > At Fri, 12 Sep 2003 18:18:39 +0100,
>
> > Is it that much work to, as Osamu Aoki said, change the
> > priority or downgrade the bug? Then I'd know how I stand WRT
> > package. I know its lim
On Fri, 2003-09-12 at 18:29, csj wrote:
> At Fri, 12 Sep 2003 18:18:39 +0100,
> Is it that much work to, as Osamu Aoki said, change the priority
> or downgrade the bug? Then I'd know how I stand WRT package. I
> know its limits, especially when the author or maintainer rants
> "Yyyou moron, that
On Sat, Sep 13, 2003 at 08:29:42AM +0800, csj wrote:
> At Fri, 12 Sep 2003 18:18:39 +0100,
> Colin Watson wrote:
> > That's entirely up to the maintainer of the package and/or any
> > other random people who happen to look at it. Forget policy
> > here, it's a matter of people having time and inter
On Sat, Sep 13, 2003 at 08:29:42AM +0800, csj wrote:
> At Fri, 12 Sep 2003 18:18:39 +0100, Colin Watson wrote:
> >
> > That's entirely up to the maintainer of the package and/or any
> > other random people who happen to look at it. Forget policy
> > here, it's a matter of people having time and in
At Fri, 12 Sep 2003 18:18:39 +0100,
Colin Watson wrote:
>
> On Fri, Sep 12, 2003 at 04:02:11PM +0800, csj wrote:
> > I'm just curious about Debian's "bug" policy.
> >
> > I know that some bugs aren't fixable (because either they're
> > too expensive to fix or upstream thinks they're a "feature").
At Fri, 12 Sep 2003 20:38:20 -0400,
Greg Folkert wrote:
>
> [1 ]
> On Fri, 2003-09-12 at 04:02, csj wrote:
> > I'm just curious about Debian's "bug" policy.
> >
> > I know that some bugs aren't fixable (because either they're
> > too expensive to fix or upstream thinks they're a "feature").
> >
On Fri, 2003-09-12 at 04:02, csj wrote:
> I'm just curious about Debian's "bug" policy.
>
> I know that some bugs aren't fixable (because either they're too
> expensive to fix or upstream thinks they're a "feature"). But
> how are bug reports resolved in the Debian bug system? I just
> checked m
On Fri, Sep 12, 2003 at 04:02:11PM +0800, csj wrote:
> I'm just curious about Debian's "bug" policy.
>
> I know that some bugs aren't fixable (because either they're too
> expensive to fix or upstream thinks they're a "feature"). But
> how are bug reports resolved in the Debian bug system? I jus
On Fri, Sep 12, 2003 at 04:02:11PM +0800, csj wrote:
> I'm just curious about Debian's "bug" policy.
>
> I know that some bugs aren't fixable (because either they're too
> expensive to fix or upstream thinks they're a "feature"). But
> how are bug reports resolved in the Debian bug system? I jus
Richard Hector said:
> Other unixes seem to manage to dump to the swap partition - is there some
> significant difference that make this impractical/more dangerous for
> Linux?
even better, I've had my solaris boxes able to panic and dump their
"oops" messages to a syslog server before rebooting!
On Tue, 2002-11-19 at 22:17, Rob Weir wrote:
> On Wed, Nov 20, 2002 at 03:03:59PM +1300, Richard Hector wrote:
> > On Tue, 2002-11-19 at 21:36, Rob Weir wrote:
> > >
> > > When the kernel crashes, there's no way for it to be able to know that
> > > it's state is consistent. Because of this, it's
On Wed, Nov 20, 2002 at 03:03:59PM +1300, Richard Hector wrote:
> On Tue, 2002-11-19 at 21:36, Rob Weir wrote:
> >
> > When the kernel crashes, there's no way for it to be able to know that
> > it's state is consistent. Because of this, it's not safe for it to try
> > to write to disks (since it
On Tue, 2002-11-19 at 21:36, Rob Weir wrote:
>
> When the kernel crashes, there's no way for it to be able to know that
> it's state is consistent. Because of this, it's not safe for it to try
> to write to disks (since it could easily destroy everything on the
> disks).
>
> The best it can mana
On Mon, Nov 18, 2002 at 02:17:41PM -0500, [EMAIL PROTECTED] wrote:
^^^
Maybe you could have something
a little more friendly as your
on Mon, Nov 19, 2001 at 03:54:37PM +0100, Josef Dalcolmo ([EMAIL PROTECTED])
wrote:
> I know I am supposed to check first if a bug has already been
> registered, before submitting a new message. But how does one do that,
> if one cannot search the bug reports by content? I cannot know the
> number
%% Josef Dalcolmo <[EMAIL PROTECTED]> writes:
jd> I know I am supposed to check first if a bug has already been
jd> registered, before submitting a new message. But how does one do
jd> that, if one cannot search the bug reports by content? I cannot
jd> know the number, or author of a bug r
On Apr 12, Francesco Tapparo wrote
> Hi all,
> I have a proble with the Debian bug tracking system.
> I have found a minor bugs in some packages, and I have used "bug" to
> report the error. But I have not received the automatical answer from the
> bug tracking system. I like to know what's is wron
26 matches
Mail list logo
