On Thu, 2006-03-16 at 15:24 +0100, Marco Presi wrote:
> rj> Conflicting with anything doesn't solve the problem.
>
> Why *anything*?
I meant "something".
> Actually, 2.6.15 is the only available kernel both in testing
> and unstable. The package doesn't work out of the box as it
> should with the actual kernel series, and if I understood the
> problem, it will not work with the next kernel releases. I think
> users should be warned about this problem. If you don't agree
> to set a conflict with a specific kernel version, probably a
> warning message could be helpful for users.
The current problem (gpib not working with a kernel >= 2.6.15) cannot be
expressed by a conflict. Especially not since you can have many kernels
installed (e.g. 2.6.12 and 2.6.15) and gpib compiled for only one (in
this case 2.6.12). Then this problem is not apparent. But a conflict
would even prohibit that situation and make things worse.
A not could be done but will have the same effect. A user compiling
gpib, loading it and seeing the oops is just as unhappy as a user trying
to compile gpib and reading the note that it won't work. The bug
remains. As does the problem.
> If I find time, I will also look to try to backport the changes
> to solve this bug.
Ok. great. Thanks.
Robert.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
