On Friday 05 January 2007 02:30, Joey Hess wrote:
Well, I'd hate to miss the syslog, it's invaluable when there's a
problem. Perhaps the last N lines could be included, where N is
sufficiently large to include most syslogs.
Is it really that important?
It is only (optionally!) included if
Frans Pop wrote:
Is it really that important?
It is only (optionally!) included if reportbug is used, which means that
the install was more or less successful.
reportbug is able to pull the logs from a running d-i instance. Granted
I don't know if a lot of people use it that way..
(Maybe we
Joey Hess wrote:
reportbug is able to pull the logs from a running d-i instance. Granted
I don't know if a lot of people use it that way..
Probably none, since I thought I'd implemented it, but have apparently
not yet. :-)
--
see shy jo
signature.asc
Description: Digital signature
Frans Pop wrote:
Yes, I suggested the same in my other mail, but I'd disable syslog as well
as its size is indeterminate and so could still result in us missing the
installation report.
Well, I'd hate to miss the syslog, it's invaluable when there's a
problem. Perhaps the last N lines could
Frans Pop wrote:
Joey, do you have any ideas how to resolve this?
AFAIK it's not possible to attach things to messages using the current
reportbug interface.
--
see shy jo
signature.asc
Description: Digital signature
On Tuesday 02 January 2007 21:06, you wrote:
Frans Pop wrote:
Joey, do you have any ideas how to resolve this?
AFAIK it's not possible to attach things to messages using the current
reportbug interface.
I've taken a look at reportbug and it looks like you are right. I also
don't see a
Frans Pop wrote:
Another example: http://bugs.debian.org/405169
and I have no idea how many other reports we've not seen on the list...
I really feel we are losing too many bug reports through this and am
therefore raising severity to serious.
I don't think that the serious severity is
On Tuesday 02 January 2007 22:23, Joey Hess wrote:
I don't think that the serious severity is approprate for t his report,
unless it's causing actual data loss (if so, it should be grave). Posts
not getting through to a mailing list is not data loss, if they make it
to the BTS.
IMO it is
severity 403346 serious
thanks
Another example: http://bugs.debian.org/405169
and I have no idea how many other reports we've not seen on the list...
I really feel we are losing too many bug reports through this and am
therefore raising severity to serious.
Joey, do you have any ideas how to
Op 01-01-2007 om 13:12 schreef Frans Pop:
severity 403346 serious
second!
Another example: http://bugs.debian.org/405169
and I have no idea how many other reports we've not seen on the list...
Initial _long_ report seen on the list
402956
403778
403904
all got a follow-up that don't need
Op 16-12-2006 om 13:12 schreef Frans Pop:
Two possible solutions are:
- not including files that can get huge by default
Or even not including any file by default.
Bugreport should be opened with a small message.
That allows easy processing (and is a minimum load to mailinglists)
-
Package: installation-report
Version: 2.24
Severity: important
Because installation-report attaches all log files uncompressed, we are
missing _a lot_ of installation reports on the debian-boot list.
The mailing lists have a default size limit set of 102400. For debian-boot
this has already
12 matches
Mail list logo
