Hi!
No, 2.3.1 does not fix it, but Chris Schlaeger has fixed it upstream. The fix
is basically
Index: TaskJugglerUI/TjPrintReport.cpp
===
--- TaskJugglerUI/TjPrintReport.cpp (revision 1378)
+++ TaskJugglerUI/TjPrintReport.cpp
Package: taskjuggler
Version: 2.3.1~beta1-1
Severity: normal
When I try to print out a report containing duration field, the
resulting value differs from what one obtains on the screen.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture:
Package: octave2.9
Version: 2.9.4-12
Severity: normal
If I hit Control-C in an Octave session, the interpreter enters a busy
loop (according to top) and stops responding. A gentle kill from
another shell is able to terminate the Octave session. It is possible to
reproduce the problem using the
Additional info:
if I run Octave under gdb, I can break the process by Control-C and resume it
flawlessly using c. Can it be the signal handler going wrong?
Andrey
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: libtao-qtreactor-dev
Version: 5.4.2.1.0-2
Severity: important
While unpacking the package tries to overwrite
/usr/include/tao/qt_resource.h which is also in
package libtao-dev. Installation fails.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500,
5 matches
Mail list logo