Your message dated Thu, 18 Dec 2008 21:55:49 +0100
with message-id <[email protected]>
and subject line lirc-modules-source FTBFS with 2.6.26
has caused the Debian Bug report #509081,
regarding lirc-modules-source FTBFS with 2.6.26
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
509081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509081
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lirc-modules-source
Version: 0.8.3-3
Severity: grave

Rationale for severity: FTBFS with 2.6.26 kernel (at least using
module-assistant), build log:

/usr/src/modules/lirc/drivers/lirc_dev/lirc_dev.c: In function
‘cleanup’:  
/usr/src/modules/lirc/drivers/lirc_dev/lirc_dev.c:132: error: implicit
declaration of function ‘class_device_destroy’                                
/usr/src/modules/lirc/drivers/lirc_dev/lirc_dev.c: In function
‘lirc_register_plugin’:
/usr/src/modules/lirc/drivers/lirc_dev/lirc_dev.c:382: error: implicit
declaration of function ‘class_device_create’
make[6]: *** [/usr/src/modules/lirc/drivers/lirc_dev/lirc_dev.o] Error 1   
make[5]: *** [_module_/usr/src/modules/lirc/drivers/lirc_dev] Error 2

While it should be noted that it's not the package itself that fails to
build, but the sources provided by the package, it seems reasonable that
the failure is to be considered an FTBFS anyway, since it's a
source-package.


Regards: David
-- 
 /) David Weinehall <[email protected]> /) Rime on my window           (\
//  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~   //  Diamond-white roses of fire //
\)  http://www.acc.umu.se/~tao/    (/   Beautiful hoar-frost       (/



--- End Message ---
--- Begin Message ---
It seems that it was indeed a case of unclean build tree; I thought,
incorrectly, that module-assistant would install the sources
in a clean tree when I told it to upgrade the package.  Anyway, sorry
for the false alarm.


Regards: David
-- 
 /) David Weinehall <[email protected]> /) Rime on my window           (\
//  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~   //  Diamond-white roses of fire //
\)  http://www.acc.umu.se/~tao/    (/   Beautiful hoar-frost       (/


--- End Message ---

Reply via email to