Hi Evgeni,
On Mon, Nov 21, 2005 at 09:48:16AM +0100, Evgeni Golov wrote:
> I've still didn't try the new modules. Whats about the loop-aes-util
> package? Should I rebiuld it with Sid sources too? Or leave it and hope
> the new loop-aes module is backward-compatible?
There is no need for using newer -utils at the moment. The current
loop-aes-source in sid works fine with the version of -utils in sarge.
If some newer version of -source will require newer utils, I'll change
the dependencies of binary module packages to reflect such requirements.
By the way, you can use the upstream testsuite included in the sid
versions of loop-aes-$KVERS packages to verify that the modules and
-utils are working correctly. Just load the loop module and run
/usr/share/loop-aes-$KVERS/runtests.
> So wouldn't it be a candidate for debian-volatile then?
Perhaps, but something tells me this would be better be placed on
backports.org. I think I can directly upload to backports, so I'll
look into this once the backports repository gets ready for sarge.
Would that work for you like volatile, or is there something I'm
not considering about differences between them?
> > Could you send the complete build log to this bug?
>
> It's in the attachment - hope you can read it better than me. ;-)
There are a couple of problems actually. At least two changes that
were introduced in later versions of loop-AES to account for changes in
the kernel are missing from 2.2d: One to account for vanished
QUEUE_FLAG_ORDERED and another for change of lo_pending and perhaps
others from simple type int to struct { volatile int }. One could
probably backport the changes from a newer version, but the amount of
work that would bring doesn't seem justified given that later versions
already include them, are well tested and work OK on sarge.
cheers,
Max
--
PS: please CC the bug address [EMAIL PROTECTED] in your replies.
This way other users can find perhaps useful information in the BTS.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
