Re: How was the slink -- potato switch? How will be potato -- woody? When?
Josip Rodin wrote: When you install from scratch you lose the configuration file changes on the old installation. It is not a problem, since most of the configs are default anyway. Set the debconf level to critical and you'll only get the most important questions. May I know how/ what/ where to set? Thus, I would like to know, how **LONG** after woody release, will potato be kept at the mirrors, before it will be put to the archive server. Probably a few days/weeks, depending on when the archive maintainers have time to move it out. - Is it possible to keep it for at least two weeks? - May I know how to archive potato? CMIIW, potato is partly in pool directory. - May I know how to archive woody which is totally in pool? regards, -- Rahmat M. Samik-Ibrahim -- vLSM.org -- http://rms46.vLSM.org -- -- 152.118? 167.205? Ha! --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How was the slink -- potato switch? How will be potato -- woody? When?
On Mon, Apr 29, 2002 at 11:20:08AM +0700, Rahmat M. Samik-Ibrahim wrote: When you install from scratch you lose the configuration file changes on the old installation. It is not a problem, since most of the configs are default anyway. Maybe for you... Set the debconf level to critical and you'll only get the most important questions. May I know how/ what/ where to set? Run dpkg-reconfigure debconf as root. Thus, I would like to know, how **LONG** after woody release, will potato be kept at the mirrors, before it will be put to the archive server. Probably a few days/weeks, depending on when the archive maintainers have time to move it out. - Is it possible to keep it for at least two weeks? Everything's possible... I don't know. - May I know how to archive potato? CMIIW, potato is partly in pool directory. - May I know how to archive woody which is totally in pool? Something will be arranged on archive.debian.org for those purposes, I guess, I don't know if we have programs ready to do that right now. Ask [EMAIL PROTECTED] -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: How was the slink -- potato switch? How will be potato -- woody? When?
| However, | - may I know what happened during the slink-potato switch period? I had a slink box that upgraded to potato just fine. | - was there a sufficient grace period before slink was deleted | from the mirrors? IIRC, potato will be moved to archive.debian.org and remain there like other old releases. | - may I know where to get information about potato to woody switch | plan? what will happen on May 1st ? There should be an announcement from the debian-announce list, it will most assuredly be in the debian weekly news, and posted prominently on the main web site. | - what is better: to use potato or stable in the production | systems' sources.list? If you use stable, you will automagically be brought up to the current release state, if you use potato, you will probably error out when potato is moved to the archive. | - is there a way to keep/ save all configuration files, and then | installing woody from scratch (which is faster)? Instead of reinstalling (ala red hat), just to an 'apt-get update' and an 'apt-get dist-upgrade' and move up your packages like before. HTH, Brooks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How was the slink -- potato switch? How will be potato -- woody? When?
Rahmat M. Samik-Ibrahim rms46@vlsm.org wrote on 26/04/2002 (07:53) : Hello: I have just tested this following: - get a packet copy using dpkg --get-selections - put it to a new installed system using dpkg --set-selections - after installing potato, I changed the sources.list dist to woody - besides very slow, it was not straight forward since many packages were deleted, but some replacements were not inVstalled (e.g. sawmill -- sawfish). Fortunately, it was just a test system, and not a production one. Are your systems off-line? Why didn't you just do: apt-get update;apt-get dist-upgrade ? However, - may I know what happened during the slink-potato switch period? - was there a sufficient grace period before slink was deleted from the mirrors? - may I know where to get information about potato to woody switch plan? what will happen on May 1st ? - what is better: to use potato or stable in the production systems' sources.list? isn't potato = stable? - is there a way to keep/ save all configuration files, and then installing woody from scratch (which is faster)? Please explain your installation process, because I don't understand how: apt-get update;apt-get dist-upgrade can be slower. Preben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How was the slink -- potato switch? How will be potato -- woody? When?
Hello Again: Apology for my poor english. Let me try again to express my concerns: I believe that most packages will be upgraded when stable is changed from potato to woody. I guess that that process will be relatively slower since it has to delete/ replace the old packages first before installing the new ones. Therefore, why not just installing from scratch? My own workstation is already a woody. It was a nightmare as well as slow when I switched from potato to woody a couple of months ago. I noticed that installing from scratch is faster (I was installing another system from scratch that time). There are a couple of potato production servers at my place. I copied the package list from one of that server by using dpkg --get-selections. Then I installed a new test system using that package list (using dpkg --set-selections). First, I installed the potato set, then I tried to upgrade it to woody. OK, I did not use apt-get for upgrading. Instead, I was using dselect. The upgrade process was slow, because many interactive questions were asked. Therefore, I believe (unlike security patch), that the upgrading process from potato to woody will not be a 10 minute one. Especially, for the ones who maintaining a server farm. Thus, I would like to know, how **LONG** after woody release, will potato be kept at the mirrors, before it will be put to the archive server. regards, -- Rahmat M. Samik-Ibrahim -- vLSM.org -- http://rms46.vLSM.org -- -- 152.118? 167.205? Ha! --- Previously I wrote: Hello: I have just tested this following: - get a packet copy using dpkg --get-selections - put it to a new installed system using dpkg --set-selections - after installing potato, I changed the sources.list dist to woody - besides very slow, it was not straight forward since many packages were deleted, but some replacements were not installed (e.g. sawmill -- sawfish). Fortunately, it was just a test system, and not a production one. However, - may I know what happened during the slink-potato switch period? - was there a sufficient grace period before slink was deleted from the mirrors? - may I know where to get information about potato to woody switch plan? what will happen on May 1st ? - what is better: to use potato or stable in the production systems' sources.list? - is there a way to keep/ save all configuration files, and then installing woody from scratch (which is faster)? -- Rahmat M. Samik-Ibrahim -- vLSM.org -- http://rms46.vLSM.org -- -- 152.118? 167.205? Ha! --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How was the slink -- potato switch? How will be potato -- woody? When?
On Fri, Apr 26, 2002 at 03:23:14PM +0200, Preben Randhol wrote: - what is better: to use potato or stable in the production systems' sources.list? isn't potato = stable? Sure it is. Today. Next month, though, if all goes as planned, stable will point to woody. potato will, of course, still point to potato. Personally, I use release status (unstable/testing/stable) in my sources.list. However, if you want to be more sure of what you're getting or if you want to continue running potato for a while after woody's release, you should consider using release names (sid/woody/ potato) instead. -- When we reduce our own liberties to stop terrorism, the terrorists have already won. - reverius Innocence is no protection when governments go bad. - Tom Swiss -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How was the slink -- potato switch? How will be potato -- woody? When?
On Fri, Apr 26, 2002 at 10:00:32PM +0700, Rahmat M. Samik-Ibrahim wrote: I believe that most packages will be upgraded when stable is changed from potato to woody. I guess that that process will be relatively slower since it has to delete/ replace the old packages first before installing the new ones. Therefore, why not just installing from scratch? If you install from scratch, you'll need to reconfigure everything. In my experience, you'll be done a lot quicker if you just do the dist-upgrade. dist-upgrading also saves you the time of installing a new base system. My own workstation is already a woody. It was a nightmare as well as slow when I switched from potato to woody a couple of months ago. I noticed that installing from scratch is faster (I was installing another system from scratch that time). Was the install from scratch CD-based and the upgrade network-based? The only part of a dist-upgrade that I consider to be slow is waiting for packages to download. An easy way around that is to do `apt-get -d dist-upgrade` just before going to bed/going home from work, letting the packages download overnight, and then `apt-get dist-upgrade`ing the next day. First, I installed the potato set, then I tried to upgrade it to woody. OK, I did not use apt-get for upgrading. Instead, I was using dselect. The upgrade process was slow, because many interactive questions were asked. The only questions which come up during an upgrade are those which would also be asked on a fresh install and those that result from config files having been customized after installation[1]. The first type can be ignored, since they'll be there either way. As for the second type, I would expect answering the question to take less time than repeating your customizations. [1] OK, not strictly true. There are also things like the postgres database format changing from potato to woody, but they're pretty rare. -- When we reduce our own liberties to stop terrorism, the terrorists have already won. - reverius Innocence is no protection when governments go bad. - Tom Swiss -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How was the slink -- potato switch? How will be potato -- woody? When?
On Fri, Apr 26, 2002 at 10:00:32PM +0700, Rahmat M. Samik-Ibrahim wrote: I believe that most packages will be upgraded when stable is changed from potato to woody. I guess that that process will be relatively slower since it has to delete/ replace the old packages first before installing the new ones. Delete/replace? On each upgrade, dpkg unpacks the new files into a temporary directory, checks for conflicts, moves the new files into the filesystem, and removes the removed files from the filesystem. Therefore, why not just installing from scratch? My own workstation is already a woody. It was a nightmare as well as slow when I switched from potato to woody a couple of months ago. I noticed that installing from scratch is faster (I was installing another system from scratch that time). When you install from scratch you lose the configuration file changes on the old installation. The upgrade process was slow, because many interactive questions were asked. Set the debconf level to critical and you'll only get the most important questions. Therefore, I believe (unlike security patch), that the upgrading process from potato to woody will not be a 10 minute one. Especially, for the ones who maintaining a server farm. Nobody said it would be. Thus, I would like to know, how **LONG** after woody release, will potato be kept at the mirrors, before it will be put to the archive server. Probably a few days/weeks, depending on when the archive maintainers have time to move it out. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
How was the slink -- potato switch? How will be potato -- woody? When?
Hello: I have just tested this following: - get a packet copy using dpkg --get-selections - put it to a new installed system using dpkg --set-selections - after installing potato, I changed the sources.list dist to woody - besides very slow, it was not straight forward since many packages were deleted, but some replacements were not installed (e.g. sawmill -- sawfish). Fortunately, it was just a test system, and not a production one. However, - may I know what happened during the slink-potato switch period? - was there a sufficient grace period before slink was deleted from the mirrors? - may I know where to get information about potato to woody switch plan? what will happen on May 1st ? - what is better: to use potato or stable in the production systems' sources.list? - is there a way to keep/ save all configuration files, and then installing woody from scratch (which is faster)? regards, -- Rahmat M. Samik-Ibrahim -- vLSM.org -- http://rms46.vLSM.org -- -- 152.118? 167.205? Ha! --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
