diff options
| author | Vasudev Kamath <kamathvasudev@gmail.com> | 2015-11-10 10:23:38 +0530 |
|---|---|---|
| committer | Vasudev Kamath <kamathvasudev@gmail.com> | 2015-11-10 10:23:38 +0530 |
| commit | 7732bd6ac27f9995fa798ce22848794eab93c98d (patch) | |
| tree | ca2361efe534af6cc5a3c469d761ae796796ca9a | |
| parent | e17efaac433fab17d76f3ee5c5266df7e3879b58 (diff) | |
Copy fonts-roboto.bug-* files from fonts-android
| -rw-r--r-- | debian/fonts-roboto.bug-presubj | 15 | ||||
| -rwxr-xr-x | debian/fonts-roboto.bug-script | 3 |
2 files changed, 18 insertions, 0 deletions
diff --git a/debian/fonts-roboto.bug-presubj b/debian/fonts-roboto.bug-presubj new file mode 100644 index 0000000..9c35306 --- /dev/null +++ b/debian/fonts-roboto.bug-presubj @@ -0,0 +1,15 @@ +When reporting bugs in the fonts themselves (i.e. not just in the packaging) +please be sure to include the following information as far as applicable: + + - the versions of your libfreetype6, libxft2 and fontconfig packages + (these should be automatically appended by reportbug), + - all relevant configuration (especially anti-aliasing and hinting), + - the application being used, + - the affected unicode code points. + +It may also be helpful if you can provide a screen shot demonstrating the +problem, however please don't attach it to the initial bug report (especially +not if it is large). Please also try to make sure that it is actually a bug in +the fonts and not e.g. in freetype (if a problem appears after a freetype +update or if other fonts exhibit similar problems it is a sure sign that the +problem is in freetype). diff --git a/debian/fonts-roboto.bug-script b/debian/fonts-roboto.bug-script new file mode 100755 index 0000000..2dcb3c4 --- /dev/null +++ b/debian/fonts-roboto.bug-script @@ -0,0 +1,3 @@ +#!/bin/sh + +dpkg -l libfreetype6 libxft2 fontconfig >&3 |