On Sun, 15 Mar 2015, 慕冬亮 wrote: > > > On 03/15/2015 02:09 AM, Patrick Bartek wrote: > > On Sat, 14 Mar 2015, James wrote: > > > >> > >> On 03/14/2015 12:47 PM, kamaraju kusumanchi wrote: > >>> On Sat, Mar 14, 2015 at 12:08 PM, James <bjloc...@lockie.ca> > >>> wrote: > >>>> I'm trying to upgrade wheezy to testing. > >>>> I am following the instructions at: > >>>> http://unix.stackexchange.com/questions/90389/how-to-upgrade-debian-stable-wheezy-to-testing-jessie > >>>> > >>>> I get this error when I try apt-update: > >>>> > >>>> W: Failed to fetch cdrom://[Debian GNU/Linux 7 _Wheezy_ - > >>>> Official Snapshot amd64 LIVE/INSTALL Binary > >>>> 20150114-03:58]/dists/testing/main/binary-amd64/Packages Please > >>>> use apt-cdrom to make this CD-ROM recognized by APT. apt-get > >>>> update cannot be used to add new CD-ROMs > >>>> > >>>> Does anyone know why? > >>>> > >>> Most likely a misconfigured /etc/apt/sources.list file. Can you > >>> post the contents of it? How are you upgrading the system - over > >>> the network or by using an installation CD? > >>> > >>> raju > >> sources.list: > >> > >> # deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot amd64 > >> LIVE/INSTALL Binary 20150114-03:58]/ testing main > >> > >> deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot amd64 > >> LIVE/INSTALL Binary 20150114-03:58]/ testing main > > Comment out (or delete) the above entry. It is the original Wheezy > > install CD. You don't need it if you're upgrading to testing. > > > >> deb http://mirror.its.dal.ca/debian/ testing main contrib non-free > >> deb-src http://mirror.its.dal.ca/debian/ testing main contrib > >> non-free > >> > >> deb http://security.debian.org/ testing/updates main contrib > >> non-free deb-src http://security.debian.org/ testing/updates main > >> contrib non-free > >> > >> # testing-updates, previously known as 'volatile' > >> deb http://mirror.its.dal.ca/debian/ testing-updates main contrib > >> non-free deb-src http://mirror.its.dal.ca/debian/ testing-updates > >> main contrib non-free > > Also, if your intent is to upgrade to testing/Jessie, enter "jessie" > > instead of "testing" in those sources lists; otherwise, when Jessie > > becomes Stable, you will continue upgrading with the NEW testing > > release. > This is a small and detailed problem I encountered before !
This isn't a "problem," per se. It's just the way the process works. > > Some doing this, so they have the more current release files like a > > Rolling Release without having to use backports. > I have a problem about this ?? > So If I use "stable" instead of "Jessie" or "Wheezy" , I will have a > rolling release like "archlinux" or "gentoo"! > Is it ??? Not really. You'll end up with a system which is a mix of the new Stable and what used to be Stable. It may even break your system. Debian isn't set up for roll releasing. I accidently did this once by "upgrading" an Etch system after Lenny had become Stable. My sources lists for Etch had Stable entered and not Etch. I ended up with a hydrid of Etch and Lenny. Surprisingly, it still worked. I "fixed" it by properly dist-upgrading to Lenny. If you want to avoid problems, use the release name in your sources list, and not the general names Testing, Stable, etc. Of course, there are those who don't do this, but they have specific reasons for doing so, and know what they are doing. B -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150314232223.2f58d...@debian7.boseck208.net
