Re: [RFU] sqlite3-3.7.17-3
On Jun 13 16:54, Warren Young wrote: Would someone flip this package from test to curr for me, please? Leave 3.7.16.2-1 as prev. Done. Do you want to keep 3.7.13-1? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
Re: [RFU] sqlite3-3.7.17-3
On 6/14/2013 01:54, Corinna Vinschen wrote: On Jun 13 16:54, Warren Young wrote: Would someone flip this package from test to curr for me, please? Leave 3.7.16.2-1 as prev. Done. Thanks! Do you want to keep 3.7.13-1? I didn't know I could have more than one prev. Sure, let's keep it a while. Just in this past week, I got a complaint about one of the changes in .16.2 relative to .13, so it's conceivable some may want to step back two steps if .17 doesn't work out for everyone.
Re: [RFU] sqlite3-3.7.17-3
Would someone flip this package from test to curr for me, please? Leave 3.7.16.2-1 as prev.
Re: [RFU] sqlite3-3.7.17-3
Il 6/10/2013 9:55 PM, Warren Young ha scritto: Leave 3.7.16.2-1 as curr, and make this test only for now. you should make it test adding the relevant prev/current/test entries as specified on http://cygwin.com/setup.html (I am hoping to be able to promote it to curr later, but it changes too much to risk that without more testing. The only reason I'm RFU'ing it is because there seems to be some resistance to installing test versions from raw tarballs.) From within release/sqlite3: wget -e robots=off --cut-dirs=2 -np -nH -A'*3.7.17-3*' -A'*.hint' \ -r http://etr-usa.com/cygwin/sqlite3/ uploaded and put as test. Regards Marco
Re: [RFU] sqlite3-3.7.17-3
On 6/11/2013 01:37, marco atzeri wrote: you should make it test adding the relevant prev/current/test entries as specified on http://cygwin.com/setup.html Is there a way to set this via the .cygport file? I tried searching its HTML manual, and didn't find one. The alternative is to manually adjust the generated .hint files on test releases on my end.
Re: [RFU] sqlite3-3.7.17-3
On 6/11/2013 10:10 AM, Warren Young wrote: On 6/11/2013 01:37, marco atzeri wrote: you should make it test adding the relevant prev/current/test entries as specified on http://cygwin.com/setup.html Is there a way to set this via the .cygport file? I tried searching its HTML manual, and didn't find one. The alternative is to manually adjust the generated .hint files on test releases on my end. David Rothenberger submitted a patch for cygport to this list on 6/2, to add that feature. Don't know if Yaakov incorporated it or not, but you could locally patch your cygport if you wanted. -- Chuck
[RFU] sqlite3-3.7.17-3
Leave 3.7.16.2-1 as curr, and make this test only for now. (I am hoping to be able to promote it to curr later, but it changes too much to risk that without more testing. The only reason I'm RFU'ing it is because there seems to be some resistance to installing test versions from raw tarballs.) From within release/sqlite3: wget -e robots=off --cut-dirs=2 -np -nH -A'*3.7.17-3*' -A'*.hint' \ -r http://etr-usa.com/cygwin/sqlite3/
