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

libdrm: Changes to 'debian-unstable'



 debian/changelog |    6 ++++++
 debian/rules     |    2 +-
 2 files changed, 7 insertions(+), 1 deletion(-)

New commits:
commit 90b9243bf63ab66a04115dc46f1d2f0fd51f454d
Author: Julien Cristau <jcristau@debian.org>
Date:   Wed Mar 25 10:57:13 2009 +0100

    Prepare changelog for upload

diff --git a/debian/changelog b/debian/changelog
index c883ae8..adec56f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,8 @@
-libdrm (2.4.5-2) UNRELEASED; urgency=low
+libdrm (2.4.5-2) unstable; urgency=low
 
   * Add drm_mode.h to the list of headers we don't ship.
 
- -- Julien Cristau <jcristau@debian.org>  Wed, 25 Mar 2009 10:55:10 +0100
+ -- Julien Cristau <jcristau@debian.org>  Wed, 25 Mar 2009 10:56:53 +0100
 
 libdrm (2.4.5-1) unstable; urgency=low
 

commit d81f91481ca67e7ae214712f9f979bcde0d72817
Author: Julien Cristau <jcristau@debian.org>
Date:   Wed Mar 25 10:56:51 2009 +0100

    Add drm_mode.h to the list of headers we don't ship.

diff --git a/debian/changelog b/debian/changelog
index 75a8afe..c883ae8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libdrm (2.4.5-2) UNRELEASED; urgency=low
+
+  * Add drm_mode.h to the list of headers we don't ship.
+
+ -- Julien Cristau <jcristau@debian.org>  Wed, 25 Mar 2009 10:55:10 +0100
+
 libdrm (2.4.5-1) unstable; urgency=low
 
   * New upstream release. (closes: #505740)
diff --git a/debian/rules b/debian/rules
index a7a7c97..37b7210 100755
--- a/debian/rules
+++ b/debian/rules
@@ -80,7 +80,7 @@ install: build
 
 	cd obj-$(DEB_BUILD_GNU_TYPE) && $(MAKE) install DESTDIR=$(CURDIR)/debian/tmp
 	# remove files provided by linux-libc-dev
-	for file in drm_sarea.h drm.h i915_drm.h mga_drm.h r128_drm.h radeon_drm.h savage_drm.h sis_drm.h via_drm.h; do \
+	for file in drm_mode.h drm_sarea.h drm.h i915_drm.h mga_drm.h r128_drm.h radeon_drm.h savage_drm.h sis_drm.h via_drm.h; do \
 		rm -f debian/tmp/usr/include/drm/$$file; \
 	done
 


Reply to: