SteveRiley's post #54 got me curious, so I cloned an existing Saucy VM, and changed /etc/apt/sources.list to all the devel stuff:
As you can see, I haven't pulled the trigger on 'proposed' yet.
After an aptitude update I got these warnings:
But everything seems to be updating fine.
Code:
deb http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel main restricted multiverse universe deb-src http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel restricted main multiverse universe deb http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-updates main restricted multiverse universe deb-src http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-updates restricted main multiverse universe deb http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-backports main restricted universe multiverse deb-src http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-backports main restricted universe multiverse deb http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-security main restricted multiverse universe deb-src http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-security restricted main multiverse universe # deb http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-proposed restricted main universe multiverse # deb-src http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-proposed restricted main universe multiverse
After an aptitude update I got these warnings:
Code:
W: Conflicting distribution: http://mirror.cc.columbia.edu devel Release (expected devel but got saucy) W: Conflicting distribution: http://mirror.cc.columbia.edu devel-updates Release (expected devel-updates but got saucy) W: Conflicting distribution: http://mirror.cc.columbia.edu devel-backports Release (expected devel-backports but got saucy) W: Conflicting distribution: http://mirror.cc.columbia.edu devel-security Release (expected devel-security but got saucy)
Comment