Debian-news is about one simple thing - news about Debian GNU/Linux and the top free distributions based on Debian GNU/Linux.


 

How to install a single package from Debian Sid or Debian Testing

Today I was in need to install 1 single package from the unstable release of Debian in a server installed with the stable release, so what’s the best way to get this done ? For this example I’ll use the package drush because there are a lot of differences in the versions between the different release of Debian

Read more here

2 Responses to “How to install a single package from Debian Sid or Debian Testing” »

  1. Comment by Jimmy — December 6, 2012 @ 6:23 pm

    I don’t know if that is possible. Packages have dependencies and those have other dependencies and if you pull them all you will end up with a khimera mixing up SId or Testing with Stable (or Oldstable). I would not recommend trying this.

    Backports *may* have something for you. Maybe.

  2. Comment by Andrea — December 16, 2012 @ 3:32 pm

    The only reliable way is, get the deb file(s), and try using gdebi. Check listed dependencies which are not met, look for and collect ALL required deb files FROM THE SAME REPO you got the first package from.

    ALL collected deb’s must then be manually examined with gdebi before installing them:
    – new packages that don’t show unmet dependencies may be installed *ALMOST* safely (especially binary library files).
    – updated (existing) packages that don’t show unmet dependencies *might be installed*, but may break some other packages, namely those depending on previous version of the package being replaced. My advice is, make a backup copy of the (original) deb file before proceeding, so you can rollback safely, and make a backup of your current version of any config files within the package (those in /etc/…. as well as those in your home dir)
    – any package showing unmet dependencies must be examined. If dependency deb’s can be fetched, download them from the repo of the first package, and examine them first. Once all dependencies have been examined & installed, there is nothing preventing a package from being installed.

    Please note though, that packages (and their maintainers) couldn’t and didn’t know about possible future changes in other packages. Thus, even packages that install successfully, may not work as expected. This is especially true if packages are particularly complex, depend on certain directory/paths/links/libraries/binaries to be present.

    I wouldn’t even try to install (from another repo) anything involving: kernel, kernel modules, video drivers, networking, X system, etc, while I would say it is fairly safe to install applications and their libraries (beware of related GTK / QT library dependencies though).

    But you’re not left alone! Whenever you can’t manage (or risk) to install a deb from outside your repo’s, you can always build them from source!

RSS feed for comments on this post. TrackBack URI

Leave a comment

Leave a Reply

Your email address will not be published. Required fields are marked *


*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Debian-News is not related to the Debian Project.
All logos and trademarks on this site are property of their respective owners.