[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

intel-gpu-tools: Changes to 'debian-unstable'



 debian/changelog |    7 +++++++
 debian/compat    |    2 +-
 debian/control   |   18 ++++++++++++++++--
 debian/rules     |    3 +++
 4 files changed, 27 insertions(+), 3 deletions(-)

New commits:
commit 4d37637a811235cb4cbeee650533757e68b72101
Author: Vincent Cheng <vcheng@debian.org>
Date:   Tue May 13 18:54:04 2014 -0700

    wrap-and-sort accidentally removed some build-deps...

diff --git a/debian/control b/debian/control
index d544ef3..d469485 100644
--- a/debian/control
+++ b/debian/control
@@ -16,7 +16,10 @@ Build-Depends:
  libpciaccess-dev (>= 0.10),
  libudev-dev,
  libxrandr-dev,
- pkg-config
+ pkg-config,
+ quilt,
+ swig2.0,
+ xutils-dev (>= 1:7.6+6)
 Standards-Version: 3.9.5
 Homepage: https://01.org/linuxgraphics/
 Vcs-Git: git://anonscm.debian.org/pkg-xorg/app/intel-gpu-tools.git

commit e611af5b896ba3df3e0829606f72891a52c2afb1
Author: Vincent Cheng <vcheng@debian.org>
Date:   Tue May 13 18:49:51 2014 -0700

    Add -dbg package for intel-gpu-tools

diff --git a/debian/changelog b/debian/changelog
index ff24084..0a68b73 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
 intel-gpu-tools (1.6-2) unstable; urgency=medium
 
   * Enable build hardening (bump dh compat level to 9).
+  * Strip debug symbols into separate intel-gpu-tools-dbg package.
 
  -- Vincent Cheng <vcheng@debian.org>  Tue, 13 May 2014 18:43:34 -0700
 
diff --git a/debian/control b/debian/control
index d5faf92..d544ef3 100644
--- a/debian/control
+++ b/debian/control
@@ -16,11 +16,7 @@ Build-Depends:
  libpciaccess-dev (>= 0.10),
  libudev-dev,
  libxrandr-dev,
- pkg-config,
-# python3-dev,
- quilt,
- swig2.0,
- xutils-dev (>= 1:7.6+6)
+ pkg-config
 Standards-Version: 3.9.5
 Homepage: https://01.org/linuxgraphics/
 Vcs-Git: git://anonscm.debian.org/pkg-xorg/app/intel-gpu-tools.git
@@ -34,3 +30,18 @@ Description: tools for debugging the Intel graphics driver
  intel-gpu-tools is a package of tools for debugging the Intel graphics driver,
  including a GPU hang dumping program, performance monitor, and performance
  microbenchmarks for regression testing the DRM.
+
+Package: intel-gpu-tools-dbg
+Section: debug
+Priority: extra
+Architecture: amd64 i386
+Depends:
+ intel-gpu-tools (= ${binary:Version}),
+ ${misc:Depends},
+ ${shlibs:Depends}
+Description: tools for debugging the Intel graphics driver (debug)
+ intel-gpu-tools is a package of tools for debugging the Intel graphics driver,
+ including a GPU hang dumping program, performance monitor, and performance
+ microbenchmarks for regression testing the DRM.
+ .
+ This package contains debugging symbols for intel-gpu-tools.
diff --git a/debian/rules b/debian/rules
index b7911a4..5e95be9 100755
--- a/debian/rules
+++ b/debian/rules
@@ -20,6 +20,9 @@ override_dh_install:
 	find debian/tmp -name '*.la' -delete
 	dh_install --fail-missing
 
+override_dh_strip:
+	dh_strip --dbg-package=intel-gpu-tools-dbg
+
 %:
 	dh $@ --with quilt,autoreconf --builddirectory=build/
 

commit a072fc4219ace0c6ebafde813ad27fd5d68cf492
Author: Vincent Cheng <vcheng@debian.org>
Date:   Tue May 13 18:45:28 2014 -0700

    Enable build hardening (dh compat 9)

diff --git a/debian/changelog b/debian/changelog
index 0b81ef3..ff24084 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+intel-gpu-tools (1.6-2) unstable; urgency=medium
+
+  * Enable build hardening (bump dh compat level to 9).
+
+ -- Vincent Cheng <vcheng@debian.org>  Tue, 13 May 2014 18:43:34 -0700
+
 intel-gpu-tools (1.6-1) unstable; urgency=medium
 
   [ Timo Aaltonen ]
diff --git a/debian/compat b/debian/compat
index 45a4fb7..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-8
+9
diff --git a/debian/control b/debian/control
index 6c5de8d..d5faf92 100644
--- a/debian/control
+++ b/debian/control
@@ -9,7 +9,7 @@ Uploaders:
  Vincent Cheng <vcheng@debian.org>
 Build-Depends:
  bison,
- debhelper (>= 8),
+ debhelper (>= 9),
  dh-autoreconf,
  libcairo2-dev,
  libdrm-dev (>= 2.4.38),


Reply to: