Bug#497739: rrdtool: Reported fix...doesn't work

2009-06-04 Thread Matthew Exley
Package: rrdtool
Version: 1.3.8-1
Followup-For: Bug #497739


I've just tested both the reported-fixed 1.3.7-1 and the refreshed
1.3.8-1 versions of RRDTool and the buggy behaviour persists in these
versions.

Using a sample invocation of:

rrdtool graph /var/www/sysinfo/rrdcgi-eth0.png \
--imginfo 'IMG SRC=/sysinfo/%s WIDTH=%lu HEIGHT=%lu ' \
--start -1week \
--width 800  \
--height 600 \
--title=eth0 Network Utilisation \
--interlaced \
--vertical-label Bytes/Sec \
--base 1000 \
--slope-mode \
DEF:RX=/var/local/rrd/netutil_eth0.rrd:rx:AVERAGE \
DEF:TX=/var/local/rrd/netutil_eth0.rrd:tx:AVERAGE \
CDEF:RXkb=RX,1000,/  \
CDEF:TXkb=TX,1000,/ \
LINE2:RX#20FF20:RX \
LINE2:TX#FF2020:TX

Still produces output of:

IMG SRC=/sysinfo//var/www/sysinfo/rrdcgi-eth0.png WIDTH=897 HEIGHT=674 


Instead of the documented and expected output of:

IMG SRC=/sysinfo/rrdcgi-eth0.png WIDTH=897 HEIGHT=674 


-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (200, 'stable'), (50, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to 
en_GB)
Shell: /bin/sh linked to /bin/bash

Versions of packages rrdtool depends on:
ii  libc6  2.9-6 GNU C Library: Shared libraries
ii  libcairo2  1.8.6-2+b1The Cairo 2D vector graphics libra
ii  libglib2.0-0   2.20.0-2  The GLib library of C routines
ii  libpango1.0-0  1.22.4-3  Layout and rendering of internatio
ii  libpng12-0 1.2.27-2  PNG library - runtime
ii  librrd41.3.1-4   Time-series data storage and displ
ii  libxml22.6.32.dfsg-5 GNOME XML library

rrdtool recommends no packages.

Versions of packages rrdtool suggests:
ii  librrds-perl  1.3.1-4Time-series data storage and displ

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#497739: rrdtool: Reported fix...doesn't work

2009-06-04 Thread Sebastian Harl
Hi,

On Thu, Jun 04, 2009 at 03:02:50PM +0100, Matthew Exley wrote:
 I've just tested both the reported-fixed 1.3.7-1 and the refreshed
 1.3.8-1 versions of RRDTool and the buggy behaviour persists in these
 versions.

 Versions of packages rrdtool depends on:
[...]
 ii  librrd41.3.1-4   Time-series data storage and 
 displ

You should upgrade librrd4 as well. The rrdtool binary only provides a
wrapper around the library - all functionality is implemented in the
library.

HTH,
Sebastian

-- 
Sebastian tokkee Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin



signature.asc
Description: Digital signature


Bug#497739: rrdtool: Reported fix...doesn't work

2009-06-04 Thread Matthew Exley
AAARRRGGHGHH

Missed that *completely* - thanks for the email, upgrading librrd4 fixed the
problem as you'd suggested it would.

Now, should I have egg on my face for missing it, or should the dependencies
for rrdtool have sorted that out for me?

I note rrdtool only has:
 librrd4 (= 1.3.0)

(I did apt-get -u install rrdtool to upgrade, and that's normally pretty
good at pulling in dependencies).

Sorry for wasting your time on this one though.

Cheers,

Matthew


2009/6/4 Sebastian Harl s...@tokkee.org

 Hi,

 On Thu, Jun 04, 2009 at 03:02:50PM +0100, Matthew Exley wrote:
  I've just tested both the reported-fixed 1.3.7-1 and the refreshed
  1.3.8-1 versions of RRDTool and the buggy behaviour persists in these
  versions.

  Versions of packages rrdtool depends on:
 [...]
  ii  librrd41.3.1-4   Time-series data storage and
 displ

 You should upgrade librrd4 as well. The rrdtool binary only provides a
 wrapper around the library - all functionality is implemented in the
 library.

 HTH,
 Sebastian

 --
 Sebastian tokkee Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/

 Those who would give up Essential Liberty to purchase a little Temporary
 Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin


 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (GNU/Linux)

 iEYEARECAAYFAkon2u8ACgkQEFEKc4UBx/ygIQCcCrZ1UgpT+2Qj9f8CY7H5vM+7
 RVEAnjpITFrzUYfPDPO6NRi9TqgqTBNc
 =SsKw
 -END PGP SIGNATURE-




-- 
Matthew Exley
hen...@guided-naafi.org


Bug#497739: rrdtool: Reported fix...doesn't work

2009-06-04 Thread Sebastian Harl
Hi,

On Thu, Jun 04, 2009 at 03:37:51PM +0100, Matthew Exley wrote:
 Now, should I have egg on my face for missing it, or should the dependencies
 for rrdtool have sorted that out for me?
 
 I note rrdtool only has:
  librrd4 (= 1.3.0)

rrdtool does not _require_ a more up-to-date version of librrd4.

 (I did apt-get -u install rrdtool to upgrade, and that's normally pretty
 good at pulling in dependencies).

Do you use pinning or something similar? Letting aside dependencies, the
new version should have been pulled in because of the higher version
number.

HTH,
Sebastian

-- 
Sebastian tokkee Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin



signature.asc
Description: Digital signature


Bug#497739: rrdtool: Reported fix...doesn't work

2009-06-04 Thread Matthew Exley
Thanks again for looking at this..

2009/6/4 Sebastian Harl s...@tokkee.org

 Hi,

 On Thu, Jun 04, 2009 at 03:37:51PM +0100, Matthew Exley wrote:
  Now, should I have egg on my face for missing it, or should the
 dependencies
  for rrdtool have sorted that out for me?
 
  I note rrdtool only has:
   librrd4 (= 1.3.0)

 rrdtool does not _require_ a more up-to-date version of librrd4.


Understood. (Seems odd to me that they're not in lockstep, but I'm not
questioning it)


  (I did apt-get -u install rrdtool to upgrade, and that's normally
 pretty
  good at pulling in dependencies).

 Do you use pinning or something similar? Letting aside dependencies, the
 new version should have been pulled in because of the higher version
 number.


I did mention I did a single-package install. I'm sure an apt-get upgrade
would have dragged it in, but I didn't do that. Your explanation above about
not  *requiring* an upgrade explains the behaviour adequately, I think.

Cheers,

-- 
Matthew Exley
hen...@guided-naafi.org