Bug in consecutive.so and sametimeas.so found

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

I have some bad news today.

Updater functions in modules consecutive.so and sametimeas.so do not
properly respect resource domains for the 'time' resource type. For
example: in consecutive.so the resource domain is only respected for the
first event in the block. This means other events in the block will be
scheduled after the first one even if 'time' resource domains do not
allow that.

In other words this means that you may have problems if you use
'fixed-day' or 'fixed-period' restrictions on events that are also
handled by restrictions defined by consecutive.so or sametimeas.so modules.

I've made two example files that demonstrate this bug. You can download
them from http://www.tablix.org/~avian/updater-bug

Unfortunately I currently do not see an elegant solution to this
problem. CVS version of the kernel will now check for this condition and
display a warning about a failed assertion. On the other hand it will
most likely take me some time to develop a proper fix for this bug as it
will probably include some changes to the kernel.

Best regards
Tomaz Solc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEKZHFsAlAlRhL9q8RAiC7AJ9aSbtN6yPDF5L3T3TkkvDPGlsGAACZAYSj
5yJzgKm0kiXUlSSauWcg6Gk=
=NBAa
-----END PGP SIGNATURE-----
Received on Tue Mar 28 21:43:03 2006