yes: it has been fixed in Debian with version 5.0-4 and this version has been synced on the 25th of August. That's why the package now builds in Maverick (see comment 6).
Just in case, I've just checked and the package still builds and install fine.
Thanks, Fabrice
yes: it has been fixed in Debian with version 5.0-4 and this version has been synced on the 25th of August. That's why the package now builds in Maverick (see comment 6).
Just in case, I've just checked and the package still builds and install fine.
Thanks,
Fabrice