This is an automated email from the ASF dual-hosted git repository.
brondsem pushed a change to branch db/8520
in repository https://gitbox.apache.org/repos/asf/allura.git
discard d7d58b7e3 [#8520] update deprecated beautifulsoup methods
discard e1ea83174 [#8520] drop python 3.9 support for easier
entry_points(group= usage in Allura and other libraries like easywidgets and
activitystream)
discard 71d6e5bab [#8520] fixes
discard c639060f0 replacing pkg_resources
new e6257574e [#8520] replacing pkg_resources
new 40ef78f0a [#8520] fixes
new a833009cd [#8520] drop python 3.9 support for easier
entry_points(group= usage in Allura and other libraries like easywidgets and
activitystream)
new f0f102d8a [#8520] update deprecated beautifulsoup methods
new 6e395eb4b [#8520] show warnings from ./run_tests
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (d7d58b7e3)
\
N -- N -- N refs/heads/db/8520 (6e395eb4b)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 5 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
Allura/allura/lib/package_path_loader.py | 5 ++++-
Allura/allura/tests/unit/test_package_path_loader.py | 10 +++++-----
pytest.ini | 6 +++---
run_tests | 1 -
4 files changed, 12 insertions(+), 10 deletions(-)
