Warning: Permanently added '2620:52:3:1:dead:beef:cafe:c1ca' (ED25519) to the list of known hosts.

You can reproduce this build on your computer by running:

  sudo dnf install copr-rpmbuild
  /usr/bin/copr-rpmbuild --verbose --drop-resultdir --task-url https://copr.fedorainfracloud.org/backend/get-build-task/7150395-fedora-40-x86_64 --chroot fedora-40-x86_64


Version: 0.71
PID: 10030
Logging PID: 10031
Task:
{'allow_user_ssh': False,
 'appstream': False,
 'background': True,
 'build_id': 7150395,
 'buildroot_pkgs': [],
 'chroot': 'fedora-40-x86_64',
 'enable_net': False,
 'fedora_review': False,
 'git_hash': '53795c9e12ed170ad6cdc9e67df854468e33bbdb',
 'git_repo': 'https://copr-dist-git.fedorainfracloud.org/git/@copr/PyPI/python-ckan',
 'isolation': 'default',
 'memory_reqs': 2048,
 'package_name': 'python-ckan',
 'package_version': '2.10.4-1',
 'project_dirname': 'PyPI',
 'project_name': 'PyPI',
 'project_owner': '@copr',
 'repo_priority': None,
 'repos': [{'baseurl': 'https://download.copr.fedorainfracloud.org/results/@copr/PyPI/fedora-40-x86_64/',
            'id': 'copr_base',
            'name': 'Copr repository',
            'priority': None}],
 'sandbox': '@copr/PyPI--ksurma',
 'source_json': {},
 'source_type': None,
 'ssh_public_keys': None,
 'submitter': 'ksurma',
 'tags': [],
 'task_id': '7150395-fedora-40-x86_64',
 'timeout': 18000,
 'uses_devel_repo': False,
 'with_opts': [],
 'without_opts': []}

Running: git clone https://copr-dist-git.fedorainfracloud.org/git/@copr/PyPI/python-ckan /var/lib/copr-rpmbuild/workspace/workdir-6l0e9ih2/python-ckan --depth 500 --no-single-branch --recursive

cmd: ['git', 'clone', 'https://copr-dist-git.fedorainfracloud.org/git/@copr/PyPI/python-ckan', '/var/lib/copr-rpmbuild/workspace/workdir-6l0e9ih2/python-ckan', '--depth', '500', '--no-single-branch', '--recursive']
cwd: .
rc: 0
stdout: 
stderr: Cloning into '/var/lib/copr-rpmbuild/workspace/workdir-6l0e9ih2/python-ckan'...

Running: git checkout 53795c9e12ed170ad6cdc9e67df854468e33bbdb --

cmd: ['git', 'checkout', '53795c9e12ed170ad6cdc9e67df854468e33bbdb', '--']
cwd: /var/lib/copr-rpmbuild/workspace/workdir-6l0e9ih2/python-ckan
rc: 0
stdout: 
stderr: Note: switching to '53795c9e12ed170ad6cdc9e67df854468e33bbdb'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 53795c9 automatic import of python-ckan

Running: copr-distgit-client sources
INFO: Calling: curl -H Pragma: -o ckan-2.10.4.tar.gz --location --connect-timeout 60 --retry 3 --retry-delay 10 --remote-time --show-error --fail --retry-all-errors https://copr-dist-git.fedorainfracloud.org/repo/pkgs/@copr/PyPI/python-ckan/ckan-2.10.4.tar.gz/md5/f59b72343d1fd0ab5d83824c0ef6deb5/ckan-2.10.4.tar.gz
/usr/bin/tail: /var/lib/copr-rpmbuild/main.log: file truncated
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 8580k  100 8580k    0     0  52.5M      0 --:--:-- --:--:-- --:--:-- 52.7M
INFO: Reading stdout from command: md5sum ckan-2.10.4.tar.gz

Running (timeout=18000): unbuffer mock --spec /var/lib/copr-rpmbuild/workspace/workdir-6l0e9ih2/python-ckan/python-ckan.spec --sources /var/lib/copr-rpmbuild/workspace/workdir-6l0e9ih2/python-ckan --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1710336054.221965 -r /var/lib/copr-rpmbuild/results/configs/child.cfg
INFO: mock.py version 5.5 starting (python version = 3.12.1, NVR = mock-5.5-1.fc39), args: /usr/libexec/mock/mock --spec /var/lib/copr-rpmbuild/workspace/workdir-6l0e9ih2/python-ckan/python-ckan.spec --sources /var/lib/copr-rpmbuild/workspace/workdir-6l0e9ih2/python-ckan --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1710336054.221965 -r /var/lib/copr-rpmbuild/results/configs/child.cfg
Start(bootstrap): init plugins
INFO: tmpfs initialized
INFO: selinux enabled
INFO: chroot_scan: initialized
INFO: compress_logs: initialized
Finish(bootstrap): init plugins
Start: init plugins
INFO: tmpfs initialized
INFO: selinux enabled
INFO: chroot_scan: initialized
INFO: compress_logs: initialized
Finish: init plugins
INFO: Signal handler active
Start: run
INFO: Start(/var/lib/copr-rpmbuild/workspace/workdir-6l0e9ih2/python-ckan/python-ckan.spec)  Config(fedora-40-x86_64)
Start: clean chroot
Finish: clean chroot
Mock Version: 5.5
INFO: Mock Version: 5.5
Start(bootstrap): chroot init
INFO: mounting tmpfs at /var/lib/mock/fedora-40-x86_64-bootstrap-1710336054.221965/root.
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled package manager cache
Start(bootstrap): cleaning package manager metadata
Finish(bootstrap): cleaning package manager metadata
INFO: Guessed host environment type: unknown
INFO: Using bootstrap image: registry.fedoraproject.org/fedora:40
INFO: Pulling image: registry.fedoraproject.org/fedora:40
INFO: Copy content of container registry.fedoraproject.org/fedora:40 to /var/lib/mock/fedora-40-x86_64-bootstrap-1710336054.221965/root
INFO: Checking that registry.fedoraproject.org/fedora:40 image matches host's architecture
INFO: mounting registry.fedoraproject.org/fedora:40 with podman image mount
INFO: image registry.fedoraproject.org/fedora:40 as /var/lib/containers/storage/overlay/8d3b52bd7baca8b7c86c3cea26a0cc19786aba5d864073bdbcaa6b7dbdbd9364/merged
INFO: umounting image registry.fedoraproject.org/fedora:40 (/var/lib/containers/storage/overlay/8d3b52bd7baca8b7c86c3cea26a0cc19786aba5d864073bdbcaa6b7dbdbd9364/merged) with podman image umount
INFO: Using 'dnf' instead of 'dnf5' for bootstrap chroot
INFO: Package manager dnf detected and used (fallback)
INFO: Bootstrap image not marked ready
Start(bootstrap): installing dnf5 tooling
No matches found for the following disable plugin patterns: local, spacewalk, versionlock
Copr repository                                  39 MB/s |  41 MB     00:01    
fedora                                           13 MB/s |  33 MB     00:02    
updates                                         1.5 kB/s | 134  B     00:00    
Last metadata expiration check: 0:00:01 ago on Wed Mar 13 13:21:09 2024.
Dependencies resolved.
================================================================================
 Package              Architecture   Version               Repository      Size
================================================================================
Installing:
 dnf5                 x86_64         5.1.12-1.fc40         fedora         588 k
 dnf5-plugins         x86_64         5.1.12-1.fc40         fedora         351 k
Installing dependencies:
 fmt                  x86_64         10.2.1-3.fc40         fedora         125 k
 libdnf5              x86_64         5.1.12-1.fc40         fedora         974 k
 libdnf5-cli          x86_64         5.1.12-1.fc40         fedora         262 k
 sdbus-cpp            x86_64         1.4.0-2.fc40          fedora         110 k

Transaction Summary
================================================================================
Install  6 Packages

Total download size: 2.4 M
Installed size: 6.5 M
Downloading Packages:
(1/6): fmt-10.2.1-3.fc40.x86_64.rpm             491 kB/s | 125 kB     00:00    
(2/6): dnf5-plugins-5.1.12-1.fc40.x86_64.rpm    1.1 MB/s | 351 kB     00:00    
(3/6): dnf5-5.1.12-1.fc40.x86_64.rpm            1.6 MB/s | 588 kB     00:00    
(4/6): libdnf5-cli-5.1.12-1.fc40.x86_64.rpm     4.0 MB/s | 262 kB     00:00    
(5/6): sdbus-cpp-1.4.0-2.fc40.x86_64.rpm        1.6 MB/s | 110 kB     00:00    
(6/6): libdnf5-5.1.12-1.fc40.x86_64.rpm         4.9 MB/s | 974 kB     00:00    
--------------------------------------------------------------------------------
Total                                           5.0 MB/s | 2.4 MB     00:00     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                        1/1 
  Installing       : fmt-10.2.1-3.fc40.x86_64                               1/6 
  Installing       : libdnf5-5.1.12-1.fc40.x86_64                           2/6 
  Installing       : libdnf5-cli-5.1.12-1.fc40.x86_64                       3/6 
  Installing       : dnf5-5.1.12-1.fc40.x86_64                              4/6 
  Installing       : sdbus-cpp-1.4.0-2.fc40.x86_64                          5/6 
  Installing       : dnf5-plugins-5.1.12-1.fc40.x86_64                      6/6 
  Running scriptlet: dnf5-plugins-5.1.12-1.fc40.x86_64                      6/6 

Installed:
  dnf5-5.1.12-1.fc40.x86_64              dnf5-plugins-5.1.12-1.fc40.x86_64      
  fmt-10.2.1-3.fc40.x86_64               libdnf5-5.1.12-1.fc40.x86_64           
  libdnf5-cli-5.1.12-1.fc40.x86_64       sdbus-cpp-1.4.0-2.fc40.x86_64          

Complete!
INFO: Switching package manager from dnf to the dnf5 (direct choice)
Finish(bootstrap): installing dnf5 tooling
Start(bootstrap): creating root cache
Finish(bootstrap): creating root cache
Finish(bootstrap): chroot init
Start: chroot init
INFO: mounting tmpfs at /var/lib/mock/fedora-40-x86_64-1710336054.221965/root.
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled package manager cache
Start: cleaning package manager metadata
Finish: cleaning package manager metadata
INFO: enabled HW Info plugin
INFO: Package manager dnf5 detected and used (direct choice)
INFO: Buildroot is handled by package management downloaded with a bootstrap image:
  rpm-4.19.1.1-1.fc40.x86_64
  rpm-sequoia-1.6.0-2.fc40.x86_64
  python3-dnf-4.19.0-1.fc40.noarch
  yum-4.19.0-1.fc40.noarch
  dnf5-5.1.12-1.fc40.x86_64
  dnf5-plugins-5.1.12-1.fc40.x86_64
Start: installing minimal buildroot with dnf5
Updating and loading repositories:
 updates                                100% |   1.0 MiB/s |  23.8 KiB |  00m00s
 fedora                                 100% | 871.3 KiB/s |  20.9 KiB |  00m00s
 Copr repository                        100% |  51.3 KiB/s |   1.5 KiB |  00m00s
 Copr repository                        100% |  37.9 MiB/s |  41.3 MiB |  00m01s
Repositories loaded.
Package                           Arch   Version                    Repository      Size
Installing group/module packages:                                                       
 bash                             x86_64 5.2.26-3.fc40              fedora       8.1 MiB
 bzip2                            x86_64 1.0.8-18.fc40              fedora      91.7 KiB
 coreutils                        x86_64 9.4-6.fc40                 fedora       5.8 MiB
 cpio                             x86_64 2.15-1.fc40                fedora       1.1 MiB
 diffutils                        x86_64 3.10-5.fc40                fedora       1.6 MiB
 fedora-release-common            noarch 40-0.36                    fedora      19.0 KiB
 findutils                        x86_64 1:4.9.0-8.fc40             fedora       1.5 MiB
 gawk                             x86_64 5.3.0-3.fc40               fedora       1.7 MiB
 glibc-minimal-langpack           x86_64 2.39-2.fc40                fedora       0.0   B
 grep                             x86_64 3.11-7.fc40                fedora       1.0 MiB
 gzip                             x86_64 1.13-1.fc40                fedora     385.0 KiB
 info                             x86_64 7.1-2.fc40                 fedora     357.8 KiB
 patch                            x86_64 2.7.6-24.fc40              fedora     262.8 KiB
 redhat-rpm-config                noarch 285-1.fc40                 fedora     185.1 KiB
 rpm-build                        x86_64 4.19.1.1-1.fc40            fedora     173.7 KiB
 sed                              x86_64 4.9-1.fc40                 fedora     861.5 KiB
 shadow-utils                     x86_64 2:4.15.0rc2-1.fc40         fedora       4.1 MiB
 tar                              x86_64 2:1.35-3.fc40              fedora       2.9 MiB
 unzip                            x86_64 6.0-63.fc40                fedora     382.8 KiB
 util-linux                       x86_64 2.40-0.9.rc1.fc40          fedora       3.7 MiB
 which                            x86_64 2.21-41.fc40               fedora      80.2 KiB
 xz                               x86_64 5.4.6-1.fc40               fedora       2.0 MiB
Installing dependencies:                                                                
 alternatives                     x86_64 1.26-3.fc40                fedora      62.3 KiB
 ansible-srpm-macros              noarch 1-14.fc40                  fedora      35.7 KiB
 audit-libs                       x86_64 4.0-8.fc40                 fedora     311.3 KiB
 authselect                       x86_64 1.5.0-5.fc40               fedora     153.6 KiB
 authselect-libs                  x86_64 1.5.0-5.fc40               fedora     818.3 KiB
 basesystem                       noarch 11-20.fc40                 fedora       0.0   B
 binutils                         x86_64 2.41-34.fc40               fedora      26.4 MiB
 binutils-gold                    x86_64 2.41-34.fc40               fedora       2.0 MiB
 bzip2-libs                       x86_64 1.0.8-18.fc40              fedora      80.7 KiB
 ca-certificates                  noarch 2023.2.62_v7.0.401-6.fc40  fedora       2.3 MiB
 coreutils-common                 x86_64 9.4-6.fc40                 fedora      11.4 MiB
 cracklib                         x86_64 2.9.11-5.fc40              fedora     238.9 KiB
 crypto-policies                  noarch 20240201-2.git9f501f3.fc40 fedora     149.3 KiB
 curl                             x86_64 8.6.0-7.fc40               fedora     734.6 KiB
 cyrus-sasl-lib                   x86_64 2.1.28-19.fc40             fedora       2.3 MiB
 debugedit                        x86_64 5.0-14.fc40                fedora     199.0 KiB
 dwz                              x86_64 0.15-6.fc40                fedora     290.9 KiB
 ed                               x86_64 1.20.1-1.fc40              fedora     146.5 KiB
 efi-srpm-macros                  noarch 5-11.fc40                  fedora      40.1 KiB
 elfutils                         x86_64 0.190-6.fc40               fedora       2.5 MiB
 elfutils-debuginfod-client       x86_64 0.190-6.fc40               fedora      64.9 KiB
 elfutils-default-yama-scope      noarch 0.190-6.fc40               fedora       1.8 KiB
 elfutils-libelf                  x86_64 0.190-6.fc40               fedora       1.0 MiB
 elfutils-libs                    x86_64 0.190-6.fc40               fedora     642.1 KiB
 fedora-gpg-keys                  noarch 40-0.4                     fedora     125.0 KiB
 fedora-release                   noarch 40-0.36                    fedora       0.0   B
 fedora-release-identity-basic    noarch 40-0.36                    fedora     676.0   B
 fedora-repos                     noarch 40-0.4                     fedora       4.9 KiB
 file                             x86_64 5.45-4.fc40                fedora     103.5 KiB
 file-libs                        x86_64 5.45-4.fc40                fedora       9.9 MiB
 filesystem                       x86_64 3.18-8.fc40                fedora     106.0   B
 fonts-srpm-macros                noarch 1:2.0.5-14.fc40            fedora      55.3 KiB
 forge-srpm-macros                noarch 0.2.0-3.fc40               fedora      37.4 KiB
 fpc-srpm-macros                  noarch 1.3-12.fc40                fedora     144.0   B
 gdb-minimal                      x86_64 14.1-8.fc40                fedora      12.3 MiB
 gdbm                             x86_64 1:1.23-6.fc40              fedora     460.9 KiB
 gdbm-libs                        x86_64 1:1.23-6.fc40              fedora     121.9 KiB
 ghc-srpm-macros                  noarch 1.6.1-5.fc40               fedora     369.0   B
 glibc                            x86_64 2.39-2.fc40                fedora       6.7 MiB
 glibc-common                     x86_64 2.39-2.fc40                fedora       1.0 MiB
 glibc-gconv-extra                x86_64 2.39-2.fc40                fedora       7.8 MiB
 gmp                              x86_64 1:6.2.1-8.fc40             fedora     794.6 KiB
 gnat-srpm-macros                 noarch 6-5.fc40                   fedora       1.0 KiB
 go-srpm-macros                   noarch 3.4.0-2.fc40               fedora      60.6 KiB
 jansson                          x86_64 2.13.1-9.fc40              fedora      88.3 KiB
 kernel-srpm-macros               noarch 1.0-22.fc40                fedora       1.9 KiB
 keyutils-libs                    x86_64 1.6.3-3.fc40               fedora      54.4 KiB
 krb5-libs                        x86_64 1.21.2-5.fc40              fedora       2.3 MiB
 libacl                           x86_64 2.3.2-1.fc40               fedora      40.0 KiB
 libarchive                       x86_64 3.7.2-3.fc40               fedora     914.6 KiB
 libattr                          x86_64 2.5.2-3.fc40               fedora      28.5 KiB
 libblkid                         x86_64 2.40-0.9.rc1.fc40          fedora     237.0 KiB
 libbrotli                        x86_64 1.1.0-3.fc40               fedora     829.5 KiB
 libcap                           x86_64 2.69-3.fc40                fedora     217.2 KiB
 libcap-ng                        x86_64 0.8.4-4.fc40               fedora      73.1 KiB
 libcom_err                       x86_64 1.47.0-5.fc40              fedora      67.2 KiB
 libcurl                          x86_64 8.6.0-7.fc40               fedora     772.8 KiB
 libeconf                         x86_64 0.5.2-3.fc40               fedora      52.0 KiB
 libevent                         x86_64 2.1.12-12.fc40             fedora     895.6 KiB
 libfdisk                         x86_64 2.40-0.9.rc1.fc40          fedora     363.3 KiB
 libffi                           x86_64 3.4.4-7.fc40               fedora      81.6 KiB
 libgcc                           x86_64 14.0.1-0.7.fc40            fedora     270.6 KiB
 libgomp                          x86_64 14.0.1-0.7.fc40            fedora     518.0 KiB
 libidn2                          x86_64 2.3.7-1.fc40               fedora     329.1 KiB
 libmount                         x86_64 2.40-0.9.rc1.fc40          fedora     352.1 KiB
 libnghttp2                       x86_64 1.59.0-2.fc40              fedora     166.1 KiB
 libnsl2                          x86_64 2.0.1-1.fc40               fedora      57.9 KiB
 libpkgconf                       x86_64 2.1.0-1.fc40               fedora      74.2 KiB
 libpsl                           x86_64 0.21.5-3.fc40              fedora      80.5 KiB
 libpwquality                     x86_64 1.4.5-9.fc40               fedora     417.8 KiB
 libselinux                       x86_64 3.6-4.fc40                 fedora     173.0 KiB
 libsemanage                      x86_64 3.6-3.fc40                 fedora     293.5 KiB
 libsepol                         x86_64 3.6-3.fc40                 fedora     802.0 KiB
 libsmartcols                     x86_64 2.40-0.9.rc1.fc40          fedora     180.7 KiB
 libssh                           x86_64 0.10.6-4.fc40              fedora     509.3 KiB
 libssh-config                    noarch 0.10.6-4.fc40              fedora     277.0   B
 libstdc++                        x86_64 14.0.1-0.7.fc40            fedora       2.8 MiB
 libtasn1                         x86_64 4.19.0-6.fc40              fedora     175.7 KiB
 libtirpc                         x86_64 1.3.4-1.rc2.fc40.2         fedora     202.8 KiB
 libtool-ltdl                     x86_64 2.4.7-10.fc40              fedora      66.2 KiB
 libunistring                     x86_64 1.1-7.fc40                 fedora       1.7 MiB
 libutempter                      x86_64 1.2.1-13.fc40              fedora      57.7 KiB
 libuuid                          x86_64 2.40-0.9.rc1.fc40          fedora      37.6 KiB
 libverto                         x86_64 0.3.2-8.fc40               fedora      29.5 KiB
 libxcrypt                        x86_64 4.4.36-5.fc40              fedora     262.8 KiB
 libxml2                          x86_64 2.12.5-1.fc40              fedora       1.7 MiB
 libzstd                          x86_64 1.5.5-5.fc40               fedora     772.0 KiB
 lua-libs                         x86_64 5.4.6-5.fc40               fedora     281.1 KiB
 lua-srpm-macros                  noarch 1-13.fc40                  fedora       1.3 KiB
 lz4-libs                         x86_64 1.9.4-6.fc40               fedora     129.4 KiB
 mpfr                             x86_64 4.2.1-3.fc40               fedora     832.0 KiB
 ncurses-base                     noarch 6.4-12.20240127.fc40       fedora     326.2 KiB
 ncurses-libs                     x86_64 6.4-12.20240127.fc40       fedora     963.2 KiB
 ocaml-srpm-macros                noarch 9-3.fc40                   fedora       1.9 KiB
 openblas-srpm-macros             noarch 2-16.fc40                  fedora     104.0   B
 openldap                         x86_64 2.6.7-1.fc40               fedora     635.1 KiB
 openssl-libs                     x86_64 1:3.2.1-2.fc40             fedora       7.8 MiB
 p11-kit                          x86_64 0.25.3-4.fc40              fedora       2.2 MiB
 p11-kit-trust                    x86_64 0.25.3-4.fc40              fedora     391.4 KiB
 package-notes-srpm-macros        noarch 0.5-11.fc40                fedora       1.6 KiB
 pam                              x86_64 1.6.0-2.fc40               fedora       1.8 MiB
 pam-libs                         x86_64 1.6.0-2.fc40               fedora     135.0 KiB
 pcre2                            x86_64 10.42-2.fc40.2             fedora     637.6 KiB
 pcre2-syntax                     noarch 10.42-2.fc40.2             fedora     235.1 KiB
 perl-srpm-macros                 noarch 1-53.fc40                  fedora     861.0   B
 pkgconf                          x86_64 2.1.0-1.fc40               fedora      82.4 KiB
 pkgconf-m4                       noarch 2.1.0-1.fc40               fedora      13.9 KiB
 pkgconf-pkg-config               x86_64 2.1.0-1.fc40               fedora     989.0   B
 popt                             x86_64 1.19-6.fc40                fedora     136.9 KiB
 publicsuffix-list-dafsa          noarch 20240107-3.fc40            fedora      67.5 KiB
 pyproject-srpm-macros            noarch 1.12.0-1.fc40              fedora       1.5 KiB
 python-srpm-macros               noarch 3.12-7.fc40                fedora      50.1 KiB
 qt5-srpm-macros                  noarch 5.15.12-3.fc40             fedora     492.0   B
 qt6-srpm-macros                  noarch 6.6.2-1.fc40               fedora     456.0   B
 readline                         x86_64 8.2-8.fc40                 fedora     489.2 KiB
 rpm                              x86_64 4.19.1.1-1.fc40            fedora       3.0 MiB
 rpm-build-libs                   x86_64 4.19.1.1-1.fc40            fedora     198.4 KiB
 rpm-libs                         x86_64 4.19.1.1-1.fc40            fedora     709.9 KiB
 rpm-sequoia                      x86_64 1.6.0-2.fc40               fedora       2.2 MiB
 rust-srpm-macros                 noarch 26.1-1.fc40                fedora       4.8 KiB
 setup                            noarch 2.14.5-2.fc40              fedora     720.4 KiB
 sqlite-libs                      x86_64 3.45.1-2.fc40              fedora       1.4 MiB
 systemd-libs                     x86_64 255.3-1.fc40               fedora       1.9 MiB
 util-linux-core                  x86_64 2.40-0.9.rc1.fc40          fedora       1.4 MiB
 xxhash-libs                      x86_64 0.8.2-2.fc40               fedora      88.5 KiB
 xz-libs                          x86_64 5.4.6-1.fc40               fedora     209.8 KiB
 zig-srpm-macros                  noarch 1-2.fc40                   fedora       1.1 KiB
 zip                              x86_64 3.0-40.fc40                fedora     703.2 KiB
 zlib-ng-compat                   x86_64 2.1.6-2.fc40               fedora     134.0 KiB
 zstd                             x86_64 1.5.5-5.fc40               fedora       1.6 MiB
Installing groups:                                                                      
 Buildsystem building group                                                             

Transaction Summary:
 Installing:      152 packages

Total size of inbound packages is 53 MiB. Need to download 0 B.
After this operation 177 MiB will be used (install 177 MiB, remove 0 B).
[  1/152] tar-2:1.35-3.fc40.x86_64      100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[  2/152] bzip2-0:1.0.8-18.fc40.x86_64  100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[  3/152] redhat-rpm-config-0:285-1.fc4 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[  4/152] rpm-build-0:4.19.1.1-1.fc40.x 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[  5/152] unzip-0:6.0-63.fc40.x86_64    100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[  6/152] cpio-0:2.15-1.fc40.x86_64     100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[  7/152] which-0:2.21-41.fc40.x86_64   100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[  8/152] bash-0:5.2.26-3.fc40.x86_64   100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[  9/152] coreutils-0:9.4-6.fc40.x86_64 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 10/152] grep-0:3.11-7.fc40.x86_64     100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 11/152] patch-0:2.7.6-24.fc40.x86_64  100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 12/152] sed-0:4.9-1.fc40.x86_64       100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 13/152] shadow-utils-2:4.15.0rc2-1.fc 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 14/152] diffutils-0:3.10-5.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 15/152] fedora-release-common-0:40-0. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 16/152] findutils-1:4.9.0-8.fc40.x86_ 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 17/152] glibc-minimal-langpack-0:2.39 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 18/152] gzip-0:1.13-1.fc40.x86_64     100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 19/152] info-0:7.1-2.fc40.x86_64      100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 20/152] xz-0:5.4.6-1.fc40.x86_64      100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 21/152] util-linux-0:2.40-0.9.rc1.fc4 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 22/152] gawk-0:5.3.0-3.fc40.x86_64    100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 23/152] glibc-0:2.39-2.fc40.x86_64    100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 24/152] libacl-0:2.3.2-1.fc40.x86_64  100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 25/152] libselinux-0:3.6-4.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 26/152] bzip2-libs-0:1.0.8-18.fc40.x8 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 27/152] ansible-srpm-macros-0:1-14.fc 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 28/152] dwz-0:0.15-6.fc40.x86_64      100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 29/152] efi-srpm-macros-0:5-11.fc40.n 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 30/152] file-0:5.45-4.fc40.x86_64     100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 31/152] fonts-srpm-macros-1:2.0.5-14. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 32/152] forge-srpm-macros-0:0.2.0-3.f 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 33/152] fpc-srpm-macros-0:1.3-12.fc40 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 34/152] ghc-srpm-macros-0:1.6.1-5.fc4 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 35/152] gnat-srpm-macros-0:6-5.fc40.n 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 36/152] go-srpm-macros-0:3.4.0-2.fc40 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 37/152] kernel-srpm-macros-0:1.0-22.f 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 38/152] lua-srpm-macros-0:1-13.fc40.n 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 39/152] ocaml-srpm-macros-0:9-3.fc40. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 40/152] openblas-srpm-macros-0:2-16.f 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 41/152] package-notes-srpm-macros-0:0 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 42/152] perl-srpm-macros-0:1-53.fc40. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 43/152] pyproject-srpm-macros-0:1.12. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 44/152] python-srpm-macros-0:3.12-7.f 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 45/152] qt5-srpm-macros-0:5.15.12-3.f 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 46/152] qt6-srpm-macros-0:6.6.2-1.fc4 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 47/152] rpm-0:4.19.1.1-1.fc40.x86_64  100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 48/152] rust-srpm-macros-0:26.1-1.fc4 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 49/152] zig-srpm-macros-0:1-2.fc40.no 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 50/152] zip-0:3.0-40.fc40.x86_64      100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 51/152] debugedit-0:5.0-14.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 52/152] elfutils-0:0.190-6.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 53/152] elfutils-libelf-0:0.190-6.fc4 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 54/152] popt-0:1.19-6.fc40.x86_64     100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 55/152] readline-0:8.2-8.fc40.x86_64  100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 56/152] rpm-build-libs-0:4.19.1.1-1.f 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 57/152] rpm-libs-0:4.19.1.1-1.fc40.x8 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 58/152] zstd-0:1.5.5-5.fc40.x86_64    100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 59/152] filesystem-0:3.18-8.fc40.x86_ 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 60/152] ncurses-libs-0:6.4-12.2024012 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 61/152] coreutils-common-0:9.4-6.fc40 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 62/152] gmp-1:6.2.1-8.fc40.x86_64     100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 63/152] libattr-0:2.5.2-3.fc40.x86_64 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 64/152] libcap-0:2.69-3.fc40.x86_64   100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 65/152] openssl-libs-1:3.2.1-2.fc40.x 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 66/152] pcre2-0:10.42-2.fc40.2.x86_64 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 67/152] ed-0:1.20.1-1.fc40.x86_64     100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 68/152] audit-libs-0:4.0-8.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 69/152] libeconf-0:0.5.2-3.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 70/152] libsemanage-0:3.6-3.fc40.x86_ 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 71/152] libxcrypt-0:4.4.36-5.fc40.x86 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 72/152] pam-libs-0:1.6.0-2.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 73/152] setup-0:2.14.5-2.fc40.noarch  100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 74/152] fedora-repos-0:40-0.4.noarch  100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 75/152] glibc-common-0:2.39-2.fc40.x8 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 76/152] xz-libs-0:5.4.6-1.fc40.x86_64 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 77/152] libblkid-0:2.40-0.9.rc1.fc40. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 78/152] libcap-ng-0:0.8.4-4.fc40.x86_ 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 79/152] libfdisk-0:2.40-0.9.rc1.fc40. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 80/152] libmount-0:2.40-0.9.rc1.fc40. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 81/152] libsmartcols-0:2.40-0.9.rc1.f 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 82/152] libutempter-0:1.2.1-13.fc40.x 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 83/152] libuuid-0:2.40-0.9.rc1.fc40.x 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 84/152] systemd-libs-0:255.3-1.fc40.x 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 85/152] util-linux-core-0:2.40-0.9.rc 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 86/152] zlib-ng-compat-0:2.1.6-2.fc40 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 87/152] mpfr-0:4.2.1-3.fc40.x86_64    100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 88/152] glibc-gconv-extra-0:2.39-2.fc 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 89/152] basesystem-0:11-20.fc40.noarc 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 90/152] libgcc-0:14.0.1-0.7.fc40.x86_ 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 91/152] libsepol-0:3.6-3.fc40.x86_64  100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 92/152] file-libs-0:5.45-4.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 93/152] curl-0:8.6.0-7.fc40.x86_64    100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 94/152] libarchive-0:3.7.2-3.fc40.x86 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 95/152] elfutils-libs-0:0.190-6.fc40. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 96/152] libstdc++-0:14.0.1-0.7.fc40.x 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 97/152] libzstd-0:1.5.5-5.fc40.x86_64 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 98/152] libgomp-0:14.0.1-0.7.fc40.x86 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 99/152] lua-libs-0:5.4.6-5.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[100/152] rpm-sequoia-0:1.6.0-2.fc40.x8 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[101/152] sqlite-libs-0:3.45.1-2.fc40.x 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[102/152] lz4-libs-0:1.9.4-6.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[103/152] ncurses-base-0:6.4-12.2024012 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[104/152] ca-certificates-0:2023.2.62_v 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[105/152] crypto-policies-0:20240201-2. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[106/152] pcre2-syntax-0:10.42-2.fc40.2 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[107/152] fedora-gpg-keys-0:40-0.4.noar 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[108/152] libxml2-0:2.12.5-1.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[109/152] elfutils-default-yama-scope-0 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[110/152] authselect-libs-0:1.5.0-5.fc4 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[111/152] pam-0:1.6.0-2.fc40.x86_64     100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[112/152] authselect-0:1.5.0-5.fc40.x86 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[113/152] gdbm-libs-1:1.23-6.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[114/152] libnsl2-0:2.0.1-1.fc40.x86_64 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[115/152] libpwquality-0:1.4.5-9.fc40.x 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[116/152] libtirpc-0:1.3.4-1.rc2.fc40.2 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[117/152] cracklib-0:2.9.11-5.fc40.x86_ 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[118/152] krb5-libs-0:1.21.2-5.fc40.x86 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[119/152] libcom_err-0:1.47.0-5.fc40.x8 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[120/152] keyutils-libs-0:1.6.3-3.fc40. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[121/152] libverto-0:0.3.2-8.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[122/152] binutils-0:2.41-34.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[123/152] alternatives-0:1.26-3.fc40.x8 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[124/152] binutils-gold-0:2.41-34.fc40. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[125/152] elfutils-debuginfod-client-0: 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[126/152] jansson-0:2.13.1-9.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[127/152] pkgconf-pkg-config-0:2.1.0-1. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[128/152] pkgconf-0:2.1.0-1.fc40.x86_64 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[129/152] pkgconf-m4-0:2.1.0-1.fc40.noa 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[130/152] libpkgconf-0:2.1.0-1.fc40.x86 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[131/152] gdbm-1:1.23-6.fc40.x86_64     100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[132/152] p11-kit-0:0.25.3-4.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[133/152] libffi-0:3.4.4-7.fc40.x86_64  100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[134/152] libtasn1-0:4.19.0-6.fc40.x86_ 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[135/152] p11-kit-trust-0:0.25.3-4.fc40 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[136/152] fedora-release-0:40-0.36.noar 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[137/152] gdb-minimal-0:14.1-8.fc40.x86 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[138/152] xxhash-libs-0:0.8.2-2.fc40.x8 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[139/152] fedora-release-identity-basic 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[140/152] libcurl-0:8.6.0-7.fc40.x86_64 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[141/152] libbrotli-0:1.1.0-3.fc40.x86_ 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[142/152] libidn2-0:2.3.7-1.fc40.x86_64 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[143/152] libnghttp2-0:1.59.0-2.fc40.x8 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[144/152] libpsl-0:0.21.5-3.fc40.x86_64 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[145/152] libssh-0:0.10.6-4.fc40.x86_64 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[146/152] openldap-0:2.6.7-1.fc40.x86_6 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[147/152] libunistring-0:1.1-7.fc40.x86 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[148/152] publicsuffix-list-dafsa-0:202 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[149/152] libssh-config-0:0.10.6-4.fc40 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[150/152] cyrus-sasl-lib-0:2.1.28-19.fc 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[151/152] libevent-0:2.1.12-12.fc40.x86 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[152/152] libtool-ltdl-0:2.4.7-10.fc40. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
--------------------------------------------------------------------------------
[152/152] Total                         100% |   0.0   B/s |   0.0   B |  00m00s
Running transaction
Importing PGP key 0xA15B79CC:
 Userid     : "Fedora (40) <fedora-40-primary@fedoraproject.org>"
 Fingerprint: 115DF9AEF857853EE8445D0A0727707EA15B79CC
 From       : file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-40-primary
The key was successfully imported.
[  1/154] Verify package files          100% | 571.0   B/s | 152.0   B |  00m00s
>>> Running pre-transaction scriptlet: filesystem-0:3.18-8.fc40.x86_64
>>> Stop pre-transaction scriptlet: filesystem-0:3.18-8.fc40.x86_64
[  2/154] Prepare transaction           100% |   1.9 KiB/s | 152.0   B |  00m00s
[  3/154] Installing libgcc-0:14.0.1-0. 100% | 133.0 MiB/s | 272.3 KiB |  00m00s
>>> Running post-install scriptlet: libgcc-0:14.0.1-0.7.fc40.x86_64
>>> Stop post-install scriptlet: libgcc-0:14.0.1-0.7.fc40.x86_64
[  4/154] Installing crypto-policies-0: 100% |  17.7 MiB/s | 181.7 KiB |  00m00s
>>> Running post-install scriptlet: crypto-policies-0:20240201-2.git9f501f3.fc40
>>> Stop post-install scriptlet: crypto-policies-0:20240201-2.git9f501f3.fc40.no
[  5/154] Installing fedora-release-ide 100% | 910.2 KiB/s | 932.0   B |  00m00s
[  6/154] Installing fedora-gpg-keys-0: 100% |  20.8 MiB/s | 170.1 KiB |  00m00s
[  7/154] Installing fedora-repos-0:40- 100% |   0.0   B/s |   5.7 KiB |  00m00s
[  8/154] Installing fedora-release-com 100% |  11.3 MiB/s |  23.2 KiB |  00m00s
[  9/154] Installing fedora-release-0:4 100% |   0.0   B/s | 124.0   B |  00m00s
[ 10/154] Installing setup-0:2.14.5-2.f 100% |  47.3 MiB/s | 725.8 KiB |  00m00s
>>> Running post-install scriptlet: setup-0:2.14.5-2.fc40.noarch
>>> Stop post-install scriptlet: setup-0:2.14.5-2.fc40.noarch
[ 11/154] Installing filesystem-0:3.18- 100% |   1.7 MiB/s | 212.4 KiB |  00m00s
[ 12/154] Installing basesystem-0:11-20 100% |   0.0   B/s | 124.0   B |  00m00s
[ 13/154] Installing libssh-config-0:0. 100% |   0.0   B/s | 816.0   B |  00m00s
[ 14/154] Installing publicsuffix-list- 100% |  66.7 MiB/s |  68.3 KiB |  00m00s
[ 15/154] Installing pkgconf-m4-0:2.1.0 100% |   0.0   B/s |  14.3 KiB |  00m00s
[ 16/154] Installing pcre2-syntax-0:10. 100% | 116.0 MiB/s | 237.6 KiB |  00m00s
[ 17/154] Installing ncurses-base-0:6.4 100% |  38.2 MiB/s | 351.6 KiB |  00m00s
[ 18/154] Installing glibc-minimal-lang 100% |   0.0   B/s | 124.0   B |  00m00s
[ 19/154] Installing ncurses-libs-0:6.4 100% | 157.8 MiB/s | 969.7 KiB |  00m00s
>>> Running pre-install scriptlet: glibc-0:2.39-2.fc40.x86_64
>>> Stop pre-install scriptlet: glibc-0:2.39-2.fc40.x86_64
[ 20/154] Installing glibc-0:2.39-2.fc4 100% | 114.3 MiB/s |   6.7 MiB |  00m00s
>>> Running post-install scriptlet: glibc-0:2.39-2.fc40.x86_64
>>> Stop post-install scriptlet: glibc-0:2.39-2.fc40.x86_64
[ 21/154] Installing bash-0:5.2.26-3.fc 100% | 263.3 MiB/s |   8.2 MiB |  00m00s
>>> Running post-install scriptlet: bash-0:5.2.26-3.fc40.x86_64
>>> Stop post-install scriptlet: bash-0:5.2.26-3.fc40.x86_64
[ 22/154] Installing glibc-common-0:2.3 100% | 127.6 MiB/s |   1.0 MiB |  00m00s
[ 23/154] Installing glibc-gconv-extra- 100% | 122.8 MiB/s |   7.9 MiB |  00m00s
>>> Running post-install scriptlet: glibc-gconv-extra-0:2.39-2.fc40.x86_64
>>> Stop post-install scriptlet: glibc-gconv-extra-0:2.39-2.fc40.x86_64
[ 24/154] Installing zlib-ng-compat-0:2 100% | 131.7 MiB/s | 134.8 KiB |  00m00s
[ 25/154] Installing xz-libs-0:5.4.6-1. 100% | 206.0 MiB/s | 210.9 KiB |  00m00s
[ 26/154] Installing bzip2-libs-0:1.0.8 100% |  79.9 MiB/s |  81.8 KiB |  00m00s
[ 27/154] Installing popt-0:1.19-6.fc40 100% |  35.0 MiB/s | 143.5 KiB |  00m00s
[ 28/154] Installing readline-0:8.2-8.f 100% | 160.0 MiB/s | 491.4 KiB |  00m00s
[ 29/154] Installing libuuid-0:2.40-0.9 100% |  37.8 MiB/s |  38.7 KiB |  00m00s
[ 30/154] Installing libstdc++-0:14.0.1 100% | 251.1 MiB/s |   2.8 MiB |  00m00s
[ 31/154] Installing libzstd-0:1.5.5-5. 100% | 251.7 MiB/s | 773.2 KiB |  00m00s
[ 32/154] Installing elfutils-libelf-0: 100% | 246.4 MiB/s |   1.0 MiB |  00m00s
[ 33/154] Installing libblkid-0:2.40-0. 100% | 232.4 MiB/s | 237.9 KiB |  00m00s
[ 34/154] Installing gmp-1:6.2.1-8.fc40 100% | 259.4 MiB/s | 796.8 KiB |  00m00s
[ 35/154] Installing libattr-0:2.5.2-3. 100% |  28.8 MiB/s |  29.5 KiB |  00m00s
[ 36/154] Installing libacl-0:2.3.2-1.f 100% |  39.9 MiB/s |  40.8 KiB |  00m00s
[ 37/154] Installing libxcrypt-0:4.4.36 100% | 129.7 MiB/s | 265.5 KiB |  00m00s
[ 38/154] Installing libeconf-0:0.5.2-3 100% |  52.4 MiB/s |  53.7 KiB |  00m00s
[ 39/154] Installing lz4-libs-0:1.9.4-6 100% | 127.4 MiB/s | 130.5 KiB |  00m00s
[ 40/154] Installing gdbm-libs-1:1.23-6 100% | 120.7 MiB/s | 123.6 KiB |  00m00s
[ 41/154] Installing mpfr-0:4.2.1-3.fc4 100% | 203.5 MiB/s | 833.5 KiB |  00m00s
[ 42/154] Installing gawk-0:5.3.0-3.fc4 100% | 172.8 MiB/s |   1.7 MiB |  00m00s
[ 43/154] Installing dwz-0:0.15-6.fc40. 100% | 142.7 MiB/s | 292.3 KiB |  00m00s
[ 44/154] Installing unzip-0:6.0-63.fc4 100% | 125.8 MiB/s | 386.3 KiB |  00m00s
[ 45/154] Installing file-libs-0:5.45-4 100% | 472.9 MiB/s |   9.9 MiB |  00m00s
[ 46/154] Installing file-0:5.45-4.fc40 100% | 102.6 MiB/s | 105.0 KiB |  00m00s
[ 47/154] Installing pcre2-0:10.42-2.fc 100% | 208.0 MiB/s | 639.1 KiB |  00m00s
[ 48/154] Installing grep-0:3.11-7.fc40 100% | 111.5 MiB/s |   1.0 MiB |  00m00s
[ 49/154] Installing xz-0:5.4.6-1.fc40. 100% | 143.0 MiB/s |   2.0 MiB |  00m00s
[ 50/154] Installing libcap-ng-0:0.8.4- 100% |  73.2 MiB/s |  75.0 KiB |  00m00s
[ 51/154] Installing audit-libs-0:4.0-8 100% | 153.0 MiB/s | 313.4 KiB |  00m00s
[ 52/154] Installing pam-libs-0:1.6.0-2 100% |  67.1 MiB/s | 137.4 KiB |  00m00s
[ 53/154] Installing libcap-0:2.69-3.fc 100% |  72.2 MiB/s | 221.9 KiB |  00m00s
[ 54/154] Installing systemd-libs-0:255 100% | 241.3 MiB/s |   1.9 MiB |  00m00s
[ 55/154] Installing libsmartcols-0:2.4 100% | 177.8 MiB/s | 182.0 KiB |  00m00s
[ 56/154] Installing libsepol-0:3.6-3.f 100% | 261.4 MiB/s | 803.0 KiB |  00m00s
[ 57/154] Installing libselinux-0:3.6-4 100% |  85.1 MiB/s | 174.3 KiB |  00m00s
[ 58/154] Installing sed-0:4.9-1.fc40.x 100% | 121.3 MiB/s | 869.7 KiB |  00m00s
[ 59/154] Installing findutils-1:4.9.0- 100% | 162.9 MiB/s |   1.5 MiB |  00m00s
[ 60/154] Installing libmount-0:2.40-0. 100% | 172.5 MiB/s | 353.3 KiB |  00m00s
[ 61/154] Installing lua-libs-0:5.4.6-5 100% | 137.8 MiB/s | 282.3 KiB |  00m00s
[ 62/154] Installing libcom_err-0:1.47. 100% |  66.7 MiB/s |  68.3 KiB |  00m00s
[ 63/154] Installing alternatives-0:1.2 100% |  62.5 MiB/s |  64.0 KiB |  00m00s
[ 64/154] Installing jansson-0:2.13.1-9 100% |  87.6 MiB/s |  89.7 KiB |  00m00s
[ 65/154] Installing libtasn1-0:4.19.0- 100% | 173.3 MiB/s | 177.5 KiB |  00m00s
[ 66/154] Installing libunistring-0:1.1 100% | 247.2 MiB/s |   1.7 MiB |  00m00s
[ 67/154] Installing libidn2-0:2.3.7-1. 100% |  81.8 MiB/s | 335.0 KiB |  00m00s
[ 68/154] Installing libpsl-0:0.21.5-3. 100% |  79.7 MiB/s |  81.6 KiB |  00m00s
[ 69/154] Installing util-linux-core-0: 100% | 126.0 MiB/s |   1.4 MiB |  00m00s
[ 70/154] Installing tar-2:1.35-3.fc40. 100% | 227.0 MiB/s |   3.0 MiB |  00m00s
[ 71/154] Installing libsemanage-0:3.6- 100% |  96.1 MiB/s | 295.3 KiB |  00m00s
[ 72/154] Installing shadow-utils-2:4.1 100% |  73.3 MiB/s |   4.2 MiB |  00m00s
>>> Running pre-install scriptlet: libutempter-0:1.2.1-13.fc40.x86_64
>>> Stop pre-install scriptlet: libutempter-0:1.2.1-13.fc40.x86_64
[ 73/154] Installing libutempter-0:1.2. 100% |  29.2 MiB/s |  59.7 KiB |  00m00s
[ 74/154] Installing zip-0:3.0-40.fc40. 100% | 172.6 MiB/s | 707.1 KiB |  00m00s
[ 75/154] Installing gdbm-1:1.23-6.fc40 100% | 113.7 MiB/s | 465.8 KiB |  00m00s
[ 76/154] Installing cyrus-sasl-lib-0:2 100% | 228.3 MiB/s |   2.3 MiB |  00m00s
[ 77/154] Installing zstd-0:1.5.5-5.fc4 100% | 274.4 MiB/s |   1.6 MiB |  00m00s
[ 78/154] Installing libfdisk-0:2.40-0. 100% | 177.9 MiB/s | 364.4 KiB |  00m00s
[ 79/154] Installing bzip2-0:1.0.8-18.f 100% |  47.0 MiB/s |  96.2 KiB |  00m00s
[ 80/154] Installing libxml2-0:2.12.5-1 100% | 242.8 MiB/s |   1.7 MiB |  00m00s
[ 81/154] Installing sqlite-libs-0:3.45 100% | 280.3 MiB/s |   1.4 MiB |  00m00s
[ 82/154] Installing ed-0:1.20.1-1.fc40 100% |  72.6 MiB/s | 148.8 KiB |  00m00s
[ 83/154] Installing patch-0:2.7.6-24.f 100% | 129.0 MiB/s | 264.3 KiB |  00m00s
[ 84/154] Installing elfutils-default-y 100% | 136.2 KiB/s |   2.0 KiB |  00m00s
>>> Running post-install scriptlet: elfutils-default-yama-scope-0:0.190-6.fc40.n
>>> Stop post-install scriptlet: elfutils-default-yama-scope-0:0.190-6.fc40.noar
[ 85/154] Installing cpio-0:2.15-1.fc40 100% | 137.5 MiB/s |   1.1 MiB |  00m00s
[ 86/154] Installing diffutils-0:3.10-5 100% | 176.2 MiB/s |   1.6 MiB |  00m00s
[ 87/154] Installing libgomp-0:14.0.1-0 100% | 253.6 MiB/s | 519.4 KiB |  00m00s
[ 88/154] Installing keyutils-libs-0:1. 100% |  54.5 MiB/s |  55.8 KiB |  00m00s
[ 89/154] Installing libverto-0:0.3.2-8 100% |  30.5 MiB/s |  31.3 KiB |  00m00s
[ 90/154] Installing libpkgconf-0:2.1.0 100% |  73.6 MiB/s |  75.3 KiB |  00m00s
[ 91/154] Installing pkgconf-0:2.1.0-1. 100% |  41.5 MiB/s |  84.9 KiB |  00m00s
[ 92/154] Installing pkgconf-pkg-config 100% |   1.7 MiB/s |   1.8 KiB |  00m00s
[ 93/154] Installing libffi-0:3.4.4-7.f 100% |  81.0 MiB/s |  83.0 KiB |  00m00s
[ 94/154] Installing p11-kit-0:0.25.3-4 100% | 146.3 MiB/s |   2.2 MiB |  00m00s
[ 95/154] Installing p11-kit-trust-0:0. 100% |  20.2 MiB/s | 393.1 KiB |  00m00s
>>> Running post-install scriptlet: p11-kit-trust-0:0.25.3-4.fc40.x86_64
>>> Stop post-install scriptlet: p11-kit-trust-0:0.25.3-4.fc40.x86_64
[ 96/154] Installing xxhash-libs-0:0.8. 100% |  87.8 MiB/s |  89.9 KiB |  00m00s
[ 97/154] Installing libbrotli-0:1.1.0- 100% | 203.1 MiB/s | 831.8 KiB |  00m00s
[ 98/154] Installing libnghttp2-0:1.59. 100% | 163.3 MiB/s | 167.2 KiB |  00m00s
[ 99/154] Installing libtool-ltdl-0:2.4 100% |  65.7 MiB/s |  67.3 KiB |  00m00s
[100/154] Installing coreutils-common-0 100% | 254.8 MiB/s |  11.5 MiB |  00m00s
[101/154] Installing openssl-libs-1:3.2 100% | 311.5 MiB/s |   7.8 MiB |  00m00s
[102/154] Installing coreutils-0:9.4-6. 100% | 138.4 MiB/s |   5.8 MiB |  00m00s
>>> Running pre-install scriptlet: ca-certificates-0:2023.2.62_v7.0.401-6.fc40.n
>>> Stop pre-install scriptlet: ca-certificates-0:2023.2.62_v7.0.401-6.fc40.noar
[103/154] Installing ca-certificates-0: 100% |   2.6 MiB/s |   2.3 MiB |  00m01s
>>> Running post-install scriptlet: ca-certificates-0:2023.2.62_v7.0.401-6.fc40.
>>> Stop post-install scriptlet: ca-certificates-0:2023.2.62_v7.0.401-6.fc40.noa
[104/154] Installing krb5-libs-0:1.21.2 100% | 191.2 MiB/s |   2.3 MiB |  00m00s
[105/154] Installing libtirpc-0:1.3.4-1 100% |  99.9 MiB/s | 204.6 KiB |  00m00s
[106/154] Installing gzip-0:1.13-1.fc40 100% |  95.4 MiB/s | 390.6 KiB |  00m00s
[107/154] Installing authselect-libs-0: 100% |  90.4 MiB/s | 833.2 KiB |  00m00s
[108/154] Installing authselect-0:1.5.0 100% |  38.6 MiB/s | 157.9 KiB |  00m00s
[109/154] Installing cracklib-0:2.9.11- 100% |  34.9 MiB/s | 250.3 KiB |  00m00s
[110/154] Installing libpwquality-0:1.4 100% |  52.5 MiB/s | 430.1 KiB |  00m00s
[111/154] Installing libnsl2-0:2.0.1-1. 100% |  28.8 MiB/s |  59.0 KiB |  00m00s
[112/154] Installing pam-0:1.6.0-2.fc40 100% |  78.7 MiB/s |   1.8 MiB |  00m00s
[113/154] Installing libssh-0:0.10.6-4. 100% | 166.5 MiB/s | 511.4 KiB |  00m00s
[114/154] Installing libarchive-0:3.7.2 100% | 223.8 MiB/s | 916.6 KiB |  00m00s
[115/154] Installing rpm-sequoia-0:1.6. 100% | 278.7 MiB/s |   2.2 MiB |  00m00s
[116/154] Installing rpm-libs-0:4.19.1. 100% | 231.6 MiB/s | 711.4 KiB |  00m00s
[117/154] Installing libevent-0:2.1.12- 100% | 219.6 MiB/s | 899.4 KiB |  00m00s
[118/154] Installing openldap-0:2.6.7-1 100% | 156.0 MiB/s | 638.9 KiB |  00m00s
[119/154] Installing libcurl-0:8.6.0-7. 100% | 188.9 MiB/s | 773.9 KiB |  00m00s
[120/154] Installing elfutils-libs-0:0. 100% | 157.2 MiB/s | 644.0 KiB |  00m00s
[121/154] Installing elfutils-debuginfo 100% |  65.3 MiB/s |  66.9 KiB |  00m00s
[122/154] Installing binutils-gold-0:2. 100% |  84.5 MiB/s |   2.0 MiB |  00m00s
>>> Running post-install scriptlet: binutils-gold-0:2.41-34.fc40.x86_64
>>> Stop post-install scriptlet: binutils-gold-0:2.41-34.fc40.x86_64
[123/154] Installing binutils-0:2.41-34 100% | 251.4 MiB/s |  26.4 MiB |  00m00s
>>> Running post-install scriptlet: binutils-0:2.41-34.fc40.x86_64
>>> Stop post-install scriptlet: binutils-0:2.41-34.fc40.x86_64
[124/154] Installing elfutils-0:0.190-6 100% | 229.9 MiB/s |   2.5 MiB |  00m00s
[125/154] Installing gdb-minimal-0:14.1 100% | 314.6 MiB/s |  12.3 MiB |  00m00s
[126/154] Installing debugedit-0:5.0-14 100% |  98.5 MiB/s | 201.7 KiB |  00m00s
[127/154] Installing rpm-build-libs-0:4 100% |  97.3 MiB/s | 199.2 KiB |  00m00s
[128/154] Installing curl-0:8.6.0-7.fc4 100% |  28.8 MiB/s | 736.9 KiB |  00m00s
>>> Running pre-install scriptlet: rpm-0:4.19.1.1-1.fc40.x86_64
>>> Stop pre-install scriptlet: rpm-0:4.19.1.1-1.fc40.x86_64
[129/154] Installing rpm-0:4.19.1.1-1.f 100% |  88.8 MiB/s |   2.4 MiB |  00m00s
[130/154] Installing efi-srpm-macros-0: 100% |  40.2 MiB/s |  41.2 KiB |  00m00s
[131/154] Installing lua-srpm-macros-0: 100% |   1.9 MiB/s |   1.9 KiB |  00m00s
[132/154] Installing zig-srpm-macros-0: 100% |   0.0   B/s |   1.7 KiB |  00m00s
[133/154] Installing rust-srpm-macros-0 100% |   5.4 MiB/s |   5.5 KiB |  00m00s
[134/154] Installing qt6-srpm-macros-0: 100% |   0.0   B/s | 732.0   B |  00m00s
[135/154] Installing qt5-srpm-macros-0: 100% |   0.0   B/s | 768.0   B |  00m00s
[136/154] Installing perl-srpm-macros-0 100% |   0.0   B/s |   1.1 KiB |  00m00s
[137/154] Installing package-notes-srpm 100% |   0.0   B/s |   2.0 KiB |  00m00s
[138/154] Installing openblas-srpm-macr 100% |   0.0   B/s | 384.0   B |  00m00s
[139/154] Installing ocaml-srpm-macros- 100% |   0.0   B/s |   2.2 KiB |  00m00s
[140/154] Installing kernel-srpm-macros 100% |   0.0   B/s |   2.3 KiB |  00m00s
[141/154] Installing gnat-srpm-macros-0 100% |   0.0   B/s |   1.3 KiB |  00m00s
[142/154] Installing ghc-srpm-macros-0: 100% |   0.0   B/s | 648.0   B |  00m00s
[143/154] Installing fpc-srpm-macros-0: 100% |   0.0   B/s | 420.0   B |  00m00s
[144/154] Installing ansible-srpm-macro 100% |  35.4 MiB/s |  36.2 KiB |  00m00s
[145/154] Installing fonts-srpm-macros- 100% |  55.1 MiB/s |  56.5 KiB |  00m00s
[146/154] Installing forge-srpm-macros- 100% |  37.7 MiB/s |  38.6 KiB |  00m00s
[147/154] Installing go-srpm-macros-0:3 100% |  60.2 MiB/s |  61.6 KiB |  00m00s
[148/154] Installing python-srpm-macros 100% |  50.1 MiB/s |  51.3 KiB |  00m00s
[149/154] Installing redhat-rpm-config- 100% |  46.7 MiB/s | 191.4 KiB |  00m00s
[150/154] Installing rpm-build-0:4.19.1 100% |  44.4 MiB/s | 182.0 KiB |  00m00s
[151/154] Installing pyproject-srpm-mac 100% |   1.0 MiB/s |   2.1 KiB |  00m00s
[152/154] Installing util-linux-0:2.40- 100% |  84.6 MiB/s |   3.7 MiB |  00m00s
>>> Running post-install scriptlet: util-linux-0:2.40-0.9.rc1.fc40.x86_64
>>> Stop post-install scriptlet: util-linux-0:2.40-0.9.rc1.fc40.x86_64
[153/154] Installing which-0:2.21-41.fc 100% |  40.3 MiB/s |  82.4 KiB |  00m00s
[154/154] Installing info-0:7.1-2.fc40. 100% | 291.0 KiB/s | 358.2 KiB |  00m01s
>>> Running post-transaction scriptlet: filesystem-0:3.18-8.fc40.x86_64
>>> Stop post-transaction scriptlet: filesystem-0:3.18-8.fc40.x86_64
>>> Running post-transaction scriptlet: ca-certificates-0:2023.2.62_v7.0.401-6.f
>>> Stop post-transaction scriptlet: ca-certificates-0:2023.2.62_v7.0.401-6.fc40
>>> Running post-transaction scriptlet: authselect-libs-0:1.5.0-5.fc40.x86_64
>>> Stop post-transaction scriptlet: authselect-libs-0:1.5.0-5.fc40.x86_64
>>> Running post-transaction scriptlet: rpm-0:4.19.1.1-1.fc40.x86_64
>>> Stop post-transaction scriptlet: rpm-0:4.19.1.1-1.fc40.x86_64
>>> Running trigger-install scriptlet: glibc-common-0:2.39-2.fc40.x86_64
>>> Stop trigger-install scriptlet: glibc-common-0:2.39-2.fc40.x86_64
>>> Running trigger-install scriptlet: info-0:7.1-2.fc40.x86_64
>>> Stop trigger-install scriptlet: info-0:7.1-2.fc40.x86_64
Finish: installing minimal buildroot with dnf5
Start: creating root cache
Finish: creating root cache
Finish: chroot init
INFO: Installed packages:
INFO: alternatives-1.26-3.fc40.x86_64
ansible-srpm-macros-1-14.fc40.noarch
audit-libs-4.0-8.fc40.x86_64
authselect-1.5.0-5.fc40.x86_64
authselect-libs-1.5.0-5.fc40.x86_64
basesystem-11-20.fc40.noarch
bash-5.2.26-3.fc40.x86_64
binutils-2.41-34.fc40.x86_64
binutils-gold-2.41-34.fc40.x86_64
bzip2-1.0.8-18.fc40.x86_64
bzip2-libs-1.0.8-18.fc40.x86_64
ca-certificates-2023.2.62_v7.0.401-6.fc40.noarch
coreutils-9.4-6.fc40.x86_64
coreutils-common-9.4-6.fc40.x86_64
cpio-2.15-1.fc40.x86_64
cracklib-2.9.11-5.fc40.x86_64
crypto-policies-20240201-2.git9f501f3.fc40.noarch
curl-8.6.0-7.fc40.x86_64
cyrus-sasl-lib-2.1.28-19.fc40.x86_64
debugedit-5.0-14.fc40.x86_64
diffutils-3.10-5.fc40.x86_64
dwz-0.15-6.fc40.x86_64
ed-1.20.1-1.fc40.x86_64
efi-srpm-macros-5-11.fc40.noarch
elfutils-0.190-6.fc40.x86_64
elfutils-debuginfod-client-0.190-6.fc40.x86_64
elfutils-default-yama-scope-0.190-6.fc40.noarch
elfutils-libelf-0.190-6.fc40.x86_64
elfutils-libs-0.190-6.fc40.x86_64
fedora-gpg-keys-40-0.4.noarch
fedora-release-40-0.36.noarch
fedora-release-common-40-0.36.noarch
fedora-release-identity-basic-40-0.36.noarch
fedora-repos-40-0.4.noarch
file-5.45-4.fc40.x86_64
file-libs-5.45-4.fc40.x86_64
filesystem-3.18-8.fc40.x86_64
findutils-4.9.0-8.fc40.x86_64
fonts-srpm-macros-2.0.5-14.fc40.noarch
forge-srpm-macros-0.2.0-3.fc40.noarch
fpc-srpm-macros-1.3-12.fc40.noarch
gawk-5.3.0-3.fc40.x86_64
gdb-minimal-14.1-8.fc40.x86_64
gdbm-1.23-6.fc40.x86_64
gdbm-libs-1.23-6.fc40.x86_64
ghc-srpm-macros-1.6.1-5.fc40.noarch
glibc-2.39-2.fc40.x86_64
glibc-common-2.39-2.fc40.x86_64
glibc-gconv-extra-2.39-2.fc40.x86_64
glibc-minimal-langpack-2.39-2.fc40.x86_64
gmp-6.2.1-8.fc40.x86_64
gnat-srpm-macros-6-5.fc40.noarch
go-srpm-macros-3.4.0-2.fc40.noarch
gpg-pubkey-a15b79cc-63d04c2c
grep-3.11-7.fc40.x86_64
gzip-1.13-1.fc40.x86_64
info-7.1-2.fc40.x86_64
jansson-2.13.1-9.fc40.x86_64
kernel-srpm-macros-1.0-22.fc40.noarch
keyutils-libs-1.6.3-3.fc40.x86_64
krb5-libs-1.21.2-5.fc40.x86_64
libacl-2.3.2-1.fc40.x86_64
libarchive-3.7.2-3.fc40.x86_64
libattr-2.5.2-3.fc40.x86_64
libblkid-2.40-0.9.rc1.fc40.x86_64
libbrotli-1.1.0-3.fc40.x86_64
libcap-2.69-3.fc40.x86_64
libcap-ng-0.8.4-4.fc40.x86_64
libcom_err-1.47.0-5.fc40.x86_64
libcurl-8.6.0-7.fc40.x86_64
libeconf-0.5.2-3.fc40.x86_64
libevent-2.1.12-12.fc40.x86_64
libfdisk-2.40-0.9.rc1.fc40.x86_64
libffi-3.4.4-7.fc40.x86_64
libgcc-14.0.1-0.7.fc40.x86_64
libgomp-14.0.1-0.7.fc40.x86_64
libidn2-2.3.7-1.fc40.x86_64
libmount-2.40-0.9.rc1.fc40.x86_64
libnghttp2-1.59.0-2.fc40.x86_64
libnsl2-2.0.1-1.fc40.x86_64
libpkgconf-2.1.0-1.fc40.x86_64
libpsl-0.21.5-3.fc40.x86_64
libpwquality-1.4.5-9.fc40.x86_64
libselinux-3.6-4.fc40.x86_64
libsemanage-3.6-3.fc40.x86_64
libsepol-3.6-3.fc40.x86_64
libsmartcols-2.40-0.9.rc1.fc40.x86_64
libssh-0.10.6-4.fc40.x86_64
libssh-config-0.10.6-4.fc40.noarch
libstdc++-14.0.1-0.7.fc40.x86_64
libtasn1-4.19.0-6.fc40.x86_64
libtirpc-1.3.4-1.rc2.fc40.2.x86_64
libtool-ltdl-2.4.7-10.fc40.x86_64
libunistring-1.1-7.fc40.x86_64
libutempter-1.2.1-13.fc40.x86_64
libuuid-2.40-0.9.rc1.fc40.x86_64
libverto-0.3.2-8.fc40.x86_64
libxcrypt-4.4.36-5.fc40.x86_64
libxml2-2.12.5-1.fc40.x86_64
libzstd-1.5.5-5.fc40.x86_64
lua-libs-5.4.6-5.fc40.x86_64
lua-srpm-macros-1-13.fc40.noarch
lz4-libs-1.9.4-6.fc40.x86_64
mpfr-4.2.1-3.fc40.x86_64
ncurses-base-6.4-12.20240127.fc40.noarch
ncurses-libs-6.4-12.20240127.fc40.x86_64
ocaml-srpm-macros-9-3.fc40.noarch
openblas-srpm-macros-2-16.fc40.noarch
openldap-2.6.7-1.fc40.x86_64
openssl-libs-3.2.1-2.fc40.x86_64
p11-kit-0.25.3-4.fc40.x86_64
p11-kit-trust-0.25.3-4.fc40.x86_64
package-notes-srpm-macros-0.5-11.fc40.noarch
pam-1.6.0-2.fc40.x86_64
pam-libs-1.6.0-2.fc40.x86_64
patch-2.7.6-24.fc40.x86_64
pcre2-10.42-2.fc40.2.x86_64
pcre2-syntax-10.42-2.fc40.2.noarch
perl-srpm-macros-1-53.fc40.noarch
pkgconf-2.1.0-1.fc40.x86_64
pkgconf-m4-2.1.0-1.fc40.noarch
pkgconf-pkg-config-2.1.0-1.fc40.x86_64
popt-1.19-6.fc40.x86_64
publicsuffix-list-dafsa-20240107-3.fc40.noarch
pyproject-srpm-macros-1.12.0-1.fc40.noarch
python-srpm-macros-3.12-7.fc40.noarch
qt5-srpm-macros-5.15.12-3.fc40.noarch
qt6-srpm-macros-6.6.2-1.fc40.noarch
readline-8.2-8.fc40.x86_64
redhat-rpm-config-285-1.fc40.noarch
rpm-4.19.1.1-1.fc40.x86_64
rpm-build-4.19.1.1-1.fc40.x86_64
rpm-build-libs-4.19.1.1-1.fc40.x86_64
rpm-libs-4.19.1.1-1.fc40.x86_64
rpm-sequoia-1.6.0-2.fc40.x86_64
rust-srpm-macros-26.1-1.fc40.noarch
sed-4.9-1.fc40.x86_64
setup-2.14.5-2.fc40.noarch
shadow-utils-4.15.0rc2-1.fc40.x86_64
sqlite-libs-3.45.1-2.fc40.x86_64
systemd-libs-255.3-1.fc40.x86_64
tar-1.35-3.fc40.x86_64
unzip-6.0-63.fc40.x86_64
util-linux-2.40-0.9.rc1.fc40.x86_64
util-linux-core-2.40-0.9.rc1.fc40.x86_64
which-2.21-41.fc40.x86_64
xxhash-libs-0.8.2-2.fc40.x86_64
xz-5.4.6-1.fc40.x86_64
xz-libs-5.4.6-1.fc40.x86_64
zig-srpm-macros-1-2.fc40.noarch
zip-3.0-40.fc40.x86_64
zlib-ng-compat-2.1.6-2.fc40.x86_64
zstd-1.5.5-5.fc40.x86_64
Start: buildsrpm
Start: rpmbuild -bs
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1710288000
Wrote: /builddir/build/SRPMS/python-ckan-2.10.4-1.fc40.src.rpm
Finish: rpmbuild -bs
cp: preserving permissions for ‘/var/lib/copr-rpmbuild/results/chroot_scan/var/lib/mock/fedora-40-x86_64-1710336054.221965/root/var/log’: No such file or directory
INFO: chroot_scan: 1 files copied to /var/lib/copr-rpmbuild/results/chroot_scan
INFO: /var/lib/mock/fedora-40-x86_64-1710336054.221965/root/var/log/dnf5.log
Finish: buildsrpm
INFO: Done(/var/lib/copr-rpmbuild/workspace/workdir-6l0e9ih2/python-ckan/python-ckan.spec) Config(child) 0 minutes 43 seconds
INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results
INFO: Cleaning up build root ('cleanup_on_success=True')
Start: clean chroot
INFO: unmounting tmpfs.
Finish: clean chroot
INFO: Start(/var/lib/copr-rpmbuild/results/python-ckan-2.10.4-1.fc40.src.rpm)  Config(fedora-40-x86_64)
Start(bootstrap): chroot init
INFO: mounting tmpfs at /var/lib/mock/fedora-40-x86_64-bootstrap-1710336054.221965/root.
INFO: reusing tmpfs at /var/lib/mock/fedora-40-x86_64-bootstrap-1710336054.221965/root.
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled package manager cache
Start(bootstrap): cleaning package manager metadata
Finish(bootstrap): cleaning package manager metadata
Finish(bootstrap): chroot init
Start: chroot init
INFO: mounting tmpfs at /var/lib/mock/fedora-40-x86_64-1710336054.221965/root.
INFO: calling preinit hooks
INFO: enabled root cache
Start: unpacking root cache
Finish: unpacking root cache
INFO: enabled package manager cache
Start: cleaning package manager metadata
Finish: cleaning package manager metadata
INFO: enabled HW Info plugin
INFO: Buildroot is handled by package management downloaded with a bootstrap image:
  rpm-4.19.1.1-1.fc40.x86_64
  rpm-sequoia-1.6.0-2.fc40.x86_64
  python3-dnf-4.19.0-1.fc40.noarch
  yum-4.19.0-1.fc40.noarch
  dnf5-5.1.12-1.fc40.x86_64
  dnf5-plugins-5.1.12-1.fc40.x86_64
Finish: chroot init
Start: build phase for python-ckan-2.10.4-1.fc40.src.rpm
Start: build setup for python-ckan-2.10.4-1.fc40.src.rpm
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1710288000
Wrote: /builddir/build/SRPMS/python-ckan-2.10.4-1.fc40.src.rpm
Updating and loading repositories:
 updates                                100% | 767.8 KiB/s |  23.8 KiB |  00m00s
 fedora                                 100% | 871.3 KiB/s |  20.9 KiB |  00m00s
 Copr repository                        100% |   5.0 KiB/s |   1.5 KiB |  00m00s
Repositories loaded.
Package                  Arch   Version        Repository      Size
Installing:                                                        
 python3-devel           x86_64 3.12.2-1.fc40  fedora       1.2 MiB
Installing dependencies:                                           
 expat                   x86_64 2.6.0-1.fc40   fedora     276.9 KiB
 libb2                   x86_64 0.98.1-11.fc40 fedora      42.2 KiB
 mpdecimal               x86_64 2.5.1-9.fc40   fedora     200.9 KiB
 pyproject-rpm-macros    noarch 1.12.0-1.fc40  fedora      98.8 KiB
 python-pip-wheel        noarch 23.3.2-1.fc40  fedora       1.5 MiB
 python-rpm-macros       noarch 3.12-7.fc40    fedora      22.1 KiB
 python3                 x86_64 3.12.2-1.fc40  fedora      31.9 KiB
 python3-libs            x86_64 3.12.2-1.fc40  fedora      41.0 MiB
 python3-packaging       noarch 23.2-4.fc40    fedora     421.1 KiB
 python3-rpm-generators  noarch 14-10.fc40     fedora      81.7 KiB
 python3-rpm-macros      noarch 3.12-7.fc40    fedora       6.4 KiB
 tzdata                  noarch 2024a-2.fc40   fedora       1.6 MiB

Transaction Summary:
 Installing:       13 packages

Total size of inbound packages is 12 MiB. Need to download 0 B.
After this operation 47 MiB will be used (install 47 MiB, remove 0 B).
[ 1/13] python3-devel-0:3.12.2-1.fc40.x 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 2/13] python3-libs-0:3.12.2-1.fc40.x8 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 3/13] expat-0:2.6.0-1.fc40.x86_64     100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 4/13] libb2-0:0.98.1-11.fc40.x86_64   100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 5/13] mpdecimal-0:2.5.1-9.fc40.x86_64 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 6/13] python-pip-wheel-0:23.3.2-1.fc4 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 7/13] tzdata-0:2024a-2.fc40.noarch    100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 8/13] pyproject-rpm-macros-0:1.12.0-1 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[ 9/13] python-rpm-macros-0:3.12-7.fc40 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[10/13] python3-rpm-generators-0:14-10. 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[11/13] python3-rpm-macros-0:3.12-7.fc4 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[12/13] python3-packaging-0:23.2-4.fc40 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[13/13] python3-0:3.12.2-1.fc40.x86_64  100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
--------------------------------------------------------------------------------
[13/13] Total                           100% |   0.0   B/s |   0.0   B |  00m00s
Running transaction
[ 1/15] Verify package files            100% | 260.0   B/s |  13.0   B |  00m00s
[ 2/15] Prepare transaction             100% | 302.0   B/s |  13.0   B |  00m00s
[ 3/15] Installing python-rpm-macros-0: 100% |  22.3 MiB/s |  22.8 KiB |  00m00s
[ 4/15] Installing python3-rpm-macros-0 100% |   6.5 MiB/s |   6.7 KiB |  00m00s
[ 5/15] Installing pyproject-rpm-macros 100% |  19.7 MiB/s | 100.8 KiB |  00m00s
[ 6/15] Installing tzdata-0:2024a-2.fc4 100% |  27.1 MiB/s |   1.9 MiB |  00m00s
[ 7/15] Installing python-pip-wheel-0:2 100% | 380.0 MiB/s |   1.5 MiB |  00m00s
[ 8/15] Installing mpdecimal-0:2.5.1-9. 100% |  98.6 MiB/s | 202.0 KiB |  00m00s
[ 9/15] Installing libb2-0:0.98.1-11.fc 100% |  42.3 MiB/s |  43.3 KiB |  00m00s
[10/15] Installing expat-0:2.6.0-1.fc40 100% | 136.2 MiB/s | 278.9 KiB |  00m00s
[11/15] Installing python3-0:3.12.2-1.f 100% |   4.7 MiB/s |  33.6 KiB |  00m00s
[12/15] Installing python3-libs-0:3.12. 100% | 206.0 MiB/s |  41.4 MiB |  00m00s
[13/15] Installing python3-packaging-0: 100% | 105.4 MiB/s | 431.9 KiB |  00m00s
[14/15] Installing python3-rpm-generato 100% |  40.5 MiB/s |  82.9 KiB |  00m00s
[15/15] Installing python3-devel-0:3.12 100% |  26.0 MiB/s |   1.3 MiB |  00m00s
>>> Running trigger-install scriptlet: glibc-common-0:2.39-2.fc40.x86_64
>>> Stop trigger-install scriptlet: glibc-common-0:2.39-2.fc40.x86_64
Finish: build setup for python-ckan-2.10.4-1.fc40.src.rpm
Start: rpmbuild python-ckan-2.10.4-1.fc40.src.rpm
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1710288000
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.3HJLwj
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf ckan-2.10.4
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/ckan-2.10.4.tar.gz
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd ckan-2.10.4
+ rm -rf /builddir/build/BUILD/ckan-2.10.4-SPECPARTS
+ /usr/bin/mkdir -p /builddir/build/BUILD/ckan-2.10.4-SPECPARTS
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.VF4LAj
+ umask 022
+ cd /builddir/build/BUILD
+ cd ckan-2.10.4
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1  '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(pip) >= 19'
+ echo 'python3dist(packaging)'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1  '
+ TMPDIR=/builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir
+ RPM_TOXENV=py312
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/ckan-2.10.4/pyproject-wheeldir --output /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-buildrequires
Handling setuptools >= 40.8 from default build backend
Requirement not satisfied: setuptools >= 40.8
Handling wheel from default build backend
Requirement not satisfied: wheel
Exiting dependency generation pass: build backend
+ cat /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-buildrequires
+ rm -rfv '*.dist-info/'
+ RPM_EC=0
++ jobs -p
+ exit 0
Wrote: /builddir/build/SRPMS/python-ckan-2.10.4-1.fc40.buildreqs.nosrc.rpm
INFO: Going to install missing dynamic buildrequires
Updating and loading repositories:
 updates                                100% | 850.1 KiB/s |  23.8 KiB |  00m00s
 fedora                                 100% | 950.5 KiB/s |  20.9 KiB |  00m00s
 Copr repository                        100% |  53.1 KiB/s |   1.5 KiB |  00m00s
Repositories loaded.
Package             Arch   Version         Repository      Size
Installing:                                                    
 python3-pip        noarch 23.3.2-1.fc40   fedora      14.2 MiB
 python3-setuptools noarch 69.0.3-3.fc40   fedora       7.1 MiB
 python3-wheel      noarch 1:0.41.2-3.fc40 fedora     507.1 KiB

Transaction Summary:
 Installing:        3 packages

Package "pyproject-rpm-macros-1.12.0-1.fc40.noarch" is already installed.
Package "python3-devel-3.12.2-1.fc40.x86_64" is already installed.
Package "python3-packaging-23.2-4.fc40.noarch" is already installed.

Total size of inbound packages is 5 MiB. Need to download 0 B.
After this operation 22 MiB will be used (install 22 MiB, remove 0 B).
[1/3] python3-pip-0:23.3.2-1.fc40.noarc 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[2/3] python3-setuptools-0:69.0.3-3.fc4 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
[3/3] python3-wheel-1:0.41.2-3.fc40.noa 100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
--------------------------------------------------------------------------------
[3/3] Total                             100% |   0.0   B/s |   0.0   B |  00m00s
Running transaction
[1/5] Verify package files              100% | 157.0   B/s |   3.0   B |  00m00s
[2/5] Prepare transaction               100% | 103.0   B/s |   3.0   B |  00m00s
[3/5] Installing python3-wheel-1:0.41.2 100% |  64.2 MiB/s | 526.1 KiB |  00m00s
[4/5] Installing python3-setuptools-0:6 100% | 132.7 MiB/s |   7.3 MiB |  00m00s
[5/5] Installing python3-pip-0:23.3.2-1 100% | 109.9 MiB/s |  14.5 MiB |  00m00s
>>> Running trigger-install scriptlet: glibc-common-0:2.39-2.fc40.x86_64
>>> Stop trigger-install scriptlet: glibc-common-0:2.39-2.fc40.x86_64
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1710288000
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.Ah17dD
+ umask 022
+ cd /builddir/build/BUILD
+ cd ckan-2.10.4
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1  '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(pip) >= 19'
+ echo 'python3dist(packaging)'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1  '
+ TMPDIR=/builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir
+ RPM_TOXENV=py312
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/ckan-2.10.4/pyproject-wheeldir --output /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-buildrequires
Handling setuptools >= 40.8 from default build backend
Requirement satisfied: setuptools >= 40.8
   (installed: setuptools 69.0.3)
Handling wheel from default build backend
Requirement satisfied: wheel
   (installed: wheel 0.41.2)
/usr/lib/python3.12/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg`
!!

        ********************************************************************************
        The namespace_packages parameter is deprecated, consider using implicit namespaces instead (PEP 420).

        See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
        ********************************************************************************

!!
  parsed = self.parsers.get(option_name, lambda x: x)(value)
/usr/lib/python3.12/site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'message_extractors'
  warnings.warn(msg)
running egg_info
writing ckan.egg-info/PKG-INFO
writing dependency_links to ckan.egg-info/dependency_links.txt
writing entry points to ckan.egg-info/entry_points.txt
writing namespace_packages to ckan.egg-info/namespace_packages.txt
writing requirements to ckan.egg-info/requires.txt
writing top-level names to ckan.egg-info/top_level.txt
reading manifest file 'ckan.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching '.git'
warning: no files found matching 'CHANGELOG.txt'
adding license file 'LICENSE.txt'
writing manifest file 'ckan.egg-info/SOURCES.txt'
Handling wheel from get_requires_for_build_wheel
Requirement satisfied: wheel
   (installed: wheel 0.41.2)
running dist_info
writing ckan.egg-info/PKG-INFO
writing dependency_links to ckan.egg-info/dependency_links.txt
writing entry points to ckan.egg-info/entry_points.txt
writing namespace_packages to ckan.egg-info/namespace_packages.txt
writing requirements to ckan.egg-info/requires.txt
writing top-level names to ckan.egg-info/top_level.txt
reading manifest file 'ckan.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching '.git'
warning: no files found matching 'CHANGELOG.txt'
adding license file 'LICENSE.txt'
writing manifest file 'ckan.egg-info/SOURCES.txt'
creating '/builddir/build/BUILD/ckan-2.10.4/ckan-2.10.4.dist-info'
Handling setuptools >=44.1.0 from hook generated metadata: Requires-Dist (ckan)
Requirement satisfied: setuptools >=44.1.0
   (installed: setuptools 69.0.3)
Handling beautifulsoup4 ==4.11.1 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: beautifulsoup4 ==4.11.1 ; extra == 'dev'
Handling cookiecutter ==2.1.1 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: cookiecutter ==2.1.1 ; extra == 'dev'
Handling coveralls ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: coveralls ; extra == 'dev'
Handling docutils ==0.17 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: docutils ==0.17 ; extra == 'dev'
Handling Faker ==14.2.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: Faker ==14.2.0 ; extra == 'dev'
Handling factory-boy ==3.2.1 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: factory-boy ==3.2.1 ; extra == 'dev'
Handling flask-debugtoolbar ==0.13.1 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: flask-debugtoolbar ==0.13.1 ; extra == 'dev'
Handling freezegun ==1.2.2 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: freezegun ==1.2.2 ; extra == 'dev'
Handling ipdb ==0.13.9 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: ipdb ==0.13.9 ; extra == 'dev'
Handling pip-tools ==6.8.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pip-tools ==6.8.0 ; extra == 'dev'
Handling Pillow ==9.2.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: Pillow ==9.2.0 ; extra == 'dev'
Handling responses ==0.21.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: responses ==0.21.0 ; extra == 'dev'
Handling sphinx-rtd-theme ==1.0.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: sphinx-rtd-theme ==1.0.0 ; extra == 'dev'
Handling sqlalchemy-stubs ==0.4 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: sqlalchemy-stubs ==0.4 ; extra == 'dev'
Handling sphinx ==5.1.1 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: sphinx ==5.1.1 ; extra == 'dev'
Handling towncrier ==22.8.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: towncrier ==22.8.0 ; extra == 'dev'
Handling pytest ==7.1.3 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytest ==7.1.3 ; extra == 'dev'
Handling pytest-cov ==3.0.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytest-cov ==3.0.0 ; extra == 'dev'
Handling pytest-factoryboy ==2.4.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytest-factoryboy ==2.4.0 ; extra == 'dev'
Handling pytest-freezegun ==0.4.2 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytest-freezegun ==0.4.2 ; extra == 'dev'
Handling pytest-rerunfailures ==10.2 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytest-rerunfailures ==10.2 ; extra == 'dev'
Handling pytest-split ==0.8.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytest-split ==0.8.0 ; extra == 'dev'
Handling alembic ==1.8.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: alembic ==1.8.1 ; extra == 'requirements'
Handling babel ==2.10.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: babel ==2.10.3 ; extra == 'requirements'
Handling beaker ==1.11.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: beaker ==1.11.0 ; extra == 'requirements'
Handling bleach ==5.0.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: bleach ==5.0.1 ; extra == 'requirements'
Handling blinker ==1.5 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: blinker ==1.5 ; extra == 'requirements'
Handling certifi ==2021.10.8 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: certifi ==2021.10.8 ; extra == 'requirements'
Handling charset-normalizer ==2.0.12 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: charset-normalizer ==2.0.12 ; extra == 'requirements'
Handling click ==8.1.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: click ==8.1.3 ; extra == 'requirements'
Handling deprecated ==1.2.13 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: deprecated ==1.2.13 ; extra == 'requirements'
Handling dominate ==2.7.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: dominate ==2.7.0 ; extra == 'requirements'
Handling feedgen ==0.9.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: feedgen ==0.9.0 ; extra == 'requirements'
Handling flask ==2.0.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: flask ==2.0.3 ; extra == 'requirements'
Handling flask-babel ==1.0.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: flask-babel ==1.0.0 ; extra == 'requirements'
Handling flask-login ==0.6.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: flask-login ==0.6.1 ; extra == 'requirements'
Handling flask-multistatic ==1.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: flask-multistatic ==1.0 ; extra == 'requirements'
Handling flask-wtf ==1.0.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: flask-wtf ==1.0.1 ; extra == 'requirements'
Handling greenlet ==2.0.2 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: greenlet ==2.0.2 ; extra == 'requirements'
Handling idna ==3.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: idna ==3.3 ; extra == 'requirements'
Handling importlib-metadata ==4.11.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: importlib-metadata ==4.11.3 ; extra == 'requirements'
Handling itsdangerous ==2.1.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: itsdangerous ==2.1.1 ; extra == 'requirements'
Handling jinja2 ==3.1.2 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: jinja2 ==3.1.2 ; extra == 'requirements'
Handling lxml ==4.9.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: lxml ==4.9.1 ; extra == 'requirements'
Handling mako ==1.2.2 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: mako ==1.2.2 ; extra == 'requirements'
Handling markdown ==3.4.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: markdown ==3.4.1 ; extra == 'requirements'
Handling markupsafe ==2.1.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: markupsafe ==2.1.1 ; extra == 'requirements'
Handling mypy ==0.971 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: mypy ==0.971 ; extra == 'requirements'
Handling mypy-extensions ==0.4.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: mypy-extensions ==0.4.3 ; extra == 'requirements'
Handling nose ==1.3.7 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: nose ==1.3.7 ; extra == 'requirements'
Handling packaging ==21.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: packaging ==21.3 ; extra == 'requirements'
Handling passlib ==1.7.4 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: passlib ==1.7.4 ; extra == 'requirements'
Handling polib ==1.1.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: polib ==1.1.1 ; extra == 'requirements'
Handling psycopg2 ==2.9.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: psycopg2 ==2.9.3 ; extra == 'requirements'
Handling pyjwt ==2.4.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pyjwt ==2.4.0 ; extra == 'requirements'
Handling pyparsing ==3.0.7 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pyparsing ==3.0.7 ; extra == 'requirements'
Handling pysolr ==3.9.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pysolr ==3.9.0 ; extra == 'requirements'
Handling python-dateutil ==2.8.2 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: python-dateutil ==2.8.2 ; extra == 'requirements'
Handling python-magic ==0.4.27 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: python-magic ==0.4.27 ; extra == 'requirements'
Handling pytz ==2021.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytz ==2021.3 ; extra == 'requirements'
Handling pytz-deprecation-shim ==0.1.0.post0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytz-deprecation-shim ==0.1.0.post0 ; extra == 'requirements'
Handling pyutilib ==6.0.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pyutilib ==6.0.0 ; extra == 'requirements'
Handling pyyaml ==6.0.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pyyaml ==6.0.1 ; extra == 'requirements'
Handling redis ==4.1.4 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: redis ==4.1.4 ; extra == 'requirements'
Handling requests ==2.28.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: requests ==2.28.1 ; extra == 'requirements'
Handling rq ==1.11.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: rq ==1.11.0 ; extra == 'requirements'
Handling simplejson ==3.17.6 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: simplejson ==3.17.6 ; extra == 'requirements'
Handling six ==1.16.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: six ==1.16.0 ; extra == 'requirements'
Handling sqlalchemy[mypy] ==1.4.41 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: sqlalchemy[mypy] ==1.4.41 ; extra == 'requirements'
Handling sqlalchemy2-stubs ==0.0.2a27 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: sqlalchemy2-stubs ==0.0.2a27 ; extra == 'requirements'
Handling sqlparse ==0.4.2 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: sqlparse ==0.4.2 ; extra == 'requirements'
Handling tomli ==2.0.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: tomli ==2.0.1 ; extra == 'requirements'
Handling typing-extensions ==4.3.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: typing-extensions ==4.3.0 ; extra == 'requirements'
Handling tzdata ==2022.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: tzdata ==2022.1 ; extra == 'requirements'
Handling tzlocal ==4.2 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: tzlocal ==4.2 ; extra == 'requirements'
Handling urllib3 ==1.26.9 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: urllib3 ==1.26.9 ; extra == 'requirements'
Handling watchdog ==2.1.6 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: watchdog ==2.1.6 ; extra == 'requirements'
Handling webassets ==2.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: webassets ==2.0 ; extra == 'requirements'
Handling webencodings ==0.5.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: webencodings ==0.5.1 ; extra == 'requirements'
Handling werkzeug[watchdog] ==2.0.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: werkzeug[watchdog] ==2.0.3 ; extra == 'requirements'
Handling wrapt ==1.14.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: wrapt ==1.14.0 ; extra == 'requirements'
Handling wtforms ==3.0.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: wtforms ==3.0.1 ; extra == 'requirements'
Handling zipp ==3.7.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: zipp ==3.7.0 ; extra == 'requirements'
Handling zope-interface ==5.4.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: zope-interface ==5.4.0 ; extra == 'requirements'
Handling backports-zoneinfo ==0.2.1 ; (python_version < "3.9") and extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: backports-zoneinfo ==0.2.1 ; (python_version < "3.9") and extra == 'requirements'
+ cat /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-buildrequires
+ rm -rfv ckan-2.10.4.dist-info/
removed 'ckan-2.10.4.dist-info/entry_points.txt'
removed 'ckan-2.10.4.dist-info/namespace_packages.txt'
removed 'ckan-2.10.4.dist-info/top_level.txt'
removed 'ckan-2.10.4.dist-info/METADATA'
removed 'ckan-2.10.4.dist-info/LICENSE.txt'
removed directory 'ckan-2.10.4.dist-info/'
+ RPM_EC=0
++ jobs -p
+ exit 0
Wrote: /builddir/build/SRPMS/python-ckan-2.10.4-1.fc40.buildreqs.nosrc.rpm
INFO: Going to install missing dynamic buildrequires
Updating and loading repositories:
 updates                                100% | 850.1 KiB/s |  23.8 KiB |  00m00s
 fedora                                 100% | 804.2 KiB/s |  20.9 KiB |  00m00s
 Copr repository                        100% |  17.3 KiB/s |   1.5 KiB |  00m00s
Repositories loaded.
Nothing to do.
Package "pyproject-rpm-macros-1.12.0-1.fc40.noarch" is already installed.
Package "python3-devel-3.12.2-1.fc40.x86_64" is already installed.
Package "python3-packaging-23.2-4.fc40.noarch" is already installed.
Package "python3-pip-23.3.2-1.fc40.noarch" is already installed.
Package "python3-setuptools-69.0.3-3.fc40.noarch" is already installed.
Package "python3-setuptools-69.0.3-3.fc40.noarch" is already installed.
Package "python3-wheel-1:0.41.2-3.fc40.noarch" is already installed.

Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1710288000
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.grwnzP
+ umask 022
+ cd /builddir/build/BUILD
+ cd ckan-2.10.4
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1  '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(pip) >= 19'
+ echo 'python3dist(packaging)'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1  '
+ TMPDIR=/builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir
+ RPM_TOXENV=py312
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/ckan-2.10.4/pyproject-wheeldir --output /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-buildrequires
Handling setuptools >= 40.8 from default build backend
Requirement satisfied: setuptools >= 40.8
   (installed: setuptools 69.0.3)
Handling wheel from default build backend
Requirement satisfied: wheel
   (installed: wheel 0.41.2)
/usr/lib/python3.12/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg`
!!

        ********************************************************************************
        The namespace_packages parameter is deprecated, consider using implicit namespaces instead (PEP 420).

        See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
        ********************************************************************************

!!
  parsed = self.parsers.get(option_name, lambda x: x)(value)
/usr/lib/python3.12/site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'message_extractors'
  warnings.warn(msg)
running egg_info
writing ckan.egg-info/PKG-INFO
writing dependency_links to ckan.egg-info/dependency_links.txt
writing entry points to ckan.egg-info/entry_points.txt
writing namespace_packages to ckan.egg-info/namespace_packages.txt
writing requirements to ckan.egg-info/requires.txt
writing top-level names to ckan.egg-info/top_level.txt
reading manifest file 'ckan.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching '.git'
warning: no files found matching 'CHANGELOG.txt'
adding license file 'LICENSE.txt'
writing manifest file 'ckan.egg-info/SOURCES.txt'
Handling wheel from get_requires_for_build_wheel
Requirement satisfied: wheel
   (installed: wheel 0.41.2)
running dist_info
writing ckan.egg-info/PKG-INFO
writing dependency_links to ckan.egg-info/dependency_links.txt
writing entry points to ckan.egg-info/entry_points.txt
writing namespace_packages to ckan.egg-info/namespace_packages.txt
writing requirements to ckan.egg-info/requires.txt
writing top-level names to ckan.egg-info/top_level.txt
reading manifest file 'ckan.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching '.git'
warning: no files found matching 'CHANGELOG.txt'
adding license file 'LICENSE.txt'
writing manifest file 'ckan.egg-info/SOURCES.txt'
creating '/builddir/build/BUILD/ckan-2.10.4/ckan-2.10.4.dist-info'
Handling setuptools >=44.1.0 from hook generated metadata: Requires-Dist (ckan)
Requirement satisfied: setuptools >=44.1.0
   (installed: setuptools 69.0.3)
Handling beautifulsoup4 ==4.11.1 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: beautifulsoup4 ==4.11.1 ; extra == 'dev'
Handling cookiecutter ==2.1.1 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: cookiecutter ==2.1.1 ; extra == 'dev'
Handling coveralls ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: coveralls ; extra == 'dev'
Handling docutils ==0.17 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: docutils ==0.17 ; extra == 'dev'
Handling Faker ==14.2.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: Faker ==14.2.0 ; extra == 'dev'
Handling factory-boy ==3.2.1 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: factory-boy ==3.2.1 ; extra == 'dev'
Handling flask-debugtoolbar ==0.13.1 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: flask-debugtoolbar ==0.13.1 ; extra == 'dev'
Handling freezegun ==1.2.2 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: freezegun ==1.2.2 ; extra == 'dev'
Handling ipdb ==0.13.9 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: ipdb ==0.13.9 ; extra == 'dev'
Handling pip-tools ==6.8.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pip-tools ==6.8.0 ; extra == 'dev'
Handling Pillow ==9.2.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: Pillow ==9.2.0 ; extra == 'dev'
Handling responses ==0.21.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: responses ==0.21.0 ; extra == 'dev'
Handling sphinx-rtd-theme ==1.0.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: sphinx-rtd-theme ==1.0.0 ; extra == 'dev'
Handling sqlalchemy-stubs ==0.4 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: sqlalchemy-stubs ==0.4 ; extra == 'dev'
Handling sphinx ==5.1.1 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: sphinx ==5.1.1 ; extra == 'dev'
Handling towncrier ==22.8.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: towncrier ==22.8.0 ; extra == 'dev'
Handling pytest ==7.1.3 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytest ==7.1.3 ; extra == 'dev'
Handling pytest-cov ==3.0.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytest-cov ==3.0.0 ; extra == 'dev'
Handling pytest-factoryboy ==2.4.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytest-factoryboy ==2.4.0 ; extra == 'dev'
Handling pytest-freezegun ==0.4.2 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytest-freezegun ==0.4.2 ; extra == 'dev'
Handling pytest-rerunfailures ==10.2 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytest-rerunfailures ==10.2 ; extra == 'dev'
Handling pytest-split ==0.8.0 ; extra == 'dev' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytest-split ==0.8.0 ; extra == 'dev'
Handling alembic ==1.8.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: alembic ==1.8.1 ; extra == 'requirements'
Handling babel ==2.10.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: babel ==2.10.3 ; extra == 'requirements'
Handling beaker ==1.11.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: beaker ==1.11.0 ; extra == 'requirements'
Handling bleach ==5.0.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: bleach ==5.0.1 ; extra == 'requirements'
Handling blinker ==1.5 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: blinker ==1.5 ; extra == 'requirements'
Handling certifi ==2021.10.8 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: certifi ==2021.10.8 ; extra == 'requirements'
Handling charset-normalizer ==2.0.12 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: charset-normalizer ==2.0.12 ; extra == 'requirements'
Handling click ==8.1.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: click ==8.1.3 ; extra == 'requirements'
Handling deprecated ==1.2.13 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: deprecated ==1.2.13 ; extra == 'requirements'
Handling dominate ==2.7.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: dominate ==2.7.0 ; extra == 'requirements'
Handling feedgen ==0.9.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: feedgen ==0.9.0 ; extra == 'requirements'
Handling flask ==2.0.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: flask ==2.0.3 ; extra == 'requirements'
Handling flask-babel ==1.0.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: flask-babel ==1.0.0 ; extra == 'requirements'
Handling flask-login ==0.6.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: flask-login ==0.6.1 ; extra == 'requirements'
Handling flask-multistatic ==1.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: flask-multistatic ==1.0 ; extra == 'requirements'
Handling flask-wtf ==1.0.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: flask-wtf ==1.0.1 ; extra == 'requirements'
Handling greenlet ==2.0.2 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: greenlet ==2.0.2 ; extra == 'requirements'
Handling idna ==3.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: idna ==3.3 ; extra == 'requirements'
Handling importlib-metadata ==4.11.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: importlib-metadata ==4.11.3 ; extra == 'requirements'
Handling itsdangerous ==2.1.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: itsdangerous ==2.1.1 ; extra == 'requirements'
Handling jinja2 ==3.1.2 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: jinja2 ==3.1.2 ; extra == 'requirements'
Handling lxml ==4.9.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: lxml ==4.9.1 ; extra == 'requirements'
Handling mako ==1.2.2 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: mako ==1.2.2 ; extra == 'requirements'
Handling markdown ==3.4.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: markdown ==3.4.1 ; extra == 'requirements'
Handling markupsafe ==2.1.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: markupsafe ==2.1.1 ; extra == 'requirements'
Handling mypy ==0.971 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: mypy ==0.971 ; extra == 'requirements'
Handling mypy-extensions ==0.4.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: mypy-extensions ==0.4.3 ; extra == 'requirements'
Handling nose ==1.3.7 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: nose ==1.3.7 ; extra == 'requirements'
Handling packaging ==21.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: packaging ==21.3 ; extra == 'requirements'
Handling passlib ==1.7.4 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: passlib ==1.7.4 ; extra == 'requirements'
Handling polib ==1.1.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: polib ==1.1.1 ; extra == 'requirements'
Handling psycopg2 ==2.9.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: psycopg2 ==2.9.3 ; extra == 'requirements'
Handling pyjwt ==2.4.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pyjwt ==2.4.0 ; extra == 'requirements'
Handling pyparsing ==3.0.7 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pyparsing ==3.0.7 ; extra == 'requirements'
Handling pysolr ==3.9.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pysolr ==3.9.0 ; extra == 'requirements'
Handling python-dateutil ==2.8.2 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: python-dateutil ==2.8.2 ; extra == 'requirements'
Handling python-magic ==0.4.27 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: python-magic ==0.4.27 ; extra == 'requirements'
Handling pytz ==2021.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytz ==2021.3 ; extra == 'requirements'
Handling pytz-deprecation-shim ==0.1.0.post0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pytz-deprecation-shim ==0.1.0.post0 ; extra == 'requirements'
Handling pyutilib ==6.0.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pyutilib ==6.0.0 ; extra == 'requirements'
Handling pyyaml ==6.0.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: pyyaml ==6.0.1 ; extra == 'requirements'
Handling redis ==4.1.4 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: redis ==4.1.4 ; extra == 'requirements'
Handling requests ==2.28.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: requests ==2.28.1 ; extra == 'requirements'
Handling rq ==1.11.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: rq ==1.11.0 ; extra == 'requirements'
Handling simplejson ==3.17.6 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: simplejson ==3.17.6 ; extra == 'requirements'
Handling six ==1.16.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: six ==1.16.0 ; extra == 'requirements'
Handling sqlalchemy[mypy] ==1.4.41 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: sqlalchemy[mypy] ==1.4.41 ; extra == 'requirements'
Handling sqlalchemy2-stubs ==0.0.2a27 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: sqlalchemy2-stubs ==0.0.2a27 ; extra == 'requirements'
Handling sqlparse ==0.4.2 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: sqlparse ==0.4.2 ; extra == 'requirements'
Handling tomli ==2.0.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: tomli ==2.0.1 ; extra == 'requirements'
Handling typing-extensions ==4.3.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: typing-extensions ==4.3.0 ; extra == 'requirements'
Handling tzdata ==2022.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: tzdata ==2022.1 ; extra == 'requirements'
Handling tzlocal ==4.2 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: tzlocal ==4.2 ; extra == 'requirements'
Handling urllib3 ==1.26.9 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: urllib3 ==1.26.9 ; extra == 'requirements'
Handling watchdog ==2.1.6 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: watchdog ==2.1.6 ; extra == 'requirements'
Handling webassets ==2.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: webassets ==2.0 ; extra == 'requirements'
Handling webencodings ==0.5.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: webencodings ==0.5.1 ; extra == 'requirements'
Handling werkzeug[watchdog] ==2.0.3 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: werkzeug[watchdog] ==2.0.3 ; extra == 'requirements'
Handling wrapt ==1.14.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: wrapt ==1.14.0 ; extra == 'requirements'
Handling wtforms ==3.0.1 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: wtforms ==3.0.1 ; extra == 'requirements'
Handling zipp ==3.7.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: zipp ==3.7.0 ; extra == 'requirements'
Handling zope-interface ==5.4.0 ; extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: zope-interface ==5.4.0 ; extra == 'requirements'
Handling backports-zoneinfo ==0.2.1 ; (python_version < "3.9") and extra == 'requirements' from hook generated metadata: Requires-Dist (ckan)
Ignoring alien requirement: backports-zoneinfo ==0.2.1 ; (python_version < "3.9") and extra == 'requirements'
+ cat /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-buildrequires
+ rm -rfv ckan-2.10.4.dist-info/
removed 'ckan-2.10.4.dist-info/entry_points.txt'
removed 'ckan-2.10.4.dist-info/namespace_packages.txt'
removed 'ckan-2.10.4.dist-info/top_level.txt'
removed 'ckan-2.10.4.dist-info/METADATA'
removed 'ckan-2.10.4.dist-info/LICENSE.txt'
removed directory 'ckan-2.10.4.dist-info/'
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.X5eLbv
+ umask 022
+ cd /builddir/build/BUILD
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ cd ckan-2.10.4
+ mkdir -p /builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '
+ TMPDIR=/builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_wheel.py /builddir/build/BUILD/ckan-2.10.4/pyproject-wheeldir
Processing /builddir/build/BUILD/ckan-2.10.4
  Preparing metadata (pyproject.toml): started
  Running command Preparing metadata (pyproject.toml)
  /usr/lib/python3.12/site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'message_extractors'
    warnings.warn(msg)
  /usr/lib/python3.12/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg`
  !!

          ********************************************************************************
          The namespace_packages parameter is deprecated, consider using implicit namespaces instead (PEP 420).

          See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
          ********************************************************************************

  !!
    parsed = self.parsers.get(option_name, lambda x: x)(value)
  running dist_info
  creating /builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir/pip-modern-metadata-q6m8s_kc/ckan.egg-info
  writing /builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir/pip-modern-metadata-q6m8s_kc/ckan.egg-info/PKG-INFO
  writing dependency_links to /builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir/pip-modern-metadata-q6m8s_kc/ckan.egg-info/dependency_links.txt
  writing entry points to /builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir/pip-modern-metadata-q6m8s_kc/ckan.egg-info/entry_points.txt
  writing namespace_packages to /builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir/pip-modern-metadata-q6m8s_kc/ckan.egg-info/namespace_packages.txt
  writing requirements to /builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir/pip-modern-metadata-q6m8s_kc/ckan.egg-info/requires.txt
  writing top-level names to /builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir/pip-modern-metadata-q6m8s_kc/ckan.egg-info/top_level.txt
  writing manifest file '/builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir/pip-modern-metadata-q6m8s_kc/ckan.egg-info/SOURCES.txt'
  reading manifest file '/builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir/pip-modern-metadata-q6m8s_kc/ckan.egg-info/SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  no previously-included directories found matching '.git'
  warning: no files found matching 'CHANGELOG.txt'
  adding license file 'LICENSE.txt'
  writing manifest file '/builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir/pip-modern-metadata-q6m8s_kc/ckan.egg-info/SOURCES.txt'
  creating '/builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir/pip-modern-metadata-q6m8s_kc/ckan-2.10.4.dist-info'
  Preparing metadata (pyproject.toml): finished with status 'done'
Building wheels for collected packages: ckan
  Building wheel for ckan (pyproject.toml): started
  Running command Building wheel for ckan (pyproject.toml)
  /usr/lib/python3.12/site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'message_extractors'
    warnings.warn(msg)
  /usr/lib/python3.12/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg`
  !!

          ********************************************************************************
          The namespace_packages parameter is deprecated, consider using implicit namespaces instead (PEP 420).

          See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
          ********************************************************************************

  !!
    parsed = self.parsers.get(option_name, lambda x: x)(value)
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib
  creating build/lib/ckan
  copying ckan/__init__.py -> build/lib/ckan
  copying ckan/authz.py -> build/lib/ckan
  copying ckan/common.py -> build/lib/ckan
  copying ckan/exceptions.py -> build/lib/ckan
  creating build/lib/ckanext
  copying ckanext/__init__.py -> build/lib/ckanext
  running egg_info
  writing ckan.egg-info/PKG-INFO
  writing dependency_links to ckan.egg-info/dependency_links.txt
  writing entry points to ckan.egg-info/entry_points.txt
  writing namespace_packages to ckan.egg-info/namespace_packages.txt
  writing requirements to ckan.egg-info/requires.txt
  writing top-level names to ckan.egg-info/top_level.txt
  reading manifest file 'ckan.egg-info/SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  no previously-included directories found matching '.git'
  warning: no files found matching 'CHANGELOG.txt'
  adding license file 'LICENSE.txt'
  writing manifest file 'ckan.egg-info/SOURCES.txt'
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.cli' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.cli' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.cli' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.cli' to be distributed and are
          already explicitly excluding 'ckan.cli' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.config' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.config' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.config' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.config' to be distributed and are
          already explicitly excluding 'ckan.config' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.config.declaration' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.config.declaration' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.config.declaration' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.config.declaration' to be distributed and are
          already explicitly excluding 'ckan.config.declaration' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.config.middleware' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.config.middleware' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.config.middleware' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.config.middleware' to be distributed and are
          already explicitly excluding 'ckan.config.middleware' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.config.solr' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.config.solr' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.config.solr' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.config.solr' to be distributed and are
          already explicitly excluding 'ckan.config.solr' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n' to be distributed and are
          already explicitly excluding 'ckan.i18n' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.am.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.am.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.am.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.am.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.am.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.ar.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.ar.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.ar.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.ar.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.ar.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.bg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.bg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.bg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.bg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.bg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.bs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.bs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.bs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.bs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.bs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.ca.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.ca.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.ca.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.ca.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.ca.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.cs_CZ.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.cs_CZ.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.cs_CZ.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.cs_CZ.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.cs_CZ.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.da_DK.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.da_DK.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.da_DK.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.da_DK.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.da_DK.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.de.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.de.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.de.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.de.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.de.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.el.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.el.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.el.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.el.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.el.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.en_AU.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.en_AU.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.en_AU.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.en_AU.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.en_GB.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.en_GB.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.en_GB.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.en_GB.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.es.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.es.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.es.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.es.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.es.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.es_AR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.es_AR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.es_AR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.es_AR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.eu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.eu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.eu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.eu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.eu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.fa_IR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.fa_IR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.fa_IR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.fa_IR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.fa_IR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.fi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.fi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.fi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.fi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.fi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.fr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.fr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.fr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.fr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.gl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.gl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.gl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.gl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.gl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.he.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.he.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.he.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.he.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.he.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.hr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.hr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.hr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.hr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.hr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.hu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.hu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.hu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.hu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.hu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.id.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.id.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.id.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.id.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.id.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.is.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.is.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.is.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.is.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.is.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.it.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.it.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.it.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.it.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.it.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.ja.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.ja.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.ja.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.ja.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.ja.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.km.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.km.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.km.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.km.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.km.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.ko_KR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.ko_KR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.ko_KR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.ko_KR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.ko_KR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.lt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.lt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.lt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.lt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.lt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.lv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.lv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.lv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.lv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.lv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.mk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.mk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.mk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.mk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.mk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.mn_MN.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.mn_MN.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.mn_MN.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.mn_MN.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.mn_MN.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.my_MM.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.my_MM.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.my_MM.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.my_MM.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.my_MM.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.nb_NO.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.nb_NO.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.nb_NO.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.nb_NO.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.nb_NO.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.ne.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.ne.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.ne.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.ne.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.ne.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.nl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.nl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.nl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.nl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.nl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.no.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.no.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.no.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.no.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.no.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.pl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.pl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.pl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.pl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.pl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.pt_BR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.pt_BR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.pt_BR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.pt_BR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.pt_PT.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.pt_PT.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.pt_PT.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.pt_PT.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.pt_PT.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.ro.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.ro.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.ro.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.ro.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.ro.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.ru.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.ru.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.ru.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.ru.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.ru.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.sk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.sk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.sk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.sk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.sk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.sl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.sl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.sl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.sl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.sl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.sq.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.sq.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.sq.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.sq.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.sq.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.sr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.sr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.sr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.sr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.sr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.sr_Latn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.sr_Latn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.sr_Latn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.sr_Latn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.sv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.sv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.sv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.sv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.sv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.th.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.th.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.th.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.th.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.th.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.tl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.tl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.tl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.tl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.tl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.tr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.tr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.tr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.tr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.tr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.uk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.uk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.uk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.uk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.uk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.uk_UA.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.uk_UA.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.uk_UA.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.uk_UA.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.uk_UA.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.vi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.vi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.vi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.vi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.vi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.zh_Hans_CN.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.zh_Hans_CN.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.zh_Hans_CN.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.zh_Hans_CN.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.zh_Hans_CN.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.i18n.zh_Hant_TW.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.i18n.zh_Hant_TW.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.i18n.zh_Hant_TW.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.i18n.zh_Hant_TW.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckan.i18n.zh_Hant_TW.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.lib' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.lib' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.lib' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.lib' to be distributed and are
          already explicitly excluding 'ckan.lib' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.lib.dictization' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.lib.dictization' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.lib.dictization' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.lib.dictization' to be distributed and are
          already explicitly excluding 'ckan.lib.dictization' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.lib.navl' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.lib.navl' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.lib.navl' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.lib.navl' to be distributed and are
          already explicitly excluding 'ckan.lib.navl' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.lib.search' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.lib.search' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.lib.search' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.lib.search' to be distributed and are
          already explicitly excluding 'ckan.lib.search' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.logic' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.logic' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.logic' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.logic' to be distributed and are
          already explicitly excluding 'ckan.logic' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.logic.action' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.logic.action' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.logic.action' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.logic.action' to be distributed and are
          already explicitly excluding 'ckan.logic.action' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.logic.auth' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.logic.auth' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.logic.auth' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.logic.auth' to be distributed and are
          already explicitly excluding 'ckan.logic.auth' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.migration' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.migration' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.migration' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.migration' to be distributed and are
          already explicitly excluding 'ckan.migration' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.migration.versions' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.migration.versions' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.migration.versions' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.migration.versions' to be distributed and are
          already explicitly excluding 'ckan.migration.versions' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.model' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.model' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.model' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.model' to be distributed and are
          already explicitly excluding 'ckan.model' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.plugins' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.plugins' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.plugins' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.plugins' to be distributed and are
          already explicitly excluding 'ckan.plugins' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base' to be distributed and are
          already explicitly excluding 'ckan.public.base' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.css' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.css' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.css' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.css' to be distributed and are
          already explicitly excluding 'ckan.public.base.css' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.i18n' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.i18n' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.i18n' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.i18n' to be distributed and are
          already explicitly excluding 'ckan.public.base.i18n' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.images' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.images' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.images' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.images' to be distributed and are
          already explicitly excluding 'ckan.public.base.images' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.javascript' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.javascript' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.javascript' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.javascript' to be distributed and are
          already explicitly excluding 'ckan.public.base.javascript' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.javascript.modules' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.javascript.modules' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.javascript.modules' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.javascript.modules' to be distributed and are
          already explicitly excluding 'ckan.public.base.javascript.modules' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.javascript.plugins' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.javascript.plugins' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.javascript.plugins' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.javascript.plugins' to be distributed and are
          already explicitly excluding 'ckan.public.base.javascript.plugins' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.scss' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.scss' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.scss' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.scss' to be distributed and are
          already explicitly excluding 'ckan.public.base.scss' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.vendor' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.vendor' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.vendor' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.vendor' to be distributed and are
          already explicitly excluding 'ckan.public.base.vendor' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.vendor.bootstrap.css' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.vendor.bootstrap.css' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.vendor.bootstrap.css' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.vendor.bootstrap.css' to be distributed and are
          already explicitly excluding 'ckan.public.base.vendor.bootstrap.css' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.vendor.bootstrap.js' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.vendor.bootstrap.js' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.vendor.bootstrap.js' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.vendor.bootstrap.js' to be distributed and are
          already explicitly excluding 'ckan.public.base.vendor.bootstrap.js' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.vendor.bootstrap.js.dom' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.vendor.bootstrap.js.dom' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.vendor.bootstrap.js.dom' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.vendor.bootstrap.js.dom' to be distributed and are
          already explicitly excluding 'ckan.public.base.vendor.bootstrap.js.dom' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.vendor.bootstrap.scss' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.vendor.bootstrap.scss' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.vendor.bootstrap.scss' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.vendor.bootstrap.scss' to be distributed and are
          already explicitly excluding 'ckan.public.base.vendor.bootstrap.scss' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.vendor.bootstrap.scss.forms' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.vendor.bootstrap.scss.forms' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.vendor.bootstrap.scss.forms' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.vendor.bootstrap.scss.forms' to be distributed and are
          already explicitly excluding 'ckan.public.base.vendor.bootstrap.scss.forms' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.vendor.bootstrap.scss.helpers' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.vendor.bootstrap.scss.helpers' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.vendor.bootstrap.scss.helpers' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.vendor.bootstrap.scss.helpers' to be distributed and are
          already explicitly excluding 'ckan.public.base.vendor.bootstrap.scss.helpers' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.vendor.bootstrap.scss.mixins' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.vendor.bootstrap.scss.mixins' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.vendor.bootstrap.scss.mixins' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.vendor.bootstrap.scss.mixins' to be distributed and are
          already explicitly excluding 'ckan.public.base.vendor.bootstrap.scss.mixins' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.vendor.bootstrap.scss.utilities' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.vendor.bootstrap.scss.utilities' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.vendor.bootstrap.scss.utilities' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.vendor.bootstrap.scss.utilities' to be distributed and are
          already explicitly excluding 'ckan.public.base.vendor.bootstrap.scss.utilities' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.vendor.bootstrap.scss.vendor' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.vendor.bootstrap.scss.vendor' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.vendor.bootstrap.scss.vendor' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.vendor.bootstrap.scss.vendor' to be distributed and are
          already explicitly excluding 'ckan.public.base.vendor.bootstrap.scss.vendor' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.public.base.vendor.select2' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.public.base.vendor.select2' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.public.base.vendor.select2' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.public.base.vendor.select2' to be distributed and are
          already explicitly excluding 'ckan.public.base.vendor.select2' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates' to be distributed and are
          already explicitly excluding 'ckan.templates' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.activity_streams' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.activity_streams' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.activity_streams' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.activity_streams' to be distributed and are
          already explicitly excluding 'ckan.templates.activity_streams' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.admin' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.admin' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.admin' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.admin' to be distributed and are
          already explicitly excluding 'ckan.templates.admin' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.admin.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.admin.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.admin.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.admin.snippets' to be distributed and are
          already explicitly excluding 'ckan.templates.admin.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.ajax_snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.ajax_snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.ajax_snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.ajax_snippets' to be distributed and are
          already explicitly excluding 'ckan.templates.ajax_snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.dataviewer' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.dataviewer' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.dataviewer' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.dataviewer' to be distributed and are
          already explicitly excluding 'ckan.templates.dataviewer' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.development' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.development' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.development' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.development' to be distributed and are
          already explicitly excluding 'ckan.templates.development' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.development.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.development.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.development.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.development.snippets' to be distributed and are
          already explicitly excluding 'ckan.templates.development.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.emails' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.emails' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.emails' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.emails' to be distributed and are
          already explicitly excluding 'ckan.templates.emails' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.group' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.group' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.group' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.group' to be distributed and are
          already explicitly excluding 'ckan.templates.group' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.group.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.group.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.group.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.group.snippets' to be distributed and are
          already explicitly excluding 'ckan.templates.group.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.home' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.home' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.home' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.home' to be distributed and are
          already explicitly excluding 'ckan.templates.home' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.home.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.home.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.home.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.home.snippets' to be distributed and are
          already explicitly excluding 'ckan.templates.home.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.macros' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.macros' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.macros' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.macros' to be distributed and are
          already explicitly excluding 'ckan.templates.macros' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.macros.form' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.macros.form' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.macros.form' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.macros.form' to be distributed and are
          already explicitly excluding 'ckan.templates.macros.form' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.organization' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.organization' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.organization' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.organization' to be distributed and are
          already explicitly excluding 'ckan.templates.organization' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.organization.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.organization.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.organization.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.organization.snippets' to be distributed and are
          already explicitly excluding 'ckan.templates.organization.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.package' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.package' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.package' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.package' to be distributed and are
          already explicitly excluding 'ckan.templates.package' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.package.collaborators' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.package.collaborators' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.package.collaborators' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.package.collaborators' to be distributed and are
          already explicitly excluding 'ckan.templates.package.collaborators' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.package.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.package.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.package.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.package.snippets' to be distributed and are
          already explicitly excluding 'ckan.templates.package.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.revision' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.revision' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.revision' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.revision' to be distributed and are
          already explicitly excluding 'ckan.templates.revision' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.snippets' to be distributed and are
          already explicitly excluding 'ckan.templates.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.snippets.context' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.snippets.context' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.snippets.context' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.snippets.context' to be distributed and are
          already explicitly excluding 'ckan.templates.snippets.context' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.tests' to be distributed and are
          already explicitly excluding 'ckan.templates.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.user' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.user' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.user' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.user' to be distributed and are
          already explicitly excluding 'ckan.templates.user' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.templates.user.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.templates.user.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.templates.user.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.templates.user.snippets' to be distributed and are
          already explicitly excluding 'ckan.templates.user.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests' to be distributed and are
          already explicitly excluding 'ckan.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.cli' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.cli' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.cli' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.cli' to be distributed and are
          already explicitly excluding 'ckan.tests.cli' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.cli.data' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.cli.data' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.cli.data' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.cli.data' to be distributed and are
          already explicitly excluding 'ckan.tests.cli.data' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.cli.data.sub' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.cli.data.sub' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.cli.data.sub' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.cli.data.sub' to be distributed and are
          already explicitly excluding 'ckan.tests.cli.data.sub' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.config' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.config' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.config' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.config' to be distributed and are
          already explicitly excluding 'ckan.tests.config' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.config.declaration' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.config.declaration' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.config.declaration' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.config.declaration' to be distributed and are
          already explicitly excluding 'ckan.tests.config.declaration' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.controllers' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.controllers' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.controllers' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.controllers' to be distributed and are
          already explicitly excluding 'ckan.tests.controllers' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.i18n' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.i18n' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.i18n' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.i18n' to be distributed and are
          already explicitly excluding 'ckan.tests.i18n' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.lib' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.lib' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.lib' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.lib' to be distributed and are
          already explicitly excluding 'ckan.tests.lib' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.lib.dictization' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.lib.dictization' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.lib.dictization' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.lib.dictization' to be distributed and are
          already explicitly excluding 'ckan.tests.lib.dictization' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.lib.navl' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.lib.navl' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.lib.navl' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.lib.navl' to be distributed and are
          already explicitly excluding 'ckan.tests.lib.navl' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.lib.search' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.lib.search' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.lib.search' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.lib.search' to be distributed and are
          already explicitly excluding 'ckan.tests.lib.search' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.logic' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.logic' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.logic' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.logic' to be distributed and are
          already explicitly excluding 'ckan.tests.logic' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.logic.action' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.logic.action' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.logic.action' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.logic.action' to be distributed and are
          already explicitly excluding 'ckan.tests.logic.action' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.logic.auth' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.logic.auth' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.logic.auth' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.logic.auth' to be distributed and are
          already explicitly excluding 'ckan.tests.logic.auth' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.model' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.model' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.model' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.model' to be distributed and are
          already explicitly excluding 'ckan.tests.model' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.plugins' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.plugins' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.plugins' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.plugins' to be distributed and are
          already explicitly excluding 'ckan.tests.plugins' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.tests.pytest_ckan' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.tests.pytest_ckan' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.tests.pytest_ckan' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.tests.pytest_ckan' to be distributed and are
          already explicitly excluding 'ckan.tests.pytest_ckan' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.types' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.types' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.types' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.types' to be distributed and are
          already explicitly excluding 'ckan.types' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.types.logic' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.types.logic' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.types.logic' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.types.logic' to be distributed and are
          already explicitly excluding 'ckan.types.logic' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckan.views' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckan.views' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckan.views' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckan.views' to be distributed and are
          already explicitly excluding 'ckan.views' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity' to be distributed and are
          already explicitly excluding 'ckanext.activity' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.assets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.assets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.assets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.assets' to be distributed and are
          already explicitly excluding 'ckanext.activity.assets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.logic' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.logic' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.logic' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.logic' to be distributed and are
          already explicitly excluding 'ckanext.activity.logic' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.model' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.model' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.model' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.model' to be distributed and are
          already explicitly excluding 'ckanext.activity.model' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.public' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.public' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.public' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.public' to be distributed and are
          already explicitly excluding 'ckanext.activity.public' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.activity_streams' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.activity_streams' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.activity_streams' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.activity_streams' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.activity_streams' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.ajax_snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.ajax_snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.ajax_snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.ajax_snippets' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.ajax_snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.group' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.group' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.group' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.group' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.group' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.group.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.group.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.group.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.group.snippets' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.group.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.organization' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.organization' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.organization' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.organization' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.organization' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.organization.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.organization.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.organization.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.organization.snippets' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.organization.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.package' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.package' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.package' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.package' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.package' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.package.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.package.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.package.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.package.snippets' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.package.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.snippets' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.snippets.activities' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.snippets.activities' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.snippets.activities' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.snippets.activities' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.snippets.activities' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.snippets.changes' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.snippets.changes' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.snippets.changes' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.snippets.changes' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.snippets.changes' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.snippets.group_changes' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.snippets.group_changes' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.snippets.group_changes' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.snippets.group_changes' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.snippets.group_changes' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.snippets.organization_changes' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.snippets.organization_changes' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.snippets.organization_changes' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.snippets.organization_changes' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.snippets.organization_changes' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.user' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.user' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.user' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.user' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.user' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.templates.user.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.templates.user.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.templates.user.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.templates.user.snippets' to be distributed and are
          already explicitly excluding 'ckanext.activity.templates.user.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.tests' to be distributed and are
          already explicitly excluding 'ckanext.activity.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.tests.logic' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.tests.logic' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.tests.logic' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.tests.logic' to be distributed and are
          already explicitly excluding 'ckanext.activity.tests.logic' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.activity.tests.model' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.activity.tests.model' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.activity.tests.model' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.activity.tests.model' to be distributed and are
          already explicitly excluding 'ckanext.activity.tests.model' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.audioview' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.audioview' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.audioview' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.audioview' to be distributed and are
          already explicitly excluding 'ckanext.audioview' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.audioview.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.audioview.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.audioview.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.audioview.tests' to be distributed and are
          already explicitly excluding 'ckanext.audioview.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.audioview.theme.templates' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.audioview.theme.templates' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.audioview.theme.templates' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.audioview.theme.templates' to be distributed and are
          already explicitly excluding 'ckanext.audioview.theme.templates' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.chained_functions' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.chained_functions' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.chained_functions' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.chained_functions' to be distributed and are
          already explicitly excluding 'ckanext.chained_functions' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.chained_functions.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.chained_functions.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.chained_functions.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.chained_functions.tests' to be distributed and are
          already explicitly excluding 'ckanext.chained_functions.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datapusher' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datapusher' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datapusher' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datapusher' to be distributed and are
          already explicitly excluding 'ckanext.datapusher' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datapusher.assets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datapusher.assets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datapusher.assets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datapusher.assets' to be distributed and are
          already explicitly excluding 'ckanext.datapusher.assets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datapusher.logic' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datapusher.logic' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datapusher.logic' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datapusher.logic' to be distributed and are
          already explicitly excluding 'ckanext.datapusher.logic' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datapusher.public' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datapusher.public' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datapusher.public' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datapusher.public' to be distributed and are
          already explicitly excluding 'ckanext.datapusher.public' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datapusher.templates.datapusher' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datapusher.templates.datapusher' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datapusher.templates.datapusher' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datapusher.templates.datapusher' to be distributed and are
          already explicitly excluding 'ckanext.datapusher.templates.datapusher' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datapusher.templates.package' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datapusher.templates.package' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datapusher.templates.package' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datapusher.templates.package' to be distributed and are
          already explicitly excluding 'ckanext.datapusher.templates.package' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datapusher.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datapusher.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datapusher.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datapusher.tests' to be distributed and are
          already explicitly excluding 'ckanext.datapusher.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datastore' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datastore' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datastore' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datastore' to be distributed and are
          already explicitly excluding 'ckanext.datastore' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datastore.backend' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datastore.backend' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datastore.backend' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datastore.backend' to be distributed and are
          already explicitly excluding 'ckanext.datastore.backend' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datastore.logic' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datastore.logic' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datastore.logic' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datastore.logic' to be distributed and are
          already explicitly excluding 'ckanext.datastore.logic' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datastore.templates.ajax_snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datastore.templates.ajax_snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datastore.templates.ajax_snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datastore.templates.ajax_snippets' to be distributed and are
          already explicitly excluding 'ckanext.datastore.templates.ajax_snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datastore.templates.datastore' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datastore.templates.datastore' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datastore.templates.datastore' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datastore.templates.datastore' to be distributed and are
          already explicitly excluding 'ckanext.datastore.templates.datastore' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datastore.templates.datastore.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datastore.templates.datastore.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datastore.templates.datastore.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datastore.templates.datastore.snippets' to be distributed and are
          already explicitly excluding 'ckanext.datastore.templates.datastore.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datastore.templates.package' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datastore.templates.package' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datastore.templates.package' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datastore.templates.package' to be distributed and are
          already explicitly excluding 'ckanext.datastore.templates.package' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datastore.templates.package.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datastore.templates.package.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datastore.templates.package.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datastore.templates.package.snippets' to be distributed and are
          already explicitly excluding 'ckanext.datastore.templates.package.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datastore.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datastore.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datastore.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datastore.tests' to be distributed and are
          already explicitly excluding 'ckanext.datastore.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datatablesview' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datatablesview' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datatablesview' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datatablesview' to be distributed and are
          already explicitly excluding 'ckanext.datatablesview' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datatablesview.public' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datatablesview.public' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datatablesview.public' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datatablesview.public' to be distributed and are
          already explicitly excluding 'ckanext.datatablesview.public' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datatablesview.public.vendor.DataTables' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datatablesview.public.vendor.DataTables' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datatablesview.public.vendor.DataTables' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datatablesview.public.vendor.DataTables' to be distributed and are
          already explicitly excluding 'ckanext.datatablesview.public.vendor.DataTables' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datatablesview.public.vendor.DataTables.i18n' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datatablesview.public.vendor.DataTables.i18n' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datatablesview.public.vendor.DataTables.i18n' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datatablesview.public.vendor.DataTables.i18n' to be distributed and are
          already explicitly excluding 'ckanext.datatablesview.public.vendor.DataTables.i18n' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datatablesview.public.vendor.FontAwesome.images' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datatablesview.public.vendor.FontAwesome.images' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datatablesview.public.vendor.FontAwesome.images' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datatablesview.public.vendor.FontAwesome.images' to be distributed and are
          already explicitly excluding 'ckanext.datatablesview.public.vendor.FontAwesome.images' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.datatablesview.templates.datatables' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.datatablesview.templates.datatables' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.datatablesview.templates.datatables' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.datatablesview.templates.datatables' to be distributed and are
          already explicitly excluding 'ckanext.datatablesview.templates.datatables' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_blanket_implementation' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_blanket_implementation' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_blanket_implementation' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_blanket_implementation' to be distributed and are
          already explicitly excluding 'ckanext.example_blanket_implementation' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_blanket_implementation.logic' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_blanket_implementation.logic' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_blanket_implementation.logic' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_blanket_implementation.logic' to be distributed and are
          already explicitly excluding 'ckanext.example_blanket_implementation.logic' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_blanket_implementation.logic.action' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_blanket_implementation.logic.action' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_blanket_implementation.logic.action' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_blanket_implementation.logic.action' to be distributed and are
          already explicitly excluding 'ckanext.example_blanket_implementation.logic.action' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_database_migrations' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_database_migrations' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_database_migrations' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_database_migrations' to be distributed and are
          already explicitly excluding 'ckanext.example_database_migrations' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_database_migrations.migration.example_database_migrations' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_database_migrations.migration.example_database_migrations' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_database_migrations.migration.example_database_migrations' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_database_migrations.migration.example_database_migrations' to be distributed and are
          already explicitly excluding 'ckanext.example_database_migrations.migration.example_database_migrations' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_database_migrations.migration.example_database_migrations.versions' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_database_migrations.migration.example_database_migrations.versions' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_database_migrations.migration.example_database_migrations.versions' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_database_migrations.migration.example_database_migrations.versions' to be distributed and are
          already explicitly excluding 'ckanext.example_database_migrations.migration.example_database_migrations.versions' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_flask_iblueprint' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_flask_iblueprint' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_flask_iblueprint' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_flask_iblueprint' to be distributed and are
          already explicitly excluding 'ckanext.example_flask_iblueprint' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_flask_iblueprint.templates' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_flask_iblueprint.templates' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_flask_iblueprint.templates' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_flask_iblueprint.templates' to be distributed and are
          already explicitly excluding 'ckanext.example_flask_iblueprint.templates' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_flask_iblueprint.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_flask_iblueprint.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_flask_iblueprint.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_flask_iblueprint.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_flask_iblueprint.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_flask_streaming' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_flask_streaming' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_flask_streaming' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_flask_streaming' to be distributed and are
          already explicitly excluding 'ckanext.example_flask_streaming' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_flask_streaming.templates' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_flask_streaming.templates' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_flask_streaming.templates' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_flask_streaming.templates' to be distributed and are
          already explicitly excluding 'ckanext.example_flask_streaming.templates' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_flask_streaming.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_flask_streaming.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_flask_streaming.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_flask_streaming.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_flask_streaming.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_humanizer' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_humanizer' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_humanizer' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_humanizer' to be distributed and are
          already explicitly excluding 'ckanext.example_humanizer' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_humanizer.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_humanizer.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_humanizer.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_humanizer.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_humanizer.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iapitoken' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iapitoken' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iapitoken' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iapitoken' to be distributed and are
          already explicitly excluding 'ckanext.example_iapitoken' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iapitoken.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iapitoken.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iapitoken.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iapitoken.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_iapitoken.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iauthenticator' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iauthenticator' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iauthenticator' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iauthenticator' to be distributed and are
          already explicitly excluding 'ckanext.example_iauthenticator' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iauthenticator.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iauthenticator.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iauthenticator.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iauthenticator.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_iauthenticator.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iauthfunctions' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iauthfunctions' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iauthfunctions' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iauthfunctions' to be distributed and are
          already explicitly excluding 'ckanext.example_iauthfunctions' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iauthfunctions.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iauthfunctions.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iauthfunctions.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iauthfunctions.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_iauthfunctions.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iclick' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iclick' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iclick' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iclick' to be distributed and are
          already explicitly excluding 'ckanext.example_iclick' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iconfigurer' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iconfigurer' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iconfigurer' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iconfigurer' to be distributed and are
          already explicitly excluding 'ckanext.example_iconfigurer' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iconfigurer.templates.admin' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iconfigurer.templates.admin' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iconfigurer.templates.admin' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iconfigurer.templates.admin' to be distributed and are
          already explicitly excluding 'ckanext.example_iconfigurer.templates.admin' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iconfigurer.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iconfigurer.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iconfigurer.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iconfigurer.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_iconfigurer.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_idatasetform' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_idatasetform' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_idatasetform' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_idatasetform' to be distributed and are
          already explicitly excluding 'ckanext.example_idatasetform' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_idatasetform.templates.first' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_idatasetform.templates.first' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_idatasetform.templates.first' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_idatasetform.templates.first' to be distributed and are
          already explicitly excluding 'ckanext.example_idatasetform.templates.first' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_idatasetform.templates.package' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_idatasetform.templates.package' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_idatasetform.templates.package' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_idatasetform.templates.package' to be distributed and are
          already explicitly excluding 'ckanext.example_idatasetform.templates.package' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_idatasetform.templates.package.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_idatasetform.templates.package.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_idatasetform.templates.package.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_idatasetform.templates.package.snippets' to be distributed and are
          already explicitly excluding 'ckanext.example_idatasetform.templates.package.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_idatasetform.templates.second' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_idatasetform.templates.second' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_idatasetform.templates.second' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_idatasetform.templates.second' to be distributed and are
          already explicitly excluding 'ckanext.example_idatasetform.templates.second' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_idatasetform.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_idatasetform.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_idatasetform.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_idatasetform.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_idatasetform.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_idatastorebackend' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_idatastorebackend' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_idatastorebackend' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_idatastorebackend' to be distributed and are
          already explicitly excluding 'ckanext.example_idatastorebackend' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_idatastorebackend.test' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_idatastorebackend.test' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_idatastorebackend.test' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_idatastorebackend.test' to be distributed and are
          already explicitly excluding 'ckanext.example_idatastorebackend.test' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_igroupform' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_igroupform' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_igroupform' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_igroupform' to be distributed and are
          already explicitly excluding 'ckanext.example_igroupform' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_igroupform.templates.example_igroup_form' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_igroupform.templates.example_igroup_form' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_igroupform.templates.example_igroup_form' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_igroupform.templates.example_igroup_form' to be distributed and are
          already explicitly excluding 'ckanext.example_igroupform.templates.example_igroup_form' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_igroupform.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_igroupform.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_igroupform.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_igroupform.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_igroupform.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_ipermissionlabels' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_ipermissionlabels' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_ipermissionlabels' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_ipermissionlabels' to be distributed and are
          already explicitly excluding 'ckanext.example_ipermissionlabels' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_ipermissionlabels.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_ipermissionlabels.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_ipermissionlabels.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_ipermissionlabels.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_ipermissionlabels.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iresourcecontroller' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iresourcecontroller' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iresourcecontroller' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iresourcecontroller' to be distributed and are
          already explicitly excluding 'ckanext.example_iresourcecontroller' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iresourcecontroller.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iresourcecontroller.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iresourcecontroller.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iresourcecontroller.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_iresourcecontroller.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_isignal' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_isignal' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_isignal' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_isignal' to be distributed and are
          already explicitly excluding 'ckanext.example_isignal' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_isignal.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_isignal.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_isignal.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_isignal.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_isignal.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_itemplatehelpers' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_itemplatehelpers' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_itemplatehelpers' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_itemplatehelpers' to be distributed and are
          already explicitly excluding 'ckanext.example_itemplatehelpers' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_itemplatehelpers.templates.home' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_itemplatehelpers.templates.home' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_itemplatehelpers.templates.home' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_itemplatehelpers.templates.home' to be distributed and are
          already explicitly excluding 'ckanext.example_itemplatehelpers.templates.home' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_itemplatehelpers.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_itemplatehelpers.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_itemplatehelpers.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_itemplatehelpers.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_itemplatehelpers.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_itranslation' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_itranslation' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_itranslation' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_itranslation' to be distributed and are
          already explicitly excluding 'ckanext.example_itranslation' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_itranslation.i18n' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_itranslation.i18n' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_itranslation.i18n' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_itranslation.i18n' to be distributed and are
          already explicitly excluding 'ckanext.example_itranslation.i18n' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_itranslation.i18n.en.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_itranslation.i18n.en.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_itranslation.i18n.en.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_itranslation.i18n.en.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckanext.example_itranslation.i18n.en.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_itranslation.i18n.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_itranslation.i18n.fr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_itranslation.i18n.fr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_itranslation.i18n.fr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'ckanext.example_itranslation.i18n.fr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_itranslation.templates.home' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_itranslation.templates.home' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_itranslation.templates.home' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_itranslation.templates.home' to be distributed and are
          already explicitly excluding 'ckanext.example_itranslation.templates.home' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_itranslation.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_itranslation.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_itranslation.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_itranslation.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_itranslation.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iuploader' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iuploader' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iuploader' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iuploader' to be distributed and are
          already explicitly excluding 'ckanext.example_iuploader' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_iuploader.test' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_iuploader.test' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_iuploader.test' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_iuploader.test' to be distributed and are
          already explicitly excluding 'ckanext.example_iuploader.test' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_ivalidators' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_ivalidators' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_ivalidators' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_ivalidators' to be distributed and are
          already explicitly excluding 'ckanext.example_ivalidators' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_ivalidators.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_ivalidators.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_ivalidators.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_ivalidators.tests' to be distributed and are
          already explicitly excluding 'ckanext.example_ivalidators.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.custom_config_setting' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.custom_config_setting' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.custom_config_setting' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.custom_config_setting' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.custom_config_setting' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.custom_emails' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.custom_emails' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.custom_emails' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.custom_emails' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.custom_emails' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v01_empty_extension' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v01_empty_extension' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v01_empty_extension' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v01_empty_extension' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v01_empty_extension' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v02_empty_template' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v02_empty_template' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v02_empty_template' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v02_empty_template' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v02_empty_template' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v03_jinja' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v03_jinja' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v03_jinja' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v03_jinja' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v03_jinja' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v04_ckan_extends' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v04_ckan_extends' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v04_ckan_extends' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v04_ckan_extends' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v04_ckan_extends' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v05_block' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v05_block' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v05_block' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v05_block' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v05_block' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v06_super' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v06_super' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v06_super' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v06_super' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v06_super' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v07_helper_function' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v07_helper_function' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v07_helper_function' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v07_helper_function' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v07_helper_function' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v08_custom_helper_function' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v08_custom_helper_function' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v08_custom_helper_function' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v08_custom_helper_function' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v08_custom_helper_function' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v09_snippet' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v09_snippet' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v09_snippet' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v09_snippet' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v09_snippet' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v10_custom_snippet' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v10_custom_snippet' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v10_custom_snippet' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v10_custom_snippet' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v10_custom_snippet' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v11_HTML_and_CSS' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v11_HTML_and_CSS' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v11_HTML_and_CSS' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v11_HTML_and_CSS' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v11_HTML_and_CSS' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v12_extra_public_dir' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v12_extra_public_dir' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v12_extra_public_dir' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v12_extra_public_dir' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v12_extra_public_dir' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v13_custom_css' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v13_custom_css' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v13_custom_css' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v13_custom_css' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v13_custom_css' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v14_more_custom_css' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v14_more_custom_css' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v14_more_custom_css' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v14_more_custom_css' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v14_more_custom_css' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v15_webassets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v15_webassets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v15_webassets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v15_webassets' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v15_webassets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v16_initialize_a_javascript_module' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v16_initialize_a_javascript_module' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v16_initialize_a_javascript_module' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v16_initialize_a_javascript_module' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v16_initialize_a_javascript_module' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v17_popover' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v17_popover' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v17_popover' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v17_popover' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v17_popover' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v18_snippet_api' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v18_snippet_api' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v18_snippet_api' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v18_snippet_api' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v18_snippet_api' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v19_01_error' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v19_01_error' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v19_01_error' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v19_01_error' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v19_01_error' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v19_02_error_handling' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v19_02_error_handling' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v19_02_error_handling' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v19_02_error_handling' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v19_02_error_handling' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v20_pubsub' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v20_pubsub' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v20_pubsub' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v20_pubsub' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v20_pubsub' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v21_custom_jquery_plugin' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v21_custom_jquery_plugin' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v21_custom_jquery_plugin' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v21_custom_jquery_plugin' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v21_custom_jquery_plugin' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.example_theme_docs.v22_webassets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.example_theme_docs.v22_webassets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.example_theme_docs.v22_webassets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.example_theme_docs.v22_webassets' to be distributed and are
          already explicitly excluding 'ckanext.example_theme_docs.v22_webassets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.expire_api_token' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.expire_api_token' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.expire_api_token' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.expire_api_token' to be distributed and are
          already explicitly excluding 'ckanext.expire_api_token' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.expire_api_token.templates.user' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.expire_api_token.templates.user' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.expire_api_token.templates.user' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.expire_api_token.templates.user' to be distributed and are
          already explicitly excluding 'ckanext.expire_api_token.templates.user' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.expire_api_token.templates.user.snippets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.expire_api_token.templates.user.snippets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.expire_api_token.templates.user.snippets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.expire_api_token.templates.user.snippets' to be distributed and are
          already explicitly excluding 'ckanext.expire_api_token.templates.user.snippets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.expire_api_token.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.expire_api_token.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.expire_api_token.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.expire_api_token.tests' to be distributed and are
          already explicitly excluding 'ckanext.expire_api_token.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.imageview' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.imageview' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.imageview' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.imageview' to be distributed and are
          already explicitly excluding 'ckanext.imageview' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.imageview.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.imageview.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.imageview.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.imageview.tests' to be distributed and are
          already explicitly excluding 'ckanext.imageview.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.imageview.theme.templates' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.imageview.theme.templates' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.imageview.theme.templates' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.imageview.theme.templates' to be distributed and are
          already explicitly excluding 'ckanext.imageview.theme.templates' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.multilingual' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.multilingual' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.multilingual' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.multilingual' to be distributed and are
          already explicitly excluding 'ckanext.multilingual' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.multilingual.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.multilingual.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.multilingual.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.multilingual.tests' to be distributed and are
          already explicitly excluding 'ckanext.multilingual.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview' to be distributed and are
          already explicitly excluding 'ckanext.reclineview' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.tests' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.css' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.css' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.css' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.css' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.css' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.img' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.img' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.img' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.img' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.img' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.backbone' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.backbone' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.backbone' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.backbone' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.backbone' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.bootstrap' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.bootstrap' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.bootstrap' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.bootstrap' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.bootstrap' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.flot' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.flot' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.flot' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.flot' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.flot' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.flotr2' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.flotr2' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.flotr2' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.flotr2' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.flotr2' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.jquery' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.jquery' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.jquery' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.jquery' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.jquery' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.json' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.json' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.json' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.json' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.json' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.leaflet' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.leaflet' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.leaflet' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.leaflet' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.leaflet' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.moment' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.moment' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.moment' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.moment' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.moment' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.mustache' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.mustache' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.mustache' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.mustache' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.mustache' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.recline' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.recline' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.recline' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.recline' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.recline' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.showdown' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.showdown' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.showdown' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.showdown' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.showdown' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.slickgrid' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.slickgrid' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.slickgrid' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.slickgrid' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.slickgrid' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.timeline' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.timeline' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.timeline' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.timeline' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.timeline' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.timeline.css' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.timeline.css' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.timeline.css' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.timeline.css' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.timeline.css' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.timeline.js' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.timeline.js' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.timeline.js' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.timeline.js' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.timeline.js' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.public.vendor.underscore' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.public.vendor.underscore' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.public.vendor.underscore' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.public.vendor.underscore' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.public.vendor.underscore' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.reclineview.theme.templates' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.reclineview.theme.templates' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.reclineview.theme.templates' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.reclineview.theme.templates' to be distributed and are
          already explicitly excluding 'ckanext.reclineview.theme.templates' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.resourceproxy' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.resourceproxy' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.resourceproxy' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.resourceproxy' to be distributed and are
          already explicitly excluding 'ckanext.resourceproxy' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.resourceproxy.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.resourceproxy.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.resourceproxy.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.resourceproxy.tests' to be distributed and are
          already explicitly excluding 'ckanext.resourceproxy.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.stats' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.stats' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.stats' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.stats' to be distributed and are
          already explicitly excluding 'ckanext.stats' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.stats.public' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.stats.public' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.stats.public' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.stats.public' to be distributed and are
          already explicitly excluding 'ckanext.stats.public' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.stats.public.ckanext' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.stats.public.ckanext' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.stats.public.ckanext' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.stats.public.ckanext' to be distributed and are
          already explicitly excluding 'ckanext.stats.public.ckanext' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.stats.public.ckanext.stats' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.stats.public.ckanext.stats' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.stats.public.ckanext.stats' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.stats.public.ckanext.stats' to be distributed and are
          already explicitly excluding 'ckanext.stats.public.ckanext.stats' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.stats.public.ckanext.stats.css' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.stats.public.ckanext.stats.css' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.stats.public.ckanext.stats.css' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.stats.public.ckanext.stats.css' to be distributed and are
          already explicitly excluding 'ckanext.stats.public.ckanext.stats.css' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.stats.public.ckanext.stats.javascript.modules' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.stats.public.ckanext.stats.javascript.modules' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.stats.public.ckanext.stats.javascript.modules' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.stats.public.ckanext.stats.javascript.modules' to be distributed and are
          already explicitly excluding 'ckanext.stats.public.ckanext.stats.javascript.modules' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.stats.public.ckanext.stats.test' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.stats.public.ckanext.stats.test' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.stats.public.ckanext.stats.test' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.stats.public.ckanext.stats.test' to be distributed and are
          already explicitly excluding 'ckanext.stats.public.ckanext.stats.test' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.stats.public.ckanext.stats.test.fixtures' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.stats.public.ckanext.stats.test.fixtures' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.stats.public.ckanext.stats.test.fixtures' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.stats.public.ckanext.stats.test.fixtures' to be distributed and are
          already explicitly excluding 'ckanext.stats.public.ckanext.stats.test.fixtures' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.stats.public.ckanext.stats.test.spec.modules' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.stats.public.ckanext.stats.test.spec.modules' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.stats.public.ckanext.stats.test.spec.modules' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.stats.public.ckanext.stats.test.spec.modules' to be distributed and are
          already explicitly excluding 'ckanext.stats.public.ckanext.stats.test.spec.modules' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.stats.public.ckanext.stats.vendor' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.stats.public.ckanext.stats.vendor' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.stats.public.ckanext.stats.vendor' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.stats.public.ckanext.stats.vendor' to be distributed and are
          already explicitly excluding 'ckanext.stats.public.ckanext.stats.vendor' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.stats.templates.ckanext.stats' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.stats.templates.ckanext.stats' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.stats.templates.ckanext.stats' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.stats.templates.ckanext.stats' to be distributed and are
          already explicitly excluding 'ckanext.stats.templates.ckanext.stats' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.stats.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.stats.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.stats.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.stats.tests' to be distributed and are
          already explicitly excluding 'ckanext.stats.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.textview' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.textview' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.textview' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.textview' to be distributed and are
          already explicitly excluding 'ckanext.textview' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.textview.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.textview.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.textview.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.textview.tests' to be distributed and are
          already explicitly excluding 'ckanext.textview.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.textview.theme.public' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.textview.theme.public' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.textview.theme.public' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.textview.theme.public' to be distributed and are
          already explicitly excluding 'ckanext.textview.theme.public' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.textview.theme.public.css' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.textview.theme.public.css' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.textview.theme.public.css' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.textview.theme.public.css' to be distributed and are
          already explicitly excluding 'ckanext.textview.theme.public.css' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.textview.theme.public.styles' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.textview.theme.public.styles' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.textview.theme.public.styles' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.textview.theme.public.styles' to be distributed and are
          already explicitly excluding 'ckanext.textview.theme.public.styles' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.textview.theme.public.vendor' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.textview.theme.public.vendor' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.textview.theme.public.vendor' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.textview.theme.public.vendor' to be distributed and are
          already explicitly excluding 'ckanext.textview.theme.public.vendor' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.textview.theme.templates' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.textview.theme.templates' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.textview.theme.templates' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.textview.theme.templates' to be distributed and are
          already explicitly excluding 'ckanext.textview.theme.templates' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.videoview' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.videoview' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.videoview' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.videoview' to be distributed and are
          already explicitly excluding 'ckanext.videoview' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.videoview.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.videoview.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.videoview.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.videoview.tests' to be distributed and are
          already explicitly excluding 'ckanext.videoview.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.videoview.theme.templates' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.videoview.theme.templates' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.videoview.theme.templates' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.videoview.theme.templates' to be distributed and are
          already explicitly excluding 'ckanext.videoview.theme.templates' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.webpageview' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.webpageview' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.webpageview' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.webpageview' to be distributed and are
          already explicitly excluding 'ckanext.webpageview' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.webpageview.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.webpageview.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.webpageview.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.webpageview.tests' to be distributed and are
          already explicitly excluding 'ckanext.webpageview.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'ckanext.webpageview.theme.templates' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'ckanext.webpageview.theme.templates' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'ckanext.webpageview.theme.templates' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'ckanext.webpageview.theme.templates' to be distributed and are
          already explicitly excluding 'ckanext.webpageview.theme.templates' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  creating build/lib/ckan/cli
  copying ckan/cli/__init__.py -> build/lib/ckan/cli
  copying ckan/cli/asset.py -> build/lib/ckan/cli
  copying ckan/cli/clean.py -> build/lib/ckan/cli
  copying ckan/cli/cli.py -> build/lib/ckan/cli
  copying ckan/cli/config.py -> build/lib/ckan/cli
  copying ckan/cli/config_tool.py -> build/lib/ckan/cli
  copying ckan/cli/dataset.py -> build/lib/ckan/cli
  copying ckan/cli/db.py -> build/lib/ckan/cli
  copying ckan/cli/generate.py -> build/lib/ckan/cli
  copying ckan/cli/jobs.py -> build/lib/ckan/cli
  copying ckan/cli/notify.py -> build/lib/ckan/cli
  copying ckan/cli/plugin_info.py -> build/lib/ckan/cli
  copying ckan/cli/profile.py -> build/lib/ckan/cli
  copying ckan/cli/sass.py -> build/lib/ckan/cli
  copying ckan/cli/search_index.py -> build/lib/ckan/cli
  copying ckan/cli/server.py -> build/lib/ckan/cli
  copying ckan/cli/shell.py -> build/lib/ckan/cli
  copying ckan/cli/sysadmin.py -> build/lib/ckan/cli
  copying ckan/cli/tracking.py -> build/lib/ckan/cli
  copying ckan/cli/translation.py -> build/lib/ckan/cli
  copying ckan/cli/user.py -> build/lib/ckan/cli
  copying ckan/cli/views.py -> build/lib/ckan/cli
  creating build/lib/ckan/config
  copying ckan/config/__init__.py -> build/lib/ckan/config
  copying ckan/config/config_declaration.yaml -> build/lib/ckan/config
  copying ckan/config/deployment.ini_tmpl -> build/lib/ckan/config
  copying ckan/config/environment.py -> build/lib/ckan/config
  copying ckan/config/resource_formats.json -> build/lib/ckan/config
  copying ckan/config/who.ini -> build/lib/ckan/config
  creating build/lib/ckan/config/declaration
  copying ckan/config/declaration/__init__.py -> build/lib/ckan/config/declaration
  copying ckan/config/declaration/describe.py -> build/lib/ckan/config/declaration
  copying ckan/config/declaration/key.py -> build/lib/ckan/config/declaration
  copying ckan/config/declaration/load.py -> build/lib/ckan/config/declaration
  copying ckan/config/declaration/option.py -> build/lib/ckan/config/declaration
  copying ckan/config/declaration/serialize.py -> build/lib/ckan/config/declaration
  copying ckan/config/declaration/utils.py -> build/lib/ckan/config/declaration
  creating build/lib/ckan/config/middleware
  copying ckan/config/middleware/__init__.py -> build/lib/ckan/config/middleware
  copying ckan/config/middleware/common_middleware.py -> build/lib/ckan/config/middleware
  copying ckan/config/middleware/flask_app.py -> build/lib/ckan/config/middleware
  creating build/lib/ckan/config/solr
  copying ckan/config/solr/schema.xml -> build/lib/ckan/config/solr
  creating build/lib/ckan/i18n
  copying ckan/i18n/__init__.py -> build/lib/ckan/i18n
  copying ckan/i18n/ckan.pot -> build/lib/ckan/i18n
  creating build/lib/ckan/i18n/am
  creating build/lib/ckan/i18n/am/LC_MESSAGES
  copying ckan/i18n/am/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/am/LC_MESSAGES
  copying ckan/i18n/am/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/am/LC_MESSAGES
  creating build/lib/ckan/i18n/ar
  creating build/lib/ckan/i18n/ar/LC_MESSAGES
  copying ckan/i18n/ar/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/ar/LC_MESSAGES
  copying ckan/i18n/ar/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/ar/LC_MESSAGES
  creating build/lib/ckan/i18n/bg
  creating build/lib/ckan/i18n/bg/LC_MESSAGES
  copying ckan/i18n/bg/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/bg/LC_MESSAGES
  copying ckan/i18n/bg/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/bg/LC_MESSAGES
  creating build/lib/ckan/i18n/bs
  creating build/lib/ckan/i18n/bs/LC_MESSAGES
  copying ckan/i18n/bs/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/bs/LC_MESSAGES
  copying ckan/i18n/bs/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/bs/LC_MESSAGES
  creating build/lib/ckan/i18n/ca
  creating build/lib/ckan/i18n/ca/LC_MESSAGES
  copying ckan/i18n/ca/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/ca/LC_MESSAGES
  copying ckan/i18n/ca/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/ca/LC_MESSAGES
  creating build/lib/ckan/i18n/cs_CZ
  creating build/lib/ckan/i18n/cs_CZ/LC_MESSAGES
  copying ckan/i18n/cs_CZ/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/cs_CZ/LC_MESSAGES
  copying ckan/i18n/cs_CZ/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/cs_CZ/LC_MESSAGES
  creating build/lib/ckan/i18n/da_DK
  creating build/lib/ckan/i18n/da_DK/LC_MESSAGES
  copying ckan/i18n/da_DK/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/da_DK/LC_MESSAGES
  copying ckan/i18n/da_DK/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/da_DK/LC_MESSAGES
  creating build/lib/ckan/i18n/de
  creating build/lib/ckan/i18n/de/LC_MESSAGES
  copying ckan/i18n/de/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/de/LC_MESSAGES
  copying ckan/i18n/de/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/de/LC_MESSAGES
  creating build/lib/ckan/i18n/el
  creating build/lib/ckan/i18n/el/LC_MESSAGES
  copying ckan/i18n/el/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/el/LC_MESSAGES
  copying ckan/i18n/el/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/el/LC_MESSAGES
  creating build/lib/ckan/i18n/en_AU
  creating build/lib/ckan/i18n/en_AU/LC_MESSAGES
  copying ckan/i18n/en_AU/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/en_AU/LC_MESSAGES
  copying ckan/i18n/en_AU/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/en_AU/LC_MESSAGES
  creating build/lib/ckan/i18n/en_GB
  creating build/lib/ckan/i18n/en_GB/LC_MESSAGES
  copying ckan/i18n/en_GB/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/en_GB/LC_MESSAGES
  copying ckan/i18n/en_GB/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/en_GB/LC_MESSAGES
  creating build/lib/ckan/i18n/es
  creating build/lib/ckan/i18n/es/LC_MESSAGES
  copying ckan/i18n/es/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/es/LC_MESSAGES
  copying ckan/i18n/es/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/es/LC_MESSAGES
  creating build/lib/ckan/i18n/es_AR
  creating build/lib/ckan/i18n/es_AR/LC_MESSAGES
  copying ckan/i18n/es_AR/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/es_AR/LC_MESSAGES
  copying ckan/i18n/es_AR/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/es_AR/LC_MESSAGES
  creating build/lib/ckan/i18n/eu
  creating build/lib/ckan/i18n/eu/LC_MESSAGES
  copying ckan/i18n/eu/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/eu/LC_MESSAGES
  copying ckan/i18n/eu/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/eu/LC_MESSAGES
  creating build/lib/ckan/i18n/fa_IR
  creating build/lib/ckan/i18n/fa_IR/LC_MESSAGES
  copying ckan/i18n/fa_IR/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/fa_IR/LC_MESSAGES
  copying ckan/i18n/fa_IR/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/fa_IR/LC_MESSAGES
  creating build/lib/ckan/i18n/fi
  creating build/lib/ckan/i18n/fi/LC_MESSAGES
  copying ckan/i18n/fi/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/fi/LC_MESSAGES
  copying ckan/i18n/fi/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/fi/LC_MESSAGES
  creating build/lib/ckan/i18n/fr
  creating build/lib/ckan/i18n/fr/LC_MESSAGES
  copying ckan/i18n/fr/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/fr/LC_MESSAGES
  copying ckan/i18n/fr/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/fr/LC_MESSAGES
  creating build/lib/ckan/i18n/gl
  creating build/lib/ckan/i18n/gl/LC_MESSAGES
  copying ckan/i18n/gl/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/gl/LC_MESSAGES
  copying ckan/i18n/gl/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/gl/LC_MESSAGES
  creating build/lib/ckan/i18n/he
  creating build/lib/ckan/i18n/he/LC_MESSAGES
  copying ckan/i18n/he/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/he/LC_MESSAGES
  copying ckan/i18n/he/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/he/LC_MESSAGES
  creating build/lib/ckan/i18n/hr
  creating build/lib/ckan/i18n/hr/LC_MESSAGES
  copying ckan/i18n/hr/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/hr/LC_MESSAGES
  copying ckan/i18n/hr/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/hr/LC_MESSAGES
  creating build/lib/ckan/i18n/hu
  creating build/lib/ckan/i18n/hu/LC_MESSAGES
  copying ckan/i18n/hu/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/hu/LC_MESSAGES
  copying ckan/i18n/hu/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/hu/LC_MESSAGES
  creating build/lib/ckan/i18n/id
  creating build/lib/ckan/i18n/id/LC_MESSAGES
  copying ckan/i18n/id/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/id/LC_MESSAGES
  copying ckan/i18n/id/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/id/LC_MESSAGES
  creating build/lib/ckan/i18n/is
  creating build/lib/ckan/i18n/is/LC_MESSAGES
  copying ckan/i18n/is/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/is/LC_MESSAGES
  copying ckan/i18n/is/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/is/LC_MESSAGES
  creating build/lib/ckan/i18n/it
  creating build/lib/ckan/i18n/it/LC_MESSAGES
  copying ckan/i18n/it/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/it/LC_MESSAGES
  copying ckan/i18n/it/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/it/LC_MESSAGES
  creating build/lib/ckan/i18n/ja
  creating build/lib/ckan/i18n/ja/LC_MESSAGES
  copying ckan/i18n/ja/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/ja/LC_MESSAGES
  copying ckan/i18n/ja/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/ja/LC_MESSAGES
  creating build/lib/ckan/i18n/km
  creating build/lib/ckan/i18n/km/LC_MESSAGES
  copying ckan/i18n/km/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/km/LC_MESSAGES
  copying ckan/i18n/km/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/km/LC_MESSAGES
  creating build/lib/ckan/i18n/ko_KR
  creating build/lib/ckan/i18n/ko_KR/LC_MESSAGES
  copying ckan/i18n/ko_KR/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/ko_KR/LC_MESSAGES
  copying ckan/i18n/ko_KR/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/ko_KR/LC_MESSAGES
  creating build/lib/ckan/i18n/lt
  creating build/lib/ckan/i18n/lt/LC_MESSAGES
  copying ckan/i18n/lt/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/lt/LC_MESSAGES
  copying ckan/i18n/lt/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/lt/LC_MESSAGES
  creating build/lib/ckan/i18n/lv
  creating build/lib/ckan/i18n/lv/LC_MESSAGES
  copying ckan/i18n/lv/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/lv/LC_MESSAGES
  copying ckan/i18n/lv/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/lv/LC_MESSAGES
  creating build/lib/ckan/i18n/mk
  creating build/lib/ckan/i18n/mk/LC_MESSAGES
  copying ckan/i18n/mk/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/mk/LC_MESSAGES
  copying ckan/i18n/mk/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/mk/LC_MESSAGES
  creating build/lib/ckan/i18n/mn_MN
  creating build/lib/ckan/i18n/mn_MN/LC_MESSAGES
  copying ckan/i18n/mn_MN/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/mn_MN/LC_MESSAGES
  copying ckan/i18n/mn_MN/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/mn_MN/LC_MESSAGES
  creating build/lib/ckan/i18n/my_MM
  creating build/lib/ckan/i18n/my_MM/LC_MESSAGES
  copying ckan/i18n/my_MM/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/my_MM/LC_MESSAGES
  copying ckan/i18n/my_MM/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/my_MM/LC_MESSAGES
  creating build/lib/ckan/i18n/nb_NO
  creating build/lib/ckan/i18n/nb_NO/LC_MESSAGES
  copying ckan/i18n/nb_NO/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/nb_NO/LC_MESSAGES
  copying ckan/i18n/nb_NO/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/nb_NO/LC_MESSAGES
  creating build/lib/ckan/i18n/ne
  creating build/lib/ckan/i18n/ne/LC_MESSAGES
  copying ckan/i18n/ne/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/ne/LC_MESSAGES
  copying ckan/i18n/ne/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/ne/LC_MESSAGES
  creating build/lib/ckan/i18n/nl
  creating build/lib/ckan/i18n/nl/LC_MESSAGES
  copying ckan/i18n/nl/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/nl/LC_MESSAGES
  copying ckan/i18n/nl/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/nl/LC_MESSAGES
  creating build/lib/ckan/i18n/no
  creating build/lib/ckan/i18n/no/LC_MESSAGES
  copying ckan/i18n/no/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/no/LC_MESSAGES
  copying ckan/i18n/no/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/no/LC_MESSAGES
  creating build/lib/ckan/i18n/pl
  creating build/lib/ckan/i18n/pl/LC_MESSAGES
  copying ckan/i18n/pl/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/pl/LC_MESSAGES
  copying ckan/i18n/pl/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/pl/LC_MESSAGES
  creating build/lib/ckan/i18n/pt_BR
  creating build/lib/ckan/i18n/pt_BR/LC_MESSAGES
  copying ckan/i18n/pt_BR/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/pt_BR/LC_MESSAGES
  copying ckan/i18n/pt_BR/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/pt_BR/LC_MESSAGES
  creating build/lib/ckan/i18n/pt_PT
  creating build/lib/ckan/i18n/pt_PT/LC_MESSAGES
  copying ckan/i18n/pt_PT/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/pt_PT/LC_MESSAGES
  copying ckan/i18n/pt_PT/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/pt_PT/LC_MESSAGES
  creating build/lib/ckan/i18n/ro
  creating build/lib/ckan/i18n/ro/LC_MESSAGES
  copying ckan/i18n/ro/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/ro/LC_MESSAGES
  copying ckan/i18n/ro/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/ro/LC_MESSAGES
  creating build/lib/ckan/i18n/ru
  creating build/lib/ckan/i18n/ru/LC_MESSAGES
  copying ckan/i18n/ru/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/ru/LC_MESSAGES
  copying ckan/i18n/ru/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/ru/LC_MESSAGES
  creating build/lib/ckan/i18n/sk
  creating build/lib/ckan/i18n/sk/LC_MESSAGES
  copying ckan/i18n/sk/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/sk/LC_MESSAGES
  copying ckan/i18n/sk/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/sk/LC_MESSAGES
  creating build/lib/ckan/i18n/sl
  creating build/lib/ckan/i18n/sl/LC_MESSAGES
  copying ckan/i18n/sl/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/sl/LC_MESSAGES
  copying ckan/i18n/sl/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/sl/LC_MESSAGES
  creating build/lib/ckan/i18n/sq
  creating build/lib/ckan/i18n/sq/LC_MESSAGES
  copying ckan/i18n/sq/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/sq/LC_MESSAGES
  copying ckan/i18n/sq/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/sq/LC_MESSAGES
  creating build/lib/ckan/i18n/sr
  creating build/lib/ckan/i18n/sr/LC_MESSAGES
  copying ckan/i18n/sr/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/sr/LC_MESSAGES
  copying ckan/i18n/sr/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/sr/LC_MESSAGES
  creating build/lib/ckan/i18n/sr_Latn
  creating build/lib/ckan/i18n/sr_Latn/LC_MESSAGES
  copying ckan/i18n/sr_Latn/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/sr_Latn/LC_MESSAGES
  copying ckan/i18n/sr_Latn/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/sr_Latn/LC_MESSAGES
  creating build/lib/ckan/i18n/sv
  creating build/lib/ckan/i18n/sv/LC_MESSAGES
  copying ckan/i18n/sv/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/sv/LC_MESSAGES
  copying ckan/i18n/sv/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/sv/LC_MESSAGES
  creating build/lib/ckan/i18n/th
  creating build/lib/ckan/i18n/th/LC_MESSAGES
  copying ckan/i18n/th/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/th/LC_MESSAGES
  copying ckan/i18n/th/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/th/LC_MESSAGES
  creating build/lib/ckan/i18n/tl
  creating build/lib/ckan/i18n/tl/LC_MESSAGES
  copying ckan/i18n/tl/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/tl/LC_MESSAGES
  copying ckan/i18n/tl/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/tl/LC_MESSAGES
  creating build/lib/ckan/i18n/tr
  creating build/lib/ckan/i18n/tr/LC_MESSAGES
  copying ckan/i18n/tr/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/tr/LC_MESSAGES
  copying ckan/i18n/tr/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/tr/LC_MESSAGES
  creating build/lib/ckan/i18n/uk
  creating build/lib/ckan/i18n/uk/LC_MESSAGES
  copying ckan/i18n/uk/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/uk/LC_MESSAGES
  copying ckan/i18n/uk/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/uk/LC_MESSAGES
  creating build/lib/ckan/i18n/uk_UA
  creating build/lib/ckan/i18n/uk_UA/LC_MESSAGES
  copying ckan/i18n/uk_UA/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/uk_UA/LC_MESSAGES
  copying ckan/i18n/uk_UA/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/uk_UA/LC_MESSAGES
  creating build/lib/ckan/i18n/vi
  creating build/lib/ckan/i18n/vi/LC_MESSAGES
  copying ckan/i18n/vi/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/vi/LC_MESSAGES
  copying ckan/i18n/vi/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/vi/LC_MESSAGES
  creating build/lib/ckan/i18n/zh_Hans_CN
  creating build/lib/ckan/i18n/zh_Hans_CN/LC_MESSAGES
  copying ckan/i18n/zh_Hans_CN/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/zh_Hans_CN/LC_MESSAGES
  copying ckan/i18n/zh_Hans_CN/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/zh_Hans_CN/LC_MESSAGES
  creating build/lib/ckan/i18n/zh_Hant_TW
  creating build/lib/ckan/i18n/zh_Hant_TW/LC_MESSAGES
  copying ckan/i18n/zh_Hant_TW/LC_MESSAGES/ckan.mo -> build/lib/ckan/i18n/zh_Hant_TW/LC_MESSAGES
  copying ckan/i18n/zh_Hant_TW/LC_MESSAGES/ckan.po -> build/lib/ckan/i18n/zh_Hant_TW/LC_MESSAGES
  creating build/lib/ckan/lib
  copying ckan/lib/__init__.py -> build/lib/ckan/lib
  copying ckan/lib/api_token.py -> build/lib/ckan/lib
  copying ckan/lib/app_globals.py -> build/lib/ckan/lib
  copying ckan/lib/authenticator.py -> build/lib/ckan/lib
  copying ckan/lib/base.py -> build/lib/ckan/lib
  copying ckan/lib/captcha.py -> build/lib/ckan/lib
  copying ckan/lib/cli.py -> build/lib/ckan/lib
  copying ckan/lib/config_tool.py -> build/lib/ckan/lib
  copying ckan/lib/create_test_data.py -> build/lib/ckan/lib
  copying ckan/lib/datapreview.py -> build/lib/ckan/lib
  copying ckan/lib/extract.py -> build/lib/ckan/lib
  copying ckan/lib/formatters.py -> build/lib/ckan/lib
  copying ckan/lib/hash.py -> build/lib/ckan/lib
  copying ckan/lib/helpers.py -> build/lib/ckan/lib
  copying ckan/lib/i18n.py -> build/lib/ckan/lib
  copying ckan/lib/io.py -> build/lib/ckan/lib
  copying ckan/lib/jinja_extensions.py -> build/lib/ckan/lib
  copying ckan/lib/jobs.py -> build/lib/ckan/lib
  copying ckan/lib/lazyjson.py -> build/lib/ckan/lib
  copying ckan/lib/mailer.py -> build/lib/ckan/lib
  copying ckan/lib/maintain.py -> build/lib/ckan/lib
  copying ckan/lib/munge.py -> build/lib/ckan/lib
  copying ckan/lib/pagination.py -> build/lib/ckan/lib
  copying ckan/lib/plugins.py -> build/lib/ckan/lib
  copying ckan/lib/redis.py -> build/lib/ckan/lib
  copying ckan/lib/signals.py -> build/lib/ckan/lib
  copying ckan/lib/uploader.py -> build/lib/ckan/lib
  copying ckan/lib/webassets_tools.py -> build/lib/ckan/lib
  creating build/lib/ckan/lib/dictization
  copying ckan/lib/dictization/__init__.py -> build/lib/ckan/lib/dictization
  copying ckan/lib/dictization/model_dictize.py -> build/lib/ckan/lib/dictization
  copying ckan/lib/dictization/model_save.py -> build/lib/ckan/lib/dictization
  creating build/lib/ckan/lib/navl
  copying ckan/lib/navl/__init__.py -> build/lib/ckan/lib/navl
  copying ckan/lib/navl/dictization_functions.py -> build/lib/ckan/lib/navl
  copying ckan/lib/navl/validators.py -> build/lib/ckan/lib/navl
  creating build/lib/ckan/lib/search
  copying ckan/lib/search/__init__.py -> build/lib/ckan/lib/search
  copying ckan/lib/search/common.py -> build/lib/ckan/lib/search
  copying ckan/lib/search/index.py -> build/lib/ckan/lib/search
  copying ckan/lib/search/query.py -> build/lib/ckan/lib/search
  creating build/lib/ckan/logic
  copying ckan/logic/__init__.py -> build/lib/ckan/logic
  copying ckan/logic/converters.py -> build/lib/ckan/logic
  copying ckan/logic/schema.py -> build/lib/ckan/logic
  copying ckan/logic/validators.py -> build/lib/ckan/logic
  creating build/lib/ckan/logic/action
  copying ckan/logic/action/__init__.py -> build/lib/ckan/logic/action
  copying ckan/logic/action/create.py -> build/lib/ckan/logic/action
  copying ckan/logic/action/delete.py -> build/lib/ckan/logic/action
  copying ckan/logic/action/get.py -> build/lib/ckan/logic/action
  copying ckan/logic/action/patch.py -> build/lib/ckan/logic/action
  copying ckan/logic/action/update.py -> build/lib/ckan/logic/action
  creating build/lib/ckan/logic/auth
  copying ckan/logic/auth/__init__.py -> build/lib/ckan/logic/auth
  copying ckan/logic/auth/create.py -> build/lib/ckan/logic/auth
  copying ckan/logic/auth/delete.py -> build/lib/ckan/logic/auth
  copying ckan/logic/auth/get.py -> build/lib/ckan/logic/auth
  copying ckan/logic/auth/patch.py -> build/lib/ckan/logic/auth
  copying ckan/logic/auth/update.py -> build/lib/ckan/logic/auth
  creating build/lib/ckan/migration
  copying ckan/migration/README -> build/lib/ckan/migration
  copying ckan/migration/__init__.py -> build/lib/ckan/migration
  copying ckan/migration/alembic.ini -> build/lib/ckan/migration
  copying ckan/migration/env.py -> build/lib/ckan/migration
  copying ckan/migration/migrate_package_activity.py -> build/lib/ckan/migration
  copying ckan/migration/revision_legacy_code.py -> build/lib/ckan/migration
  creating build/lib/ckan/migration/versions
  copying ckan/migration/versions/001_103676e0a497_create_existing_tables.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/002_86fdd8c54775_add_author_and_maintainer.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/003_f22b4f5241a5_add_user_object.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/004_f92ee205e46d_add_group_object.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/005_12c2232c15f5_add_authorization_tables.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/006_c83955e7acb6_add_ratings.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/007_1928d4af1cda_add_system_roles.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/008_e8283ffb257e_update_vdm_ids.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/009_b739a48de5c4_add_creation_timestamps.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/010_a6f13bf14d0c_add_user_about.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/011_866f6370b4ac_add_package_search_vector.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/012_e5ca33a5d445_add_resources.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/013_8a3a5af39797_add_hash.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/014_93519b684820_hash_2.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/015_6d8ffebcaf54_remove_state_object.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/016_37ada738328e_uuids_everywhere.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/017_1250b2ff3e36_add_pkg_relationships.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/018_05a0778051ca_adjust_licenses.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/019_b2eb6f34a638_pkg_relationships_state.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/020_69a0b0efc609_add_changeset.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/021_765143af2ba3_postgresql_upgrade_sql.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/022_7b324ca6c0dc_add_group_extras.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/023_87fdd05f0744_add_harvesting.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/024_12981fe12484_add_harvested_document.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/025_b581622ad327_add_authorization_groups.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/026_3615b25af443_authorization_group_user_pk.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/027_11e5745c6fc9_adjust_harvester.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/028_cdd68fe9ba21_drop_harvest_source_status.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/029_1bfdf4240915_version_groups.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/030_b16cbf164c8a_additional_user_attributes.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/031_1b05245167d6_move_openid_to_new_field.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/032_d89e0731422d_add_extra_info_field_to_resources.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/033_6da92ef2df15_auth_group_user_id_add_conditional.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/034_6c600693af5b_resource_group_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/035_81148ccebd6c_harvesting_doc_versioning.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/036_ecaa8b38782f_lockdown_roles.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/037_edcf3b8c3c1b_role_anon_editor.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/038_fd6622e3d964_delete_migration_tables.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/039_cca459c76d45_add_expired_id_and_dates.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/040_500a08f4818e_reset_key_on_user.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/041_6817d4e3bdc3_resource_new_fields.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/042_da65e2877034_user_revision_indexes.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/043_bd38cd6502b2_drop_postgres_search.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/044_4190eeeb8d73_add_task_status.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/045_54e3f155d945_user_name_unique.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/046_b69e9b80396f_drop_changesets.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/047_883a7c406926_rename_package_group_member.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/048_4a7011172b3f_add_activity_streams_tables.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/049_e0c06c2177b5_add_group_approval_status.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/050_01a6b058cb7f_term_translation_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/051_a4fb0d85ced6_add_tag_vocabulary.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/052_ba693d64c6d7_update_member_capacities.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/053_9d051a099097_add_group_logo.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/054_da21b38da4db_add_resource_created_date.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/055_048f7db947bf_update_user_and_activity_detail.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/056_11af3215ae89_add_related_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/057_660a5aae527e_tracking.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/058_bd36d1826a5d_add_follower_tables.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/059_9291bb46f352_add_related_count_and_flag.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/060_31ad11c518fc_add_system_info_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/061_338d460bc460_add_follower_group_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/062_6deb2bbab394_add_dashboard_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/063_8b633852cb7a_org_changes.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/064_4f8becd4919a_add_email_last_sent_column.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/065_1fab0bc6439e_add_email_notifications_preference.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/066_ad16b3bd8cb6_default_package_type.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/067_266c110eafec_turn_extras_to_strings.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/068_e33a5f2b2a84_add_package_extras_index.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/069_e7524c675cdb_resource_url_and_metadata_modified.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/070_cfb544112fa7_add_activity_and_resource_indexes.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/071_c16f081ef73a_add_state_column_to_user_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/072_08dcb9233ad7_add_resource_view.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/073_011f51208be3_update_resource_view_resource_id_.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/074_a4ca55f0f45e_remove_resource_groups.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/075_9cdc88c8896a_rename_view_plugins.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/076_59995aa965c0_rename_view_plugins_2.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/077_51171a04d86d_add_revisions_to_system_info.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/078_ae821876532a_remove_old_authz_model.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/079_e0177a15d2c9_resource_revision_index.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/080_8224d872c64f_continuity_id_indexes.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/081_a64cf4a79182_set_datastore_active.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/082_8ea886d0ede4_create_index_creator_user_id.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/083_f98d8fa2a7f7_remove_related_items.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/084_d85ce5783688_add_metadata_created.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/085_f9bf3d5c4b4d_adjust_activity_timestamps.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/086_19663581b3bb_drop_openid_column.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/087_ff1b303cab77_remove_old_authorization_tables.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/088_3537d5420e0e_delete_extrase_which_are_deleted_state.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/089_23c92480926e_package_activity_migration_check.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/090_980dcd44de4b_delete_migrate_version_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/091_0ffc0b277141_group_extra_group_id_index.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/092_01afcadbd8c0_resource_package_id_index.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/093_7f70d7d15445_remove_activity_revision_id.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/094_588d7cfb9a41_add_metadata_modified_to_resource_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/095_9fadda785b07_drop_continuity_id_constraints.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/096_19ddad52b500_add_plugin_extras_to_user_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/097_f789f233226e_add_package_member_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/098_ddbd0a9a4489_add_image_url_field_to_user_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/099_3ae4b17ed66d_create_apitoken_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/100_ccd38ad5fced_remove_package_tag_revision_foreign_key.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/101_d111f446733b_add_last_active_column_in_user_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/102_ff13667243ed_create_conditinal_index_on_user.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/103_353aaf2701f0_add_plugin_data_to_package_table.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/104_9f33a0280c51_resource_view_resource_id_index.py -> build/lib/ckan/migration/versions
  copying ckan/migration/versions/__init__.py -> build/lib/ckan/migration/versions
  creating build/lib/ckan/model
  copying ckan/model/__init__.py -> build/lib/ckan/model
  copying ckan/model/api_token.py -> build/lib/ckan/model
  copying ckan/model/base.py -> build/lib/ckan/model
  copying ckan/model/core.py -> build/lib/ckan/model
  copying ckan/model/dashboard.py -> build/lib/ckan/model
  copying ckan/model/domain_object.py -> build/lib/ckan/model
  copying ckan/model/follower.py -> build/lib/ckan/model
  copying ckan/model/group.py -> build/lib/ckan/model
  copying ckan/model/group_extra.py -> build/lib/ckan/model
  copying ckan/model/license.py -> build/lib/ckan/model
  copying ckan/model/meta.py -> build/lib/ckan/model
  copying ckan/model/misc.py -> build/lib/ckan/model
  copying ckan/model/modification.py -> build/lib/ckan/model
  copying ckan/model/package.py -> build/lib/ckan/model
  copying ckan/model/package_extra.py -> build/lib/ckan/model
  copying ckan/model/package_relationship.py -> build/lib/ckan/model
  copying ckan/model/resource.py -> build/lib/ckan/model
  copying ckan/model/resource_view.py -> build/lib/ckan/model
  copying ckan/model/system.py -> build/lib/ckan/model
  copying ckan/model/system_info.py -> build/lib/ckan/model
  copying ckan/model/tag.py -> build/lib/ckan/model
  copying ckan/model/task_status.py -> build/lib/ckan/model
  copying ckan/model/term_translation.py -> build/lib/ckan/model
  copying ckan/model/tracking.py -> build/lib/ckan/model
  copying ckan/model/types.py -> build/lib/ckan/model
  copying ckan/model/user.py -> build/lib/ckan/model
  copying ckan/model/vocabulary.py -> build/lib/ckan/model
  creating build/lib/ckan/plugins
  copying ckan/plugins/__init__.py -> build/lib/ckan/plugins
  copying ckan/plugins/blanket.py -> build/lib/ckan/plugins
  copying ckan/plugins/core.py -> build/lib/ckan/plugins
  copying ckan/plugins/interfaces.py -> build/lib/ckan/plugins
  copying ckan/plugins/toolkit.py -> build/lib/ckan/plugins
  copying ckan/plugins/toolkit_sphinx_extension.py -> build/lib/ckan/plugins
  creating build/lib/ckan/public-bs3
  copying ckan/public-bs3/robots.txt -> build/lib/ckan/public-bs3
  creating build/lib/ckan/public-bs3/base
  copying ckan/public-bs3/base/.gitignore -> build/lib/ckan/public-bs3/base
  creating build/lib/ckan/public-bs3/base/css
  copying ckan/public-bs3/base/css/.gitignore -> build/lib/ckan/public-bs3/base/css
  copying ckan/public-bs3/base/css/main-rtl.css -> build/lib/ckan/public-bs3/base/css
  copying ckan/public-bs3/base/css/main.css -> build/lib/ckan/public-bs3/base/css
  copying ckan/public-bs3/base/css/webassets.yml -> build/lib/ckan/public-bs3/base/css
  creating build/lib/ckan/public-bs3/base/i18n
  copying ckan/public-bs3/base/i18n/.gitignore -> build/lib/ckan/public-bs3/base/i18n
  creating build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/background-tag-ie7.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/background-tag.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/background-tile.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/bg.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/breadcrumb-slash-ie7.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/ckan-logo-footer.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/ckan-logo-white.svg -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/ckan-logo.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/ckan-logo.svg -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/ckan.ico -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/dashboard-followee-related.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/dotted.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/editing.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/full-width-nav-right.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/icon-search-27x26.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/nav-active.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/nav.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/od_80x15_blue.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-200x125.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-420x220.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-680x400.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-application.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-group.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-image.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-organization.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-user.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/sprite-ckan-icons.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/sprite-resource-icons.png -> build/lib/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/table-seperator.png -> build/lib/ckan/public-bs3/base/images
  creating build/lib/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/apply-html-class.js -> build/lib/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/client.js -> build/lib/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/i18n.js -> build/lib/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/main.js -> build/lib/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/module.js -> build/lib/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/notify.js -> build/lib/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/pubsub.js -> build/lib/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/resource.config -> build/lib/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/sandbox.js -> build/lib/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/tracking.js -> build/lib/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/view-filters.js -> build/lib/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/webassets.yml -> build/lib/ckan/public-bs3/base/javascript
  creating build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/api-info.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/autocomplete.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/basic-form.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/confirm-action.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/copy-into-buffer.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/custom-fields.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/data-viewer.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/dataset-visibility.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/follow.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/followers-counter.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/image-upload.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/media-grid.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/metadata-button.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-form.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-reorder.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-upload-field.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-view-embed.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-view-filters-form.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-view-filters.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-view-reorder.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/select-switch.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/slug-preview.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/table-selectable-rows.js -> build/lib/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/table-toggle-more.js -> build/lib/ckan/public-bs3/base/javascript/modules
  creating build/lib/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.date-helpers.js -> build/lib/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.form-warning.js -> build/lib/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.images-loaded.js -> build/lib/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.inherit.js -> build/lib/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.masonry.js -> build/lib/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.proxy-all.js -> build/lib/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.slug-preview.js -> build/lib/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.slug.js -> build/lib/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.truncator.js -> build/lib/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.url-helpers.js -> build/lib/ckan/public-bs3/base/javascript/plugins
  creating build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_alerts.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_bootstrap-rtl.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_bootstrap-variables.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_bootstrap.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_ckan-rtl.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_ckan.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_custom.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_dashboard.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_datapusher.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_dataset.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_dropdown.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_footer.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_forms.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_group.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_homepage.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_icons.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_input-groups.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_layout.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_masthead.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_media.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_mixins.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_module.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_nav.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_profile.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_prose.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_resource-view.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_search.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_tables.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_toolbar.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_variables.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/main-rtl.scss -> build/lib/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/main.scss -> build/lib/ckan/public-bs3/base/scss
  creating build/lib/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/bootstrap.js -> build/lib/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/jed.js -> build/lib/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/jquery.js -> build/lib/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/jquery.ui.core.js -> build/lib/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/jquery.ui.mouse.js -> build/lib/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/jquery.ui.sortable.js -> build/lib/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/jquery.ui.widget.js -> build/lib/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/moment-with-locales.js -> build/lib/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/qs.js -> build/lib/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/resource.config -> build/lib/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/webassets.yml -> build/lib/ckan/public-bs3/base/vendor
  creating build/lib/ckan/public-bs3/base/vendor/bootstrap
  creating build/lib/ckan/public-bs3/base/vendor/bootstrap/fonts
  creating build/lib/ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.eot -> build/lib/ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.svg -> build/lib/ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.ttf -> build/lib/ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.woff -> build/lib/ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.woff2 -> build/lib/ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap
  creating build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap-sprockets.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts
  creating build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/affix.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/alert.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/button.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/carousel.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/collapse.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/dropdown.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/modal.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/popover.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/scrollspy.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/tab.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/tooltip.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/transition.js -> build/lib/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  creating build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/_bootstrap-compass.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/_bootstrap-mincer.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/_bootstrap-sprockets.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/_bootstrap.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets
  creating build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_alerts.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_badges.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_breadcrumbs.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_button-groups.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_buttons.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_carousel.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_close.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_code.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_component-animations.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_dropdowns.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_forms.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_glyphicons.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_grid.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_input-groups.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_jumbotron.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_labels.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_list-group.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_media.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_mixins.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_modals.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_navbar.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_navs.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_normalize.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_pager.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_pagination.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_panels.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_popovers.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_print.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_progress-bars.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_responsive-embed.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_responsive-utilities.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_scaffolding.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_tables.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_theme.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_thumbnails.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_tooltip.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_type.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_utilities.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_variables.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_wells.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  creating build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_alerts.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_background-variant.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_border-radius.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_buttons.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_center-block.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_clearfix.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_forms.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_gradients.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_grid-framework.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_grid.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_hide-text.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_image.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_labels.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_list-group.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_nav-divider.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_nav-vertical-align.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_opacity.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_pagination.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_panels.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_progress-bar.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_reset-filter.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_reset-text.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_resize.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_responsive-visibility.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_size.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_tab-focus.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_table-row.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_text-emphasis.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_text-overflow.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_vendor-prefixes.scss -> build/lib/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  creating build/lib/ckan/public-bs3/base/vendor/fontawesome-free
  creating build/lib/ckan/public-bs3/base/vendor/fontawesome-free/css
  copying ckan/public-bs3/base/vendor/fontawesome-free/css/all.css -> build/lib/ckan/public-bs3/base/vendor/fontawesome-free/css
  creating build/lib/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-brands-400.ttf -> build/lib/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-brands-400.woff2 -> build/lib/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-regular-400.ttf -> build/lib/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-regular-400.woff2 -> build/lib/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-solid-900.ttf -> build/lib/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-solid-900.woff2 -> build/lib/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-v4compatibility.ttf -> build/lib/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-v4compatibility.woff2 -> build/lib/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  creating build/lib/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-audio.js -> build/lib/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-image.js -> build/lib/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-process.js -> build/lib/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-ui.js -> build/lib/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-validate.js -> build/lib/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-video.js -> build/lib/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload.js -> build/lib/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.iframe-transport.js -> build/lib/ckan/public-bs3/base/vendor/jquery-fileupload
  creating build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/.gitignore -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/CONTRIBUTING.md -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/LICENSE -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/README.md -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/bower.json -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/component.json -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/composer.json -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/package.json -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/release.sh -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2-bootstrap.css -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2-spinner.gif -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2.css -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2.jquery.json -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2.png -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ar.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_az.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_bg.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ca.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_cs.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_da.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_de.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_el.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_en.js.template -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_es.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_et.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_eu.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_fa.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_fi.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_fr.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_gl.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_he.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_hr.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_hu.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_id.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_is.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_it.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ja.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ka.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ko.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_lt.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_lv.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_mk.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ms.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_nb.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_nl.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_pl.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_pt-BR.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_pt-PT.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ro.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_rs.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ru.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_sk.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_sv.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_th.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_tr.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ug-CN.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_uk.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_vi.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_zh-CN.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_zh-TW.js -> build/lib/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2x2.png -> build/lib/ckan/public-bs3/base/vendor/select2
  creating build/lib/ckan/public
  creating build/lib/ckan/public/base
  copying ckan/public/base/.gitignore -> build/lib/ckan/public/base
  creating build/lib/ckan/public/base/css
  copying ckan/public/base/css/.gitignore -> build/lib/ckan/public/base/css
  copying ckan/public/base/css/main-rtl.css -> build/lib/ckan/public/base/css
  copying ckan/public/base/css/main.css -> build/lib/ckan/public/base/css
  copying ckan/public/base/css/webassets.yml -> build/lib/ckan/public/base/css
  creating build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/.gitignore -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/am.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/ar.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/bg.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/bs.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/ca.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/cs_CZ.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/da_DK.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/de.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/el.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/en_AU.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/en_GB.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/es.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/es_AR.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/eu.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/fa_IR.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/fi.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/fr.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/gl.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/he.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/hr.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/hu.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/id.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/is.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/it.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/ja.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/km.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/ko_KR.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/lt.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/lv.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/mk.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/mn_MN.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/my_MM.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/nb_NO.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/ne.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/nl.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/no.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/pl.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/pt_BR.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/pt_PT.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/ro.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/ru.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/sk.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/sl.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/sq.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/sr.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/sr_Latn.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/sv.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/th.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/tl.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/tr.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/uk.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/uk_UA.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/vi.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/zh_Hans_CN.js -> build/lib/ckan/public/base/i18n
  copying ckan/public/base/i18n/zh_Hant_TW.js -> build/lib/ckan/public/base/i18n
  creating build/lib/ckan/public/base/images
  copying ckan/public/base/images/background-tag-ie7.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/background-tag.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/background-tile.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/bg.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/breadcrumb-slash-ie7.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/ckan-logo-footer.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/ckan-logo-white.svg -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/ckan-logo.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/ckan-logo.svg -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/ckan.ico -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/dashboard-followee-related.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/editing.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/full-width-nav-right.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/icon-search-27x26.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/nav-active.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/nav.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/od_80x15_blue.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/placeholder-200x125.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/placeholder-420x220.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/placeholder-680x400.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/placeholder-application.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/placeholder-group.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/placeholder-image.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/placeholder-organization.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/placeholder-user.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/sprite-resource-icons.png -> build/lib/ckan/public/base/images
  copying ckan/public/base/images/table-seperator.png -> build/lib/ckan/public/base/images
  creating build/lib/ckan/public/base/javascript
  copying ckan/public/base/javascript/apply-html-class.js -> build/lib/ckan/public/base/javascript
  copying ckan/public/base/javascript/client.js -> build/lib/ckan/public/base/javascript
  copying ckan/public/base/javascript/i18n.js -> build/lib/ckan/public/base/javascript
  copying ckan/public/base/javascript/main.js -> build/lib/ckan/public/base/javascript
  copying ckan/public/base/javascript/module.js -> build/lib/ckan/public/base/javascript
  copying ckan/public/base/javascript/notify.js -> build/lib/ckan/public/base/javascript
  copying ckan/public/base/javascript/pubsub.js -> build/lib/ckan/public/base/javascript
  copying ckan/public/base/javascript/resource.config -> build/lib/ckan/public/base/javascript
  copying ckan/public/base/javascript/sandbox.js -> build/lib/ckan/public/base/javascript
  copying ckan/public/base/javascript/tracking.js -> build/lib/ckan/public/base/javascript
  copying ckan/public/base/javascript/view-filters.js -> build/lib/ckan/public/base/javascript
  copying ckan/public/base/javascript/webassets.yml -> build/lib/ckan/public/base/javascript
  creating build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/api-info.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/autocomplete.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/basic-form.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/confirm-action.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/copy-into-buffer.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/custom-fields.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/data-viewer.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/dataset-visibility.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/follow.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/followers-counter.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/image-upload.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/media-grid.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/metadata-button.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-form.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-reorder.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-upload-field.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-view-embed.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-view-filters-form.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-view-filters.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-view-reorder.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/select-switch.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/slug-preview.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/table-selectable-rows.js -> build/lib/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/table-toggle-more.js -> build/lib/ckan/public/base/javascript/modules
  creating build/lib/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.date-helpers.js -> build/lib/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.form-warning.js -> build/lib/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.images-loaded.js -> build/lib/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.inherit.js -> build/lib/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.masonry.js -> build/lib/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.proxy-all.js -> build/lib/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.slug-preview.js -> build/lib/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.slug.js -> build/lib/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.truncator.js -> build/lib/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.url-helpers.js -> build/lib/ckan/public/base/javascript/plugins
  creating build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_alerts.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_bootstrap-rtl.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_bootstrap-variables.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_bootstrap.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_buttons.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_ckan-rtl.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_ckan.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_custom.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_dashboard.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_datapusher.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_dataset.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_footer.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_forms.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_group.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_homepage.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_input-groups.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_layout.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_masthead.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_media.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_mixins.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_module.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_nav.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_profile.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_prose.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_resource-icons.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_resource-view.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_search.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_tables.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_toolbar.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/_variables.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/main-rtl.scss -> build/lib/ckan/public/base/scss
  copying ckan/public/base/scss/main.scss -> build/lib/ckan/public/base/scss
  creating build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/bootstrap.js -> build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/jed.js -> build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/jquery.js -> build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/jquery.ui.core.js -> build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/jquery.ui.mouse.js -> build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/jquery.ui.sortable.js -> build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/jquery.ui.widget.js -> build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/moment-with-locales.js -> build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/popper.js -> build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/popperjs.js -> build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/purify.js -> build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/qs.js -> build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/resource.config -> build/lib/ckan/public/base/vendor
  copying ckan/public/base/vendor/webassets.yml -> build/lib/ckan/public/base/vendor
  creating build/lib/ckan/public/base/vendor/bootstrap
  creating build/lib/ckan/public/base/vendor/bootstrap/css
  copying ckan/public/base/vendor/bootstrap/css/bootstrap-theme.min.css.map -> build/lib/ckan/public/base/vendor/bootstrap/css
  copying ckan/public/base/vendor/bootstrap/css/bootstrap.min.css.map -> build/lib/ckan/public/base/vendor/bootstrap/css
  creating build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/alert.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/alert.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/base-component.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/base-component.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.bundle.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.bundle.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.bundle.min.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.bundle.min.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.esm.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.esm.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.esm.min.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.esm.min.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.min.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.min.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/button.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/button.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/carousel.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/carousel.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/collapse.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/collapse.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/dropdown.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/dropdown.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/modal.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/modal.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/offcanvas.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/offcanvas.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/popover.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/popover.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/scrollspy.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/scrollspy.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/tab.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/tab.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/toast.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/toast.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/tooltip.js -> build/lib/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/tooltip.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js
  creating build/lib/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/data.js -> build/lib/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/data.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/event-handler.js -> build/lib/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/event-handler.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/manipulator.js -> build/lib/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/manipulator.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/selector-engine.js -> build/lib/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/selector-engine.js.map -> build/lib/ckan/public/base/vendor/bootstrap/js/dom
  creating build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_accordion.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_alert.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_badge.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_breadcrumb.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_button-group.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_buttons.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_card.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_carousel.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_close.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_containers.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_dropdown.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_forms.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_functions.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_grid.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_helpers.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_images.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_list-group.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_mixins.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_modal.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_nav.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_navbar.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_offcanvas.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_pagination.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_placeholders.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_popover.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_progress.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_reboot.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_root.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_spinners.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_tables.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_toasts.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_tooltip.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_transitions.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_type.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_utilities.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_variables.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/bootstrap-grid.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/bootstrap-reboot.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/bootstrap-utilities.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/bootstrap.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss
  creating build/lib/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_floating-labels.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_form-check.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_form-control.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_form-range.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_form-select.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_form-text.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_input-group.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_labels.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_validation.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/forms
  creating build/lib/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_clearfix.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_colored-links.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_position.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_ratio.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_stacks.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_stretched-link.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_text-truncation.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_visually-hidden.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_vr.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/helpers
  creating build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_alert.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_backdrop.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_border-radius.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_box-shadow.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_breakpoints.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_buttons.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_caret.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_clearfix.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_color-scheme.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_container.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_deprecate.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_forms.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_gradients.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_grid.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_image.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_list-group.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_lists.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_pagination.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_reset-text.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_resize.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_table-variants.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_text-truncate.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_transition.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_utilities.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_visually-hidden.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/mixins
  creating build/lib/ckan/public/base/vendor/bootstrap/scss/utilities
  copying ckan/public/base/vendor/bootstrap/scss/utilities/_api.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/utilities
  creating build/lib/ckan/public/base/vendor/bootstrap/scss/vendor
  copying ckan/public/base/vendor/bootstrap/scss/vendor/_rfs.scss -> build/lib/ckan/public/base/vendor/bootstrap/scss/vendor
  creating build/lib/ckan/public/base/vendor/fontawesome-free
  creating build/lib/ckan/public/base/vendor/fontawesome-free/css
  copying ckan/public/base/vendor/fontawesome-free/css/all.css -> build/lib/ckan/public/base/vendor/fontawesome-free/css
  creating build/lib/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-brands-400.ttf -> build/lib/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-brands-400.woff2 -> build/lib/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-regular-400.ttf -> build/lib/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-regular-400.woff2 -> build/lib/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-solid-900.ttf -> build/lib/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-solid-900.woff2 -> build/lib/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-v4compatibility.ttf -> build/lib/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-v4compatibility.woff2 -> build/lib/ckan/public/base/vendor/fontawesome-free/webfonts
  creating build/lib/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-audio.js -> build/lib/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-image.js -> build/lib/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-process.js -> build/lib/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-ui.js -> build/lib/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-validate.js -> build/lib/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-video.js -> build/lib/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload.js -> build/lib/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.iframe-transport.js -> build/lib/ckan/public/base/vendor/jquery-fileupload
  creating build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/.gitignore -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/CONTRIBUTING.md -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/LICENSE -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/README.md -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/bower.json -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/component.json -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/composer.json -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/package.json -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/release.sh -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2-bootstrap.css -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2-spinner.gif -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2.css -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2.jquery.json -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2.png -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ar.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_az.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_bg.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ca.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_cs.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_da.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_de.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_el.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_en.js.template -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_es.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_et.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_eu.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_fa.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_fi.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_fr.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_gl.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_he.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_hr.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_hu.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_id.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_is.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_it.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ja.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ka.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ko.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_lt.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_lv.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_mk.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ms.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_nb.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_nl.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_pl.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_pt-BR.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_pt-PT.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ro.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_rs.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ru.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_sk.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_sv.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_th.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_tr.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ug-CN.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_uk.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_vi.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_zh-CN.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_zh-TW.js -> build/lib/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2x2.png -> build/lib/ckan/public/base/vendor/select2
  creating build/lib/ckan/templates
  copying ckan/templates/base.html -> build/lib/ckan/templates
  copying ckan/templates/error_document_template.html -> build/lib/ckan/templates
  copying ckan/templates/footer.html -> build/lib/ckan/templates
  copying ckan/templates/header.html -> build/lib/ckan/templates
  copying ckan/templates/page.html -> build/lib/ckan/templates
  creating build/lib/ckan/templates-bs3
  copying ckan/templates-bs3/base.html -> build/lib/ckan/templates-bs3
  copying ckan/templates-bs3/error_document_template.html -> build/lib/ckan/templates-bs3
  copying ckan/templates-bs3/footer.html -> build/lib/ckan/templates-bs3
  copying ckan/templates-bs3/header.html -> build/lib/ckan/templates-bs3
  copying ckan/templates-bs3/page.html -> build/lib/ckan/templates-bs3
  creating build/lib/ckan/templates-bs3/admin
  copying ckan/templates-bs3/admin/base.html -> build/lib/ckan/templates-bs3/admin
  copying ckan/templates-bs3/admin/config.html -> build/lib/ckan/templates-bs3/admin
  copying ckan/templates-bs3/admin/confirm_reset.html -> build/lib/ckan/templates-bs3/admin
  copying ckan/templates-bs3/admin/index.html -> build/lib/ckan/templates-bs3/admin
  copying ckan/templates-bs3/admin/trash.html -> build/lib/ckan/templates-bs3/admin
  creating build/lib/ckan/templates-bs3/admin/snippets
  copying ckan/templates-bs3/admin/snippets/confirm_delete.html -> build/lib/ckan/templates-bs3/admin/snippets
  copying ckan/templates-bs3/admin/snippets/data_type.html -> build/lib/ckan/templates-bs3/admin/snippets
  creating build/lib/ckan/templates-bs3/ajax_snippets
  copying ckan/templates-bs3/ajax_snippets/custom_fields.html -> build/lib/ckan/templates-bs3/ajax_snippets
  copying ckan/templates-bs3/ajax_snippets/follow_button.html -> build/lib/ckan/templates-bs3/ajax_snippets
  creating build/lib/ckan/templates-bs3/dataviewer
  copying ckan/templates-bs3/dataviewer/base.html -> build/lib/ckan/templates-bs3/dataviewer
  creating build/lib/ckan/templates-bs3/development
  copying ckan/templates-bs3/development/primer.html -> build/lib/ckan/templates-bs3/development
  creating build/lib/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/actions.html -> build/lib/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/breadcrumb.html -> build/lib/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/context.html -> build/lib/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/facet.html -> build/lib/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/form.html -> build/lib/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/form_stages.html -> build/lib/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/list.html -> build/lib/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/media_grid.html -> build/lib/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/module.html -> build/lib/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/nav.html -> build/lib/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/page_header.html -> build/lib/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/pagination.html -> build/lib/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/simple-input.html -> build/lib/ckan/templates-bs3/development/snippets
  creating build/lib/ckan/templates-bs3/emails
  copying ckan/templates-bs3/emails/invite_user.txt -> build/lib/ckan/templates-bs3/emails
  copying ckan/templates-bs3/emails/invite_user_subject.txt -> build/lib/ckan/templates-bs3/emails
  copying ckan/templates-bs3/emails/reset_password.txt -> build/lib/ckan/templates-bs3/emails
  copying ckan/templates-bs3/emails/reset_password_subject.txt -> build/lib/ckan/templates-bs3/emails
  creating build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/about.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/admins.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/base_form_page.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/confirm_delete.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/confirm_delete_member.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/edit.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/edit_base.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/followers.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/index.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/member_new.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/members.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/new.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/new_group_form.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/read.html -> build/lib/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/read_base.html -> build/lib/ckan/templates-bs3/group
  creating build/lib/ckan/templates-bs3/group/snippets
  copying ckan/templates-bs3/group/snippets/feeds.html -> build/lib/ckan/templates-bs3/group/snippets
  copying ckan/templates-bs3/group/snippets/group_form.html -> build/lib/ckan/templates-bs3/group/snippets
  copying ckan/templates-bs3/group/snippets/group_item.html -> build/lib/ckan/templates-bs3/group/snippets
  copying ckan/templates-bs3/group/snippets/group_list.html -> build/lib/ckan/templates-bs3/group/snippets
  copying ckan/templates-bs3/group/snippets/helper.html -> build/lib/ckan/templates-bs3/group/snippets
  copying ckan/templates-bs3/group/snippets/info.html -> build/lib/ckan/templates-bs3/group/snippets
  creating build/lib/ckan/templates-bs3/home
  copying ckan/templates-bs3/home/about.html -> build/lib/ckan/templates-bs3/home
  copying ckan/templates-bs3/home/index.html -> build/lib/ckan/templates-bs3/home
  copying ckan/templates-bs3/home/layout1.html -> build/lib/ckan/templates-bs3/home
  copying ckan/templates-bs3/home/layout2.html -> build/lib/ckan/templates-bs3/home
  copying ckan/templates-bs3/home/layout3.html -> build/lib/ckan/templates-bs3/home
  creating build/lib/ckan/templates-bs3/home/snippets
  copying ckan/templates-bs3/home/snippets/about_text.html -> build/lib/ckan/templates-bs3/home/snippets
  copying ckan/templates-bs3/home/snippets/featured_group.html -> build/lib/ckan/templates-bs3/home/snippets
  copying ckan/templates-bs3/home/snippets/featured_organization.html -> build/lib/ckan/templates-bs3/home/snippets
  copying ckan/templates-bs3/home/snippets/promoted.html -> build/lib/ckan/templates-bs3/home/snippets
  copying ckan/templates-bs3/home/snippets/search.html -> build/lib/ckan/templates-bs3/home/snippets
  copying ckan/templates-bs3/home/snippets/stats.html -> build/lib/ckan/templates-bs3/home/snippets
  creating build/lib/ckan/templates-bs3/macros
  copying ckan/templates-bs3/macros/autoform.html -> build/lib/ckan/templates-bs3/macros
  copying ckan/templates-bs3/macros/form.html -> build/lib/ckan/templates-bs3/macros
  creating build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/about.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/admins.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/base_form_page.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/bulk_process.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/confirm_delete.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/confirm_delete_member.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/edit.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/edit_base.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/index.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/member_new.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/members.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/new.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/new_organization_form.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/read.html -> build/lib/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/read_base.html -> build/lib/ckan/templates-bs3/organization
  creating build/lib/ckan/templates-bs3/organization/snippets
  copying ckan/templates-bs3/organization/snippets/feeds.html -> build/lib/ckan/templates-bs3/organization/snippets
  copying ckan/templates-bs3/organization/snippets/helper.html -> build/lib/ckan/templates-bs3/organization/snippets
  copying ckan/templates-bs3/organization/snippets/organization_form.html -> build/lib/ckan/templates-bs3/organization/snippets
  copying ckan/templates-bs3/organization/snippets/organization_item.html -> build/lib/ckan/templates-bs3/organization/snippets
  copying ckan/templates-bs3/organization/snippets/organization_list.html -> build/lib/ckan/templates-bs3/organization/snippets
  creating build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/base.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/base_form_page.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/confirm_delete.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/confirm_delete_resource.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/edit.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/edit_base.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/edit_view.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/followers.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/group_list.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/new.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/new_package_form.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/new_resource.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/new_resource_not_draft.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/new_view.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/read.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/read_base.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/resource_edit.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/resource_edit_base.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/resource_read.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/resource_views.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/resources.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/search.html -> build/lib/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/view_edit_base.html -> build/lib/ckan/templates-bs3/package
  creating build/lib/ckan/templates-bs3/package/collaborators
  copying ckan/templates-bs3/package/collaborators/collaborator_new.html -> build/lib/ckan/templates-bs3/package/collaborators
  copying ckan/templates-bs3/package/collaborators/collaborators.html -> build/lib/ckan/templates-bs3/package/collaborators
  creating build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/additional_info.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/cannot_create_package.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/info.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/new_package_breadcrumb.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/package_basic_fields.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/package_form.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/package_metadata_fields.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_edit_form.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_form.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_help.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_info.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_item.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_upload_field.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_view.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_view_embed.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_view_filters.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_views_list.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_views_list_item.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resources.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resources_list.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/stages.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/tags.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/view_form.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/view_form_filters.html -> build/lib/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/view_help.html -> build/lib/ckan/templates-bs3/package/snippets
  creating build/lib/ckan/templates-bs3/revision
  copying ckan/templates-bs3/revision/__init__.py -> build/lib/ckan/templates-bs3/revision
  creating build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/add_dataset.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/additional_info.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/context.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/csrf_input.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/custom_form_fields.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/datapusher_status.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/disqus_trackback.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/facet_list.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/follow_button.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/group.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/group_item.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/home_breadcrumb_item.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/language_selector.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/license.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/local_friendly_datetime.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/organization.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/organization_item.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/package_item.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/package_list.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/popular.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/private.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/search_form.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/search_result_text.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/simple_search.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/social.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/subscribe.html -> build/lib/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/tag_list.html -> build/lib/ckan/templates-bs3/snippets
  creating build/lib/ckan/templates-bs3/snippets/context
  copying ckan/templates-bs3/snippets/context/dataset.html -> build/lib/ckan/templates-bs3/snippets/context
  copying ckan/templates-bs3/snippets/context/group.html -> build/lib/ckan/templates-bs3/snippets/context
  copying ckan/templates-bs3/snippets/context/user.html -> build/lib/ckan/templates-bs3/snippets/context
  creating build/lib/ckan/templates-bs3/tests
  copying ckan/templates-bs3/tests/broken_helper_as_attribute.html -> build/lib/ckan/templates-bs3/tests
  copying ckan/templates-bs3/tests/broken_helper_as_item.html -> build/lib/ckan/templates-bs3/tests
  copying ckan/templates-bs3/tests/flash_messages.html -> build/lib/ckan/templates-bs3/tests
  copying ckan/templates-bs3/tests/helper_as_attribute.html -> build/lib/ckan/templates-bs3/tests
  copying ckan/templates-bs3/tests/helper_as_item.html -> build/lib/ckan/templates-bs3/tests
  copying ckan/templates-bs3/tests/mock_json_resource_preview_template.html -> build/lib/ckan/templates-bs3/tests
  copying ckan/templates-bs3/tests/mock_resource_preview_template.html -> build/lib/ckan/templates-bs3/tests
  creating build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/api_tokens.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/dashboard.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/dashboard_datasets.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/dashboard_groups.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/dashboard_organizations.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/edit.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/edit_base.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/edit_user_form.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/followers.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/list.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/login.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/logout.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/logout_first.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/new.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/new_user_form.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/perform_reset.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/read.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/read_base.html -> build/lib/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/request_reset.html -> build/lib/ckan/templates-bs3/user
  creating build/lib/ckan/templates-bs3/user/snippets
  copying ckan/templates-bs3/user/snippets/api_token_list.html -> build/lib/ckan/templates-bs3/user/snippets
  copying ckan/templates-bs3/user/snippets/followers.html -> build/lib/ckan/templates-bs3/user/snippets
  copying ckan/templates-bs3/user/snippets/login_form.html -> build/lib/ckan/templates-bs3/user/snippets
  copying ckan/templates-bs3/user/snippets/placeholder.html -> build/lib/ckan/templates-bs3/user/snippets
  copying ckan/templates-bs3/user/snippets/recaptcha.html -> build/lib/ckan/templates-bs3/user/snippets
  copying ckan/templates-bs3/user/snippets/user_search.html -> build/lib/ckan/templates-bs3/user/snippets
  creating build/lib/ckan/templates/activity_streams
  copying ckan/templates/activity_streams/activity_stream_email_notifications.text -> build/lib/ckan/templates/activity_streams
  creating build/lib/ckan/templates/admin
  copying ckan/templates/admin/base.html -> build/lib/ckan/templates/admin
  copying ckan/templates/admin/config.html -> build/lib/ckan/templates/admin
  copying ckan/templates/admin/confirm_reset.html -> build/lib/ckan/templates/admin
  copying ckan/templates/admin/index.html -> build/lib/ckan/templates/admin
  copying ckan/templates/admin/trash.html -> build/lib/ckan/templates/admin
  creating build/lib/ckan/templates/admin/snippets
  copying ckan/templates/admin/snippets/confirm_delete.html -> build/lib/ckan/templates/admin/snippets
  copying ckan/templates/admin/snippets/data_type.html -> build/lib/ckan/templates/admin/snippets
  creating build/lib/ckan/templates/ajax_snippets
  copying ckan/templates/ajax_snippets/custom_fields.html -> build/lib/ckan/templates/ajax_snippets
  copying ckan/templates/ajax_snippets/follow_button.html -> build/lib/ckan/templates/ajax_snippets
  creating build/lib/ckan/templates/dataviewer
  copying ckan/templates/dataviewer/base.html -> build/lib/ckan/templates/dataviewer
  creating build/lib/ckan/templates/development
  copying ckan/templates/development/primer.html -> build/lib/ckan/templates/development
  creating build/lib/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/actions.html -> build/lib/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/breadcrumb.html -> build/lib/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/context.html -> build/lib/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/facet.html -> build/lib/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/form.html -> build/lib/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/form_stages.html -> build/lib/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/list.html -> build/lib/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/media_grid.html -> build/lib/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/module.html -> build/lib/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/nav.html -> build/lib/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/page_header.html -> build/lib/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/pagination.html -> build/lib/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/simple-input.html -> build/lib/ckan/templates/development/snippets
  creating build/lib/ckan/templates/emails
  copying ckan/templates/emails/invite_user.txt -> build/lib/ckan/templates/emails
  copying ckan/templates/emails/invite_user_subject.txt -> build/lib/ckan/templates/emails
  copying ckan/templates/emails/reset_password.txt -> build/lib/ckan/templates/emails
  copying ckan/templates/emails/reset_password_subject.txt -> build/lib/ckan/templates/emails
  creating build/lib/ckan/templates/group
  copying ckan/templates/group/about.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/admins.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/base_form_page.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/confirm_delete.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/confirm_delete_member.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/edit.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/edit_base.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/followers.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/index.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/member_new.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/members.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/new.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/new_group_form.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/read.html -> build/lib/ckan/templates/group
  copying ckan/templates/group/read_base.html -> build/lib/ckan/templates/group
  creating build/lib/ckan/templates/group/snippets
  copying ckan/templates/group/snippets/feeds.html -> build/lib/ckan/templates/group/snippets
  copying ckan/templates/group/snippets/group_form.html -> build/lib/ckan/templates/group/snippets
  copying ckan/templates/group/snippets/group_item.html -> build/lib/ckan/templates/group/snippets
  copying ckan/templates/group/snippets/group_list.html -> build/lib/ckan/templates/group/snippets
  copying ckan/templates/group/snippets/helper.html -> build/lib/ckan/templates/group/snippets
  copying ckan/templates/group/snippets/info.html -> build/lib/ckan/templates/group/snippets
  creating build/lib/ckan/templates/home
  copying ckan/templates/home/about.html -> build/lib/ckan/templates/home
  copying ckan/templates/home/index.html -> build/lib/ckan/templates/home
  copying ckan/templates/home/layout1.html -> build/lib/ckan/templates/home
  copying ckan/templates/home/layout2.html -> build/lib/ckan/templates/home
  copying ckan/templates/home/layout3.html -> build/lib/ckan/templates/home
  copying ckan/templates/home/robots.txt -> build/lib/ckan/templates/home
  creating build/lib/ckan/templates/home/snippets
  copying ckan/templates/home/snippets/about_text.html -> build/lib/ckan/templates/home/snippets
  copying ckan/templates/home/snippets/featured_group.html -> build/lib/ckan/templates/home/snippets
  copying ckan/templates/home/snippets/featured_organization.html -> build/lib/ckan/templates/home/snippets
  copying ckan/templates/home/snippets/promoted.html -> build/lib/ckan/templates/home/snippets
  copying ckan/templates/home/snippets/search.html -> build/lib/ckan/templates/home/snippets
  copying ckan/templates/home/snippets/stats.html -> build/lib/ckan/templates/home/snippets
  creating build/lib/ckan/templates/macros
  copying ckan/templates/macros/autoform.html -> build/lib/ckan/templates/macros
  copying ckan/templates/macros/form.html -> build/lib/ckan/templates/macros
  creating build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/attributes.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/checkbox.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/custom.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/errors.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/hidden.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/hidden_from_list.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/image_upload.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/info.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/input.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/input_block.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/markdown.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/prepend.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/required_message.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/select.html -> build/lib/ckan/templates/macros/form
  copying ckan/templates/macros/form/textarea.html -> build/lib/ckan/templates/macros/form
  creating build/lib/ckan/templates/organization
  copying ckan/templates/organization/about.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/admins.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/base_form_page.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/bulk_process.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/confirm_delete.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/confirm_delete_member.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/edit.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/edit_base.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/index.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/member_new.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/members.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/new.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/new_organization_form.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/read.html -> build/lib/ckan/templates/organization
  copying ckan/templates/organization/read_base.html -> build/lib/ckan/templates/organization
  creating build/lib/ckan/templates/organization/snippets
  copying ckan/templates/organization/snippets/feeds.html -> build/lib/ckan/templates/organization/snippets
  copying ckan/templates/organization/snippets/helper.html -> build/lib/ckan/templates/organization/snippets
  copying ckan/templates/organization/snippets/organization_form.html -> build/lib/ckan/templates/organization/snippets
  copying ckan/templates/organization/snippets/organization_item.html -> build/lib/ckan/templates/organization/snippets
  copying ckan/templates/organization/snippets/organization_list.html -> build/lib/ckan/templates/organization/snippets
  creating build/lib/ckan/templates/package
  copying ckan/templates/package/base.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/base_form_page.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/confirm_delete.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/confirm_delete_resource.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/edit.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/edit_base.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/edit_view.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/followers.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/group_list.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/new.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/new_package_form.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/new_resource.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/new_resource_not_draft.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/new_view.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/read.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/read_base.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/resource_edit.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/resource_edit_base.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/resource_read.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/resource_views.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/resources.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/search.html -> build/lib/ckan/templates/package
  copying ckan/templates/package/view_edit_base.html -> build/lib/ckan/templates/package
  creating build/lib/ckan/templates/package/collaborators
  copying ckan/templates/package/collaborators/collaborator_new.html -> build/lib/ckan/templates/package/collaborators
  copying ckan/templates/package/collaborators/collaborators.html -> build/lib/ckan/templates/package/collaborators
  copying ckan/templates/package/collaborators/confirm_delete.html -> build/lib/ckan/templates/package/collaborators
  creating build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/additional_info.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/cannot_create_package.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/info.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/new_package_breadcrumb.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/package_basic_fields.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/package_form.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/package_metadata_fields.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_edit_form.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_form.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_help.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_info.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_item.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_upload_field.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_view.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_view_embed.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_view_filters.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_views_list.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_views_list_item.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resources.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resources_list.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/stages.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/tags.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/view_form.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/view_form_filters.html -> build/lib/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/view_help.html -> build/lib/ckan/templates/package/snippets
  creating build/lib/ckan/templates/revision
  copying ckan/templates/revision/__init__.py -> build/lib/ckan/templates/revision
  creating build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/add_dataset.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/additional_info.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/context.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/csrf_input.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/custom_form_fields.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/datapusher_status.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/disqus_trackback.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/facet_list.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/follow_button.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/group.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/group_item.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/home_breadcrumb_item.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/language_selector.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/license.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/local_friendly_datetime.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/organization.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/organization_item.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/package_item.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/package_list.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/popular.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/private.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/search_form.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/search_result_text.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/simple_search.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/social.html -> build/lib/ckan/templates/snippets
  copying ckan/templates/snippets/tag_list.html -> build/lib/ckan/templates/snippets
  creating build/lib/ckan/templates/snippets/context
  copying ckan/templates/snippets/context/dataset.html -> build/lib/ckan/templates/snippets/context
  copying ckan/templates/snippets/context/group.html -> build/lib/ckan/templates/snippets/context
  copying ckan/templates/snippets/context/user.html -> build/lib/ckan/templates/snippets/context
  creating build/lib/ckan/templates/tests
  copying ckan/templates/tests/broken_helper_as_attribute.html -> build/lib/ckan/templates/tests
  copying ckan/templates/tests/broken_helper_as_item.html -> build/lib/ckan/templates/tests
  copying ckan/templates/tests/flash_messages.html -> build/lib/ckan/templates/tests
  copying ckan/templates/tests/helper_as_attribute.html -> build/lib/ckan/templates/tests
  copying ckan/templates/tests/helper_as_item.html -> build/lib/ckan/templates/tests
  copying ckan/templates/tests/mock_json_resource_preview_template.html -> build/lib/ckan/templates/tests
  copying ckan/templates/tests/mock_resource_preview_template.html -> build/lib/ckan/templates/tests
  creating build/lib/ckan/templates/user
  copying ckan/templates/user/api_tokens.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/confirm_delete.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/dashboard.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/dashboard_datasets.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/dashboard_groups.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/dashboard_organizations.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/edit.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/edit_base.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/edit_user_form.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/followers.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/list.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/login.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/logout.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/logout_first.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/new.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/new_user_form.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/perform_reset.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/read.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/read_base.html -> build/lib/ckan/templates/user
  copying ckan/templates/user/request_reset.html -> build/lib/ckan/templates/user
  creating build/lib/ckan/templates/user/snippets
  copying ckan/templates/user/snippets/api_token_list.html -> build/lib/ckan/templates/user/snippets
  copying ckan/templates/user/snippets/followers.html -> build/lib/ckan/templates/user/snippets
  copying ckan/templates/user/snippets/login_form.html -> build/lib/ckan/templates/user/snippets
  copying ckan/templates/user/snippets/placeholder.html -> build/lib/ckan/templates/user/snippets
  copying ckan/templates/user/snippets/recaptcha.html -> build/lib/ckan/templates/user/snippets
  copying ckan/templates/user/snippets/user_search.html -> build/lib/ckan/templates/user/snippets
  creating build/lib/ckan/tests
  copying ckan/tests/__init__.py -> build/lib/ckan/tests
  copying ckan/tests/factories.py -> build/lib/ckan/tests
  copying ckan/tests/helpers.py -> build/lib/ckan/tests
  copying ckan/tests/test_authz.py -> build/lib/ckan/tests
  copying ckan/tests/test_coding_standards.py -> build/lib/ckan/tests
  copying ckan/tests/test_common.py -> build/lib/ckan/tests
  copying ckan/tests/test_factories.py -> build/lib/ckan/tests
  copying ckan/tests/test_none_root.py -> build/lib/ckan/tests
  copying ckan/tests/test_robots_txt.py -> build/lib/ckan/tests
  creating build/lib/ckan/tests/cli
  copying ckan/tests/cli/__init__.py -> build/lib/ckan/tests/cli
  copying ckan/tests/cli/test_asset.py -> build/lib/ckan/tests/cli
  copying ckan/tests/cli/test_clean.py -> build/lib/ckan/tests/cli
  copying ckan/tests/cli/test_cli.py -> build/lib/ckan/tests/cli
  copying ckan/tests/cli/test_config.py -> build/lib/ckan/tests/cli
  copying ckan/tests/cli/test_config_tool.py -> build/lib/ckan/tests/cli
  copying ckan/tests/cli/test_db.py -> build/lib/ckan/tests/cli
  copying ckan/tests/cli/test_jobs.py -> build/lib/ckan/tests/cli
  copying ckan/tests/cli/test_search_index.py -> build/lib/ckan/tests/cli
  copying ckan/tests/cli/test_user.py -> build/lib/ckan/tests/cli
  creating build/lib/ckan/tests/cli/data
  copying ckan/tests/cli/data/test-env-var.ini -> build/lib/ckan/tests/cli/data
  copying ckan/tests/cli/data/test-invalid-use.ini -> build/lib/ckan/tests/cli/data
  copying ckan/tests/cli/data/test-no-env-var.ini -> build/lib/ckan/tests/cli/data
  copying ckan/tests/cli/data/test-one-recursive.ini -> build/lib/ckan/tests/cli/data
  copying ckan/tests/cli/data/test-one.ini -> build/lib/ckan/tests/cli/data
  copying ckan/tests/cli/data/test-three-recursive.ini -> build/lib/ckan/tests/cli/data
  copying ckan/tests/cli/data/test-three.ini -> build/lib/ckan/tests/cli/data
  creating build/lib/ckan/tests/cli/data/sub
  copying ckan/tests/cli/data/sub/test-two-recursive.ini -> build/lib/ckan/tests/cli/data/sub
  copying ckan/tests/cli/data/sub/test-two.ini -> build/lib/ckan/tests/cli/data/sub
  creating build/lib/ckan/tests/config
  copying ckan/tests/config/__init__.py -> build/lib/ckan/tests/config
  copying ckan/tests/config/test_environment.py -> build/lib/ckan/tests/config
  copying ckan/tests/config/test_middleware.py -> build/lib/ckan/tests/config
  copying ckan/tests/config/test_sessions.py -> build/lib/ckan/tests/config
  creating build/lib/ckan/tests/config/declaration
  copying ckan/tests/config/declaration/__init__.py -> build/lib/ckan/tests/config/declaration
  copying ckan/tests/config/declaration/test_declaration.py -> build/lib/ckan/tests/config/declaration
  copying ckan/tests/config/declaration/test_key.py -> build/lib/ckan/tests/config/declaration
  copying ckan/tests/config/declaration/test_option.py -> build/lib/ckan/tests/config/declaration
  creating build/lib/ckan/tests/controllers
  copying ckan/tests/controllers/__init__.py -> build/lib/ckan/tests/controllers
  copying ckan/tests/controllers/test_admin.py -> build/lib/ckan/tests/controllers
  copying ckan/tests/controllers/test_api.py -> build/lib/ckan/tests/controllers
  copying ckan/tests/controllers/test_feed.py -> build/lib/ckan/tests/controllers
  copying ckan/tests/controllers/test_group.py -> build/lib/ckan/tests/controllers
  copying ckan/tests/controllers/test_home.py -> build/lib/ckan/tests/controllers
  copying ckan/tests/controllers/test_organization.py -> build/lib/ckan/tests/controllers
  copying ckan/tests/controllers/test_package.py -> build/lib/ckan/tests/controllers
  copying ckan/tests/controllers/test_pagination.py -> build/lib/ckan/tests/controllers
  copying ckan/tests/controllers/test_resource.py -> build/lib/ckan/tests/controllers
  copying ckan/tests/controllers/test_user.py -> build/lib/ckan/tests/controllers
  copying ckan/tests/controllers/test_util.py -> build/lib/ckan/tests/controllers
  creating build/lib/ckan/tests/i18n
  copying ckan/tests/i18n/__init__.py -> build/lib/ckan/tests/i18n
  copying ckan/tests/i18n/test_check_po_files.py -> build/lib/ckan/tests/i18n
  creating build/lib/ckan/tests/lib
  copying ckan/tests/lib/__init__.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_app_globals.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_authenticator.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_base.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_config_tool.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_datapreview.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_formatters.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_hash.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_helpers.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_i18n.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_io.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_jobs.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_mailer.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_munge.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_signals.py -> build/lib/ckan/tests/lib
  copying ckan/tests/lib/test_uploader.py -> build/lib/ckan/tests/lib
  creating build/lib/ckan/tests/lib/dictization
  copying ckan/tests/lib/dictization/__init__.py -> build/lib/ckan/tests/lib/dictization
  copying ckan/tests/lib/dictization/test_dictization.py -> build/lib/ckan/tests/lib/dictization
  copying ckan/tests/lib/dictization/test_model_dictize.py -> build/lib/ckan/tests/lib/dictization
  creating build/lib/ckan/tests/lib/navl
  copying ckan/tests/lib/navl/__init__.py -> build/lib/ckan/tests/lib/navl
  copying ckan/tests/lib/navl/test_dictization_functions.py -> build/lib/ckan/tests/lib/navl
  copying ckan/tests/lib/navl/test_validators.py -> build/lib/ckan/tests/lib/navl
  creating build/lib/ckan/tests/lib/search
  copying ckan/tests/lib/search/__init__.py -> build/lib/ckan/tests/lib/search
  copying ckan/tests/lib/search/test_common.py -> build/lib/ckan/tests/lib/search
  copying ckan/tests/lib/search/test_index.py -> build/lib/ckan/tests/lib/search
  copying ckan/tests/lib/search/test_query.py -> build/lib/ckan/tests/lib/search
  copying ckan/tests/lib/search/test_search.py -> build/lib/ckan/tests/lib/search
  creating build/lib/ckan/tests/logic
  copying ckan/tests/logic/__init__.py -> build/lib/ckan/tests/logic
  copying ckan/tests/logic/test_conversion.py -> build/lib/ckan/tests/logic
  copying ckan/tests/logic/test_converters.py -> build/lib/ckan/tests/logic
  copying ckan/tests/logic/test_logic.py -> build/lib/ckan/tests/logic
  copying ckan/tests/logic/test_schema.py -> build/lib/ckan/tests/logic
  copying ckan/tests/logic/test_validators.py -> build/lib/ckan/tests/logic
  creating build/lib/ckan/tests/logic/action
  copying ckan/tests/logic/action/__init__.py -> build/lib/ckan/tests/logic/action
  copying ckan/tests/logic/action/test_create.py -> build/lib/ckan/tests/logic/action
  copying ckan/tests/logic/action/test_delete.py -> build/lib/ckan/tests/logic/action
  copying ckan/tests/logic/action/test_get.py -> build/lib/ckan/tests/logic/action
  copying ckan/tests/logic/action/test_init.py -> build/lib/ckan/tests/logic/action
  copying ckan/tests/logic/action/test_patch.py -> build/lib/ckan/tests/logic/action
  copying ckan/tests/logic/action/test_update.py -> build/lib/ckan/tests/logic/action
  creating build/lib/ckan/tests/logic/auth
  copying ckan/tests/logic/auth/__init__.py -> build/lib/ckan/tests/logic/auth
  copying ckan/tests/logic/auth/test_create.py -> build/lib/ckan/tests/logic/auth
  copying ckan/tests/logic/auth/test_delete.py -> build/lib/ckan/tests/logic/auth
  copying ckan/tests/logic/auth/test_get.py -> build/lib/ckan/tests/logic/auth
  copying ckan/tests/logic/auth/test_init.py -> build/lib/ckan/tests/logic/auth
  copying ckan/tests/logic/auth/test_update.py -> build/lib/ckan/tests/logic/auth
  creating build/lib/ckan/tests/model
  copying ckan/tests/model/__init__.py -> build/lib/ckan/tests/model
  copying ckan/tests/model/test_api_token.py -> build/lib/ckan/tests/model
  copying ckan/tests/model/test_follower.py -> build/lib/ckan/tests/model
  copying ckan/tests/model/test_group.py -> build/lib/ckan/tests/model
  copying ckan/tests/model/test_license.py -> build/lib/ckan/tests/model
  copying ckan/tests/model/test_misc.py -> build/lib/ckan/tests/model
  copying ckan/tests/model/test_package.py -> build/lib/ckan/tests/model
  copying ckan/tests/model/test_package_extra.py -> build/lib/ckan/tests/model
  copying ckan/tests/model/test_resource.py -> build/lib/ckan/tests/model
  copying ckan/tests/model/test_resource_view.py -> build/lib/ckan/tests/model
  copying ckan/tests/model/test_system_info.py -> build/lib/ckan/tests/model
  copying ckan/tests/model/test_tags.py -> build/lib/ckan/tests/model
  copying ckan/tests/model/test_user.py -> build/lib/ckan/tests/model
  creating build/lib/ckan/tests/plugins
  copying ckan/tests/plugins/__init__.py -> build/lib/ckan/tests/plugins
  copying ckan/tests/plugins/ckantestplugins.py -> build/lib/ckan/tests/plugins
  copying ckan/tests/plugins/mock_plugin.py -> build/lib/ckan/tests/plugins
  copying ckan/tests/plugins/test_blanket.py -> build/lib/ckan/tests/plugins
  copying ckan/tests/plugins/test_core.py -> build/lib/ckan/tests/plugins
  copying ckan/tests/plugins/test_interfaces.py -> build/lib/ckan/tests/plugins
  copying ckan/tests/plugins/test_toolkit.py -> build/lib/ckan/tests/plugins
  creating build/lib/ckan/tests/pytest_ckan
  copying ckan/tests/pytest_ckan/__init__.py -> build/lib/ckan/tests/pytest_ckan
  copying ckan/tests/pytest_ckan/ckan_setup.py -> build/lib/ckan/tests/pytest_ckan
  copying ckan/tests/pytest_ckan/fixtures.py -> build/lib/ckan/tests/pytest_ckan
  copying ckan/tests/pytest_ckan/test_fixtures.py -> build/lib/ckan/tests/pytest_ckan
  creating build/lib/ckan/types
  copying ckan/types/__init__.py -> build/lib/ckan/types
  copying ckan/types/model.py -> build/lib/ckan/types
  creating build/lib/ckan/types/logic
  copying ckan/types/logic/__init__.py -> build/lib/ckan/types/logic
  copying ckan/types/logic/action_result.py -> build/lib/ckan/types/logic
  creating build/lib/ckan/views
  copying ckan/views/__init__.py -> build/lib/ckan/views
  copying ckan/views/admin.py -> build/lib/ckan/views
  copying ckan/views/api.py -> build/lib/ckan/views
  copying ckan/views/dashboard.py -> build/lib/ckan/views
  copying ckan/views/dataset.py -> build/lib/ckan/views
  copying ckan/views/feed.py -> build/lib/ckan/views
  copying ckan/views/group.py -> build/lib/ckan/views
  copying ckan/views/home.py -> build/lib/ckan/views
  copying ckan/views/resource.py -> build/lib/ckan/views
  copying ckan/views/user.py -> build/lib/ckan/views
  copying ckan/views/util.py -> build/lib/ckan/views
  creating build/lib/ckanext/activity
  copying ckanext/activity/__init__.py -> build/lib/ckanext/activity
  copying ckanext/activity/changes.py -> build/lib/ckanext/activity
  copying ckanext/activity/email_notifications.py -> build/lib/ckanext/activity
  copying ckanext/activity/helpers.py -> build/lib/ckanext/activity
  copying ckanext/activity/plugin.py -> build/lib/ckanext/activity
  copying ckanext/activity/subscriptions.py -> build/lib/ckanext/activity
  copying ckanext/activity/views.py -> build/lib/ckanext/activity
  creating build/lib/ckanext/activity/assets
  copying ckanext/activity/assets/activity-stream.js -> build/lib/ckanext/activity/assets
  copying ckanext/activity/assets/activity.css -> build/lib/ckanext/activity/assets
  copying ckanext/activity/assets/activity.css.map -> build/lib/ckanext/activity/assets
  copying ckanext/activity/assets/activity.scss -> build/lib/ckanext/activity/assets
  copying ckanext/activity/assets/dashboard.js -> build/lib/ckanext/activity/assets
  copying ckanext/activity/assets/dashboard.spec.js -> build/lib/ckanext/activity/assets
  copying ckanext/activity/assets/webassets.yml -> build/lib/ckanext/activity/assets
  creating build/lib/ckanext/activity/logic
  copying ckanext/activity/logic/__init__.py -> build/lib/ckanext/activity/logic
  copying ckanext/activity/logic/action.py -> build/lib/ckanext/activity/logic
  copying ckanext/activity/logic/auth.py -> build/lib/ckanext/activity/logic
  copying ckanext/activity/logic/schema.py -> build/lib/ckanext/activity/logic
  copying ckanext/activity/logic/validators.py -> build/lib/ckanext/activity/logic
  creating build/lib/ckanext/activity/model
  copying ckanext/activity/model/__init__.py -> build/lib/ckanext/activity/model
  copying ckanext/activity/model/activity.py -> build/lib/ckanext/activity/model
  creating build/lib/ckanext/activity/public
  copying ckanext/activity/public/dotted.png -> build/lib/ckanext/activity/public
  creating build/lib/ckanext/activity/templates
  copying ckanext/activity/templates/base.html -> build/lib/ckanext/activity/templates
  copying ckanext/activity/templates/header.html -> build/lib/ckanext/activity/templates
  copying ckanext/activity/templates/page.html -> build/lib/ckanext/activity/templates
  creating build/lib/ckanext/activity/templates/activity_streams
  copying ckanext/activity/templates/activity_streams/activity_stream_email_notifications.text -> build/lib/ckanext/activity/templates/activity_streams
  creating build/lib/ckanext/activity/templates/ajax_snippets
  copying ckanext/activity/templates/ajax_snippets/dashboard.html -> build/lib/ckanext/activity/templates/ajax_snippets
  creating build/lib/ckanext/activity/templates/group
  copying ckanext/activity/templates/group/activity_stream.html -> build/lib/ckanext/activity/templates/group
  copying ckanext/activity/templates/group/changes.html -> build/lib/ckanext/activity/templates/group
  copying ckanext/activity/templates/group/read_base.html -> build/lib/ckanext/activity/templates/group
  creating build/lib/ckanext/activity/templates/group/snippets
  copying ckanext/activity/templates/group/snippets/item_group.html -> build/lib/ckanext/activity/templates/group/snippets
  creating build/lib/ckanext/activity/templates/organization
  copying ckanext/activity/templates/organization/activity_stream.html -> build/lib/ckanext/activity/templates/organization
  copying ckanext/activity/templates/organization/changes.html -> build/lib/ckanext/activity/templates/organization
  copying ckanext/activity/templates/organization/read_base.html -> build/lib/ckanext/activity/templates/organization
  creating build/lib/ckanext/activity/templates/organization/snippets
  copying ckanext/activity/templates/organization/snippets/item_organization.html -> build/lib/ckanext/activity/templates/organization/snippets
  creating build/lib/ckanext/activity/templates/package
  copying ckanext/activity/templates/package/activity_stream.html -> build/lib/ckanext/activity/templates/package
  copying ckanext/activity/templates/package/changes.html -> build/lib/ckanext/activity/templates/package
  copying ckanext/activity/templates/package/history.html -> build/lib/ckanext/activity/templates/package
  copying ckanext/activity/templates/package/read_base.html -> build/lib/ckanext/activity/templates/package
  copying ckanext/activity/templates/package/resource_history.html -> build/lib/ckanext/activity/templates/package
  creating build/lib/ckanext/activity/templates/package/snippets
  copying ckanext/activity/templates/package/snippets/change_item.html -> build/lib/ckanext/activity/templates/package/snippets
  copying ckanext/activity/templates/package/snippets/resource_item.html -> build/lib/ckanext/activity/templates/package/snippets
  copying ckanext/activity/templates/package/snippets/resources.html -> build/lib/ckanext/activity/templates/package/snippets
  copying ckanext/activity/templates/package/snippets/resources_list.html -> build/lib/ckanext/activity/templates/package/snippets
  creating build/lib/ckanext/activity/templates/snippets
  copying ckanext/activity/templates/snippets/activity_type_selector.html -> build/lib/ckanext/activity/templates/snippets
  copying ckanext/activity/templates/snippets/pagination.html -> build/lib/ckanext/activity/templates/snippets
  copying ckanext/activity/templates/snippets/stream.html -> build/lib/ckanext/activity/templates/snippets
  creating build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/added_tag.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/changed_group.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/changed_organization.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/changed_package.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/changed_resource.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/changed_user.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/deleted_group.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/deleted_organization.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/deleted_package.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/deleted_resource.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/fallback.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/follow_dataset.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/follow_group.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/follow_user.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/new_group.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/new_organization.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/new_package.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/new_resource.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/new_user.html -> build/lib/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/removed_tag.html -> build/lib/ckanext/activity/templates/snippets/activities
  creating build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/author.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/author_email.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/delete_resource.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/extension_fields.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/extra_fields.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/license.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/maintainer.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/maintainer_email.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/name.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/new_file.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/new_resource.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/no_change.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/notes.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/org.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/private.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/resource_desc.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/resource_extras.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/resource_format.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/resource_name.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/tags.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/title.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/url.html -> build/lib/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/version.html -> build/lib/ckanext/activity/templates/snippets/changes
  creating build/lib/ckanext/activity/templates/snippets/group_changes
  copying ckanext/activity/templates/snippets/group_changes/description.html -> build/lib/ckanext/activity/templates/snippets/group_changes
  copying ckanext/activity/templates/snippets/group_changes/image_url.html -> build/lib/ckanext/activity/templates/snippets/group_changes
  copying ckanext/activity/templates/snippets/group_changes/no_change.html -> build/lib/ckanext/activity/templates/snippets/group_changes
  copying ckanext/activity/templates/snippets/group_changes/title.html -> build/lib/ckanext/activity/templates/snippets/group_changes
  creating build/lib/ckanext/activity/templates/snippets/organization_changes
  copying ckanext/activity/templates/snippets/organization_changes/description.html -> build/lib/ckanext/activity/templates/snippets/organization_changes
  copying ckanext/activity/templates/snippets/organization_changes/image_url.html -> build/lib/ckanext/activity/templates/snippets/organization_changes
  copying ckanext/activity/templates/snippets/organization_changes/no_change.html -> build/lib/ckanext/activity/templates/snippets/organization_changes
  copying ckanext/activity/templates/snippets/organization_changes/title.html -> build/lib/ckanext/activity/templates/snippets/organization_changes
  creating build/lib/ckanext/activity/templates/user
  copying ckanext/activity/templates/user/activity_stream.html -> build/lib/ckanext/activity/templates/user
  copying ckanext/activity/templates/user/dashboard.html -> build/lib/ckanext/activity/templates/user
  copying ckanext/activity/templates/user/edit_user_form.html -> build/lib/ckanext/activity/templates/user
  copying ckanext/activity/templates/user/read_base.html -> build/lib/ckanext/activity/templates/user
  creating build/lib/ckanext/activity/templates/user/snippets
  copying ckanext/activity/templates/user/snippets/followee_dropdown.html -> build/lib/ckanext/activity/templates/user/snippets
  creating build/lib/ckanext/activity/tests
  copying ckanext/activity/tests/__init__.py -> build/lib/ckanext/activity/tests
  copying ckanext/activity/tests/conftest.py -> build/lib/ckanext/activity/tests
  copying ckanext/activity/tests/test_changes.py -> build/lib/ckanext/activity/tests
  copying ckanext/activity/tests/test_email_notifications.py -> build/lib/ckanext/activity/tests
  copying ckanext/activity/tests/test_helpers.py -> build/lib/ckanext/activity/tests
  copying ckanext/activity/tests/test_views.py -> build/lib/ckanext/activity/tests
  creating build/lib/ckanext/activity/tests/logic
  copying ckanext/activity/tests/logic/__init__.py -> build/lib/ckanext/activity/tests/logic
  copying ckanext/activity/tests/logic/test_action.py -> build/lib/ckanext/activity/tests/logic
  copying ckanext/activity/tests/logic/test_auth.py -> build/lib/ckanext/activity/tests/logic
  copying ckanext/activity/tests/logic/test_functional.py -> build/lib/ckanext/activity/tests/logic
  copying ckanext/activity/tests/logic/test_pagination.py -> build/lib/ckanext/activity/tests/logic
  creating build/lib/ckanext/activity/tests/model
  copying ckanext/activity/tests/model/__init__.py -> build/lib/ckanext/activity/tests/model
  copying ckanext/activity/tests/model/test_activity.py -> build/lib/ckanext/activity/tests/model
  creating build/lib/ckanext/audioview
  copying ckanext/audioview/__init__.py -> build/lib/ckanext/audioview
  copying ckanext/audioview/plugin.py -> build/lib/ckanext/audioview
  creating build/lib/ckanext/audioview/tests
  copying ckanext/audioview/tests/__init__.py -> build/lib/ckanext/audioview/tests
  copying ckanext/audioview/tests/test_view.py -> build/lib/ckanext/audioview/tests
  creating build/lib/ckanext/audioview/theme
  creating build/lib/ckanext/audioview/theme/templates
  copying ckanext/audioview/theme/templates/audio_form.html -> build/lib/ckanext/audioview/theme/templates
  copying ckanext/audioview/theme/templates/audio_view.html -> build/lib/ckanext/audioview/theme/templates
  creating build/lib/ckanext/chained_functions
  copying ckanext/chained_functions/__init__.py -> build/lib/ckanext/chained_functions
  copying ckanext/chained_functions/plugin.py -> build/lib/ckanext/chained_functions
  creating build/lib/ckanext/chained_functions/tests
  copying ckanext/chained_functions/tests/__init__.py -> build/lib/ckanext/chained_functions/tests
  copying ckanext/chained_functions/tests/test_plugin.py -> build/lib/ckanext/chained_functions/tests
  creating build/lib/ckanext/datapusher
  copying ckanext/datapusher/__init__.py -> build/lib/ckanext/datapusher
  copying ckanext/datapusher/cli.py -> build/lib/ckanext/datapusher
  copying ckanext/datapusher/config_declaration.yaml -> build/lib/ckanext/datapusher
  copying ckanext/datapusher/helpers.py -> build/lib/ckanext/datapusher
  copying ckanext/datapusher/interfaces.py -> build/lib/ckanext/datapusher
  copying ckanext/datapusher/plugin.py -> build/lib/ckanext/datapusher
  copying ckanext/datapusher/views.py -> build/lib/ckanext/datapusher
  creating build/lib/ckanext/datapusher/assets
  copying ckanext/datapusher/assets/datapusher.css -> build/lib/ckanext/datapusher/assets
  copying ckanext/datapusher/assets/datapusher.css.map -> build/lib/ckanext/datapusher/assets
  copying ckanext/datapusher/assets/datapusher.scss -> build/lib/ckanext/datapusher/assets
  copying ckanext/datapusher/assets/datapusher_popover.js -> build/lib/ckanext/datapusher/assets
  copying ckanext/datapusher/assets/webassets.yml -> build/lib/ckanext/datapusher/assets
  creating build/lib/ckanext/datapusher/logic
  copying ckanext/datapusher/logic/__init__.py -> build/lib/ckanext/datapusher/logic
  copying ckanext/datapusher/logic/action.py -> build/lib/ckanext/datapusher/logic
  copying ckanext/datapusher/logic/auth.py -> build/lib/ckanext/datapusher/logic
  copying ckanext/datapusher/logic/schema.py -> build/lib/ckanext/datapusher/logic
  creating build/lib/ckanext/datapusher/public
  copying ckanext/datapusher/public/dotted.png -> build/lib/ckanext/datapusher/public
  creating build/lib/ckanext/datapusher/templates
  creating build/lib/ckanext/datapusher/templates/datapusher
  copying ckanext/datapusher/templates/datapusher/resource_data.html -> build/lib/ckanext/datapusher/templates/datapusher
  creating build/lib/ckanext/datapusher/templates/package
  copying ckanext/datapusher/templates/package/resource_edit_base.html -> build/lib/ckanext/datapusher/templates/package
  creating build/lib/ckanext/datapusher/tests
  copying ckanext/datapusher/tests/__init__.py -> build/lib/ckanext/datapusher/tests
  copying ckanext/datapusher/tests/test.py -> build/lib/ckanext/datapusher/tests
  copying ckanext/datapusher/tests/test_action.py -> build/lib/ckanext/datapusher/tests
  copying ckanext/datapusher/tests/test_default_views.py -> build/lib/ckanext/datapusher/tests
  copying ckanext/datapusher/tests/test_interfaces.py -> build/lib/ckanext/datapusher/tests
  copying ckanext/datapusher/tests/test_views.py -> build/lib/ckanext/datapusher/tests
  creating build/lib/ckanext/datastore
  copying ckanext/datastore/__init__.py -> build/lib/ckanext/datastore
  copying ckanext/datastore/allowed_functions.txt -> build/lib/ckanext/datastore
  copying ckanext/datastore/blueprint.py -> build/lib/ckanext/datastore
  copying ckanext/datastore/cli.py -> build/lib/ckanext/datastore
  copying ckanext/datastore/config_declaration.yaml -> build/lib/ckanext/datastore
  copying ckanext/datastore/helpers.py -> build/lib/ckanext/datastore
  copying ckanext/datastore/interfaces.py -> build/lib/ckanext/datastore
  copying ckanext/datastore/plugin.py -> build/lib/ckanext/datastore
  copying ckanext/datastore/set_permissions.sql -> build/lib/ckanext/datastore
  copying ckanext/datastore/writer.py -> build/lib/ckanext/datastore
  creating build/lib/ckanext/datastore/backend
  copying ckanext/datastore/backend/__init__.py -> build/lib/ckanext/datastore/backend
  copying ckanext/datastore/backend/postgres.py -> build/lib/ckanext/datastore/backend
  creating build/lib/ckanext/datastore/logic
  copying ckanext/datastore/logic/__init__.py -> build/lib/ckanext/datastore/logic
  copying ckanext/datastore/logic/action.py -> build/lib/ckanext/datastore/logic
  copying ckanext/datastore/logic/auth.py -> build/lib/ckanext/datastore/logic
  copying ckanext/datastore/logic/schema.py -> build/lib/ckanext/datastore/logic
  creating build/lib/ckanext/datastore/templates
  creating build/lib/ckanext/datastore/templates/ajax_snippets
  copying ckanext/datastore/templates/ajax_snippets/api_info.html -> build/lib/ckanext/datastore/templates/ajax_snippets
  creating build/lib/ckanext/datastore/templates/datastore
  copying ckanext/datastore/templates/datastore/dictionary.html -> build/lib/ckanext/datastore/templates/datastore
  creating build/lib/ckanext/datastore/templates/datastore/snippets
  copying ckanext/datastore/templates/datastore/snippets/dictionary_form.html -> build/lib/ckanext/datastore/templates/datastore/snippets
  creating build/lib/ckanext/datastore/templates/package
  copying ckanext/datastore/templates/package/resource_edit_base.html -> build/lib/ckanext/datastore/templates/package
  copying ckanext/datastore/templates/package/resource_read.html -> build/lib/ckanext/datastore/templates/package
  creating build/lib/ckanext/datastore/templates/package/snippets
  copying ckanext/datastore/templates/package/snippets/data_api_button.html -> build/lib/ckanext/datastore/templates/package/snippets
  copying ckanext/datastore/templates/package/snippets/dictionary_table.html -> build/lib/ckanext/datastore/templates/package/snippets
  creating build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/__init__.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/conftest.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/helpers.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/sample_datastore_plugin.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_auth.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_chained_action.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_chained_auth_functions.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_create.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_db.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_delete.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_dictionary.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_disable.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_dump.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_helpers.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_info.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_interface.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_plugin.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_search.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_unit.py -> build/lib/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_upsert.py -> build/lib/ckanext/datastore/tests
  creating build/lib/ckanext/datatablesview
  copying ckanext/datatablesview/__init__.py -> build/lib/ckanext/datatablesview
  copying ckanext/datatablesview/blueprint.py -> build/lib/ckanext/datatablesview
  copying ckanext/datatablesview/config_declaration.yaml -> build/lib/ckanext/datatablesview
  copying ckanext/datatablesview/plugin.py -> build/lib/ckanext/datatablesview
  creating build/lib/ckanext/datatablesview/public
  copying ckanext/datatablesview/public/datatables_view.css -> build/lib/ckanext/datatablesview/public
  copying ckanext/datatablesview/public/datatablesview.js -> build/lib/ckanext/datatablesview/public
  copying ckanext/datatablesview/public/resource.config -> build/lib/ckanext/datatablesview/public
  copying ckanext/datatablesview/public/webassets.yml -> build/lib/ckanext/datatablesview/public
  creating build/lib/ckanext/datatablesview/public/vendor
  creating build/lib/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/dataTables.scrollResize.js -> build/lib/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/datatables.css -> build/lib/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/datatables.js -> build/lib/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/datatables.mark.css -> build/lib/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/datatables.mark.js -> build/lib/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/datetime.js -> build/lib/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/jquery.mark.js -> build/lib/ckanext/datatablesview/public/vendor/DataTables
  creating build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/af.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/am.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ar.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/az.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/az_az.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/be.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/bg.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/bn.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/bs.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ca.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/cs.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/cs_CZ.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/cy.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/da.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/de.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/el.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/en-gb.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/en_GB.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/eo.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/es.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/et.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/eu.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/fa.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/fi.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/fil.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/fr.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ga.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/gl.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/gu.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/he.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/hi.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/hr.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/hu.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/hy.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/id.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/id_alt.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/is.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/it.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ja.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ka.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/kk.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/km.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/kn.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ko.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ko_KR.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ku.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ky.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/lo.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/lt.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/lv.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/mk.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/mn.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ms.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ne.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/nl.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/no.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/no_nb.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/pa.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/pl.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ps.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/pt.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/pt_BR.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/pt_pt.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/rm.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ro.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ru.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/si.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sk.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sl.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/snd.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sq.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sr.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sr@latin.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sr_sp.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sv.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sw.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ta.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/te.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/tg.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/th.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/tl.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/tr.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/uk.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ur.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/uz.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/vi.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/zh.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/zh_CN.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/zh_Hant.json -> build/lib/ckanext/datatablesview/public/vendor/DataTables/i18n
  creating build/lib/ckanext/datatablesview/public/vendor/FontAwesome
  creating build/lib/ckanext/datatablesview/public/vendor/FontAwesome/images
  copying ckanext/datatablesview/public/vendor/FontAwesome/images/times-circle-solid.svg -> build/lib/ckanext/datatablesview/public/vendor/FontAwesome/images
  creating build/lib/ckanext/datatablesview/templates
  creating build/lib/ckanext/datatablesview/templates/datatables
  copying ckanext/datatablesview/templates/datatables/datatables_form.html -> build/lib/ckanext/datatablesview/templates/datatables
  copying ckanext/datatablesview/templates/datatables/datatables_view.html -> build/lib/ckanext/datatablesview/templates/datatables
  creating build/lib/ckanext/example_blanket_implementation
  copying ckanext/example_blanket_implementation/__init__.py -> build/lib/ckanext/example_blanket_implementation
  copying ckanext/example_blanket_implementation/cli.py -> build/lib/ckanext/example_blanket_implementation
  copying ckanext/example_blanket_implementation/config_declaration.yaml -> build/lib/ckanext/example_blanket_implementation
  copying ckanext/example_blanket_implementation/helpers.py -> build/lib/ckanext/example_blanket_implementation
  copying ckanext/example_blanket_implementation/plugin.py -> build/lib/ckanext/example_blanket_implementation
  copying ckanext/example_blanket_implementation/views.py -> build/lib/ckanext/example_blanket_implementation
  creating build/lib/ckanext/example_blanket_implementation/logic
  copying ckanext/example_blanket_implementation/logic/__init__.py -> build/lib/ckanext/example_blanket_implementation/logic
  copying ckanext/example_blanket_implementation/logic/auth.py -> build/lib/ckanext/example_blanket_implementation/logic
  copying ckanext/example_blanket_implementation/logic/validators.py -> build/lib/ckanext/example_blanket_implementation/logic
  creating build/lib/ckanext/example_blanket_implementation/logic/action
  copying ckanext/example_blanket_implementation/logic/action/__init__.py -> build/lib/ckanext/example_blanket_implementation/logic/action
  creating build/lib/ckanext/example_database_migrations
  copying ckanext/example_database_migrations/__init__.py -> build/lib/ckanext/example_database_migrations
  copying ckanext/example_database_migrations/plugin.py -> build/lib/ckanext/example_database_migrations
  creating build/lib/ckanext/example_database_migrations/migration
  creating build/lib/ckanext/example_database_migrations/migration/example_database_migrations
  copying ckanext/example_database_migrations/migration/example_database_migrations/env.py -> build/lib/ckanext/example_database_migrations/migration/example_database_migrations
  creating build/lib/ckanext/example_database_migrations/migration/example_database_migrations/versions
  copying ckanext/example_database_migrations/migration/example_database_migrations/versions/4f59069f433e_create_x_table.py -> build/lib/ckanext/example_database_migrations/migration/example_database_migrations/versions
  copying ckanext/example_database_migrations/migration/example_database_migrations/versions/728663ebe30e_create_y_table.py -> build/lib/ckanext/example_database_migrations/migration/example_database_migrations/versions
  creating build/lib/ckanext/example_flask_iblueprint
  copying ckanext/example_flask_iblueprint/__init__.py -> build/lib/ckanext/example_flask_iblueprint
  copying ckanext/example_flask_iblueprint/plugin.py -> build/lib/ckanext/example_flask_iblueprint
  creating build/lib/ckanext/example_flask_iblueprint/templates
  copying ckanext/example_flask_iblueprint/templates/about.html -> build/lib/ckanext/example_flask_iblueprint/templates
  copying ckanext/example_flask_iblueprint/templates/about_base.html -> build/lib/ckanext/example_flask_iblueprint/templates
  creating build/lib/ckanext/example_flask_iblueprint/tests
  copying ckanext/example_flask_iblueprint/tests/__init__.py -> build/lib/ckanext/example_flask_iblueprint/tests
  copying ckanext/example_flask_iblueprint/tests/test_routes.py -> build/lib/ckanext/example_flask_iblueprint/tests
  creating build/lib/ckanext/example_flask_streaming
  copying ckanext/example_flask_streaming/__init__.py -> build/lib/ckanext/example_flask_streaming
  copying ckanext/example_flask_streaming/plugin.py -> build/lib/ckanext/example_flask_streaming
  creating build/lib/ckanext/example_flask_streaming/templates
  copying ckanext/example_flask_streaming/templates/stream.html -> build/lib/ckanext/example_flask_streaming/templates
  creating build/lib/ckanext/example_flask_streaming/tests
  copying ckanext/example_flask_streaming/tests/__init__.py -> build/lib/ckanext/example_flask_streaming/tests
  copying ckanext/example_flask_streaming/tests/test_streaming_responses.py -> build/lib/ckanext/example_flask_streaming/tests
  creating build/lib/ckanext/example_humanizer
  copying ckanext/example_humanizer/__init__.py -> build/lib/ckanext/example_humanizer
  copying ckanext/example_humanizer/plugin.py -> build/lib/ckanext/example_humanizer
  creating build/lib/ckanext/example_humanizer/tests
  copying ckanext/example_humanizer/tests/__init__.py -> build/lib/ckanext/example_humanizer/tests
  copying ckanext/example_humanizer/tests/test_plugin.py -> build/lib/ckanext/example_humanizer/tests
  creating build/lib/ckanext/example_iapitoken
  copying ckanext/example_iapitoken/__init__.py -> build/lib/ckanext/example_iapitoken
  copying ckanext/example_iapitoken/plugin.py -> build/lib/ckanext/example_iapitoken
  creating build/lib/ckanext/example_iapitoken/tests
  copying ckanext/example_iapitoken/tests/__init__.py -> build/lib/ckanext/example_iapitoken/tests
  copying ckanext/example_iapitoken/tests/test_plugin.py -> build/lib/ckanext/example_iapitoken/tests
  creating build/lib/ckanext/example_iauthenticator
  copying ckanext/example_iauthenticator/__init__.py -> build/lib/ckanext/example_iauthenticator
  copying ckanext/example_iauthenticator/plugin.py -> build/lib/ckanext/example_iauthenticator
  creating build/lib/ckanext/example_iauthenticator/tests
  copying ckanext/example_iauthenticator/tests/test_example_iauthenticator.py -> build/lib/ckanext/example_iauthenticator/tests
  creating build/lib/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/__init__.py -> build/lib/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/plugin_v1.py -> build/lib/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/plugin_v2.py -> build/lib/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/plugin_v3.py -> build/lib/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/plugin_v4.py -> build/lib/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/plugin_v5_custom_config_setting.py -> build/lib/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/plugin_v6_parent_auth_functions.py -> build/lib/ckanext/example_iauthfunctions
  creating build/lib/ckanext/example_iauthfunctions/tests
  copying ckanext/example_iauthfunctions/tests/test_example_iauthfunctions.py -> build/lib/ckanext/example_iauthfunctions/tests
  creating build/lib/ckanext/example_iclick
  copying ckanext/example_iclick/__init__.py -> build/lib/ckanext/example_iclick
  copying ckanext/example_iclick/cli.py -> build/lib/ckanext/example_iclick
  copying ckanext/example_iclick/plugin.py -> build/lib/ckanext/example_iclick
  creating build/lib/ckanext/example_iconfigurer
  copying ckanext/example_iconfigurer/__init__.py -> build/lib/ckanext/example_iconfigurer
  copying ckanext/example_iconfigurer/blueprint.py -> build/lib/ckanext/example_iconfigurer
  copying ckanext/example_iconfigurer/plugin.py -> build/lib/ckanext/example_iconfigurer
  copying ckanext/example_iconfigurer/plugin_v1.py -> build/lib/ckanext/example_iconfigurer
  copying ckanext/example_iconfigurer/plugin_v2.py -> build/lib/ckanext/example_iconfigurer
  creating build/lib/ckanext/example_iconfigurer/templates
  creating build/lib/ckanext/example_iconfigurer/templates/admin
  copying ckanext/example_iconfigurer/templates/admin/config.html -> build/lib/ckanext/example_iconfigurer/templates/admin
  copying ckanext/example_iconfigurer/templates/admin/myext_config.html -> build/lib/ckanext/example_iconfigurer/templates/admin
  creating build/lib/ckanext/example_iconfigurer/tests
  copying ckanext/example_iconfigurer/tests/__init__.py -> build/lib/ckanext/example_iconfigurer/tests
  copying ckanext/example_iconfigurer/tests/test_example_iconfigurer.py -> build/lib/ckanext/example_iconfigurer/tests
  copying ckanext/example_iconfigurer/tests/test_iconfigurer_toolkit.py -> build/lib/ckanext/example_iconfigurer/tests
  copying ckanext/example_iconfigurer/tests/test_iconfigurer_update_config.py -> build/lib/ckanext/example_iconfigurer/tests
  creating build/lib/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/__init__.py -> build/lib/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin.py -> build/lib/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v1.py -> build/lib/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v2.py -> build/lib/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v3.py -> build/lib/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v4.py -> build/lib/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v5.py -> build/lib/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v6.py -> build/lib/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v7.py -> build/lib/ckanext/example_idatasetform
  creating build/lib/ckanext/example_idatasetform/templates
  creating build/lib/ckanext/example_idatasetform/templates/first
  copying ckanext/example_idatasetform/templates/first/new.html -> build/lib/ckanext/example_idatasetform/templates/first
  copying ckanext/example_idatasetform/templates/first/read.html -> build/lib/ckanext/example_idatasetform/templates/first
  creating build/lib/ckanext/example_idatasetform/templates/package
  copying ckanext/example_idatasetform/templates/package/read.html -> build/lib/ckanext/example_idatasetform/templates/package
  copying ckanext/example_idatasetform/templates/package/search.html -> build/lib/ckanext/example_idatasetform/templates/package
  creating build/lib/ckanext/example_idatasetform/templates/package/snippets
  copying ckanext/example_idatasetform/templates/package/snippets/additional_info.html -> build/lib/ckanext/example_idatasetform/templates/package/snippets
  copying ckanext/example_idatasetform/templates/package/snippets/package_basic_fields.html -> build/lib/ckanext/example_idatasetform/templates/package/snippets
  copying ckanext/example_idatasetform/templates/package/snippets/package_metadata_fields.html -> build/lib/ckanext/example_idatasetform/templates/package/snippets
  copying ckanext/example_idatasetform/templates/package/snippets/resource_form.html -> build/lib/ckanext/example_idatasetform/templates/package/snippets
  creating build/lib/ckanext/example_idatasetform/templates/second
  copying ckanext/example_idatasetform/templates/second/read.html -> build/lib/ckanext/example_idatasetform/templates/second
  creating build/lib/ckanext/example_idatasetform/tests
  copying ckanext/example_idatasetform/tests/__init__.py -> build/lib/ckanext/example_idatasetform/tests
  copying ckanext/example_idatasetform/tests/test_controllers.py -> build/lib/ckanext/example_idatasetform/tests
  copying ckanext/example_idatasetform/tests/test_example_idatasetform.py -> build/lib/ckanext/example_idatasetform/tests
  creating build/lib/ckanext/example_idatastorebackend
  copying ckanext/example_idatastorebackend/__init__.py -> build/lib/ckanext/example_idatastorebackend
  copying ckanext/example_idatastorebackend/example_sqlite.py -> build/lib/ckanext/example_idatastorebackend
  copying ckanext/example_idatastorebackend/plugin.py -> build/lib/ckanext/example_idatastorebackend
  creating build/lib/ckanext/example_idatastorebackend/test
  copying ckanext/example_idatastorebackend/test/__init__.py -> build/lib/ckanext/example_idatastorebackend/test
  copying ckanext/example_idatastorebackend/test/test_plugin.py -> build/lib/ckanext/example_idatastorebackend/test
  creating build/lib/ckanext/example_igroupform
  copying ckanext/example_igroupform/__init__.py -> build/lib/ckanext/example_igroupform
  copying ckanext/example_igroupform/plugin.py -> build/lib/ckanext/example_igroupform
  copying ckanext/example_igroupform/plugin_v2.py -> build/lib/ckanext/example_igroupform
  creating build/lib/ckanext/example_igroupform/templates
  creating build/lib/ckanext/example_igroupform/templates/example_igroup_form
  copying ckanext/example_igroupform/templates/example_igroup_form/group_form.html -> build/lib/ckanext/example_igroupform/templates/example_igroup_form
  creating build/lib/ckanext/example_igroupform/tests
  copying ckanext/example_igroupform/tests/__init__.py -> build/lib/ckanext/example_igroupform/tests
  copying ckanext/example_igroupform/tests/test_controllers.py -> build/lib/ckanext/example_igroupform/tests
  creating build/lib/ckanext/example_ipermissionlabels
  copying ckanext/example_ipermissionlabels/__init__.py -> build/lib/ckanext/example_ipermissionlabels
  copying ckanext/example_ipermissionlabels/plugin.py -> build/lib/ckanext/example_ipermissionlabels
  creating build/lib/ckanext/example_ipermissionlabels/tests
  copying ckanext/example_ipermissionlabels/tests/__init__.py -> build/lib/ckanext/example_ipermissionlabels/tests
  copying ckanext/example_ipermissionlabels/tests/test_example_ipermissionlabels.py -> build/lib/ckanext/example_ipermissionlabels/tests
  creating build/lib/ckanext/example_iresourcecontroller
  copying ckanext/example_iresourcecontroller/__init__.py -> build/lib/ckanext/example_iresourcecontroller
  copying ckanext/example_iresourcecontroller/plugin.py -> build/lib/ckanext/example_iresourcecontroller
  creating build/lib/ckanext/example_iresourcecontroller/tests
  copying ckanext/example_iresourcecontroller/tests/test_example_iresourcecontroller.py -> build/lib/ckanext/example_iresourcecontroller/tests
  creating build/lib/ckanext/example_isignal
  copying ckanext/example_isignal/__init__.py -> build/lib/ckanext/example_isignal
  copying ckanext/example_isignal/plugin.py -> build/lib/ckanext/example_isignal
  creating build/lib/ckanext/example_isignal/tests
  copying ckanext/example_isignal/tests/__init__.py -> build/lib/ckanext/example_isignal/tests
  copying ckanext/example_isignal/tests/test_plugin.py -> build/lib/ckanext/example_isignal/tests
  creating build/lib/ckanext/example_itemplatehelpers
  copying ckanext/example_itemplatehelpers/__init__.py -> build/lib/ckanext/example_itemplatehelpers
  copying ckanext/example_itemplatehelpers/plugin.py -> build/lib/ckanext/example_itemplatehelpers
  creating build/lib/ckanext/example_itemplatehelpers/templates
  creating build/lib/ckanext/example_itemplatehelpers/templates/home
  copying ckanext/example_itemplatehelpers/templates/home/index.html -> build/lib/ckanext/example_itemplatehelpers/templates/home
  creating build/lib/ckanext/example_itemplatehelpers/tests
  copying ckanext/example_itemplatehelpers/tests/__init__.py -> build/lib/ckanext/example_itemplatehelpers/tests
  copying ckanext/example_itemplatehelpers/tests/test_plugin.py -> build/lib/ckanext/example_itemplatehelpers/tests
  creating build/lib/ckanext/example_itranslation
  copying ckanext/example_itranslation/__init__.py -> build/lib/ckanext/example_itranslation
  copying ckanext/example_itranslation/plugin.py -> build/lib/ckanext/example_itranslation
  copying ckanext/example_itranslation/plugin_v1.py -> build/lib/ckanext/example_itranslation
  creating build/lib/ckanext/example_itranslation/i18n
  copying ckanext/example_itranslation/i18n/ckanext-example_itranslation.pot -> build/lib/ckanext/example_itranslation/i18n
  creating build/lib/ckanext/example_itranslation/i18n/en
  creating build/lib/ckanext/example_itranslation/i18n/en/LC_MESSAGES
  copying ckanext/example_itranslation/i18n/en/LC_MESSAGES/ckanext-example_itranslation.mo -> build/lib/ckanext/example_itranslation/i18n/en/LC_MESSAGES
  copying ckanext/example_itranslation/i18n/en/LC_MESSAGES/ckanext-example_itranslation.po -> build/lib/ckanext/example_itranslation/i18n/en/LC_MESSAGES
  copying ckanext/example_itranslation/i18n/en/LC_MESSAGES/ckanext-example_translation.po -> build/lib/ckanext/example_itranslation/i18n/en/LC_MESSAGES
  creating build/lib/ckanext/example_itranslation/i18n/fr
  creating build/lib/ckanext/example_itranslation/i18n/fr/LC_MESSAGES
  copying ckanext/example_itranslation/i18n/fr/LC_MESSAGES/ckanext-example_itranslation.mo -> build/lib/ckanext/example_itranslation/i18n/fr/LC_MESSAGES
  copying ckanext/example_itranslation/i18n/fr/LC_MESSAGES/ckanext-example_itranslation.po -> build/lib/ckanext/example_itranslation/i18n/fr/LC_MESSAGES
  creating build/lib/ckanext/example_itranslation/templates
  creating build/lib/ckanext/example_itranslation/templates/home
  copying ckanext/example_itranslation/templates/home/index.html -> build/lib/ckanext/example_itranslation/templates/home
  creating build/lib/ckanext/example_itranslation/tests
  copying ckanext/example_itranslation/tests/__init__.py -> build/lib/ckanext/example_itranslation/tests
  copying ckanext/example_itranslation/tests/test_plugin.py -> build/lib/ckanext/example_itranslation/tests
  creating build/lib/ckanext/example_iuploader
  copying ckanext/example_iuploader/__init__.py -> build/lib/ckanext/example_iuploader
  copying ckanext/example_iuploader/plugin.py -> build/lib/ckanext/example_iuploader
  creating build/lib/ckanext/example_iuploader/test
  copying ckanext/example_iuploader/test/__init__.py -> build/lib/ckanext/example_iuploader/test
  copying ckanext/example_iuploader/test/test_plugin.py -> build/lib/ckanext/example_iuploader/test
  creating build/lib/ckanext/example_ivalidators
  copying ckanext/example_ivalidators/__init__.py -> build/lib/ckanext/example_ivalidators
  copying ckanext/example_ivalidators/plugin.py -> build/lib/ckanext/example_ivalidators
  creating build/lib/ckanext/example_ivalidators/tests
  copying ckanext/example_ivalidators/tests/__init__.py -> build/lib/ckanext/example_ivalidators/tests
  copying ckanext/example_ivalidators/tests/test_ivalidators.py -> build/lib/ckanext/example_ivalidators/tests
  creating build/lib/ckanext/example_theme_docs
  copying ckanext/example_theme_docs/__init__.py -> build/lib/ckanext/example_theme_docs
  creating build/lib/ckanext/example_theme_docs/custom_config_setting
  copying ckanext/example_theme_docs/custom_config_setting/__init__.py -> build/lib/ckanext/example_theme_docs/custom_config_setting
  copying ckanext/example_theme_docs/custom_config_setting/plugin.py -> build/lib/ckanext/example_theme_docs/custom_config_setting
  creating build/lib/ckanext/example_theme_docs/custom_emails
  copying ckanext/example_theme_docs/custom_emails/__init__.py -> build/lib/ckanext/example_theme_docs/custom_emails
  copying ckanext/example_theme_docs/custom_emails/plugin.py -> build/lib/ckanext/example_theme_docs/custom_emails
  copying ckanext/example_theme_docs/custom_emails/test_custom_emails.py -> build/lib/ckanext/example_theme_docs/custom_emails
  creating build/lib/ckanext/example_theme_docs/v01_empty_extension
  copying ckanext/example_theme_docs/v01_empty_extension/__init__.py -> build/lib/ckanext/example_theme_docs/v01_empty_extension
  copying ckanext/example_theme_docs/v01_empty_extension/plugin.py -> build/lib/ckanext/example_theme_docs/v01_empty_extension
  creating build/lib/ckanext/example_theme_docs/v02_empty_template
  copying ckanext/example_theme_docs/v02_empty_template/__init__.py -> build/lib/ckanext/example_theme_docs/v02_empty_template
  copying ckanext/example_theme_docs/v02_empty_template/plugin.py -> build/lib/ckanext/example_theme_docs/v02_empty_template
  creating build/lib/ckanext/example_theme_docs/v03_jinja
  copying ckanext/example_theme_docs/v03_jinja/__init__.py -> build/lib/ckanext/example_theme_docs/v03_jinja
  copying ckanext/example_theme_docs/v03_jinja/plugin.py -> build/lib/ckanext/example_theme_docs/v03_jinja
  creating build/lib/ckanext/example_theme_docs/v04_ckan_extends
  copying ckanext/example_theme_docs/v04_ckan_extends/__init__.py -> build/lib/ckanext/example_theme_docs/v04_ckan_extends
  copying ckanext/example_theme_docs/v04_ckan_extends/plugin.py -> build/lib/ckanext/example_theme_docs/v04_ckan_extends
  creating build/lib/ckanext/example_theme_docs/v05_block
  copying ckanext/example_theme_docs/v05_block/__init__.py -> build/lib/ckanext/example_theme_docs/v05_block
  copying ckanext/example_theme_docs/v05_block/plugin.py -> build/lib/ckanext/example_theme_docs/v05_block
  creating build/lib/ckanext/example_theme_docs/v06_super
  copying ckanext/example_theme_docs/v06_super/__init__.py -> build/lib/ckanext/example_theme_docs/v06_super
  copying ckanext/example_theme_docs/v06_super/plugin.py -> build/lib/ckanext/example_theme_docs/v06_super
  creating build/lib/ckanext/example_theme_docs/v07_helper_function
  copying ckanext/example_theme_docs/v07_helper_function/__init__.py -> build/lib/ckanext/example_theme_docs/v07_helper_function
  copying ckanext/example_theme_docs/v07_helper_function/plugin.py -> build/lib/ckanext/example_theme_docs/v07_helper_function
  creating build/lib/ckanext/example_theme_docs/v08_custom_helper_function
  copying ckanext/example_theme_docs/v08_custom_helper_function/__init__.py -> build/lib/ckanext/example_theme_docs/v08_custom_helper_function
  copying ckanext/example_theme_docs/v08_custom_helper_function/plugin.py -> build/lib/ckanext/example_theme_docs/v08_custom_helper_function
  creating build/lib/ckanext/example_theme_docs/v09_snippet
  copying ckanext/example_theme_docs/v09_snippet/__init__.py -> build/lib/ckanext/example_theme_docs/v09_snippet
  copying ckanext/example_theme_docs/v09_snippet/plugin.py -> build/lib/ckanext/example_theme_docs/v09_snippet
  creating build/lib/ckanext/example_theme_docs/v10_custom_snippet
  copying ckanext/example_theme_docs/v10_custom_snippet/__init__.py -> build/lib/ckanext/example_theme_docs/v10_custom_snippet
  copying ckanext/example_theme_docs/v10_custom_snippet/plugin.py -> build/lib/ckanext/example_theme_docs/v10_custom_snippet
  creating build/lib/ckanext/example_theme_docs/v11_HTML_and_CSS
  copying ckanext/example_theme_docs/v11_HTML_and_CSS/__init__.py -> build/lib/ckanext/example_theme_docs/v11_HTML_and_CSS
  copying ckanext/example_theme_docs/v11_HTML_and_CSS/plugin.py -> build/lib/ckanext/example_theme_docs/v11_HTML_and_CSS
  creating build/lib/ckanext/example_theme_docs/v12_extra_public_dir
  copying ckanext/example_theme_docs/v12_extra_public_dir/__init__.py -> build/lib/ckanext/example_theme_docs/v12_extra_public_dir
  copying ckanext/example_theme_docs/v12_extra_public_dir/plugin.py -> build/lib/ckanext/example_theme_docs/v12_extra_public_dir
  creating build/lib/ckanext/example_theme_docs/v13_custom_css
  copying ckanext/example_theme_docs/v13_custom_css/__init__.py -> build/lib/ckanext/example_theme_docs/v13_custom_css
  copying ckanext/example_theme_docs/v13_custom_css/plugin.py -> build/lib/ckanext/example_theme_docs/v13_custom_css
  creating build/lib/ckanext/example_theme_docs/v14_more_custom_css
  copying ckanext/example_theme_docs/v14_more_custom_css/__init__.py -> build/lib/ckanext/example_theme_docs/v14_more_custom_css
  copying ckanext/example_theme_docs/v14_more_custom_css/plugin.py -> build/lib/ckanext/example_theme_docs/v14_more_custom_css
  creating build/lib/ckanext/example_theme_docs/v15_webassets
  copying ckanext/example_theme_docs/v15_webassets/__init__.py -> build/lib/ckanext/example_theme_docs/v15_webassets
  copying ckanext/example_theme_docs/v15_webassets/plugin.py -> build/lib/ckanext/example_theme_docs/v15_webassets
  creating build/lib/ckanext/example_theme_docs/v16_initialize_a_javascript_module
  copying ckanext/example_theme_docs/v16_initialize_a_javascript_module/__init__.py -> build/lib/ckanext/example_theme_docs/v16_initialize_a_javascript_module
  copying ckanext/example_theme_docs/v16_initialize_a_javascript_module/plugin.py -> build/lib/ckanext/example_theme_docs/v16_initialize_a_javascript_module
  creating build/lib/ckanext/example_theme_docs/v17_popover
  copying ckanext/example_theme_docs/v17_popover/__init__.py -> build/lib/ckanext/example_theme_docs/v17_popover
  copying ckanext/example_theme_docs/v17_popover/plugin.py -> build/lib/ckanext/example_theme_docs/v17_popover
  creating build/lib/ckanext/example_theme_docs/v18_snippet_api
  copying ckanext/example_theme_docs/v18_snippet_api/__init__.py -> build/lib/ckanext/example_theme_docs/v18_snippet_api
  copying ckanext/example_theme_docs/v18_snippet_api/plugin.py -> build/lib/ckanext/example_theme_docs/v18_snippet_api
  creating build/lib/ckanext/example_theme_docs/v19_01_error
  copying ckanext/example_theme_docs/v19_01_error/__init__.py -> build/lib/ckanext/example_theme_docs/v19_01_error
  copying ckanext/example_theme_docs/v19_01_error/plugin.py -> build/lib/ckanext/example_theme_docs/v19_01_error
  creating build/lib/ckanext/example_theme_docs/v19_02_error_handling
  copying ckanext/example_theme_docs/v19_02_error_handling/__init__.py -> build/lib/ckanext/example_theme_docs/v19_02_error_handling
  copying ckanext/example_theme_docs/v19_02_error_handling/plugin.py -> build/lib/ckanext/example_theme_docs/v19_02_error_handling
  creating build/lib/ckanext/example_theme_docs/v20_pubsub
  copying ckanext/example_theme_docs/v20_pubsub/__init__.py -> build/lib/ckanext/example_theme_docs/v20_pubsub
  copying ckanext/example_theme_docs/v20_pubsub/plugin.py -> build/lib/ckanext/example_theme_docs/v20_pubsub
  creating build/lib/ckanext/example_theme_docs/v21_custom_jquery_plugin
  copying ckanext/example_theme_docs/v21_custom_jquery_plugin/__init__.py -> build/lib/ckanext/example_theme_docs/v21_custom_jquery_plugin
  copying ckanext/example_theme_docs/v21_custom_jquery_plugin/plugin.py -> build/lib/ckanext/example_theme_docs/v21_custom_jquery_plugin
  creating build/lib/ckanext/example_theme_docs/v22_webassets
  copying ckanext/example_theme_docs/v22_webassets/__init__.py -> build/lib/ckanext/example_theme_docs/v22_webassets
  copying ckanext/example_theme_docs/v22_webassets/plugin.py -> build/lib/ckanext/example_theme_docs/v22_webassets
  creating build/lib/ckanext/expire_api_token
  copying ckanext/expire_api_token/__init__.py -> build/lib/ckanext/expire_api_token
  copying ckanext/expire_api_token/plugin.py -> build/lib/ckanext/expire_api_token
  creating build/lib/ckanext/expire_api_token/templates
  creating build/lib/ckanext/expire_api_token/templates/user
  copying ckanext/expire_api_token/templates/user/api_tokens.html -> build/lib/ckanext/expire_api_token/templates/user
  creating build/lib/ckanext/expire_api_token/templates/user/snippets
  copying ckanext/expire_api_token/templates/user/snippets/api_token_list.html -> build/lib/ckanext/expire_api_token/templates/user/snippets
  creating build/lib/ckanext/expire_api_token/tests
  copying ckanext/expire_api_token/tests/__init__.py -> build/lib/ckanext/expire_api_token/tests
  copying ckanext/expire_api_token/tests/test_plugin.py -> build/lib/ckanext/expire_api_token/tests
  creating build/lib/ckanext/imageview
  copying ckanext/imageview/__init__.py -> build/lib/ckanext/imageview
  copying ckanext/imageview/config_declaration.yaml -> build/lib/ckanext/imageview
  copying ckanext/imageview/plugin.py -> build/lib/ckanext/imageview
  creating build/lib/ckanext/imageview/tests
  copying ckanext/imageview/tests/__init__.py -> build/lib/ckanext/imageview/tests
  copying ckanext/imageview/tests/test_view.py -> build/lib/ckanext/imageview/tests
  creating build/lib/ckanext/imageview/theme
  creating build/lib/ckanext/imageview/theme/templates
  copying ckanext/imageview/theme/templates/image_form.html -> build/lib/ckanext/imageview/theme/templates
  copying ckanext/imageview/theme/templates/image_view.html -> build/lib/ckanext/imageview/theme/templates
  creating build/lib/ckanext/multilingual
  copying ckanext/multilingual/__init__.py -> build/lib/ckanext/multilingual
  copying ckanext/multilingual/plugin.py -> build/lib/ckanext/multilingual
  creating build/lib/ckanext/multilingual/tests
  copying ckanext/multilingual/tests/test_multilingual_plugin.py -> build/lib/ckanext/multilingual/tests
  creating build/lib/ckanext/reclineview
  copying ckanext/reclineview/__init__.py -> build/lib/ckanext/reclineview
  copying ckanext/reclineview/config_declaration.yaml -> build/lib/ckanext/reclineview
  copying ckanext/reclineview/plugin.py -> build/lib/ckanext/reclineview
  creating build/lib/ckanext/reclineview/tests
  copying ckanext/reclineview/tests/__init__.py -> build/lib/ckanext/reclineview/tests
  copying ckanext/reclineview/tests/test_view.py -> build/lib/ckanext/reclineview/tests
  creating build/lib/ckanext/reclineview/theme
  creating build/lib/ckanext/reclineview/theme/public
  copying ckanext/reclineview/theme/public/recline_view.js -> build/lib/ckanext/reclineview/theme/public
  copying ckanext/reclineview/theme/public/recline_view.min.js -> build/lib/ckanext/reclineview/theme/public
  copying ckanext/reclineview/theme/public/resource.config -> build/lib/ckanext/reclineview/theme/public
  copying ckanext/reclineview/theme/public/webassets.yml -> build/lib/ckanext/reclineview/theme/public
  copying ckanext/reclineview/theme/public/widget.recordcount.js -> build/lib/ckanext/reclineview/theme/public
  copying ckanext/reclineview/theme/public/widget.recordcount.min.js -> build/lib/ckanext/reclineview/theme/public
  creating build/lib/ckanext/reclineview/theme/public/css
  copying ckanext/reclineview/theme/public/css/recline.css -> build/lib/ckanext/reclineview/theme/public/css
  copying ckanext/reclineview/theme/public/css/recline.min.css -> build/lib/ckanext/reclineview/theme/public/css
  creating build/lib/ckanext/reclineview/theme/public/img
  copying ckanext/reclineview/theme/public/img/ajaxload-circle.gif -> build/lib/ckanext/reclineview/theme/public/img
  creating build/lib/ckanext/reclineview/theme/public/vendor
  creating build/lib/ckanext/reclineview/theme/public/vendor/backbone
  creating build/lib/ckanext/reclineview/theme/public/vendor/backbone/1.0.0
  copying ckanext/reclineview/theme/public/vendor/backbone/1.0.0/backbone.js -> build/lib/ckanext/reclineview/theme/public/vendor/backbone/1.0.0
  creating build/lib/ckanext/reclineview/theme/public/vendor/bootstrap
  creating build/lib/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0
  creating build/lib/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/css
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/css/bootstrap-theme.css -> build/lib/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/css
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/css/bootstrap.css -> build/lib/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/css
  creating build/lib/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts/glyphicons-halflings-regular.eot -> build/lib/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts/glyphicons-halflings-regular.svg -> build/lib/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts/glyphicons-halflings-regular.ttf -> build/lib/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts/glyphicons-halflings-regular.woff -> build/lib/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts
  creating build/lib/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/js
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/js/bootstrap.js -> build/lib/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/js
  creating build/lib/ckanext/reclineview/theme/public/vendor/ckan.js
  copying ckanext/reclineview/theme/public/vendor/ckan.js/ckan.js -> build/lib/ckanext/reclineview/theme/public/vendor/ckan.js
  creating build/lib/ckanext/reclineview/theme/public/vendor/flot
  copying ckanext/reclineview/theme/public/vendor/flot/excanvas.js -> build/lib/ckanext/reclineview/theme/public/vendor/flot
  copying ckanext/reclineview/theme/public/vendor/flot/excanvas.min.js -> build/lib/ckanext/reclineview/theme/public/vendor/flot
  copying ckanext/reclineview/theme/public/vendor/flot/jquery.flot.js -> build/lib/ckanext/reclineview/theme/public/vendor/flot
  copying ckanext/reclineview/theme/public/vendor/flot/jquery.flot.time.js -> build/lib/ckanext/reclineview/theme/public/vendor/flot
  creating build/lib/ckanext/reclineview/theme/public/vendor/flotr2
  copying ckanext/reclineview/theme/public/vendor/flotr2/flotr2.js -> build/lib/ckanext/reclineview/theme/public/vendor/flotr2
  copying ckanext/reclineview/theme/public/vendor/flotr2/flotr2.min.js -> build/lib/ckanext/reclineview/theme/public/vendor/flotr2
  creating build/lib/ckanext/reclineview/theme/public/vendor/jquery
  creating build/lib/ckanext/reclineview/theme/public/vendor/jquery/1.7.1
  copying ckanext/reclineview/theme/public/vendor/jquery/1.7.1/jquery.js -> build/lib/ckanext/reclineview/theme/public/vendor/jquery/1.7.1
  copying ckanext/reclineview/theme/public/vendor/jquery/1.7.1/jquery.min.js -> build/lib/ckanext/reclineview/theme/public/vendor/jquery/1.7.1
  creating build/lib/ckanext/reclineview/theme/public/vendor/json
  copying ckanext/reclineview/theme/public/vendor/json/json2.js -> build/lib/ckanext/reclineview/theme/public/vendor/json
  copying ckanext/reclineview/theme/public/vendor/json/json2.min.js -> build/lib/ckanext/reclineview/theme/public/vendor/json
  creating build/lib/ckanext/reclineview/theme/public/vendor/leaflet.markercluster
  copying ckanext/reclineview/theme/public/vendor/leaflet.markercluster/MarkerCluster.Default.css -> build/lib/ckanext/reclineview/theme/public/vendor/leaflet.markercluster
  copying ckanext/reclineview/theme/public/vendor/leaflet.markercluster/MarkerCluster.css -> build/lib/ckanext/reclineview/theme/public/vendor/leaflet.markercluster
  copying ckanext/reclineview/theme/public/vendor/leaflet.markercluster/leaflet.markercluster-src.js -> build/lib/ckanext/reclineview/theme/public/vendor/leaflet.markercluster
  copying ckanext/reclineview/theme/public/vendor/leaflet.markercluster/leaflet.markercluster.js -> build/lib/ckanext/reclineview/theme/public/vendor/leaflet.markercluster
  creating build/lib/ckanext/reclineview/theme/public/vendor/leaflet
  creating build/lib/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/leaflet-src.js -> build/lib/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/leaflet.css -> build/lib/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/leaflet.js -> build/lib/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7
  creating build/lib/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/layers-2x.png -> build/lib/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/layers.png -> build/lib/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/marker-icon-2x.png -> build/lib/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/marker-icon.png -> build/lib/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/marker-shadow.png -> build/lib/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images
  creating build/lib/ckanext/reclineview/theme/public/vendor/moment
  creating build/lib/ckanext/reclineview/theme/public/vendor/moment/2.0.0
  copying ckanext/reclineview/theme/public/vendor/moment/2.0.0/moment.js -> build/lib/ckanext/reclineview/theme/public/vendor/moment/2.0.0
  creating build/lib/ckanext/reclineview/theme/public/vendor/mustache
  creating build/lib/ckanext/reclineview/theme/public/vendor/mustache/0.5.0-dev
  copying ckanext/reclineview/theme/public/vendor/mustache/0.5.0-dev/mustache.js -> build/lib/ckanext/reclineview/theme/public/vendor/mustache/0.5.0-dev
  copying ckanext/reclineview/theme/public/vendor/mustache/0.5.0-dev/mustache.min.js -> build/lib/ckanext/reclineview/theme/public/vendor/mustache/0.5.0-dev
  creating build/lib/ckanext/reclineview/theme/public/vendor/recline
  copying ckanext/reclineview/theme/public/vendor/recline/flot.css -> build/lib/ckanext/reclineview/theme/public/vendor/recline
  copying ckanext/reclineview/theme/public/vendor/recline/map.css -> build/lib/ckanext/reclineview/theme/public/vendor/recline
  copying ckanext/reclineview/theme/public/vendor/recline/recline.css -> build/lib/ckanext/reclineview/theme/public/vendor/recline
  copying ckanext/reclineview/theme/public/vendor/recline/recline.dataset.js -> build/lib/ckanext/reclineview/theme/public/vendor/recline
  copying ckanext/reclineview/theme/public/vendor/recline/recline.js -> build/lib/ckanext/reclineview/theme/public/vendor/recline
  copying ckanext/reclineview/theme/public/vendor/recline/slickgrid.css -> build/lib/ckanext/reclineview/theme/public/vendor/recline
  creating build/lib/ckanext/reclineview/theme/public/vendor/showdown
  creating build/lib/ckanext/reclineview/theme/public/vendor/showdown/20120615
  copying ckanext/reclineview/theme/public/vendor/showdown/20120615/showdown.js -> build/lib/ckanext/reclineview/theme/public/vendor/showdown/20120615
  copying ckanext/reclineview/theme/public/vendor/showdown/20120615/showdown.min.js -> build/lib/ckanext/reclineview/theme/public/vendor/showdown/20120615
  creating build/lib/ckanext/reclineview/theme/public/vendor/slickgrid
  creating build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/MIT-LICENSE.txt -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/README.md -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/jquery-1.7.min.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/jquery-ui-1.8.16.custom.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/jquery.event.drag-2.2.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/jquery.event.drop-2.2.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick-default-theme.css -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.core.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.dataview.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.editors.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.formatters.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.grid.css -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.grid.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.groupitemmetadataprovider.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.remotemodel.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  creating build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls/slick.columnpicker.css -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls/slick.columnpicker.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls/slick.pager.css -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls/slick.pager.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls
  creating build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css
  creating build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/jquery-ui-1.8.16.custom.css -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness
  creating build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_flat_0_aaaaaa_40x100.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_flat_75_ffffff_40x100.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_55_fbf9ee_1x400.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_65_ffffff_1x400.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_75_dadada_1x400.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_75_e6e6e6_1x400.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_95_fef1ec_1x400.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_highlight-soft_75_cccccc_1x100.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_222222_256x240.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_2e83ff_256x240.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_454545_256x240.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_888888_256x240.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_cd0a0a_256x240.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  creating build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/actions.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/ajax-loader-small.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/arrow_redo.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/arrow_right_peppermint.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/arrow_right_spearmint.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/arrow_undo.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/bullet_blue.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/bullet_star.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/bullet_toggle_minus.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/bullet_toggle_plus.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/calendar.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/collapse.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/comment_yellow.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/down.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/drag-handle.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/editor-helper-bg.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/expand.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/header-bg.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/header-columns-bg.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/header-columns-over-bg.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/help.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/info.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/listview.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/pencil.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/row-over-bg.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/sort-asc.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/sort-asc.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/sort-desc.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/sort-desc.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/stripes.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/tag_red.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/tick.png -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/user_identity.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/user_identity_plus.gif -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  creating build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.autotooltips.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.cellcopymanager.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.cellrangedecorator.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.cellrangeselector.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.cellselectionmodel.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.checkboxselectcolumn.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.headerbuttons.css -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.headerbuttons.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.headermenu.css -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.headermenu.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.rowmovemanager.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.rowselectionmodel.js -> build/lib/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  creating build/lib/ckanext/reclineview/theme/public/vendor/timeline
  copying ckanext/reclineview/theme/public/vendor/timeline/LICENSE -> build/lib/ckanext/reclineview/theme/public/vendor/timeline
  copying ckanext/reclineview/theme/public/vendor/timeline/README -> build/lib/ckanext/reclineview/theme/public/vendor/timeline
  creating build/lib/ckanext/reclineview/theme/public/vendor/timeline/css
  copying ckanext/reclineview/theme/public/vendor/timeline/css/loading.gif -> build/lib/ckanext/reclineview/theme/public/vendor/timeline/css
  copying ckanext/reclineview/theme/public/vendor/timeline/css/timeline.css -> build/lib/ckanext/reclineview/theme/public/vendor/timeline/css
  copying ckanext/reclineview/theme/public/vendor/timeline/css/timeline.png -> build/lib/ckanext/reclineview/theme/public/vendor/timeline/css
  copying ckanext/reclineview/theme/public/vendor/timeline/css/timeline@2x.png -> build/lib/ckanext/reclineview/theme/public/vendor/timeline/css
  creating build/lib/ckanext/reclineview/theme/public/vendor/timeline/js
  copying ckanext/reclineview/theme/public/vendor/timeline/js/timeline.js -> build/lib/ckanext/reclineview/theme/public/vendor/timeline/js
  creating build/lib/ckanext/reclineview/theme/public/vendor/underscore.deferred
  creating build/lib/ckanext/reclineview/theme/public/vendor/underscore.deferred/0.4.0
  copying ckanext/reclineview/theme/public/vendor/underscore.deferred/0.4.0/underscore.deferred.js -> build/lib/ckanext/reclineview/theme/public/vendor/underscore.deferred/0.4.0
  copying ckanext/reclineview/theme/public/vendor/underscore.deferred/0.4.0/underscore.deferred.min.js -> build/lib/ckanext/reclineview/theme/public/vendor/underscore.deferred/0.4.0
  creating build/lib/ckanext/reclineview/theme/public/vendor/underscore
  creating build/lib/ckanext/reclineview/theme/public/vendor/underscore/1.4.4
  copying ckanext/reclineview/theme/public/vendor/underscore/1.4.4/underscore.js -> build/lib/ckanext/reclineview/theme/public/vendor/underscore/1.4.4
  creating build/lib/ckanext/reclineview/theme/templates
  copying ckanext/reclineview/theme/templates/recline_graph_form.html -> build/lib/ckanext/reclineview/theme/templates
  copying ckanext/reclineview/theme/templates/recline_map_form.html -> build/lib/ckanext/reclineview/theme/templates
  copying ckanext/reclineview/theme/templates/recline_view.html -> build/lib/ckanext/reclineview/theme/templates
  creating build/lib/ckanext/resourceproxy
  copying ckanext/resourceproxy/__init__.py -> build/lib/ckanext/resourceproxy
  copying ckanext/resourceproxy/blueprint.py -> build/lib/ckanext/resourceproxy
  copying ckanext/resourceproxy/config_declaration.yaml -> build/lib/ckanext/resourceproxy
  copying ckanext/resourceproxy/plugin.py -> build/lib/ckanext/resourceproxy
  creating build/lib/ckanext/resourceproxy/tests
  copying ckanext/resourceproxy/tests/__init__.py -> build/lib/ckanext/resourceproxy/tests
  copying ckanext/resourceproxy/tests/test_proxy.py -> build/lib/ckanext/resourceproxy/tests
  creating build/lib/ckanext/stats
  copying ckanext/stats/__init__.py -> build/lib/ckanext/stats
  copying ckanext/stats/blueprint.py -> build/lib/ckanext/stats
  copying ckanext/stats/plugin.py -> build/lib/ckanext/stats
  copying ckanext/stats/stats.py -> build/lib/ckanext/stats
  creating build/lib/ckanext/stats/public
  copying ckanext/stats/public/.gitignore -> build/lib/ckanext/stats/public
  copying ckanext/stats/public/__init__.py -> build/lib/ckanext/stats/public
  creating build/lib/ckanext/stats/public/ckanext
  copying ckanext/stats/public/ckanext/__init__.py -> build/lib/ckanext/stats/public/ckanext
  creating build/lib/ckanext/stats/public/ckanext/stats
  copying ckanext/stats/public/ckanext/stats/__init__.py -> build/lib/ckanext/stats/public/ckanext/stats
  copying ckanext/stats/public/ckanext/stats/resource.config -> build/lib/ckanext/stats/public/ckanext/stats
  copying ckanext/stats/public/ckanext/stats/webassets.yml -> build/lib/ckanext/stats/public/ckanext/stats
  creating build/lib/ckanext/stats/public/ckanext/stats/css
  copying ckanext/stats/public/ckanext/stats/css/stats.css -> build/lib/ckanext/stats/public/ckanext/stats/css
  creating build/lib/ckanext/stats/public/ckanext/stats/javascript
  creating build/lib/ckanext/stats/public/ckanext/stats/javascript/modules
  copying ckanext/stats/public/ckanext/stats/javascript/modules/plot.js -> build/lib/ckanext/stats/public/ckanext/stats/javascript/modules
  copying ckanext/stats/public/ckanext/stats/javascript/modules/stats-nav.js -> build/lib/ckanext/stats/public/ckanext/stats/javascript/modules
  creating build/lib/ckanext/stats/public/ckanext/stats/test
  copying ckanext/stats/public/ckanext/stats/test/index.html -> build/lib/ckanext/stats/public/ckanext/stats/test
  creating build/lib/ckanext/stats/public/ckanext/stats/test/fixtures
  copying ckanext/stats/public/ckanext/stats/test/fixtures/table.html -> build/lib/ckanext/stats/public/ckanext/stats/test/fixtures
  creating build/lib/ckanext/stats/public/ckanext/stats/test/spec
  creating build/lib/ckanext/stats/public/ckanext/stats/test/spec/modules
  copying ckanext/stats/public/ckanext/stats/test/spec/modules/plot.spec.js -> build/lib/ckanext/stats/public/ckanext/stats/test/spec/modules
  copying ckanext/stats/public/ckanext/stats/test/spec/modules/stats-nav.spec.js -> build/lib/ckanext/stats/public/ckanext/stats/test/spec/modules
  creating build/lib/ckanext/stats/public/ckanext/stats/vendor
  copying ckanext/stats/public/ckanext/stats/vendor/excanvas.js -> build/lib/ckanext/stats/public/ckanext/stats/vendor
  copying ckanext/stats/public/ckanext/stats/vendor/jquery.flot.js -> build/lib/ckanext/stats/public/ckanext/stats/vendor
  creating build/lib/ckanext/stats/templates
  creating build/lib/ckanext/stats/templates/ckanext
  creating build/lib/ckanext/stats/templates/ckanext/stats
  copying ckanext/stats/templates/ckanext/stats/index.html -> build/lib/ckanext/stats/templates/ckanext/stats
  creating build/lib/ckanext/stats/tests
  copying ckanext/stats/tests/__init__.py -> build/lib/ckanext/stats/tests
  copying ckanext/stats/tests/test_stats_lib.py -> build/lib/ckanext/stats/tests
  copying ckanext/stats/tests/test_stats_plugin.py -> build/lib/ckanext/stats/tests
  creating build/lib/ckanext/textview
  copying ckanext/textview/__init__.py -> build/lib/ckanext/textview
  copying ckanext/textview/config_declaration.yaml -> build/lib/ckanext/textview
  copying ckanext/textview/plugin.py -> build/lib/ckanext/textview
  creating build/lib/ckanext/textview/tests
  copying ckanext/textview/tests/__init__.py -> build/lib/ckanext/textview/tests
  copying ckanext/textview/tests/test_view.py -> build/lib/ckanext/textview/tests
  creating build/lib/ckanext/textview/theme
  creating build/lib/ckanext/textview/theme/public
  copying ckanext/textview/theme/public/LICENSE -> build/lib/ckanext/textview/theme/public
  copying ckanext/textview/theme/public/resource.config -> build/lib/ckanext/textview/theme/public
  copying ckanext/textview/theme/public/text_view.js -> build/lib/ckanext/textview/theme/public
  copying ckanext/textview/theme/public/webassets.yml -> build/lib/ckanext/textview/theme/public
  creating build/lib/ckanext/textview/theme/public/css
  copying ckanext/textview/theme/public/css/text.css -> build/lib/ckanext/textview/theme/public/css
  creating build/lib/ckanext/textview/theme/public/styles
  copying ckanext/textview/theme/public/styles/a11y-light.css -> build/lib/ckanext/textview/theme/public/styles
  creating build/lib/ckanext/textview/theme/public/vendor
  copying ckanext/textview/theme/public/vendor/highlight.js -> build/lib/ckanext/textview/theme/public/vendor
  creating build/lib/ckanext/textview/theme/templates
  copying ckanext/textview/theme/templates/text_form.html -> build/lib/ckanext/textview/theme/templates
  copying ckanext/textview/theme/templates/text_view.html -> build/lib/ckanext/textview/theme/templates
  creating build/lib/ckanext/videoview
  copying ckanext/videoview/__init__.py -> build/lib/ckanext/videoview
  copying ckanext/videoview/plugin.py -> build/lib/ckanext/videoview
  creating build/lib/ckanext/videoview/tests
  copying ckanext/videoview/tests/__init__.py -> build/lib/ckanext/videoview/tests
  copying ckanext/videoview/tests/test_view.py -> build/lib/ckanext/videoview/tests
  creating build/lib/ckanext/videoview/theme
  creating build/lib/ckanext/videoview/theme/templates
  copying ckanext/videoview/theme/templates/video_form.html -> build/lib/ckanext/videoview/theme/templates
  copying ckanext/videoview/theme/templates/video_view.html -> build/lib/ckanext/videoview/theme/templates
  creating build/lib/ckanext/webpageview
  copying ckanext/webpageview/__init__.py -> build/lib/ckanext/webpageview
  copying ckanext/webpageview/plugin.py -> build/lib/ckanext/webpageview
  creating build/lib/ckanext/webpageview/tests
  copying ckanext/webpageview/tests/__init__.py -> build/lib/ckanext/webpageview/tests
  copying ckanext/webpageview/tests/test_view.py -> build/lib/ckanext/webpageview/tests
  creating build/lib/ckanext/webpageview/theme
  creating build/lib/ckanext/webpageview/theme/templates
  copying ckanext/webpageview/theme/templates/webpage_form.html -> build/lib/ckanext/webpageview/theme/templates
  copying ckanext/webpageview/theme/templates/webpage_view.html -> build/lib/ckanext/webpageview/theme/templates
  installing to build/bdist.linux-x86_64/wheel
  running install
  running install_lib
  copying ckan/__init__.py -> build/bdist.linux-x86_64/wheel/ckan
  copying ckan/authz.py -> build/bdist.linux-x86_64/wheel/ckan
  copying ckan/common.py -> build/bdist.linux-x86_64/wheel/ckan
  copying ckan/exceptions.py -> build/bdist.linux-x86_64/wheel/ckan
  copying ckan/cli/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/asset.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/clean.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/cli.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/config.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/config_tool.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/dataset.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/db.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/generate.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/jobs.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/notify.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/plugin_info.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/profile.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/sass.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/search_index.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/server.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/shell.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/sysadmin.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/tracking.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/translation.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/user.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/cli/views.py -> build/bdist.linux-x86_64/wheel/ckan/cli
  copying ckan/config/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/config
  copying ckan/config/config_declaration.yaml -> build/bdist.linux-x86_64/wheel/ckan/config
  copying ckan/config/deployment.ini_tmpl -> build/bdist.linux-x86_64/wheel/ckan/config
  copying ckan/config/environment.py -> build/bdist.linux-x86_64/wheel/ckan/config
  copying ckan/config/resource_formats.json -> build/bdist.linux-x86_64/wheel/ckan/config
  copying ckan/config/who.ini -> build/bdist.linux-x86_64/wheel/ckan/config
  copying ckan/config/declaration/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/config/declaration
  copying ckan/config/declaration/describe.py -> build/bdist.linux-x86_64/wheel/ckan/config/declaration
  copying ckan/config/declaration/key.py -> build/bdist.linux-x86_64/wheel/ckan/config/declaration
  copying ckan/config/declaration/load.py -> build/bdist.linux-x86_64/wheel/ckan/config/declaration
  copying ckan/config/declaration/option.py -> build/bdist.linux-x86_64/wheel/ckan/config/declaration
  copying ckan/config/declaration/serialize.py -> build/bdist.linux-x86_64/wheel/ckan/config/declaration
  copying ckan/config/declaration/utils.py -> build/bdist.linux-x86_64/wheel/ckan/config/declaration
  copying ckan/config/middleware/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/config/middleware
  copying ckan/config/middleware/common_middleware.py -> build/bdist.linux-x86_64/wheel/ckan/config/middleware
  copying ckan/config/middleware/flask_app.py -> build/bdist.linux-x86_64/wheel/ckan/config/middleware
  copying ckan/config/solr/schema.xml -> build/bdist.linux-x86_64/wheel/ckan/config/solr
  copying ckan/i18n/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/i18n
  copying ckan/i18n/ckan.pot -> build/bdist.linux-x86_64/wheel/ckan/i18n
  copying ckan/i18n/am/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/am/LC_MESSAGES
  copying ckan/i18n/am/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/am/LC_MESSAGES
  copying ckan/i18n/ar/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/ar/LC_MESSAGES
  copying ckan/i18n/ar/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/ar/LC_MESSAGES
  copying ckan/i18n/bg/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/bg/LC_MESSAGES
  copying ckan/i18n/bg/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/bg/LC_MESSAGES
  copying ckan/i18n/bs/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/bs/LC_MESSAGES
  copying ckan/i18n/bs/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/bs/LC_MESSAGES
  copying ckan/i18n/ca/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/ca/LC_MESSAGES
  copying ckan/i18n/ca/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/ca/LC_MESSAGES
  copying ckan/i18n/cs_CZ/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/cs_CZ/LC_MESSAGES
  copying ckan/i18n/cs_CZ/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/cs_CZ/LC_MESSAGES
  copying ckan/i18n/da_DK/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/da_DK/LC_MESSAGES
  copying ckan/i18n/da_DK/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/da_DK/LC_MESSAGES
  copying ckan/i18n/de/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/de/LC_MESSAGES
  copying ckan/i18n/de/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/de/LC_MESSAGES
  copying ckan/i18n/el/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/el/LC_MESSAGES
  copying ckan/i18n/el/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/el/LC_MESSAGES
  copying ckan/i18n/en_AU/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/en_AU/LC_MESSAGES
  copying ckan/i18n/en_AU/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/en_AU/LC_MESSAGES
  copying ckan/i18n/en_GB/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/en_GB/LC_MESSAGES
  copying ckan/i18n/en_GB/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/en_GB/LC_MESSAGES
  copying ckan/i18n/es/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/es/LC_MESSAGES
  copying ckan/i18n/es/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/es/LC_MESSAGES
  copying ckan/i18n/es_AR/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/es_AR/LC_MESSAGES
  copying ckan/i18n/es_AR/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/es_AR/LC_MESSAGES
  copying ckan/i18n/eu/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/eu/LC_MESSAGES
  copying ckan/i18n/eu/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/eu/LC_MESSAGES
  copying ckan/i18n/fa_IR/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/fa_IR/LC_MESSAGES
  copying ckan/i18n/fa_IR/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/fa_IR/LC_MESSAGES
  copying ckan/i18n/fi/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/fi/LC_MESSAGES
  copying ckan/i18n/fi/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/fi/LC_MESSAGES
  copying ckan/i18n/fr/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/fr/LC_MESSAGES
  copying ckan/i18n/fr/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/fr/LC_MESSAGES
  copying ckan/i18n/gl/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/gl/LC_MESSAGES
  copying ckan/i18n/gl/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/gl/LC_MESSAGES
  copying ckan/i18n/he/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/he/LC_MESSAGES
  copying ckan/i18n/he/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/he/LC_MESSAGES
  copying ckan/i18n/hr/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/hr/LC_MESSAGES
  copying ckan/i18n/hr/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/hr/LC_MESSAGES
  copying ckan/i18n/hu/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/hu/LC_MESSAGES
  copying ckan/i18n/hu/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/hu/LC_MESSAGES
  copying ckan/i18n/id/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/id/LC_MESSAGES
  copying ckan/i18n/id/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/id/LC_MESSAGES
  copying ckan/i18n/is/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/is/LC_MESSAGES
  copying ckan/i18n/is/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/is/LC_MESSAGES
  copying ckan/i18n/it/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/it/LC_MESSAGES
  copying ckan/i18n/it/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/it/LC_MESSAGES
  copying ckan/i18n/ja/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/ja/LC_MESSAGES
  copying ckan/i18n/ja/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/ja/LC_MESSAGES
  copying ckan/i18n/km/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/km/LC_MESSAGES
  copying ckan/i18n/km/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/km/LC_MESSAGES
  copying ckan/i18n/ko_KR/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/ko_KR/LC_MESSAGES
  copying ckan/i18n/ko_KR/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/ko_KR/LC_MESSAGES
  copying ckan/i18n/lt/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/lt/LC_MESSAGES
  copying ckan/i18n/lt/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/lt/LC_MESSAGES
  copying ckan/i18n/lv/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/lv/LC_MESSAGES
  copying ckan/i18n/lv/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/lv/LC_MESSAGES
  copying ckan/i18n/mk/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/mk/LC_MESSAGES
  copying ckan/i18n/mk/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/mk/LC_MESSAGES
  copying ckan/i18n/mn_MN/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/mn_MN/LC_MESSAGES
  copying ckan/i18n/mn_MN/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/mn_MN/LC_MESSAGES
  copying ckan/i18n/my_MM/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/my_MM/LC_MESSAGES
  copying ckan/i18n/my_MM/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/my_MM/LC_MESSAGES
  copying ckan/i18n/nb_NO/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/nb_NO/LC_MESSAGES
  copying ckan/i18n/nb_NO/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/nb_NO/LC_MESSAGES
  copying ckan/i18n/ne/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/ne/LC_MESSAGES
  copying ckan/i18n/ne/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/ne/LC_MESSAGES
  copying ckan/i18n/nl/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/nl/LC_MESSAGES
  copying ckan/i18n/nl/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/nl/LC_MESSAGES
  copying ckan/i18n/no/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/no/LC_MESSAGES
  copying ckan/i18n/no/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/no/LC_MESSAGES
  copying ckan/i18n/pl/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/pl/LC_MESSAGES
  copying ckan/i18n/pl/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/pl/LC_MESSAGES
  copying ckan/i18n/pt_BR/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/pt_BR/LC_MESSAGES
  copying ckan/i18n/pt_BR/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/pt_BR/LC_MESSAGES
  copying ckan/i18n/pt_PT/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/pt_PT/LC_MESSAGES
  copying ckan/i18n/pt_PT/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/pt_PT/LC_MESSAGES
  copying ckan/i18n/ro/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/ro/LC_MESSAGES
  copying ckan/i18n/ro/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/ro/LC_MESSAGES
  copying ckan/i18n/ru/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/ru/LC_MESSAGES
  copying ckan/i18n/ru/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/ru/LC_MESSAGES
  copying ckan/i18n/sk/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/sk/LC_MESSAGES
  copying ckan/i18n/sk/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/sk/LC_MESSAGES
  copying ckan/i18n/sl/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/sl/LC_MESSAGES
  copying ckan/i18n/sl/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/sl/LC_MESSAGES
  copying ckan/i18n/sq/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/sq/LC_MESSAGES
  copying ckan/i18n/sq/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/sq/LC_MESSAGES
  copying ckan/i18n/sr/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/sr/LC_MESSAGES
  copying ckan/i18n/sr/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/sr/LC_MESSAGES
  copying ckan/i18n/sr_Latn/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/sr_Latn/LC_MESSAGES
  copying ckan/i18n/sr_Latn/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/sr_Latn/LC_MESSAGES
  copying ckan/i18n/sv/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/sv/LC_MESSAGES
  copying ckan/i18n/sv/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/sv/LC_MESSAGES
  copying ckan/i18n/th/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/th/LC_MESSAGES
  copying ckan/i18n/th/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/th/LC_MESSAGES
  copying ckan/i18n/tl/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/tl/LC_MESSAGES
  copying ckan/i18n/tl/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/tl/LC_MESSAGES
  copying ckan/i18n/tr/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/tr/LC_MESSAGES
  copying ckan/i18n/tr/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/tr/LC_MESSAGES
  copying ckan/i18n/uk/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/uk/LC_MESSAGES
  copying ckan/i18n/uk/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/uk/LC_MESSAGES
  copying ckan/i18n/uk_UA/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/uk_UA/LC_MESSAGES
  copying ckan/i18n/uk_UA/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/uk_UA/LC_MESSAGES
  copying ckan/i18n/vi/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/vi/LC_MESSAGES
  copying ckan/i18n/vi/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/vi/LC_MESSAGES
  copying ckan/i18n/zh_Hans_CN/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/zh_Hans_CN/LC_MESSAGES
  copying ckan/i18n/zh_Hans_CN/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/zh_Hans_CN/LC_MESSAGES
  copying ckan/i18n/zh_Hant_TW/LC_MESSAGES/ckan.mo -> build/bdist.linux-x86_64/wheel/ckan/i18n/zh_Hant_TW/LC_MESSAGES
  copying ckan/i18n/zh_Hant_TW/LC_MESSAGES/ckan.po -> build/bdist.linux-x86_64/wheel/ckan/i18n/zh_Hant_TW/LC_MESSAGES
  copying ckan/lib/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/api_token.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/app_globals.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/authenticator.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/base.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/captcha.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/cli.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/config_tool.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/create_test_data.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/datapreview.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/extract.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/formatters.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/hash.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/helpers.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/i18n.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/io.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/jinja_extensions.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/jobs.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/lazyjson.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/mailer.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/maintain.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/munge.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/pagination.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/plugins.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/redis.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/signals.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/uploader.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/webassets_tools.py -> build/bdist.linux-x86_64/wheel/ckan/lib
  copying ckan/lib/dictization/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/lib/dictization
  copying ckan/lib/dictization/model_dictize.py -> build/bdist.linux-x86_64/wheel/ckan/lib/dictization
  copying ckan/lib/dictization/model_save.py -> build/bdist.linux-x86_64/wheel/ckan/lib/dictization
  copying ckan/lib/navl/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/lib/navl
  copying ckan/lib/navl/dictization_functions.py -> build/bdist.linux-x86_64/wheel/ckan/lib/navl
  copying ckan/lib/navl/validators.py -> build/bdist.linux-x86_64/wheel/ckan/lib/navl
  copying ckan/lib/search/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/lib/search
  copying ckan/lib/search/common.py -> build/bdist.linux-x86_64/wheel/ckan/lib/search
  copying ckan/lib/search/index.py -> build/bdist.linux-x86_64/wheel/ckan/lib/search
  copying ckan/lib/search/query.py -> build/bdist.linux-x86_64/wheel/ckan/lib/search
  copying ckan/logic/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/logic
  copying ckan/logic/converters.py -> build/bdist.linux-x86_64/wheel/ckan/logic
  copying ckan/logic/schema.py -> build/bdist.linux-x86_64/wheel/ckan/logic
  copying ckan/logic/validators.py -> build/bdist.linux-x86_64/wheel/ckan/logic
  copying ckan/logic/action/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/logic/action
  copying ckan/logic/action/create.py -> build/bdist.linux-x86_64/wheel/ckan/logic/action
  copying ckan/logic/action/delete.py -> build/bdist.linux-x86_64/wheel/ckan/logic/action
  copying ckan/logic/action/get.py -> build/bdist.linux-x86_64/wheel/ckan/logic/action
  copying ckan/logic/action/patch.py -> build/bdist.linux-x86_64/wheel/ckan/logic/action
  copying ckan/logic/action/update.py -> build/bdist.linux-x86_64/wheel/ckan/logic/action
  copying ckan/logic/auth/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/logic/auth
  copying ckan/logic/auth/create.py -> build/bdist.linux-x86_64/wheel/ckan/logic/auth
  copying ckan/logic/auth/delete.py -> build/bdist.linux-x86_64/wheel/ckan/logic/auth
  copying ckan/logic/auth/get.py -> build/bdist.linux-x86_64/wheel/ckan/logic/auth
  copying ckan/logic/auth/patch.py -> build/bdist.linux-x86_64/wheel/ckan/logic/auth
  copying ckan/logic/auth/update.py -> build/bdist.linux-x86_64/wheel/ckan/logic/auth
  copying ckan/migration/README -> build/bdist.linux-x86_64/wheel/ckan/migration
  copying ckan/migration/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/migration
  copying ckan/migration/alembic.ini -> build/bdist.linux-x86_64/wheel/ckan/migration
  copying ckan/migration/env.py -> build/bdist.linux-x86_64/wheel/ckan/migration
  copying ckan/migration/migrate_package_activity.py -> build/bdist.linux-x86_64/wheel/ckan/migration
  copying ckan/migration/revision_legacy_code.py -> build/bdist.linux-x86_64/wheel/ckan/migration
  copying ckan/migration/versions/001_103676e0a497_create_existing_tables.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/002_86fdd8c54775_add_author_and_maintainer.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/003_f22b4f5241a5_add_user_object.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/004_f92ee205e46d_add_group_object.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/005_12c2232c15f5_add_authorization_tables.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/006_c83955e7acb6_add_ratings.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/007_1928d4af1cda_add_system_roles.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/008_e8283ffb257e_update_vdm_ids.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/009_b739a48de5c4_add_creation_timestamps.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/010_a6f13bf14d0c_add_user_about.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/011_866f6370b4ac_add_package_search_vector.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/012_e5ca33a5d445_add_resources.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/013_8a3a5af39797_add_hash.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/014_93519b684820_hash_2.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/015_6d8ffebcaf54_remove_state_object.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/016_37ada738328e_uuids_everywhere.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/017_1250b2ff3e36_add_pkg_relationships.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/018_05a0778051ca_adjust_licenses.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/019_b2eb6f34a638_pkg_relationships_state.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/020_69a0b0efc609_add_changeset.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/021_765143af2ba3_postgresql_upgrade_sql.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/022_7b324ca6c0dc_add_group_extras.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/023_87fdd05f0744_add_harvesting.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/024_12981fe12484_add_harvested_document.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/025_b581622ad327_add_authorization_groups.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/026_3615b25af443_authorization_group_user_pk.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/027_11e5745c6fc9_adjust_harvester.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/028_cdd68fe9ba21_drop_harvest_source_status.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/029_1bfdf4240915_version_groups.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/030_b16cbf164c8a_additional_user_attributes.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/031_1b05245167d6_move_openid_to_new_field.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/032_d89e0731422d_add_extra_info_field_to_resources.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/033_6da92ef2df15_auth_group_user_id_add_conditional.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/034_6c600693af5b_resource_group_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/035_81148ccebd6c_harvesting_doc_versioning.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/036_ecaa8b38782f_lockdown_roles.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/037_edcf3b8c3c1b_role_anon_editor.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/038_fd6622e3d964_delete_migration_tables.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/039_cca459c76d45_add_expired_id_and_dates.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/040_500a08f4818e_reset_key_on_user.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/041_6817d4e3bdc3_resource_new_fields.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/042_da65e2877034_user_revision_indexes.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/043_bd38cd6502b2_drop_postgres_search.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/044_4190eeeb8d73_add_task_status.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/045_54e3f155d945_user_name_unique.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/046_b69e9b80396f_drop_changesets.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/047_883a7c406926_rename_package_group_member.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/048_4a7011172b3f_add_activity_streams_tables.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/049_e0c06c2177b5_add_group_approval_status.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/050_01a6b058cb7f_term_translation_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/051_a4fb0d85ced6_add_tag_vocabulary.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/052_ba693d64c6d7_update_member_capacities.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/053_9d051a099097_add_group_logo.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/054_da21b38da4db_add_resource_created_date.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/055_048f7db947bf_update_user_and_activity_detail.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/056_11af3215ae89_add_related_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/057_660a5aae527e_tracking.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/058_bd36d1826a5d_add_follower_tables.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/059_9291bb46f352_add_related_count_and_flag.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/060_31ad11c518fc_add_system_info_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/061_338d460bc460_add_follower_group_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/062_6deb2bbab394_add_dashboard_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/063_8b633852cb7a_org_changes.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/064_4f8becd4919a_add_email_last_sent_column.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/065_1fab0bc6439e_add_email_notifications_preference.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/066_ad16b3bd8cb6_default_package_type.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/067_266c110eafec_turn_extras_to_strings.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/068_e33a5f2b2a84_add_package_extras_index.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/069_e7524c675cdb_resource_url_and_metadata_modified.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/070_cfb544112fa7_add_activity_and_resource_indexes.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/071_c16f081ef73a_add_state_column_to_user_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/072_08dcb9233ad7_add_resource_view.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/073_011f51208be3_update_resource_view_resource_id_.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/074_a4ca55f0f45e_remove_resource_groups.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/075_9cdc88c8896a_rename_view_plugins.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/076_59995aa965c0_rename_view_plugins_2.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/077_51171a04d86d_add_revisions_to_system_info.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/078_ae821876532a_remove_old_authz_model.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/079_e0177a15d2c9_resource_revision_index.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/080_8224d872c64f_continuity_id_indexes.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/081_a64cf4a79182_set_datastore_active.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/082_8ea886d0ede4_create_index_creator_user_id.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/083_f98d8fa2a7f7_remove_related_items.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/084_d85ce5783688_add_metadata_created.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/085_f9bf3d5c4b4d_adjust_activity_timestamps.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/086_19663581b3bb_drop_openid_column.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/087_ff1b303cab77_remove_old_authorization_tables.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/088_3537d5420e0e_delete_extrase_which_are_deleted_state.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/089_23c92480926e_package_activity_migration_check.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/090_980dcd44de4b_delete_migrate_version_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/091_0ffc0b277141_group_extra_group_id_index.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/092_01afcadbd8c0_resource_package_id_index.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/093_7f70d7d15445_remove_activity_revision_id.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/094_588d7cfb9a41_add_metadata_modified_to_resource_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/095_9fadda785b07_drop_continuity_id_constraints.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/096_19ddad52b500_add_plugin_extras_to_user_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/097_f789f233226e_add_package_member_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/098_ddbd0a9a4489_add_image_url_field_to_user_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/099_3ae4b17ed66d_create_apitoken_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/100_ccd38ad5fced_remove_package_tag_revision_foreign_key.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/101_d111f446733b_add_last_active_column_in_user_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/102_ff13667243ed_create_conditinal_index_on_user.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/103_353aaf2701f0_add_plugin_data_to_package_table.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/104_9f33a0280c51_resource_view_resource_id_index.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/migration/versions/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/migration/versions
  copying ckan/model/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/api_token.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/base.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/core.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/dashboard.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/domain_object.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/follower.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/group.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/group_extra.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/license.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/meta.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/misc.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/modification.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/package.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/package_extra.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/package_relationship.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/resource.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/resource_view.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/system.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/system_info.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/tag.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/task_status.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/term_translation.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/tracking.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/types.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/user.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/model/vocabulary.py -> build/bdist.linux-x86_64/wheel/ckan/model
  copying ckan/plugins/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/plugins
  copying ckan/plugins/blanket.py -> build/bdist.linux-x86_64/wheel/ckan/plugins
  copying ckan/plugins/core.py -> build/bdist.linux-x86_64/wheel/ckan/plugins
  copying ckan/plugins/interfaces.py -> build/bdist.linux-x86_64/wheel/ckan/plugins
  copying ckan/plugins/toolkit.py -> build/bdist.linux-x86_64/wheel/ckan/plugins
  copying ckan/plugins/toolkit_sphinx_extension.py -> build/bdist.linux-x86_64/wheel/ckan/plugins
  copying ckan/public-bs3/robots.txt -> build/bdist.linux-x86_64/wheel/ckan/public-bs3
  copying ckan/public-bs3/base/.gitignore -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base
  copying ckan/public-bs3/base/css/.gitignore -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/css
  copying ckan/public-bs3/base/css/main-rtl.css -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/css
  copying ckan/public-bs3/base/css/main.css -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/css
  copying ckan/public-bs3/base/css/webassets.yml -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/css
  copying ckan/public-bs3/base/i18n/.gitignore -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/i18n
  copying ckan/public-bs3/base/images/background-tag-ie7.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/background-tag.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/background-tile.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/bg.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/breadcrumb-slash-ie7.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/ckan-logo-footer.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/ckan-logo-white.svg -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/ckan-logo.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/ckan-logo.svg -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/ckan.ico -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/dashboard-followee-related.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/dotted.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/editing.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/full-width-nav-right.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/icon-search-27x26.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/nav-active.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/nav.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/od_80x15_blue.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-200x125.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-420x220.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-680x400.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-application.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-group.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-image.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-organization.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/placeholder-user.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/sprite-ckan-icons.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/sprite-resource-icons.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/images/table-seperator.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/images
  copying ckan/public-bs3/base/javascript/apply-html-class.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/client.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/i18n.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/main.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/module.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/notify.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/pubsub.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/resource.config -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/sandbox.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/tracking.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/view-filters.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/webassets.yml -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript
  copying ckan/public-bs3/base/javascript/modules/api-info.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/autocomplete.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/basic-form.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/confirm-action.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/copy-into-buffer.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/custom-fields.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/data-viewer.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/dataset-visibility.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/follow.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/followers-counter.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/image-upload.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/media-grid.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/metadata-button.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-form.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-reorder.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-upload-field.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-view-embed.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-view-filters-form.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-view-filters.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/resource-view-reorder.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/select-switch.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/slug-preview.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/table-selectable-rows.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/modules/table-toggle-more.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/modules
  copying ckan/public-bs3/base/javascript/plugins/jquery.date-helpers.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.form-warning.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.images-loaded.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.inherit.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.masonry.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.proxy-all.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.slug-preview.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.slug.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.truncator.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/javascript/plugins/jquery.url-helpers.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/javascript/plugins
  copying ckan/public-bs3/base/scss/_alerts.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_bootstrap-rtl.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_bootstrap-variables.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_bootstrap.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_ckan-rtl.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_ckan.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_custom.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_dashboard.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_datapusher.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_dataset.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_dropdown.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_footer.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_forms.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_group.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_homepage.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_icons.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_input-groups.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_layout.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_masthead.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_media.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_mixins.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_module.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_nav.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_profile.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_prose.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_resource-view.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_search.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_tables.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_toolbar.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/_variables.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/main-rtl.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/scss/main.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/scss
  copying ckan/public-bs3/base/vendor/bootstrap.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/jed.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/jquery.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/jquery.ui.core.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/jquery.ui.mouse.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/jquery.ui.sortable.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/jquery.ui.widget.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/moment-with-locales.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/qs.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/resource.config -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/webassets.yml -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor
  copying ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.eot -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.svg -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.ttf -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.woff -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.woff2 -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap-sprockets.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/affix.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/alert.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/button.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/carousel.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/collapse.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/dropdown.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/modal.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/popover.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/scrollspy.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/tab.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/tooltip.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/transition.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/_bootstrap-compass.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/_bootstrap-mincer.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/_bootstrap-sprockets.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/_bootstrap.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_alerts.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_badges.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_breadcrumbs.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_button-groups.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_buttons.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_carousel.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_close.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_code.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_component-animations.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_dropdowns.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_forms.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_glyphicons.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_grid.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_input-groups.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_jumbotron.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_labels.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_list-group.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_media.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_mixins.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_modals.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_navbar.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_navs.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_normalize.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_pager.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_pagination.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_panels.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_popovers.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_print.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_progress-bars.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_responsive-embed.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_responsive-utilities.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_scaffolding.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_tables.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_theme.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_thumbnails.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_tooltip.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_type.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_utilities.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_variables.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_wells.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_alerts.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_background-variant.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_border-radius.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_buttons.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_center-block.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_clearfix.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_forms.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_gradients.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_grid-framework.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_grid.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_hide-text.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_image.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_labels.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_list-group.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_nav-divider.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_nav-vertical-align.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_opacity.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_pagination.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_panels.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_progress-bar.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_reset-filter.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_reset-text.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_resize.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_responsive-visibility.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_size.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_tab-focus.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_table-row.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_text-emphasis.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_text-overflow.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_vendor-prefixes.scss -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins
  copying ckan/public-bs3/base/vendor/fontawesome-free/css/all.css -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/fontawesome-free/css
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-brands-400.ttf -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-brands-400.woff2 -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-regular-400.ttf -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-regular-400.woff2 -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-solid-900.ttf -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-solid-900.woff2 -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-v4compatibility.ttf -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-v4compatibility.woff2 -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/fontawesome-free/webfonts
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-audio.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-image.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-process.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-ui.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-validate.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-video.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/jquery-fileupload/jquery.iframe-transport.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/jquery-fileupload
  copying ckan/public-bs3/base/vendor/select2/.gitignore -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/LICENSE -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/README.md -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/bower.json -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/component.json -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/composer.json -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/package.json -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/release.sh -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2-bootstrap.css -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2-spinner.gif -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2.css -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2.jquery.json -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ar.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_az.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_bg.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ca.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_cs.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_da.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_de.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_el.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_en.js.template -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_es.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_et.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_eu.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_fa.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_fi.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_fr.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_gl.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_he.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_hr.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_hu.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_id.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_is.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_it.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ja.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ka.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ko.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_lt.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_lv.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_mk.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ms.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_nb.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_nl.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_pl.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_pt-BR.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_pt-PT.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ro.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_rs.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ru.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_sk.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_sv.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_th.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_tr.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_ug-CN.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_uk.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_vi.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_zh-CN.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2_locale_zh-TW.js -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public-bs3/base/vendor/select2/select2x2.png -> build/bdist.linux-x86_64/wheel/ckan/public-bs3/base/vendor/select2
  copying ckan/public/base/.gitignore -> build/bdist.linux-x86_64/wheel/ckan/public/base
  copying ckan/public/base/css/.gitignore -> build/bdist.linux-x86_64/wheel/ckan/public/base/css
  copying ckan/public/base/css/main-rtl.css -> build/bdist.linux-x86_64/wheel/ckan/public/base/css
  copying ckan/public/base/css/main.css -> build/bdist.linux-x86_64/wheel/ckan/public/base/css
  copying ckan/public/base/css/webassets.yml -> build/bdist.linux-x86_64/wheel/ckan/public/base/css
  copying ckan/public/base/i18n/.gitignore -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/am.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/ar.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/bg.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/bs.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/ca.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/cs_CZ.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/da_DK.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/de.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/el.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/en_AU.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/en_GB.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/es.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/es_AR.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/eu.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/fa_IR.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/fi.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/fr.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/gl.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/he.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/hr.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/hu.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/id.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/is.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/it.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/ja.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/km.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/ko_KR.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/lt.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/lv.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/mk.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/mn_MN.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/my_MM.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/nb_NO.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/ne.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/nl.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/no.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/pl.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/pt_BR.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/pt_PT.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/ro.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/ru.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/sk.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/sl.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/sq.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/sr.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/sr_Latn.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/sv.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/th.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/tl.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/tr.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/uk.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/uk_UA.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/vi.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/zh_Hans_CN.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/i18n/zh_Hant_TW.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/i18n
  copying ckan/public/base/images/background-tag-ie7.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/background-tag.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/background-tile.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/bg.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/breadcrumb-slash-ie7.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/ckan-logo-footer.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/ckan-logo-white.svg -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/ckan-logo.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/ckan-logo.svg -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/ckan.ico -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/dashboard-followee-related.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/editing.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/full-width-nav-right.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/icon-search-27x26.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/nav-active.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/nav.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/od_80x15_blue.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/placeholder-200x125.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/placeholder-420x220.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/placeholder-680x400.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/placeholder-application.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/placeholder-group.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/placeholder-image.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/placeholder-organization.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/placeholder-user.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/sprite-resource-icons.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/images/table-seperator.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/images
  copying ckan/public/base/javascript/apply-html-class.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript
  copying ckan/public/base/javascript/client.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript
  copying ckan/public/base/javascript/i18n.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript
  copying ckan/public/base/javascript/main.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript
  copying ckan/public/base/javascript/module.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript
  copying ckan/public/base/javascript/notify.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript
  copying ckan/public/base/javascript/pubsub.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript
  copying ckan/public/base/javascript/resource.config -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript
  copying ckan/public/base/javascript/sandbox.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript
  copying ckan/public/base/javascript/tracking.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript
  copying ckan/public/base/javascript/view-filters.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript
  copying ckan/public/base/javascript/webassets.yml -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript
  copying ckan/public/base/javascript/modules/api-info.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/autocomplete.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/basic-form.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/confirm-action.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/copy-into-buffer.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/custom-fields.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/data-viewer.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/dataset-visibility.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/follow.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/followers-counter.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/image-upload.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/media-grid.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/metadata-button.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-form.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-reorder.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-upload-field.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-view-embed.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-view-filters-form.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-view-filters.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/resource-view-reorder.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/select-switch.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/slug-preview.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/table-selectable-rows.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/modules/table-toggle-more.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/modules
  copying ckan/public/base/javascript/plugins/jquery.date-helpers.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.form-warning.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.images-loaded.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.inherit.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.masonry.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.proxy-all.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.slug-preview.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.slug.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.truncator.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/plugins
  copying ckan/public/base/javascript/plugins/jquery.url-helpers.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/javascript/plugins
  copying ckan/public/base/scss/_alerts.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_bootstrap-rtl.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_bootstrap-variables.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_bootstrap.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_buttons.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_ckan-rtl.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_ckan.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_custom.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_dashboard.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_datapusher.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_dataset.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_footer.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_forms.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_group.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_homepage.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_input-groups.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_layout.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_masthead.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_media.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_mixins.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_module.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_nav.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_profile.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_prose.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_resource-icons.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_resource-view.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_search.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_tables.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_toolbar.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/_variables.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/main-rtl.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/scss/main.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/scss
  copying ckan/public/base/vendor/bootstrap.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/jed.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/jquery.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/jquery.ui.core.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/jquery.ui.mouse.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/jquery.ui.sortable.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/jquery.ui.widget.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/moment-with-locales.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/popper.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/popperjs.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/purify.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/qs.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/resource.config -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/webassets.yml -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor
  copying ckan/public/base/vendor/bootstrap/css/bootstrap-theme.min.css.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/css
  copying ckan/public/base/vendor/bootstrap/css/bootstrap.min.css.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/css
  copying ckan/public/base/vendor/bootstrap/js/alert.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/alert.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/base-component.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/base-component.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.bundle.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.bundle.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.bundle.min.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.bundle.min.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.esm.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.esm.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.esm.min.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.esm.min.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.min.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/bootstrap.min.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/button.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/button.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/carousel.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/carousel.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/collapse.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/collapse.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/dropdown.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/dropdown.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/modal.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/modal.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/offcanvas.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/offcanvas.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/popover.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/popover.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/scrollspy.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/scrollspy.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/tab.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/tab.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/toast.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/toast.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/tooltip.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/tooltip.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js
  copying ckan/public/base/vendor/bootstrap/js/dom/data.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/data.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/event-handler.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/event-handler.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/manipulator.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/manipulator.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/selector-engine.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/js/dom/selector-engine.js.map -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/js/dom
  copying ckan/public/base/vendor/bootstrap/scss/_accordion.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_alert.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_badge.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_breadcrumb.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_button-group.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_buttons.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_card.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_carousel.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_close.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_containers.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_dropdown.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_forms.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_functions.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_grid.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_helpers.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_images.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_list-group.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_mixins.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_modal.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_nav.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_navbar.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_offcanvas.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_pagination.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_placeholders.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_popover.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_progress.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_reboot.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_root.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_spinners.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_tables.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_toasts.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_tooltip.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_transitions.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_type.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_utilities.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/_variables.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/bootstrap-grid.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/bootstrap-reboot.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/bootstrap-utilities.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/bootstrap.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss
  copying ckan/public/base/vendor/bootstrap/scss/forms/_floating-labels.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_form-check.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_form-control.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_form-range.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_form-select.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_form-text.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_input-group.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_labels.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/forms/_validation.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/forms
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_clearfix.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_colored-links.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_position.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_ratio.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_stacks.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_stretched-link.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_text-truncation.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_visually-hidden.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/helpers/_vr.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/helpers
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_alert.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_backdrop.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_border-radius.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_box-shadow.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_breakpoints.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_buttons.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_caret.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_clearfix.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_color-scheme.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_container.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_deprecate.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_forms.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_gradients.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_grid.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_image.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_list-group.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_lists.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_pagination.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_reset-text.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_resize.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_table-variants.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_text-truncate.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_transition.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_utilities.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/mixins/_visually-hidden.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/mixins
  copying ckan/public/base/vendor/bootstrap/scss/utilities/_api.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/utilities
  copying ckan/public/base/vendor/bootstrap/scss/vendor/_rfs.scss -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/bootstrap/scss/vendor
  copying ckan/public/base/vendor/fontawesome-free/css/all.css -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/fontawesome-free/css
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-brands-400.ttf -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-brands-400.woff2 -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-regular-400.ttf -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-regular-400.woff2 -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-solid-900.ttf -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-solid-900.woff2 -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-v4compatibility.ttf -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/fontawesome-free/webfonts/fa-v4compatibility.woff2 -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/fontawesome-free/webfonts
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-audio.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-image.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-process.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-ui.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-validate.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-video.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.fileupload.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/jquery-fileupload/jquery.iframe-transport.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/jquery-fileupload
  copying ckan/public/base/vendor/select2/.gitignore -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/LICENSE -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/README.md -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/bower.json -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/component.json -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/composer.json -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/package.json -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/release.sh -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2-bootstrap.css -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2-spinner.gif -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2.css -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2.jquery.json -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ar.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_az.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_bg.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ca.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_cs.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_da.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_de.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_el.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_en.js.template -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_es.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_et.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_eu.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_fa.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_fi.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_fr.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_gl.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_he.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_hr.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_hu.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_id.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_is.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_it.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ja.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ka.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ko.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_lt.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_lv.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_mk.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ms.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_nb.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_nl.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_pl.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_pt-BR.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_pt-PT.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ro.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_rs.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ru.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_sk.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_sv.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_th.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_tr.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_ug-CN.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_uk.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_vi.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_zh-CN.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2_locale_zh-TW.js -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/public/base/vendor/select2/select2x2.png -> build/bdist.linux-x86_64/wheel/ckan/public/base/vendor/select2
  copying ckan/templates/base.html -> build/bdist.linux-x86_64/wheel/ckan/templates
  copying ckan/templates/error_document_template.html -> build/bdist.linux-x86_64/wheel/ckan/templates
  copying ckan/templates/footer.html -> build/bdist.linux-x86_64/wheel/ckan/templates
  copying ckan/templates/header.html -> build/bdist.linux-x86_64/wheel/ckan/templates
  copying ckan/templates/page.html -> build/bdist.linux-x86_64/wheel/ckan/templates
  copying ckan/templates/activity_streams/activity_stream_email_notifications.text -> build/bdist.linux-x86_64/wheel/ckan/templates/activity_streams
  copying ckan/templates/admin/base.html -> build/bdist.linux-x86_64/wheel/ckan/templates/admin
  copying ckan/templates/admin/config.html -> build/bdist.linux-x86_64/wheel/ckan/templates/admin
  copying ckan/templates/admin/confirm_reset.html -> build/bdist.linux-x86_64/wheel/ckan/templates/admin
  copying ckan/templates/admin/index.html -> build/bdist.linux-x86_64/wheel/ckan/templates/admin
  copying ckan/templates/admin/trash.html -> build/bdist.linux-x86_64/wheel/ckan/templates/admin
  copying ckan/templates/admin/snippets/confirm_delete.html -> build/bdist.linux-x86_64/wheel/ckan/templates/admin/snippets
  copying ckan/templates/admin/snippets/data_type.html -> build/bdist.linux-x86_64/wheel/ckan/templates/admin/snippets
  copying ckan/templates/ajax_snippets/custom_fields.html -> build/bdist.linux-x86_64/wheel/ckan/templates/ajax_snippets
  copying ckan/templates/ajax_snippets/follow_button.html -> build/bdist.linux-x86_64/wheel/ckan/templates/ajax_snippets
  copying ckan/templates/dataviewer/base.html -> build/bdist.linux-x86_64/wheel/ckan/templates/dataviewer
  copying ckan/templates/development/primer.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development
  copying ckan/templates/development/snippets/actions.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/breadcrumb.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/context.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/facet.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/form_stages.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/list.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/media_grid.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/module.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/nav.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/page_header.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/pagination.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development/snippets
  copying ckan/templates/development/snippets/simple-input.html -> build/bdist.linux-x86_64/wheel/ckan/templates/development/snippets
  copying ckan/templates/emails/invite_user.txt -> build/bdist.linux-x86_64/wheel/ckan/templates/emails
  copying ckan/templates/emails/invite_user_subject.txt -> build/bdist.linux-x86_64/wheel/ckan/templates/emails
  copying ckan/templates/emails/reset_password.txt -> build/bdist.linux-x86_64/wheel/ckan/templates/emails
  copying ckan/templates/emails/reset_password_subject.txt -> build/bdist.linux-x86_64/wheel/ckan/templates/emails
  copying ckan/templates/group/about.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/admins.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/base_form_page.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/confirm_delete.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/confirm_delete_member.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/edit.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/edit_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/followers.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/index.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/member_new.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/members.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/new.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/new_group_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/read.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/read_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group
  copying ckan/templates/group/snippets/feeds.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group/snippets
  copying ckan/templates/group/snippets/group_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group/snippets
  copying ckan/templates/group/snippets/group_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group/snippets
  copying ckan/templates/group/snippets/group_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group/snippets
  copying ckan/templates/group/snippets/helper.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group/snippets
  copying ckan/templates/group/snippets/info.html -> build/bdist.linux-x86_64/wheel/ckan/templates/group/snippets
  copying ckan/templates/home/about.html -> build/bdist.linux-x86_64/wheel/ckan/templates/home
  copying ckan/templates/home/index.html -> build/bdist.linux-x86_64/wheel/ckan/templates/home
  copying ckan/templates/home/layout1.html -> build/bdist.linux-x86_64/wheel/ckan/templates/home
  copying ckan/templates/home/layout2.html -> build/bdist.linux-x86_64/wheel/ckan/templates/home
  copying ckan/templates/home/layout3.html -> build/bdist.linux-x86_64/wheel/ckan/templates/home
  copying ckan/templates/home/robots.txt -> build/bdist.linux-x86_64/wheel/ckan/templates/home
  copying ckan/templates/home/snippets/about_text.html -> build/bdist.linux-x86_64/wheel/ckan/templates/home/snippets
  copying ckan/templates/home/snippets/featured_group.html -> build/bdist.linux-x86_64/wheel/ckan/templates/home/snippets
  copying ckan/templates/home/snippets/featured_organization.html -> build/bdist.linux-x86_64/wheel/ckan/templates/home/snippets
  copying ckan/templates/home/snippets/promoted.html -> build/bdist.linux-x86_64/wheel/ckan/templates/home/snippets
  copying ckan/templates/home/snippets/search.html -> build/bdist.linux-x86_64/wheel/ckan/templates/home/snippets
  copying ckan/templates/home/snippets/stats.html -> build/bdist.linux-x86_64/wheel/ckan/templates/home/snippets
  copying ckan/templates/macros/autoform.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros
  copying ckan/templates/macros/form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros
  copying ckan/templates/macros/form/attributes.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/checkbox.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/custom.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/errors.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/hidden.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/hidden_from_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/image_upload.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/info.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/input.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/input_block.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/markdown.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/prepend.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/required_message.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/select.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/macros/form/textarea.html -> build/bdist.linux-x86_64/wheel/ckan/templates/macros/form
  copying ckan/templates/organization/about.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/admins.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/base_form_page.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/bulk_process.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/confirm_delete.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/confirm_delete_member.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/edit.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/edit_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/index.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/member_new.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/members.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/new.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/new_organization_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/read.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/read_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization
  copying ckan/templates/organization/snippets/feeds.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization/snippets
  copying ckan/templates/organization/snippets/helper.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization/snippets
  copying ckan/templates/organization/snippets/organization_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization/snippets
  copying ckan/templates/organization/snippets/organization_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization/snippets
  copying ckan/templates/organization/snippets/organization_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates/organization/snippets
  copying ckan/templates/package/base.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/base_form_page.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/confirm_delete.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/confirm_delete_resource.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/edit.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/edit_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/edit_view.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/followers.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/group_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/new.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/new_package_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/new_resource.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/new_resource_not_draft.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/new_view.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/read.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/read_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/resource_edit.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/resource_edit_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/resource_read.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/resource_views.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/resources.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/search.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/view_edit_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package
  copying ckan/templates/package/collaborators/collaborator_new.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/collaborators
  copying ckan/templates/package/collaborators/collaborators.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/collaborators
  copying ckan/templates/package/collaborators/confirm_delete.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/collaborators
  copying ckan/templates/package/snippets/additional_info.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/cannot_create_package.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/info.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/new_package_breadcrumb.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/package_basic_fields.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/package_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/package_metadata_fields.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_edit_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_help.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_info.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_upload_field.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_view.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_view_embed.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_view_filters.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_views_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resource_views_list_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resources.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/resources_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/stages.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/tags.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/view_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/view_form_filters.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/package/snippets/view_help.html -> build/bdist.linux-x86_64/wheel/ckan/templates/package/snippets
  copying ckan/templates/revision/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/templates/revision
  copying ckan/templates/snippets/add_dataset.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/additional_info.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/context.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/csrf_input.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/custom_form_fields.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/datapusher_status.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/disqus_trackback.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/facet_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/follow_button.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/group.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/group_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/home_breadcrumb_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/language_selector.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/license.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/local_friendly_datetime.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/organization.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/organization_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/package_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/package_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/popular.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/private.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/search_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/search_result_text.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/simple_search.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/social.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/tag_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets
  copying ckan/templates/snippets/context/dataset.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets/context
  copying ckan/templates/snippets/context/group.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets/context
  copying ckan/templates/snippets/context/user.html -> build/bdist.linux-x86_64/wheel/ckan/templates/snippets/context
  copying ckan/templates/tests/broken_helper_as_attribute.html -> build/bdist.linux-x86_64/wheel/ckan/templates/tests
  copying ckan/templates/tests/broken_helper_as_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates/tests
  copying ckan/templates/tests/flash_messages.html -> build/bdist.linux-x86_64/wheel/ckan/templates/tests
  copying ckan/templates/tests/helper_as_attribute.html -> build/bdist.linux-x86_64/wheel/ckan/templates/tests
  copying ckan/templates/tests/helper_as_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates/tests
  copying ckan/templates/tests/mock_json_resource_preview_template.html -> build/bdist.linux-x86_64/wheel/ckan/templates/tests
  copying ckan/templates/tests/mock_resource_preview_template.html -> build/bdist.linux-x86_64/wheel/ckan/templates/tests
  copying ckan/templates/user/api_tokens.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/confirm_delete.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/dashboard.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/dashboard_datasets.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/dashboard_groups.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/dashboard_organizations.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/edit.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/edit_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/edit_user_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/followers.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/list.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/login.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/logout.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/logout_first.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/new.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/new_user_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/perform_reset.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/read.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/read_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/request_reset.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user
  copying ckan/templates/user/snippets/api_token_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user/snippets
  copying ckan/templates/user/snippets/followers.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user/snippets
  copying ckan/templates/user/snippets/login_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user/snippets
  copying ckan/templates/user/snippets/placeholder.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user/snippets
  copying ckan/templates/user/snippets/recaptcha.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user/snippets
  copying ckan/templates/user/snippets/user_search.html -> build/bdist.linux-x86_64/wheel/ckan/templates/user/snippets
  copying ckan/templates-bs3/base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3
  copying ckan/templates-bs3/error_document_template.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3
  copying ckan/templates-bs3/footer.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3
  copying ckan/templates-bs3/header.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3
  copying ckan/templates-bs3/page.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3
  copying ckan/templates-bs3/admin/base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/admin
  copying ckan/templates-bs3/admin/config.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/admin
  copying ckan/templates-bs3/admin/confirm_reset.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/admin
  copying ckan/templates-bs3/admin/index.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/admin
  copying ckan/templates-bs3/admin/trash.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/admin
  copying ckan/templates-bs3/admin/snippets/confirm_delete.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/admin/snippets
  copying ckan/templates-bs3/admin/snippets/data_type.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/admin/snippets
  copying ckan/templates-bs3/ajax_snippets/custom_fields.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/ajax_snippets
  copying ckan/templates-bs3/ajax_snippets/follow_button.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/ajax_snippets
  copying ckan/templates-bs3/dataviewer/base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/dataviewer
  copying ckan/templates-bs3/development/primer.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development
  copying ckan/templates-bs3/development/snippets/actions.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/breadcrumb.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/context.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/facet.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/form_stages.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/list.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/media_grid.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/module.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/nav.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/page_header.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/pagination.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/development/snippets/simple-input.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/development/snippets
  copying ckan/templates-bs3/emails/invite_user.txt -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/emails
  copying ckan/templates-bs3/emails/invite_user_subject.txt -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/emails
  copying ckan/templates-bs3/emails/reset_password.txt -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/emails
  copying ckan/templates-bs3/emails/reset_password_subject.txt -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/emails
  copying ckan/templates-bs3/group/about.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/admins.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/base_form_page.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/confirm_delete.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/confirm_delete_member.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/edit.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/edit_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/followers.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/index.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/member_new.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/members.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/new.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/new_group_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/read.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/read_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group
  copying ckan/templates-bs3/group/snippets/feeds.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group/snippets
  copying ckan/templates-bs3/group/snippets/group_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group/snippets
  copying ckan/templates-bs3/group/snippets/group_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group/snippets
  copying ckan/templates-bs3/group/snippets/group_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group/snippets
  copying ckan/templates-bs3/group/snippets/helper.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group/snippets
  copying ckan/templates-bs3/group/snippets/info.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/group/snippets
  copying ckan/templates-bs3/home/about.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/home
  copying ckan/templates-bs3/home/index.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/home
  copying ckan/templates-bs3/home/layout1.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/home
  copying ckan/templates-bs3/home/layout2.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/home
  copying ckan/templates-bs3/home/layout3.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/home
  copying ckan/templates-bs3/home/snippets/about_text.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/home/snippets
  copying ckan/templates-bs3/home/snippets/featured_group.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/home/snippets
  copying ckan/templates-bs3/home/snippets/featured_organization.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/home/snippets
  copying ckan/templates-bs3/home/snippets/promoted.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/home/snippets
  copying ckan/templates-bs3/home/snippets/search.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/home/snippets
  copying ckan/templates-bs3/home/snippets/stats.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/home/snippets
  copying ckan/templates-bs3/macros/autoform.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/macros
  copying ckan/templates-bs3/macros/form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/macros
  copying ckan/templates-bs3/organization/about.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/admins.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/base_form_page.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/bulk_process.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/confirm_delete.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/confirm_delete_member.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/edit.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/edit_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/index.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/member_new.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/members.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/new.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/new_organization_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/read.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/read_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization
  copying ckan/templates-bs3/organization/snippets/feeds.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization/snippets
  copying ckan/templates-bs3/organization/snippets/helper.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization/snippets
  copying ckan/templates-bs3/organization/snippets/organization_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization/snippets
  copying ckan/templates-bs3/organization/snippets/organization_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization/snippets
  copying ckan/templates-bs3/organization/snippets/organization_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/organization/snippets
  copying ckan/templates-bs3/package/base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/base_form_page.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/confirm_delete.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/confirm_delete_resource.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/edit.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/edit_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/edit_view.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/followers.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/group_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/new.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/new_package_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/new_resource.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/new_resource_not_draft.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/new_view.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/read.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/read_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/resource_edit.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/resource_edit_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/resource_read.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/resource_views.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/resources.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/search.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/view_edit_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package
  copying ckan/templates-bs3/package/collaborators/collaborator_new.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/collaborators
  copying ckan/templates-bs3/package/collaborators/collaborators.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/collaborators
  copying ckan/templates-bs3/package/snippets/additional_info.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/cannot_create_package.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/info.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/new_package_breadcrumb.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/package_basic_fields.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/package_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/package_metadata_fields.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_edit_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_help.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_info.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_upload_field.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_view.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_view_embed.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_view_filters.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_views_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resource_views_list_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resources.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/resources_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/stages.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/tags.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/view_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/view_form_filters.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/package/snippets/view_help.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/package/snippets
  copying ckan/templates-bs3/revision/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/revision
  copying ckan/templates-bs3/snippets/add_dataset.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/additional_info.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/context.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/csrf_input.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/custom_form_fields.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/datapusher_status.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/disqus_trackback.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/facet_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/follow_button.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/group.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/group_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/home_breadcrumb_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/language_selector.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/license.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/local_friendly_datetime.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/organization.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/organization_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/package_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/package_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/popular.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/private.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/search_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/search_result_text.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/simple_search.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/social.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/subscribe.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/tag_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets
  copying ckan/templates-bs3/snippets/context/dataset.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets/context
  copying ckan/templates-bs3/snippets/context/group.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets/context
  copying ckan/templates-bs3/snippets/context/user.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/snippets/context
  copying ckan/templates-bs3/tests/broken_helper_as_attribute.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/tests
  copying ckan/templates-bs3/tests/broken_helper_as_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/tests
  copying ckan/templates-bs3/tests/flash_messages.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/tests
  copying ckan/templates-bs3/tests/helper_as_attribute.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/tests
  copying ckan/templates-bs3/tests/helper_as_item.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/tests
  copying ckan/templates-bs3/tests/mock_json_resource_preview_template.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/tests
  copying ckan/templates-bs3/tests/mock_resource_preview_template.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/tests
  copying ckan/templates-bs3/user/api_tokens.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/dashboard.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/dashboard_datasets.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/dashboard_groups.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/dashboard_organizations.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/edit.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/edit_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/edit_user_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/followers.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/list.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/login.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/logout.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/logout_first.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/new.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/new_user_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/perform_reset.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/read.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/read_base.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/request_reset.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user
  copying ckan/templates-bs3/user/snippets/api_token_list.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user/snippets
  copying ckan/templates-bs3/user/snippets/followers.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user/snippets
  copying ckan/templates-bs3/user/snippets/login_form.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user/snippets
  copying ckan/templates-bs3/user/snippets/placeholder.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user/snippets
  copying ckan/templates-bs3/user/snippets/recaptcha.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user/snippets
  copying ckan/templates-bs3/user/snippets/user_search.html -> build/bdist.linux-x86_64/wheel/ckan/templates-bs3/user/snippets
  copying ckan/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests
  copying ckan/tests/factories.py -> build/bdist.linux-x86_64/wheel/ckan/tests
  copying ckan/tests/helpers.py -> build/bdist.linux-x86_64/wheel/ckan/tests
  copying ckan/tests/test_authz.py -> build/bdist.linux-x86_64/wheel/ckan/tests
  copying ckan/tests/test_coding_standards.py -> build/bdist.linux-x86_64/wheel/ckan/tests
  copying ckan/tests/test_common.py -> build/bdist.linux-x86_64/wheel/ckan/tests
  copying ckan/tests/test_factories.py -> build/bdist.linux-x86_64/wheel/ckan/tests
  copying ckan/tests/test_none_root.py -> build/bdist.linux-x86_64/wheel/ckan/tests
  copying ckan/tests/test_robots_txt.py -> build/bdist.linux-x86_64/wheel/ckan/tests
  copying ckan/tests/cli/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/cli
  copying ckan/tests/cli/test_asset.py -> build/bdist.linux-x86_64/wheel/ckan/tests/cli
  copying ckan/tests/cli/test_clean.py -> build/bdist.linux-x86_64/wheel/ckan/tests/cli
  copying ckan/tests/cli/test_cli.py -> build/bdist.linux-x86_64/wheel/ckan/tests/cli
  copying ckan/tests/cli/test_config.py -> build/bdist.linux-x86_64/wheel/ckan/tests/cli
  copying ckan/tests/cli/test_config_tool.py -> build/bdist.linux-x86_64/wheel/ckan/tests/cli
  copying ckan/tests/cli/test_db.py -> build/bdist.linux-x86_64/wheel/ckan/tests/cli
  copying ckan/tests/cli/test_jobs.py -> build/bdist.linux-x86_64/wheel/ckan/tests/cli
  copying ckan/tests/cli/test_search_index.py -> build/bdist.linux-x86_64/wheel/ckan/tests/cli
  copying ckan/tests/cli/test_user.py -> build/bdist.linux-x86_64/wheel/ckan/tests/cli
  copying ckan/tests/cli/data/test-env-var.ini -> build/bdist.linux-x86_64/wheel/ckan/tests/cli/data
  copying ckan/tests/cli/data/test-invalid-use.ini -> build/bdist.linux-x86_64/wheel/ckan/tests/cli/data
  copying ckan/tests/cli/data/test-no-env-var.ini -> build/bdist.linux-x86_64/wheel/ckan/tests/cli/data
  copying ckan/tests/cli/data/test-one-recursive.ini -> build/bdist.linux-x86_64/wheel/ckan/tests/cli/data
  copying ckan/tests/cli/data/test-one.ini -> build/bdist.linux-x86_64/wheel/ckan/tests/cli/data
  copying ckan/tests/cli/data/test-three-recursive.ini -> build/bdist.linux-x86_64/wheel/ckan/tests/cli/data
  copying ckan/tests/cli/data/test-three.ini -> build/bdist.linux-x86_64/wheel/ckan/tests/cli/data
  copying ckan/tests/cli/data/sub/test-two-recursive.ini -> build/bdist.linux-x86_64/wheel/ckan/tests/cli/data/sub
  copying ckan/tests/cli/data/sub/test-two.ini -> build/bdist.linux-x86_64/wheel/ckan/tests/cli/data/sub
  copying ckan/tests/config/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/config
  copying ckan/tests/config/test_environment.py -> build/bdist.linux-x86_64/wheel/ckan/tests/config
  copying ckan/tests/config/test_middleware.py -> build/bdist.linux-x86_64/wheel/ckan/tests/config
  copying ckan/tests/config/test_sessions.py -> build/bdist.linux-x86_64/wheel/ckan/tests/config
  copying ckan/tests/config/declaration/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/config/declaration
  copying ckan/tests/config/declaration/test_declaration.py -> build/bdist.linux-x86_64/wheel/ckan/tests/config/declaration
  copying ckan/tests/config/declaration/test_key.py -> build/bdist.linux-x86_64/wheel/ckan/tests/config/declaration
  copying ckan/tests/config/declaration/test_option.py -> build/bdist.linux-x86_64/wheel/ckan/tests/config/declaration
  copying ckan/tests/controllers/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/controllers
  copying ckan/tests/controllers/test_admin.py -> build/bdist.linux-x86_64/wheel/ckan/tests/controllers
  copying ckan/tests/controllers/test_api.py -> build/bdist.linux-x86_64/wheel/ckan/tests/controllers
  copying ckan/tests/controllers/test_feed.py -> build/bdist.linux-x86_64/wheel/ckan/tests/controllers
  copying ckan/tests/controllers/test_group.py -> build/bdist.linux-x86_64/wheel/ckan/tests/controllers
  copying ckan/tests/controllers/test_home.py -> build/bdist.linux-x86_64/wheel/ckan/tests/controllers
  copying ckan/tests/controllers/test_organization.py -> build/bdist.linux-x86_64/wheel/ckan/tests/controllers
  copying ckan/tests/controllers/test_package.py -> build/bdist.linux-x86_64/wheel/ckan/tests/controllers
  copying ckan/tests/controllers/test_pagination.py -> build/bdist.linux-x86_64/wheel/ckan/tests/controllers
  copying ckan/tests/controllers/test_resource.py -> build/bdist.linux-x86_64/wheel/ckan/tests/controllers
  copying ckan/tests/controllers/test_user.py -> build/bdist.linux-x86_64/wheel/ckan/tests/controllers
  copying ckan/tests/controllers/test_util.py -> build/bdist.linux-x86_64/wheel/ckan/tests/controllers
  copying ckan/tests/i18n/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/i18n
  copying ckan/tests/i18n/test_check_po_files.py -> build/bdist.linux-x86_64/wheel/ckan/tests/i18n
  copying ckan/tests/lib/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_app_globals.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_authenticator.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_base.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_config_tool.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_datapreview.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_formatters.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_hash.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_helpers.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_i18n.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_io.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_jobs.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_mailer.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_munge.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_signals.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/test_uploader.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib
  copying ckan/tests/lib/dictization/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib/dictization
  copying ckan/tests/lib/dictization/test_dictization.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib/dictization
  copying ckan/tests/lib/dictization/test_model_dictize.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib/dictization
  copying ckan/tests/lib/navl/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib/navl
  copying ckan/tests/lib/navl/test_dictization_functions.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib/navl
  copying ckan/tests/lib/navl/test_validators.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib/navl
  copying ckan/tests/lib/search/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib/search
  copying ckan/tests/lib/search/test_common.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib/search
  copying ckan/tests/lib/search/test_index.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib/search
  copying ckan/tests/lib/search/test_query.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib/search
  copying ckan/tests/lib/search/test_search.py -> build/bdist.linux-x86_64/wheel/ckan/tests/lib/search
  copying ckan/tests/logic/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic
  copying ckan/tests/logic/test_conversion.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic
  copying ckan/tests/logic/test_converters.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic
  copying ckan/tests/logic/test_logic.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic
  copying ckan/tests/logic/test_schema.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic
  copying ckan/tests/logic/test_validators.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic
  copying ckan/tests/logic/action/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic/action
  copying ckan/tests/logic/action/test_create.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic/action
  copying ckan/tests/logic/action/test_delete.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic/action
  copying ckan/tests/logic/action/test_get.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic/action
  copying ckan/tests/logic/action/test_init.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic/action
  copying ckan/tests/logic/action/test_patch.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic/action
  copying ckan/tests/logic/action/test_update.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic/action
  copying ckan/tests/logic/auth/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic/auth
  copying ckan/tests/logic/auth/test_create.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic/auth
  copying ckan/tests/logic/auth/test_delete.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic/auth
  copying ckan/tests/logic/auth/test_get.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic/auth
  copying ckan/tests/logic/auth/test_init.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic/auth
  copying ckan/tests/logic/auth/test_update.py -> build/bdist.linux-x86_64/wheel/ckan/tests/logic/auth
  copying ckan/tests/model/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/model
  copying ckan/tests/model/test_api_token.py -> build/bdist.linux-x86_64/wheel/ckan/tests/model
  copying ckan/tests/model/test_follower.py -> build/bdist.linux-x86_64/wheel/ckan/tests/model
  copying ckan/tests/model/test_group.py -> build/bdist.linux-x86_64/wheel/ckan/tests/model
  copying ckan/tests/model/test_license.py -> build/bdist.linux-x86_64/wheel/ckan/tests/model
  copying ckan/tests/model/test_misc.py -> build/bdist.linux-x86_64/wheel/ckan/tests/model
  copying ckan/tests/model/test_package.py -> build/bdist.linux-x86_64/wheel/ckan/tests/model
  copying ckan/tests/model/test_package_extra.py -> build/bdist.linux-x86_64/wheel/ckan/tests/model
  copying ckan/tests/model/test_resource.py -> build/bdist.linux-x86_64/wheel/ckan/tests/model
  copying ckan/tests/model/test_resource_view.py -> build/bdist.linux-x86_64/wheel/ckan/tests/model
  copying ckan/tests/model/test_system_info.py -> build/bdist.linux-x86_64/wheel/ckan/tests/model
  copying ckan/tests/model/test_tags.py -> build/bdist.linux-x86_64/wheel/ckan/tests/model
  copying ckan/tests/model/test_user.py -> build/bdist.linux-x86_64/wheel/ckan/tests/model
  copying ckan/tests/plugins/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/plugins
  copying ckan/tests/plugins/ckantestplugins.py -> build/bdist.linux-x86_64/wheel/ckan/tests/plugins
  copying ckan/tests/plugins/mock_plugin.py -> build/bdist.linux-x86_64/wheel/ckan/tests/plugins
  copying ckan/tests/plugins/test_blanket.py -> build/bdist.linux-x86_64/wheel/ckan/tests/plugins
  copying ckan/tests/plugins/test_core.py -> build/bdist.linux-x86_64/wheel/ckan/tests/plugins
  copying ckan/tests/plugins/test_interfaces.py -> build/bdist.linux-x86_64/wheel/ckan/tests/plugins
  copying ckan/tests/plugins/test_toolkit.py -> build/bdist.linux-x86_64/wheel/ckan/tests/plugins
  copying ckan/tests/pytest_ckan/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/tests/pytest_ckan
  copying ckan/tests/pytest_ckan/ckan_setup.py -> build/bdist.linux-x86_64/wheel/ckan/tests/pytest_ckan
  copying ckan/tests/pytest_ckan/fixtures.py -> build/bdist.linux-x86_64/wheel/ckan/tests/pytest_ckan
  copying ckan/tests/pytest_ckan/test_fixtures.py -> build/bdist.linux-x86_64/wheel/ckan/tests/pytest_ckan
  copying ckan/types/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/types
  copying ckan/types/model.py -> build/bdist.linux-x86_64/wheel/ckan/types
  copying ckan/types/logic/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/types/logic
  copying ckan/types/logic/action_result.py -> build/bdist.linux-x86_64/wheel/ckan/types/logic
  copying ckan/views/__init__.py -> build/bdist.linux-x86_64/wheel/ckan/views
  copying ckan/views/admin.py -> build/bdist.linux-x86_64/wheel/ckan/views
  copying ckan/views/api.py -> build/bdist.linux-x86_64/wheel/ckan/views
  copying ckan/views/dashboard.py -> build/bdist.linux-x86_64/wheel/ckan/views
  copying ckan/views/dataset.py -> build/bdist.linux-x86_64/wheel/ckan/views
  copying ckan/views/feed.py -> build/bdist.linux-x86_64/wheel/ckan/views
  copying ckan/views/group.py -> build/bdist.linux-x86_64/wheel/ckan/views
  copying ckan/views/home.py -> build/bdist.linux-x86_64/wheel/ckan/views
  copying ckan/views/resource.py -> build/bdist.linux-x86_64/wheel/ckan/views
  copying ckan/views/user.py -> build/bdist.linux-x86_64/wheel/ckan/views
  copying ckan/views/util.py -> build/bdist.linux-x86_64/wheel/ckan/views
  Skipping installation of build/bdist.linux-x86_64/wheel/ckanext/__init__.py (namespace package)
  copying ckanext/activity/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/activity
  copying ckanext/activity/changes.py -> build/bdist.linux-x86_64/wheel/ckanext/activity
  copying ckanext/activity/email_notifications.py -> build/bdist.linux-x86_64/wheel/ckanext/activity
  copying ckanext/activity/helpers.py -> build/bdist.linux-x86_64/wheel/ckanext/activity
  copying ckanext/activity/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/activity
  copying ckanext/activity/subscriptions.py -> build/bdist.linux-x86_64/wheel/ckanext/activity
  copying ckanext/activity/views.py -> build/bdist.linux-x86_64/wheel/ckanext/activity
  copying ckanext/activity/assets/activity-stream.js -> build/bdist.linux-x86_64/wheel/ckanext/activity/assets
  copying ckanext/activity/assets/activity.css -> build/bdist.linux-x86_64/wheel/ckanext/activity/assets
  copying ckanext/activity/assets/activity.css.map -> build/bdist.linux-x86_64/wheel/ckanext/activity/assets
  copying ckanext/activity/assets/activity.scss -> build/bdist.linux-x86_64/wheel/ckanext/activity/assets
  copying ckanext/activity/assets/dashboard.js -> build/bdist.linux-x86_64/wheel/ckanext/activity/assets
  copying ckanext/activity/assets/dashboard.spec.js -> build/bdist.linux-x86_64/wheel/ckanext/activity/assets
  copying ckanext/activity/assets/webassets.yml -> build/bdist.linux-x86_64/wheel/ckanext/activity/assets
  copying ckanext/activity/logic/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/logic
  copying ckanext/activity/logic/action.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/logic
  copying ckanext/activity/logic/auth.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/logic
  copying ckanext/activity/logic/schema.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/logic
  copying ckanext/activity/logic/validators.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/logic
  copying ckanext/activity/model/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/model
  copying ckanext/activity/model/activity.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/model
  copying ckanext/activity/public/dotted.png -> build/bdist.linux-x86_64/wheel/ckanext/activity/public
  copying ckanext/activity/templates/base.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates
  copying ckanext/activity/templates/header.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates
  copying ckanext/activity/templates/page.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates
  copying ckanext/activity/templates/activity_streams/activity_stream_email_notifications.text -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/activity_streams
  copying ckanext/activity/templates/ajax_snippets/dashboard.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/ajax_snippets
  copying ckanext/activity/templates/group/activity_stream.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/group
  copying ckanext/activity/templates/group/changes.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/group
  copying ckanext/activity/templates/group/read_base.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/group
  copying ckanext/activity/templates/group/snippets/item_group.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/group/snippets
  copying ckanext/activity/templates/organization/activity_stream.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/organization
  copying ckanext/activity/templates/organization/changes.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/organization
  copying ckanext/activity/templates/organization/read_base.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/organization
  copying ckanext/activity/templates/organization/snippets/item_organization.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/organization/snippets
  copying ckanext/activity/templates/package/activity_stream.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/package
  copying ckanext/activity/templates/package/changes.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/package
  copying ckanext/activity/templates/package/history.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/package
  copying ckanext/activity/templates/package/read_base.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/package
  copying ckanext/activity/templates/package/resource_history.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/package
  copying ckanext/activity/templates/package/snippets/change_item.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/package/snippets
  copying ckanext/activity/templates/package/snippets/resource_item.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/package/snippets
  copying ckanext/activity/templates/package/snippets/resources.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/package/snippets
  copying ckanext/activity/templates/package/snippets/resources_list.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/package/snippets
  copying ckanext/activity/templates/snippets/activity_type_selector.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets
  copying ckanext/activity/templates/snippets/pagination.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets
  copying ckanext/activity/templates/snippets/stream.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets
  copying ckanext/activity/templates/snippets/activities/added_tag.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/changed_group.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/changed_organization.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/changed_package.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/changed_resource.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/changed_user.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/deleted_group.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/deleted_organization.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/deleted_package.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/deleted_resource.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/fallback.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/follow_dataset.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/follow_group.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/follow_user.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/new_group.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/new_organization.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/new_package.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/new_resource.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/new_user.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/activities/removed_tag.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/activities
  copying ckanext/activity/templates/snippets/changes/author.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/author_email.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/delete_resource.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/extension_fields.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/extra_fields.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/license.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/maintainer.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/maintainer_email.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/name.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/new_file.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/new_resource.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/no_change.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/notes.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/org.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/private.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/resource_desc.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/resource_extras.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/resource_format.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/resource_name.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/tags.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/title.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/url.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/changes/version.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/changes
  copying ckanext/activity/templates/snippets/group_changes/description.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/group_changes
  copying ckanext/activity/templates/snippets/group_changes/image_url.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/group_changes
  copying ckanext/activity/templates/snippets/group_changes/no_change.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/group_changes
  copying ckanext/activity/templates/snippets/group_changes/title.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/group_changes
  copying ckanext/activity/templates/snippets/organization_changes/description.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/organization_changes
  copying ckanext/activity/templates/snippets/organization_changes/image_url.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/organization_changes
  copying ckanext/activity/templates/snippets/organization_changes/no_change.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/organization_changes
  copying ckanext/activity/templates/snippets/organization_changes/title.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/snippets/organization_changes
  copying ckanext/activity/templates/user/activity_stream.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/user
  copying ckanext/activity/templates/user/dashboard.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/user
  copying ckanext/activity/templates/user/edit_user_form.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/user
  copying ckanext/activity/templates/user/read_base.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/user
  copying ckanext/activity/templates/user/snippets/followee_dropdown.html -> build/bdist.linux-x86_64/wheel/ckanext/activity/templates/user/snippets
  copying ckanext/activity/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/tests
  copying ckanext/activity/tests/conftest.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/tests
  copying ckanext/activity/tests/test_changes.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/tests
  copying ckanext/activity/tests/test_email_notifications.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/tests
  copying ckanext/activity/tests/test_helpers.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/tests
  copying ckanext/activity/tests/test_views.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/tests
  copying ckanext/activity/tests/logic/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/tests/logic
  copying ckanext/activity/tests/logic/test_action.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/tests/logic
  copying ckanext/activity/tests/logic/test_auth.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/tests/logic
  copying ckanext/activity/tests/logic/test_functional.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/tests/logic
  copying ckanext/activity/tests/logic/test_pagination.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/tests/logic
  copying ckanext/activity/tests/model/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/tests/model
  copying ckanext/activity/tests/model/test_activity.py -> build/bdist.linux-x86_64/wheel/ckanext/activity/tests/model
  copying ckanext/audioview/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/audioview
  copying ckanext/audioview/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/audioview
  copying ckanext/audioview/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/audioview/tests
  copying ckanext/audioview/tests/test_view.py -> build/bdist.linux-x86_64/wheel/ckanext/audioview/tests
  copying ckanext/audioview/theme/templates/audio_form.html -> build/bdist.linux-x86_64/wheel/ckanext/audioview/theme/templates
  copying ckanext/audioview/theme/templates/audio_view.html -> build/bdist.linux-x86_64/wheel/ckanext/audioview/theme/templates
  copying ckanext/chained_functions/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/chained_functions
  copying ckanext/chained_functions/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/chained_functions
  copying ckanext/chained_functions/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/chained_functions/tests
  copying ckanext/chained_functions/tests/test_plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/chained_functions/tests
  copying ckanext/datapusher/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher
  copying ckanext/datapusher/cli.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher
  copying ckanext/datapusher/config_declaration.yaml -> build/bdist.linux-x86_64/wheel/ckanext/datapusher
  copying ckanext/datapusher/helpers.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher
  copying ckanext/datapusher/interfaces.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher
  copying ckanext/datapusher/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher
  copying ckanext/datapusher/views.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher
  copying ckanext/datapusher/assets/datapusher.css -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/assets
  copying ckanext/datapusher/assets/datapusher.css.map -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/assets
  copying ckanext/datapusher/assets/datapusher.scss -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/assets
  copying ckanext/datapusher/assets/datapusher_popover.js -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/assets
  copying ckanext/datapusher/assets/webassets.yml -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/assets
  copying ckanext/datapusher/logic/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/logic
  copying ckanext/datapusher/logic/action.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/logic
  copying ckanext/datapusher/logic/auth.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/logic
  copying ckanext/datapusher/logic/schema.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/logic
  copying ckanext/datapusher/public/dotted.png -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/public
  copying ckanext/datapusher/templates/datapusher/resource_data.html -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/templates/datapusher
  copying ckanext/datapusher/templates/package/resource_edit_base.html -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/templates/package
  copying ckanext/datapusher/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/tests
  copying ckanext/datapusher/tests/test.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/tests
  copying ckanext/datapusher/tests/test_action.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/tests
  copying ckanext/datapusher/tests/test_default_views.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/tests
  copying ckanext/datapusher/tests/test_interfaces.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/tests
  copying ckanext/datapusher/tests/test_views.py -> build/bdist.linux-x86_64/wheel/ckanext/datapusher/tests
  copying ckanext/datastore/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore
  copying ckanext/datastore/allowed_functions.txt -> build/bdist.linux-x86_64/wheel/ckanext/datastore
  copying ckanext/datastore/blueprint.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore
  copying ckanext/datastore/cli.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore
  copying ckanext/datastore/config_declaration.yaml -> build/bdist.linux-x86_64/wheel/ckanext/datastore
  copying ckanext/datastore/helpers.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore
  copying ckanext/datastore/interfaces.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore
  copying ckanext/datastore/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore
  copying ckanext/datastore/set_permissions.sql -> build/bdist.linux-x86_64/wheel/ckanext/datastore
  copying ckanext/datastore/writer.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore
  copying ckanext/datastore/backend/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/backend
  copying ckanext/datastore/backend/postgres.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/backend
  copying ckanext/datastore/logic/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/logic
  copying ckanext/datastore/logic/action.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/logic
  copying ckanext/datastore/logic/auth.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/logic
  copying ckanext/datastore/logic/schema.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/logic
  copying ckanext/datastore/templates/ajax_snippets/api_info.html -> build/bdist.linux-x86_64/wheel/ckanext/datastore/templates/ajax_snippets
  copying ckanext/datastore/templates/datastore/dictionary.html -> build/bdist.linux-x86_64/wheel/ckanext/datastore/templates/datastore
  copying ckanext/datastore/templates/datastore/snippets/dictionary_form.html -> build/bdist.linux-x86_64/wheel/ckanext/datastore/templates/datastore/snippets
  copying ckanext/datastore/templates/package/resource_edit_base.html -> build/bdist.linux-x86_64/wheel/ckanext/datastore/templates/package
  copying ckanext/datastore/templates/package/resource_read.html -> build/bdist.linux-x86_64/wheel/ckanext/datastore/templates/package
  copying ckanext/datastore/templates/package/snippets/data_api_button.html -> build/bdist.linux-x86_64/wheel/ckanext/datastore/templates/package/snippets
  copying ckanext/datastore/templates/package/snippets/dictionary_table.html -> build/bdist.linux-x86_64/wheel/ckanext/datastore/templates/package/snippets
  copying ckanext/datastore/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/conftest.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/helpers.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/sample_datastore_plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_auth.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_chained_action.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_chained_auth_functions.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_create.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_db.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_delete.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_dictionary.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_disable.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_dump.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_helpers.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_info.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_interface.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_search.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_unit.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datastore/tests/test_upsert.py -> build/bdist.linux-x86_64/wheel/ckanext/datastore/tests
  copying ckanext/datatablesview/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview
  copying ckanext/datatablesview/blueprint.py -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview
  copying ckanext/datatablesview/config_declaration.yaml -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview
  copying ckanext/datatablesview/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview
  copying ckanext/datatablesview/public/datatables_view.css -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public
  copying ckanext/datatablesview/public/datatablesview.js -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public
  copying ckanext/datatablesview/public/resource.config -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public
  copying ckanext/datatablesview/public/webassets.yml -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public
  copying ckanext/datatablesview/public/vendor/DataTables/dataTables.scrollResize.js -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/datatables.css -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/datatables.js -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/datatables.mark.css -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/datatables.mark.js -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/datetime.js -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/jquery.mark.js -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/af.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/am.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ar.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/az.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/az_az.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/be.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/bg.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/bn.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/bs.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ca.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/cs.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/cs_CZ.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/cy.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/da.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/de.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/el.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/en-gb.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/en_GB.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/eo.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/es.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/et.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/eu.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/fa.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/fi.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/fil.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/fr.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ga.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/gl.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/gu.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/he.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/hi.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/hr.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/hu.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/hy.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/id.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/id_alt.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/is.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/it.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ja.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ka.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/kk.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/km.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/kn.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ko.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ko_KR.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ku.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ky.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/lo.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/lt.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/lv.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/mk.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/mn.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ms.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ne.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/nl.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/no.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/no_nb.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/pa.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/pl.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ps.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/pt.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/pt_BR.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/pt_pt.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/rm.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ro.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ru.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/si.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sk.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sl.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/snd.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sq.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sr.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sr@latin.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sr_sp.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sv.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/sw.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ta.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/te.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/tg.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/th.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/tl.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/tr.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/uk.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/ur.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/uz.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/vi.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/zh.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/zh_CN.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/DataTables/i18n/zh_Hant.json -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/DataTables/i18n
  copying ckanext/datatablesview/public/vendor/FontAwesome/images/times-circle-solid.svg -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/public/vendor/FontAwesome/images
  copying ckanext/datatablesview/templates/datatables/datatables_form.html -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/templates/datatables
  copying ckanext/datatablesview/templates/datatables/datatables_view.html -> build/bdist.linux-x86_64/wheel/ckanext/datatablesview/templates/datatables
  copying ckanext/example_blanket_implementation/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_blanket_implementation
  copying ckanext/example_blanket_implementation/cli.py -> build/bdist.linux-x86_64/wheel/ckanext/example_blanket_implementation
  copying ckanext/example_blanket_implementation/config_declaration.yaml -> build/bdist.linux-x86_64/wheel/ckanext/example_blanket_implementation
  copying ckanext/example_blanket_implementation/helpers.py -> build/bdist.linux-x86_64/wheel/ckanext/example_blanket_implementation
  copying ckanext/example_blanket_implementation/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_blanket_implementation
  copying ckanext/example_blanket_implementation/views.py -> build/bdist.linux-x86_64/wheel/ckanext/example_blanket_implementation
  copying ckanext/example_blanket_implementation/logic/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_blanket_implementation/logic
  copying ckanext/example_blanket_implementation/logic/auth.py -> build/bdist.linux-x86_64/wheel/ckanext/example_blanket_implementation/logic
  copying ckanext/example_blanket_implementation/logic/validators.py -> build/bdist.linux-x86_64/wheel/ckanext/example_blanket_implementation/logic
  copying ckanext/example_blanket_implementation/logic/action/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_blanket_implementation/logic/action
  copying ckanext/example_database_migrations/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_database_migrations
  copying ckanext/example_database_migrations/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_database_migrations
  copying ckanext/example_database_migrations/migration/example_database_migrations/env.py -> build/bdist.linux-x86_64/wheel/ckanext/example_database_migrations/migration/example_database_migrations
  copying ckanext/example_database_migrations/migration/example_database_migrations/versions/4f59069f433e_create_x_table.py -> build/bdist.linux-x86_64/wheel/ckanext/example_database_migrations/migration/example_database_migrations/versions
  copying ckanext/example_database_migrations/migration/example_database_migrations/versions/728663ebe30e_create_y_table.py -> build/bdist.linux-x86_64/wheel/ckanext/example_database_migrations/migration/example_database_migrations/versions
  copying ckanext/example_flask_iblueprint/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_flask_iblueprint
  copying ckanext/example_flask_iblueprint/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_flask_iblueprint
  copying ckanext/example_flask_iblueprint/templates/about.html -> build/bdist.linux-x86_64/wheel/ckanext/example_flask_iblueprint/templates
  copying ckanext/example_flask_iblueprint/templates/about_base.html -> build/bdist.linux-x86_64/wheel/ckanext/example_flask_iblueprint/templates
  copying ckanext/example_flask_iblueprint/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_flask_iblueprint/tests
  copying ckanext/example_flask_iblueprint/tests/test_routes.py -> build/bdist.linux-x86_64/wheel/ckanext/example_flask_iblueprint/tests
  copying ckanext/example_flask_streaming/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_flask_streaming
  copying ckanext/example_flask_streaming/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_flask_streaming
  copying ckanext/example_flask_streaming/templates/stream.html -> build/bdist.linux-x86_64/wheel/ckanext/example_flask_streaming/templates
  copying ckanext/example_flask_streaming/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_flask_streaming/tests
  copying ckanext/example_flask_streaming/tests/test_streaming_responses.py -> build/bdist.linux-x86_64/wheel/ckanext/example_flask_streaming/tests
  copying ckanext/example_humanizer/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_humanizer
  copying ckanext/example_humanizer/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_humanizer
  copying ckanext/example_humanizer/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_humanizer/tests
  copying ckanext/example_humanizer/tests/test_plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_humanizer/tests
  copying ckanext/example_iapitoken/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iapitoken
  copying ckanext/example_iapitoken/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iapitoken
  copying ckanext/example_iapitoken/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iapitoken/tests
  copying ckanext/example_iapitoken/tests/test_plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iapitoken/tests
  copying ckanext/example_iauthenticator/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iauthenticator
  copying ckanext/example_iauthenticator/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iauthenticator
  copying ckanext/example_iauthenticator/tests/test_example_iauthenticator.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iauthenticator/tests
  copying ckanext/example_iauthfunctions/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/plugin_v1.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/plugin_v2.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/plugin_v3.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/plugin_v4.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/plugin_v5_custom_config_setting.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/plugin_v6_parent_auth_functions.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iauthfunctions
  copying ckanext/example_iauthfunctions/tests/test_example_iauthfunctions.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iauthfunctions/tests
  copying ckanext/example_iclick/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iclick
  copying ckanext/example_iclick/cli.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iclick
  copying ckanext/example_iclick/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iclick
  copying ckanext/example_iconfigurer/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iconfigurer
  copying ckanext/example_iconfigurer/blueprint.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iconfigurer
  copying ckanext/example_iconfigurer/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iconfigurer
  copying ckanext/example_iconfigurer/plugin_v1.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iconfigurer
  copying ckanext/example_iconfigurer/plugin_v2.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iconfigurer
  copying ckanext/example_iconfigurer/templates/admin/config.html -> build/bdist.linux-x86_64/wheel/ckanext/example_iconfigurer/templates/admin
  copying ckanext/example_iconfigurer/templates/admin/myext_config.html -> build/bdist.linux-x86_64/wheel/ckanext/example_iconfigurer/templates/admin
  copying ckanext/example_iconfigurer/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iconfigurer/tests
  copying ckanext/example_iconfigurer/tests/test_example_iconfigurer.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iconfigurer/tests
  copying ckanext/example_iconfigurer/tests/test_iconfigurer_toolkit.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iconfigurer/tests
  copying ckanext/example_iconfigurer/tests/test_iconfigurer_update_config.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iconfigurer/tests
  copying ckanext/example_idatasetform/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v1.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v2.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v3.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v4.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v5.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v6.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/plugin_v7.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform
  copying ckanext/example_idatasetform/templates/first/new.html -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform/templates/first
  copying ckanext/example_idatasetform/templates/first/read.html -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform/templates/first
  copying ckanext/example_idatasetform/templates/package/read.html -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform/templates/package
  copying ckanext/example_idatasetform/templates/package/search.html -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform/templates/package
  copying ckanext/example_idatasetform/templates/package/snippets/additional_info.html -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform/templates/package/snippets
  copying ckanext/example_idatasetform/templates/package/snippets/package_basic_fields.html -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform/templates/package/snippets
  copying ckanext/example_idatasetform/templates/package/snippets/package_metadata_fields.html -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform/templates/package/snippets
  copying ckanext/example_idatasetform/templates/package/snippets/resource_form.html -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform/templates/package/snippets
  copying ckanext/example_idatasetform/templates/second/read.html -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform/templates/second
  copying ckanext/example_idatasetform/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform/tests
  copying ckanext/example_idatasetform/tests/test_controllers.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform/tests
  copying ckanext/example_idatasetform/tests/test_example_idatasetform.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatasetform/tests
  copying ckanext/example_idatastorebackend/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatastorebackend
  copying ckanext/example_idatastorebackend/example_sqlite.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatastorebackend
  copying ckanext/example_idatastorebackend/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatastorebackend
  copying ckanext/example_idatastorebackend/test/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatastorebackend/test
  copying ckanext/example_idatastorebackend/test/test_plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_idatastorebackend/test
  copying ckanext/example_igroupform/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_igroupform
  copying ckanext/example_igroupform/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_igroupform
  copying ckanext/example_igroupform/plugin_v2.py -> build/bdist.linux-x86_64/wheel/ckanext/example_igroupform
  copying ckanext/example_igroupform/templates/example_igroup_form/group_form.html -> build/bdist.linux-x86_64/wheel/ckanext/example_igroupform/templates/example_igroup_form
  copying ckanext/example_igroupform/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_igroupform/tests
  copying ckanext/example_igroupform/tests/test_controllers.py -> build/bdist.linux-x86_64/wheel/ckanext/example_igroupform/tests
  copying ckanext/example_ipermissionlabels/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_ipermissionlabels
  copying ckanext/example_ipermissionlabels/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_ipermissionlabels
  copying ckanext/example_ipermissionlabels/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_ipermissionlabels/tests
  copying ckanext/example_ipermissionlabels/tests/test_example_ipermissionlabels.py -> build/bdist.linux-x86_64/wheel/ckanext/example_ipermissionlabels/tests
  copying ckanext/example_iresourcecontroller/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iresourcecontroller
  copying ckanext/example_iresourcecontroller/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iresourcecontroller
  copying ckanext/example_iresourcecontroller/tests/test_example_iresourcecontroller.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iresourcecontroller/tests
  copying ckanext/example_isignal/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_isignal
  copying ckanext/example_isignal/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_isignal
  copying ckanext/example_isignal/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_isignal/tests
  copying ckanext/example_isignal/tests/test_plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_isignal/tests
  copying ckanext/example_itemplatehelpers/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_itemplatehelpers
  copying ckanext/example_itemplatehelpers/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_itemplatehelpers
  copying ckanext/example_itemplatehelpers/templates/home/index.html -> build/bdist.linux-x86_64/wheel/ckanext/example_itemplatehelpers/templates/home
  copying ckanext/example_itemplatehelpers/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_itemplatehelpers/tests
  copying ckanext/example_itemplatehelpers/tests/test_plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_itemplatehelpers/tests
  copying ckanext/example_itranslation/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_itranslation
  copying ckanext/example_itranslation/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_itranslation
  copying ckanext/example_itranslation/plugin_v1.py -> build/bdist.linux-x86_64/wheel/ckanext/example_itranslation
  copying ckanext/example_itranslation/i18n/ckanext-example_itranslation.pot -> build/bdist.linux-x86_64/wheel/ckanext/example_itranslation/i18n
  copying ckanext/example_itranslation/i18n/en/LC_MESSAGES/ckanext-example_itranslation.mo -> build/bdist.linux-x86_64/wheel/ckanext/example_itranslation/i18n/en/LC_MESSAGES
  copying ckanext/example_itranslation/i18n/en/LC_MESSAGES/ckanext-example_itranslation.po -> build/bdist.linux-x86_64/wheel/ckanext/example_itranslation/i18n/en/LC_MESSAGES
  copying ckanext/example_itranslation/i18n/en/LC_MESSAGES/ckanext-example_translation.po -> build/bdist.linux-x86_64/wheel/ckanext/example_itranslation/i18n/en/LC_MESSAGES
  copying ckanext/example_itranslation/i18n/fr/LC_MESSAGES/ckanext-example_itranslation.mo -> build/bdist.linux-x86_64/wheel/ckanext/example_itranslation/i18n/fr/LC_MESSAGES
  copying ckanext/example_itranslation/i18n/fr/LC_MESSAGES/ckanext-example_itranslation.po -> build/bdist.linux-x86_64/wheel/ckanext/example_itranslation/i18n/fr/LC_MESSAGES
  copying ckanext/example_itranslation/templates/home/index.html -> build/bdist.linux-x86_64/wheel/ckanext/example_itranslation/templates/home
  copying ckanext/example_itranslation/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_itranslation/tests
  copying ckanext/example_itranslation/tests/test_plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_itranslation/tests
  copying ckanext/example_iuploader/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iuploader
  copying ckanext/example_iuploader/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iuploader
  copying ckanext/example_iuploader/test/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iuploader/test
  copying ckanext/example_iuploader/test/test_plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_iuploader/test
  copying ckanext/example_ivalidators/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_ivalidators
  copying ckanext/example_ivalidators/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_ivalidators
  copying ckanext/example_ivalidators/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_ivalidators/tests
  copying ckanext/example_ivalidators/tests/test_ivalidators.py -> build/bdist.linux-x86_64/wheel/ckanext/example_ivalidators/tests
  copying ckanext/example_theme_docs/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs
  copying ckanext/example_theme_docs/custom_config_setting/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/custom_config_setting
  copying ckanext/example_theme_docs/custom_config_setting/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/custom_config_setting
  copying ckanext/example_theme_docs/custom_emails/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/custom_emails
  copying ckanext/example_theme_docs/custom_emails/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/custom_emails
  copying ckanext/example_theme_docs/custom_emails/test_custom_emails.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/custom_emails
  copying ckanext/example_theme_docs/v01_empty_extension/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v01_empty_extension
  copying ckanext/example_theme_docs/v01_empty_extension/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v01_empty_extension
  copying ckanext/example_theme_docs/v02_empty_template/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v02_empty_template
  copying ckanext/example_theme_docs/v02_empty_template/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v02_empty_template
  copying ckanext/example_theme_docs/v03_jinja/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v03_jinja
  copying ckanext/example_theme_docs/v03_jinja/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v03_jinja
  copying ckanext/example_theme_docs/v04_ckan_extends/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v04_ckan_extends
  copying ckanext/example_theme_docs/v04_ckan_extends/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v04_ckan_extends
  copying ckanext/example_theme_docs/v05_block/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v05_block
  copying ckanext/example_theme_docs/v05_block/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v05_block
  copying ckanext/example_theme_docs/v06_super/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v06_super
  copying ckanext/example_theme_docs/v06_super/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v06_super
  copying ckanext/example_theme_docs/v07_helper_function/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v07_helper_function
  copying ckanext/example_theme_docs/v07_helper_function/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v07_helper_function
  copying ckanext/example_theme_docs/v08_custom_helper_function/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v08_custom_helper_function
  copying ckanext/example_theme_docs/v08_custom_helper_function/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v08_custom_helper_function
  copying ckanext/example_theme_docs/v09_snippet/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v09_snippet
  copying ckanext/example_theme_docs/v09_snippet/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v09_snippet
  copying ckanext/example_theme_docs/v10_custom_snippet/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v10_custom_snippet
  copying ckanext/example_theme_docs/v10_custom_snippet/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v10_custom_snippet
  copying ckanext/example_theme_docs/v11_HTML_and_CSS/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v11_HTML_and_CSS
  copying ckanext/example_theme_docs/v11_HTML_and_CSS/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v11_HTML_and_CSS
  copying ckanext/example_theme_docs/v12_extra_public_dir/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v12_extra_public_dir
  copying ckanext/example_theme_docs/v12_extra_public_dir/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v12_extra_public_dir
  copying ckanext/example_theme_docs/v13_custom_css/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v13_custom_css
  copying ckanext/example_theme_docs/v13_custom_css/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v13_custom_css
  copying ckanext/example_theme_docs/v14_more_custom_css/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v14_more_custom_css
  copying ckanext/example_theme_docs/v14_more_custom_css/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v14_more_custom_css
  copying ckanext/example_theme_docs/v15_webassets/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v15_webassets
  copying ckanext/example_theme_docs/v15_webassets/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v15_webassets
  copying ckanext/example_theme_docs/v16_initialize_a_javascript_module/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v16_initialize_a_javascript_module
  copying ckanext/example_theme_docs/v16_initialize_a_javascript_module/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v16_initialize_a_javascript_module
  copying ckanext/example_theme_docs/v17_popover/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v17_popover
  copying ckanext/example_theme_docs/v17_popover/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v17_popover
  copying ckanext/example_theme_docs/v18_snippet_api/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v18_snippet_api
  copying ckanext/example_theme_docs/v18_snippet_api/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v18_snippet_api
  copying ckanext/example_theme_docs/v19_01_error/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v19_01_error
  copying ckanext/example_theme_docs/v19_01_error/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v19_01_error
  copying ckanext/example_theme_docs/v19_02_error_handling/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v19_02_error_handling
  copying ckanext/example_theme_docs/v19_02_error_handling/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v19_02_error_handling
  copying ckanext/example_theme_docs/v20_pubsub/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v20_pubsub
  copying ckanext/example_theme_docs/v20_pubsub/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v20_pubsub
  copying ckanext/example_theme_docs/v21_custom_jquery_plugin/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v21_custom_jquery_plugin
  copying ckanext/example_theme_docs/v21_custom_jquery_plugin/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v21_custom_jquery_plugin
  copying ckanext/example_theme_docs/v22_webassets/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v22_webassets
  copying ckanext/example_theme_docs/v22_webassets/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/example_theme_docs/v22_webassets
  copying ckanext/expire_api_token/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/expire_api_token
  copying ckanext/expire_api_token/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/expire_api_token
  copying ckanext/expire_api_token/templates/user/api_tokens.html -> build/bdist.linux-x86_64/wheel/ckanext/expire_api_token/templates/user
  copying ckanext/expire_api_token/templates/user/snippets/api_token_list.html -> build/bdist.linux-x86_64/wheel/ckanext/expire_api_token/templates/user/snippets
  copying ckanext/expire_api_token/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/expire_api_token/tests
  copying ckanext/expire_api_token/tests/test_plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/expire_api_token/tests
  copying ckanext/imageview/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/imageview
  copying ckanext/imageview/config_declaration.yaml -> build/bdist.linux-x86_64/wheel/ckanext/imageview
  copying ckanext/imageview/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/imageview
  copying ckanext/imageview/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/imageview/tests
  copying ckanext/imageview/tests/test_view.py -> build/bdist.linux-x86_64/wheel/ckanext/imageview/tests
  copying ckanext/imageview/theme/templates/image_form.html -> build/bdist.linux-x86_64/wheel/ckanext/imageview/theme/templates
  copying ckanext/imageview/theme/templates/image_view.html -> build/bdist.linux-x86_64/wheel/ckanext/imageview/theme/templates
  copying ckanext/multilingual/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/multilingual
  copying ckanext/multilingual/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/multilingual
  copying ckanext/multilingual/tests/test_multilingual_plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/multilingual/tests
  copying ckanext/reclineview/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/reclineview
  copying ckanext/reclineview/config_declaration.yaml -> build/bdist.linux-x86_64/wheel/ckanext/reclineview
  copying ckanext/reclineview/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/reclineview
  copying ckanext/reclineview/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/tests
  copying ckanext/reclineview/tests/test_view.py -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/tests
  copying ckanext/reclineview/theme/public/recline_view.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public
  copying ckanext/reclineview/theme/public/recline_view.min.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public
  copying ckanext/reclineview/theme/public/resource.config -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public
  copying ckanext/reclineview/theme/public/webassets.yml -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public
  copying ckanext/reclineview/theme/public/widget.recordcount.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public
  copying ckanext/reclineview/theme/public/widget.recordcount.min.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public
  copying ckanext/reclineview/theme/public/css/recline.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/css
  copying ckanext/reclineview/theme/public/css/recline.min.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/css
  copying ckanext/reclineview/theme/public/img/ajaxload-circle.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/img
  copying ckanext/reclineview/theme/public/vendor/backbone/1.0.0/backbone.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/backbone/1.0.0
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/css/bootstrap-theme.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/css
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/css/bootstrap.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/css
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts/glyphicons-halflings-regular.eot -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts/glyphicons-halflings-regular.svg -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts/glyphicons-halflings-regular.ttf -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts/glyphicons-halflings-regular.woff -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts
  copying ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/js/bootstrap.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/js
  copying ckanext/reclineview/theme/public/vendor/ckan.js/ckan.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/ckan.js
  copying ckanext/reclineview/theme/public/vendor/flot/excanvas.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/flot
  copying ckanext/reclineview/theme/public/vendor/flot/excanvas.min.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/flot
  copying ckanext/reclineview/theme/public/vendor/flot/jquery.flot.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/flot
  copying ckanext/reclineview/theme/public/vendor/flot/jquery.flot.time.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/flot
  copying ckanext/reclineview/theme/public/vendor/flotr2/flotr2.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/flotr2
  copying ckanext/reclineview/theme/public/vendor/flotr2/flotr2.min.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/flotr2
  copying ckanext/reclineview/theme/public/vendor/jquery/1.7.1/jquery.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/jquery/1.7.1
  copying ckanext/reclineview/theme/public/vendor/jquery/1.7.1/jquery.min.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/jquery/1.7.1
  copying ckanext/reclineview/theme/public/vendor/json/json2.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/json
  copying ckanext/reclineview/theme/public/vendor/json/json2.min.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/json
  copying ckanext/reclineview/theme/public/vendor/leaflet.markercluster/MarkerCluster.Default.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/leaflet.markercluster
  copying ckanext/reclineview/theme/public/vendor/leaflet.markercluster/MarkerCluster.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/leaflet.markercluster
  copying ckanext/reclineview/theme/public/vendor/leaflet.markercluster/leaflet.markercluster-src.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/leaflet.markercluster
  copying ckanext/reclineview/theme/public/vendor/leaflet.markercluster/leaflet.markercluster.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/leaflet.markercluster
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/leaflet-src.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/leaflet.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/leaflet.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/layers-2x.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/layers.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/marker-icon-2x.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/marker-icon.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images
  copying ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/marker-shadow.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images
  copying ckanext/reclineview/theme/public/vendor/moment/2.0.0/moment.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/moment/2.0.0
  copying ckanext/reclineview/theme/public/vendor/mustache/0.5.0-dev/mustache.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/mustache/0.5.0-dev
  copying ckanext/reclineview/theme/public/vendor/mustache/0.5.0-dev/mustache.min.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/mustache/0.5.0-dev
  copying ckanext/reclineview/theme/public/vendor/recline/flot.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/recline
  copying ckanext/reclineview/theme/public/vendor/recline/map.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/recline
  copying ckanext/reclineview/theme/public/vendor/recline/recline.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/recline
  copying ckanext/reclineview/theme/public/vendor/recline/recline.dataset.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/recline
  copying ckanext/reclineview/theme/public/vendor/recline/recline.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/recline
  copying ckanext/reclineview/theme/public/vendor/recline/slickgrid.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/recline
  copying ckanext/reclineview/theme/public/vendor/showdown/20120615/showdown.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/showdown/20120615
  copying ckanext/reclineview/theme/public/vendor/showdown/20120615/showdown.min.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/showdown/20120615
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/MIT-LICENSE.txt -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/README.md -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/jquery-1.7.min.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/jquery-ui-1.8.16.custom.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/jquery.event.drag-2.2.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/jquery.event.drop-2.2.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick-default-theme.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.core.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.dataview.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.editors.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.formatters.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.grid.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.grid.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.groupitemmetadataprovider.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.remotemodel.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls/slick.columnpicker.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls/slick.columnpicker.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls/slick.pager.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls/slick.pager.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/jquery-ui-1.8.16.custom.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_flat_0_aaaaaa_40x100.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_flat_75_ffffff_40x100.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_55_fbf9ee_1x400.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_65_ffffff_1x400.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_75_dadada_1x400.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_75_e6e6e6_1x400.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_95_fef1ec_1x400.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_highlight-soft_75_cccccc_1x100.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_222222_256x240.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_2e83ff_256x240.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_454545_256x240.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_888888_256x240.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_cd0a0a_256x240.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/actions.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/ajax-loader-small.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/arrow_redo.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/arrow_right_peppermint.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/arrow_right_spearmint.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/arrow_undo.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/bullet_blue.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/bullet_star.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/bullet_toggle_minus.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/bullet_toggle_plus.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/calendar.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/collapse.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/comment_yellow.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/down.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/drag-handle.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/editor-helper-bg.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/expand.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/header-bg.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/header-columns-bg.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/header-columns-over-bg.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/help.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/info.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/listview.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/pencil.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/row-over-bg.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/sort-asc.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/sort-asc.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/sort-desc.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/sort-desc.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/stripes.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/tag_red.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/tick.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/user_identity.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/user_identity_plus.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.autotooltips.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.cellcopymanager.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.cellrangedecorator.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.cellrangeselector.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.cellselectionmodel.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.checkboxselectcolumn.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.headerbuttons.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.headerbuttons.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.headermenu.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.headermenu.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.rowmovemanager.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.rowselectionmodel.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins
  copying ckanext/reclineview/theme/public/vendor/timeline/LICENSE -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/timeline
  copying ckanext/reclineview/theme/public/vendor/timeline/README -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/timeline
  copying ckanext/reclineview/theme/public/vendor/timeline/css/loading.gif -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/timeline/css
  copying ckanext/reclineview/theme/public/vendor/timeline/css/timeline.css -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/timeline/css
  copying ckanext/reclineview/theme/public/vendor/timeline/css/timeline.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/timeline/css
  copying ckanext/reclineview/theme/public/vendor/timeline/css/timeline@2x.png -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/timeline/css
  copying ckanext/reclineview/theme/public/vendor/timeline/js/timeline.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/timeline/js
  copying ckanext/reclineview/theme/public/vendor/underscore.deferred/0.4.0/underscore.deferred.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/underscore.deferred/0.4.0
  copying ckanext/reclineview/theme/public/vendor/underscore.deferred/0.4.0/underscore.deferred.min.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/underscore.deferred/0.4.0
  copying ckanext/reclineview/theme/public/vendor/underscore/1.4.4/underscore.js -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/public/vendor/underscore/1.4.4
  copying ckanext/reclineview/theme/templates/recline_graph_form.html -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/templates
  copying ckanext/reclineview/theme/templates/recline_map_form.html -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/templates
  copying ckanext/reclineview/theme/templates/recline_view.html -> build/bdist.linux-x86_64/wheel/ckanext/reclineview/theme/templates
  copying ckanext/resourceproxy/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/resourceproxy
  copying ckanext/resourceproxy/blueprint.py -> build/bdist.linux-x86_64/wheel/ckanext/resourceproxy
  copying ckanext/resourceproxy/config_declaration.yaml -> build/bdist.linux-x86_64/wheel/ckanext/resourceproxy
  copying ckanext/resourceproxy/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/resourceproxy
  copying ckanext/resourceproxy/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/resourceproxy/tests
  copying ckanext/resourceproxy/tests/test_proxy.py -> build/bdist.linux-x86_64/wheel/ckanext/resourceproxy/tests
  copying ckanext/stats/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/stats
  copying ckanext/stats/blueprint.py -> build/bdist.linux-x86_64/wheel/ckanext/stats
  copying ckanext/stats/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/stats
  copying ckanext/stats/stats.py -> build/bdist.linux-x86_64/wheel/ckanext/stats
  copying ckanext/stats/public/.gitignore -> build/bdist.linux-x86_64/wheel/ckanext/stats/public
  copying ckanext/stats/public/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/stats/public
  copying ckanext/stats/public/ckanext/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/stats/public/ckanext
  copying ckanext/stats/public/ckanext/stats/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/stats/public/ckanext/stats
  copying ckanext/stats/public/ckanext/stats/resource.config -> build/bdist.linux-x86_64/wheel/ckanext/stats/public/ckanext/stats
  copying ckanext/stats/public/ckanext/stats/webassets.yml -> build/bdist.linux-x86_64/wheel/ckanext/stats/public/ckanext/stats
  copying ckanext/stats/public/ckanext/stats/css/stats.css -> build/bdist.linux-x86_64/wheel/ckanext/stats/public/ckanext/stats/css
  copying ckanext/stats/public/ckanext/stats/javascript/modules/plot.js -> build/bdist.linux-x86_64/wheel/ckanext/stats/public/ckanext/stats/javascript/modules
  copying ckanext/stats/public/ckanext/stats/javascript/modules/stats-nav.js -> build/bdist.linux-x86_64/wheel/ckanext/stats/public/ckanext/stats/javascript/modules
  copying ckanext/stats/public/ckanext/stats/test/index.html -> build/bdist.linux-x86_64/wheel/ckanext/stats/public/ckanext/stats/test
  copying ckanext/stats/public/ckanext/stats/test/fixtures/table.html -> build/bdist.linux-x86_64/wheel/ckanext/stats/public/ckanext/stats/test/fixtures
  copying ckanext/stats/public/ckanext/stats/test/spec/modules/plot.spec.js -> build/bdist.linux-x86_64/wheel/ckanext/stats/public/ckanext/stats/test/spec/modules
  copying ckanext/stats/public/ckanext/stats/test/spec/modules/stats-nav.spec.js -> build/bdist.linux-x86_64/wheel/ckanext/stats/public/ckanext/stats/test/spec/modules
  copying ckanext/stats/public/ckanext/stats/vendor/excanvas.js -> build/bdist.linux-x86_64/wheel/ckanext/stats/public/ckanext/stats/vendor
  copying ckanext/stats/public/ckanext/stats/vendor/jquery.flot.js -> build/bdist.linux-x86_64/wheel/ckanext/stats/public/ckanext/stats/vendor
  copying ckanext/stats/templates/ckanext/stats/index.html -> build/bdist.linux-x86_64/wheel/ckanext/stats/templates/ckanext/stats
  copying ckanext/stats/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/stats/tests
  copying ckanext/stats/tests/test_stats_lib.py -> build/bdist.linux-x86_64/wheel/ckanext/stats/tests
  copying ckanext/stats/tests/test_stats_plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/stats/tests
  copying ckanext/textview/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/textview
  copying ckanext/textview/config_declaration.yaml -> build/bdist.linux-x86_64/wheel/ckanext/textview
  copying ckanext/textview/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/textview
  copying ckanext/textview/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/textview/tests
  copying ckanext/textview/tests/test_view.py -> build/bdist.linux-x86_64/wheel/ckanext/textview/tests
  copying ckanext/textview/theme/public/LICENSE -> build/bdist.linux-x86_64/wheel/ckanext/textview/theme/public
  copying ckanext/textview/theme/public/resource.config -> build/bdist.linux-x86_64/wheel/ckanext/textview/theme/public
  copying ckanext/textview/theme/public/text_view.js -> build/bdist.linux-x86_64/wheel/ckanext/textview/theme/public
  copying ckanext/textview/theme/public/webassets.yml -> build/bdist.linux-x86_64/wheel/ckanext/textview/theme/public
  copying ckanext/textview/theme/public/css/text.css -> build/bdist.linux-x86_64/wheel/ckanext/textview/theme/public/css
  copying ckanext/textview/theme/public/styles/a11y-light.css -> build/bdist.linux-x86_64/wheel/ckanext/textview/theme/public/styles
  copying ckanext/textview/theme/public/vendor/highlight.js -> build/bdist.linux-x86_64/wheel/ckanext/textview/theme/public/vendor
  copying ckanext/textview/theme/templates/text_form.html -> build/bdist.linux-x86_64/wheel/ckanext/textview/theme/templates
  copying ckanext/textview/theme/templates/text_view.html -> build/bdist.linux-x86_64/wheel/ckanext/textview/theme/templates
  copying ckanext/videoview/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/videoview
  copying ckanext/videoview/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/videoview
  copying ckanext/videoview/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/videoview/tests
  copying ckanext/videoview/tests/test_view.py -> build/bdist.linux-x86_64/wheel/ckanext/videoview/tests
  copying ckanext/videoview/theme/templates/video_form.html -> build/bdist.linux-x86_64/wheel/ckanext/videoview/theme/templates
  copying ckanext/videoview/theme/templates/video_view.html -> build/bdist.linux-x86_64/wheel/ckanext/videoview/theme/templates
  copying ckanext/webpageview/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/webpageview
  copying ckanext/webpageview/plugin.py -> build/bdist.linux-x86_64/wheel/ckanext/webpageview
  copying ckanext/webpageview/tests/__init__.py -> build/bdist.linux-x86_64/wheel/ckanext/webpageview/tests
  copying ckanext/webpageview/tests/test_view.py -> build/bdist.linux-x86_64/wheel/ckanext/webpageview/tests
  copying ckanext/webpageview/theme/templates/webpage_form.html -> build/bdist.linux-x86_64/wheel/ckanext/webpageview/theme/templates
  copying ckanext/webpageview/theme/templates/webpage_view.html -> build/bdist.linux-x86_64/wheel/ckanext/webpageview/theme/templates
  running install_egg_info
  Copying ckan.egg-info to build/bdist.linux-x86_64/wheel/ckan-2.10.4-py3.12.egg-info
  Installing build/bdist.linux-x86_64/wheel/ckan-2.10.4-py3.12-nspkg.pth
  running install_scripts
  creating build/bdist.linux-x86_64/wheel/ckan-2.10.4.dist-info/WHEEL
  creating '/builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir/pip-wheel-1qzbz286/.tmp-9zt2lrys/ckan-2.10.4-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it
  adding 'ckan-2.10.4-py3.12-nspkg.pth'
  adding 'ckan/__init__.py'
  adding 'ckan/authz.py'
  adding 'ckan/common.py'
  adding 'ckan/exceptions.py'
  adding 'ckan/cli/__init__.py'
  adding 'ckan/cli/asset.py'
  adding 'ckan/cli/clean.py'
  adding 'ckan/cli/cli.py'
  adding 'ckan/cli/config.py'
  adding 'ckan/cli/config_tool.py'
  adding 'ckan/cli/dataset.py'
  adding 'ckan/cli/db.py'
  adding 'ckan/cli/generate.py'
  adding 'ckan/cli/jobs.py'
  adding 'ckan/cli/notify.py'
  adding 'ckan/cli/plugin_info.py'
  adding 'ckan/cli/profile.py'
  adding 'ckan/cli/sass.py'
  adding 'ckan/cli/search_index.py'
  adding 'ckan/cli/server.py'
  adding 'ckan/cli/shell.py'
  adding 'ckan/cli/sysadmin.py'
  adding 'ckan/cli/tracking.py'
  adding 'ckan/cli/translation.py'
  adding 'ckan/cli/user.py'
  adding 'ckan/cli/views.py'
  adding 'ckan/config/__init__.py'
  adding 'ckan/config/config_declaration.yaml'
  adding 'ckan/config/deployment.ini_tmpl'
  adding 'ckan/config/environment.py'
  adding 'ckan/config/resource_formats.json'
  adding 'ckan/config/who.ini'
  adding 'ckan/config/declaration/__init__.py'
  adding 'ckan/config/declaration/describe.py'
  adding 'ckan/config/declaration/key.py'
  adding 'ckan/config/declaration/load.py'
  adding 'ckan/config/declaration/option.py'
  adding 'ckan/config/declaration/serialize.py'
  adding 'ckan/config/declaration/utils.py'
  adding 'ckan/config/middleware/__init__.py'
  adding 'ckan/config/middleware/common_middleware.py'
  adding 'ckan/config/middleware/flask_app.py'
  adding 'ckan/config/solr/schema.xml'
  adding 'ckan/i18n/__init__.py'
  adding 'ckan/i18n/ckan.pot'
  adding 'ckan/i18n/am/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/am/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/ar/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/ar/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/bg/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/bg/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/bs/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/bs/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/ca/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/ca/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/cs_CZ/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/cs_CZ/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/da_DK/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/da_DK/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/de/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/de/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/el/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/el/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/en_AU/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/en_AU/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/en_GB/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/en_GB/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/es/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/es/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/es_AR/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/es_AR/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/eu/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/eu/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/fa_IR/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/fa_IR/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/fi/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/fi/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/fr/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/fr/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/gl/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/gl/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/he/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/he/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/hr/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/hr/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/hu/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/hu/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/id/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/id/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/is/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/is/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/it/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/it/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/ja/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/ja/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/km/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/km/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/ko_KR/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/ko_KR/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/lt/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/lt/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/lv/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/lv/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/mk/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/mk/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/mn_MN/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/mn_MN/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/my_MM/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/my_MM/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/nb_NO/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/nb_NO/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/ne/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/ne/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/nl/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/nl/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/no/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/no/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/pl/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/pl/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/pt_BR/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/pt_BR/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/pt_PT/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/pt_PT/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/ro/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/ro/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/ru/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/ru/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/sk/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/sk/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/sl/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/sl/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/sq/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/sq/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/sr/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/sr/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/sr_Latn/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/sr_Latn/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/sv/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/sv/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/th/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/th/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/tl/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/tl/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/tr/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/tr/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/uk/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/uk/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/uk_UA/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/uk_UA/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/vi/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/vi/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/zh_Hans_CN/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/zh_Hans_CN/LC_MESSAGES/ckan.po'
  adding 'ckan/i18n/zh_Hant_TW/LC_MESSAGES/ckan.mo'
  adding 'ckan/i18n/zh_Hant_TW/LC_MESSAGES/ckan.po'
  adding 'ckan/lib/__init__.py'
  adding 'ckan/lib/api_token.py'
  adding 'ckan/lib/app_globals.py'
  adding 'ckan/lib/authenticator.py'
  adding 'ckan/lib/base.py'
  adding 'ckan/lib/captcha.py'
  adding 'ckan/lib/cli.py'
  adding 'ckan/lib/config_tool.py'
  adding 'ckan/lib/create_test_data.py'
  adding 'ckan/lib/datapreview.py'
  adding 'ckan/lib/extract.py'
  adding 'ckan/lib/formatters.py'
  adding 'ckan/lib/hash.py'
  adding 'ckan/lib/helpers.py'
  adding 'ckan/lib/i18n.py'
  adding 'ckan/lib/io.py'
  adding 'ckan/lib/jinja_extensions.py'
  adding 'ckan/lib/jobs.py'
  adding 'ckan/lib/lazyjson.py'
  adding 'ckan/lib/mailer.py'
  adding 'ckan/lib/maintain.py'
  adding 'ckan/lib/munge.py'
  adding 'ckan/lib/pagination.py'
  adding 'ckan/lib/plugins.py'
  adding 'ckan/lib/redis.py'
  adding 'ckan/lib/signals.py'
  adding 'ckan/lib/uploader.py'
  adding 'ckan/lib/webassets_tools.py'
  adding 'ckan/lib/dictization/__init__.py'
  adding 'ckan/lib/dictization/model_dictize.py'
  adding 'ckan/lib/dictization/model_save.py'
  adding 'ckan/lib/navl/__init__.py'
  adding 'ckan/lib/navl/dictization_functions.py'
  adding 'ckan/lib/navl/validators.py'
  adding 'ckan/lib/search/__init__.py'
  adding 'ckan/lib/search/common.py'
  adding 'ckan/lib/search/index.py'
  adding 'ckan/lib/search/query.py'
  adding 'ckan/logic/__init__.py'
  adding 'ckan/logic/converters.py'
  adding 'ckan/logic/schema.py'
  adding 'ckan/logic/validators.py'
  adding 'ckan/logic/action/__init__.py'
  adding 'ckan/logic/action/create.py'
  adding 'ckan/logic/action/delete.py'
  adding 'ckan/logic/action/get.py'
  adding 'ckan/logic/action/patch.py'
  adding 'ckan/logic/action/update.py'
  adding 'ckan/logic/auth/__init__.py'
  adding 'ckan/logic/auth/create.py'
  adding 'ckan/logic/auth/delete.py'
  adding 'ckan/logic/auth/get.py'
  adding 'ckan/logic/auth/patch.py'
  adding 'ckan/logic/auth/update.py'
  adding 'ckan/migration/README'
  adding 'ckan/migration/__init__.py'
  adding 'ckan/migration/alembic.ini'
  adding 'ckan/migration/env.py'
  adding 'ckan/migration/migrate_package_activity.py'
  adding 'ckan/migration/revision_legacy_code.py'
  adding 'ckan/migration/versions/001_103676e0a497_create_existing_tables.py'
  adding 'ckan/migration/versions/002_86fdd8c54775_add_author_and_maintainer.py'
  adding 'ckan/migration/versions/003_f22b4f5241a5_add_user_object.py'
  adding 'ckan/migration/versions/004_f92ee205e46d_add_group_object.py'
  adding 'ckan/migration/versions/005_12c2232c15f5_add_authorization_tables.py'
  adding 'ckan/migration/versions/006_c83955e7acb6_add_ratings.py'
  adding 'ckan/migration/versions/007_1928d4af1cda_add_system_roles.py'
  adding 'ckan/migration/versions/008_e8283ffb257e_update_vdm_ids.py'
  adding 'ckan/migration/versions/009_b739a48de5c4_add_creation_timestamps.py'
  adding 'ckan/migration/versions/010_a6f13bf14d0c_add_user_about.py'
  adding 'ckan/migration/versions/011_866f6370b4ac_add_package_search_vector.py'
  adding 'ckan/migration/versions/012_e5ca33a5d445_add_resources.py'
  adding 'ckan/migration/versions/013_8a3a5af39797_add_hash.py'
  adding 'ckan/migration/versions/014_93519b684820_hash_2.py'
  adding 'ckan/migration/versions/015_6d8ffebcaf54_remove_state_object.py'
  adding 'ckan/migration/versions/016_37ada738328e_uuids_everywhere.py'
  adding 'ckan/migration/versions/017_1250b2ff3e36_add_pkg_relationships.py'
  adding 'ckan/migration/versions/018_05a0778051ca_adjust_licenses.py'
  adding 'ckan/migration/versions/019_b2eb6f34a638_pkg_relationships_state.py'
  adding 'ckan/migration/versions/020_69a0b0efc609_add_changeset.py'
  adding 'ckan/migration/versions/021_765143af2ba3_postgresql_upgrade_sql.py'
  adding 'ckan/migration/versions/022_7b324ca6c0dc_add_group_extras.py'
  adding 'ckan/migration/versions/023_87fdd05f0744_add_harvesting.py'
  adding 'ckan/migration/versions/024_12981fe12484_add_harvested_document.py'
  adding 'ckan/migration/versions/025_b581622ad327_add_authorization_groups.py'
  adding 'ckan/migration/versions/026_3615b25af443_authorization_group_user_pk.py'
  adding 'ckan/migration/versions/027_11e5745c6fc9_adjust_harvester.py'
  adding 'ckan/migration/versions/028_cdd68fe9ba21_drop_harvest_source_status.py'
  adding 'ckan/migration/versions/029_1bfdf4240915_version_groups.py'
  adding 'ckan/migration/versions/030_b16cbf164c8a_additional_user_attributes.py'
  adding 'ckan/migration/versions/031_1b05245167d6_move_openid_to_new_field.py'
  adding 'ckan/migration/versions/032_d89e0731422d_add_extra_info_field_to_resources.py'
  adding 'ckan/migration/versions/033_6da92ef2df15_auth_group_user_id_add_conditional.py'
  adding 'ckan/migration/versions/034_6c600693af5b_resource_group_table.py'
  adding 'ckan/migration/versions/035_81148ccebd6c_harvesting_doc_versioning.py'
  adding 'ckan/migration/versions/036_ecaa8b38782f_lockdown_roles.py'
  adding 'ckan/migration/versions/037_edcf3b8c3c1b_role_anon_editor.py'
  adding 'ckan/migration/versions/038_fd6622e3d964_delete_migration_tables.py'
  adding 'ckan/migration/versions/039_cca459c76d45_add_expired_id_and_dates.py'
  adding 'ckan/migration/versions/040_500a08f4818e_reset_key_on_user.py'
  adding 'ckan/migration/versions/041_6817d4e3bdc3_resource_new_fields.py'
  adding 'ckan/migration/versions/042_da65e2877034_user_revision_indexes.py'
  adding 'ckan/migration/versions/043_bd38cd6502b2_drop_postgres_search.py'
  adding 'ckan/migration/versions/044_4190eeeb8d73_add_task_status.py'
  adding 'ckan/migration/versions/045_54e3f155d945_user_name_unique.py'
  adding 'ckan/migration/versions/046_b69e9b80396f_drop_changesets.py'
  adding 'ckan/migration/versions/047_883a7c406926_rename_package_group_member.py'
  adding 'ckan/migration/versions/048_4a7011172b3f_add_activity_streams_tables.py'
  adding 'ckan/migration/versions/049_e0c06c2177b5_add_group_approval_status.py'
  adding 'ckan/migration/versions/050_01a6b058cb7f_term_translation_table.py'
  adding 'ckan/migration/versions/051_a4fb0d85ced6_add_tag_vocabulary.py'
  adding 'ckan/migration/versions/052_ba693d64c6d7_update_member_capacities.py'
  adding 'ckan/migration/versions/053_9d051a099097_add_group_logo.py'
  adding 'ckan/migration/versions/054_da21b38da4db_add_resource_created_date.py'
  adding 'ckan/migration/versions/055_048f7db947bf_update_user_and_activity_detail.py'
  adding 'ckan/migration/versions/056_11af3215ae89_add_related_table.py'
  adding 'ckan/migration/versions/057_660a5aae527e_tracking.py'
  adding 'ckan/migration/versions/058_bd36d1826a5d_add_follower_tables.py'
  adding 'ckan/migration/versions/059_9291bb46f352_add_related_count_and_flag.py'
  adding 'ckan/migration/versions/060_31ad11c518fc_add_system_info_table.py'
  adding 'ckan/migration/versions/061_338d460bc460_add_follower_group_table.py'
  adding 'ckan/migration/versions/062_6deb2bbab394_add_dashboard_table.py'
  adding 'ckan/migration/versions/063_8b633852cb7a_org_changes.py'
  adding 'ckan/migration/versions/064_4f8becd4919a_add_email_last_sent_column.py'
  adding 'ckan/migration/versions/065_1fab0bc6439e_add_email_notifications_preference.py'
  adding 'ckan/migration/versions/066_ad16b3bd8cb6_default_package_type.py'
  adding 'ckan/migration/versions/067_266c110eafec_turn_extras_to_strings.py'
  adding 'ckan/migration/versions/068_e33a5f2b2a84_add_package_extras_index.py'
  adding 'ckan/migration/versions/069_e7524c675cdb_resource_url_and_metadata_modified.py'
  adding 'ckan/migration/versions/070_cfb544112fa7_add_activity_and_resource_indexes.py'
  adding 'ckan/migration/versions/071_c16f081ef73a_add_state_column_to_user_table.py'
  adding 'ckan/migration/versions/072_08dcb9233ad7_add_resource_view.py'
  adding 'ckan/migration/versions/073_011f51208be3_update_resource_view_resource_id_.py'
  adding 'ckan/migration/versions/074_a4ca55f0f45e_remove_resource_groups.py'
  adding 'ckan/migration/versions/075_9cdc88c8896a_rename_view_plugins.py'
  adding 'ckan/migration/versions/076_59995aa965c0_rename_view_plugins_2.py'
  adding 'ckan/migration/versions/077_51171a04d86d_add_revisions_to_system_info.py'
  adding 'ckan/migration/versions/078_ae821876532a_remove_old_authz_model.py'
  adding 'ckan/migration/versions/079_e0177a15d2c9_resource_revision_index.py'
  adding 'ckan/migration/versions/080_8224d872c64f_continuity_id_indexes.py'
  adding 'ckan/migration/versions/081_a64cf4a79182_set_datastore_active.py'
  adding 'ckan/migration/versions/082_8ea886d0ede4_create_index_creator_user_id.py'
  adding 'ckan/migration/versions/083_f98d8fa2a7f7_remove_related_items.py'
  adding 'ckan/migration/versions/084_d85ce5783688_add_metadata_created.py'
  adding 'ckan/migration/versions/085_f9bf3d5c4b4d_adjust_activity_timestamps.py'
  adding 'ckan/migration/versions/086_19663581b3bb_drop_openid_column.py'
  adding 'ckan/migration/versions/087_ff1b303cab77_remove_old_authorization_tables.py'
  adding 'ckan/migration/versions/088_3537d5420e0e_delete_extrase_which_are_deleted_state.py'
  adding 'ckan/migration/versions/089_23c92480926e_package_activity_migration_check.py'
  adding 'ckan/migration/versions/090_980dcd44de4b_delete_migrate_version_table.py'
  adding 'ckan/migration/versions/091_0ffc0b277141_group_extra_group_id_index.py'
  adding 'ckan/migration/versions/092_01afcadbd8c0_resource_package_id_index.py'
  adding 'ckan/migration/versions/093_7f70d7d15445_remove_activity_revision_id.py'
  adding 'ckan/migration/versions/094_588d7cfb9a41_add_metadata_modified_to_resource_table.py'
  adding 'ckan/migration/versions/095_9fadda785b07_drop_continuity_id_constraints.py'
  adding 'ckan/migration/versions/096_19ddad52b500_add_plugin_extras_to_user_table.py'
  adding 'ckan/migration/versions/097_f789f233226e_add_package_member_table.py'
  adding 'ckan/migration/versions/098_ddbd0a9a4489_add_image_url_field_to_user_table.py'
  adding 'ckan/migration/versions/099_3ae4b17ed66d_create_apitoken_table.py'
  adding 'ckan/migration/versions/100_ccd38ad5fced_remove_package_tag_revision_foreign_key.py'
  adding 'ckan/migration/versions/101_d111f446733b_add_last_active_column_in_user_table.py'
  adding 'ckan/migration/versions/102_ff13667243ed_create_conditinal_index_on_user.py'
  adding 'ckan/migration/versions/103_353aaf2701f0_add_plugin_data_to_package_table.py'
  adding 'ckan/migration/versions/104_9f33a0280c51_resource_view_resource_id_index.py'
  adding 'ckan/migration/versions/__init__.py'
  adding 'ckan/model/__init__.py'
  adding 'ckan/model/api_token.py'
  adding 'ckan/model/base.py'
  adding 'ckan/model/core.py'
  adding 'ckan/model/dashboard.py'
  adding 'ckan/model/domain_object.py'
  adding 'ckan/model/follower.py'
  adding 'ckan/model/group.py'
  adding 'ckan/model/group_extra.py'
  adding 'ckan/model/license.py'
  adding 'ckan/model/meta.py'
  adding 'ckan/model/misc.py'
  adding 'ckan/model/modification.py'
  adding 'ckan/model/package.py'
  adding 'ckan/model/package_extra.py'
  adding 'ckan/model/package_relationship.py'
  adding 'ckan/model/resource.py'
  adding 'ckan/model/resource_view.py'
  adding 'ckan/model/system.py'
  adding 'ckan/model/system_info.py'
  adding 'ckan/model/tag.py'
  adding 'ckan/model/task_status.py'
  adding 'ckan/model/term_translation.py'
  adding 'ckan/model/tracking.py'
  adding 'ckan/model/types.py'
  adding 'ckan/model/user.py'
  adding 'ckan/model/vocabulary.py'
  adding 'ckan/plugins/__init__.py'
  adding 'ckan/plugins/blanket.py'
  adding 'ckan/plugins/core.py'
  adding 'ckan/plugins/interfaces.py'
  adding 'ckan/plugins/toolkit.py'
  adding 'ckan/plugins/toolkit_sphinx_extension.py'
  adding 'ckan/public/base/.gitignore'
  adding 'ckan/public/base/css/.gitignore'
  adding 'ckan/public/base/css/main-rtl.css'
  adding 'ckan/public/base/css/main.css'
  adding 'ckan/public/base/css/webassets.yml'
  adding 'ckan/public/base/i18n/.gitignore'
  adding 'ckan/public/base/i18n/am.js'
  adding 'ckan/public/base/i18n/ar.js'
  adding 'ckan/public/base/i18n/bg.js'
  adding 'ckan/public/base/i18n/bs.js'
  adding 'ckan/public/base/i18n/ca.js'
  adding 'ckan/public/base/i18n/cs_CZ.js'
  adding 'ckan/public/base/i18n/da_DK.js'
  adding 'ckan/public/base/i18n/de.js'
  adding 'ckan/public/base/i18n/el.js'
  adding 'ckan/public/base/i18n/en_AU.js'
  adding 'ckan/public/base/i18n/en_GB.js'
  adding 'ckan/public/base/i18n/es.js'
  adding 'ckan/public/base/i18n/es_AR.js'
  adding 'ckan/public/base/i18n/eu.js'
  adding 'ckan/public/base/i18n/fa_IR.js'
  adding 'ckan/public/base/i18n/fi.js'
  adding 'ckan/public/base/i18n/fr.js'
  adding 'ckan/public/base/i18n/gl.js'
  adding 'ckan/public/base/i18n/he.js'
  adding 'ckan/public/base/i18n/hr.js'
  adding 'ckan/public/base/i18n/hu.js'
  adding 'ckan/public/base/i18n/id.js'
  adding 'ckan/public/base/i18n/is.js'
  adding 'ckan/public/base/i18n/it.js'
  adding 'ckan/public/base/i18n/ja.js'
  adding 'ckan/public/base/i18n/km.js'
  adding 'ckan/public/base/i18n/ko_KR.js'
  adding 'ckan/public/base/i18n/lt.js'
  adding 'ckan/public/base/i18n/lv.js'
  adding 'ckan/public/base/i18n/mk.js'
  adding 'ckan/public/base/i18n/mn_MN.js'
  adding 'ckan/public/base/i18n/my_MM.js'
  adding 'ckan/public/base/i18n/nb_NO.js'
  adding 'ckan/public/base/i18n/ne.js'
  adding 'ckan/public/base/i18n/nl.js'
  adding 'ckan/public/base/i18n/no.js'
  adding 'ckan/public/base/i18n/pl.js'
  adding 'ckan/public/base/i18n/pt_BR.js'
  adding 'ckan/public/base/i18n/pt_PT.js'
  adding 'ckan/public/base/i18n/ro.js'
  adding 'ckan/public/base/i18n/ru.js'
  adding 'ckan/public/base/i18n/sk.js'
  adding 'ckan/public/base/i18n/sl.js'
  adding 'ckan/public/base/i18n/sq.js'
  adding 'ckan/public/base/i18n/sr.js'
  adding 'ckan/public/base/i18n/sr_Latn.js'
  adding 'ckan/public/base/i18n/sv.js'
  adding 'ckan/public/base/i18n/th.js'
  adding 'ckan/public/base/i18n/tl.js'
  adding 'ckan/public/base/i18n/tr.js'
  adding 'ckan/public/base/i18n/uk.js'
  adding 'ckan/public/base/i18n/uk_UA.js'
  adding 'ckan/public/base/i18n/vi.js'
  adding 'ckan/public/base/i18n/zh_Hans_CN.js'
  adding 'ckan/public/base/i18n/zh_Hant_TW.js'
  adding 'ckan/public/base/images/background-tag-ie7.png'
  adding 'ckan/public/base/images/background-tag.png'
  adding 'ckan/public/base/images/background-tile.png'
  adding 'ckan/public/base/images/bg.png'
  adding 'ckan/public/base/images/breadcrumb-slash-ie7.png'
  adding 'ckan/public/base/images/ckan-logo-footer.png'
  adding 'ckan/public/base/images/ckan-logo-white.svg'
  adding 'ckan/public/base/images/ckan-logo.png'
  adding 'ckan/public/base/images/ckan-logo.svg'
  adding 'ckan/public/base/images/ckan.ico'
  adding 'ckan/public/base/images/dashboard-followee-related.png'
  adding 'ckan/public/base/images/editing.png'
  adding 'ckan/public/base/images/full-width-nav-right.png'
  adding 'ckan/public/base/images/icon-search-27x26.png'
  adding 'ckan/public/base/images/nav-active.png'
  adding 'ckan/public/base/images/nav.png'
  adding 'ckan/public/base/images/od_80x15_blue.png'
  adding 'ckan/public/base/images/placeholder-200x125.png'
  adding 'ckan/public/base/images/placeholder-420x220.png'
  adding 'ckan/public/base/images/placeholder-680x400.png'
  adding 'ckan/public/base/images/placeholder-application.png'
  adding 'ckan/public/base/images/placeholder-group.png'
  adding 'ckan/public/base/images/placeholder-image.png'
  adding 'ckan/public/base/images/placeholder-organization.png'
  adding 'ckan/public/base/images/placeholder-user.png'
  adding 'ckan/public/base/images/sprite-resource-icons.png'
  adding 'ckan/public/base/images/table-seperator.png'
  adding 'ckan/public/base/javascript/apply-html-class.js'
  adding 'ckan/public/base/javascript/client.js'
  adding 'ckan/public/base/javascript/i18n.js'
  adding 'ckan/public/base/javascript/main.js'
  adding 'ckan/public/base/javascript/module.js'
  adding 'ckan/public/base/javascript/notify.js'
  adding 'ckan/public/base/javascript/pubsub.js'
  adding 'ckan/public/base/javascript/resource.config'
  adding 'ckan/public/base/javascript/sandbox.js'
  adding 'ckan/public/base/javascript/tracking.js'
  adding 'ckan/public/base/javascript/view-filters.js'
  adding 'ckan/public/base/javascript/webassets.yml'
  adding 'ckan/public/base/javascript/modules/api-info.js'
  adding 'ckan/public/base/javascript/modules/autocomplete.js'
  adding 'ckan/public/base/javascript/modules/basic-form.js'
  adding 'ckan/public/base/javascript/modules/confirm-action.js'
  adding 'ckan/public/base/javascript/modules/copy-into-buffer.js'
  adding 'ckan/public/base/javascript/modules/custom-fields.js'
  adding 'ckan/public/base/javascript/modules/data-viewer.js'
  adding 'ckan/public/base/javascript/modules/dataset-visibility.js'
  adding 'ckan/public/base/javascript/modules/follow.js'
  adding 'ckan/public/base/javascript/modules/followers-counter.js'
  adding 'ckan/public/base/javascript/modules/image-upload.js'
  adding 'ckan/public/base/javascript/modules/media-grid.js'
  adding 'ckan/public/base/javascript/modules/metadata-button.js'
  adding 'ckan/public/base/javascript/modules/resource-form.js'
  adding 'ckan/public/base/javascript/modules/resource-reorder.js'
  adding 'ckan/public/base/javascript/modules/resource-upload-field.js'
  adding 'ckan/public/base/javascript/modules/resource-view-embed.js'
  adding 'ckan/public/base/javascript/modules/resource-view-filters-form.js'
  adding 'ckan/public/base/javascript/modules/resource-view-filters.js'
  adding 'ckan/public/base/javascript/modules/resource-view-reorder.js'
  adding 'ckan/public/base/javascript/modules/select-switch.js'
  adding 'ckan/public/base/javascript/modules/slug-preview.js'
  adding 'ckan/public/base/javascript/modules/table-selectable-rows.js'
  adding 'ckan/public/base/javascript/modules/table-toggle-more.js'
  adding 'ckan/public/base/javascript/plugins/jquery.date-helpers.js'
  adding 'ckan/public/base/javascript/plugins/jquery.form-warning.js'
  adding 'ckan/public/base/javascript/plugins/jquery.images-loaded.js'
  adding 'ckan/public/base/javascript/plugins/jquery.inherit.js'
  adding 'ckan/public/base/javascript/plugins/jquery.masonry.js'
  adding 'ckan/public/base/javascript/plugins/jquery.proxy-all.js'
  adding 'ckan/public/base/javascript/plugins/jquery.slug-preview.js'
  adding 'ckan/public/base/javascript/plugins/jquery.slug.js'
  adding 'ckan/public/base/javascript/plugins/jquery.truncator.js'
  adding 'ckan/public/base/javascript/plugins/jquery.url-helpers.js'
  adding 'ckan/public/base/scss/_alerts.scss'
  adding 'ckan/public/base/scss/_bootstrap-rtl.scss'
  adding 'ckan/public/base/scss/_bootstrap-variables.scss'
  adding 'ckan/public/base/scss/_bootstrap.scss'
  adding 'ckan/public/base/scss/_buttons.scss'
  adding 'ckan/public/base/scss/_ckan-rtl.scss'
  adding 'ckan/public/base/scss/_ckan.scss'
  adding 'ckan/public/base/scss/_custom.scss'
  adding 'ckan/public/base/scss/_dashboard.scss'
  adding 'ckan/public/base/scss/_datapusher.scss'
  adding 'ckan/public/base/scss/_dataset.scss'
  adding 'ckan/public/base/scss/_footer.scss'
  adding 'ckan/public/base/scss/_forms.scss'
  adding 'ckan/public/base/scss/_group.scss'
  adding 'ckan/public/base/scss/_homepage.scss'
  adding 'ckan/public/base/scss/_input-groups.scss'
  adding 'ckan/public/base/scss/_layout.scss'
  adding 'ckan/public/base/scss/_masthead.scss'
  adding 'ckan/public/base/scss/_media.scss'
  adding 'ckan/public/base/scss/_mixins.scss'
  adding 'ckan/public/base/scss/_module.scss'
  adding 'ckan/public/base/scss/_nav.scss'
  adding 'ckan/public/base/scss/_profile.scss'
  adding 'ckan/public/base/scss/_prose.scss'
  adding 'ckan/public/base/scss/_resource-icons.scss'
  adding 'ckan/public/base/scss/_resource-view.scss'
  adding 'ckan/public/base/scss/_search.scss'
  adding 'ckan/public/base/scss/_tables.scss'
  adding 'ckan/public/base/scss/_toolbar.scss'
  adding 'ckan/public/base/scss/_variables.scss'
  adding 'ckan/public/base/scss/main-rtl.scss'
  adding 'ckan/public/base/scss/main.scss'
  adding 'ckan/public/base/vendor/bootstrap.js'
  adding 'ckan/public/base/vendor/jed.js'
  adding 'ckan/public/base/vendor/jquery.js'
  adding 'ckan/public/base/vendor/jquery.ui.core.js'
  adding 'ckan/public/base/vendor/jquery.ui.mouse.js'
  adding 'ckan/public/base/vendor/jquery.ui.sortable.js'
  adding 'ckan/public/base/vendor/jquery.ui.widget.js'
  adding 'ckan/public/base/vendor/moment-with-locales.js'
  adding 'ckan/public/base/vendor/popper.js'
  adding 'ckan/public/base/vendor/popperjs.js'
  adding 'ckan/public/base/vendor/purify.js'
  adding 'ckan/public/base/vendor/qs.js'
  adding 'ckan/public/base/vendor/resource.config'
  adding 'ckan/public/base/vendor/webassets.yml'
  adding 'ckan/public/base/vendor/bootstrap/css/bootstrap-theme.min.css.map'
  adding 'ckan/public/base/vendor/bootstrap/css/bootstrap.min.css.map'
  adding 'ckan/public/base/vendor/bootstrap/js/alert.js'
  adding 'ckan/public/base/vendor/bootstrap/js/alert.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/base-component.js'
  adding 'ckan/public/base/vendor/bootstrap/js/base-component.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/bootstrap.bundle.js'
  adding 'ckan/public/base/vendor/bootstrap/js/bootstrap.bundle.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/bootstrap.bundle.min.js'
  adding 'ckan/public/base/vendor/bootstrap/js/bootstrap.bundle.min.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/bootstrap.esm.js'
  adding 'ckan/public/base/vendor/bootstrap/js/bootstrap.esm.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/bootstrap.esm.min.js'
  adding 'ckan/public/base/vendor/bootstrap/js/bootstrap.esm.min.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/bootstrap.js'
  adding 'ckan/public/base/vendor/bootstrap/js/bootstrap.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/bootstrap.min.js'
  adding 'ckan/public/base/vendor/bootstrap/js/bootstrap.min.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/button.js'
  adding 'ckan/public/base/vendor/bootstrap/js/button.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/carousel.js'
  adding 'ckan/public/base/vendor/bootstrap/js/carousel.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/collapse.js'
  adding 'ckan/public/base/vendor/bootstrap/js/collapse.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/dropdown.js'
  adding 'ckan/public/base/vendor/bootstrap/js/dropdown.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/modal.js'
  adding 'ckan/public/base/vendor/bootstrap/js/modal.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/offcanvas.js'
  adding 'ckan/public/base/vendor/bootstrap/js/offcanvas.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/popover.js'
  adding 'ckan/public/base/vendor/bootstrap/js/popover.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/scrollspy.js'
  adding 'ckan/public/base/vendor/bootstrap/js/scrollspy.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/tab.js'
  adding 'ckan/public/base/vendor/bootstrap/js/tab.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/toast.js'
  adding 'ckan/public/base/vendor/bootstrap/js/toast.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/tooltip.js'
  adding 'ckan/public/base/vendor/bootstrap/js/tooltip.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/dom/data.js'
  adding 'ckan/public/base/vendor/bootstrap/js/dom/data.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/dom/event-handler.js'
  adding 'ckan/public/base/vendor/bootstrap/js/dom/event-handler.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/dom/manipulator.js'
  adding 'ckan/public/base/vendor/bootstrap/js/dom/manipulator.js.map'
  adding 'ckan/public/base/vendor/bootstrap/js/dom/selector-engine.js'
  adding 'ckan/public/base/vendor/bootstrap/js/dom/selector-engine.js.map'
  adding 'ckan/public/base/vendor/bootstrap/scss/_accordion.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_alert.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_badge.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_breadcrumb.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_button-group.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_buttons.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_card.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_carousel.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_close.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_containers.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_dropdown.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_forms.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_functions.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_grid.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_helpers.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_images.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_list-group.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_mixins.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_modal.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_nav.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_navbar.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_offcanvas.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_pagination.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_placeholders.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_popover.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_progress.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_reboot.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_root.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_spinners.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_tables.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_toasts.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_tooltip.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_transitions.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_type.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_utilities.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/_variables.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/bootstrap-grid.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/bootstrap-reboot.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/bootstrap-utilities.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/bootstrap.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/forms/_floating-labels.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/forms/_form-check.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/forms/_form-control.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/forms/_form-range.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/forms/_form-select.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/forms/_form-text.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/forms/_input-group.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/forms/_labels.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/forms/_validation.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/helpers/_clearfix.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/helpers/_colored-links.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/helpers/_position.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/helpers/_ratio.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/helpers/_stacks.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/helpers/_stretched-link.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/helpers/_text-truncation.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/helpers/_visually-hidden.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/helpers/_vr.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_alert.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_backdrop.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_border-radius.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_box-shadow.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_breakpoints.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_buttons.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_caret.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_clearfix.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_color-scheme.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_container.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_deprecate.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_forms.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_gradients.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_grid.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_image.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_list-group.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_lists.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_pagination.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_reset-text.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_resize.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_table-variants.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_text-truncate.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_transition.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_utilities.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/mixins/_visually-hidden.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/utilities/_api.scss'
  adding 'ckan/public/base/vendor/bootstrap/scss/vendor/_rfs.scss'
  adding 'ckan/public/base/vendor/fontawesome-free/css/all.css'
  adding 'ckan/public/base/vendor/fontawesome-free/webfonts/fa-brands-400.ttf'
  adding 'ckan/public/base/vendor/fontawesome-free/webfonts/fa-brands-400.woff2'
  adding 'ckan/public/base/vendor/fontawesome-free/webfonts/fa-regular-400.ttf'
  adding 'ckan/public/base/vendor/fontawesome-free/webfonts/fa-regular-400.woff2'
  adding 'ckan/public/base/vendor/fontawesome-free/webfonts/fa-solid-900.ttf'
  adding 'ckan/public/base/vendor/fontawesome-free/webfonts/fa-solid-900.woff2'
  adding 'ckan/public/base/vendor/fontawesome-free/webfonts/fa-v4compatibility.ttf'
  adding 'ckan/public/base/vendor/fontawesome-free/webfonts/fa-v4compatibility.woff2'
  adding 'ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-audio.js'
  adding 'ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-image.js'
  adding 'ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-process.js'
  adding 'ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-ui.js'
  adding 'ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-validate.js'
  adding 'ckan/public/base/vendor/jquery-fileupload/jquery.fileupload-video.js'
  adding 'ckan/public/base/vendor/jquery-fileupload/jquery.fileupload.js'
  adding 'ckan/public/base/vendor/jquery-fileupload/jquery.iframe-transport.js'
  adding 'ckan/public/base/vendor/select2/.gitignore'
  adding 'ckan/public/base/vendor/select2/CONTRIBUTING.md'
  adding 'ckan/public/base/vendor/select2/LICENSE'
  adding 'ckan/public/base/vendor/select2/README.md'
  adding 'ckan/public/base/vendor/select2/bower.json'
  adding 'ckan/public/base/vendor/select2/component.json'
  adding 'ckan/public/base/vendor/select2/composer.json'
  adding 'ckan/public/base/vendor/select2/package.json'
  adding 'ckan/public/base/vendor/select2/release.sh'
  adding 'ckan/public/base/vendor/select2/select2-bootstrap.css'
  adding 'ckan/public/base/vendor/select2/select2-spinner.gif'
  adding 'ckan/public/base/vendor/select2/select2.css'
  adding 'ckan/public/base/vendor/select2/select2.jquery.json'
  adding 'ckan/public/base/vendor/select2/select2.js'
  adding 'ckan/public/base/vendor/select2/select2.png'
  adding 'ckan/public/base/vendor/select2/select2_locale_ar.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_az.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_bg.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_ca.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_cs.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_da.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_de.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_el.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_en.js.template'
  adding 'ckan/public/base/vendor/select2/select2_locale_es.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_et.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_eu.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_fa.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_fi.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_fr.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_gl.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_he.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_hr.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_hu.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_id.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_is.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_it.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_ja.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_ka.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_ko.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_lt.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_lv.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_mk.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_ms.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_nb.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_nl.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_pl.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_pt-BR.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_pt-PT.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_ro.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_rs.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_ru.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_sk.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_sv.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_th.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_tr.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_ug-CN.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_uk.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_vi.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_zh-CN.js'
  adding 'ckan/public/base/vendor/select2/select2_locale_zh-TW.js'
  adding 'ckan/public/base/vendor/select2/select2x2.png'
  adding 'ckan/public-bs3/robots.txt'
  adding 'ckan/public-bs3/base/.gitignore'
  adding 'ckan/public-bs3/base/css/.gitignore'
  adding 'ckan/public-bs3/base/css/main-rtl.css'
  adding 'ckan/public-bs3/base/css/main.css'
  adding 'ckan/public-bs3/base/css/webassets.yml'
  adding 'ckan/public-bs3/base/i18n/.gitignore'
  adding 'ckan/public-bs3/base/images/background-tag-ie7.png'
  adding 'ckan/public-bs3/base/images/background-tag.png'
  adding 'ckan/public-bs3/base/images/background-tile.png'
  adding 'ckan/public-bs3/base/images/bg.png'
  adding 'ckan/public-bs3/base/images/breadcrumb-slash-ie7.png'
  adding 'ckan/public-bs3/base/images/ckan-logo-footer.png'
  adding 'ckan/public-bs3/base/images/ckan-logo-white.svg'
  adding 'ckan/public-bs3/base/images/ckan-logo.png'
  adding 'ckan/public-bs3/base/images/ckan-logo.svg'
  adding 'ckan/public-bs3/base/images/ckan.ico'
  adding 'ckan/public-bs3/base/images/dashboard-followee-related.png'
  adding 'ckan/public-bs3/base/images/dotted.png'
  adding 'ckan/public-bs3/base/images/editing.png'
  adding 'ckan/public-bs3/base/images/full-width-nav-right.png'
  adding 'ckan/public-bs3/base/images/icon-search-27x26.png'
  adding 'ckan/public-bs3/base/images/nav-active.png'
  adding 'ckan/public-bs3/base/images/nav.png'
  adding 'ckan/public-bs3/base/images/od_80x15_blue.png'
  adding 'ckan/public-bs3/base/images/placeholder-200x125.png'
  adding 'ckan/public-bs3/base/images/placeholder-420x220.png'
  adding 'ckan/public-bs3/base/images/placeholder-680x400.png'
  adding 'ckan/public-bs3/base/images/placeholder-application.png'
  adding 'ckan/public-bs3/base/images/placeholder-group.png'
  adding 'ckan/public-bs3/base/images/placeholder-image.png'
  adding 'ckan/public-bs3/base/images/placeholder-organization.png'
  adding 'ckan/public-bs3/base/images/placeholder-user.png'
  adding 'ckan/public-bs3/base/images/sprite-ckan-icons.png'
  adding 'ckan/public-bs3/base/images/sprite-resource-icons.png'
  adding 'ckan/public-bs3/base/images/table-seperator.png'
  adding 'ckan/public-bs3/base/javascript/apply-html-class.js'
  adding 'ckan/public-bs3/base/javascript/client.js'
  adding 'ckan/public-bs3/base/javascript/i18n.js'
  adding 'ckan/public-bs3/base/javascript/main.js'
  adding 'ckan/public-bs3/base/javascript/module.js'
  adding 'ckan/public-bs3/base/javascript/notify.js'
  adding 'ckan/public-bs3/base/javascript/pubsub.js'
  adding 'ckan/public-bs3/base/javascript/resource.config'
  adding 'ckan/public-bs3/base/javascript/sandbox.js'
  adding 'ckan/public-bs3/base/javascript/tracking.js'
  adding 'ckan/public-bs3/base/javascript/view-filters.js'
  adding 'ckan/public-bs3/base/javascript/webassets.yml'
  adding 'ckan/public-bs3/base/javascript/modules/api-info.js'
  adding 'ckan/public-bs3/base/javascript/modules/autocomplete.js'
  adding 'ckan/public-bs3/base/javascript/modules/basic-form.js'
  adding 'ckan/public-bs3/base/javascript/modules/confirm-action.js'
  adding 'ckan/public-bs3/base/javascript/modules/copy-into-buffer.js'
  adding 'ckan/public-bs3/base/javascript/modules/custom-fields.js'
  adding 'ckan/public-bs3/base/javascript/modules/data-viewer.js'
  adding 'ckan/public-bs3/base/javascript/modules/dataset-visibility.js'
  adding 'ckan/public-bs3/base/javascript/modules/follow.js'
  adding 'ckan/public-bs3/base/javascript/modules/followers-counter.js'
  adding 'ckan/public-bs3/base/javascript/modules/image-upload.js'
  adding 'ckan/public-bs3/base/javascript/modules/media-grid.js'
  adding 'ckan/public-bs3/base/javascript/modules/metadata-button.js'
  adding 'ckan/public-bs3/base/javascript/modules/resource-form.js'
  adding 'ckan/public-bs3/base/javascript/modules/resource-reorder.js'
  adding 'ckan/public-bs3/base/javascript/modules/resource-upload-field.js'
  adding 'ckan/public-bs3/base/javascript/modules/resource-view-embed.js'
  adding 'ckan/public-bs3/base/javascript/modules/resource-view-filters-form.js'
  adding 'ckan/public-bs3/base/javascript/modules/resource-view-filters.js'
  adding 'ckan/public-bs3/base/javascript/modules/resource-view-reorder.js'
  adding 'ckan/public-bs3/base/javascript/modules/select-switch.js'
  adding 'ckan/public-bs3/base/javascript/modules/slug-preview.js'
  adding 'ckan/public-bs3/base/javascript/modules/table-selectable-rows.js'
  adding 'ckan/public-bs3/base/javascript/modules/table-toggle-more.js'
  adding 'ckan/public-bs3/base/javascript/plugins/jquery.date-helpers.js'
  adding 'ckan/public-bs3/base/javascript/plugins/jquery.form-warning.js'
  adding 'ckan/public-bs3/base/javascript/plugins/jquery.images-loaded.js'
  adding 'ckan/public-bs3/base/javascript/plugins/jquery.inherit.js'
  adding 'ckan/public-bs3/base/javascript/plugins/jquery.masonry.js'
  adding 'ckan/public-bs3/base/javascript/plugins/jquery.proxy-all.js'
  adding 'ckan/public-bs3/base/javascript/plugins/jquery.slug-preview.js'
  adding 'ckan/public-bs3/base/javascript/plugins/jquery.slug.js'
  adding 'ckan/public-bs3/base/javascript/plugins/jquery.truncator.js'
  adding 'ckan/public-bs3/base/javascript/plugins/jquery.url-helpers.js'
  adding 'ckan/public-bs3/base/scss/_alerts.scss'
  adding 'ckan/public-bs3/base/scss/_bootstrap-rtl.scss'
  adding 'ckan/public-bs3/base/scss/_bootstrap-variables.scss'
  adding 'ckan/public-bs3/base/scss/_bootstrap.scss'
  adding 'ckan/public-bs3/base/scss/_ckan-rtl.scss'
  adding 'ckan/public-bs3/base/scss/_ckan.scss'
  adding 'ckan/public-bs3/base/scss/_custom.scss'
  adding 'ckan/public-bs3/base/scss/_dashboard.scss'
  adding 'ckan/public-bs3/base/scss/_datapusher.scss'
  adding 'ckan/public-bs3/base/scss/_dataset.scss'
  adding 'ckan/public-bs3/base/scss/_dropdown.scss'
  adding 'ckan/public-bs3/base/scss/_footer.scss'
  adding 'ckan/public-bs3/base/scss/_forms.scss'
  adding 'ckan/public-bs3/base/scss/_group.scss'
  adding 'ckan/public-bs3/base/scss/_homepage.scss'
  adding 'ckan/public-bs3/base/scss/_icons.scss'
  adding 'ckan/public-bs3/base/scss/_input-groups.scss'
  adding 'ckan/public-bs3/base/scss/_layout.scss'
  adding 'ckan/public-bs3/base/scss/_masthead.scss'
  adding 'ckan/public-bs3/base/scss/_media.scss'
  adding 'ckan/public-bs3/base/scss/_mixins.scss'
  adding 'ckan/public-bs3/base/scss/_module.scss'
  adding 'ckan/public-bs3/base/scss/_nav.scss'
  adding 'ckan/public-bs3/base/scss/_profile.scss'
  adding 'ckan/public-bs3/base/scss/_prose.scss'
  adding 'ckan/public-bs3/base/scss/_resource-view.scss'
  adding 'ckan/public-bs3/base/scss/_search.scss'
  adding 'ckan/public-bs3/base/scss/_tables.scss'
  adding 'ckan/public-bs3/base/scss/_toolbar.scss'
  adding 'ckan/public-bs3/base/scss/_variables.scss'
  adding 'ckan/public-bs3/base/scss/main-rtl.scss'
  adding 'ckan/public-bs3/base/scss/main.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap.js'
  adding 'ckan/public-bs3/base/vendor/jed.js'
  adding 'ckan/public-bs3/base/vendor/jquery.js'
  adding 'ckan/public-bs3/base/vendor/jquery.ui.core.js'
  adding 'ckan/public-bs3/base/vendor/jquery.ui.mouse.js'
  adding 'ckan/public-bs3/base/vendor/jquery.ui.sortable.js'
  adding 'ckan/public-bs3/base/vendor/jquery.ui.widget.js'
  adding 'ckan/public-bs3/base/vendor/moment-with-locales.js'
  adding 'ckan/public-bs3/base/vendor/qs.js'
  adding 'ckan/public-bs3/base/vendor/resource.config'
  adding 'ckan/public-bs3/base/vendor/webassets.yml'
  adding 'ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.eot'
  adding 'ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.svg'
  adding 'ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.ttf'
  adding 'ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.woff'
  adding 'ckan/public-bs3/base/vendor/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.woff2'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap-sprockets.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/affix.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/alert.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/button.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/carousel.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/collapse.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/dropdown.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/modal.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/popover.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/scrollspy.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/tab.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/tooltip.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/javascripts/bootstrap/transition.js'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/_bootstrap-compass.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/_bootstrap-mincer.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/_bootstrap-sprockets.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/_bootstrap.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_alerts.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_badges.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_breadcrumbs.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_button-groups.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_buttons.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_carousel.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_close.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_code.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_component-animations.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_dropdowns.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_forms.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_glyphicons.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_grid.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_input-groups.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_jumbotron.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_labels.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_list-group.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_media.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_mixins.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_modals.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_navbar.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_navs.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_normalize.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_pager.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_pagination.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_panels.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_popovers.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_print.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_progress-bars.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_responsive-embed.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_responsive-utilities.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_scaffolding.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_tables.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_theme.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_thumbnails.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_tooltip.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_type.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_utilities.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_variables.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/_wells.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_alerts.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_background-variant.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_border-radius.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_buttons.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_center-block.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_clearfix.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_forms.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_gradients.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_grid-framework.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_grid.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_hide-text.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_image.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_labels.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_list-group.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_nav-divider.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_nav-vertical-align.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_opacity.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_pagination.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_panels.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_progress-bar.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_reset-filter.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_reset-text.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_resize.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_responsive-visibility.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_size.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_tab-focus.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_table-row.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_text-emphasis.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_text-overflow.scss'
  adding 'ckan/public-bs3/base/vendor/bootstrap/stylesheets/bootstrap/mixins/_vendor-prefixes.scss'
  adding 'ckan/public-bs3/base/vendor/fontawesome-free/css/all.css'
  adding 'ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-brands-400.ttf'
  adding 'ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-brands-400.woff2'
  adding 'ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-regular-400.ttf'
  adding 'ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-regular-400.woff2'
  adding 'ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-solid-900.ttf'
  adding 'ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-solid-900.woff2'
  adding 'ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-v4compatibility.ttf'
  adding 'ckan/public-bs3/base/vendor/fontawesome-free/webfonts/fa-v4compatibility.woff2'
  adding 'ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-audio.js'
  adding 'ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-image.js'
  adding 'ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-process.js'
  adding 'ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-ui.js'
  adding 'ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-validate.js'
  adding 'ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload-video.js'
  adding 'ckan/public-bs3/base/vendor/jquery-fileupload/jquery.fileupload.js'
  adding 'ckan/public-bs3/base/vendor/jquery-fileupload/jquery.iframe-transport.js'
  adding 'ckan/public-bs3/base/vendor/select2/.gitignore'
  adding 'ckan/public-bs3/base/vendor/select2/CONTRIBUTING.md'
  adding 'ckan/public-bs3/base/vendor/select2/LICENSE'
  adding 'ckan/public-bs3/base/vendor/select2/README.md'
  adding 'ckan/public-bs3/base/vendor/select2/bower.json'
  adding 'ckan/public-bs3/base/vendor/select2/component.json'
  adding 'ckan/public-bs3/base/vendor/select2/composer.json'
  adding 'ckan/public-bs3/base/vendor/select2/package.json'
  adding 'ckan/public-bs3/base/vendor/select2/release.sh'
  adding 'ckan/public-bs3/base/vendor/select2/select2-bootstrap.css'
  adding 'ckan/public-bs3/base/vendor/select2/select2-spinner.gif'
  adding 'ckan/public-bs3/base/vendor/select2/select2.css'
  adding 'ckan/public-bs3/base/vendor/select2/select2.jquery.json'
  adding 'ckan/public-bs3/base/vendor/select2/select2.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2.png'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_ar.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_az.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_bg.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_ca.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_cs.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_da.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_de.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_el.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_en.js.template'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_es.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_et.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_eu.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_fa.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_fi.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_fr.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_gl.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_he.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_hr.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_hu.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_id.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_is.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_it.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_ja.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_ka.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_ko.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_lt.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_lv.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_mk.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_ms.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_nb.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_nl.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_pl.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_pt-BR.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_pt-PT.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_ro.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_rs.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_ru.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_sk.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_sv.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_th.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_tr.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_ug-CN.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_uk.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_vi.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_zh-CN.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2_locale_zh-TW.js'
  adding 'ckan/public-bs3/base/vendor/select2/select2x2.png'
  adding 'ckan/templates/base.html'
  adding 'ckan/templates/error_document_template.html'
  adding 'ckan/templates/footer.html'
  adding 'ckan/templates/header.html'
  adding 'ckan/templates/page.html'
  adding 'ckan/templates/activity_streams/activity_stream_email_notifications.text'
  adding 'ckan/templates/admin/base.html'
  adding 'ckan/templates/admin/config.html'
  adding 'ckan/templates/admin/confirm_reset.html'
  adding 'ckan/templates/admin/index.html'
  adding 'ckan/templates/admin/trash.html'
  adding 'ckan/templates/admin/snippets/confirm_delete.html'
  adding 'ckan/templates/admin/snippets/data_type.html'
  adding 'ckan/templates/ajax_snippets/custom_fields.html'
  adding 'ckan/templates/ajax_snippets/follow_button.html'
  adding 'ckan/templates/dataviewer/base.html'
  adding 'ckan/templates/development/primer.html'
  adding 'ckan/templates/development/snippets/actions.html'
  adding 'ckan/templates/development/snippets/breadcrumb.html'
  adding 'ckan/templates/development/snippets/context.html'
  adding 'ckan/templates/development/snippets/facet.html'
  adding 'ckan/templates/development/snippets/form.html'
  adding 'ckan/templates/development/snippets/form_stages.html'
  adding 'ckan/templates/development/snippets/list.html'
  adding 'ckan/templates/development/snippets/media_grid.html'
  adding 'ckan/templates/development/snippets/module.html'
  adding 'ckan/templates/development/snippets/nav.html'
  adding 'ckan/templates/development/snippets/page_header.html'
  adding 'ckan/templates/development/snippets/pagination.html'
  adding 'ckan/templates/development/snippets/simple-input.html'
  adding 'ckan/templates/emails/invite_user.txt'
  adding 'ckan/templates/emails/invite_user_subject.txt'
  adding 'ckan/templates/emails/reset_password.txt'
  adding 'ckan/templates/emails/reset_password_subject.txt'
  adding 'ckan/templates/group/about.html'
  adding 'ckan/templates/group/admins.html'
  adding 'ckan/templates/group/base_form_page.html'
  adding 'ckan/templates/group/confirm_delete.html'
  adding 'ckan/templates/group/confirm_delete_member.html'
  adding 'ckan/templates/group/edit.html'
  adding 'ckan/templates/group/edit_base.html'
  adding 'ckan/templates/group/followers.html'
  adding 'ckan/templates/group/index.html'
  adding 'ckan/templates/group/member_new.html'
  adding 'ckan/templates/group/members.html'
  adding 'ckan/templates/group/new.html'
  adding 'ckan/templates/group/new_group_form.html'
  adding 'ckan/templates/group/read.html'
  adding 'ckan/templates/group/read_base.html'
  adding 'ckan/templates/group/snippets/feeds.html'
  adding 'ckan/templates/group/snippets/group_form.html'
  adding 'ckan/templates/group/snippets/group_item.html'
  adding 'ckan/templates/group/snippets/group_list.html'
  adding 'ckan/templates/group/snippets/helper.html'
  adding 'ckan/templates/group/snippets/info.html'
  adding 'ckan/templates/home/about.html'
  adding 'ckan/templates/home/index.html'
  adding 'ckan/templates/home/layout1.html'
  adding 'ckan/templates/home/layout2.html'
  adding 'ckan/templates/home/layout3.html'
  adding 'ckan/templates/home/robots.txt'
  adding 'ckan/templates/home/snippets/about_text.html'
  adding 'ckan/templates/home/snippets/featured_group.html'
  adding 'ckan/templates/home/snippets/featured_organization.html'
  adding 'ckan/templates/home/snippets/promoted.html'
  adding 'ckan/templates/home/snippets/search.html'
  adding 'ckan/templates/home/snippets/stats.html'
  adding 'ckan/templates/macros/autoform.html'
  adding 'ckan/templates/macros/form.html'
  adding 'ckan/templates/macros/form/attributes.html'
  adding 'ckan/templates/macros/form/checkbox.html'
  adding 'ckan/templates/macros/form/custom.html'
  adding 'ckan/templates/macros/form/errors.html'
  adding 'ckan/templates/macros/form/hidden.html'
  adding 'ckan/templates/macros/form/hidden_from_list.html'
  adding 'ckan/templates/macros/form/image_upload.html'
  adding 'ckan/templates/macros/form/info.html'
  adding 'ckan/templates/macros/form/input.html'
  adding 'ckan/templates/macros/form/input_block.html'
  adding 'ckan/templates/macros/form/markdown.html'
  adding 'ckan/templates/macros/form/prepend.html'
  adding 'ckan/templates/macros/form/required_message.html'
  adding 'ckan/templates/macros/form/select.html'
  adding 'ckan/templates/macros/form/textarea.html'
  adding 'ckan/templates/organization/about.html'
  adding 'ckan/templates/organization/admins.html'
  adding 'ckan/templates/organization/base_form_page.html'
  adding 'ckan/templates/organization/bulk_process.html'
  adding 'ckan/templates/organization/confirm_delete.html'
  adding 'ckan/templates/organization/confirm_delete_member.html'
  adding 'ckan/templates/organization/edit.html'
  adding 'ckan/templates/organization/edit_base.html'
  adding 'ckan/templates/organization/index.html'
  adding 'ckan/templates/organization/member_new.html'
  adding 'ckan/templates/organization/members.html'
  adding 'ckan/templates/organization/new.html'
  adding 'ckan/templates/organization/new_organization_form.html'
  adding 'ckan/templates/organization/read.html'
  adding 'ckan/templates/organization/read_base.html'
  adding 'ckan/templates/organization/snippets/feeds.html'
  adding 'ckan/templates/organization/snippets/helper.html'
  adding 'ckan/templates/organization/snippets/organization_form.html'
  adding 'ckan/templates/organization/snippets/organization_item.html'
  adding 'ckan/templates/organization/snippets/organization_list.html'
  adding 'ckan/templates/package/base.html'
  adding 'ckan/templates/package/base_form_page.html'
  adding 'ckan/templates/package/confirm_delete.html'
  adding 'ckan/templates/package/confirm_delete_resource.html'
  adding 'ckan/templates/package/edit.html'
  adding 'ckan/templates/package/edit_base.html'
  adding 'ckan/templates/package/edit_view.html'
  adding 'ckan/templates/package/followers.html'
  adding 'ckan/templates/package/group_list.html'
  adding 'ckan/templates/package/new.html'
  adding 'ckan/templates/package/new_package_form.html'
  adding 'ckan/templates/package/new_resource.html'
  adding 'ckan/templates/package/new_resource_not_draft.html'
  adding 'ckan/templates/package/new_view.html'
  adding 'ckan/templates/package/read.html'
  adding 'ckan/templates/package/read_base.html'
  adding 'ckan/templates/package/resource_edit.html'
  adding 'ckan/templates/package/resource_edit_base.html'
  adding 'ckan/templates/package/resource_read.html'
  adding 'ckan/templates/package/resource_views.html'
  adding 'ckan/templates/package/resources.html'
  adding 'ckan/templates/package/search.html'
  adding 'ckan/templates/package/view_edit_base.html'
  adding 'ckan/templates/package/collaborators/collaborator_new.html'
  adding 'ckan/templates/package/collaborators/collaborators.html'
  adding 'ckan/templates/package/collaborators/confirm_delete.html'
  adding 'ckan/templates/package/snippets/additional_info.html'
  adding 'ckan/templates/package/snippets/cannot_create_package.html'
  adding 'ckan/templates/package/snippets/info.html'
  adding 'ckan/templates/package/snippets/new_package_breadcrumb.html'
  adding 'ckan/templates/package/snippets/package_basic_fields.html'
  adding 'ckan/templates/package/snippets/package_form.html'
  adding 'ckan/templates/package/snippets/package_metadata_fields.html'
  adding 'ckan/templates/package/snippets/resource_edit_form.html'
  adding 'ckan/templates/package/snippets/resource_form.html'
  adding 'ckan/templates/package/snippets/resource_help.html'
  adding 'ckan/templates/package/snippets/resource_info.html'
  adding 'ckan/templates/package/snippets/resource_item.html'
  adding 'ckan/templates/package/snippets/resource_upload_field.html'
  adding 'ckan/templates/package/snippets/resource_view.html'
  adding 'ckan/templates/package/snippets/resource_view_embed.html'
  adding 'ckan/templates/package/snippets/resource_view_filters.html'
  adding 'ckan/templates/package/snippets/resource_views_list.html'
  adding 'ckan/templates/package/snippets/resource_views_list_item.html'
  adding 'ckan/templates/package/snippets/resources.html'
  adding 'ckan/templates/package/snippets/resources_list.html'
  adding 'ckan/templates/package/snippets/stages.html'
  adding 'ckan/templates/package/snippets/tags.html'
  adding 'ckan/templates/package/snippets/view_form.html'
  adding 'ckan/templates/package/snippets/view_form_filters.html'
  adding 'ckan/templates/package/snippets/view_help.html'
  adding 'ckan/templates/revision/__init__.py'
  adding 'ckan/templates/snippets/add_dataset.html'
  adding 'ckan/templates/snippets/additional_info.html'
  adding 'ckan/templates/snippets/context.html'
  adding 'ckan/templates/snippets/csrf_input.html'
  adding 'ckan/templates/snippets/custom_form_fields.html'
  adding 'ckan/templates/snippets/datapusher_status.html'
  adding 'ckan/templates/snippets/disqus_trackback.html'
  adding 'ckan/templates/snippets/facet_list.html'
  adding 'ckan/templates/snippets/follow_button.html'
  adding 'ckan/templates/snippets/group.html'
  adding 'ckan/templates/snippets/group_item.html'
  adding 'ckan/templates/snippets/home_breadcrumb_item.html'
  adding 'ckan/templates/snippets/language_selector.html'
  adding 'ckan/templates/snippets/license.html'
  adding 'ckan/templates/snippets/local_friendly_datetime.html'
  adding 'ckan/templates/snippets/organization.html'
  adding 'ckan/templates/snippets/organization_item.html'
  adding 'ckan/templates/snippets/package_item.html'
  adding 'ckan/templates/snippets/package_list.html'
  adding 'ckan/templates/snippets/popular.html'
  adding 'ckan/templates/snippets/private.html'
  adding 'ckan/templates/snippets/search_form.html'
  adding 'ckan/templates/snippets/search_result_text.html'
  adding 'ckan/templates/snippets/simple_search.html'
  adding 'ckan/templates/snippets/social.html'
  adding 'ckan/templates/snippets/tag_list.html'
  adding 'ckan/templates/snippets/context/dataset.html'
  adding 'ckan/templates/snippets/context/group.html'
  adding 'ckan/templates/snippets/context/user.html'
  adding 'ckan/templates/tests/broken_helper_as_attribute.html'
  adding 'ckan/templates/tests/broken_helper_as_item.html'
  adding 'ckan/templates/tests/flash_messages.html'
  adding 'ckan/templates/tests/helper_as_attribute.html'
  adding 'ckan/templates/tests/helper_as_item.html'
  adding 'ckan/templates/tests/mock_json_resource_preview_template.html'
  adding 'ckan/templates/tests/mock_resource_preview_template.html'
  adding 'ckan/templates/user/api_tokens.html'
  adding 'ckan/templates/user/confirm_delete.html'
  adding 'ckan/templates/user/dashboard.html'
  adding 'ckan/templates/user/dashboard_datasets.html'
  adding 'ckan/templates/user/dashboard_groups.html'
  adding 'ckan/templates/user/dashboard_organizations.html'
  adding 'ckan/templates/user/edit.html'
  adding 'ckan/templates/user/edit_base.html'
  adding 'ckan/templates/user/edit_user_form.html'
  adding 'ckan/templates/user/followers.html'
  adding 'ckan/templates/user/list.html'
  adding 'ckan/templates/user/login.html'
  adding 'ckan/templates/user/logout.html'
  adding 'ckan/templates/user/logout_first.html'
  adding 'ckan/templates/user/new.html'
  adding 'ckan/templates/user/new_user_form.html'
  adding 'ckan/templates/user/perform_reset.html'
  adding 'ckan/templates/user/read.html'
  adding 'ckan/templates/user/read_base.html'
  adding 'ckan/templates/user/request_reset.html'
  adding 'ckan/templates/user/snippets/api_token_list.html'
  adding 'ckan/templates/user/snippets/followers.html'
  adding 'ckan/templates/user/snippets/login_form.html'
  adding 'ckan/templates/user/snippets/placeholder.html'
  adding 'ckan/templates/user/snippets/recaptcha.html'
  adding 'ckan/templates/user/snippets/user_search.html'
  adding 'ckan/templates-bs3/base.html'
  adding 'ckan/templates-bs3/error_document_template.html'
  adding 'ckan/templates-bs3/footer.html'
  adding 'ckan/templates-bs3/header.html'
  adding 'ckan/templates-bs3/page.html'
  adding 'ckan/templates-bs3/admin/base.html'
  adding 'ckan/templates-bs3/admin/config.html'
  adding 'ckan/templates-bs3/admin/confirm_reset.html'
  adding 'ckan/templates-bs3/admin/index.html'
  adding 'ckan/templates-bs3/admin/trash.html'
  adding 'ckan/templates-bs3/admin/snippets/confirm_delete.html'
  adding 'ckan/templates-bs3/admin/snippets/data_type.html'
  adding 'ckan/templates-bs3/ajax_snippets/custom_fields.html'
  adding 'ckan/templates-bs3/ajax_snippets/follow_button.html'
  adding 'ckan/templates-bs3/dataviewer/base.html'
  adding 'ckan/templates-bs3/development/primer.html'
  adding 'ckan/templates-bs3/development/snippets/actions.html'
  adding 'ckan/templates-bs3/development/snippets/breadcrumb.html'
  adding 'ckan/templates-bs3/development/snippets/context.html'
  adding 'ckan/templates-bs3/development/snippets/facet.html'
  adding 'ckan/templates-bs3/development/snippets/form.html'
  adding 'ckan/templates-bs3/development/snippets/form_stages.html'
  adding 'ckan/templates-bs3/development/snippets/list.html'
  adding 'ckan/templates-bs3/development/snippets/media_grid.html'
  adding 'ckan/templates-bs3/development/snippets/module.html'
  adding 'ckan/templates-bs3/development/snippets/nav.html'
  adding 'ckan/templates-bs3/development/snippets/page_header.html'
  adding 'ckan/templates-bs3/development/snippets/pagination.html'
  adding 'ckan/templates-bs3/development/snippets/simple-input.html'
  adding 'ckan/templates-bs3/emails/invite_user.txt'
  adding 'ckan/templates-bs3/emails/invite_user_subject.txt'
  adding 'ckan/templates-bs3/emails/reset_password.txt'
  adding 'ckan/templates-bs3/emails/reset_password_subject.txt'
  adding 'ckan/templates-bs3/group/about.html'
  adding 'ckan/templates-bs3/group/admins.html'
  adding 'ckan/templates-bs3/group/base_form_page.html'
  adding 'ckan/templates-bs3/group/confirm_delete.html'
  adding 'ckan/templates-bs3/group/confirm_delete_member.html'
  adding 'ckan/templates-bs3/group/edit.html'
  adding 'ckan/templates-bs3/group/edit_base.html'
  adding 'ckan/templates-bs3/group/followers.html'
  adding 'ckan/templates-bs3/group/index.html'
  adding 'ckan/templates-bs3/group/member_new.html'
  adding 'ckan/templates-bs3/group/members.html'
  adding 'ckan/templates-bs3/group/new.html'
  adding 'ckan/templates-bs3/group/new_group_form.html'
  adding 'ckan/templates-bs3/group/read.html'
  adding 'ckan/templates-bs3/group/read_base.html'
  adding 'ckan/templates-bs3/group/snippets/feeds.html'
  adding 'ckan/templates-bs3/group/snippets/group_form.html'
  adding 'ckan/templates-bs3/group/snippets/group_item.html'
  adding 'ckan/templates-bs3/group/snippets/group_list.html'
  adding 'ckan/templates-bs3/group/snippets/helper.html'
  adding 'ckan/templates-bs3/group/snippets/info.html'
  adding 'ckan/templates-bs3/home/about.html'
  adding 'ckan/templates-bs3/home/index.html'
  adding 'ckan/templates-bs3/home/layout1.html'
  adding 'ckan/templates-bs3/home/layout2.html'
  adding 'ckan/templates-bs3/home/layout3.html'
  adding 'ckan/templates-bs3/home/snippets/about_text.html'
  adding 'ckan/templates-bs3/home/snippets/featured_group.html'
  adding 'ckan/templates-bs3/home/snippets/featured_organization.html'
  adding 'ckan/templates-bs3/home/snippets/promoted.html'
  adding 'ckan/templates-bs3/home/snippets/search.html'
  adding 'ckan/templates-bs3/home/snippets/stats.html'
  adding 'ckan/templates-bs3/macros/autoform.html'
  adding 'ckan/templates-bs3/macros/form.html'
  adding 'ckan/templates-bs3/organization/about.html'
  adding 'ckan/templates-bs3/organization/admins.html'
  adding 'ckan/templates-bs3/organization/base_form_page.html'
  adding 'ckan/templates-bs3/organization/bulk_process.html'
  adding 'ckan/templates-bs3/organization/confirm_delete.html'
  adding 'ckan/templates-bs3/organization/confirm_delete_member.html'
  adding 'ckan/templates-bs3/organization/edit.html'
  adding 'ckan/templates-bs3/organization/edit_base.html'
  adding 'ckan/templates-bs3/organization/index.html'
  adding 'ckan/templates-bs3/organization/member_new.html'
  adding 'ckan/templates-bs3/organization/members.html'
  adding 'ckan/templates-bs3/organization/new.html'
  adding 'ckan/templates-bs3/organization/new_organization_form.html'
  adding 'ckan/templates-bs3/organization/read.html'
  adding 'ckan/templates-bs3/organization/read_base.html'
  adding 'ckan/templates-bs3/organization/snippets/feeds.html'
  adding 'ckan/templates-bs3/organization/snippets/helper.html'
  adding 'ckan/templates-bs3/organization/snippets/organization_form.html'
  adding 'ckan/templates-bs3/organization/snippets/organization_item.html'
  adding 'ckan/templates-bs3/organization/snippets/organization_list.html'
  adding 'ckan/templates-bs3/package/base.html'
  adding 'ckan/templates-bs3/package/base_form_page.html'
  adding 'ckan/templates-bs3/package/confirm_delete.html'
  adding 'ckan/templates-bs3/package/confirm_delete_resource.html'
  adding 'ckan/templates-bs3/package/edit.html'
  adding 'ckan/templates-bs3/package/edit_base.html'
  adding 'ckan/templates-bs3/package/edit_view.html'
  adding 'ckan/templates-bs3/package/followers.html'
  adding 'ckan/templates-bs3/package/group_list.html'
  adding 'ckan/templates-bs3/package/new.html'
  adding 'ckan/templates-bs3/package/new_package_form.html'
  adding 'ckan/templates-bs3/package/new_resource.html'
  adding 'ckan/templates-bs3/package/new_resource_not_draft.html'
  adding 'ckan/templates-bs3/package/new_view.html'
  adding 'ckan/templates-bs3/package/read.html'
  adding 'ckan/templates-bs3/package/read_base.html'
  adding 'ckan/templates-bs3/package/resource_edit.html'
  adding 'ckan/templates-bs3/package/resource_edit_base.html'
  adding 'ckan/templates-bs3/package/resource_read.html'
  adding 'ckan/templates-bs3/package/resource_views.html'
  adding 'ckan/templates-bs3/package/resources.html'
  adding 'ckan/templates-bs3/package/search.html'
  adding 'ckan/templates-bs3/package/view_edit_base.html'
  adding 'ckan/templates-bs3/package/collaborators/collaborator_new.html'
  adding 'ckan/templates-bs3/package/collaborators/collaborators.html'
  adding 'ckan/templates-bs3/package/snippets/additional_info.html'
  adding 'ckan/templates-bs3/package/snippets/cannot_create_package.html'
  adding 'ckan/templates-bs3/package/snippets/info.html'
  adding 'ckan/templates-bs3/package/snippets/new_package_breadcrumb.html'
  adding 'ckan/templates-bs3/package/snippets/package_basic_fields.html'
  adding 'ckan/templates-bs3/package/snippets/package_form.html'
  adding 'ckan/templates-bs3/package/snippets/package_metadata_fields.html'
  adding 'ckan/templates-bs3/package/snippets/resource_edit_form.html'
  adding 'ckan/templates-bs3/package/snippets/resource_form.html'
  adding 'ckan/templates-bs3/package/snippets/resource_help.html'
  adding 'ckan/templates-bs3/package/snippets/resource_info.html'
  adding 'ckan/templates-bs3/package/snippets/resource_item.html'
  adding 'ckan/templates-bs3/package/snippets/resource_upload_field.html'
  adding 'ckan/templates-bs3/package/snippets/resource_view.html'
  adding 'ckan/templates-bs3/package/snippets/resource_view_embed.html'
  adding 'ckan/templates-bs3/package/snippets/resource_view_filters.html'
  adding 'ckan/templates-bs3/package/snippets/resource_views_list.html'
  adding 'ckan/templates-bs3/package/snippets/resource_views_list_item.html'
  adding 'ckan/templates-bs3/package/snippets/resources.html'
  adding 'ckan/templates-bs3/package/snippets/resources_list.html'
  adding 'ckan/templates-bs3/package/snippets/stages.html'
  adding 'ckan/templates-bs3/package/snippets/tags.html'
  adding 'ckan/templates-bs3/package/snippets/view_form.html'
  adding 'ckan/templates-bs3/package/snippets/view_form_filters.html'
  adding 'ckan/templates-bs3/package/snippets/view_help.html'
  adding 'ckan/templates-bs3/revision/__init__.py'
  adding 'ckan/templates-bs3/snippets/add_dataset.html'
  adding 'ckan/templates-bs3/snippets/additional_info.html'
  adding 'ckan/templates-bs3/snippets/context.html'
  adding 'ckan/templates-bs3/snippets/csrf_input.html'
  adding 'ckan/templates-bs3/snippets/custom_form_fields.html'
  adding 'ckan/templates-bs3/snippets/datapusher_status.html'
  adding 'ckan/templates-bs3/snippets/disqus_trackback.html'
  adding 'ckan/templates-bs3/snippets/facet_list.html'
  adding 'ckan/templates-bs3/snippets/follow_button.html'
  adding 'ckan/templates-bs3/snippets/group.html'
  adding 'ckan/templates-bs3/snippets/group_item.html'
  adding 'ckan/templates-bs3/snippets/home_breadcrumb_item.html'
  adding 'ckan/templates-bs3/snippets/language_selector.html'
  adding 'ckan/templates-bs3/snippets/license.html'
  adding 'ckan/templates-bs3/snippets/local_friendly_datetime.html'
  adding 'ckan/templates-bs3/snippets/organization.html'
  adding 'ckan/templates-bs3/snippets/organization_item.html'
  adding 'ckan/templates-bs3/snippets/package_item.html'
  adding 'ckan/templates-bs3/snippets/package_list.html'
  adding 'ckan/templates-bs3/snippets/popular.html'
  adding 'ckan/templates-bs3/snippets/private.html'
  adding 'ckan/templates-bs3/snippets/search_form.html'
  adding 'ckan/templates-bs3/snippets/search_result_text.html'
  adding 'ckan/templates-bs3/snippets/simple_search.html'
  adding 'ckan/templates-bs3/snippets/social.html'
  adding 'ckan/templates-bs3/snippets/subscribe.html'
  adding 'ckan/templates-bs3/snippets/tag_list.html'
  adding 'ckan/templates-bs3/snippets/context/dataset.html'
  adding 'ckan/templates-bs3/snippets/context/group.html'
  adding 'ckan/templates-bs3/snippets/context/user.html'
  adding 'ckan/templates-bs3/tests/broken_helper_as_attribute.html'
  adding 'ckan/templates-bs3/tests/broken_helper_as_item.html'
  adding 'ckan/templates-bs3/tests/flash_messages.html'
  adding 'ckan/templates-bs3/tests/helper_as_attribute.html'
  adding 'ckan/templates-bs3/tests/helper_as_item.html'
  adding 'ckan/templates-bs3/tests/mock_json_resource_preview_template.html'
  adding 'ckan/templates-bs3/tests/mock_resource_preview_template.html'
  adding 'ckan/templates-bs3/user/api_tokens.html'
  adding 'ckan/templates-bs3/user/dashboard.html'
  adding 'ckan/templates-bs3/user/dashboard_datasets.html'
  adding 'ckan/templates-bs3/user/dashboard_groups.html'
  adding 'ckan/templates-bs3/user/dashboard_organizations.html'
  adding 'ckan/templates-bs3/user/edit.html'
  adding 'ckan/templates-bs3/user/edit_base.html'
  adding 'ckan/templates-bs3/user/edit_user_form.html'
  adding 'ckan/templates-bs3/user/followers.html'
  adding 'ckan/templates-bs3/user/list.html'
  adding 'ckan/templates-bs3/user/login.html'
  adding 'ckan/templates-bs3/user/logout.html'
  adding 'ckan/templates-bs3/user/logout_first.html'
  adding 'ckan/templates-bs3/user/new.html'
  adding 'ckan/templates-bs3/user/new_user_form.html'
  adding 'ckan/templates-bs3/user/perform_reset.html'
  adding 'ckan/templates-bs3/user/read.html'
  adding 'ckan/templates-bs3/user/read_base.html'
  adding 'ckan/templates-bs3/user/request_reset.html'
  adding 'ckan/templates-bs3/user/snippets/api_token_list.html'
  adding 'ckan/templates-bs3/user/snippets/followers.html'
  adding 'ckan/templates-bs3/user/snippets/login_form.html'
  adding 'ckan/templates-bs3/user/snippets/placeholder.html'
  adding 'ckan/templates-bs3/user/snippets/recaptcha.html'
  adding 'ckan/templates-bs3/user/snippets/user_search.html'
  adding 'ckan/tests/__init__.py'
  adding 'ckan/tests/factories.py'
  adding 'ckan/tests/helpers.py'
  adding 'ckan/tests/test_authz.py'
  adding 'ckan/tests/test_coding_standards.py'
  adding 'ckan/tests/test_common.py'
  adding 'ckan/tests/test_factories.py'
  adding 'ckan/tests/test_none_root.py'
  adding 'ckan/tests/test_robots_txt.py'
  adding 'ckan/tests/cli/__init__.py'
  adding 'ckan/tests/cli/test_asset.py'
  adding 'ckan/tests/cli/test_clean.py'
  adding 'ckan/tests/cli/test_cli.py'
  adding 'ckan/tests/cli/test_config.py'
  adding 'ckan/tests/cli/test_config_tool.py'
  adding 'ckan/tests/cli/test_db.py'
  adding 'ckan/tests/cli/test_jobs.py'
  adding 'ckan/tests/cli/test_search_index.py'
  adding 'ckan/tests/cli/test_user.py'
  adding 'ckan/tests/cli/data/test-env-var.ini'
  adding 'ckan/tests/cli/data/test-invalid-use.ini'
  adding 'ckan/tests/cli/data/test-no-env-var.ini'
  adding 'ckan/tests/cli/data/test-one-recursive.ini'
  adding 'ckan/tests/cli/data/test-one.ini'
  adding 'ckan/tests/cli/data/test-three-recursive.ini'
  adding 'ckan/tests/cli/data/test-three.ini'
  adding 'ckan/tests/cli/data/sub/test-two-recursive.ini'
  adding 'ckan/tests/cli/data/sub/test-two.ini'
  adding 'ckan/tests/config/__init__.py'
  adding 'ckan/tests/config/test_environment.py'
  adding 'ckan/tests/config/test_middleware.py'
  adding 'ckan/tests/config/test_sessions.py'
  adding 'ckan/tests/config/declaration/__init__.py'
  adding 'ckan/tests/config/declaration/test_declaration.py'
  adding 'ckan/tests/config/declaration/test_key.py'
  adding 'ckan/tests/config/declaration/test_option.py'
  adding 'ckan/tests/controllers/__init__.py'
  adding 'ckan/tests/controllers/test_admin.py'
  adding 'ckan/tests/controllers/test_api.py'
  adding 'ckan/tests/controllers/test_feed.py'
  adding 'ckan/tests/controllers/test_group.py'
  adding 'ckan/tests/controllers/test_home.py'
  adding 'ckan/tests/controllers/test_organization.py'
  adding 'ckan/tests/controllers/test_package.py'
  adding 'ckan/tests/controllers/test_pagination.py'
  adding 'ckan/tests/controllers/test_resource.py'
  adding 'ckan/tests/controllers/test_user.py'
  adding 'ckan/tests/controllers/test_util.py'
  adding 'ckan/tests/i18n/__init__.py'
  adding 'ckan/tests/i18n/test_check_po_files.py'
  adding 'ckan/tests/lib/__init__.py'
  adding 'ckan/tests/lib/test_app_globals.py'
  adding 'ckan/tests/lib/test_authenticator.py'
  adding 'ckan/tests/lib/test_base.py'
  adding 'ckan/tests/lib/test_config_tool.py'
  adding 'ckan/tests/lib/test_datapreview.py'
  adding 'ckan/tests/lib/test_formatters.py'
  adding 'ckan/tests/lib/test_hash.py'
  adding 'ckan/tests/lib/test_helpers.py'
  adding 'ckan/tests/lib/test_i18n.py'
  adding 'ckan/tests/lib/test_io.py'
  adding 'ckan/tests/lib/test_jobs.py'
  adding 'ckan/tests/lib/test_mailer.py'
  adding 'ckan/tests/lib/test_munge.py'
  adding 'ckan/tests/lib/test_signals.py'
  adding 'ckan/tests/lib/test_uploader.py'
  adding 'ckan/tests/lib/dictization/__init__.py'
  adding 'ckan/tests/lib/dictization/test_dictization.py'
  adding 'ckan/tests/lib/dictization/test_model_dictize.py'
  adding 'ckan/tests/lib/navl/__init__.py'
  adding 'ckan/tests/lib/navl/test_dictization_functions.py'
  adding 'ckan/tests/lib/navl/test_validators.py'
  adding 'ckan/tests/lib/search/__init__.py'
  adding 'ckan/tests/lib/search/test_common.py'
  adding 'ckan/tests/lib/search/test_index.py'
  adding 'ckan/tests/lib/search/test_query.py'
  adding 'ckan/tests/lib/search/test_search.py'
  adding 'ckan/tests/logic/__init__.py'
  adding 'ckan/tests/logic/test_conversion.py'
  adding 'ckan/tests/logic/test_converters.py'
  adding 'ckan/tests/logic/test_logic.py'
  adding 'ckan/tests/logic/test_schema.py'
  adding 'ckan/tests/logic/test_validators.py'
  adding 'ckan/tests/logic/action/__init__.py'
  adding 'ckan/tests/logic/action/test_create.py'
  adding 'ckan/tests/logic/action/test_delete.py'
  adding 'ckan/tests/logic/action/test_get.py'
  adding 'ckan/tests/logic/action/test_init.py'
  adding 'ckan/tests/logic/action/test_patch.py'
  adding 'ckan/tests/logic/action/test_update.py'
  adding 'ckan/tests/logic/auth/__init__.py'
  adding 'ckan/tests/logic/auth/test_create.py'
  adding 'ckan/tests/logic/auth/test_delete.py'
  adding 'ckan/tests/logic/auth/test_get.py'
  adding 'ckan/tests/logic/auth/test_init.py'
  adding 'ckan/tests/logic/auth/test_update.py'
  adding 'ckan/tests/model/__init__.py'
  adding 'ckan/tests/model/test_api_token.py'
  adding 'ckan/tests/model/test_follower.py'
  adding 'ckan/tests/model/test_group.py'
  adding 'ckan/tests/model/test_license.py'
  adding 'ckan/tests/model/test_misc.py'
  adding 'ckan/tests/model/test_package.py'
  adding 'ckan/tests/model/test_package_extra.py'
  adding 'ckan/tests/model/test_resource.py'
  adding 'ckan/tests/model/test_resource_view.py'
  adding 'ckan/tests/model/test_system_info.py'
  adding 'ckan/tests/model/test_tags.py'
  adding 'ckan/tests/model/test_user.py'
  adding 'ckan/tests/plugins/__init__.py'
  adding 'ckan/tests/plugins/ckantestplugins.py'
  adding 'ckan/tests/plugins/mock_plugin.py'
  adding 'ckan/tests/plugins/test_blanket.py'
  adding 'ckan/tests/plugins/test_core.py'
  adding 'ckan/tests/plugins/test_interfaces.py'
  adding 'ckan/tests/plugins/test_toolkit.py'
  adding 'ckan/tests/pytest_ckan/__init__.py'
  adding 'ckan/tests/pytest_ckan/ckan_setup.py'
  adding 'ckan/tests/pytest_ckan/fixtures.py'
  adding 'ckan/tests/pytest_ckan/test_fixtures.py'
  adding 'ckan/types/__init__.py'
  adding 'ckan/types/model.py'
  adding 'ckan/types/logic/__init__.py'
  adding 'ckan/types/logic/action_result.py'
  adding 'ckan/views/__init__.py'
  adding 'ckan/views/admin.py'
  adding 'ckan/views/api.py'
  adding 'ckan/views/dashboard.py'
  adding 'ckan/views/dataset.py'
  adding 'ckan/views/feed.py'
  adding 'ckan/views/group.py'
  adding 'ckan/views/home.py'
  adding 'ckan/views/resource.py'
  adding 'ckan/views/user.py'
  adding 'ckan/views/util.py'
  adding 'ckanext/activity/__init__.py'
  adding 'ckanext/activity/changes.py'
  adding 'ckanext/activity/email_notifications.py'
  adding 'ckanext/activity/helpers.py'
  adding 'ckanext/activity/plugin.py'
  adding 'ckanext/activity/subscriptions.py'
  adding 'ckanext/activity/views.py'
  adding 'ckanext/activity/assets/activity-stream.js'
  adding 'ckanext/activity/assets/activity.css'
  adding 'ckanext/activity/assets/activity.css.map'
  adding 'ckanext/activity/assets/activity.scss'
  adding 'ckanext/activity/assets/dashboard.js'
  adding 'ckanext/activity/assets/dashboard.spec.js'
  adding 'ckanext/activity/assets/webassets.yml'
  adding 'ckanext/activity/logic/__init__.py'
  adding 'ckanext/activity/logic/action.py'
  adding 'ckanext/activity/logic/auth.py'
  adding 'ckanext/activity/logic/schema.py'
  adding 'ckanext/activity/logic/validators.py'
  adding 'ckanext/activity/model/__init__.py'
  adding 'ckanext/activity/model/activity.py'
  adding 'ckanext/activity/public/dotted.png'
  adding 'ckanext/activity/templates/base.html'
  adding 'ckanext/activity/templates/header.html'
  adding 'ckanext/activity/templates/page.html'
  adding 'ckanext/activity/templates/activity_streams/activity_stream_email_notifications.text'
  adding 'ckanext/activity/templates/ajax_snippets/dashboard.html'
  adding 'ckanext/activity/templates/group/activity_stream.html'
  adding 'ckanext/activity/templates/group/changes.html'
  adding 'ckanext/activity/templates/group/read_base.html'
  adding 'ckanext/activity/templates/group/snippets/item_group.html'
  adding 'ckanext/activity/templates/organization/activity_stream.html'
  adding 'ckanext/activity/templates/organization/changes.html'
  adding 'ckanext/activity/templates/organization/read_base.html'
  adding 'ckanext/activity/templates/organization/snippets/item_organization.html'
  adding 'ckanext/activity/templates/package/activity_stream.html'
  adding 'ckanext/activity/templates/package/changes.html'
  adding 'ckanext/activity/templates/package/history.html'
  adding 'ckanext/activity/templates/package/read_base.html'
  adding 'ckanext/activity/templates/package/resource_history.html'
  adding 'ckanext/activity/templates/package/snippets/change_item.html'
  adding 'ckanext/activity/templates/package/snippets/resource_item.html'
  adding 'ckanext/activity/templates/package/snippets/resources.html'
  adding 'ckanext/activity/templates/package/snippets/resources_list.html'
  adding 'ckanext/activity/templates/snippets/activity_type_selector.html'
  adding 'ckanext/activity/templates/snippets/pagination.html'
  adding 'ckanext/activity/templates/snippets/stream.html'
  adding 'ckanext/activity/templates/snippets/activities/added_tag.html'
  adding 'ckanext/activity/templates/snippets/activities/changed_group.html'
  adding 'ckanext/activity/templates/snippets/activities/changed_organization.html'
  adding 'ckanext/activity/templates/snippets/activities/changed_package.html'
  adding 'ckanext/activity/templates/snippets/activities/changed_resource.html'
  adding 'ckanext/activity/templates/snippets/activities/changed_user.html'
  adding 'ckanext/activity/templates/snippets/activities/deleted_group.html'
  adding 'ckanext/activity/templates/snippets/activities/deleted_organization.html'
  adding 'ckanext/activity/templates/snippets/activities/deleted_package.html'
  adding 'ckanext/activity/templates/snippets/activities/deleted_resource.html'
  adding 'ckanext/activity/templates/snippets/activities/fallback.html'
  adding 'ckanext/activity/templates/snippets/activities/follow_dataset.html'
  adding 'ckanext/activity/templates/snippets/activities/follow_group.html'
  adding 'ckanext/activity/templates/snippets/activities/follow_user.html'
  adding 'ckanext/activity/templates/snippets/activities/new_group.html'
  adding 'ckanext/activity/templates/snippets/activities/new_organization.html'
  adding 'ckanext/activity/templates/snippets/activities/new_package.html'
  adding 'ckanext/activity/templates/snippets/activities/new_resource.html'
  adding 'ckanext/activity/templates/snippets/activities/new_user.html'
  adding 'ckanext/activity/templates/snippets/activities/removed_tag.html'
  adding 'ckanext/activity/templates/snippets/changes/author.html'
  adding 'ckanext/activity/templates/snippets/changes/author_email.html'
  adding 'ckanext/activity/templates/snippets/changes/delete_resource.html'
  adding 'ckanext/activity/templates/snippets/changes/extension_fields.html'
  adding 'ckanext/activity/templates/snippets/changes/extra_fields.html'
  adding 'ckanext/activity/templates/snippets/changes/license.html'
  adding 'ckanext/activity/templates/snippets/changes/maintainer.html'
  adding 'ckanext/activity/templates/snippets/changes/maintainer_email.html'
  adding 'ckanext/activity/templates/snippets/changes/name.html'
  adding 'ckanext/activity/templates/snippets/changes/new_file.html'
  adding 'ckanext/activity/templates/snippets/changes/new_resource.html'
  adding 'ckanext/activity/templates/snippets/changes/no_change.html'
  adding 'ckanext/activity/templates/snippets/changes/notes.html'
  adding 'ckanext/activity/templates/snippets/changes/org.html'
  adding 'ckanext/activity/templates/snippets/changes/private.html'
  adding 'ckanext/activity/templates/snippets/changes/resource_desc.html'
  adding 'ckanext/activity/templates/snippets/changes/resource_extras.html'
  adding 'ckanext/activity/templates/snippets/changes/resource_format.html'
  adding 'ckanext/activity/templates/snippets/changes/resource_name.html'
  adding 'ckanext/activity/templates/snippets/changes/tags.html'
  adding 'ckanext/activity/templates/snippets/changes/title.html'
  adding 'ckanext/activity/templates/snippets/changes/url.html'
  adding 'ckanext/activity/templates/snippets/changes/version.html'
  adding 'ckanext/activity/templates/snippets/group_changes/description.html'
  adding 'ckanext/activity/templates/snippets/group_changes/image_url.html'
  adding 'ckanext/activity/templates/snippets/group_changes/no_change.html'
  adding 'ckanext/activity/templates/snippets/group_changes/title.html'
  adding 'ckanext/activity/templates/snippets/organization_changes/description.html'
  adding 'ckanext/activity/templates/snippets/organization_changes/image_url.html'
  adding 'ckanext/activity/templates/snippets/organization_changes/no_change.html'
  adding 'ckanext/activity/templates/snippets/organization_changes/title.html'
  adding 'ckanext/activity/templates/user/activity_stream.html'
  adding 'ckanext/activity/templates/user/dashboard.html'
  adding 'ckanext/activity/templates/user/edit_user_form.html'
  adding 'ckanext/activity/templates/user/read_base.html'
  adding 'ckanext/activity/templates/user/snippets/followee_dropdown.html'
  adding 'ckanext/activity/tests/__init__.py'
  adding 'ckanext/activity/tests/conftest.py'
  adding 'ckanext/activity/tests/test_changes.py'
  adding 'ckanext/activity/tests/test_email_notifications.py'
  adding 'ckanext/activity/tests/test_helpers.py'
  adding 'ckanext/activity/tests/test_views.py'
  adding 'ckanext/activity/tests/logic/__init__.py'
  adding 'ckanext/activity/tests/logic/test_action.py'
  adding 'ckanext/activity/tests/logic/test_auth.py'
  adding 'ckanext/activity/tests/logic/test_functional.py'
  adding 'ckanext/activity/tests/logic/test_pagination.py'
  adding 'ckanext/activity/tests/model/__init__.py'
  adding 'ckanext/activity/tests/model/test_activity.py'
  adding 'ckanext/audioview/__init__.py'
  adding 'ckanext/audioview/plugin.py'
  adding 'ckanext/audioview/tests/__init__.py'
  adding 'ckanext/audioview/tests/test_view.py'
  adding 'ckanext/audioview/theme/templates/audio_form.html'
  adding 'ckanext/audioview/theme/templates/audio_view.html'
  adding 'ckanext/chained_functions/__init__.py'
  adding 'ckanext/chained_functions/plugin.py'
  adding 'ckanext/chained_functions/tests/__init__.py'
  adding 'ckanext/chained_functions/tests/test_plugin.py'
  adding 'ckanext/datapusher/__init__.py'
  adding 'ckanext/datapusher/cli.py'
  adding 'ckanext/datapusher/config_declaration.yaml'
  adding 'ckanext/datapusher/helpers.py'
  adding 'ckanext/datapusher/interfaces.py'
  adding 'ckanext/datapusher/plugin.py'
  adding 'ckanext/datapusher/views.py'
  adding 'ckanext/datapusher/assets/datapusher.css'
  adding 'ckanext/datapusher/assets/datapusher.css.map'
  adding 'ckanext/datapusher/assets/datapusher.scss'
  adding 'ckanext/datapusher/assets/datapusher_popover.js'
  adding 'ckanext/datapusher/assets/webassets.yml'
  adding 'ckanext/datapusher/logic/__init__.py'
  adding 'ckanext/datapusher/logic/action.py'
  adding 'ckanext/datapusher/logic/auth.py'
  adding 'ckanext/datapusher/logic/schema.py'
  adding 'ckanext/datapusher/public/dotted.png'
  adding 'ckanext/datapusher/templates/datapusher/resource_data.html'
  adding 'ckanext/datapusher/templates/package/resource_edit_base.html'
  adding 'ckanext/datapusher/tests/__init__.py'
  adding 'ckanext/datapusher/tests/test.py'
  adding 'ckanext/datapusher/tests/test_action.py'
  adding 'ckanext/datapusher/tests/test_default_views.py'
  adding 'ckanext/datapusher/tests/test_interfaces.py'
  adding 'ckanext/datapusher/tests/test_views.py'
  adding 'ckanext/datastore/__init__.py'
  adding 'ckanext/datastore/allowed_functions.txt'
  adding 'ckanext/datastore/blueprint.py'
  adding 'ckanext/datastore/cli.py'
  adding 'ckanext/datastore/config_declaration.yaml'
  adding 'ckanext/datastore/helpers.py'
  adding 'ckanext/datastore/interfaces.py'
  adding 'ckanext/datastore/plugin.py'
  adding 'ckanext/datastore/set_permissions.sql'
  adding 'ckanext/datastore/writer.py'
  adding 'ckanext/datastore/backend/__init__.py'
  adding 'ckanext/datastore/backend/postgres.py'
  adding 'ckanext/datastore/logic/__init__.py'
  adding 'ckanext/datastore/logic/action.py'
  adding 'ckanext/datastore/logic/auth.py'
  adding 'ckanext/datastore/logic/schema.py'
  adding 'ckanext/datastore/templates/ajax_snippets/api_info.html'
  adding 'ckanext/datastore/templates/datastore/dictionary.html'
  adding 'ckanext/datastore/templates/datastore/snippets/dictionary_form.html'
  adding 'ckanext/datastore/templates/package/resource_edit_base.html'
  adding 'ckanext/datastore/templates/package/resource_read.html'
  adding 'ckanext/datastore/templates/package/snippets/data_api_button.html'
  adding 'ckanext/datastore/templates/package/snippets/dictionary_table.html'
  adding 'ckanext/datastore/tests/__init__.py'
  adding 'ckanext/datastore/tests/conftest.py'
  adding 'ckanext/datastore/tests/helpers.py'
  adding 'ckanext/datastore/tests/sample_datastore_plugin.py'
  adding 'ckanext/datastore/tests/test_auth.py'
  adding 'ckanext/datastore/tests/test_chained_action.py'
  adding 'ckanext/datastore/tests/test_chained_auth_functions.py'
  adding 'ckanext/datastore/tests/test_create.py'
  adding 'ckanext/datastore/tests/test_db.py'
  adding 'ckanext/datastore/tests/test_delete.py'
  adding 'ckanext/datastore/tests/test_dictionary.py'
  adding 'ckanext/datastore/tests/test_disable.py'
  adding 'ckanext/datastore/tests/test_dump.py'
  adding 'ckanext/datastore/tests/test_helpers.py'
  adding 'ckanext/datastore/tests/test_info.py'
  adding 'ckanext/datastore/tests/test_interface.py'
  adding 'ckanext/datastore/tests/test_plugin.py'
  adding 'ckanext/datastore/tests/test_search.py'
  adding 'ckanext/datastore/tests/test_unit.py'
  adding 'ckanext/datastore/tests/test_upsert.py'
  adding 'ckanext/datatablesview/__init__.py'
  adding 'ckanext/datatablesview/blueprint.py'
  adding 'ckanext/datatablesview/config_declaration.yaml'
  adding 'ckanext/datatablesview/plugin.py'
  adding 'ckanext/datatablesview/public/datatables_view.css'
  adding 'ckanext/datatablesview/public/datatablesview.js'
  adding 'ckanext/datatablesview/public/resource.config'
  adding 'ckanext/datatablesview/public/webassets.yml'
  adding 'ckanext/datatablesview/public/vendor/DataTables/dataTables.scrollResize.js'
  adding 'ckanext/datatablesview/public/vendor/DataTables/datatables.css'
  adding 'ckanext/datatablesview/public/vendor/DataTables/datatables.js'
  adding 'ckanext/datatablesview/public/vendor/DataTables/datatables.mark.css'
  adding 'ckanext/datatablesview/public/vendor/DataTables/datatables.mark.js'
  adding 'ckanext/datatablesview/public/vendor/DataTables/datetime.js'
  adding 'ckanext/datatablesview/public/vendor/DataTables/jquery.mark.js'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/af.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/am.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ar.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/az.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/az_az.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/be.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/bg.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/bn.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/bs.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ca.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/cs.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/cs_CZ.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/cy.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/da.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/de.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/el.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/en-gb.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/en_GB.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/eo.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/es.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/et.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/eu.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/fa.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/fi.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/fil.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/fr.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ga.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/gl.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/gu.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/he.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/hi.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/hr.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/hu.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/hy.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/id.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/id_alt.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/is.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/it.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ja.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ka.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/kk.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/km.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/kn.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ko.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ko_KR.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ku.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ky.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/lo.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/lt.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/lv.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/mk.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/mn.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ms.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ne.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/nl.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/no.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/no_nb.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/pa.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/pl.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ps.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/pt.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/pt_BR.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/pt_pt.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/rm.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ro.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ru.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/si.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/sk.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/sl.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/snd.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/sq.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/sr.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/sr@latin.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/sr_sp.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/sv.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/sw.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ta.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/te.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/tg.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/th.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/tl.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/tr.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/uk.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/ur.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/uz.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/vi.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/zh.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/zh_CN.json'
  adding 'ckanext/datatablesview/public/vendor/DataTables/i18n/zh_Hant.json'
  adding 'ckanext/datatablesview/public/vendor/FontAwesome/images/times-circle-solid.svg'
  adding 'ckanext/datatablesview/templates/datatables/datatables_form.html'
  adding 'ckanext/datatablesview/templates/datatables/datatables_view.html'
  adding 'ckanext/example_blanket_implementation/__init__.py'
  adding 'ckanext/example_blanket_implementation/cli.py'
  adding 'ckanext/example_blanket_implementation/config_declaration.yaml'
  adding 'ckanext/example_blanket_implementation/helpers.py'
  adding 'ckanext/example_blanket_implementation/plugin.py'
  adding 'ckanext/example_blanket_implementation/views.py'
  adding 'ckanext/example_blanket_implementation/logic/__init__.py'
  adding 'ckanext/example_blanket_implementation/logic/auth.py'
  adding 'ckanext/example_blanket_implementation/logic/validators.py'
  adding 'ckanext/example_blanket_implementation/logic/action/__init__.py'
  adding 'ckanext/example_database_migrations/__init__.py'
  adding 'ckanext/example_database_migrations/plugin.py'
  adding 'ckanext/example_database_migrations/migration/example_database_migrations/env.py'
  adding 'ckanext/example_database_migrations/migration/example_database_migrations/versions/4f59069f433e_create_x_table.py'
  adding 'ckanext/example_database_migrations/migration/example_database_migrations/versions/728663ebe30e_create_y_table.py'
  adding 'ckanext/example_flask_iblueprint/__init__.py'
  adding 'ckanext/example_flask_iblueprint/plugin.py'
  adding 'ckanext/example_flask_iblueprint/templates/about.html'
  adding 'ckanext/example_flask_iblueprint/templates/about_base.html'
  adding 'ckanext/example_flask_iblueprint/tests/__init__.py'
  adding 'ckanext/example_flask_iblueprint/tests/test_routes.py'
  adding 'ckanext/example_flask_streaming/__init__.py'
  adding 'ckanext/example_flask_streaming/plugin.py'
  adding 'ckanext/example_flask_streaming/templates/stream.html'
  adding 'ckanext/example_flask_streaming/tests/__init__.py'
  adding 'ckanext/example_flask_streaming/tests/test_streaming_responses.py'
  adding 'ckanext/example_humanizer/__init__.py'
  adding 'ckanext/example_humanizer/plugin.py'
  adding 'ckanext/example_humanizer/tests/__init__.py'
  adding 'ckanext/example_humanizer/tests/test_plugin.py'
  adding 'ckanext/example_iapitoken/__init__.py'
  adding 'ckanext/example_iapitoken/plugin.py'
  adding 'ckanext/example_iapitoken/tests/__init__.py'
  adding 'ckanext/example_iapitoken/tests/test_plugin.py'
  adding 'ckanext/example_iauthenticator/__init__.py'
  adding 'ckanext/example_iauthenticator/plugin.py'
  adding 'ckanext/example_iauthenticator/tests/test_example_iauthenticator.py'
  adding 'ckanext/example_iauthfunctions/__init__.py'
  adding 'ckanext/example_iauthfunctions/plugin_v1.py'
  adding 'ckanext/example_iauthfunctions/plugin_v2.py'
  adding 'ckanext/example_iauthfunctions/plugin_v3.py'
  adding 'ckanext/example_iauthfunctions/plugin_v4.py'
  adding 'ckanext/example_iauthfunctions/plugin_v5_custom_config_setting.py'
  adding 'ckanext/example_iauthfunctions/plugin_v6_parent_auth_functions.py'
  adding 'ckanext/example_iauthfunctions/tests/test_example_iauthfunctions.py'
  adding 'ckanext/example_iclick/__init__.py'
  adding 'ckanext/example_iclick/cli.py'
  adding 'ckanext/example_iclick/plugin.py'
  adding 'ckanext/example_iconfigurer/__init__.py'
  adding 'ckanext/example_iconfigurer/blueprint.py'
  adding 'ckanext/example_iconfigurer/plugin.py'
  adding 'ckanext/example_iconfigurer/plugin_v1.py'
  adding 'ckanext/example_iconfigurer/plugin_v2.py'
  adding 'ckanext/example_iconfigurer/templates/admin/config.html'
  adding 'ckanext/example_iconfigurer/templates/admin/myext_config.html'
  adding 'ckanext/example_iconfigurer/tests/__init__.py'
  adding 'ckanext/example_iconfigurer/tests/test_example_iconfigurer.py'
  adding 'ckanext/example_iconfigurer/tests/test_iconfigurer_toolkit.py'
  adding 'ckanext/example_iconfigurer/tests/test_iconfigurer_update_config.py'
  adding 'ckanext/example_idatasetform/__init__.py'
  adding 'ckanext/example_idatasetform/plugin.py'
  adding 'ckanext/example_idatasetform/plugin_v1.py'
  adding 'ckanext/example_idatasetform/plugin_v2.py'
  adding 'ckanext/example_idatasetform/plugin_v3.py'
  adding 'ckanext/example_idatasetform/plugin_v4.py'
  adding 'ckanext/example_idatasetform/plugin_v5.py'
  adding 'ckanext/example_idatasetform/plugin_v6.py'
  adding 'ckanext/example_idatasetform/plugin_v7.py'
  adding 'ckanext/example_idatasetform/templates/first/new.html'
  adding 'ckanext/example_idatasetform/templates/first/read.html'
  adding 'ckanext/example_idatasetform/templates/package/read.html'
  adding 'ckanext/example_idatasetform/templates/package/search.html'
  adding 'ckanext/example_idatasetform/templates/package/snippets/additional_info.html'
  adding 'ckanext/example_idatasetform/templates/package/snippets/package_basic_fields.html'
  adding 'ckanext/example_idatasetform/templates/package/snippets/package_metadata_fields.html'
  adding 'ckanext/example_idatasetform/templates/package/snippets/resource_form.html'
  adding 'ckanext/example_idatasetform/templates/second/read.html'
  adding 'ckanext/example_idatasetform/tests/__init__.py'
  adding 'ckanext/example_idatasetform/tests/test_controllers.py'
  adding 'ckanext/example_idatasetform/tests/test_example_idatasetform.py'
  adding 'ckanext/example_idatastorebackend/__init__.py'
  adding 'ckanext/example_idatastorebackend/example_sqlite.py'
  adding 'ckanext/example_idatastorebackend/plugin.py'
  adding 'ckanext/example_idatastorebackend/test/__init__.py'
  adding 'ckanext/example_idatastorebackend/test/test_plugin.py'
  adding 'ckanext/example_igroupform/__init__.py'
  adding 'ckanext/example_igroupform/plugin.py'
  adding 'ckanext/example_igroupform/plugin_v2.py'
  adding 'ckanext/example_igroupform/templates/example_igroup_form/group_form.html'
  adding 'ckanext/example_igroupform/tests/__init__.py'
  adding 'ckanext/example_igroupform/tests/test_controllers.py'
  adding 'ckanext/example_ipermissionlabels/__init__.py'
  adding 'ckanext/example_ipermissionlabels/plugin.py'
  adding 'ckanext/example_ipermissionlabels/tests/__init__.py'
  adding 'ckanext/example_ipermissionlabels/tests/test_example_ipermissionlabels.py'
  adding 'ckanext/example_iresourcecontroller/__init__.py'
  adding 'ckanext/example_iresourcecontroller/plugin.py'
  adding 'ckanext/example_iresourcecontroller/tests/test_example_iresourcecontroller.py'
  adding 'ckanext/example_isignal/__init__.py'
  adding 'ckanext/example_isignal/plugin.py'
  adding 'ckanext/example_isignal/tests/__init__.py'
  adding 'ckanext/example_isignal/tests/test_plugin.py'
  adding 'ckanext/example_itemplatehelpers/__init__.py'
  adding 'ckanext/example_itemplatehelpers/plugin.py'
  adding 'ckanext/example_itemplatehelpers/templates/home/index.html'
  adding 'ckanext/example_itemplatehelpers/tests/__init__.py'
  adding 'ckanext/example_itemplatehelpers/tests/test_plugin.py'
  adding 'ckanext/example_itranslation/__init__.py'
  adding 'ckanext/example_itranslation/plugin.py'
  adding 'ckanext/example_itranslation/plugin_v1.py'
  adding 'ckanext/example_itranslation/i18n/ckanext-example_itranslation.pot'
  adding 'ckanext/example_itranslation/i18n/en/LC_MESSAGES/ckanext-example_itranslation.mo'
  adding 'ckanext/example_itranslation/i18n/en/LC_MESSAGES/ckanext-example_itranslation.po'
  adding 'ckanext/example_itranslation/i18n/en/LC_MESSAGES/ckanext-example_translation.po'
  adding 'ckanext/example_itranslation/i18n/fr/LC_MESSAGES/ckanext-example_itranslation.mo'
  adding 'ckanext/example_itranslation/i18n/fr/LC_MESSAGES/ckanext-example_itranslation.po'
  adding 'ckanext/example_itranslation/templates/home/index.html'
  adding 'ckanext/example_itranslation/tests/__init__.py'
  adding 'ckanext/example_itranslation/tests/test_plugin.py'
  adding 'ckanext/example_iuploader/__init__.py'
  adding 'ckanext/example_iuploader/plugin.py'
  adding 'ckanext/example_iuploader/test/__init__.py'
  adding 'ckanext/example_iuploader/test/test_plugin.py'
  adding 'ckanext/example_ivalidators/__init__.py'
  adding 'ckanext/example_ivalidators/plugin.py'
  adding 'ckanext/example_ivalidators/tests/__init__.py'
  adding 'ckanext/example_ivalidators/tests/test_ivalidators.py'
  adding 'ckanext/example_theme_docs/__init__.py'
  adding 'ckanext/example_theme_docs/custom_config_setting/__init__.py'
  adding 'ckanext/example_theme_docs/custom_config_setting/plugin.py'
  adding 'ckanext/example_theme_docs/custom_emails/__init__.py'
  adding 'ckanext/example_theme_docs/custom_emails/plugin.py'
  adding 'ckanext/example_theme_docs/custom_emails/test_custom_emails.py'
  adding 'ckanext/example_theme_docs/v01_empty_extension/__init__.py'
  adding 'ckanext/example_theme_docs/v01_empty_extension/plugin.py'
  adding 'ckanext/example_theme_docs/v02_empty_template/__init__.py'
  adding 'ckanext/example_theme_docs/v02_empty_template/plugin.py'
  adding 'ckanext/example_theme_docs/v03_jinja/__init__.py'
  adding 'ckanext/example_theme_docs/v03_jinja/plugin.py'
  adding 'ckanext/example_theme_docs/v04_ckan_extends/__init__.py'
  adding 'ckanext/example_theme_docs/v04_ckan_extends/plugin.py'
  adding 'ckanext/example_theme_docs/v05_block/__init__.py'
  adding 'ckanext/example_theme_docs/v05_block/plugin.py'
  adding 'ckanext/example_theme_docs/v06_super/__init__.py'
  adding 'ckanext/example_theme_docs/v06_super/plugin.py'
  adding 'ckanext/example_theme_docs/v07_helper_function/__init__.py'
  adding 'ckanext/example_theme_docs/v07_helper_function/plugin.py'
  adding 'ckanext/example_theme_docs/v08_custom_helper_function/__init__.py'
  adding 'ckanext/example_theme_docs/v08_custom_helper_function/plugin.py'
  adding 'ckanext/example_theme_docs/v09_snippet/__init__.py'
  adding 'ckanext/example_theme_docs/v09_snippet/plugin.py'
  adding 'ckanext/example_theme_docs/v10_custom_snippet/__init__.py'
  adding 'ckanext/example_theme_docs/v10_custom_snippet/plugin.py'
  adding 'ckanext/example_theme_docs/v11_HTML_and_CSS/__init__.py'
  adding 'ckanext/example_theme_docs/v11_HTML_and_CSS/plugin.py'
  adding 'ckanext/example_theme_docs/v12_extra_public_dir/__init__.py'
  adding 'ckanext/example_theme_docs/v12_extra_public_dir/plugin.py'
  adding 'ckanext/example_theme_docs/v13_custom_css/__init__.py'
  adding 'ckanext/example_theme_docs/v13_custom_css/plugin.py'
  adding 'ckanext/example_theme_docs/v14_more_custom_css/__init__.py'
  adding 'ckanext/example_theme_docs/v14_more_custom_css/plugin.py'
  adding 'ckanext/example_theme_docs/v15_webassets/__init__.py'
  adding 'ckanext/example_theme_docs/v15_webassets/plugin.py'
  adding 'ckanext/example_theme_docs/v16_initialize_a_javascript_module/__init__.py'
  adding 'ckanext/example_theme_docs/v16_initialize_a_javascript_module/plugin.py'
  adding 'ckanext/example_theme_docs/v17_popover/__init__.py'
  adding 'ckanext/example_theme_docs/v17_popover/plugin.py'
  adding 'ckanext/example_theme_docs/v18_snippet_api/__init__.py'
  adding 'ckanext/example_theme_docs/v18_snippet_api/plugin.py'
  adding 'ckanext/example_theme_docs/v19_01_error/__init__.py'
  adding 'ckanext/example_theme_docs/v19_01_error/plugin.py'
  adding 'ckanext/example_theme_docs/v19_02_error_handling/__init__.py'
  adding 'ckanext/example_theme_docs/v19_02_error_handling/plugin.py'
  adding 'ckanext/example_theme_docs/v20_pubsub/__init__.py'
  adding 'ckanext/example_theme_docs/v20_pubsub/plugin.py'
  adding 'ckanext/example_theme_docs/v21_custom_jquery_plugin/__init__.py'
  adding 'ckanext/example_theme_docs/v21_custom_jquery_plugin/plugin.py'
  adding 'ckanext/example_theme_docs/v22_webassets/__init__.py'
  adding 'ckanext/example_theme_docs/v22_webassets/plugin.py'
  adding 'ckanext/expire_api_token/__init__.py'
  adding 'ckanext/expire_api_token/plugin.py'
  adding 'ckanext/expire_api_token/templates/user/api_tokens.html'
  adding 'ckanext/expire_api_token/templates/user/snippets/api_token_list.html'
  adding 'ckanext/expire_api_token/tests/__init__.py'
  adding 'ckanext/expire_api_token/tests/test_plugin.py'
  adding 'ckanext/imageview/__init__.py'
  adding 'ckanext/imageview/config_declaration.yaml'
  adding 'ckanext/imageview/plugin.py'
  adding 'ckanext/imageview/tests/__init__.py'
  adding 'ckanext/imageview/tests/test_view.py'
  adding 'ckanext/imageview/theme/templates/image_form.html'
  adding 'ckanext/imageview/theme/templates/image_view.html'
  adding 'ckanext/multilingual/__init__.py'
  adding 'ckanext/multilingual/plugin.py'
  adding 'ckanext/multilingual/tests/test_multilingual_plugin.py'
  adding 'ckanext/reclineview/__init__.py'
  adding 'ckanext/reclineview/config_declaration.yaml'
  adding 'ckanext/reclineview/plugin.py'
  adding 'ckanext/reclineview/tests/__init__.py'
  adding 'ckanext/reclineview/tests/test_view.py'
  adding 'ckanext/reclineview/theme/public/recline_view.js'
  adding 'ckanext/reclineview/theme/public/recline_view.min.js'
  adding 'ckanext/reclineview/theme/public/resource.config'
  adding 'ckanext/reclineview/theme/public/webassets.yml'
  adding 'ckanext/reclineview/theme/public/widget.recordcount.js'
  adding 'ckanext/reclineview/theme/public/widget.recordcount.min.js'
  adding 'ckanext/reclineview/theme/public/css/recline.css'
  adding 'ckanext/reclineview/theme/public/css/recline.min.css'
  adding 'ckanext/reclineview/theme/public/img/ajaxload-circle.gif'
  adding 'ckanext/reclineview/theme/public/vendor/backbone/1.0.0/backbone.js'
  adding 'ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/css/bootstrap-theme.css'
  adding 'ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/css/bootstrap.css'
  adding 'ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts/glyphicons-halflings-regular.eot'
  adding 'ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts/glyphicons-halflings-regular.svg'
  adding 'ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts/glyphicons-halflings-regular.ttf'
  adding 'ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/fonts/glyphicons-halflings-regular.woff'
  adding 'ckanext/reclineview/theme/public/vendor/bootstrap/3.2.0/js/bootstrap.js'
  adding 'ckanext/reclineview/theme/public/vendor/ckan.js/ckan.js'
  adding 'ckanext/reclineview/theme/public/vendor/flot/excanvas.js'
  adding 'ckanext/reclineview/theme/public/vendor/flot/excanvas.min.js'
  adding 'ckanext/reclineview/theme/public/vendor/flot/jquery.flot.js'
  adding 'ckanext/reclineview/theme/public/vendor/flot/jquery.flot.time.js'
  adding 'ckanext/reclineview/theme/public/vendor/flotr2/flotr2.js'
  adding 'ckanext/reclineview/theme/public/vendor/flotr2/flotr2.min.js'
  adding 'ckanext/reclineview/theme/public/vendor/jquery/1.7.1/jquery.js'
  adding 'ckanext/reclineview/theme/public/vendor/jquery/1.7.1/jquery.min.js'
  adding 'ckanext/reclineview/theme/public/vendor/json/json2.js'
  adding 'ckanext/reclineview/theme/public/vendor/json/json2.min.js'
  adding 'ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/leaflet-src.js'
  adding 'ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/leaflet.css'
  adding 'ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/leaflet.js'
  adding 'ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/layers-2x.png'
  adding 'ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/layers.png'
  adding 'ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/marker-icon-2x.png'
  adding 'ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/marker-icon.png'
  adding 'ckanext/reclineview/theme/public/vendor/leaflet/0.7.7/images/marker-shadow.png'
  adding 'ckanext/reclineview/theme/public/vendor/leaflet.markercluster/MarkerCluster.Default.css'
  adding 'ckanext/reclineview/theme/public/vendor/leaflet.markercluster/MarkerCluster.css'
  adding 'ckanext/reclineview/theme/public/vendor/leaflet.markercluster/leaflet.markercluster-src.js'
  adding 'ckanext/reclineview/theme/public/vendor/leaflet.markercluster/leaflet.markercluster.js'
  adding 'ckanext/reclineview/theme/public/vendor/moment/2.0.0/moment.js'
  adding 'ckanext/reclineview/theme/public/vendor/mustache/0.5.0-dev/mustache.js'
  adding 'ckanext/reclineview/theme/public/vendor/mustache/0.5.0-dev/mustache.min.js'
  adding 'ckanext/reclineview/theme/public/vendor/recline/flot.css'
  adding 'ckanext/reclineview/theme/public/vendor/recline/map.css'
  adding 'ckanext/reclineview/theme/public/vendor/recline/recline.css'
  adding 'ckanext/reclineview/theme/public/vendor/recline/recline.dataset.js'
  adding 'ckanext/reclineview/theme/public/vendor/recline/recline.js'
  adding 'ckanext/reclineview/theme/public/vendor/recline/slickgrid.css'
  adding 'ckanext/reclineview/theme/public/vendor/showdown/20120615/showdown.js'
  adding 'ckanext/reclineview/theme/public/vendor/showdown/20120615/showdown.min.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/MIT-LICENSE.txt'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/README.md'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/jquery-1.7.min.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/jquery-ui-1.8.16.custom.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/jquery.event.drag-2.2.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/jquery.event.drop-2.2.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick-default-theme.css'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.core.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.dataview.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.editors.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.formatters.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.grid.css'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.grid.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.groupitemmetadataprovider.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/slick.remotemodel.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls/slick.columnpicker.css'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls/slick.columnpicker.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls/slick.pager.css'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/controls/slick.pager.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/jquery-ui-1.8.16.custom.css'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_flat_0_aaaaaa_40x100.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_flat_75_ffffff_40x100.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_55_fbf9ee_1x400.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_65_ffffff_1x400.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_75_dadada_1x400.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_75_e6e6e6_1x400.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_glass_95_fef1ec_1x400.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-bg_highlight-soft_75_cccccc_1x100.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_222222_256x240.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_2e83ff_256x240.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_454545_256x240.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_888888_256x240.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/css/smoothness/images/ui-icons_cd0a0a_256x240.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/actions.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/ajax-loader-small.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/arrow_redo.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/arrow_right_peppermint.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/arrow_right_spearmint.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/arrow_undo.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/bullet_blue.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/bullet_star.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/bullet_toggle_minus.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/bullet_toggle_plus.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/calendar.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/collapse.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/comment_yellow.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/down.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/drag-handle.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/editor-helper-bg.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/expand.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/header-bg.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/header-columns-bg.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/header-columns-over-bg.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/help.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/info.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/listview.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/pencil.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/row-over-bg.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/sort-asc.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/sort-asc.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/sort-desc.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/sort-desc.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/stripes.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/tag_red.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/tick.png'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/user_identity.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/images/user_identity_plus.gif'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.autotooltips.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.cellcopymanager.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.cellrangedecorator.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.cellrangeselector.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.cellselectionmodel.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.checkboxselectcolumn.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.headerbuttons.css'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.headerbuttons.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.headermenu.css'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.headermenu.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.rowmovemanager.js'
  adding 'ckanext/reclineview/theme/public/vendor/slickgrid/2.2/plugins/slick.rowselectionmodel.js'
  adding 'ckanext/reclineview/theme/public/vendor/timeline/LICENSE'
  adding 'ckanext/reclineview/theme/public/vendor/timeline/README'
  adding 'ckanext/reclineview/theme/public/vendor/timeline/css/loading.gif'
  adding 'ckanext/reclineview/theme/public/vendor/timeline/css/timeline.css'
  adding 'ckanext/reclineview/theme/public/vendor/timeline/css/timeline.png'
  adding 'ckanext/reclineview/theme/public/vendor/timeline/css/timeline@2x.png'
  adding 'ckanext/reclineview/theme/public/vendor/timeline/js/timeline.js'
  adding 'ckanext/reclineview/theme/public/vendor/underscore/1.4.4/underscore.js'
  adding 'ckanext/reclineview/theme/public/vendor/underscore.deferred/0.4.0/underscore.deferred.js'
  adding 'ckanext/reclineview/theme/public/vendor/underscore.deferred/0.4.0/underscore.deferred.min.js'
  adding 'ckanext/reclineview/theme/templates/recline_graph_form.html'
  adding 'ckanext/reclineview/theme/templates/recline_map_form.html'
  adding 'ckanext/reclineview/theme/templates/recline_view.html'
  adding 'ckanext/resourceproxy/__init__.py'
  adding 'ckanext/resourceproxy/blueprint.py'
  adding 'ckanext/resourceproxy/config_declaration.yaml'
  adding 'ckanext/resourceproxy/plugin.py'
  adding 'ckanext/resourceproxy/tests/__init__.py'
  adding 'ckanext/resourceproxy/tests/test_proxy.py'
  adding 'ckanext/stats/__init__.py'
  adding 'ckanext/stats/blueprint.py'
  adding 'ckanext/stats/plugin.py'
  adding 'ckanext/stats/stats.py'
  adding 'ckanext/stats/public/.gitignore'
  adding 'ckanext/stats/public/__init__.py'
  adding 'ckanext/stats/public/ckanext/__init__.py'
  adding 'ckanext/stats/public/ckanext/stats/__init__.py'
  adding 'ckanext/stats/public/ckanext/stats/resource.config'
  adding 'ckanext/stats/public/ckanext/stats/webassets.yml'
  adding 'ckanext/stats/public/ckanext/stats/css/stats.css'
  adding 'ckanext/stats/public/ckanext/stats/javascript/modules/plot.js'
  adding 'ckanext/stats/public/ckanext/stats/javascript/modules/stats-nav.js'
  adding 'ckanext/stats/public/ckanext/stats/test/index.html'
  adding 'ckanext/stats/public/ckanext/stats/test/fixtures/table.html'
  adding 'ckanext/stats/public/ckanext/stats/test/spec/modules/plot.spec.js'
  adding 'ckanext/stats/public/ckanext/stats/test/spec/modules/stats-nav.spec.js'
  adding 'ckanext/stats/public/ckanext/stats/vendor/excanvas.js'
  adding 'ckanext/stats/public/ckanext/stats/vendor/jquery.flot.js'
  adding 'ckanext/stats/templates/ckanext/stats/index.html'
  adding 'ckanext/stats/tests/__init__.py'
  adding 'ckanext/stats/tests/test_stats_lib.py'
  adding 'ckanext/stats/tests/test_stats_plugin.py'
  adding 'ckanext/textview/__init__.py'
  adding 'ckanext/textview/config_declaration.yaml'
  adding 'ckanext/textview/plugin.py'
  adding 'ckanext/textview/tests/__init__.py'
  adding 'ckanext/textview/tests/test_view.py'
  adding 'ckanext/textview/theme/public/LICENSE'
  adding 'ckanext/textview/theme/public/resource.config'
  adding 'ckanext/textview/theme/public/text_view.js'
  adding 'ckanext/textview/theme/public/webassets.yml'
  adding 'ckanext/textview/theme/public/css/text.css'
  adding 'ckanext/textview/theme/public/styles/a11y-light.css'
  adding 'ckanext/textview/theme/public/vendor/highlight.js'
  adding 'ckanext/textview/theme/templates/text_form.html'
  adding 'ckanext/textview/theme/templates/text_view.html'
  adding 'ckanext/videoview/__init__.py'
  adding 'ckanext/videoview/plugin.py'
  adding 'ckanext/videoview/tests/__init__.py'
  adding 'ckanext/videoview/tests/test_view.py'
  adding 'ckanext/videoview/theme/templates/video_form.html'
  adding 'ckanext/videoview/theme/templates/video_view.html'
  adding 'ckanext/webpageview/__init__.py'
  adding 'ckanext/webpageview/plugin.py'
  adding 'ckanext/webpageview/tests/__init__.py'
  adding 'ckanext/webpageview/tests/test_view.py'
  adding 'ckanext/webpageview/theme/templates/webpage_form.html'
  adding 'ckanext/webpageview/theme/templates/webpage_view.html'
  adding 'ckan-2.10.4.dist-info/LICENSE.txt'
  adding 'ckan-2.10.4.dist-info/METADATA'
  adding 'ckan-2.10.4.dist-info/WHEEL'
  adding 'ckan-2.10.4.dist-info/entry_points.txt'
  adding 'ckan-2.10.4.dist-info/namespace_packages.txt'
  adding 'ckan-2.10.4.dist-info/top_level.txt'
  adding 'ckan-2.10.4.dist-info/RECORD'
  removing build/bdist.linux-x86_64/wheel
  Building wheel for ckan (pyproject.toml): finished with status 'done'
  Created wheel for ckan: filename=ckan-2.10.4-py3-none-any.whl size=9748094 sha256=9bea44e3e3b4896c5c35fbd0d347aad6e56459dc9c9d5b1a38e165de1852bd1a
  Stored in directory: /builddir/.cache/pip/wheels/ef/08/e3/4498d19cf5bb1c0245d91f3a4b6fa5c68a9930b89c9c6956d2
Successfully built ckan
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.YLH0cr
+ umask 022
+ cd /builddir/build/BUILD
+ '[' /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64 '!=' / ']'
+ rm -rf /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64
++ dirname /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64
+ mkdir -p /builddir/build/BUILDROOT
+ mkdir /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ cd ckan-2.10.4
++ ls /builddir/build/BUILD/ckan-2.10.4/pyproject-wheeldir/ckan-2.10.4-py3-none-any.whl
++ xargs basename --multiple
++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/'
+ specifier=ckan==2.10.4
+ '[' -z ckan==2.10.4 ']'
+ TMPDIR=/builddir/build/BUILD/ckan-2.10.4/.pyproject-builddir
+ /usr/bin/python3 -m pip install --root /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64 --prefix /usr --no-deps --disable-pip-version-check --progress-bar off --verbose --ignore-installed --no-warn-script-location --no-index --no-cache-dir --find-links /builddir/build/BUILD/ckan-2.10.4/pyproject-wheeldir ckan==2.10.4
Using pip 23.3.2 from /usr/lib/python3.12/site-packages/pip (python 3.12)
Looking in links: /builddir/build/BUILD/ckan-2.10.4/pyproject-wheeldir
Processing ./pyproject-wheeldir/ckan-2.10.4-py3-none-any.whl
Installing collected packages: ckan
  Creating /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/bin
  changing mode of /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/bin/ckan to 755
Successfully installed ckan-2.10.4
+ '[' -d /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/bin ']'
+ '[' -z sP ']'
+ shebang_flags=-kasP
+ /usr/bin/python3 -B /usr/lib/rpm/redhat/pathfix.py -pni /usr/bin/python3 -kasP /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/bin/ckan
/builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/bin/ckan: updating
+ rm -rfv /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/bin/__pycache__
+ rm -f /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-ghost-distinfo
+ site_dirs=()
+ '[' -d /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib/python3.12/site-packages ']'
+ site_dirs+=("/usr/lib/python3.12/site-packages")
+ '[' /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib64/python3.12/site-packages '!=' /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib/python3.12/site-packages ']'
+ '[' -d /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib64/python3.12/site-packages ']'
+ for site_dir in ${site_dirs[@]}
+ for distinfo in /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64$site_dir/*.dist-info
+ echo '%ghost /usr/lib/python3.12/site-packages/ckan-2.10.4.dist-info'
+ sed -i s/pip/rpm/ /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib/python3.12/site-packages/ckan-2.10.4.dist-info/INSTALLER
+ PYTHONPATH=/usr/lib/rpm/redhat
+ /usr/bin/python3 -B /usr/lib/rpm/redhat/pyproject_preprocess_record.py --buildroot /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64 --record /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib/python3.12/site-packages/ckan-2.10.4.dist-info/RECORD --output /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-record
+ rm -fv /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib/python3.12/site-packages/ckan-2.10.4.dist-info/RECORD
removed '/builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib/python3.12/site-packages/ckan-2.10.4.dist-info/RECORD'
+ rm -fv /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib/python3.12/site-packages/ckan-2.10.4.dist-info/REQUESTED
removed '/builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib/python3.12/site-packages/ckan-2.10.4.dist-info/REQUESTED'
++ wc -l /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-ghost-distinfo
++ cut -f1 '-d '
+ lines=1
+ '[' 1 -ne 1 ']'
+ RPM_PERCENTAGES_COUNT=2
+ /usr/bin/python3 /usr/lib/rpm/redhat/pyproject_save_files.py --output-files /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-files --output-modules /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-modules --buildroot /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64 --sitelib /usr/lib/python3.12/site-packages --sitearch /usr/lib64/python3.12/site-packages --python-version 3.12 --pyproject-record /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-record --prefix /usr '*' +auto
+ /usr/bin/find-debuginfo -j2 --strict-build-id -m -i --build-id-seed 2.10.4-1.fc40 --unique-debug-suffix -2.10.4-1.fc40.x86_64 --unique-debug-src-base python-ckan-2.10.4-1.fc40.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 -S debugsourcefiles.list /builddir/build/BUILD/ckan-2.10.4
find-debuginfo: starting
Extracting debug info from 0 files
Creating .debug symlinks for symlinks to ELF files
find: ‘debug’: No such file or directory
find-debuginfo: done
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/redhat/brp-ldconfig
+ /usr/lib/rpm/brp-compress
+ /usr/lib/rpm/redhat/brp-strip-lto /usr/bin/strip
+ /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/check-rpaths
+ /usr/lib/rpm/redhat/brp-mangle-shebangs
*** WARNING: ./usr/lib/python3.12/site-packages/ckan/public/base/vendor/jed.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckan/public/base/vendor/jquery.ui.core.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckan/public/base/vendor/jquery.ui.mouse.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckan/public/base/vendor/jquery.ui.sortable.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckan/public/base/vendor/jquery.ui.widget.js is executable but has no shebang, removing executable bit
mangling shebang in /usr/lib/python3.12/site-packages/ckan/public/base/vendor/select2/release.sh from /bin/bash to #!/usr/bin/bash
*** WARNING: ./usr/lib/python3.12/site-packages/ckan/public-bs3/base/vendor/jed.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckan/public-bs3/base/vendor/jquery.ui.core.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckan/public-bs3/base/vendor/jquery.ui.mouse.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckan/public-bs3/base/vendor/jquery.ui.sortable.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckan/public-bs3/base/vendor/jquery.ui.widget.js is executable but has no shebang, removing executable bit
mangling shebang in /usr/lib/python3.12/site-packages/ckan/public-bs3/base/vendor/select2/release.sh from /bin/bash to #!/usr/bin/bash
*** WARNING: ./usr/lib/python3.12/site-packages/ckanext/reclineview/theme/public/vendor/flot/excanvas.js is executable but has no shebang, removing executable bit
*** WARNING: Cannot read the first line from ./usr/lib/python3.12/site-packages/ckanext/reclineview/theme/public/vendor/flot/excanvas.min.js, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckanext/reclineview/theme/public/vendor/flot/jquery.flot.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckanext/reclineview/theme/public/vendor/flot/jquery.flot.time.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckanext/reclineview/theme/public/vendor/moment/2.0.0/moment.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckanext/reclineview/theme/public/vendor/recline/recline.css is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckanext/reclineview/theme/public/vendor/recline/recline.dataset.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckanext/reclineview/theme/public/vendor/recline/recline.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckanext/reclineview/theme/public/vendor/timeline/css/timeline.css is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckanext/reclineview/theme/public/vendor/timeline/js/timeline.js is executable but has no shebang, removing executable bit
*** WARNING: ./usr/lib/python3.12/site-packages/ckanext/reclineview/theme/public/vendor/underscore/1.4.4/underscore.js is executable but has no shebang, removing executable bit
+ /usr/lib/rpm/brp-remove-la-files
+ env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j2
Bytecompiling .py files below /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib/python3.12 using python3.12
+ /usr/lib/rpm/redhat/brp-python-hardlink
Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.Ah87lb
+ umask 022
+ cd /builddir/build/BUILD
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ cd ckan-2.10.4
+ '[' '!' -f /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-modules ']'
+ PATH=/builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin
+ PYTHONPATH=/builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib64/python3.12/site-packages:/builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib/python3.12/site-packages
+ _PYTHONSITE=/builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib64/python3.12/site-packages:/builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64/usr/lib/python3.12/site-packages
+ PYTHONDONTWRITEBYTECODE=1
+ /usr/bin/python3 -sP /usr/lib/rpm/redhat/import_all_modules.py -f /builddir/build/BUILD/python-ckan-2.10.4-1.fc40.x86_64-pyproject-modules -t
Check import: ckan
Check import: ckanext
+ RPM_EC=0
++ jobs -p
+ exit 0
Processing files: python3-ckan-2.10.4-1.fc40.noarch
Provides: python-ckan = 2.10.4-1.fc40 python3-ckan = 2.10.4-1.fc40 python3.12-ckan = 2.10.4-1.fc40 python3.12dist(ckan) = 2.10.4 python3dist(ckan) = 2.10.4
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires: /usr/bin/bash /usr/bin/python3 python(abi) = 3.12 python3.12dist(setuptools) >= 44.1
Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64
Wrote: /builddir/build/SRPMS/python-ckan-2.10.4-1.fc40.src.rpm
Wrote: /builddir/build/RPMS/python3-ckan-2.10.4-1.fc40.noarch.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.d1re6V
+ umask 022
+ cd /builddir/build/BUILD
+ cd ckan-2.10.4
+ /usr/bin/rm -rf /builddir/build/BUILDROOT/python-ckan-2.10.4-1.fc40.x86_64
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(rmbuild): /bin/sh -e /var/tmp/rpm-tmp.8kypnD
+ umask 022
+ cd /builddir/build/BUILD
+ rm -rf /builddir/build/BUILD/ckan-2.10.4-SPECPARTS
+ rm -rf ckan-2.10.4 ckan-2.10.4.gemspec
+ RPM_EC=0
++ jobs -p
+ exit 0
Finish: rpmbuild python-ckan-2.10.4-1.fc40.src.rpm
Finish: build phase for python-ckan-2.10.4-1.fc40.src.rpm
INFO: chroot_scan: 1 files copied to /var/lib/copr-rpmbuild/results/chroot_scan
INFO: /var/lib/mock/fedora-40-x86_64-1710336054.221965/root/var/log/dnf5.log
INFO: Done(/var/lib/copr-rpmbuild/results/python-ckan-2.10.4-1.fc40.src.rpm) Config(child) 0 minutes 57 seconds
INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results
INFO: Cleaning up build root ('cleanup_on_success=True')
Start: clean chroot
INFO: unmounting tmpfs.
Finish: clean chroot
Finish: run
Running RPMResults tool
Package info:
{
    "packages": [
        {
            "name": "python3-ckan",
            "epoch": null,
            "version": "2.10.4",
            "release": "1.fc40",
            "arch": "noarch"
        },
        {
            "name": "python-ckan",
            "epoch": null,
            "version": "2.10.4",
            "release": "1.fc40",
            "arch": "src"
        }
    ]
}
RPMResults finished