Sune Broendum Woeller

I just tried forcing it - more packages give warnings: root@wlr-laptop:/tmp# dpkg --force-conflicts -i tmp.RxjO2Hl7Jg/texlive-local_2014-1~9_all.deb dpkg: regarding .../texlive-local_2014-1~9_all.deb containing texlive-local: texlive-binaries conflicts with makejvf texlive-local provides makejvf and is to...

actually this is related to a hamful bug - if you have a multiline div inside another div, and rename the outer div, the matching is wrong, and the inner...

I think this would complicate other things. For instance it would not be possible to see if there is no effective_date. And: When publishing a page in plone (5.1.2), the...

@esteele let me know what can be improved - we need to make it easier...

You will also see these warnings when running : ``` ..../plone.coredev-5.1/src/mockup (master)$ make bootstrap mkdir -p ./mockup/build npm link audited 2066 packages in 4.152s found 50 vulnerabilities (19 low, 26...

The bootstrap issue is not fixed in a (v3) release yet: https://github.com/twbs/bootstrap/issues/25679

@vangheem for bootstrap at least I agree. But there is also some value in being able to report to clients what versions are depended upon; to be able to document...

I'm looking at some low hanging fruits to upgrade. Question: Are we still using saucelabs? And are we still testing on these old browsers? src/mockup/mockup/js/grunt.js: ``` testCI: { singleRun: true,...

We are using a git checkout of grunt-sed on a specific hash. But the original and the fork are identical: https://github.com/jharding/grunt-sed/compare/master...collective:master I'd use the released version of grunt-sed instead What...

Found the reason in the corresponding commit in cmfplone: " Use fork of grunt-sed The problem with released versions is that they are not compatible with newer grunt versions. This...