libx11: Changes to 'debian-experimental'
debian/changelog | 7 +++++++
debian/libx11-6.symbols | 6 +++---
2 files changed, 10 insertions(+), 3 deletions(-)
New commits:
commit 2cc13c4d65e22d0c806ebb95b3720389e286476f
Author: Julien Cristau <jcristau@debian.org>
Date: Tue Oct 13 14:43:20 2009 +0200
libx11-6.symbols: minor tweak
_XkbReadBufferCopy32, _XkbReadCopyData32 and _XkbWriteCopyData32 are
only present on 64-bit architectures.
diff --git a/debian/changelog b/debian/changelog
index 768a3d2..39eb7a2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+libx11 (2:1.3-2) UNRELEASED; urgency=low
+
+ * libx11-6.symbols: _XkbReadBufferCopy32, _XkbReadCopyData32 and
+ _XkbWriteCopyData32 are only present on 64-bit architectures.
+
+ -- Julien Cristau <jcristau@debian.org> Tue, 13 Oct 2009 14:41:38 +0200
+
libx11 (2:1.3-1) experimental; urgency=low
* libx11-6.symbols: mark some more stuff as private.
diff --git a/debian/libx11-6.symbols b/debian/libx11-6.symbols
index 89ca5f8..c5edd42 100644
--- a/debian/libx11-6.symbols
+++ b/debian/libx11-6.symbols
@@ -1103,9 +1103,9 @@ libX11.so.6 libx11-6 #MINVER#
(optional)_XkbInternAtomFunc@Base 0 1
(optional)_XkbNoteCoreMapChanges@Base 0 1
(optional)_XkbPeekAtReadBuffer@Base 0 1
- (optional)_XkbReadBufferCopy32@Base 0 1
+ (optional|arch=alpha amd64 kfreebsd-amd64 ia64)_XkbReadBufferCopy32@Base 0 1
(optional)_XkbReadBufferCopyKeySyms@Base 0 1
- (optional)_XkbReadCopyData32@Base 0 1
+ (optional|arch=alpha amd64 kfreebsd-amd64 ia64)_XkbReadCopyData32@Base 0 1
(optional)_XkbReadCopyKeySyms@Base 0 1
(optional)_XkbReadGetCompatMapReply@Base 0 1
(optional)_XkbReadGetGeometryReply@Base 0 1
@@ -1114,7 +1114,7 @@ libX11.so.6 libx11-6 #MINVER#
(optional)_XkbReadGetNamesReply@Base 0 1
(optional)_XkbReloadDpy@Base 0 1
(optional)_XkbSkipReadBufferData@Base 0 1
- (optional)_XkbWriteCopyData32@Base 0 1
+ (optional|arch=alpha amd64 kfreebsd-amd64 ia64)_XkbWriteCopyData32@Base 0 1
(optional)_XkbWriteCopyKeySyms@Base 0 1
(optional)_XkeyTable@Base 0 1
(optional)_XlcAddCT@Base 0 1
Reply to: