Re: Bug#606794: ldap-account-manager: package fails to upgrade properly from lenny
-----BEGIN PGP SIGNED MESSAGE-----
I need some advice from you on the bug below.
Am 12.12.2010 12:01, schrieb Lucas Nussbaum:
>> Am 11.12.2010 18:11, schrieb Lucas Nussbaum:
>>> While testing the installation of all packages in squeeze, I ran
>>> into the following problem:
>>>> Setting up ldap-account-manager (3.1.0-2) ...
>>>> Configuration file `/etc/ldap-account-manager/config.cfg'
>>>> ==> Modified (by you or by a script) since installation.
>>>> ==> Package distributor has shipped an updated version.
>>>> What would you like to do about it ? Your options are:
>>>> Y or I : install the package maintainer's version
>>>> N or O : keep your currently-installed version
>>>> D : show the differences between the versions
>>>> Z : start a shell to examine the situation
>>>> The default action is to keep your current version.
>>>> *** config.cfg (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing ldap-account-manager (--configure):
>>>> EOF on stdin at conffile prompt
>>>> Errors were encountered while processing:
>>>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>> Note that the configuration files were not modified during the test,
>>> so this should not happen.
>> this is a bug (#582020) in the lenny version of ldap-account-manager. It
>> was fixed in 3.0.0-2. The bug affects all package upgrades.
>> How should we proceed with this bug, merge it with #582020 or tag it lenny?
> Ideally, this would be fixed in lenny too.
The problem is that a bug in the lenny package version leads to a
question on an package upgrade. The question cannot be eliminated by a
fix in a new package version because the error already exists on the
machine when the lenny version is installed.
This bug is fixed in the squeeze version of the package.
Now my questions are:
* Is this kind of bug important enough to be fixed in a lenny update
* Will there be any update release (5.0.8) of lenny before squeeze?
* What is the correct upload queue (lenny-proposed-updates with urgency
Thanks in advance for your help.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----