Re: effect of having stable and unstable listed in sources.list

1999-12-08 Thread Marc Haber
On Sat, 4 Dec 1999 16:16:24 -0500 (EST), you wrote: I would not recomend mixing slink and potato sources. Early in the potato development this was possible as slink and potato were not too different and only a few files were updated. But now most files depend in some way on libc6 v2.1 or

RE: effect of having stable and unstable listed in sources.list

1999-12-04 Thread Pollywog
On 04-Dec-1999 Bryan Scaringe wrote: I have seen many examples on this list of people putting entries in sources.list for both stable and unstable trees at the same time. How does apt/dselect handle this? Would an apt-get upgrade always pull from stable or unstable? Thanks in advance.

RE: effect of having stable and unstable listed in sources.list

1999-12-04 Thread Bryan Scaringe
Opps, When in doubt, I should read the man pages. Looks like apt will go through sources.list, and will install the package from the first source it finds. if I am reading man sources.list correctly :) Bryan On 04-Dec-1999 Pollywog wrote: On 04-Dec-1999 Bryan Scaringe wrote: I have

Re: effect of having stable and unstable listed in sources.list

1999-12-04 Thread Brad
On Sat, Dec 04, 1999 at 03:32:45PM -0500, Bryan Scaringe wrote: I have seen many examples on this list of people putting entries in sources.list for both stable and unstable trees at the same time. How does apt/dselect handle this? Would an apt-get upgrade always pull from stable or

Re: effect of having stable and unstable listed in sources.list

1999-12-04 Thread Brian Servis
No, it will install the newest version of whatever it finds. The order of the listings in sources.list only is important if it finds two sources for the *exact* same file. The file then will get installed from the first URI. This is useful if you have a local mirror that may not be up to date