diff options
| author |  Alan Fitton <ajf@eth0.org.uk> | 2011-08-31 13:34:00 +0000 |
|---|---|---|
| committer | Alan Fitton <ajf@eth0.org.uk> | 2011-08-31 13:34:00 +0000 |
| commit | 8eef0e7576d67d14efe305ba4d73cee374c57220 (patch) | |
| tree | 8b91467113da91d39c67217514ae530538cfd3ac /debian | |
| parent | 7bf25fa4ac9b91d8249a3e43e35f4e11e28c1ef4 (diff) | |
switch from using the trackers struct to trackerstats - and add some of the new columns into the trackers model and treeview
Diffstat (limited to 'debian')
| -rw-r--r-- | debian/control | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/debian/control b/debian/control index 44a9ec6..8f0ff47 100644 --- a/debian/control +++ b/debian/control @@ -2,7 +2,7 @@ Source: transmission-remote-gtk Section: net Priority: optional Maintainer: Alan Fitton <alan@eth0.org.uk> -Build-Depends: debhelper (>= 7.0.50~), autotools-dev, libcurl4-openssl-dev, libgtk2.0-dev (>= 2.16~), libglib2.0-dev (>= 2.22~), libproxy-dev, libnotify-dev, libunique-dev, libjson-glib-dev, libgconf2-dev +Build-Depends: debhelper (>= 7.0.50~), autotools-dev, libcurl4-openssl-dev, libgtk2.0-dev (>= 2.16~), libglib2.0-dev (>= 2.22~), libproxy-dev, libnotify-dev, libunique-dev, libjson-glib-dev Standards-Version: 3.8.4 Homepage: http://code.google.com/p/transmission-remote-gtk/ Vcs-Svn: http://transmission-remote-gtk.googlecode.com/svn/trunk/ @@ -10,7 +10,7 @@ Vcs-Browser: http://code.google.com/p/transmission-remote-gtk/source/browse/ Package: transmission-remote-gtk Architecture: any -Depends: libgtk2.0-0 (>= 2.16~), libglib2.0-0 (>= 2.22~), libunique-1.0-0, libgconf2-4, gconf2, libnotify1, libproxy0, libjson-glib-1.0-0 (>= 0.8~), ${shlibs:Depends}, ${misc:Depends} +Depends: libgtk2.0-0 (>= 2.16~), libglib2.0-0 (>= 2.22~), libunique-1.0-0, libnotify1, libproxy0, libjson-glib-1.0-0 (>= 0.8~), ${shlibs:Depends}, ${misc:Depends} Description: GTK remote control for the Transmission BitTorrent client transmission-remote-gtk is a GTK application for remote management of the Transmission BitTorrent client via its RPC interface. |