File: bug

package info (click to toggle)
evms 2.5.2-1.sarge2
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 14,248 kB
  • ctags: 15,488
  • sloc: ansic: 201,340; perl: 12,421; sh: 4,262; makefile: 1,516; yacc: 316; sed: 16
file content (45 lines) | stat: -rw-r--r-- 1,083 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
#!/bin/bash -e

# reportbug #169495
if [ -z "$YESNO" ]; then
  YESNO=$"yYnN"
fi

cat <<EOF


I can automatically include information about your EVMS configuration
in your bug report.  This information will help to diagnose your
problem.

EOF

if [ -f /var/log/evms-engine.log ]; then
  cat <<EOF


When the EVMS engine runs (whether the GUI, ncurses, CLI, etc.), it records a
log file for the session.  If you are experiencing a problem within the engine,
you should include this log file in your report.

I can automatically include your most recent log file.  If the problem did not
occur the last time you ran the engine, you should run it now so that I can
include a log file which demonstrates the problem.

EOF

  yesno "May I include your most recent EVMS engine log in the bug report? " yep
  if [ "$REPLY" = "yep" ]; then
    echo "engine log:" >&3
    echo "-----------" >&3
    cat /var/log/evms-engine.log >&3
    echo
  fi
fi

yesno "May I include your EVMS configuration data in the bug report? " yep

if [ "$REPLY" = "yep" ]; then
  evms_gather_info >&3
  echo >&3
fi