Date: Sun, 14 Nov 2004 02:45:34 +1100 (EST) From: Mark Russell <freebsd@mark.net.au> To: Richard Coleman <rcoleman@criticalmagic.com> Cc: Kirill Ponomarew <krion@voodoo.oberon.net> Subject: Re: HEADSUP: INDEX[-5] files were removed from CVS. Message-ID: <20041114024111.L60099@juana.isp.net.au> In-Reply-To: <41962A9C.4020609@criticalmagic.com> References: <20041113101925.GB70256@voodoo.oberon.net> <20041114003532.L60099@juana.isp.net.au> <20041114022940.F60099@juana.isp.net.au> <41962A9C.4020609@criticalmagic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 13 Nov 2004, Richard Coleman wrote: > Mark Russell wrote: >> On Sat, 13 Nov 2004, Richard Coleman wrote: >>>> please back this out, it breaks things, I've never found an out of >>>> date index to be a problem, now not havign an index is causing >>>> problems, also the extra bandwidth for fetch index is a hassle. >>>> >>>> at least let the issue be discused on the list. >>> >>> >>> Just change your cvsup script to rebuild INDEX[-5] afterwards. That's >>> what I do. The change is fine with me. >> >> on trees that are mounted -ro this barfs, on my p120 which does my personal >> mail and updates virus defs every 2 hours its dead in the water. > > I haven't tried it, but you can probably just edit out the lines concerning > INDEX[-5] in /usr/sup/ports-all/checkout file. Once cvsup believes it didn't this was changed to /var/sup by default ages ago > create the file, it won't delete it. The same will also be true if you > rebuild INDEX[-5] after cvsup has deleted it the first time. It shouldn't > delete it a second time (since it didn't install the file). Then you can > rebuild a new INDEX[-5] when you desire. I just tried it on the box with -rw access, the INDEX-5 file got trashed again, INDEX hasn't been allowed to be written due to -ro access Why was this done in the first place anyway? > -- History repeats itself. That's one of the things wrong with history.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041114024111.L60099>