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 the bug comes in because /tmp is full or a loop mount - like which havp use it - is corrupt. I also suggest the content of /etc/mtab to see the mount options. But and this is the only way it can be done: let reportbug ask the user if those information are necessary and is reportbug allowed to collect and this (with an explicit note that the information will be public available). On the other hand you to analyse the needs of the reported package. Maybe with rules in debian/control like what is needed to build the package, there could be a line for what information is needed for a reliable bugreport. Only my 2 cents, Björn -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/c4ca7ed91003152320j20fd9d99y214247c176884...@mail.gmail.com
