dpkg oddities

Has anyone on this list running lenny succeeded in installing any or all of the following packages who is not running any of the speakup distributions? I'm trying to find out if what happens here is speakup specific or not. The packages could be installed using a command line like: aptitude -y install clamav nethack-console podracer -r <cr> and I have main contrib non-free enabled in my sources.list file.

To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: Where is Phobos P430 QFE X1034A Driver
    ... The following packages are available: ... Installing Phobos P430 Adapter Driver for 32 bit PCI QuadPort ... devfsadm: driver failed to attach: pqfe ...
  • Re: Why no R in Fedora (was Statistical Package (like Minitab) for Linux)
    ... > The fedora rpm provided at the CRAN site contains very few add-on ... > packages would provide a large amount of functionality. ... > Users can easily install.packageson top of this more stuff from CRAN. ... > I always seem to end up installing a few packages eg. lineno, ...
  • Re: OpenCOBOL/GNUCobol
    ... Did you compile the compiler AND run make check ... packages and it can never seem to resolve all the conflicts. ... GNU Cobol MAY require the following external library to be installed: ... NOTE - libltdl is NOT needed when installing on Linux, ...
  • Re: Linux/Python Issues
    ... It doesn't suck if you're just installing one program, ... tool to retrieve packages, but then the developers got "feature envy" ... you've got to face the problem that your distribution isn't going to ...
  • Re: yumex vs yum
    ... From Yumex I found that installing some packages resulted in success && these packages not being installed. ... If you are using the yumex version from Extras, a bug report would be helpful to inform the developer / maintainer that there is a problem so it can be corrected. ... the problem encountered using yumex which does not yet have a policy probably caused a lot of &post and &pre scriptlet errors on the system that yumex was run on. ...