Your message dated Sun, 26 Feb 2012 00:18:27 +0000
with message-id <4f497a53.30...@p10link.net>
and subject line Re: Bug#661099: fpc depends on packages that can't be installed
has caused the Debian Bug report #661099,
regarding fpc depends on packages that can't be installed
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 ow...@bugs.debian.org
immediately.)
--
661099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fpc
Version: 2.4.0-2
Severity: grave
Justification: renders package unusable
Attempting to install fpc through aptitude or apt-get fails because of
the following packages that will not be installed:
fp-units-gnome1
fp-units-gtk
libcairo2-dev
libgtk2.0-dev
libpango1.0-dev
Aptitude simply says "Some packages were broken and have been fixed" and
goes on to say "Keep the following packages at their current version
(Not Installed)" and then the packages are listed. Apt-get complains
like this:
===begin quote===
$ sudo apt-get install fpc
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
fpc : Depends: fp-units-gtk but it is not going to be installed
Depends: fp-units-gnome1 but it is not going to be installed
E: Broken packages
$
===end quote===
-- System Information:
Debian Release: 6.0.4
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
try
apt-get install fp-units-gtk fpc libcairo2-dev libgtk2.0-dev
libpango1.0-dev fp-units-gnome1 libpixman-1-dev=0.24.0-1~bpo60+1
libpixman-1-0
That seems to work.
Good to hear it.
It appears the issue was you had a backports version of libpixman-1-0
installed but your package manager was trying to install a non-backports
version of libpixman-1-dev.
This kind of issue is an artifact of the way backports works. The
backports repositry is setup you have to explicitly requrest backports
packages be installed either by specifying an explicit version number,
by specifing a release name on the install command line or by
pinning.Normally this is what you want (you are supposed to pick and
choose backports not install them willy nilly) but it causes issues for
dev pacakges as they must generally be the same version as the
corresponding library package so if you install a backports version of a
library and then later try (directly or indirectly) to install the
corresponding dev package then you need to explicitly tell apt to
install the backports version of the dev package too.
It is particually important to be mindful of the difference between "is
not going to be installed" (which means the package is available but apt
is not planning to install it for some reason adding it to the command
line will often give you some hitns as to why) and "is not installable"
which means apt can't find a version of the package ot install at all.
Since this is not a bug in the FPC package and other than radically
changing the way backports and/or apt work there is no way for debian to
fix the issue I am now closing this bug.
--- End Message ---
