Bug#345918: Possible solution

2006-01-21 Thread Richard Burton
It appears that this has now been fixed in 2.6.15-3, the localversion file is now installed with the headers. I have tested it with the zaptel module and it now installs to the correct location. Can this bug be closed, or has it been left open for a reason? Richard. -- To UNSUBSCRIBE,

Re: Bug#345918: Possible solution

2006-01-05 Thread Bastian Blank
On Wed, Jan 04, 2006 at 08:30:11PM -0800, Jurij Smakov wrote: Since currently we don't have a clear policy on packaging the kernel modules (even though incidents like this get me more and more motivated to start working on one), I just prepare the python modules in linux-2.6 to provide a

Bug#345918: Possible solution

2006-01-04 Thread Jurij Smakov
Hi, I've looked at this bug and it appears that nothing is wrong with linux-headers. Nothing is wrong in that case means that we did not introduce any bugs compared to the previous versions, I've verified that zaptel driver behaves the same way under 2.6.14. It appears that most of the

Bug#345918: Possible solution

2006-01-04 Thread Sven Luther
On Wed, Jan 04, 2006 at 08:30:11PM -0800, Jurij Smakov wrote: Hi, I've looked at this bug and it appears that nothing is wrong with linux-headers. Nothing is wrong in that case means that we did not introduce any bugs compared to the previous versions, I've verified that zaptel driver