#foswiki-release 2018-01-22,Mon

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
***zak256 has left [11:47]
............... (idle for 1h14mn)
gac410Hi all ... Time for our release meeting. [13:01]
zak256Hello! I will attend more or less passively again. [13:02]
MichaelDaumHi there [13:02]
gac410I thought I was going to be telling you all that I built 2.1.5 yesterday. [13:05]
MichaelDaumthats awesome [13:05]
gac410But I installed a new perlbrew, and found a number of unescaped { braces
Looks like they keep tightening up the parser.
I just pushed the fixes. ... Also tried 5.10 and found compile errors in UpdatesPlugin
[13:05]
MichaelDaumseen it. [13:07]
gac410So I did a bunch more testing ... so far it still looks release worthy [13:07]
MichaelDaumhowever the checkin mentions 5.10, whereas the task is about 5.27.8 [13:07]
gac410Ya. I cheated. [13:07]
MichaelDaumtststs
btw 5.10 is terribly insecure: see CVE-2017-12883, CVE-2017-12837
[13:08]
gac410The bulk of the changes were the unescaped {. Well. We still officially claim compatibility with 5.8.8, but I can't even get that one to compile. [13:09]
MichaelDaumnobody should really be using perl < 5.26.1 ... or only when the distribution backported fixes for above CVEs. [13:09]
gac410I have 5.8.9, it has other problems. One test uses // if-defined perl op. [13:09]
MichaelDaumwe can't be serious about 5.8.8 for foswiki 2.x
unicode received loads of important fixes in 5.22
[13:10]
gac410I agree with you. But we've never officially said we don't support it, so I can't just walk away from it. [13:11]
MichaelDaumcan we raise the bar here, please? [13:11]
gac410I think we had a feature proposal that we agreed on bumping it in the next *major* release 3.x I don't recall now.
It's a pain. I'd rather delete the old perlbrews
[13:12]
MichaelDaumsure [13:13]
zak256I have no problem using something newer as requirement and don't think it should be that much of a problem. If it compiles on 5.10, maybe set this as requirement? [13:13]
MichaelDaumthats really not enough for foswiki-2.x [13:14]
gac410well to make unicode code work well, we ought to be up in the 20's for sure. [13:14]
zak256That would be the recommenden version then I guess?
The minimal required version should be the one that is absolutely necessary I think.
[13:14]
MichaelDaum5.22.1 [13:16]
zak256Ok... then 5.22.1 it should be. [13:16]
gac410gac410 needs to dig back through the old feature proposals. I guess it depends on how you define "Absolutely necessary" ... Performance? Compiles? Features? [13:17]
MichaelDaumSecurity? [13:17]
zak256compiles=yes, features=all the default features which are included should work, yes
performance... not necessarily
[13:18]
gac410Well compiles and features "work" ... perl 5.8.8 still works ... mostly :P [13:18]
zak256security: I think we shouldn't consider perl CVEs, that's a matter of the perl installation. If someone has an old perl version with backported fixes, that should work [13:18]
MichaelDaumbut yea, we can be more specific here: perl-5.10+ is fine, per-5.22.1+ is a major performance improvement, 5.26.1+ fixes important security problems [13:18]
gac410https://foswiki.org/Development/RequirePerl510From2017x03 is the most recent [13:19]
zak256I used Perl 5.16 for some time and it worked, although performance was better with the newer perl [13:19]
MichaelDaumright. so why not bring these infos to the users. [13:19]
vrurgHi all [13:20]
zak256The important thing is: People who want to setup a new Foswiki need that information to see if they can install it. If they have an environment with perl 5.16 they need to know, that they _can_ use foswiki, although not with the best performance. [13:20]
gac410We did agree on some updated language in 2.1 iirc. looking...
Hi vrurg
[13:21]
zak256I agree with MichaelDaum: Just give exactly this information to the users. [13:21]
gac410SystemRequirements states: "5.8.8 or higher. A minimum of perl 5.12 is recommended." :( [13:23]
zak256Can't we just update that for 2.1.5 ? [13:24]
gac410We are so dependent upon the distros. In theory, we only make requirements changes in minor/major releases. A "patch" should never break your system by introducing external requirements. [13:24]
MichaelDaumokay so then lets reserve this for 2.2.0 [13:25]
zak256I agree. [13:25]
gac410We really need to add a "use 5.12" or some such, to force perl to use unicode strings [13:25]
zak256Are there so many changes then in 2.1.5 ? [13:25]
MichaelDaumbtw gac410, can you check in fixes in Item14605 to master as well? thanks. [13:25]
gac410Yes I just did the push while I was waiting for coffee. ;)
Now I need to merge
Ask and ye shall receive
[13:25]
MichaelDaumyay
thanks
[13:27]
gac410The perl issue is two-fold. 1) What are the major distributions shipping in their current releases. And 2) How much time is left on their supported "LTS" versions.
RedHat is the one that kills us
[13:28]
MichaelDaumRedHat has an interesting approach to CVE-2017-12883: https://bugzilla.redhat.com/show_bug.cgi?id=1492093 says "wont fix" ... oh-kay
same for CVE-2017-12837: https://bugzilla.redhat.com/show_bug.cgi?id=1492091
[13:29]
zak256It says "Perl as shipped in Red Hat Enterprise Linux 7 and older have not been found to be vulnerable."
and "This issue does not affect perl versions older than 5.18. Perl as shipped in Red Hat Enterprise Linux 7 and older are not affected by this vulnerability."
[13:30]
gac410y, In this way, by staying really back-level, they avoid recent security issues, but suffer the performance issues. [13:31]
zak256yes... unfortunately :( [13:31]
MichaelDaumchecked distro watch: their newest perl is 5.16.3 in RHEL-7.4
so their perl even is not recommended for proper unicode
[13:32]
zak256yes, we use that here. That's why I got my own Perl [13:32]
MichaelDaumme too even though I am on ubuntu [13:33]
zak256The fact is: This is in the end not a Foswiki issue, but a Perl or distribution issue. [13:33]
gac410Anyway, the bigger decision for 2.2, is when do we change the "use" statement to force true unicode strings throughout [13:34]
MichaelDaummaybe I can find some perl core devs on the FOSDEM. will bring it up. [13:35]
gac410https://foswiki.org/Development/RequirePerl510From2017x03 has some recommendations, that we use v5.16.3 starting in Foswiki 3.0
Ah... I need to bring up a possible bug :(((
[13:36]
MichaelDaumgac410, 2.2.0 seems to be the right scope for that change, he says not knowing what would break then. :| [13:37]
gac410https://trunk.foswiki.org/TestCases/TestCaseEditTableAllFieldTypes
clicking the "stain" for the Mood (radio button) and check (checkboxes) cells don't work.
You get a rendered edit cell with no or incorrect selected elements.
I'm not sure when this broke.
I was trying last night to check it out on older foswiki, but didn't get very far
Edit row, and edit the whole table both work fine.
[13:37]
MichaelDaumthere are subtle javascript errors
edit a cell on the last row, cancel out, leave the table to the bottom, enter the same row, no yellow edit corners, hovering over another row and then back brings it back
sux
[13:42]
gac410y, ERP does have its issues. [13:44]
vrurgMichaelDaum: it also incorrectly handles <th> in a data (not header) row. Fixed in my patch. [13:44]
gac410The bigger question... What does this discovery do for 2.1.5. I need to open a task. but is it a new issue that should block 2.1.5, or do I finally release the darn thing. [13:45]
uebera||Hi there. gac410: Is the mood icon supposed to change without clicking on the disk icon?
(because that works.)
[13:45]
gac410The mood should reflect the "radio button" selected in edit.
If you clikc the stain, you should see one radio button highlighted. I get none.
On the "Check" column, clikc the stain, should show 3 of 4 checkboxes selected. I get only A checked.
Full table edit and full row edit though appear to work ine.
fine
[13:46]
uebera||yes, I see the same. [13:48]
gac410hm i was going to say please don't save :( That will put our git sources into conflict I suspect, since we don't commit from t.f.o. I'll ssh in and revert later :D [13:49]
uebera||Sorry, we can delete r2. [13:49]
gac410nah... I'll just do a "git checkout" later [13:49]
uebera||I thought t.f.o was overwritten every 15mins?
uebera|| needs to reread the documentation.
[13:50]
MichaelDaumgot a phone call coming up in 10 mins. will check back later. wrt release: gac410, if you like to create a blog posting unpublished I can look over it pimping it up a bit, maybe another image. [13:50]
gac410Okay. So 2.1.5 is a go. Ignore the ERP issues? [13:51]
uebera||Can we add avahi-daemon to the VM for 2.1.5? [13:51]
MichaelDaumyes. we can publish fixes later in between releases always. [13:51]
zak256If this can be solved for 2.1.6 then, I am for a release. [13:52]
gac410uebera||: Y, however I have not started to refresh the VM yet. That takes a bit more effort. [13:52]
uebera||No problem, I can help you test it later on... it's not urgent. ;) [13:52]
gac410re trunk. I'll have to look at the code again, but we are selective, we don't do a full overwrite of the sources. [13:53]
uebera||I see. [13:53]
gac410Okay. I've fixed it up from the shell. Found another topic that was "both modified" as well.
Anyway, we are at an hour. ... anything else for release meeting? We didn't really touch on 2.2.
[13:59]
uebera||Not from my side. [14:04]
vrurgNeigher from my. [14:05]
zak256no [14:05]
gac410Okay, lets wrap it up. I'll get 2.1.5 built today, We can let it soak on foswiki.org for 24 hours and then publish the announcements tomorrow.
Thanks everyone
[14:06]
vrurgThanks! [14:08]
uebera||Thanks! [14:08]
gac410uebera||: I'll try to catch you later regarding avahi-daemon. Do I need to configure it, or is it just an apt-get install and done. [14:09]
uebera||Sure. It should be enough to install the package, deploy the two definition files I mentioned a few days ago, and maybe add http://foswiki.local as valid hostname so it works out of the box.
--> https://media.projektzentrisch.de/temp/avahi.tar.gz
(The second file is for https; not sure this is set up, but we could add it as well.)
[14:10]
gac410We don't have https configured I don't believe. Trying to keep the setup simple [14:15]
uebera||Then we only need the http file ;) [14:15]
gac410vrurg, you mentioned the ERP issue with <th> ... is there a task for that one?
I just opened Item14606 for the edit issue
[14:16]
vrurgNo, I didn't have much time back then to make another task. As it was primarly targetting the drag button (it is showing in incorrect position) I included the fix into the patch.
I'm currently finishing a local work project and hope to get back to the flickering issue of the patch.
[14:18]
gac410Okay y, Item14537 shakey table. [14:19]
vrurg<th> problem is simple: ERP doesn't consider it a cell thus just skipping it always.
But a *bold* table cell produces <th>. Basically, to my view, use of CSS font-weight would be more correct.
[14:20]
gac410y our table handling is quite archaic [14:27]
................................ (idle for 2h36mn)
MichaelDaumgac410, see https://blog.foswiki.org/Blog/Foswiki215IsReleased ... looking up some image material to add to the posting [17:03]
gac410Looks good MichaelDaum ... thanks. [17:05]
MichaelDaumremoved For users... For admins headings [17:05]
gac410gac410 needs to go look at translation status. Maybe we ought to ack the 100%ers
y. I tend to overlook things like that. Gives it an international flair ;)
[17:07]
MichaelDaumdo we still provide a download from sourceforge or github only? [17:16]
gac410I have not uploaded sourceforge yet. But I will eventually get to it. [17:17]
MichaelDaumomg fontawesome 5.0.4 is out [17:27]
.... (idle for 16mn)
sure :D
Foswiki: the perfect xmas present.
gac410, uebera||, let me know when you are done fixing the posting and that it should go public. I'll put it on twitter and facebook afterwards.
[17:43]
gac410I guess we could say that 19 extensions are updated in this release? (6 more to go with uploading) [17:47]
uebera||Yes, I'd add that (because that's what the banner says atm :o). [17:48]
gac410Chinese (Taiwan), French, Italian, Ukrainian are at 100% translated. [17:49]
uebera||Do we add a link first for "You may download either from http://en.wikipedia.org/wiki/Special:Search?go=Go&search=][Soureforge" or do we silently change it afterwards? [17:49]
gac410Czech, Danish, German and Klingon are 90%+ [17:50]
uebera||Strange. '[[' gets modified by Konversation? [17:50]
gac410uebera||: Best to point to Foswiki:Download. That will have links to our preferred and alternate locations. [17:52]
uebera||So maybe change the announcement to ``You may download it from different locations, see [[https://github.com/foswiki/distro/releases/download/FoswikiRelease02x01x05/][our download page]] for details.´´ [17:55]
gac410No.... See https://foswiki.org/Download/FoswikiRelease02x01x05
The Download web is where we always have the latest info / pointers
[17:56]
uebera||gosh, of course.
corrected.
[17:57]
The announcement looks good to me, but maybe George wants to have a look.
Once the the blog entry if public, I'll post an announcement to the XING Foswiki group as well.
[18:06]
gac410The extensions are all uploaded. ... I hope ;) [18:08]
***zak256 has left [18:10]
....... (idle for 34mn)
gac410I'll use the blog page as the start for the announcement email. [18:44]
uebera||uebera|| forgot to modifiy the meta description (saw it after I posted to the XING Foswiki group). I take it once we touch it now it gets republished? (I'll keep my hands off it…) [18:51]
gac410er... Meta descriptioni in what? [18:51]
uebera||Of the blog post.
(you see these on the "SEO" tab.)
[18:52]
gac410gac410 doesn't really follow all that stuff. Looked at raw=all view to see what you were talking about [18:53]
............. (idle for 1h3mn)
uebera||: You said to add foswiki.local as a valid hostname. Where do you want that? /etc/hosts? or in the Foswiki LocalSite.cfg or ??? [19:56]
uebera||No, that's in configure (valid aliases for the host name).
So, yes, LocalSite.cfg ;)
[19:57]
gac410okay so http://foswiki.local ... hm.... That's already the DefaultUrlHost. Nothing to change,. [19:58]
uebera||Ah, great. I thought it was empty. [19:59]
........ (idle for 37mn)
gac410The vmware image is uploading to github now. It will take a whie. [20:36]
..... (idle for 21mn)
uebera||Unpacking it now... [20:57]
gac410great. Let me know how it goes. If it is okay, I'll upload it to sourceforge too and change the download topic. [20:58]
btw uebera|| ... if you have any ideas on stuff to remove to shrink the vm a bit more, please let me know.
I've got a script in the root user that "cleans" the image
[21:06]
uebera||Using VirtualBox on Linux, "http://foswiki.local" works but shows an Internal Server Error. [21:07]
gac410damn. Let me boot it again. Did I miss some ownership changes on the var/www/foswiki directory? [21:07]
uebera||Hm, the ownership looks ok.
Sorry, seemed to be a local problem. The test machine is too slow ("mod_fcgid: read data timeout in 30 seconds"). If you keep refreshing, it works.
[21:09]
gac410strange. I've never run into anything like that. [21:13]
uebera||Well, the MacMini I use is very slow and also I made the mistake to run "dpkg-reconfigure keyboard-configuration" in parallel which rebuilds the kernel.
I forgot that the image has ssh which accepts login via password.
uebera|| is not used to that ;)
[21:14]
gac410y. no sense trying to use ssh keys on a demo vm like this.
Comes right up for me. First hit on web server, maybe 2 seconds.
[21:15]
uebera||As it should be. Looking good. :) [21:17]
gac410Did the foswiki.local part work. Thats something I'm not prepared to test. [21:17]
uebera||Time to retire the MacMini Late2009 within the next months (Intel NUCs are so much faster nowadays).
Yes, that's what I tried first.
[21:18]
gac410great [21:19]
uebera||Regarding the shrinking, we can compare the list of packages once the vagrant test setup based on ubuntu-minimal works here. [21:24]
gac410okay. At least it didn't grow at all this time.
Uploading to sourceforge now
[21:25]
......... (idle for 42mn)
btw uebera|| If you want to feed back anything into my vm build process, see https://foswiki.org/Development/VirtualMachineImages [22:09]
..... (idle for 24mn)
uebera||thx, I will have a look at that. [22:33]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)