[fossil-users] Openssl 1.1.0 [Was:Objections to merging stash-fixes branch?]
2016-09-08 5:00 GMT+02:00 Joe Mistachkin: > I think the MSVC makefile needs updating for the OpenSSL 1.1.0 changes > to work. I think it should work fine after my changes, but feel free to fix anything I screwed up ;-) > Also, maybe we should wait for 1.1.0 to mature a bit prior > to migrating Fossil to it? Technically, their 1.0.2 branch is still > listed as "stable" and "supported" (until 2019-12-31). That's your decision (or .. actually Richard's ???) In my view, openssl-1.1.0 has a larger user base than SQLite 1.15, so it should be OK for fossil trunk. I didn't find anything wrong with it so far. (I wouldn't recommend it - yet - as default for the 1.35 branch) Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Objections to merging stash-fixes branch?
Thus said "Joe Mistachkin" on Wed, 07 Sep 2016 20:00:03 -0700: > FYI, I've modified your branch to re-merge changes from trunk without > the changes for OpenSSL 1.1.0, which is not quite ready for primetime > yet. Thanks for the heads up. The nice thing about Fossil is that it makes this whole operation so simple. Thanks, Andy -- TAI64 timestamp: 400057d1201c ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Double forward slash when using --baseurl
Hi all, I'm trying to set up a fossil server behind a loadbalancer, and so am using the --baseurl option to fossil server. For the main web page links it is working fine, however on some of the pages, I am getting links to pages with an extra '/' being inserted. It happens with all of the links from the 'Admin' tab, e.g- "https://fossil.mydomain.com//setup_ulist; "https://fossil.mydomain.com//setup_config; So these are giving a 'Not Found' when clicked (if you remove the extra / by hand, they are working fine...) Anyone have a known workaround? Cheers, Greg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Infinite loop on merge
2016-09-08 1:32 GMT+02:00 Ross Berteig: > So my testing does not block releasing 1.35.1. > > I have no strong opinion about whether such an update is required, but the > most recent regression does seem like it causes real problems if tripped > over. I agree, but it's not up to me to decide. Upcoming SQLite 3.14.2 might be an additional excuse to do a fossil 1.35.1 release (although I don't think fossil is actually affected by any of the fixed bugs since SQLite 3.13) Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Double forward slash when using --baseurl
Zombies wrote: > > For the main web page links it is working fine, however on some of the pages, > I am getting links to pages with an extra '/' being inserted. It happens with > all of the links from the 'Admin' tab, e.g- > What is the full command line being used? -- Joe Mistachkin @ https://urn.to/r/mistachkin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Openssl 1.1.0 [Was:Objections to merging stash-fixes branch?]
Jan Nijtmans wrote: > > That's your decision (or .. actually Richard's ???) > In my view, openssl-1.1.0 has a larger user base > than SQLite 1.15, so it should be OK for fossil > trunk. I didn't find anything wrong with it so far. > (I wouldn't recommend it - yet - as default > for the 1.35 branch) > I simply moved the changes to a branch for further review, partially because there are incompatible changes to the MSVC build system (which is technically a build break). Meanwhile, the 1.0.2 branch of OpenSSL has a much longer support end-date (since it's "LTS") than the 1.1.0 branch, e.g.: https://www.openssl.org/policies/releasestrat.html Version 1.1.0 will be supported until 2018-08-31. Version 1.0.2 will be supported until 2019-12-31 (LTS). Given that information, I don't see any urgent need to migrate to the 1.1.0 branch of OpenSSL, especially considering the major, incompatible differences present there. -- Joe Mistachkin @ https://urn.to/r/mistachkin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
