Update of /cvsroot/fink/dists/10.7/stable/main/finkinfo/gnome
In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv21021/gnome

Modified Files:
        evince.info evince.patch 
Log Message:
dep upgrades

Index: evince.patch
===================================================================
RCS file: /cvsroot/fink/dists/10.7/stable/main/finkinfo/gnome/evince.patch,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- evince.patch        9 Mar 2013 16:40:33 -0000       1.2
+++ evince.patch        2 Aug 2013 03:03:14 -0000       1.3
@@ -61,3 +61,15 @@
                                        (PopplerSelectionStyle)style,
                                        &r);
  
+diff -Nurd -x'*~' evince-2.22.2.orig/backend/tiff/tiff2ps.c 
evince-2.22.2/backend/tiff/tiff2ps.c
+--- evince-2.22.2.orig/backend/tiff/tiff2ps.c  2008-05-28 17:13:58.000000000 
-0400
++++ evince-2.22.2/backend/tiff/tiff2ps.c       2013-08-01 22:46:19.000000000 
-0400
+@@ -1124,7 +1124,7 @@
+       }
+       buf_data = (unsigned char *)_TIFFmalloc(chunk_size);
+       if (!buf_data) {
+-              TIFFError(ctx->filename, "Can't alloc %u bytes for %s.",
++              TIFFError(ctx->filename, "Can't alloc %lu bytes for %s.",
+                       chunk_size, tiled_image ? "tiles" : "strips");
+               return(FALSE);
+       }

Index: evince.info
===================================================================
RCS file: /cvsroot/fink/dists/10.7/stable/main/finkinfo/gnome/evince.info,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- evince.info 9 Mar 2013 16:40:33 -0000       1.8
+++ evince.info 2 Aug 2013 03:03:10 -0000       1.9
@@ -3,7 +3,7 @@
 # cannot upgrade past 2.22.2 until we get working libspectre
 # or lose PS support
 Version: 2.22.2
-Revision: 5
+Revision: 6
 
 Description: GNOME document viewer
 License: GPL
@@ -36,11 +36,11 @@
        libgnomeui2-shlibs (>= 2.24.2-2),
        libkpathsea6-shlibs,
        libnautilus-ext2-shlibs (>= 2.28.0-1),
-       libtiff-shlibs,
-       libxml2-shlibs (>= 2.8.0-1),
+       libtiff5-shlibs,
+       libxml2-shlibs (>= 2.9.1-1),
        orbit2-shlibs (>= 2.14.17-2),
        pango1-xft2-ft219-shlibs (>= 1.24.5-4),
-       poppler8-glib-shlibs,
+       poppler8-glib-shlibs (>= 0.22.5-1),
        popt-shlibs,
        rarian-compat,
        tetex-base,
@@ -58,7 +58,6 @@
        gconf2-dev (>= 2.28.0-1),
        gettext-tools,
        glib2-dev (>= 2.22.0-1),
-       glitz,
        gnome-common (>= 2.28.0-1),
        gnome-doc-utils (>= 0.18.1-1),
        gnome-keyring-dev (>= 2.28.0-1),
@@ -78,13 +77,13 @@
        libiconv-dev,
        libkpathsea6,
        libnautilus-ext2-dev (>= 2.28.0-1),
-       libtiff,
+       libtiff5,
        libtool2,
-       libxml2 (>= 2.8.0-1),
+       libxml2 (>= 2.9.1-1),
        orbit2-dev (>= 2.14.17-2),
        pango1-xft2-ft219-dev (>= 1.24.5-4),
        pkgconfig (>= 0.23),
-       poppler8-glib,
+       poppler8-glib (>= 0.22.5-1),
        popt,
        x11-dev
 <<
@@ -93,7 +92,7 @@
 GCC: 4.0
 ConfigureParams: --enable-dependency-tracking --disable-schemas-install 
--disable-scrollkeeper --enable-dvi --mandir=%p/share/man 
PKG_CONFIG_PATH="%p/lib/glib-2.0/pkgconfig-strict:$PKG_CONFIG_PATH" 
--disable-gtk-doc --disable-static
 PatchFile: %n.patch
-PatchFile-MD5: 53fb2566826fcf6b7932365c75d04e0e
+PatchFile-MD5: 49ea686e360d4043122f3608c2d4d6a5
 PatchScript: <<
        # upgrades for newer-poppler's API based on upstream
        %{default_script}


------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Fink-commits mailing list
Fink-commits@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.cvs

Reply via email to