On Mon, Jul 12, 2010 at 01:02:17AM +0200, Stefan Lippers-Hollmann wrote:
>
> Yes, I'm aware that this situation becomes worse in kernels >> 2.6.32, like
> those present in experimental and that lirc needs to be fixed. However this
> situation isn't as easy as it looks:
> - the most current lirc upstream version needs patching for
> kernel >= 2.6.32 support just as well (done in svn); 0.8.7 hasn't been
> released yet.
> - 'lirc' >= 0.8.6 introduces an FTBS on kfreebsd-{amd64,i386} (not fixed
> yet)
> - lirc >= 0.8.6 breaks the long standing ABI between kernel- and userspace,
> therefore upgrades affecting 'lirc' and 'lirc-modules-$(uname -r) must
> happen in lockstep (which doesn't seem to be easily expressable in
> packaging terms).
> - serious debconf refactoring is still pending, to meet 3.9.0 policy
> requirements (started in svn, but not finished yet).
>
> Any help with these issues is always seriously appreciated, especially in
> regards to the mandatory debconf changes - which is the most blocking
> sub-topic (and also preventing yet another 0.8.3 upload).
>
Thx for the patch. At least the I could compile the package (haven't tried to
use
it yet)
Any chance you could explain the debconf refactoring a bit more and what is
still
missing? I might give it a try (no promisses!!!).
-Peter
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
