Even better would be to update to Mantis 1.2.4 (from oneiric).
(Should this issue be modified, or should that be a different bug
request?)
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/
Enabling hardy-backports and updating debhelper (only) allowed
cppcheck_1.40-1.dsc to build for me.
cppcheck_1.44-1.dsc does *not* build with the following error:
dpkg-source: error: Unsupported format of .dsc file (3.0 (quilt))
I'll try the cppcheck 1.40 package and see how it goes.
--
Please
OK, I've tried to build cppcheck for Hardy myself from
cppcheck_1.40-1.dsc (Lucid), and I'm being thwarted by the requirement
for debhelper >= 7 (hardy provides debhelper 6).
So, this means that a backported cppcheck would therefore also require
the backported debhelper (7) from hardy-backports?
Public bug reported:
It would be extremely handy to have cppcheck available for Hardy. I'm
not certain which version would be best -- presumably re-using the
version in Jaunty backports ought to be fine.
** Affects: hardy-backports
Importance: Undecided
Status: New
--
Please back
*** This bug is a security vulnerability ***
Public security bug reported:
The existing backport for Mantis is 1.1.2, while 1.1.6 exists in jaunty.
It would be nice if the hardy backport version could be updated to this
later stable release.
As Mantis 1.1.4 was a security fix release, I believe
Public bug reported:
Mantis 1.1.2 is the current stable version of Mantis and contains a
number of significant feature enhancements over the 1.0.x series.
The key feature (from my perspective) is the new "target release"
setting, which is a huge improvement in using Mantis to manage software
rele
