Bug#1111416: quick fix

[Matija Nalis <mnalis-debianbug@voyager.hr>]

Yeah, if definitely is at least NEWS.Debian worthy IMHO, if not "Severity: important", 
as it completely breaks existing data on upgrade on supported architecture

---

For those who already upgraded to Trixie unaware of this issue, and everything RRD-related broke, and do not want to setup old Bookworm
just to dump databases, this quick and dirty trick (temporarily using old Bookworm library to dump data on Trixie system) worked for me:


mkdir /tmp/oldrrd && cd /tmp/oldrrd && wget http://deb.debian.org/debian/pool/main/r/rrdtool/librrd8_1.7.2-4+b8_armhf.deb && dpkg-deb -x *.deb .
fixrrd() { cp -ai "$1" "$1.bak" && LD_PRELOAD=/tmp/oldrrd/usr/lib/arm-linux-gnueabihf/librrd.so.8.2.1 rrdtool dump "$1" > "$1.xml" && rrdtool restore -f "$1.xml" "$1"; }

...and then you can do "fixrrd /path/to/example.rrd" to fix some specific RRD file, or automate it with something like: 

# find /var/www/db -type f -name "*.rrd" | while read rrd; do echo "Fixing $rrd"; fixrrd "$rrd"; done

(worked fine for me, but as with any advice from random people on the 'net, do your homework and make sure you have working backups)

If/when you are happy with result, you may also want to delete old "*.rrd.bak" copying and/or "*.rrd.xml" backups left behind (as well
as cleanup /tmp/oldrrd or wherever you unpacked that library)

-- 
Opinions above are GNU-copylefted.