Re: wheezy to testing
On Sun, Mar 15, 2015 at 07:50:11PM +0800, 慕冬亮 wrote: > > > On 03/15/2015 07:37 PM, Lisi Reisz wrote: > >On Sunday 15 March 2015 04:41:00 慕冬亮 wrote: > >>So If I use "stable" instead of "Jessie" or "Wheezy" , I will have a > >>rolling release like "archlinux" or "gentoo"! > >>Is it ??? > >Not "stable", no. If you use "testing" instead of a code name you will > Why ?? I can't understand ! > >effectively have a rolling release, but it will be a very rocky ride for > >about a month after Jessie becomes Stable. > > > >Lisi > > > > > I don't understand it clearly ! > I have an simple understanding of Debian development mode ! > Jessie -->>(after a frozen time) > testing stable > Debian uses code names for releases at least partly to avoid confusion. The codenames mean that when jessie is released as stable, stretch will become testing, wheezy becomes -> oldstable, squeeze-lts -> oldoldstable and so on. Etch == Debian 4 Lenny == Debian 5 Squeeze == Debian 6 == oldstable now Wheezy == Debian 7 == Stable now Jessie == Debian 8 (when released as stable) == Testing now Stretch == Debian 9 (when released as stable) == Testing once Jessie is released ... Buster == Debian 10 (when released as stable) == Testing once Stretch is released ... If you pin to Stable, then you will hit large changes as and when each release is made and then stability for the next couple of years with minimal changes. If you pin to Testing, then you'll be OK for anything up to a couple of years until a new release is made - if you pin to a release name, you can get up to five years :) All the very best, AndyC > I think if I use "stable" or "testing" ,I will sync with corresponding > version , is it ? > This is like the rolling version ! > So I don't what the problem is !!! > mudongliang > > > -- > 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/blu437-smtp84156f1e9f527d329de9bebc...@phx.gbl -- 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/20150315132103.ga2...@galactic.demon.co.uk
Re: wheezy to testing
On Sun, 15 Mar 2015 12:37:02 + Lisi Reisz wrote: Hello Lisi, >Do you use aptitude? Or can this also be done with apt(-get)? By and large, I use Synaptic. Occasionally, I use apt-get, but it's rare. >And yes, I know that this can be the case - but would you advise a >newbie, who hadn't yet learnt how to be selective with upgrades, to try >it?? A complete newbie, probably not. OTOH, somebody with a techie background, but new to Debian, maybe >Being selective obviously solves - or rather avoids - the deluge >problem. ;-) Of course. ;-) -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Is she really going out with him? New Rose - The Damned pgpadneRkIC7t.pgp Description: OpenPGP digital signature
Re: wheezy to testing
On 03/15/2015 08:24 PM, Dalios wrote: On 03/15/2015 01:50 PM, 慕冬亮 wrote: On 03/15/2015 07:37 PM, Lisi Reisz wrote: On Sunday 15 March 2015 04:41:00 慕冬亮 wrote: So If I use "stable" instead of "Jessie" or "Wheezy" , I will have a rolling release like "archlinux" or "gentoo"! Is it ??? Not "stable", no. If you use "testing" instead of a code name you will Why ?? I can't understand ! effectively have a rolling release, but it will be a very rocky ride for about a month after Jessie becomes Stable. Lisi I don't understand it clearly ! I have an simple understanding of Debian development mode ! Jessie -->>(after a frozen time) testing stable I think if I use "stable" or "testing" ,I will sync with corresponding version , is it ? This is like the rolling version ! So I don't what the problem is !!! mudongliang I think that you have got something wrong. But I am not sure I can explain this. Let's try. 1. Currently you can use "testing" and "jessie" interchangeably. It is suggested that you only use one of them and usually the right choice would be the "jessie" instead of "testing". 2. When the new Debian stable will be released it will be "Debian 8, codename: Jessie". 3. After the release if you have "jessie" on your /etc/apt/sources.list file then you will be running stable. So after the release of the new Debian stable the words "jessie" and "stable" can be used interchangeably. 4. But if you have "testing" then you will continue to run testing which will then have another codename, Stretch. In other words after the release of Debian 8, codename: Jessie as the new Debian stable the words "testing" and "stretch" will be able to be used interchangeably. 5. I guess one could claim that "testing" is a rolling release (which it is almost true in it's Debian way and when not on freeze). But using the This is good and it solves my direct problem ! codename (jessie or stretch or whatever) will not get you rolling in any sense. Dalios I think I have understood your meaning ! Thank you ! Besides , can I have your words in my google+ group ?? mudongliang -- 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/blu436-smtp159e9fdb75ce6136cf16e7ebc...@phx.gbl
Re: wheezy to testing
On Sunday 15 March 2015 12:00:27 Brad Rogers wrote: > On Sun, 15 Mar 2015 11:37:25 + > Lisi Reisz wrote: > > Hello Lisi, > > >Not "stable", no. If you use "testing" instead of a code name you will > >effectively have a rolling release, but it will be a very rocky ride > >for about a month after Jessie becomes Stable. > > I've been using 'testing' rather than a code name for years(1). It's > very rare I've had issues as a direct result of that. Perhaps twice. > Even after a large influx of packages after a freeze ends. For the > most part, problems can be avoided by being selective with upgrades, so > things don't get removed that you want/need. This may mean some > packages are in the upgrade queue for several days, occasionally a week > or two, until the necessary package updates migrate through from Sid. > > (1) Ten, at least. Do you use aptitude? Or can this also be done with apt(-get)? And yes, I know that this can be the case - but would you advise a newbie, who hadn't yet learnt how to be selective with upgrades, to try it?? Being selective obviously solves - or rather avoids - the deluge problem. ;-) Lisi -- 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/201503151237.02922.lisi.re...@gmail.com
Re: wheezy to testing
On Sunday 15 March 2015 12:00:09 慕冬亮 wrote: > On 03/15/2015 07:41 PM, Lisi Reisz wrote: > > In spite of what I have just said, I entirely agree with this advice and > > have always used code names myself, so that I can control when version > > changes happen. > > > > But then I don't like rolling releases. The one rolling release that I > > have ever used - PCLinuxOS - bit me so hard, that I now would not touch a > > rolling release with a barge pole. > > > > Lisi > > I don't use any rolling release before ! But I will try one ! > There are many problems about upgrading of wheezy in the mailing list ! You hear about the problems. It's when things go wrong that people ask for help. If things go right, they don't need help! Bear in mind that Jessie is not yet Stable, and there are therefore still problems of various kinds, including in upgrade. These will be significantly reduced in number before Jessie becomes Stable and upgrading is encouraged officially!! > Clearly , it is too! > The rolling release forbids this bad thing ! > Can you list what the PCLinux bit you ? I‘m curious about it! > mudongliang There was suddenly an enormous number of updates and the whole thing crashed beyond rescue, and as far as I could see beyond control. Give me Debian's controlled updates - using code names, of course. If you use the names testing and stable in your sources.list, Debian can bite you in the same way. If you are using code names, you have the option of not upgrading at all! Some people are still on Lenny - though I haven't heard of Etch recently. Many people prefer to wipe the slate clean. They back up, back-up the back-ups, and reinstall. In an ideal world, they install on a new partition or hard drive and retain the old, working installation until the new one is set up and working. But I'm not sure how many actually can, or do, do that. Lisi Lisi -- 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/201503151233.28559.lisi.re...@gmail.com
Re: wheezy to testing
On 03/15/2015 08:10 PM, Lisi Reisz wrote: On Sunday 15 March 2015 11:50:11 慕冬亮 wrote: On 03/15/2015 07:37 PM, Lisi Reisz wrote: On Sunday 15 March 2015 04:41:00 慕冬亮 wrote: So If I use "stable" instead of "Jessie" or "Wheezy" , I will have a rolling release like "archlinux" or "gentoo"! Is it ??? Not "stable", no. If you use "testing" instead of a code name you will Why ?? I can't understand ! effectively have a rolling release, but it will be a very rocky ride for about a month after Jessie becomes Stable. Lisi I don't understand it clearly ! I have an simple understanding of Debian development mode ! Jessie -->>(after a frozen time) testing stable I think if I use "stable" or "testing" ,I will sync with corresponding version , is it ? This is like the rolling version ! So I don't what the problem is !!! Here goes, for what it is worth. Someone will correct me if I get it wrong. Stable is stable. It sits there, more or less unchanged (except for security updates), until the next Testing is ready and becomes Stable, in one jump, and the previous Stable becomes Old Stable. Stable (the new one) then just sits there until .. etc. etc. Testing gets updated, and the new software moves up, as it becomes available, until Testing goes into freeze. So it rolls. More or less. Except when it freezes. While Testing is in freeze, the new software that would normally have moved up as it was ready, sits in Sid (Unstable). When Jessie becomes Stable, Testing will no longer be frozen and all the software queued in Sid will come up at once. Hence the brief turmoil. It will then settle down to new software moving up as it is ready, until the next freeze. Testing is always Testing. It does not become Stable. A version (Jessie next) goes from Testing to Stable, but Testing itself still exists and continues to roll. It does not get replaced. Stable gets effectively replaced. Does that help at all? Lisi Lisi That's great! I have a deep understanding of it ! Thank you , Lisi mudongliang -- 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/blu437-smtp515968e69c0f28a69bb3ffbc...@phx.gbl
Re: wheezy to testing
On 03/15/2015 01:50 PM, 慕冬亮 wrote: > > > On 03/15/2015 07:37 PM, Lisi Reisz wrote: >> On Sunday 15 March 2015 04:41:00 慕冬亮 wrote: >>> So If I use "stable" instead of "Jessie" or "Wheezy" , I will have a >>> rolling release like "archlinux" or "gentoo"! >>> Is it ??? >> Not "stable", no. If you use "testing" instead of a code name you will > Why ?? I can't understand ! >> effectively have a rolling release, but it will be a very rocky ride for >> about a month after Jessie becomes Stable. >> >> Lisi >> >> > I don't understand it clearly ! > I have an simple understanding of Debian development mode ! > Jessie -->>(after a frozen time) > testing stable > > I think if I use "stable" or "testing" ,I will sync with corresponding > version , is it ? > This is like the rolling version ! > So I don't what the problem is !!! > mudongliang > > I think that you have got something wrong. But I am not sure I can explain this. Let's try. 1. Currently you can use "testing" and "jessie" interchangeably. It is suggested that you only use one of them and usually the right choice would be the "jessie" instead of "testing". 2. When the new Debian stable will be released it will be "Debian 8, codename: Jessie". 3. After the release if you have "jessie" on your /etc/apt/sources.list file then you will be running stable. So after the release of the new Debian stable the words "jessie" and "stable" can be used interchangeably. 4. But if you have "testing" then you will continue to run testing which will then have another codename, Stretch. In other words after the release of Debian 8, codename: Jessie as the new Debian stable the words "testing" and "stretch" will be able to be used interchangeably. 5. I guess one could claim that "testing" is a rolling release (which it is almost true in it's Debian way and when not on freeze). But using the codename (jessie or stretch or whatever) will not get you rolling in any sense. Dalios -- 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/55057a0a.3090...@eumx.net
Re: wheezy to testing
On Sun, 15 Mar 2015 11:37:25 + Lisi Reisz wrote: Hello Lisi, >Not "stable", no. If you use "testing" instead of a code name you will >effectively have a rolling release, but it will be a very rocky ride >for about a month after Jessie becomes Stable. I've been using 'testing' rather than a code name for years(1). It's very rare I've had issues as a direct result of that. Perhaps twice. Even after a large influx of packages after a freeze ends. For the most part, problems can be avoided by being selective with upgrades, so things don't get removed that you want/need. This may mean some packages are in the upgrade queue for several days, occasionally a week or two, until the necessary package updates migrate through from Sid. (1) Ten, at least. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Just stop and take a second U & Ur Hand - P!nk pgpgJBvHS9qWa.pgp Description: OpenPGP digital signature
Re: wheezy to testing
On Sunday 15 March 2015 11:50:11 慕冬亮 wrote: > On 03/15/2015 07:37 PM, Lisi Reisz wrote: > > On Sunday 15 March 2015 04:41:00 慕冬亮 wrote: > >> So If I use "stable" instead of "Jessie" or "Wheezy" , I will have a > >> rolling release like "archlinux" or "gentoo"! > >> Is it ??? > > > > Not "stable", no. If you use "testing" instead of a code name you will > > Why ?? I can't understand ! > > > effectively have a rolling release, but it will be a very rocky ride for > > about a month after Jessie becomes Stable. > > > > Lisi > > I don't understand it clearly ! > I have an simple understanding of Debian development mode ! > Jessie -->>(after a frozen time) > testing stable > > I think if I use "stable" or "testing" ,I will sync with corresponding > version , is it ? > This is like the rolling version ! > So I don't what the problem is !!! Here goes, for what it is worth. Someone will correct me if I get it wrong. Stable is stable. It sits there, more or less unchanged (except for security updates), until the next Testing is ready and becomes Stable, in one jump, and the previous Stable becomes Old Stable. Stable (the new one) then just sits there until .. etc. etc. Testing gets updated, and the new software moves up, as it becomes available, until Testing goes into freeze. So it rolls. More or less. Except when it freezes. While Testing is in freeze, the new software that would normally have moved up as it was ready, sits in Sid (Unstable). When Jessie becomes Stable, Testing will no longer be frozen and all the software queued in Sid will come up at once. Hence the brief turmoil. It will then settle down to new software moving up as it is ready, until the next freeze. Testing is always Testing. It does not become Stable. A version (Jessie next) goes from Testing to Stable, but Testing itself still exists and continues to roll. It does not get replaced. Stable gets effectively replaced. Does that help at all? Lisi Lisi -- 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/201503151210.26000.lisi.re...@gmail.com
Re: wheezy to testing
On 03/15/2015 07:41 PM, Lisi Reisz wrote: In spite of what I have just said, I entirely agree with this advice and have always used code names myself, so that I can control when version changes happen. But then I don't like rolling releases. The one rolling release that I have ever used - PCLinuxOS - bit me so hard, that I now would not touch a rolling release with a barge pole. Lisi I don't use any rolling release before ! But I will try one ! There are many problems about upgrading of wheezy in the mailing list ! Clearly , it is too! The rolling release forbids this bad thing ! Can you list what the PCLinux bit you ? I‘m curious about it! mudongliang -- 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/blu436-smtp155b3f12d7183fcc8216935bc...@phx.gbl
Re: wheezy to testing
On 03/15/2015 07:37 PM, Lisi Reisz wrote: On Sunday 15 March 2015 04:41:00 慕冬亮 wrote: So If I use "stable" instead of "Jessie" or "Wheezy" , I will have a rolling release like "archlinux" or "gentoo"! Is it ??? Not "stable", no. If you use "testing" instead of a code name you will Why ?? I can't understand ! effectively have a rolling release, but it will be a very rocky ride for about a month after Jessie becomes Stable. Lisi I don't understand it clearly ! I have an simple understanding of Debian development mode ! Jessie -->>(after a frozen time) testing stable I think if I use "stable" or "testing" ,I will sync with corresponding version , is it ? This is like the rolling version ! So I don't what the problem is !!! mudongliang -- 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/blu437-smtp84156f1e9f527d329de9bebc...@phx.gbl
Re: wheezy to testing
On Sunday 15 March 2015 06:53:00 慕冬亮 wrote: > On 03/15/2015 02:22 PM, Patrick Bartek wrote: > > 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 > >>>>> > >>>>> 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 > > I will accept the advice and use specific release name in the source.list ! > Thank you for explaining it for me ! In spite of what I have just said, I entirely agree with this advice and have always used code names myself, so that I can control when version changes happen. But then I don't like rolling releases. The one rolling release that I have ever used - PCLinuxOS - bit me so hard, that I now would not touch a rolling release with a barge pole. Lisi -- 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/201503151141.28023.lisi.re...@gmail.com
Re: wheezy to testing
On Sunday 15 March 2015 04:41:00 慕冬亮 wrote: > So If I use "stable" instead of "Jessie" or "Wheezy" , I will have a > rolling release like "archlinux" or "gentoo"! > Is it ??? Not "stable", no. If you use "testing" instead of a code name you will effectively have a rolling release, but it will be a very rocky ride for about a month after Jessie becomes Stable. Lisi -- 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/201503151137.25827.lisi.re...@gmail.com
Re: wheezy to testing
On 03/15/2015 02:22 PM, Patrick Bartek wrote: 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 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 I will accept the advice and use specific release name in the source.list ! Thank you for explaining it for me ! -- 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/blu437-smtp7825ca3511508d4683364cbc...@phx.gbl
Re: wheezy to testing
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 > >>> 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
Re: wheezy to testing
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 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 ! 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 ??? 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/blu437-smtp1044d8f6002d501991c9040bc...@phx.gbl
Re: wheezy to testing
On 03/15/2015 12:08 AM, James 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 have seen this page in detail ! It uses Internet mirror to upgrade that you used before ! 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? According to your report , your source.list file looks like a local mirror , not a network mirror! I think you should check your list file or go to official web to search a good file to replace ! mudongliang -- 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/blu436-smtp1856faa37dd2dd0081b98bcbc...@phx.gbl
Re: wheezy to testing
James 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 The first problem is that you are not using the official release notes. Start with the official release notes and follow the directions there. https://www.debian.org/releases/testing/releasenotes This is the particular step you are missing: https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#upgrade-process > Does anyone know why? It is rather a pet peeve of mine, sorry, but reading random things people write on the Internet is rather like listening to random drunk people talk in a pub. Sure some of them do actually say things that make sense, especially if you have had a few yourself first. But often they don't too. And so I always wonder why people go to stackexchange.com for Debian information instead of going to debian.org for Debian information. This truly is a mystery to me. In any case, to add my random voice to the random sounds of people on the Internet I suggest you look at the non-official but very useful redirector. The .net indicates that it isn't an official Debian project resource. The .net namespace is where Debian Developers try out new things and see how they do. This one is gaining in use and may become official one day. In any case you are wanting to use Testing already so this is a perfect match for you. http://http.debian.net/ Using the redirector your complete /etc/apt/sources.list file for Debian Wheezy 7 would be this for anywhere in the world. The portability of these addresses make the redirector much easier to document. deb http://http.debian.net/debian jessie main contrib non-free deb-src http://http.debian.net/debian jessie main contrib non-free deb http://http.debian.net/debian jessie-updates main contrib non-free deb-src http://http.debian.net/debian jessie-updates main contrib non-free deb http://security.debian.org/ jessie/updates main contrib non-free deb-src http://security.debian.org/ jessie/updates main contrib non-free Edit your /etc/apt/sources.list file and replace the entire contents with the above. Then "apt-get update" to load the new sources. If you see any errors go find the errors and fix the typos. I suggest never using "testing" but sticking with the release name "jessie" in this case just as I have done above. The normal lifecycle of testing is that right now it is in freeze. It is very good and reliable right now. But after release it will be unfrozen. Then it will become quite the wild ride again for a while as all of the backlog of upgrades flow through it. Best to stick with Jessie through the first few months after the unfreeze. Come back to Testing after the main thrash has passed through if you want. It also pains me to suggest adding contrib and non-free to the list. But you already had it in your original list. And as a practical matter there are drivers and documentation there that are needed. Don't forget the minimul system upgrade step first. But also read the rest of the document too. https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade Bob signature.asc Description: Digital signature
Re: wheezy to testing
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 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. Some doing this, so they have the more current release files like a Rolling Release without having to use backports. 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/20150314110954.3827f...@debian7.boseck208.net
Re: wheezy to testing
On Sat, 2015-03-14 at 13:14 -0400, James wrote: > > On 03/14/2015 12:47 PM, kamaraju kusumanchi wrote: > > On Sat, Mar 14, 2015 at 12:08 PM, James 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 This line allows apt-get to check the Wheezy CD-ROM for newer packages and install them if necessary. Since you are trying to move to Testing I would just comment this line out (with a #). If you are installing the new packages from a optical disk, you'll have to figure out how to add the disk to sources.list 'man apt-cdrom' ? > 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 > > -- 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/1426355531.18442.9.camel@schrock.email
Re: wheezy to testing
On 03/14/2015 12:47 PM, kamaraju kusumanchi wrote: On Sat, Mar 14, 2015 at 12:08 PM, James 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 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 -- 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/55046c60.9000...@lockie.ca
Re: wheezy to testing
On Sat, Mar 14, 2015 at 12:45 PM, David Christensen wrote: > On 03/14/2015 09:08 AM, James 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? > > > > But if goal is to install Debian Jessie amd64, I'd download the latest > Jessie amd64 netinst weekly build and use that: > > > cdimage.debian.org/mirror/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso > The net installation image is not necessary in this case. The OP is trying to upgrade from Wheezy to Jessie. The net installation image is only useful if the user is installing a brand new installation (not for upgrading). raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog -- 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/CABpbYafhKxSV6ixLfwgazfD6JT1vx5MbfLwrTB56kunZT=b...@mail.gmail.com
Re: wheezy to testing
On Sat, Mar 14, 2015 at 12:08 PM, James 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 -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog -- 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/cabpbyacjtfknjuh-dhrqywc2ng03w4vawxmfu+snssnkhn2...@mail.gmail.com
Re: wheezy to testing
On 03/14/2015 09:08 AM, James 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?
Because the package manager ("Apt", possibly others) is complaining that
it can't find packages:
https://wiki.debian.org/Apt
https://wiki.debian.org/SourcesList
This is a helpful utility for generating a sources.list file:
http://debgen.simplylinux.ch/
But if goal is to install Debian Jessie amd64, I'd download the latest
Jessie amd64 netinst weekly build and use that:
cdimage.debian.org/mirror/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso
David
--
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/550465c7.9030...@holgerdanske.com
wheezy to testing
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? -- 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/55045d11.2000...@lockie.ca
Upgrade from wheezy to testing and wine
I upgraded 64 bit wheezy to testing(Jessie) yesterday. 32 bit wine applications worked great until I ran apt-get autoremove. This broke quite a few 32 bit wine applications for me. I narrowed it down to two packages that were autoremoved: libxinerama1:i386 and libxrandr2:i386. Should I file a bug against a package suggesting including these as dependencies and if so how do I figure out which package should require them? -- 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/20140415213637.ga6...@crazycoder.us
