Re: no testing packages?
You can have both testing and stable, for example, in your
sources.list. In this case, its trivial, just add a line for each
existing line in that file, and s/testing/stable/.
Using /e/a/preferences, you can set up "pinning", and do something to
the effect of "Everything should be 'stable' version, unless I
explicitly say 'testing'". This would otherwise be impossible,
because testing is guaranteed to have a version at least as high as
stable, and you'd end up with all testing packages after your first
upgrade.
This buys you the ability to install packages which do not exist in
testing, but do exist in stable. (It may not work as well sometimes,
because of package Conflicts).
You can do things like: apt-get install dselect/sid aptitude/testing
dpkg/stable.
Note, however, that downgrades are not generally supported.
Justin
On Sun, Nov 06, 2005 at 12:29:55AM +0200, trv wrote:
> Hello. I'm fairly new in debian and i have a question simiral to the one
> above about packages in testing or stable state and how they are moved.
> I use "testing", so in sources.conf all the servers are for testing
> binaries.
> Last night i wanted to install kdevelop. I use aptitude, so, i searched
> for it, and found nothing.
> Then i searched in packages.debian.org and i found these two matches:
> stable: kdevelop3 3.2.0-1
> (and a bunch of other packages e.g. kdevelop3-data,-dev etc)
> unstable: kdevelop3 3.2.2-0.5
> (and again a bunch of other packages e.g. kdevelop3-data,-dev etc)
> {latest stable version in kdevelop.org is 3.2.3, but it's not a binary!
> So as you can see there are stable and unstable packages, but not
> testing! I suppose this is the reason aptitude couldn't find any.
> So what am i supposed to do? Download manually all the (stable) debs
> needed and install it without aptitude? Could be a lot of packages and
> who knows about dependencies issues..
Reply to: