Warning: Current core (or exorcist perhaps) produces duplicate repligard table entries

Hi,

for all of you who are using the latest Midgard tech on productive servers: Be
aware that some part of the package produces duplicate entries in the repligard
table.

Midgard Core DOES NOT handle this case correctly. Versions before something
around 1.7.3 do just ignore the case leading to the actual duplicates (which
breaks MidCOM owner privileges and other stuff done directly after create()),
while newer versions prevent object creation in such a case (detected by an
UNIQUE INDEX, this is almost as bad as it prevents object creation for obscure
reasons to users).

I am encountering this problem on a regular basis on at least one live site, but
have not yet found a way to reproduce.

I thus recommend against using this piece of software until this situation is
resolved.

Specifically I officially remove any recommendation to deploy and MidCOM 2.5 on
live sites until this is resolved. I cannot support any of these combinations
until either the root of this problem is solved or at least the core gets more
error-resilent in this matter. This includes any bug reporting where either
MidCOM 2.5 or Midgard 1.7 is concerned. Such bugs will not be rejected if any
hint is there that points me to the conclusion that the mentioned bug may be the
root of this problem.

Details can be found at the Midgard Bug Report #118 [1] which also contains a
script [2] usable to detect and remove these duplicates in case you absolutely
have to deploy 2.5 somewhere.

[1] http://midgard.tigris.org/issues/show_bug.cgi?id=118
[2] http://midgard.tigris.org/nonav/issues/showattachment.cgi/7/clear_guids.sh

Live long and Prosper!
Torben Nehmer

--
Torben Nehmer, Guenzburg, Bavaria, Germany
http://www.nathan-syntronics.de, mailto:torben@...
PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc