Bug#660335: missing bits of TERM=xterm transition

2012-02-18 Thread Robert Millan
Package: sysvinit Version: 2.88dsf-13.1 Severity: wishlist Tags: patch User: debian-bsd@lists.debian.org Usertags: kfreebsd Please consider adding the following changes so that sysvinit can handle the TERM=xterm transition all by itself without having to depend on versioned kbdcontrol package.

Re: Bug#660395: xserver-xorg-input-joystick: FTBFS on kfreebsd-*

2012-02-18 Thread Cyril Brulebois
Adam D. Barratt a...@adam-barratt.org.uk (18/02/2012): Source: xserver-xorg-input-joystick Version: 1:1.6.0-1 Severity: serious Hi, xserver-xorg-input-joystick no longer builds on kfreebdsd-* (having been binNMUed for the freebsd-libs transition). Robert, please send a patch since you

Re: Bug#660395: xserver-xorg-input-joystick: FTBFS on kfreebsd-*

2012-02-18 Thread Steven Chamberlain
Hi, Don't know if this is the proper fix, but my attached diff works for me. Problem seems to be that the configure script tests usb.h without including types.h first: | #include dev/usb/usb.h ... configure:12218: gcc -std=gnu99 -c -g -O2 conftest.c 5 In file included from conftest.c:28:0:

Re: hal: FTBFS on kfreebsd-*

2012-02-18 Thread Steven Chamberlain
Hi, This is due to 'unsafe' format strings being supplied to printf in FreeBSD-specific code, revealed by the -Wformat-security build hardening option. I've attached a patch to fix this. Thanks! Regards, -- Steven Chamberlain ste...@pyro.eu.org Description: fixes for -Wformat-security in

Re: Bug#660395: xserver-xorg-input-joystick: FTBFS on kfreebsd-*

2012-02-18 Thread Cyril Brulebois
tag 660395 patch pending thanks Hi! Steven Chamberlain ste...@pyro.eu.org (19/02/2012): Don't know if this is the proper fix, but my attached diff works for me. Problem seems to be that the configure script tests usb.h without including types.h first: […] That looks like a sane thing to do,

Re: Bug#660400: hal: FTBFS on kfreebsd-*

2012-02-18 Thread Cyril Brulebois
tag 660400 patch pending thanks Steven Chamberlain ste...@pyro.eu.org (19/02/2012): This is due to 'unsafe' format strings being supplied to printf in FreeBSD-specific code, revealed by the -Wformat-security build hardening option. I've attached a patch to fix this. Thanks, uploaded right