Date: Mon, 20 Jan 2020 03:57:20 +0000 From: "Montgomery-Smith, Stephen" <stephen@missouri.edu> To: "Julian H. Stacey" <jhs@berklix.com>, "ctm-users@freebsd.org" <ctm-users@freebsd.org> Subject: Re: src-cur is stuck Message-ID: <e2cf3790-e2ed-ff0b-ebad-e1beebc1b7ef@missouri.edu> In-Reply-To: <202001191305.00JD4vPa056845@fire.js.berklix.net> References: <202001191305.00JD4vPa056845@fire.js.berklix.net>
index | next in thread | previous in thread | raw e-mail
On 1/19/20 7:04 AM, Julian H. Stacey wrote: >> "Montgomery-Smith, Stephen" wrote: >>> I have restarted src-cur. The problem is that a huge number of files were >>> deleted. I think switching llvm. mkctm was programmed to reject CTM changes >>> that huge. I reprogrammed it to have a much larger threshold. >> >> That was quick ! Thanks ! >> >> Those on either of: >> http://mailman.berklix.org/mailman/listinfo/ctm-src-cur >> ctm-src-cur@mailman.berklix.org >> http://mailman.berklix.org/mailman/listinfo/ctm-src-cur-fast >> ctm-src-cur-fast@mailman.berklix.org >> will need to >> fetch ftp://ctm.berklix.org/pub/FreeBSD/development/CTM/src-cur/src-cur.14331.gzas it is 35932628 bytes >> & the above mail lists are set to (in KB): >> max_message_size = 300 >> I dont know what the max. is on the old freebsd.org CTM lists, >> but most likely users of those will also need to ftp. > > PS I just remembered: max_message_size is not relevant to this, > max_message_size does not limit ctm delta size, but ctm piece size, > ctm_smail splits deltas to pieces before mailing > > I found another large delta 35405819 src-12.0551.gz > fetch ftp://ctm.berklix.org/pub/FreeBSD/development/CTM/src-12/src-12.0551.gz > > Stephen, possibly you might need to adjust parameters for that list too, > if your parameters are per list ? It is a universal parameter. This parameter is called "damage", and is the number of files deleted. Not related to size.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e2cf3790-e2ed-ff0b-ebad-e1beebc1b7ef>