-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
"NA" == Nelson Abramson <[EMAIL PROTECTED]>
NA> Playing around with dselect, I have six or so
NA> dependency issues...
The simple answer is that there are some packages that require
(are dependent on) other packages that are not in the archive yet
(or that haven't been mirrored by your mirror).
This situation can arise from one of several possible scenarios:
1. A developer using some non-PowerPC architecture system (i.e.,
most of them) has uploaded binary debs and source for a new
version of a package. The source tree is used to build two or
more binary packages, at least one of which is architecture
independent (binary-all). Until the build-daemon builds the
architecture-dependent binary packages for PowerPC and uploads
them to the archive, you won't be able to install the
binary-independent package. This scenario explains packages
such as gnome-panel-data and gnome-help-data.
2. An architecture-dependent binary has been uploaded, along with
its source, but the PowerPC build-daemon (or a PPC-using
developer) hasn't gotten around to building the binaries yet.
This scenario is probably the situation with libnss-db.
3. Just like 1 or 2, but one of the binary packages cannot be
built on PowerPC because of a coding or dependency problem.
These problems won't be fixed until someone can take a look at
the problem, solve it, and submit a patch or upload a new
version of the offending package. (A recent example was
libglade, which couldn't be compiled with the current version
of the bonobo package. (That problem has been resolved.))
For all three scenarios, the easiest solution is just to wait.
Eventually, the build-daemon will catch up, or a PowerPC developer
will fix the problems or upload binary packages themselves.
If you want to have the packages *now*, you can download the
source and build them yourself (if your /etc/apt/sources.list file
has the necessary deb-src lines (just like the deb lines, but with
deb-src instead, usually), you can type (as root)
apt-get -b source <package>
which will download and build the package; or, as an ordinary user
apt-get source <package>
which will download, untar, and patch the source tree. You would
then cd into the directory (usually <package>-<version>.<subversion>),
and type
dpkg-buildpackage -b -uc -rfakeroot
which will build the package (-b), with an unsigned changes file
(-uc), and uses ``fakeroot'' as the root command (allows you to
masquerade as root for the purposes of creating the package
without actually having to be root or have all of root's
privileges).
If you have all of the necessary build-dependencies (you can check
first by looking at the Build-Depends line in the
<package>-<version>/debian/control file), and there are no coding
problems, the deb(s) should be built in the directory above the
source tree, and you can install them by typing (as root)
dpkg -i <package>_<version>-<debian version>_<architecture>.deb
Voila!
If you find problems during the build and can fix them, do so, and
file a bug report against the *binary* package with a description
of the problem you encountered along with any other information
about how you fixed it (including patches, if applicable) or tried
to fix it.
I hope that helps.
CMC
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Behind the counter a boy with a shaven head stared vacantly into space,
a dozen spikes of microsoft protruding from the socket behind his ear.
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
C.M. Connelly [EMAIL PROTECTED] SHC, DS
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and GNU Privacy Guard
<http://www.gnupg.org/>
iD8DBQE6AeDizrFKeh3cmQ0RApddAJ45mqXXzp0GySpeTco37gER83uWnACgjaRe
v/vIioGQEmsjeJsjV4CrZpM=
=I0Ms
-----END PGP SIGNATURE-----
