> On Wed, Aug 12, 2009 at 10:18:30PM -0700, Mike Castle wrote:
>>
>> Severity: grave
>> Justification: causes non-serious data loss
>
> Incorrect: No data was actually *lost*, right?

I think it's correct.  After all the definition is:

'causes non-serious data loss', """causes the loss of data on the system
    that is unimportant, or restorable without resorting to backup media"""

Granted, I ran migrationtools once, two years ago.  And now, trying to
upgrade slapd caused there to be no ldap server running, because the
data is invalid.  As a result, I ended up with an ldap server with no
data in it.  Seemed lost to me.  Sure, it was there in /var/backups.
But it did involve a restore process that seems to imply the final
clause there.

If this option:
'renders package unusable', """renders the package unusable, or mostly
    so, on all or nearly all possible systems on which it could be installed
    (i.e., not a hardware-specific bug); or renders package uninstallable
    or unremovable without special effort"""

read something:  'renders OTHER package unusable'  I probably would
have chosen that as an option.

At any rate, making it impossible to log into a system as a normal
user does seem a grave error.


>> The fix for bug#307618 actually introduced another issue.  Any system that
>> used migrationtools to load services will be unable to upgrade to slapd
>> 2.4.17-1 (actually, anything newer than 2.4.15).  Reference bug#541292 for
>> details.  But essentially,
>> `cn=echo+ipServiceProtocol=tcp+ipServiceProtocol=udp' is an illegal value.
>>
>>
>> At first glance, it seems that replacing the + with _ allows the file to
>> load, but I'm not sure if that's sufficient for everything to work properly.
>>  I don't know if this dn: is used or just needs to be unique.
>
> In principle they are unique, but I suspect that most users of
> migrationtools won't actually use that data.
>
> I will simply disable that patch for now, and leave it to the user to decide
> if they want to a) use only some of the scripts og b) force-load with the
> result that tcp and udp entries are merged.

A force load that results in the same string will never work in the
long run.  Better to give them the ability to have a valid string.

Maybe instead of `+' use `_and_'   ?

mrc



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to