WHOOPS! Mixed repositories

aquaboot · 05-18-2009, 08:06 PM

Hi All,

I am running testing and accidentally uncommented unstable in my sources.list file. Before I noticed the error, I ran an aptitude update and then aptitude full-upgrade with both testing and unstable active. To try to fix things, I commented out unstable and ran aptitude update and then aptitude full upgrade again. Aptitude still shows 192 mb of packages that I believe are still a mix of the two repositories. Is there a way to fix this problem so that I'm just back to testing or am I hosed?

Thanks,

ab

jailbait · 05-18-2009, 08:17 PM

I don't think that you are hosed. The situation is the same as if you were running testing and decided to move to the latest cutting edge version of a few packages by compiling them from source. If you have bad problems with an unstable package then delete that package and reinstall it from the testing repository.

---------------------
Steve Stites

aquaboot · 05-18-2009, 08:29 PM

Makes sense. Thanks for the response!

-ab

aquaboot · 05-18-2009, 11:19 PM

Hmm... now Synaptic is returning this:

unable to find expected entry restricted/binary-i386/Packages in Meta-index file (malformed Release file?)

Only has happened since my snafu.

-ab

AlucardZero · 05-19-2009, 10:59 AM

You can downgrade everything back to testing, most likely. Modify/create /etc/apt/preferences:

Code:

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

Package: *
Pin: release a=unstable
Pin-Priority: 550

See the Debian docs and a Google for apt-pinning.

Run aptitude update then aptitude upgrade (I think).

To get rid of the last error, you may have to reuncomment the unstable line then aptitude update, not sure.

Once done, change the testing pin to 650; this will tell apt to always prefer testing but you will have the option of unstable (aptitude install -t unstable package).