Your message dated Thu, 22 May 2008 12:34:14 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Re: [php-maint] Bug#482384: php5-cli: Not installable
has caused the Debian Bug report #482384,
regarding php5-cli: Not installable
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.)
--
482384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482384
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: php5-cli
Version: php5-cli [5.2.5-3 (testing)]
Severity: grave
Justification: renders package unusable
php5-cli is not installable since its dependencies are wrong:
The following packages have unmet dependencies:
php5-cli: Depends: php5-common (= 5.2.0-8+etch11) but 5.2.5-3 is to be
installed
Jan
-- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (501, 'stable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Thu, May 22, 2008 12:24, Jan Völkers wrote:
> php5-cli is not installable since its dependencies are wrong:
>
> The following packages have unmet dependencies:
> php5-cli: Depends: php5-common (= 5.2.0-8+etch11) but 5.2.5-3 is to be
> installed
Hi,
The depends of the official packages seem just fine to me, as shown here:
http://packages.debian.org/etch/php5-cli
http://packages.debian.org/lenny/php5-cli
I think you may have made a mixup with your package manager. Check whether
your sources.list doesn't mix stable and testing/unstable sources. Trying
to completely remove (purge) all php5-related packages and then
reinstalling them from scratch may be the quickest solution.
I'm closing this bug since the packages look fine.
cheers,
Thijs
--- End Message ---
