Bug#679182: FTBFS on mips*: braces around scalar initializer for type 'unsigned int'

2013-11-25 Thread Dragoslav Sicarov
Control: tags + patch Fix for struct sigaction initialization. Patch fixing struct sigaction initialization is attached. Index: logkeys-0.1.1a/src/logkeys.cc === --- logkeys-0.1.1a.orig/src/logkeys.cc 2010-05-31 05:04:57.0

Bug#679182: FTBFS on mips*: braces around scalar initializer for type 'unsigned int'

2013-11-05 Thread Dragoslav Sicarov
Hi everyone, In my opinion this issue is not mips compiler bug. Simulating this issue on i386, amd64, mips and mipsel architectures I got same results. In definition of struct sigaction there is a difference between architectures due to the error occur. Definition for mips: struct sigaction

Bug#712695: closed by Markus Koschany a...@gambaru.de (Bug#712695: fixed in jnr-netdb 1.0.3-3)

2013-10-15 Thread Dragoslav Sicarov
f8YR7quQi8HEG7aioSPY94Z5VtCX9RPP9jm6KPejEyJYr3BE4lbYwJqfgSvgXuN3 4KDNMqfCBDWHsZkQXqCNraucUvE1CZpDt/g7VNJpxoxQldV6t0egUYxgb6gOTxII UTBkVsCUojmB4svEwLb+xcmO/uLj3YxUqC4JluOJ03FdTTFq6cv18ltTOpB7c/xh 8FPyEpc9BO5BkHuwMR5c =LHRM -END PGP SIGNATURE- -- Forwarded message -- From: Dragoslav Sicarov dsica...@gmail.com

Bug#715481: Issue in xserver-xorg-video-mga (X.Org X server -- MGA display driver) for mips BE

2013-07-09 Thread Dragoslav Sicarov
Package: xserver-xorg-video-mga Version: 1:1.5.0-3 Severity: serious Tags: wheezy xserver-xorg-video-mga does not work on big endian mips. DVI monitor: Everything loads normally. Monitor turns on for a moment and then goes to a standby mode. VGA monitor: After xserver loads

Bug#712885: fop does not generate pdf files on mips - wheezy

2013-06-20 Thread Dragoslav Sicarov
Package: fop Version: 1.0.dfsg2-6 Severity: serious Tags: wheezy During x11proto-core and xorg-docs packages rebuild on mips with sbuild, issue with fop occured. Issue is described at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712689

Bug#712510: python-whoosh FTBFS:some tests failed on mips

2013-06-17 Thread Dragoslav Sicarov
The problem does not occur in python-whoosh 2.4.1-1. How is this problem going to be fixed for wheezy? Are you going to upgrade python-whoosh to 2.4.1-1 version in wheezy, or python-whoosh 2.3.2-2 version will be patched?