Is this repo mixing a bad idea?
 

Hello,

I'm running stable and pinned testing to get a certain program. I kept testing pinned to keep the program updated but of course the pipe is open for testing updates for other things. Should I deactivate the testing pin or keep it open. I really have no need for other testing updates and don't want to end up with more of a mixed system than I already have. Here is:

/etc/apt/preferences.d/preferences:

Package: *
Pin: release a=stable
Pin-Priority: 700

Package: *
Pin: release a=testing
Pin-Priority: 650

/etc/apt/preferences:

Package: *
Pin: release a=stable
Pin-Priority: 700

Package: *
Pin: release a=testing
Pin-Priority: 650

Stable+Testing=bad idea
Testing+Sid=OK (that's what I do; it's called apt-pinning)
If you want the reasons and details about how to do it I suggest you do a web search.
jdk

P.S. If you're feeling a bit restricted by being in Stable (not an unusual feeling), I'd suggest you try Testing with no apt-pinning and see how you like it. Then when you're comfortable with Testing you can try the occasional apt-pinning to Sid. In my case most of my av packages are from Sid.

As jdkaye already said, what you are doing is a bad idea. The proper way to get newer software for your Stable system is to backport that software. In many cases this is trivial (of course depending on the software), look here for more info: http://backports.debian.org/

Should I just deactivate testing from my preferences file?

Thanks

I'd just comment out the testing repos until I was ready to update
just the one package.

But if a Big package with a ton of lib dependencies? Careful, you might shoot your eye out.

http://forums.debian.net/viewtopic.php?&t=114130

If you want to use Testing/Unstable packages in Debian Stable and they aren't available in the jessie-backports repository then backport it yourself by following this simple guide:
https://wiki.debian.org/SimpleBackportCreation