LinuxQuestions.org - Installing Packages From Testing Or Unstable While Using Stable

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - Installing Packages From Testing Or Unstable While Using Stable (https://www.linuxquestions.org/questions/debian-26/installing-packages-from-testing-or-unstable-while-using-stable-4175472114/)

Installing Packages From Testing Or Unstable While Using Stable

Is there any way to install packages from the testing or unstable repositories while still using stable? My problem is that I'm trying to install $PACKAGE from testing, but it depends on $DEPENDENCY_X.X+1 which is >= $DEPENDENCY_X.X Is there any way around this apart from moving to testing?

Add in a testing.list and unstable.list in /etc/apt/sources.list.d. Then keep them commented out (# at the beginning of the line). When you need to use one or the other, edit the file, remove the # to enable the repository, apt-get update to download the repository information, then apt-get install -t testing wahtever or apt-get install -t unstable whatever. Then after you're done, re-comment out the repository.

Now, take into consideration that doing this with some packages will cause all kinds of issues as it will create a dependency heck for other programs that want a version of a dependency below x.x.x while the program you're installing wants the depenedency of x.x.x+1 or greater. If you use this a lot, you may run into problems. I haven't when I've used it before (I now just run testing), but I've known it to happen.

Hi,

what you trying to do is typically called "running a mixed system". Sometimes this is fine, but sometimes the dependencies can't really be met. I highly recommend backporting the package instead (I'm assuming you have already check if there is an official backport).

Ie get ths src deb from testing and build it against your stable system. See for example:

https://www.linuxquestions.org/quest...3/#post4979977

This approach will keep you on stable but give you the newer version of the package you want, without changing the versions of the packages it depends on. Note however that this works better for some packages than it does for others: eg you may need to backport one or more dependency as well.

What package are you wanting to install?

Evo2.

If you must know, I'm trying to install aircrack-ng (for my own network- I don't do any illegal cracking). And I know I can run a mixed system, but I really, really don't want to for the reasons you've mentioned. There's nothing I can run it in apart from the rest of the system? Maybe something roughly equivalent to a jail?

HI,

Quote:

Originally Posted by wafflesausage (Post 5002975)

If you must know, I'm trying to install aircrack-ng (for my own network- I don't do any illegal cracking).

....that's what someone who did do illegal cracking would say ;-)

Code:

% apt-cache showsrc aircrack-ng|grep Build-Depends

Build-Depends: debhelper (>= 8.0.0), libpcap0.8-dev, libgcrypt11-dev, libsqlite3-dev (>= 3.4), zlib1g-dev, python (>= 2.6.6-3~), hardening-includes

AFAICT all of these are in Wheezy, so backporting should be trivial (see the link in my previous post).

Evo2.

A "mixed system" is testing + sid.
Stable + testing is a "broken system" - just don't do it.

Backporting is the way to go.

Hi,

Quote:

Originally Posted by descendant_command (Post 5003004)

A "mixed system" is testing + sid.
Stable + testing is a "broken system" - just don't do it.

:-)

Actually I don't do either of those. It's either sid xor stable for me.

Quote:

Backporting is the way to go.

Indeed.

Cheers,

Evo2.

Stable + unstable : Reversing to stable

Hi,

How can I go back to stable after I did this (I run stable) :

Code:

apt-get install rawtherapee/testing

(output below where I did not go as far as breaking glibc dependencies.
I never used the testing repos before)

I only read afterwards this thread that confirmed that running mixed versions
was a bad idea.

So what is the best way to come back to stable ?

1) edit /etc/apt:list and remove
deb http:/blabla testing main contrib non-free
And then which step 2 is best ?
2a) dpkg -r rawtherapee
2b) dpkg --purge rawtherapee
2c) apt-get --reinstall rawtherapee (presumably not having the unstable repos may work)
2d) aptitude update
2e) do nothing
(I stopped the package upgrade because of a warning on glibc and kdm being affected,
maybe I stopped early enough, and maybe nothing was updated - files were only unpacked if I understand correctly...)

Thanks

Code:

