[Pkg-lirc-maint] Bug#545982: lirc-modules-source: does not compile with 2.6.30-1-686

Stefan Lippers-Hollmann s.L-H at gmx.de
Thu Sep 10 14:03:50 UTC 2009

Source: lirc
Source-Version: 0.8.3-4

On Thursday 10 September 2009, A Mennucc wrote:
> Package: lirc-modules-source
> Version: 0.8.3-3
> Severity: grave
> Justification: renders package unusable
> hi,
> the lirc module does not compile on the kernel 2.6.30-1-686 , 
> in a recent Debian/unstable install
> a.

lirc-modules-source >= 0.8.3-4 (uploaded on the 7th of August 2009) 
compiles and works well with kernel 2.6.26 - 2.6.31. It's available in sid
for all architectures != mipsel, which keeps it out of testing for now[1].

On Thursday 10 September 2009, A Mennucc wrote:
> hi,
> I was looking into svn://svn.debian.org/svn/pkg-lirc/lirc/trunk/
> I am puzzled
> I see that, you are not upgrading to the latest upstream
> (currently 0.8.5 , since May 2009 - but before that there was
> 0.8.4a in Oct 2008) ; but rather, whenever a new
> kernel has entered in Debian, you have 
> backported many patches into 0.8.3 to try to support it.
> Why? 

With lirc 0.8.4 comes (initial) hal support for lirc devices that can be
autodetected by udev, upgrading to this version requires fundamental
changes in the packaging (including a round through binary NEW and a 
complete debconf/ template overhaul with its associated i18n round) - while
lirc-modules-source 0.8.3-3 in testing remains broken for all kernels >= 
2.6.27. Therefore a working version needs to go to testing first, and 
0.8.3-4/5 is tested for up to 2.6.31.

0.8.3-4/5 have both been uploaded with urgency=medium, -4 prevented from 
entering testing due to a broken chroot on hppa and Debian/ kFreeBSD 
pushing for compatibility patches, -5 is stalled on mipsel - besides 
nagging for uploading the successfully built binaries or a give-back, 
there's nothing I could do; removing liblircclient0 from mipsel would 
remove a too large number of rdepends.

> I am asking, because IMHO opinion upgrading to 0.8.5 would
> be the simplest way of solving these issues; also
> there is a bug 517507 asking for 0.8.4a , to support
> some more hw.

Unfortunately it isn't, 0.8.5 needs patches for supporting 2.6.31 (yes, 
basically a rebased version of those I backported to 0.8.3)[2], which has 
become stable tonight and is to be expected in unstable very soon, while
0.8.6pre1 breaks compilation on kernel <<2.6.31. At the same time, 0.8.6
includes a number of locking fixes, which might help with two bugreports
against lirc_i2c).

> But since you went to great effort, maybe there are issues.
> If otherwise you just need some manpower, feel free to ask.

Manpower is always scarce and appreciated.

	Stefan Lippers-Hollmann

[1]	http://lists.debian.org/debian-wb-team/2009/08/msg00055.html
	yes, I have prepared another ping, which will get sent in 2 days
[2]	http://svn.debian.org/viewsvn/pkg-lirc/lirc/trunk/debian/patches/25_kcompat-2.6.31.patch?view=markup
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-lirc-maint/attachments/20090910/ca46bb86/attachment.pgp>

More information about the Pkg-lirc-maint mailing list