Jens Vagelpohl

For the moment I have changed the configuration so the following is true: - `www.zodb.org` now points to the VM under my control, which redirects all access to `https://zodb.org` -...

I was just going to say the same thing. In a conference call a couple weeks ago Jim made it clear that he isn't using ZODB for anything right now,...

> P.S. Did maybe @tseaver somehow somewhere provided a similar update about his status? At [Pylons/zodburi#29](https://github.com/Pylons/zodburi/pull/29) I'm struggling waiting for review feedback and it is not coming despite many ping...

In your situation I would manually add debugging code to see where in the code the warning is originating and what that blob item is. That may help.

I am seeing issues that may at least be related. There's a **very insidious** bug in how buildout selects a suitable package from a list of packages provided from the...

Fixed by #1066

FYI, the file `.github/workflows/tests.yml` is auto-generated and should not be edited by hand. It uses the meta/config package, see https://github.com/zopefoundation/meta/tree/master/config, which is configured using the `.meta.toml` file.

The ZODB is governed by the OSI-certified Zope Public License version 2.1. See https://opensource.org/license/zpl-2-1/. I can't say anything about license compatibility and none of us are lawyers.

Please take a look at the GitHub Actions test run. There's some linting issues and this PR breaks all Windows tests.

There's still a linter failure: ``` lint: commands[1]> flake8 src setup.py src/ZODB/blob.py:945:1: W293 blank line contains whitespace src/ZODB/blob.py:954:64: W291 trailing whitespace ```