Re: Suggestions to fix #433462 (add free space info to reportbug)

2010-03-18 Thread Yves-Alexis Perez
On mer., 2010-03-17 at 17:26 +0100, Goswin von Brederlow wrote: On the other hand including free space information will be difficult to handle properly and possibly expose information the user considers private. But places where packages are supposed to write aren't that private. Usually /home

Re: Suggestions to fix #433462 (add free space info to reportbug)

2010-03-18 Thread Bastien ROUCARIES
On Thu, Mar 18, 2010 at 8:32 AM, Yves-Alexis Perez cor...@debian.org wrote: On mer., 2010-03-17 at 17:26 +0100, Goswin von Brederlow wrote: On the other hand including free space information will be difficult to handle properly and possibly expose information the user considers private. But

Re: Suggestions to fix #433462 (add free space info to reportbug)

2010-03-17 Thread Goswin von Brederlow
Sandro Tosi mo...@debian.org writes: Hi all, in bug #433462 there is a request to add free space information in reportbug standard info appended to bug report. It's a valid request, that I want to fulfill, but there are some aspects I'd like to discuss. If the software can not write data

Re: Suggestions to fix #433462 (add free space info to reportbug)

2010-03-16 Thread Bjoern Meier
hi, That said, what to report? Simply taking the output of df -h and attaching to reportbug template it's not what I like: there could be more partitions/disks not interesting for the report/system in that output, and I don't want to include them. I think you don't have any chance. What if

Re: Suggestions to fix #433462 (add free space info to reportbug)

2010-03-16 Thread Yves-Alexis Perez
On mar., 2010-03-16 at 00:12 +0100, Sandro Tosi wrote: - what free space information you'd like? (I'd propose only the count of free MB) - what directory to show in the report? (I'd propose /, /var, /usr, /etc if the latter 3 not in / but not going recursively under them) Imho you need to

Re: Suggestions to fix #433462 (add free space info to reportbug)

2010-03-16 Thread Petter Reinholdtsen
[Sandro Tosi] - what directory to show in the report? (I'd propose /, /var, /usr, /etc if the latter 3 not in / but not going recursively under them) I would suggest to include all directories relevant for the package at hand. Look at the file list for the package, and report all partitions

Re: Suggestions to fix #433462 (add free space info to reportbug)

2010-03-16 Thread Luca Niccoli
On 16 March 2010 00:12, Sandro Tosi mo...@debian.org wrote: That said, what to report? Simply taking the output of df -h and attaching to reportbug template it's not what I like: there could be more partitions/disks not interesting for the report/system in that output, and I don't want to

Re: Suggestions to fix #433462 (add free space info to reportbug)

2010-03-16 Thread Marc Haber
On Tue, 16 Mar 2010 00:12:22 +0100, Sandro Tosi mo...@debian.org wrote: in bug #433462 there is a request to add free space information in reportbug standard info appended to bug report. It's a valid request, that I want to fulfill, but there are some aspects I'd like to discuss. Please think

Re: Suggestions to fix #433462 (add free space info to reportbug)

2010-03-16 Thread Don Armstrong
On Tue, 16 Mar 2010, Sandro Tosi wrote: First of all, with your package maintainers hat on, what kind of information you'd like? only the value of free MB in the disk? total size, free size? also percentage? I think that from a bug report point-of-view, only the free megabytes value would do.

Re: Suggestions to fix #433462 (add free space info to reportbug)

2010-03-16 Thread Bastien ROUCARIES
On Tue, Mar 16, 2010 at 12:12 AM, Sandro Tosi mo...@debian.org wrote: Hi all, in bug #433462 there is a request to add free space information in reportbug standard info appended to bug report. It's a valid request, that I want to fulfill, but there are some aspects I'd like to discuss.

Suggestions to fix #433462 (add free space info to reportbug)

2010-03-15 Thread Sandro Tosi
Hi all, in bug #433462 there is a request to add free space information in reportbug standard info appended to bug report. It's a valid request, that I want to fulfill, but there are some aspects I'd like to discuss. First of all, with your package maintainers hat on, what kind of information