Re: Incoming

2000-04-03 Thread Craig Sanders
On Sat, Apr 01, 2000 at 02:51:28PM -0700, Jason Gunthorpe wrote: On Sat, 1 Apr 2000, Craig Sanders wrote: I hope to dismantle the sites mirroring incoming in favor of direct access, it ultimately will use less bandwidth/cpu. this is bad. sometimes installing stuff from incoming is

Re: Incoming

2000-04-03 Thread Ben Collins
On Mon, Apr 03, 2000 at 11:20:32AM +1000, Craig Sanders wrote: On Sat, Apr 01, 2000 at 02:51:28PM -0700, Jason Gunthorpe wrote: On Sat, 1 Apr 2000, Craig Sanders wrote: I hope to dismantle the sites mirroring incoming in favor of direct access, it ultimately will use less bandwidth/cpu.

Re: Incoming

2000-04-03 Thread fischer
On Sun, 2 Apr 2000, Ben Collins wrote: On Mon, Apr 03, 2000 at 01:22:12PM +1000, Craig Sanders wrote: On Sun, Apr 02, 2000 at 10:39:30PM -0400, Ben Collins wrote: If you weren't following unstable on critical machines, maybe that wouldn't happen. Then again, I guess as a developer, we

Re: Incoming

2000-04-03 Thread Mark Brown
On Sun, Apr 02, 2000 at 11:37:39PM -0400, Ben Collins wrote: Yeah...that's it, I'm for getting rid of incoming mirrors to save cpu and bandwidth on one of our resources...that's so selfish of me. God forbid I Would it be possible for Incoming to be made avalible via FTP as well as HTTP? Both

Re: Incoming

2000-04-03 Thread Jason Gunthorpe
On Mon, 3 Apr 2000, Mark Brown wrote: Would it be possible for Incoming to be made avalible via FTP as well as HTTP? Both can have problems with firewalls and forced proxying, but I don't think so, ftp is going to remain turned off on that machine. If you can't fetch things from the web,

Re: Incoming

2000-04-03 Thread Julian Gilbey
On Mon, Apr 03, 2000 at 01:22:12PM +1000, Craig Sanders wrote: debian 'unstable' is perfectly usable for production servers, using it for such does not require any more caution about upgrades than using debian 'stable' or debian 'frozen'. Like during the Perl transition period, or when a

Re: Incoming

2000-04-03 Thread Jason Gunthorpe
On Mon, 3 Apr 2000, Julian Gilbey wrote: Like during the Perl transition period, or when a recent libstdc++ broke apt, or when su stopped being able to su, or when What you are describing is a problem with the package life cycle, not the replication of incoming. Let me reiterate: DO NOT

Re: Incoming

2000-04-03 Thread Martin Schulze
Jason Gunthorpe wrote: The files may be trojans, corrupt, partial, massively screwed, fail lintian, whatever. Massive, massive caution is advised! I thougth that we're in this business for several years now. Another time warp? Regards, Joey -- Experience is something you don't get

Re: Incoming

2000-04-03 Thread Andrew McMillan
Jason Gunthorpe wrote: On Mon, 3 Apr 2000, Mark Brown wrote: Would it be possible for Incoming to be made avalible via FTP as well as HTTP? Both can have problems with firewalls and forced proxying, but I don't think so, ftp is going to remain turned off on that machine. If you

Re: Incoming

2000-04-03 Thread Craig Sanders
On Mon, Apr 03, 2000 at 09:46:13AM +0100, Julian Gilbey wrote: On Mon, Apr 03, 2000 at 01:22:12PM +1000, Craig Sanders wrote: debian 'unstable' is perfectly usable for production servers, using it for such does not require any more caution about upgrades than using debian 'stable' or debian

Re: Incoming

2000-04-03 Thread Tim Haynes
On Mon, Apr 03, 2000 at 08:49:17PM +1000, Craig Sanders wrote: On Mon, Apr 03, 2000 at 09:46:13AM +0100, Julian Gilbey wrote: On Mon, Apr 03, 2000 at 01:22:12PM +1000, Craig Sanders wrote: debian 'unstable' is perfectly usable for production servers, using it for such does not require any

Re: Incoming

2000-04-03 Thread Nils Lohner
In message [EMAIL PROTECTED], Craig Sanders writes: On Mon, Apr 03, 2000 at 09:46:13AM +0100, Julian Gilbey wrote: On Mon, Apr 03, 2000 at 01:22:12PM +1000, Craig Sanders wrote: debian 'unstable' is perfectly usable for production servers, using it for such does not require any more caution

Re: Incoming

2000-04-03 Thread Ben Collins
On Mon, Apr 03, 2000 at 06:04:25AM +0200, fischer wrote: On Sun, 2 Apr 2000, Ben Collins wrote: On Mon, Apr 03, 2000 at 01:22:12PM +1000, Craig Sanders wrote: On Sun, Apr 02, 2000 at 10:39:30PM -0400, Ben Collins wrote: If you weren't following unstable on critical machines, maybe that

Re: Incoming

2000-04-03 Thread Julian Gilbey
On Mon, Apr 03, 2000 at 03:48:00AM -0600, Jason Gunthorpe wrote: On Mon, 3 Apr 2000, Julian Gilbey wrote: Like during the Perl transition period, or when a recent libstdc++ broke apt, or when su stopped being able to su, or when What you are describing is a problem with the

Re: Incoming

2000-04-03 Thread Mark Brown
On Mon, Apr 03, 2000 at 03:30:01AM -0600, Jason Gunthorpe wrote: I don't think so, ftp is going to remain turned off on that machine. If you can't fetch things from the web, but can via ftp I think you have some serious 'issues' ; HTTP tends to be one of the first things that gets forced

Re: Incoming

2000-04-03 Thread Craig Sanders
On Mon, Apr 03, 2000 at 10:07:02AM -0400, Ben Collins wrote: If you are so careful and clueful, why do you need instant access to an incoming mirror? to fix the machine(s) i use to test any upgrades. the fact that they are unimportant enough to test an upgrade on doesn't mean that their entire

Re: Incoming

2000-04-03 Thread Craig Sanders
On Mon, Apr 03, 2000 at 02:45:12PM +0200, Nils Lohner wrote: ... so why not just package up unstable and release it without fixing bugs if using them is the same? I think I'm missing something here. Even if you're cautious, isn't unstable more likely to have bugs (the RC list comes to mind)