Your message dated Sat, 21 Aug 2010 12:41:50 +0100 (WEST)
with message-id <[email protected]>
and subject line Package gq has been removed from Debian
has caused the Debian Bug report #245458,
regarding qg: should not systematically set the replace flag when calling
ldap_modrdn2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
245458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245458
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gq
Version: 0.7.0+1.0beta1-4
Severity: critical
Justification: causes serious data loss
Context: "renaming" an entry by editing the dn and pressing "apply"
1. I get a silly-looking error message which I don't remember
precisely. IIRC it was complaining about finding no "cn" although it
was a mandatory attribute, whereas the cn was really there (I just
changed the dn, the entry was otherwise valid).
2. When retrying I get another message, this time saying it cannot
find the dn I want to rename
3. Suspecting that the rename may have succeeded nonetheless, I check
my tree, and cannot find the entry anymore
I suppose that this renaming is just a comfort feature implemented a
"delete and create new", since I cannot see any other means of doing
this sort of operation.
Then I suppose it first deletes the old entry, before creating the new
one (which the server could refused for any reason), and even before
doing some of its own sanity checks.
The natural fix would then be to start by creating the new entry, then
removing the old one iff that failed.
I could not reproduce the exact error described in 1., I think it's
another bug I do not understand yet. I also tested what happenned
when asking to rename as a dn already used by another entry, and gq
apaprently does a check first. Even if I ldapadd an entry externally,
the check occurs correctly.
--
Yann Dirson <[email protected]> http://www.alcove.com/
Senior Free-Software Consultant Consultant senior en Logiciels Libres
Debian developer ([email protected]) Développeur Debian
--- End Message ---
--- Begin Message ---
Version: 1.3.4-1+rm
You filed the bug http://bugs.debian.org/245458 in Debian BTS
against the package gq. I'm closing it at *unstable*, but it will
remain open for older distributions.
For more information about this package's removal, read
http://bugs.debian.org/593165. That bug might give the reasons why
this package was removed and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
--- End Message ---
