Re: Time for squid 3.0 STABLE2 ?
On Mon, 2008-03-10 at 14:12 +1300, Amos Jeffries wrote: As it stands we can call one or the other an up/down and leave things as-is. I'm minded to call 2.6 a 'down' of 3.0 and 3.0/2.7/2.6 downs of 3.1. I have not looked closely at the update script to see if thats right though. As I said I don't think using the changesets as tracking method for determining what needs porting from Squid-2 to 3 is appropriate. Better to start with cf.data.pre differences between the two which should now be found in the release notes, and work from there (which secondare may include collecting relevant changesets) The changesets works for new small things (i.e. bugfixes to common code) but those have been quite faithfully ported and still are, and best tracked via bugzilla. Many of the missing features is not even found in the changesets, and often require substantial effort to port or reimplement, here the changesets is just one input. These is best tracked via the releasenotes I think, or their own branches when each effort gets started. Regards Henrik
Re: Time for squid 3.0 STABLE2 ?
On Mon, 2008-03-10 at 23:19 +1300, Amos Jeffries wrote: Q: who shall do the announce and to where? I know of squid-dev, squid-users, noc, anywhere else? squid-users@ and squid-announce@ Regards Henrik
Re: Time for squid 3.0 STABLE2 ?
Amos Jeffries wrote: Henrik Nordstrom wrote: On Thu, 2008-02-28 at 01:04 +1300, Amos Jeffries wrote: Just a few issues remaining before 3.0.STABLE-2. * patch 11467 back-porting. cd English ls ERR_* ../list * Close more bugs? http://www.squid-cache.org/bugs/show_bug.cgi?id=2127 Is closed and verified by the reporter. http://www.squid-cache.org/bugs/show_bug.cgi?id=2124 Done. why is this not 2.6?? http://www.squid-cache.org/bugs/show_bug.cgi?id=2138 Don't know. * CVS branching? checkpoint?. Will need another How-To here I think Henrik.t update releasenotes and changelog. login on squid/cache.org and - get an up to date checkout of the tree cvs up -d -P - make sure the version in configure.in is correct - ./bootstrap.sh - cvs commit - cvs tag SQUID_3_0_STABLE2 - ./mkrelease.sh squid-3.0.STABLE2 /server/httpd/htdocs/squid-cache.org/Versions/v3/3.0/ (i think, verify the path) this should give you a suitable tarball in the website. download that, and the previous release and signature as well. verify the signature of the previous release make a diff between the two, and audit that diff to verify that the changes looks right. sign the new release and diff. upload the diff and signatures to the 3.0 folder on the web server. go to the 3.0 web folder co -l index.tmpl edit index.tmpl, moving the previous release down to older stable releases and the new as current stable release. ./make.sh verify that it got published right. Thanks to Henrik I'm now up to here. Just two problems preventing completion. 1) I don't have write access to the FTP area to copy the files in. I think its /server/ftp/pub/squid-3/STABLE/ anyway. (The STABLE1 signature files and diff appear to be missing too) 2) my PGP key probably needs to be added to the keyring at http://www.squid-cache.org/pgp.asc before the announce. copy the tarballs, diff, release notes and signatures to the ftp area. send announce Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: Time for squid 3.0 STABLE2 ?
On Sun, 2008-03-09 at 21:28 +1300, Amos Jeffries wrote: 1) I don't have write access to the FTP area to copy the files in. I think its /server/ftp/pub/squid-3/STABLE/ anyway. Fixed. (The STABLE1 signature files and diff appear to be missing too) I have now copied the STABLE1 signatures and release notes there. There is no diff for STABLE1 as there is no meaningful reference to make the diff from.. 2) my PGP key probably needs to be added to the keyring at http://www.squid-cache.org/pgp.asc before the announce. Agreed. And on the key servers as well... Upload it to your home and I'll add it to the squid-cache.org keyring. gpg --export -a 0xFF5CF463 gpg_key.asc Regards Henrik signature.asc Description: This is a digitally signed message part
Re: Time for squid 3.0 STABLE2 ?
On Fri, 2008-02-29 at 01:13 +1300, Amos Jeffries wrote: Hm, yes. Henrik, is there a report somewhere that lgroups the merged changesets the same way the maintainer merge.html lists the un-merged and non-merged ones? There is a merge.html in 2.7 showing what's unique for 2.7 and not merged to 2.6. http://www.squid-cache.org/Versions/v2/2.7/changesets/merge.html But remember that quite a lot of the 2/3 differences is from before we split cvs into changesets.. Better to work from cf.data.pre differences I think as most features show up in cf.data.pre.. Most bugfixes have been ported I think, at least outside COSS.. Regards Henrik
Re: Time for squid 3.0 STABLE2 ?
On Sun, 2008-03-09 at 21:28 +1300, Amos Jeffries wrote: 1) I don't have write access to the FTP area to copy the files in. I think its /server/ftp/pub/squid-3/STABLE/ anyway. Fixed. (The STABLE1 signature files and diff appear to be missing too) I have now copied the STABLE1 signatures and release notes there. There is no diff for STABLE1 as there is no meaningful reference to make the diff from.. 2) my PGP key probably needs to be added to the keyring at http://www.squid-cache.org/pgp.asc before the announce. Agreed. And on the key servers as well... Upload it to your home and I'll add it to the squid-cache.org keyring. gpg --export -a 0xFF5CF463 gpg_key.asc FYI: Just went to finish off and I'm getting ssh: connect to host squid-cache.org port __: Connection refused I'll try it again later. Thank you Amos
Re: Time for squid 3.0 STABLE2 ?
On Fri, 2008-02-29 at 01:13 +1300, Amos Jeffries wrote: Hm, yes. Henrik, is there a report somewhere that lgroups the merged changesets the same way the maintainer merge.html lists the un-merged and non-merged ones? There is a merge.html in 2.7 showing what's unique for 2.7 and not merged to 2.6. http://www.squid-cache.org/Versions/v2/2.7/changesets/merge.html But remember that quite a lot of the 2/3 differences is from before we split cvs into changesets.. Better to work from cf.data.pre differences I think as most features show up in cf.data.pre.. Most bugfixes have been ported I think, at least outside COSS.. Hmm, this leaves the two of us maintainers with a choice I think Henrik. As it stands we can call one or the other an up/down and leave things as-is. I'm minded to call 2.6 a 'down' of 3.0 and 3.0/2.7/2.6 downs of 3.1. I have not looked closely at the update script to see if thats right though. But there is an alternative of making a .cross type if we can figure an easy way to do it. Amos
Re: Time for squid 3.0 STABLE2 ?
lör 2008-03-08 klockan 16:39 +1300 skrev Amos Jeffries: Got this far. But one thing is still making me think... The official sigs Duane has up for STABLE1 look like this: File: squid-3.0.STABLE1.tar.gz Date: Fri Dec 14 00:26:31 GMT 2007 Size: 2406601 MD5 : 688d02adad9b592c5947d54237fbc076 [...] I cant figure out how to get my gpg app (1.4.6) to produce any of the File stats etc. It only seems to be doing the SIG part. Thats done by a small script I made some years ago when starting gpg signing releases. You can find a copy attached to this message. GPG only uses the gpg signature part, the other details is for manual verification using other tools. Regards Henrik signfile.sh Description: application/shellscript
Re: Time for squid 3.0 STABLE2 ?
ons 2008-03-05 klockan 01:48 +1300 skrev Amos Jeffries: Partway through. Now the its I have never done before hit me ... anything in particular to look for in the diff? Only that it seems to match the changes which is expected to be there, and that nothing else sticks out which isn't expected to be there. how (and where? my machine or squid-cache.org server?) do I do the verification and signing? Your machine. Signing using your GPG key.. You should not store your GPG key on suqid-cache.org... basic GPG security principle.. co -l index.tmpl you mean a cvs checkout of www2 branch in website repository? or is there a 'co' program? Versions/ hasn't been moved over to CVS yet, still using plain old RCS directly on squid-cache.org.. Regards Henrik
Re: Time for squid 3.0 STABLE2 ?
Hi Amos, At 12:58 04/03/2008, Amos Jeffries wrote: 2008/03/01 12:36:59| WARNING: Closing open FD 50 2008/03/01 12:36:59| diskHandleWrite: FD 11: disk write error: (9) Bad file descriptor 2008/03/01 12:36:59| storeDirWriteCleanLogs: Starting... 2008/03/01 12:36:59| WARNING: Closing open FD9 2008/03/01 12:36:59| xrename: Cannot rename c:/squid/var/cache/swap.state.clean to c:/squid/var/cache/swap.state: (17) File exists 2008/03/01 12:36:59| Finished. Wrote 229 entries. 2008/03/01 12:36:59| Took 0.01 seconds (15266.67 entries/sec). FATAL: Write failure -- check your disk space and cache.log Squid Cache (Version 3.0.STABLE1-CVS): Terminated abnormally. Regards Guido Two bugs in there. The FD issue seems to be Windows-Specific. I agree, and it seems to be a really bad thing: after some debugging, it seems that the Visual Studio 2005 CRT is assigning to sockets already used FD . Regards Guido - Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
Re: Time for squid 3.0 STABLE2 ?
Guido Serassio wrote: Hi Amos, At 11:35 01/03/2008, Amos Jeffries wrote: The above is only solved by manually removing the swap.state file. There is something funky going on with the permissions before these high-level swap.state operations. I've seen it here in HEAD and thought it in the code not ported back. This is a blocker if it's in 3.0. I think that here there is some Windows specific big problem. On Windows, when running as a service, there are no file permissions problems. I have just deleted the swap.state file, and after few requests 2008/03/01 12:36:02| setMaxFD: Cannot increase: setrlimit() not supported on this system 2008/03/01 12:36:02| Starting Squid Cache version 3.0.STABLE1-CVS for i686-pc-winnt... 2008/03/01 12:36:02| Running as Squid Windows System Service on Windows Server 2003 2008/03/01 12:36:02| Service command line is: 2008/03/01 12:36:02| Process ID 3232 2008/03/01 12:36:02| With 2048 file descriptors available 2008/03/01 12:36:02| With 2048 CRT stdio descriptors available 2008/03/01 12:36:02| Windows sockets initialized 2008/03/01 12:36:02| Performing DNS Tests... 2008/03/01 12:36:02| Successful DNS name lookup tests... 2008/03/01 12:36:02| DNS Socket created at 0.0.0.0, port 1194, FD 5 2008/03/01 12:36:02| Adding nameserver 172.30.128.1 from Registry 2008/03/01 12:36:02| Adding nameserver 172.30.1.1 from Registry 2008/03/01 12:36:02| Adding nameserver 172.30.1.2 from Registry 2008/03/01 12:36:02| User-Agent logging is disabled. 2008/03/01 12:36:02| Referer logging is disabled. 2008/03/01 12:36:02| Unlinkd pipe opened on FD 8 2008/03/01 12:36:02| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec 2008/03/01 12:36:02| Store logging disabled 2008/03/01 12:36:02| Swap maxSize 102400 KB, estimated 7876 objects 2008/03/01 12:36:02| Target number of buckets: 393 2008/03/01 12:36:02| Using 8192 Store buckets 2008/03/01 12:36:02| Max Mem size: 8192 KB 2008/03/01 12:36:02| Max Swap size: 102400 KB 2008/03/01 12:36:02| Version 1 of swap file with LFS support detected... 2008/03/01 12:36:02| Rebuilding storage in c:/squid/var/cache (CLEAN) 2008/03/01 12:36:02| Using Least Load store dir selection 2008/03/01 12:36:02| Set Current Directory to c:/squid/var/cache 2008/03/01 12:36:02| Loaded Icons. 2008/03/01 12:36:02| Accepting HTTP connections at 0.0.0.0, port 3128, FD 14. 2008/03/01 12:36:02| Accepting ICP messages at 0.0.0.0, port 3130, FD 15. 2008/03/01 12:36:02| HTCP Disabled. 2008/03/01 12:36:02| Ready to serve requests. 2008/03/01 12:36:02| Done reading c:/squid/var/cache swaplog (138 entries) 2008/03/01 12:36:02| Finished rebuilding storage from disk. 2008/03/01 12:36:02| 138 Entries scanned 2008/03/01 12:36:02| 0 Invalid entries. 2008/03/01 12:36:02| 0 With invalid flags. 2008/03/01 12:36:02| 138 Objects loaded. 2008/03/01 12:36:02| 0 Objects expired. 2008/03/01 12:36:02| 0 Objects cancelled. 2008/03/01 12:36:02| 0 Duplicate URLs purged. 2008/03/01 12:36:02| 0 Swapfile clashes avoided. 2008/03/01 12:36:02| Took 0.08 seconds (1746.84 objects/sec). 2008/03/01 12:36:02| Beginning Validation Procedure 2008/03/01 12:36:02| Completed Validation Procedure 2008/03/01 12:36:02| Validated 301 Entries 2008/03/01 12:36:02| store_swap_size = 1508 2008/03/01 12:36:03| storeLateRelease: released 0 objects 2008/03/01 12:36:59| WARNING: Closing open FD 50 2008/03/01 12:36:59| diskHandleWrite: FD 11: disk write error: (9) Bad file descriptor 2008/03/01 12:36:59| storeDirWriteCleanLogs: Starting... 2008/03/01 12:36:59| WARNING: Closing open FD9 2008/03/01 12:36:59| xrename: Cannot rename c:/squid/var/cache/swap.state.clean to c:/squid/var/cache/swap.state: (17) File exists 2008/03/01 12:36:59| Finished. Wrote 229 entries. 2008/03/01 12:36:59| Took 0.01 seconds (15266.67 entries/sec). FATAL: Write failure -- check your disk space and cache.log Squid Cache (Version 3.0.STABLE1-CVS): Terminated abnormally. Regards Guido Two bugs in there. The FD issue seems to be Windows-Specific. The swap.state one is wider. I've written it up as bug 2249 http://www.squid-cache.org/bugs/show_bug.cgi?id=2249 I've kicked off a clean build and test now on the 3.0 code to see if I can reproduce it easily outside HEAD and since its more critical branch at present. It does not seem to be obliging. But don't have time to test properly myself this week. Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: Time for squid 3.0 STABLE2 ?
Henrik Nordstrom wrote: On Thu, 2008-02-28 at 01:04 +1300, Amos Jeffries wrote: Just a few issues remaining before 3.0.STABLE-2. * patch 11467 back-porting. cd English ls ERR_* ../list * Close more bugs? http://www.squid-cache.org/bugs/show_bug.cgi?id=2127 Is closed and verified by the reporter. http://www.squid-cache.org/bugs/show_bug.cgi?id=2124 Done. why is this not 2.6?? http://www.squid-cache.org/bugs/show_bug.cgi?id=2138 Don't know. * CVS branching? checkpoint?. Will need another How-To here I think Henrik.t update releasenotes and changelog. login on squid/cache.org and - get an up to date checkout of the tree cvs up -d -P - make sure the version in configure.in is correct - ./bootstrap.sh - cvs commit - cvs tag SQUID_3_0_STABLE2 - ./mkrelease.sh squid-3.0.STABLE2 /server/httpd/htdocs/squid-cache.org/Versions/v3/3.0/ (i think, verify the path) this should give you a suitable tarball in the website. Partway through. Now the its I have never done before hit me ... anything in particular to look for in the diff? how (and where? my machine or squid-cache.org server?) do I do the verification and signing? download that, and the previous release and signature as well. verify the signature of the previous release make a diff between the two, and audit that diff to verify that the changes looks right. sign the new release and diff. upload the diff and signatures to the 3.0 folder on the web server. go to the 3.0 web folder co -l index.tmpl you mean a cvs checkout of www2 branch in website repository? or is there a 'co' program? edit index.tmpl, moving the previous release down to older stable releases and the new as current stable release. ./make.sh verify that it got published right. copy the tarballs, diff, release notes and signatures to the ftp area. send announce Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: Time for squid 3.0 STABLE2 ?
Hi Amos, At 13:04 27/02/2008, Amos Jeffries wrote: Just a few issues remaining before 3.0.STABLE-2. * Build and tests on as many OS as possible. (branch: SQUID_3_0) I am running the tests I use on Debian/Ubuntu already. Could the rest of you please jump in for any OS you have tests for or even just compiling on. As usual for 2.6, I will run a build test at least on Irix, Solaris and Windows. I hope to run some other build test on my *BSD virtual machines. The bad news is that 3.0 STABLE is still not operational on Windows: it crashes after few request. It seems that there is some strange problem in the IPC/FD interaction, but I cannot understand what is happening: 2008/02/17 19:05:01| setMaxFD: Cannot increase: setrlimit() not supported on this system 2008/02/17 19:05:01| Starting Squid Cache version 3.0.STABLE1-CVS for i686-pc-winnt... 2008/02/17 19:05:01| Running as Squid Windows System Service on Windows Server 2003 2008/02/17 19:05:01| Service command line is: 2008/02/17 19:05:01| Process ID 216 2008/02/17 19:05:01| With 2048 file descriptors available 2008/02/17 19:05:01| With 2048 CRT stdio descriptors available 2008/02/17 19:05:01| Windows sockets initialized 2008/02/17 19:05:01| Performing DNS Tests... 2008/02/17 19:05:02| Successful DNS name lookup tests... 2008/02/17 19:05:02| DNS Socket created at 0.0.0.0, port 1189, FD 5 2008/02/17 19:05:02| Adding nameserver 172.30.128.1 from Registry 2008/02/17 19:05:02| Adding nameserver 172.30.1.1 from Registry 2008/02/17 19:05:02| Adding nameserver 172.30.1.2 from Registry 2008/02/17 19:05:02| User-Agent logging is disabled. 2008/02/17 19:05:02| Referer logging is disabled. 2008/02/17 19:05:02| Unlinkd pipe opened on FD 8 2008/02/17 19:05:02| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec 2008/02/17 19:05:02| Store logging disabled 2008/02/17 19:05:02| Swap maxSize 102400 KB, estimated 7876 objects 2008/02/17 19:05:02| Target number of buckets: 393 2008/02/17 19:05:02| Using 8192 Store buckets 2008/02/17 19:05:02| Max Mem size: 8192 KB 2008/02/17 19:05:02| Max Swap size: 102400 KB 2008/02/17 19:05:02| Version 1 of swap file with LFS support detected... 2008/02/17 19:05:02| Rebuilding storage in c:/squid/var/cache (CLEAN) 2008/02/17 19:05:02| Using Least Load store dir selection 2008/02/17 19:05:02| Set Current Directory to c:/squid/var/cache 2008/02/17 19:05:02| Loaded Icons. 2008/02/17 19:05:02| Accepting HTTP connections at 0.0.0.0, port 3128, FD 14. 2008/02/17 19:05:02| Accepting ICP messages at 0.0.0.0, port 3130, FD 15. 2008/02/17 19:05:02| HTCP Disabled. 2008/02/17 19:05:02| Ready to serve requests. 2008/02/17 19:05:02| Done reading c:/squid/var/cache swaplog (135 entries) 2008/02/17 19:05:02| Finished rebuilding storage from disk. 2008/02/17 19:05:02| 135 Entries scanned 2008/02/17 19:05:02| 0 Invalid entries. 2008/02/17 19:05:02| 0 With invalid flags. 2008/02/17 19:05:02| 135 Objects loaded. 2008/02/17 19:05:02| 0 Objects expired. 2008/02/17 19:05:02| 0 Objects cancelled. 2008/02/17 19:05:02| 0 Duplicate URLs purged. 2008/02/17 19:05:02| 0 Swapfile clashes avoided. 2008/02/17 19:05:02| Took 0.08 seconds (1730.77 objects/sec). 2008/02/17 19:05:02| Beginning Validation Procedure 2008/02/17 19:05:02| Completed Validation Procedure 2008/02/17 19:05:02| Validated 295 Entries 2008/02/17 19:05:02| store_swap_size = 1496 2008/02/17 19:05:03| storeLateRelease: released 0 objects 2008/02/17 19:09:07| CACHEMGR: [EMAIL PROTECTED] requesting 'filedescriptors' 2008/02/17 19:09:57| diskHandleWrite: FD 11: disk write error: (9) Bad file descriptor 2008/02/17 19:09:57| storeDirWriteCleanLogs: Starting... 2008/02/17 19:09:57| WARNING: Closing open FD9 2008/02/17 19:09:57| xrename: Cannot rename c:/squid/var/cache/swap.state.clean to c:/squid/var/cache/swap.state: (17) File exists 2008/02/17 19:09:57| Finished. Wrote 138 entries. 2008/02/17 19:09:57| Took 0.02 seconds (8625.00 entries/sec). FATAL: Write failure -- check your disk space and cache.log There is also another (or the same ???) problem during reconfigure: 2008/02/17 20:59:02| Reconfiguring Squid Cache (version 3.0.STABLE1-CVS)... 2008/02/17 20:59:02| FD 14 Closing HTTP connection 2008/02/17 20:59:02| FD 15 Closing ICP connection 2008/02/17 20:59:02| Store logging disabled 2008/02/17 20:59:02| User-Agent logging is disabled. 2008/02/17 20:59:02| Referer logging is disabled. 2008/02/17 20:59:02| WARNING: Closing open FD9 2008/02/17 20:59:02| assertion failed: ..\..\..\src\comm.cc:901: fdc_table[new_socket].active == 0 Regards Guido - Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
Re: Time for squid 3.0 STABLE2 ?
Hi Amos, At 11:35 01/03/2008, Amos Jeffries wrote: The above is only solved by manually removing the swap.state file. There is something funky going on with the permissions before these high-level swap.state operations. I've seen it here in HEAD and thought it in the code not ported back. This is a blocker if it's in 3.0. I think that here there is some Windows specific big problem. On Windows, when running as a service, there are no file permissions problems. I have just deleted the swap.state file, and after few requests 2008/03/01 12:36:02| setMaxFD: Cannot increase: setrlimit() not supported on this system 2008/03/01 12:36:02| Starting Squid Cache version 3.0.STABLE1-CVS for i686-pc-winnt... 2008/03/01 12:36:02| Running as Squid Windows System Service on Windows Server 2003 2008/03/01 12:36:02| Service command line is: 2008/03/01 12:36:02| Process ID 3232 2008/03/01 12:36:02| With 2048 file descriptors available 2008/03/01 12:36:02| With 2048 CRT stdio descriptors available 2008/03/01 12:36:02| Windows sockets initialized 2008/03/01 12:36:02| Performing DNS Tests... 2008/03/01 12:36:02| Successful DNS name lookup tests... 2008/03/01 12:36:02| DNS Socket created at 0.0.0.0, port 1194, FD 5 2008/03/01 12:36:02| Adding nameserver 172.30.128.1 from Registry 2008/03/01 12:36:02| Adding nameserver 172.30.1.1 from Registry 2008/03/01 12:36:02| Adding nameserver 172.30.1.2 from Registry 2008/03/01 12:36:02| User-Agent logging is disabled. 2008/03/01 12:36:02| Referer logging is disabled. 2008/03/01 12:36:02| Unlinkd pipe opened on FD 8 2008/03/01 12:36:02| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec 2008/03/01 12:36:02| Store logging disabled 2008/03/01 12:36:02| Swap maxSize 102400 KB, estimated 7876 objects 2008/03/01 12:36:02| Target number of buckets: 393 2008/03/01 12:36:02| Using 8192 Store buckets 2008/03/01 12:36:02| Max Mem size: 8192 KB 2008/03/01 12:36:02| Max Swap size: 102400 KB 2008/03/01 12:36:02| Version 1 of swap file with LFS support detected... 2008/03/01 12:36:02| Rebuilding storage in c:/squid/var/cache (CLEAN) 2008/03/01 12:36:02| Using Least Load store dir selection 2008/03/01 12:36:02| Set Current Directory to c:/squid/var/cache 2008/03/01 12:36:02| Loaded Icons. 2008/03/01 12:36:02| Accepting HTTP connections at 0.0.0.0, port 3128, FD 14. 2008/03/01 12:36:02| Accepting ICP messages at 0.0.0.0, port 3130, FD 15. 2008/03/01 12:36:02| HTCP Disabled. 2008/03/01 12:36:02| Ready to serve requests. 2008/03/01 12:36:02| Done reading c:/squid/var/cache swaplog (138 entries) 2008/03/01 12:36:02| Finished rebuilding storage from disk. 2008/03/01 12:36:02| 138 Entries scanned 2008/03/01 12:36:02| 0 Invalid entries. 2008/03/01 12:36:02| 0 With invalid flags. 2008/03/01 12:36:02| 138 Objects loaded. 2008/03/01 12:36:02| 0 Objects expired. 2008/03/01 12:36:02| 0 Objects cancelled. 2008/03/01 12:36:02| 0 Duplicate URLs purged. 2008/03/01 12:36:02| 0 Swapfile clashes avoided. 2008/03/01 12:36:02| Took 0.08 seconds (1746.84 objects/sec). 2008/03/01 12:36:02| Beginning Validation Procedure 2008/03/01 12:36:02| Completed Validation Procedure 2008/03/01 12:36:02| Validated 301 Entries 2008/03/01 12:36:02| store_swap_size = 1508 2008/03/01 12:36:03| storeLateRelease: released 0 objects 2008/03/01 12:36:59| WARNING: Closing open FD 50 2008/03/01 12:36:59| diskHandleWrite: FD 11: disk write error: (9) Bad file descriptor 2008/03/01 12:36:59| storeDirWriteCleanLogs: Starting... 2008/03/01 12:36:59| WARNING: Closing open FD9 2008/03/01 12:36:59| xrename: Cannot rename c:/squid/var/cache/swap.state.clean to c:/squid/var/cache/swap.state: (17) File exists 2008/03/01 12:36:59| Finished. Wrote 229 entries. 2008/03/01 12:36:59| Took 0.01 seconds (15266.67 entries/sec). FATAL: Write failure -- check your disk space and cache.log Squid Cache (Version 3.0.STABLE1-CVS): Terminated abnormally. Regards Guido - Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
Re: Time for squid 3.0 STABLE2 ?
On Thu, 2008-02-28 at 12:41 +0900, Adrian Chadd wrote: I'd suggest just disabling COSS in -3 until someone ports over the changes or replaces it with something better. This was even decided on for the 3.0 release, but never done as Squid-3.0 didn't for from HEAD until very late in the release process.. It really is actually very broken for even light production use. Yes. Regards Henrik
Re: Time for squid 3.0 STABLE2 ?
Robert Collins wrote: On Thu, 2008-02-28 at 12:41 +0900, Adrian Chadd wrote: On Thu, Feb 28, 2008, Amos Jeffries wrote: * Close more bugs? Booger: stub time| COSS block-size = 512 bytes stub time| COSS largest file offset = -1 KB stub time| COSS cache_dir size = 102400 KB stub time| Fatal: COSS cache_dir size exceeds largest offset .FAIL: tests/testCoss I'd suggest just disabling COSS in -3 until someone ports over the changes or replaces it with something better. It really is actually very broken for even light production use. A very useful thing would be to file a bug on -3 that lists the changesets from 2 that need to be ported. -Rob Hm, yes. Henrik, is there a report somewhere that lgroups the merged changesets the same way the maintainer merge.html lists the un-merged and non-merged ones? Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: Time for squid 3.0 STABLE2 ?
Henrik Nordström wrote: tis 2008-02-19 klockan 23:00 +0100 skrev Guido Serassio: Hi, What about to release squid 3.0 STABLE2 ? Probably, even if I prefer to fix forwarding of large response headers first.. but it should not be a blocker for STABLE2.. I think that there are many patches already applied to HEAD-3 that could be applied also to SQUID_3_0. Certainly. Regards Henrik Henrik, could you check your patch 11467 and port it to 3.0 please? It's not applying cleanly. Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: Time for squid 3.0 STABLE2 ?
Just a few issues remaining before 3.0.STABLE-2. * patch 11467 back-porting. * Close more bugs? http://www.squid-cache.org/bugs/show_bug.cgi?id=2127 http://www.squid-cache.org/bugs/show_bug.cgi?id=2124 why is this not 2.6?? http://www.squid-cache.org/bugs/show_bug.cgi?id=2138 * Build and tests on as many OS as possible. (branch: SQUID_3_0) I am running the tests I use on Debian/Ubuntu already. Could the rest of you please jump in for any OS you have tests for or even just compiling on. * CVS branching? checkpoint?. Will need another How-To here I think Henrik. * Release announcement. Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: Time for squid 3.0 STABLE2 ?
On Thu, 2008-02-28 at 01:04 +1300, Amos Jeffries wrote: Just a few issues remaining before 3.0.STABLE-2. * patch 11467 back-porting. cd English ls ERR_* ../list * Close more bugs? http://www.squid-cache.org/bugs/show_bug.cgi?id=2127 http://www.squid-cache.org/bugs/show_bug.cgi?id=2124 why is this not 2.6?? http://www.squid-cache.org/bugs/show_bug.cgi?id=2138 * Build and tests on as many OS as possible. (branch: SQUID_3_0) I am running the tests I use on Debian/Ubuntu already. Could the rest of you please jump in for any OS you have tests for or even just compiling on. * CVS branching? checkpoint?. Will need another How-To here I think Henrik. * Release announcement. Amos
Re: Time for squid 3.0 STABLE2 ?
On Thu, 2008-02-28 at 01:04 +1300, Amos Jeffries wrote: Just a few issues remaining before 3.0.STABLE-2. * patch 11467 back-porting. cd English ls ERR_* ../list * Close more bugs? http://www.squid-cache.org/bugs/show_bug.cgi?id=2127 Is closed and verified by the reporter. http://www.squid-cache.org/bugs/show_bug.cgi?id=2124 Done. why is this not 2.6?? http://www.squid-cache.org/bugs/show_bug.cgi?id=2138 Don't know. * CVS branching? checkpoint?. Will need another How-To here I think Henrik.t update releasenotes and changelog. login on squid/cache.org and - get an up to date checkout of the tree cvs up -d -P - make sure the version in configure.in is correct - ./bootstrap.sh - cvs commit - cvs tag SQUID_3_0_STABLE2 - ./mkrelease.sh squid-3.0.STABLE2 /server/httpd/htdocs/squid-cache.org/Versions/v3/3.0/ (i think, verify the path) this should give you a suitable tarball in the website. download that, and the previous release and signature as well. verify the signature of the previous release make a diff between the two, and audit that diff to verify that the changes looks right. sign the new release and diff. upload the diff and signatures to the 3.0 folder on the web server. go to the 3.0 web folder co -l index.tmpl edit index.tmpl, moving the previous release down to older stable releases and the new as current stable release. ./make.sh verify that it got published right. copy the tarballs, diff, release notes and signatures to the ftp area. send announce
Re: Time for squid 3.0 STABLE2 ?
Hi all, Henrik Nordstrom wrote: On Thu, 2008-02-28 at 01:04 +1300, Amos Jeffries wrote: * Close more bugs? http://www.squid-cache.org/bugs/show_bug.cgi?id=2127 Is closed and verified by the reporter. About bug 2127, my understanding is that there are references about two bugs here. I am not sure, but I think the original bug reported here did not solved and still exists Regards, Christos
Re: Time for squid 3.0 STABLE2 ?
On Thu, 2008-02-28 at 01:04 +1300, Amos Jeffries wrote: Just a few issues remaining before 3.0.STABLE-2. snip done * Close more bugs? Booger: stub time| COSS block-size = 512 bytes stub time| COSS largest file offset = -1 KB stub time| COSS cache_dir size = 102400 KB stub time| Fatal: COSS cache_dir size exceeds largest offset .FAIL: tests/testCoss why is this not 2.6?? http://www.squid-cache.org/bugs/show_bug.cgi?id=2138 Don't know. * CVS branching? checkpoint?. Will need another How-To here I think Henrik.t update releasenotes and changelog. done. remainder pending the make-check failure. login on squid/cache.org and - get an up to date checkout of the tree cvs up -d -P - make sure the version in configure.in is correct - ./bootstrap.sh - cvs commit - cvs tag SQUID_3_0_STABLE2 - ./mkrelease.sh squid-3.0.STABLE2 /server/httpd/htdocs/squid-cache.org/Versions/v3/3.0/ (i think, verify the path) this should give you a suitable tarball in the website. download that, and the previous release and signature as well. verify the signature of the previous release make a diff between the two, and audit that diff to verify that the changes looks right. sign the new release and diff. upload the diff and signatures to the 3.0 folder on the web server. go to the 3.0 web folder co -l index.tmpl edit index.tmpl, moving the previous release down to older stable releases and the new as current stable release. ./make.sh verify that it got published right. copy the tarballs, diff, release notes and signatures to the ftp area. send announce
Re: Time for squid 3.0 STABLE2 ?
On Thu, Feb 28, 2008, Amos Jeffries wrote: * Close more bugs? Booger: stub time| COSS block-size = 512 bytes stub time| COSS largest file offset = -1 KB stub time| COSS cache_dir size = 102400 KB stub time| Fatal: COSS cache_dir size exceeds largest offset .FAIL: tests/testCoss I'd suggest just disabling COSS in -3 until someone ports over the changes or replaces it with something better. It really is actually very broken for even light production use. Adrian
Re: Time for squid 3.0 STABLE2 ?
Hi Amos, At 12:33 23/02/2008, Amos Jeffries wrote: Some weirdness: The following patches to 3.0 appear not to have been applied to 3-HEAD: 11456 Windows Port: call fdc_open() when opening IPC sockets. If I'm not wrong, this should not be needed in HEAD-3 (while is needed in SQUID_3_0) after this change: http://www.squid-cache.org/Versions/v3/HEAD/changesets/11433.patch Okay. Good enough. 11393 Fix missing default disk store type into QUICKSTART example. This is already included in this changeset: http://www.squid-cache.org/Versions/v3/HEAD/changesets/11261.patch Damn, my memory must be going again ;-) Thanks Guido. Amos
Re: Time for squid 3.0 STABLE2 ?
Amos Jeffries wrote: Henrik Nordström wrote: ons 2008-02-20 klockan 12:04 +1300 skrev Amos Jeffries: Henrik: It was suggested I ask you about how-to for editing the changesets. Seeing as I have stood up for 3.1 maintainer, I think I might get have some practice on 3.0. There is no editing, just classification grouping. It's all done using symbolic links today. changeset.group links to the main changeset of the group (or self if a lone patch) mainchangeset.nomerge marks a group as not suitable to be backported mainchangeset.merged links to the backported changeset To main work place to view as maintainer is changesets/merge.html of the prior branch (i.e. HEAD for 3.0 until 3.1 is branched) the changesets there marked with a ? there has not been grouped/classified yet. Workflow is to 1. Process the ? changesets bottom up, adding .group and .nomerge links where obvious. 2. Take a second pass over the patches and add more .nomerge links on things where there is doubt if it should be backported. 3. Apply the ones which apply cleanly. Don't forget to add an Author: line giving proper attribution, and copy the log message verbatim. Also help if the original changeset number is mentioned. 4. Ask to have the tricky ones backported. 5. Ask for backport votes on the stuff you aren't certain on. There is al long term goal to make this a little friendlier, but it's not given a very high priority, especially together with the VCS discussions... And when you get used to the symbolic links it's not so bad.. Regards Henrik Okay.everybody With that instruction (and a bit more on IRC). I'm off to patch 3.0 a lot... Amos Some weirdness: The following patches to 3.0 appear not to have been applied to 3-HEAD: 11456 Windows Port: call fdc_open() when opening IPC sockets. 11393 Fix missing default disk store type into QUICKSTART example. If they _have_ been applied to 3-HEAD please let me know the number of the 3-HEAD patch changeset. Thanks. Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: Time for squid 3.0 STABLE2 ?
Hi Amos, At 12:33 23/02/2008, Amos Jeffries wrote: Some weirdness: The following patches to 3.0 appear not to have been applied to 3-HEAD: 11456 Windows Port: call fdc_open() when opening IPC sockets. If I'm not wrong, this should not be needed in HEAD-3 (while is needed in SQUID_3_0) after this change: http://www.squid-cache.org/Versions/v3/HEAD/changesets/11433.patch 11393 Fix missing default disk store type into QUICKSTART example. This is already included in this changeset: http://www.squid-cache.org/Versions/v3/HEAD/changesets/11261.patch Regards Guido - Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
Re: Time for squid 3.0 STABLE2 ?
ons 2008-02-20 klockan 12:04 +1300 skrev Amos Jeffries: Henrik: It was suggested I ask you about how-to for editing the changesets. Seeing as I have stood up for 3.1 maintainer, I think I might get have some practice on 3.0. There is no editing, just classification grouping. It's all done using symbolic links today. changeset.group links to the main changeset of the group (or self if a lone patch) mainchangeset.nomerge marks a group as not suitable to be backported mainchangeset.merged links to the backported changeset To main work place to view as maintainer is changesets/merge.html of the prior branch (i.e. HEAD for 3.0 until 3.1 is branched) the changesets there marked with a ? there has not been grouped/classified yet. Workflow is to 1. Process the ? changesets bottom up, adding .group and .nomerge links where obvious. 2. Take a second pass over the patches and add more .nomerge links on things where there is doubt if it should be backported. 3. Apply the ones which apply cleanly. Don't forget to add an Author: line giving proper attribution, and copy the log message verbatim. Also help if the original changeset number is mentioned. 4. Ask to have the tricky ones backported. 5. Ask for backport votes on the stuff you aren't certain on. There is al long term goal to make this a little friendlier, but it's not given a very high priority, especially together with the VCS discussions... And when you get used to the symbolic links it's not so bad.. Regards Henrik signature.asc Description: Detta är en digitalt signerad meddelandedel
Re: Time for squid 3.0 STABLE2 ?
Henrik Nordström wrote: ons 2008-02-20 klockan 12:04 +1300 skrev Amos Jeffries: Henrik: It was suggested I ask you about how-to for editing the changesets. Seeing as I have stood up for 3.1 maintainer, I think I might get have some practice on 3.0. There is no editing, just classification grouping. It's all done using symbolic links today. changeset.group links to the main changeset of the group (or self if a lone patch) mainchangeset.nomerge marks a group as not suitable to be backported mainchangeset.merged links to the backported changeset To main work place to view as maintainer is changesets/merge.html of the prior branch (i.e. HEAD for 3.0 until 3.1 is branched) the changesets there marked with a ? there has not been grouped/classified yet. Workflow is to 1. Process the ? changesets bottom up, adding .group and .nomerge links where obvious. 2. Take a second pass over the patches and add more .nomerge links on things where there is doubt if it should be backported. 3. Apply the ones which apply cleanly. Don't forget to add an Author: line giving proper attribution, and copy the log message verbatim. Also help if the original changeset number is mentioned. 4. Ask to have the tricky ones backported. 5. Ask for backport votes on the stuff you aren't certain on. There is al long term goal to make this a little friendlier, but it's not given a very high priority, especially together with the VCS discussions... And when you get used to the symbolic links it's not so bad.. Regards Henrik Okay.everybody With that instruction (and a bit more on IRC). I'm off to patch 3.0 a lot... Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: Time for squid 3.0 STABLE2 ?
Alex Rousskov wrote: On Thu, 2008-02-21 at 14:46 +1300, Amos Jeffries wrote: - include directive. Being a very minor feature, and existing in 2.x. I'm undecide if it should be back-ported early to ease future upgrades from 2.6/2.7. I would be happy to see it backported to 3.0. It does not affect runtime code and does not affect old configs, so it should be safe. Eventually, things like that would go into the next minor release (i.e., v3.1 in this case). Currently we have too many disruptive features going into minor releases and cannot release them often enough for the keep the subreleases free of new features scheme to work well. what do you think of habitually considering back-porting where possible, the features added to 3.1 that are actually forward-ports from 2.x? Sounds like a good idea to me, _considering_ being the operative word. We do not have a list of 1000 features to go through, so it does not have to be rigid and formal. We can decide on a case-by-case basis. You catch my meaning exactly. Great. I'm thinking some basic criteria in a 2-minute thought process along the lines of: Did it exist in 2.6 before 3.0? 2.7 before 3.1? - No = probably ignore. Is it just a patch-and-tweak (not a lot of work)? - No = oh well Is it a big change to existing code (_new_ code gets past this)? - Yes = oh well goodbye. Is it worth a few minutes my time? - No = oh well, goodbye. ** Okay, it _might_ be worth it. Spot-check core for vetos. Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: Time for squid 3.0 STABLE2 ?
Hi, At 11:34 21/02/2008, Amos Jeffries wrote: You catch my meaning exactly. Great. I'm thinking some basic criteria in a 2-minute thought process along the lines of: Did it exist in 2.6 before 3.0? 2.7 before 3.1? - No = probably ignore. Is it just a patch-and-tweak (not a lot of work)? - No = oh well Is it a big change to existing code (_new_ code gets past this)? - Yes = oh well goodbye. Is it worth a few minutes my time? - No = oh well, goodbye. ** Okay, it _might_ be worth it. Spot-check core for vetos. So, the next step is to define the list of the candidate changeset/bug, and assign them to someone. Regards Guido - Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
Re: Time for squid 3.0 STABLE2 ?
Hi Amos, At 00:04 20/02/2008, Amos Jeffries wrote: Hi, What about to release squid 3.0 STABLE2 ? I think that there are many patches already applied to HEAD-3 that could be applied also to SQUID_3_0. If needed, I could try to contribute in the back port of some patch. I've been thinking along those lines myself for a while. Its a question of who does it, and which changesets. Whan I last looked at it I found a number that I could not confirm whether or not they were actually applicable to 3.0. There is also some small task of removing the back-ported changes from the 3-HEAD list of changes-since-3.0. I have some time now, if you like I can go through and pull up a list of those changesets I think should go in and the original author say yay/nay/backport-needed. I think that last word about any changeset should probably come from the release manager. So the first step is to identify a list of proposed changes, and after approve the really needed. There are other opinions about STABLE2 ? FYI: during the whole next week I will out of office and without a reliable Internet connection. Regards Guido - Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
Re: Time for squid 3.0 STABLE2 ?
Hi Amos, At 00:04 20/02/2008, Amos Jeffries wrote: Hi, What about to release squid 3.0 STABLE2 ? I think that there are many patches already applied to HEAD-3 that could be applied also to SQUID_3_0. If needed, I could try to contribute in the back port of some patch. I've been thinking along those lines myself for a while. Its a question of who does it, and which changesets. Whan I last looked at it I found a number that I could not confirm whether or not they were actually applicable to 3.0. There is also some small task of removing the back-ported changes from the 3-HEAD list of changes-since-3.0. I have some time now, if you like I can go through and pull up a list of those changesets I think should go in and the original author say yay/nay/backport-needed. I think that last word about any changeset should probably come from the release manager. Just one problem there. We don't formally have a release manager for 3.0. So the first step is to identify a list of proposed changes, and after approve the really needed. There are other opinions about STABLE2 ? Not as far as I can tell, just running through the patches to port down, release notes, waiting the period, and release. FYI: during the whole next week I will out of office and without a reliable Internet connection. Regards Guido - Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
Re: Time for squid 3.0 STABLE2 ?
On Wed, 2008-02-20 at 12:04 +1300, Amos Jeffries wrote: What about to release squid 3.0 STABLE2 ? I think that there are many patches already applied to HEAD-3 that could be applied also to SQUID_3_0. If needed, I could try to contribute in the back port of some patch. I've been thinking along those lines myself for a while. Its a question of who does it, and which changesets. Whan I last looked at it I found a number that I could not confirm whether or not they were actually applicable to 3.0. There is also some small task of removing the back-ported changes from the 3-HEAD list of changes-since-3.0. I have some time now, if you like I can go through and pull up a list of those changesets I think should go in and the original author say yay/nay/backport-needed. Please do! IMO, most of the bug fixes should go back to 3.0. New features, including support for arbitrary request methods should not. Thank you, Alex.
Re: Time for squid 3.0 STABLE2 ?
On Wed, 2008-02-20 at 12:04 +1300, Amos Jeffries wrote: What about to release squid 3.0 STABLE2 ? I think that there are many patches already applied to HEAD-3 that could be applied also to SQUID_3_0. If needed, I could try to contribute in the back port of some patch. I've been thinking along those lines myself for a while. Its a question of who does it, and which changesets. Whan I last looked at it I found a number that I could not confirm whether or not they were actually applicable to 3.0. There is also some small task of removing the back-ported changes from the 3-HEAD list of changes-since-3.0. I have some time now, if you like I can go through and pull up a list of those changesets I think should go in and the original author say yay/nay/backport-needed. Please do! IMO, most of the bug fixes should go back to 3.0. New features, including support for arbitrary request methods should not. Agreed. The few things I was unsure about were: - Duanes adjustment of the copyright. Why he being the only one at the time who had access to the 3.0 branch did not remove it there too. - include directive. Being a very minor feature, and existing in 2.x. I'm undecide if it should be back-ported early to ease future upgrades from 2.6/2.7. - how to remove the back-ported changesets from the HEAD list. Still had no help on this one and it is a bit of info I feel I need to keep the changesets accurate. On #2, what do you think of habitually considering back-porting where possible, the features added to 3.1 that are actually forward-ports from 2.x? To keep at least the semblance that 3.0 follows 2.x in the upgrade path? Amos
Re: Time for squid 3.0 STABLE2 ?
On Thu, 2008-02-21 at 14:46 +1300, Amos Jeffries wrote: - include directive. Being a very minor feature, and existing in 2.x. I'm undecide if it should be back-ported early to ease future upgrades from 2.6/2.7. I would be happy to see it backported to 3.0. It does not affect runtime code and does not affect old configs, so it should be safe. Eventually, things like that would go into the next minor release (i.e., v3.1 in this case). Currently we have too many disruptive features going into minor releases and cannot release them often enough for the keep the subreleases free of new features scheme to work well. what do you think of habitually considering back-porting where possible, the features added to 3.1 that are actually forward-ports from 2.x? Sounds like a good idea to me, _considering_ being the operative word. We do not have a list of 1000 features to go through, so it does not have to be rigid and formal. We can decide on a case-by-case basis. Alex.
Re: Time for squid 3.0 STABLE2 ?
Hi, What about to release squid 3.0 STABLE2 ? I think that there are many patches already applied to HEAD-3 that could be applied also to SQUID_3_0. If needed, I could try to contribute in the back port of some patch. I've been thinking along those lines myself for a while. Its a question of who does it, and which changesets. Whan I last looked at it I found a number that I could not confirm whether or not they were actually applicable to 3.0. There is also some small task of removing the back-ported changes from the 3-HEAD list of changes-since-3.0. I have some time now, if you like I can go through and pull up a list of those changesets I think should go in and the original author say yay/nay/backport-needed. Henrik: It was suggested I ask you about how-to for editing the changesets. Seeing as I have stood up for 3.1 maintainer, I think I might get have some practice on 3.0. Amos