# apt-get install rawtherapee/testing

Selected version '4.0.11+dfsg-1' (Debian:testing [amd64]) for 'rawtherapee'

The following extra packages will be installed:

gir1.2-freedesktop gir1.2-glib-2.0 glib-networking glib-networking-common glib-networking-services gnome-desktop3-data libc-dev-bin libc6 libc6-dev libelfg0 libffi6 libfftw3-3 libfftw3-double3 libfftw3-single3 libgirepository-1.0-1 libglib2.0-0 libglib2.0-bin libglibmm-2.4-1c2a libgnome-desktop-3-2 locales python-gi rawtherapee-data 

Suggested packages:

glibc-doc libfftw3-bin libfftw3-dev python-gi-cairo The following NEW packages will be installed:

libelfg0 libffi6 libfftw3-double3 libfftw3-single3 The following packages will be upgraded:

gir1.2-freedesktop gir1.2-glib-2.0 glib-networking glib-networking-common glib-networking-services gnome-desktop3-data libc-dev-bin libc6 libc6-dev

libfftw3-3 libgirepository-1.0-1 libglib2.0-0 libglib2.0-bin libglibmm-2.4-1c2a libgnome-desktop-3-2 locales python-gi rawtherapee rawtherapee-data

19 upgraded, 4 newly installed, 0 to remove 

Do you want to continue [Y/n]? y

Get:1 http://ftp2.fr.debian.org/debian/ testing/main libc-dev-bin amd64 2.17-93 [223 kB]

Get:23 http://ftp2.fr.debian.org/debian/ 

saving uncommitted changes in /etc prior to apt run

1 file changed, 3 insertions(+)

Preconfiguring packages ...

(Reading database ... 206221 files and directories currently installed.) 

Preparing to replace libc-dev-bin 2.13-38 (using .../libc-dev-bin_2.17-93_amd64.deb) ...

Unpacking replacement libc-dev-bin ...

Preparing to replace libc6-dev:amd64 2.13-38 (using .../libc6-dev_2.17-93_amd64.deb) ...

Unpacking replacement libc6-dev:amd64 ...

Preparing to replace locales 2.13-38 (using .../locales_2.17-93_all.deb) ...

Unpacking replacement locales ...

Preparing to replace libc6:amd64 2.13-38 (using .../libc6_2.17-93_amd64.deb) ...

Checking for services that may need to be restarted...

Checking init scripts...

Stopped glibc upgrade. Please retry the upgrade after you have checked or stopped services by hand.

dpkg: error processing /var/cache/apt/archives/libc6_2.17-93_amd64.deb (--unpack):

subprocess new pre-installation script returned error exit status 1 Processing triggers for man-db ...

Errors were encountered while processing:

/var/cache/apt/archives/libc6_2.17-93_amd64.deb

E: Sub-process /usr/bin/dpkg returned an error code (1)

Solved this way :

1) Remove the testing repo
2) Done then the following (maybe there was a more elegant solution)

# apt-get check
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
libc-dev-bin : Depends: libc6 (> 2.17) but 2.13-38 is installed
libc6-dev : Depends: libc6 (= 2.17-93) but 2.13-38 is installed
locales : Depends: glibc-2.17-1 but it is not installable

# apt-get -f install
The following extra packages will be installed:
locales-all
The following packages will be REMOVED:
build-essential g++ g++-4.7 libc6-dev libmjpegtools-dev libpcap-dev libpcap0.8-dev libquicktime-dev libreoffice-help-fr libreoffice-l10n-fr libstdc++6-4.7-dev locales zlib1g-dev

# apt-get install build-essential g++ g++-4.7 libc6-dev libpcap-dev libpcap0.8-dev libquicktime-dev libreoffice-help-fr libreoffice-l10n-fr libstdc++6-4.7-dev locales zlib1g-dev

without libmjpegtools-dev (not present in stable)

Checking it is ok
# apt-get check
Reading package lists... Done
Building dependency tree
Reading state information... Done

# apt-get update
Reading package lists... Done
(nothing else done - all up to date)