severity 482575 normal
reassign 482575 libldap2
retitle 482575 libldap2 is deprecated but not in oldlibs
thanks

On Fri, 23 May 2008, Wolfgang Leister wrote:

> Package: pine
> Severity: grave
> Justification: renders package unusable
> 
> By accident on my system pine was uninstalled by a dist-upgrade. 
> When trying to install pine again the following error message 
> occurs for "apt-get install pine":
> The following packages have unmet dependencies.
>   pine: Depends: libldap2 (>= 2.1.17-1) but it is not going to be installed
> 
> Trying to install libldap2 results in an uninstall of a lot of other packages:
> WARNING: The following essential packages will be removed.
> This should NOT be done unless you know exactly what you are doing!
>   apt debian-archive-keyring (due to apt)
>   0 upgraded, 1 newly installed, 280 to remove and 1 not upgraded.

Your report does not say it, but I bet you are not using the Debian version
of pine, but the pine.deb distributed by the University of Washington.

That would be like installing a package from sarge using "dpkg -i" on
a lenny system and expecting it to work. It does not have to work.

[ It is actually worse. It would be like installing a Red-Hat package
  on a Debian system and reporting it to Debian that it does not work ].

You could try adding a line like this to your sources.list

deb-src http://ftp.de.debian.org/debian lenny main contrib non-free

and then try to build pine by doing this:

apt-get --only-source build-dep pine
apt-get --only-source -b source pine

The resulting pine.deb depends on libldap-2.4-2, not on libldap2,
which seems to be obsolete in lenny.

Or you could also try alpine, which is in main.

In either case, as this is not a bug in pine but I see that libldap2
is not clearly tagged as deprecated I'm reassigning this bug to libldap2.



Note to libldap2 maintainer: If libldap2 is really deprecated, then it
should be in Section: oldlibs, so that people clearly see that a package
which depends on it is not a good thing to install on a lenny system.

Thanks.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to