Warning: Permanently added '3.238.78.52' (ECDSA) to the list of known hosts. Running: /usr/bin/copr-rpmbuild --verbose --drop-resultdir --build-id 1913346 --chroot epel-7-x86_64 --detached Version: 0.45 Task: {'bootstrap': 'off', 'build_id': 1913346, 'buildroot_pkgs': [], 'chroot': 'epel-7-x86_64', 'enable_net': True, 'git_hash': '9625ce423595a450c5be2a09f3d715a8cad59dea', 'git_repo': 'https://copr-dist-git.fedorainfracloud.org/git/averbyts/fastjet/TheP8I.git', 'isolation': 'default', 'memory_reqs': 2048, 'package_name': 'TheP8I', 'package_version': '2.0.1-1.fc33', 'project_dirname': 'fastjet', 'project_name': 'fastjet', 'project_owner': 'averbyts', 'repos': [{'baseurl': 'https://download.copr.fedorainfracloud.org/results/averbyts/fastjet/epel-7-x86_64/', 'id': 'copr_base', 'name': 'Copr repository'}, {'baseurl': 'http://mirror.centos.org/centos/7/sclo/$basearch/sclo/', 'id': 'http_mirror_centos_org_centos_7_sclo_basearch_sclo', 'name': 'Additional repo http_mirror_centos_org_centos_7_sclo_basearch_sclo'}], 'sandbox': 'averbyts/fastjet--averbyts', 'source_json': {}, 'source_type': None, 'submitter': 'averbyts', 'task_id': '1913346-epel-7-x86_64', 'timeout': 18000, 'uses_devel_repo': False, 'with_opts': [], 'without_opts': []} Running: git clone https://copr-dist-git.fedorainfracloud.org/git/averbyts/fastjet/TheP8I.git /tmp/copr-rpmbuild-x41l30bo/obtain-sources/TheP8I --depth 500 --no-single-branch cmd: ['git', 'clone', 'https://copr-dist-git.fedorainfracloud.org/git/averbyts/fastjet/TheP8I.git', '/tmp/copr-rpmbuild-x41l30bo/obtain-sources/TheP8I', '--depth', '500', '--no-single-branch'] cwd: . rc: 0 stdout: stderr: Cloning into '/tmp/copr-rpmbuild-x41l30bo/obtain-sources/TheP8I'... Running: git checkout 9625ce423595a450c5be2a09f3d715a8cad59dea cmd: ['git', 'checkout', '9625ce423595a450c5be2a09f3d715a8cad59dea'] cwd: /tmp/copr-rpmbuild-x41l30bo/obtain-sources/TheP8I rc: 0 stdout: stderr: Note: switching to '9625ce423595a450c5be2a09f3d715a8cad59dea'. 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 Or undo this operation with: git switch - Turn off this advice by setting config variable advice.detachedHead to false HEAD is now at 9625ce4 automatic import of TheP8I Running: copr-distgit-client sources cmd: ['copr-distgit-client', 'sources'] cwd: /tmp/copr-rpmbuild-x41l30bo/obtain-sources/TheP8I rc: 0 stdout: /usr/bin/tail: /var/lib/copr-rpmbuild/main.log: file truncated stderr: INFO: Reading stdout from command: git rev-parse --abbrev-ref HEAD INFO: Reading stdout from command: git rev-parse HEAD INFO: Reading sources specification file: sources INFO: Downloading TheP8I-2.0.0.tar.gz INFO: Calling: curl -H Pragma: -o TheP8I-2.0.0.tar.gz --location --remote-time --show-error --fail https://copr-dist-git.fedorainfracloud.org/repo/pkgs/averbyts/fastjet/TheP8I/TheP8I-2.0.0.tar.gz/md5/1092f128f994ace885d4ec8f39fd621d/TheP8I-2.0.0.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 440k 100 440k 0 0 7720k 0 --:--:-- --:--:-- --:--:-- 7720k INFO: Reading stdout from command: md5sum TheP8I-2.0.0.tar.gz Running (timeout=18000): unbuffer mock --buildsrpm --spec /tmp/copr-rpmbuild-x41l30bo/obtain-sources/TheP8I/TheP8I.spec --sources /tmp/copr-rpmbuild-x41l30bo/obtain-sources/TheP8I --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1611774954.410978 -r /var/lib/copr-rpmbuild/results/configs/child.cfg INFO: mock.py version 2.9 starting (python version = 3.9.1, NVR = mock-2.9-1.fc33)... WARNING: Not using '/usr/bin/yum', it is symlink to '/usr/bin/dnf-3' INFO: Using 'dnf' instead of 'yum' 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(/tmp/copr-rpmbuild-x41l30bo/obtain-sources/TheP8I/TheP8I.spec) Config(epel-7-x86_64) Start: clean chroot Finish: clean chroot Start: chroot init INFO: mounting tmpfs at /var/lib/mock/epel-7-x86_64-1611774954.410978/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 Mock Version: 2.9 INFO: Mock Version: 2.9 Start: dnf install No matches found for the following disable plugin patterns: local, spacewalk Copr repository 16 MB/s | 1.2 MB 00:00 Additional repo http_mirror_centos_org_centos_7 2.3 MB/s | 1.1 MB 00:00 CentOS-7 - Base 28 MB/s | 10 MB 00:00 CentOS-7 - Updates 31 MB/s | 5.5 MB 00:00 CentOS-7 - Extras 2.0 MB/s | 283 kB 00:00 CentOS-7 - SCLo sclo 3.9 MB/s | 1.1 MB 00:00 CentOS-7 - SCLo rh 3.9 MB/s | 15 MB 00:03 Extra Packages for Enterprise Linux 7 - x86_64 3.1 MB/s | 16 MB 00:05 Dependencies resolved. ================================================================================ Package Arch Version Repo Size ================================================================================ Installing group/module packages: bash  x86_64 4.2.46-34.el7 base 1.0 M bzip2  x86_64 1.0.6-13.el7 base 52 k coreutils  x86_64 8.22-24.el7_9.2 updates 3.3 M cpio  x86_64 2.11-28.el7 base 211 k diffutils  x86_64 3.3-5.el7 base 322 k epel-release  noarch 7-13 epel 15 k epel-rpm-macros  noarch 7-29 epel 17 k findutils  x86_64 1:4.5.11-6.el7 base 559 k gawk  x86_64 4.0.2-4.el7_3.1 base 874 k gcc  x86_64 4.8.5-44.el7 base 16 M gcc-c++  x86_64 4.8.5-44.el7 base 7.2 M grep  x86_64 2.20-3.el7 base 344 k gzip  x86_64 1.5-10.el7 base 130 k info  x86_64 5.1-5.el7 base 233 k make  x86_64 1:3.82-24.el7 base 421 k patch  x86_64 2.7.1-12.el7_7 base 111 k redhat-rpm-config  noarch 9.1.0-88.el7.centos base 81 k rpm-build  x86_64 4.11.3-45.el7 base 149 k sed  x86_64 4.2.2-7.el7 base 231 k shadow-utils  x86_64 2:4.6-5.el7 base 1.2 M tar  x86_64 2:1.26-35.el7 base 846 k unzip  x86_64 6.0-21.el7 base 171 k util-linux  x86_64 2.23.2-65.el7 base 2.0 M which  x86_64 2.20-7.el7 base 41 k xz  x86_64 5.2.2-1.el7 base 229 k Installing dependencies: acl  x86_64 2.2.51-15.el7 base 81 k audit-libs  x86_64 2.8.5-4.el7 base 102 k basesystem  noarch 10.0-7.el7.centos base 5.0 k binutils  x86_64 2.27-44.base.el7 base 5.9 M bzip2-libs  x86_64 1.0.6-13.el7 base 40 k ca-certificates  noarch 2020.2.41-70.0.el7_8 base 382 k centos-release  x86_64 7-9.2009.1.el7.centos updates 27 k chkconfig  x86_64 1.7.6-1.el7 base 182 k cpp  x86_64 4.8.5-44.el7 base 5.9 M cracklib  x86_64 2.9.0-11.el7 base 80 k cracklib-dicts  x86_64 2.9.0-11.el7 base 3.6 M cryptsetup-libs  x86_64 2.0.3-6.el7 base 339 k curl  x86_64 7.29.0-59.el7_9.1 updates 271 k cyrus-sasl-lib  x86_64 2.1.26-23.el7 base 155 k dbus  x86_64 1:1.10.24-15.el7 base 245 k dbus-libs  x86_64 1:1.10.24-15.el7 base 169 k device-mapper  x86_64 7:1.02.170-6.el7_9.3 updates 297 k device-mapper-libs  x86_64 7:1.02.170-6.el7_9.3 updates 325 k dracut  x86_64 033-572.el7 base 329 k dwz  x86_64 0.11-3.el7 base 99 k elfutils  x86_64 0.176-5.el7 base 308 k elfutils-default-yama-scope  noarch 0.176-5.el7 base 33 k elfutils-libelf  x86_64 0.176-5.el7 base 195 k elfutils-libs  x86_64 0.176-5.el7 base 291 k expat  x86_64 2.1.0-12.el7 base 81 k file  x86_64 5.11-37.el7 base 57 k file-libs  x86_64 5.11-37.el7 base 340 k filesystem  x86_64 3.2-25.el7 base 1.0 M gdb  x86_64 7.6.1-120.el7 base 2.4 M gdbm  x86_64 1.10-8.el7 base 70 k glib2  x86_64 2.56.1-8.el7 updates 2.5 M glibc  x86_64 2.17-317.el7 base 3.6 M glibc-common  x86_64 2.17-317.el7 base 11 M glibc-devel  x86_64 2.17-317.el7 base 1.1 M glibc-headers  x86_64 2.17-317.el7 base 690 k gmp  x86_64 1:6.0.0-15.el7 base 281 k gnupg2  x86_64 2.0.22-5.el7_5 base 1.5 M groff-base  x86_64 1.22.2-8.el7 base 942 k hardlink  x86_64 1:1.0-19.el7 base 14 k json-c  x86_64 0.11-4.el7_0 base 31 k kernel-headers  x86_64 3.10.0-1160.11.1.el7 updates 9.0 M keyutils-libs  x86_64 1.5.8-3.el7 base 25 k kmod  x86_64 20-28.el7 base 123 k kmod-libs  x86_64 20-28.el7 base 51 k kpartx  x86_64 0.4.9-134.el7_9 updates 81 k krb5-libs  x86_64 1.15.1-50.el7 base 809 k libacl  x86_64 2.2.51-15.el7 base 27 k libassuan  x86_64 2.1.0-3.el7 base 63 k libattr  x86_64 2.4.46-13.el7 base 18 k libblkid  x86_64 2.23.2-65.el7 base 183 k libcap  x86_64 2.22-11.el7 base 47 k libcap-ng  x86_64 0.7.5-4.el7 base 25 k libcom_err  x86_64 1.42.9-19.el7 base 42 k libcurl  x86_64 7.29.0-59.el7_9.1 updates 223 k libdb  x86_64 5.3.21-25.el7 base 720 k libdb-utils  x86_64 5.3.21-25.el7 base 132 k libffi  x86_64 3.0.13-19.el7 base 30 k libgcc  x86_64 4.8.5-44.el7 base 103 k libgcrypt  x86_64 1.5.3-14.el7 base 263 k libgomp  x86_64 4.8.5-44.el7 base 159 k libgpg-error  x86_64 1.12-3.el7 base 87 k libidn  x86_64 1.28-4.el7 base 209 k libmount  x86_64 2.23.2-65.el7 base 184 k libmpc  x86_64 1.0.1-3.el7 base 51 k libpwquality  x86_64 1.2.3-5.el7 base 85 k libselinux  x86_64 2.5-15.el7 base 162 k libsemanage  x86_64 2.5-14.el7 base 151 k libsepol  x86_64 2.5-10.el7 base 297 k libsmartcols  x86_64 2.23.2-65.el7 base 142 k libssh2  x86_64 1.8.0-4.el7 base 88 k libstdc++  x86_64 4.8.5-44.el7 base 306 k libstdc++-devel  x86_64 4.8.5-44.el7 base 1.5 M libtasn1  x86_64 4.10-1.el7 base 320 k libuser  x86_64 0.60-9.el7 base 400 k libutempter  x86_64 1.1.6-4.el7 base 25 k libuuid  x86_64 2.23.2-65.el7 base 84 k libverto  x86_64 0.2.5-4.el7 base 16 k libxml2  x86_64 2.9.1-6.el7.5 base 668 k lua  x86_64 5.1.4-15.el7 base 201 k lua-srpm-macros  noarch 1-2.el7 epel 4.7 k lz4  x86_64 1.8.3-1.el7 base 85 k mpfr  x86_64 3.1.1-4.el7 base 203 k ncurses  x86_64 5.9-14.20130511.el7_4 base 304 k ncurses-base  noarch 5.9-14.20130511.el7_4 base 68 k ncurses-libs  x86_64 5.9-14.20130511.el7_4 base 316 k nspr  x86_64 4.25.0-2.el7_9 updates 127 k nss  x86_64 3.53.1-3.el7_9 updates 869 k nss-pem  x86_64 1.0.3-7.el7 base 74 k nss-softokn  x86_64 3.53.1-6.el7_9 updates 354 k nss-softokn-freebl  x86_64 3.53.1-6.el7_9 updates 322 k nss-sysinit  x86_64 3.53.1-3.el7_9 updates 65 k nss-tools  x86_64 3.53.1-3.el7_9 updates 535 k nss-util  x86_64 3.53.1-1.el7_9 updates 79 k openldap  x86_64 2.4.44-22.el7 base 356 k openssl-libs  x86_64 1:1.0.2k-21.el7_9 updates 1.2 M p11-kit  x86_64 0.23.5-3.el7 base 252 k p11-kit-trust  x86_64 0.23.5-3.el7 base 129 k pam  x86_64 1.1.8-23.el7 base 721 k pcre  x86_64 8.32-17.el7 base 422 k perl  x86_64 4:5.16.3-297.el7 base 8.0 M perl-Carp  noarch 1.26-244.el7 base 19 k perl-Encode  x86_64 2.51-7.el7 base 1.5 M perl-Exporter  noarch 5.68-3.el7 base 28 k perl-File-Path  noarch 2.09-2.el7 base 26 k perl-File-Temp  noarch 0.23.01-3.el7 base 56 k perl-Filter  x86_64 1.49-3.el7 base 76 k perl-Getopt-Long  noarch 2.40-3.el7 base 56 k perl-HTTP-Tiny  noarch 0.033-3.el7 base 38 k perl-PathTools  x86_64 3.40-5.el7 base 82 k perl-Pod-Escapes  noarch 1:1.04-297.el7 base 52 k perl-Pod-Perldoc  noarch 3.20-4.el7 base 87 k perl-Pod-Simple  noarch 1:3.28-4.el7 base 216 k perl-Pod-Usage  noarch 1.63-3.el7 base 27 k perl-Scalar-List-Utils  x86_64 1.27-248.el7 base 36 k perl-Socket  x86_64 2.010-5.el7 base 49 k perl-Storable  x86_64 2.45-3.el7 base 77 k perl-Text-ParseWords  noarch 3.29-4.el7 base 14 k perl-Thread-Queue  noarch 3.02-2.el7 base 17 k perl-Time-HiRes  x86_64 4:1.9725-3.el7 base 45 k perl-Time-Local  noarch 1.2300-2.el7 base 24 k perl-constant  noarch 1.27-2.el7 base 19 k perl-libs  x86_64 4:5.16.3-297.el7 base 689 k perl-macros  x86_64 4:5.16.3-297.el7 base 44 k perl-parent  noarch 1:0.225-244.el7 base 12 k perl-podlators  noarch 2.5.1-3.el7 base 112 k perl-srpm-macros  noarch 1-8.el7 base 4.6 k perl-threads  x86_64 1.87-4.el7 base 49 k perl-threads-shared  x86_64 1.43-6.el7 base 39 k pinentry  x86_64 0.8.1-17.el7 base 73 k pkgconfig  x86_64 1:0.27.1-4.el7 base 54 k popt  x86_64 1.13-16.el7 base 42 k procps-ng  x86_64 3.3.10-28.el7 base 291 k pth  x86_64 2.0.7-23.el7 base 89 k python-libs  x86_64 2.7.5-90.el7 updates 5.6 M python-rpm-macros  noarch 3-34.el7 base 9.1 k python-srpm-macros  noarch 3-34.el7 base 8.8 k python2-rpm-macros  noarch 3-34.el7 base 8.1 k qrencode-libs  x86_64 3.4.1-3.el7 base 50 k readline  x86_64 6.2-11.el7 base 193 k rpm  x86_64 4.11.3-45.el7 base 1.2 M rpm-build-libs  x86_64 4.11.3-45.el7 base 107 k rpm-libs  x86_64 4.11.3-45.el7 base 278 k setup  noarch 2.8.71-11.el7 base 166 k shared-mime-info  x86_64 1.8-5.el7 base 312 k sqlite  x86_64 3.7.17-8.el7_7.1 base 394 k systemd  x86_64 219-78.el7_9.2 updates 5.1 M systemd-libs  x86_64 219-78.el7_9.2 updates 418 k tzdata  noarch 2021a-1.el7 updates 501 k ustr  x86_64 1.0.4-16.el7 base 92 k xz-libs  x86_64 5.2.2-1.el7 base 103 k zip  x86_64 3.0-11.el7 base 260 k zlib  x86_64 1.2.7-18.el7 base 90 k Installing Groups: Buildsystem building group Transaction Summary ================================================================================ Install 177 Packages Total download size: 131 M Installed size: 563 M Downloading Packages: (1/177): basesystem-10.0-7.el7.centos.noarch.rp 384 kB/s | 5.0 kB 00:00 (2/177): audit-libs-2.8.5-4.el7.x86_64.rpm 6.3 MB/s | 102 kB 00:00 (3/177): acl-2.2.51-15.el7.x86_64.rpm 4.4 MB/s | 81 kB 00:00 (4/177): bzip2-1.0.6-13.el7.x86_64.rpm 12 MB/s | 52 kB 00:00 (5/177): bzip2-libs-1.0.6-13.el7.x86_64.rpm 12 MB/s | 40 kB 00:00 (6/177): bash-4.2.46-34.el7.x86_64.rpm 52 MB/s | 1.0 MB 00:00 (7/177): ca-certificates-2020.2.41-70.0.el7_8.n 32 MB/s | 382 kB 00:00 (8/177): chkconfig-1.7.6-1.el7.x86_64.rpm 26 MB/s | 182 kB 00:00 (9/177): cpio-2.11-28.el7.x86_64.rpm 33 MB/s | 211 kB 00:00 (10/177): cracklib-2.9.0-11.el7.x86_64.rpm 20 MB/s | 80 kB 00:00 (11/177): cracklib-dicts-2.9.0-11.el7.x86_64.rp 68 MB/s | 3.6 MB 00:00 (12/177): binutils-2.27-44.base.el7.x86_64.rpm 53 MB/s | 5.9 MB 00:00 (13/177): cryptsetup-libs-2.0.3-6.el7.x86_64.rp 12 MB/s | 339 kB 00:00 (14/177): cyrus-sasl-lib-2.1.26-23.el7.x86_64.r 25 MB/s | 155 kB 00:00 (15/177): dbus-1.10.24-15.el7.x86_64.rpm 37 MB/s | 245 kB 00:00 (16/177): dbus-libs-1.10.24-15.el7.x86_64.rpm 21 MB/s | 169 kB 00:00 (17/177): diffutils-3.3-5.el7.x86_64.rpm 41 MB/s | 322 kB 00:00 (18/177): dracut-033-572.el7.x86_64.rpm 35 MB/s | 329 kB 00:00 (19/177): dwz-0.11-3.el7.x86_64.rpm 16 MB/s | 99 kB 00:00 (20/177): elfutils-default-yama-scope-0.176-5.e 10 MB/s | 33 kB 00:00 (21/177): elfutils-0.176-5.el7.x86_64.rpm 38 MB/s | 308 kB 00:00 (22/177): elfutils-libelf-0.176-5.el7.x86_64.rp 30 MB/s | 195 kB 00:00 (23/177): expat-2.1.0-12.el7.x86_64.rpm 25 MB/s | 81 kB 00:00 (24/177): elfutils-libs-0.176-5.el7.x86_64.rpm 30 MB/s | 291 kB 00:00 (25/177): file-5.11-37.el7.x86_64.rpm 20 MB/s | 57 kB 00:00 (26/177): file-libs-5.11-37.el7.x86_64.rpm 39 MB/s | 340 kB 00:00 (27/177): cpp-4.8.5-44.el7.x86_64.rpm 36 MB/s | 5.9 MB 00:00 (28/177): filesystem-3.2-25.el7.x86_64.rpm 26 MB/s | 1.0 MB 00:00 (29/177): findutils-4.5.11-6.el7.x86_64.rpm 16 MB/s | 559 kB 00:00 (30/177): gawk-4.0.2-4.el7_3.1.x86_64.rpm 41 MB/s | 874 kB 00:00 (31/177): gdb-7.6.1-120.el7.x86_64.rpm 61 MB/s | 2.4 MB 00:00 (32/177): gdbm-1.10-8.el7.x86_64.rpm 29 MB/s | 70 kB 00:00 (33/177): glibc-2.17-317.el7.x86_64.rpm 53 MB/s | 3.6 MB 00:00 (34/177): gcc-c++-4.8.5-44.el7.x86_64.rpm 43 MB/s | 7.2 MB 00:00 (35/177): glibc-devel-2.17-317.el7.x86_64.rpm 43 MB/s | 1.1 MB 00:00 (36/177): glibc-headers-2.17-317.el7.x86_64.rpm 52 MB/s | 690 kB 00:00 (37/177): gmp-6.0.0-15.el7.x86_64.rpm 41 MB/s | 281 kB 00:00 (38/177): gnupg2-2.0.22-5.el7_5.x86_64.rpm 66 MB/s | 1.5 MB 00:00 (39/177): grep-2.20-3.el7.x86_64.rpm 38 MB/s | 344 kB 00:00 (40/177): gcc-4.8.5-44.el7.x86_64.rpm 51 MB/s | 16 MB 00:00 (41/177): groff-base-1.22.2-8.el7.x86_64.rpm 12 MB/s | 942 kB 00:00 (42/177): gzip-1.5-10.el7.x86_64.rpm 16 MB/s | 130 kB 00:00 (43/177): hardlink-1.0-19.el7.x86_64.rpm 5.4 MB/s | 14 kB 00:00 (44/177): json-c-0.11-4.el7_0.x86_64.rpm 8.8 MB/s | 31 kB 00:00 (45/177): info-5.1-5.el7.x86_64.rpm 30 MB/s | 233 kB 00:00 (46/177): keyutils-libs-1.5.8-3.el7.x86_64.rpm 7.0 MB/s | 25 kB 00:00 (47/177): kmod-20-28.el7.x86_64.rpm 38 MB/s | 123 kB 00:00 (48/177): kmod-libs-20-28.el7.x86_64.rpm 10 MB/s | 51 kB 00:00 (49/177): libacl-2.2.51-15.el7.x86_64.rpm 7.6 MB/s | 27 kB 00:00 (50/177): libassuan-2.1.0-3.el7.x86_64.rpm 14 MB/s | 63 kB 00:00 (51/177): libattr-2.4.46-13.el7.x86_64.rpm 6.4 MB/s | 18 kB 00:00 (52/177): krb5-libs-1.15.1-50.el7.x86_64.rpm 39 MB/s | 809 kB 00:00 (53/177): libblkid-2.23.2-65.el7.x86_64.rpm 24 MB/s | 183 kB 00:00 (54/177): libcap-2.22-11.el7.x86_64.rpm 13 MB/s | 47 kB 00:00 (55/177): libcap-ng-0.7.5-4.el7.x86_64.rpm 8.2 MB/s | 25 kB 00:00 (56/177): libcom_err-1.42.9-19.el7.x86_64.rpm 11 MB/s | 42 kB 00:00 (57/177): libdb-utils-5.3.21-25.el7.x86_64.rpm 26 MB/s | 132 kB 00:00 (58/177): libffi-3.0.13-19.el7.x86_64.rpm 13 MB/s | 30 kB 00:00 (59/177): libdb-5.3.21-25.el7.x86_64.rpm 47 MB/s | 720 kB 00:00 (60/177): libgcc-4.8.5-44.el7.x86_64.rpm 18 MB/s | 103 kB 00:00 (61/177): glibc-common-2.17-317.el7.x86_64.rpm 38 MB/s | 11 MB 00:00 (62/177): libgomp-4.8.5-44.el7.x86_64.rpm 3.4 MB/s | 159 kB 00:00 (63/177): libgcrypt-1.5.3-14.el7.x86_64.rpm 5.2 MB/s | 263 kB 00:00 (64/177): libgpg-error-1.12-3.el7.x86_64.rpm 14 MB/s | 87 kB 00:00 (65/177): libidn-1.28-4.el7.x86_64.rpm 35 MB/s | 209 kB 00:00 (66/177): libmpc-1.0.1-3.el7.x86_64.rpm 15 MB/s | 51 kB 00:00 (67/177): libmount-2.23.2-65.el7.x86_64.rpm 26 MB/s | 184 kB 00:00 (68/177): libpwquality-1.2.3-5.el7.x86_64.rpm 20 MB/s | 85 kB 00:00 (69/177): libselinux-2.5-15.el7.x86_64.rpm 28 MB/s | 162 kB 00:00 (70/177): libsepol-2.5-10.el7.x86_64.rpm 50 MB/s | 297 kB 00:00 (71/177): libsemanage-2.5-14.el7.x86_64.rpm 19 MB/s | 151 kB 00:00 (72/177): libsmartcols-2.23.2-65.el7.x86_64.rpm 22 MB/s | 142 kB 00:00 (73/177): libssh2-1.8.0-4.el7.x86_64.rpm 16 MB/s | 88 kB 00:00 (74/177): libstdc++-4.8.5-44.el7.x86_64.rpm 35 MB/s | 306 kB 00:00 (75/177): libtasn1-4.10-1.el7.x86_64.rpm 31 MB/s | 320 kB 00:00 (76/177): libutempter-1.1.6-4.el7.x86_64.rpm 8.7 MB/s | 25 kB 00:00 (77/177): libuser-0.60-9.el7.x86_64.rpm 32 MB/s | 400 kB 00:00 (78/177): libuuid-2.23.2-65.el7.x86_64.rpm 17 MB/s | 84 kB 00:00 (79/177): libverto-0.2.5-4.el7.x86_64.rpm 5.4 MB/s | 16 kB 00:00 (80/177): libstdc++-devel-4.8.5-44.el7.x86_64.r 44 MB/s | 1.5 MB 00:00 (81/177): lua-5.1.4-15.el7.x86_64.rpm 17 MB/s | 201 kB 00:00 (82/177): lz4-1.8.3-1.el7.x86_64.rpm 24 MB/s | 85 kB 00:00 (83/177): libxml2-2.9.1-6.el7.5.x86_64.rpm 32 MB/s | 668 kB 00:00 (84/177): mpfr-3.1.1-4.el7.x86_64.rpm 27 MB/s | 203 kB 00:00 (85/177): make-3.82-24.el7.x86_64.rpm 31 MB/s | 421 kB 00:00 (86/177): ncurses-base-5.9-14.20130511.el7_4.no 14 MB/s | 68 kB 00:00 (87/177): ncurses-5.9-14.20130511.el7_4.x86_64. 30 MB/s | 304 kB 00:00 (88/177): nss-pem-1.0.3-7.el7.x86_64.rpm 19 MB/s | 74 kB 00:00 (89/177): ncurses-libs-5.9-14.20130511.el7_4.x8 36 MB/s | 316 kB 00:00 (90/177): p11-kit-0.23.5-3.el7.x86_64.rpm 40 MB/s | 252 kB 00:00 (91/177): openldap-2.4.44-22.el7.x86_64.rpm 32 MB/s | 356 kB 00:00 (92/177): p11-kit-trust-0.23.5-3.el7.x86_64.rpm 17 MB/s | 129 kB 00:00 (93/177): patch-2.7.1-12.el7_7.x86_64.rpm 29 MB/s | 111 kB 00:00 (94/177): pam-1.1.8-23.el7.x86_64.rpm 55 MB/s | 721 kB 00:00 (95/177): perl-Carp-1.26-244.el7.noarch.rpm 7.5 MB/s | 19 kB 00:00 (96/177): perl-Encode-2.51-7.el7.x86_64.rpm 78 MB/s | 1.5 MB 00:00 (97/177): perl-Exporter-5.68-3.el7.noarch.rpm 11 MB/s | 28 kB 00:00 (98/177): perl-File-Path-2.09-2.el7.noarch.rpm 8.5 MB/s | 26 kB 00:00 (99/177): pcre-8.32-17.el7.x86_64.rpm 10 MB/s | 422 kB 00:00 (100/177): perl-File-Temp-0.23.01-3.el7.noarch. 13 MB/s | 56 kB 00:00 (101/177): perl-Filter-1.49-3.el7.x86_64.rpm 29 MB/s | 76 kB 00:00 (102/177): perl-HTTP-Tiny-0.033-3.el7.noarch.rp 20 MB/s | 38 kB 00:00 (103/177): perl-Getopt-Long-2.40-3.el7.noarch.r 11 MB/s | 56 kB 00:00 (104/177): perl-PathTools-3.40-5.el7.x86_64.rpm 34 MB/s | 82 kB 00:00 (105/177): perl-Pod-Perldoc-3.20-4.el7.noarch.r 28 MB/s | 87 kB 00:00 (106/177): perl-Pod-Escapes-1.04-297.el7.noarch 8.4 MB/s | 52 kB 00:00 (107/177): perl-Pod-Usage-1.63-3.el7.noarch.rpm 17 MB/s | 27 kB 00:00 (108/177): perl-Pod-Simple-3.28-4.el7.noarch.rp 45 MB/s | 216 kB 00:00 (109/177): perl-Scalar-List-Utils-1.27-248.el7. 11 MB/s | 36 kB 00:00 (110/177): perl-Socket-2.010-5.el7.x86_64.rpm 19 MB/s | 49 kB 00:00 (111/177): perl-Storable-2.45-3.el7.x86_64.rpm 30 MB/s | 77 kB 00:00 (112/177): perl-Text-ParseWords-3.29-4.el7.noar 6.2 MB/s | 14 kB 00:00 (113/177): perl-Time-HiRes-1.9725-3.el7.x86_64. 13 MB/s | 45 kB 00:00 (114/177): perl-Thread-Queue-3.02-2.el7.noarch. 3.0 MB/s | 17 kB 00:00 (115/177): perl-Time-Local-1.2300-2.el7.noarch. 15 MB/s | 24 kB 00:00 (116/177): perl-constant-1.27-2.el7.noarch.rpm 11 MB/s | 19 kB 00:00 (117/177): perl-macros-5.16.3-297.el7.x86_64.rp 13 MB/s | 44 kB 00:00 (118/177): perl-parent-0.225-244.el7.noarch.rpm 9.2 MB/s | 12 kB 00:00 (119/177): perl-libs-5.16.3-297.el7.x86_64.rpm 53 MB/s | 689 kB 00:00 (120/177): perl-podlators-2.5.1-3.el7.noarch.rp 16 MB/s | 112 kB 00:00 (121/177): perl-srpm-macros-1-8.el7.noarch.rpm 2.1 MB/s | 4.6 kB 00:00 (122/177): perl-threads-1.87-4.el7.x86_64.rpm 27 MB/s | 49 kB 00:00 (123/177): perl-threads-shared-1.43-6.el7.x86_6 17 MB/s | 39 kB 00:00 (124/177): pkgconfig-0.27.1-4.el7.x86_64.rpm 19 MB/s | 54 kB 00:00 (125/177): pinentry-0.8.1-17.el7.x86_64.rpm 13 MB/s | 73 kB 00:00 (126/177): popt-1.13-16.el7.x86_64.rpm 12 MB/s | 42 kB 00:00 (127/177): procps-ng-3.3.10-28.el7.x86_64.rpm 46 MB/s | 291 kB 00:00 (128/177): pth-2.0.7-23.el7.x86_64.rpm 17 MB/s | 89 kB 00:00 (129/177): python-rpm-macros-3-34.el7.noarch.rp 3.7 MB/s | 9.1 kB 00:00 (130/177): python-srpm-macros-3-34.el7.noarch.r 4.7 MB/s | 8.8 kB 00:00 (131/177): python2-rpm-macros-3-34.el7.noarch.r 3.8 MB/s | 8.1 kB 00:00 (132/177): qrencode-libs-3.4.1-3.el7.x86_64.rpm 7.4 MB/s | 50 kB 00:00 (133/177): readline-6.2-11.el7.x86_64.rpm 18 MB/s | 193 kB 00:00 (134/177): redhat-rpm-config-9.1.0-88.el7.cento 15 MB/s | 81 kB 00:00 (135/177): perl-5.16.3-297.el7.x86_64.rpm 53 MB/s | 8.0 MB 00:00 (136/177): rpm-build-4.11.3-45.el7.x86_64.rpm 4.2 MB/s | 149 kB 00:00 (137/177): rpm-build-libs-4.11.3-45.el7.x86_64. 22 MB/s | 107 kB 00:00 (138/177): rpm-libs-4.11.3-45.el7.x86_64.rpm 49 MB/s | 278 kB 00:00 (139/177): sed-4.2.2-7.el7.x86_64.rpm 32 MB/s | 231 kB 00:00 (140/177): rpm-4.11.3-45.el7.x86_64.rpm 22 MB/s | 1.2 MB 00:00 (141/177): setup-2.8.71-11.el7.noarch.rpm 13 MB/s | 166 kB 00:00 (142/177): shared-mime-info-1.8-5.el7.x86_64.rp 46 MB/s | 312 kB 00:00 (143/177): sqlite-3.7.17-8.el7_7.1.x86_64.rpm 40 MB/s | 394 kB 00:00 (144/177): unzip-6.0-21.el7.x86_64.rpm 54 MB/s | 171 kB 00:00 (145/177): shadow-utils-4.6-5.el7.x86_64.rpm 41 MB/s | 1.2 MB 00:00 (146/177): ustr-1.0.4-16.el7.x86_64.rpm 11 MB/s | 92 kB 00:00 (147/177): tar-1.26-35.el7.x86_64.rpm 37 MB/s | 846 kB 00:00 (148/177): which-2.20-7.el7.x86_64.rpm 7.2 MB/s | 41 kB 00:00 (149/177): xz-libs-5.2.2-1.el7.x86_64.rpm 31 MB/s | 103 kB 00:00 (150/177): xz-5.2.2-1.el7.x86_64.rpm 34 MB/s | 229 kB 00:00 (151/177): zlib-1.2.7-18.el7.x86_64.rpm 23 MB/s | 90 kB 00:00 (152/177): zip-3.0-11.el7.x86_64.rpm 32 MB/s | 260 kB 00:00 (153/177): centos-release-7-9.2009.1.el7.centos 9.5 MB/s | 27 kB 00:00 (154/177): curl-7.29.0-59.el7_9.1.x86_64.rpm 26 MB/s | 271 kB 00:00 (155/177): util-linux-2.23.2-65.el7.x86_64.rpm 45 MB/s | 2.0 MB 00:00 (156/177): device-mapper-1.02.170-6.el7_9.3.x86 21 MB/s | 297 kB 00:00 (157/177): device-mapper-libs-1.02.170-6.el7_9. 38 MB/s | 325 kB 00:00 (158/177): coreutils-8.22-24.el7_9.2.x86_64.rpm 54 MB/s | 3.3 MB 00:00 (159/177): kpartx-0.4.9-134.el7_9.x86_64.rpm 19 MB/s | 81 kB 00:00 (160/177): libcurl-7.29.0-59.el7_9.1.x86_64.rpm 41 MB/s | 223 kB 00:00 (161/177): nspr-4.25.0-2.el7_9.x86_64.rpm 41 MB/s | 127 kB 00:00 (162/177): glib2-2.56.1-8.el7.x86_64.rpm 34 MB/s | 2.5 MB 00:00 (163/177): nss-3.53.1-3.el7_9.x86_64.rpm 30 MB/s | 869 kB 00:00 (164/177): nss-softokn-3.53.1-6.el7_9.x86_64.rp 34 MB/s | 354 kB 00:00 (165/177): nss-softokn-freebl-3.53.1-6.el7_9.x8 43 MB/s | 322 kB 00:00 (166/177): nss-sysinit-3.53.1-3.el7_9.x86_64.rp 15 MB/s | 65 kB 00:00 (167/177): nss-util-3.53.1-1.el7_9.x86_64.rpm 34 MB/s | 79 kB 00:00 (168/177): nss-tools-3.53.1-3.el7_9.x86_64.rpm 50 MB/s | 535 kB 00:00 (169/177): openssl-libs-1.0.2k-21.el7_9.x86_64. 58 MB/s | 1.2 MB 00:00 (170/177): kernel-headers-3.10.0-1160.11.1.el7. 53 MB/s | 9.0 MB 00:00 (171/177): systemd-libs-219-78.el7_9.2.x86_64.r 39 MB/s | 418 kB 00:00 (172/177): tzdata-2021a-1.el7.noarch.rpm 44 MB/s | 501 kB 00:00 (173/177): systemd-219-78.el7_9.2.x86_64.rpm 44 MB/s | 5.1 MB 00:00 (174/177): python-libs-2.7.5-90.el7.x86_64.rpm 36 MB/s | 5.6 MB 00:00 (175/177): lua-srpm-macros-1-2.el7.noarch.rpm 51 kB/s | 4.7 kB 00:00 (176/177): epel-release-7-13.noarch.rpm 103 kB/s | 15 kB 00:00 (177/177): epel-rpm-macros-7-29.noarch.rpm 123 kB/s | 17 kB 00:00 -------------------------------------------------------------------------------- Total 80 MB/s | 131 MB 00:01 warning: /var/lib/mock/epel-7-x86_64-1611774954.410978/root/var/cache/dnf/base-65e58d35cd0ad0ed/packages/acl-2.2.51-15.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY CentOS-7 - Base 1.6 MB/s | 1.7 kB 00:00 Importing GPG key 0xF4A80EB5: Userid : "CentOS-7 Key (CentOS 7 Official Signing Key) " Fingerprint: 6341 AB27 53D7 8A78 A7C2 7BB1 24C6 A8A7 F4A8 0EB5 From : /usr/share/distribution-gpg-keys/centos/RPM-GPG-KEY-CentOS-7 Key imported successfully warning: /var/lib/mock/epel-7-x86_64-1611774954.410978/root/var/cache/dnf/epel-b7d9da81043aa7ab/packages/epel-release-7-13.noarch.rpm: Header V4 RSA/SHA256 Signature, key ID 352c64e5: NOKEY Extra Packages for Enterprise Linux 7 - x86_64 1.6 MB/s | 1.6 kB 00:00 Importing GPG key 0x352C64E5: Userid : "Fedora EPEL (7) " Fingerprint: 91E9 7D7C 4A5E 96F1 7F3E 888F 6A2F AEA2 352C 64E5 From : /usr/share/distribution-gpg-keys/epel/RPM-GPG-KEY-EPEL-7 Key imported successfully Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Running scriptlet: filesystem-3.2-25.el7.x86_64 1/1 Preparing : 1/1 Installing : libgcc-4.8.5-44.el7.x86_64 1/177 Running scriptlet: libgcc-4.8.5-44.el7.x86_64 1/177 Installing : centos-release-7-9.2009.1.el7.centos.x86_64 2/177 Installing : setup-2.8.71-11.el7.noarch 3/177 Running scriptlet: setup-2.8.71-11.el7.noarch 3/177 Installing : filesystem-3.2-25.el7.x86_64 4/177 Installing : python-srpm-macros-3-34.el7.noarch 5/177 Installing : python-rpm-macros-3-34.el7.noarch 6/177 Installing : basesystem-10.0-7.el7.centos.noarch 7/177 Installing : tzdata-2021a-1.el7.noarch 8/177 Installing : kernel-headers-3.10.0-1160.11.1.el7.x86_64 9/177 Installing : python2-rpm-macros-3-34.el7.noarch 10/177 Installing : perl-srpm-macros-1-8.el7.noarch 11/177 Installing : ncurses-base-5.9-14.20130511.el7_4.noarch 12/177 Installing : glibc-common-2.17-317.el7.x86_64 13/177 Running scriptlet: glibc-common-2.17-317.el7.x86_64 13/177 Installing : nss-softokn-freebl-3.53.1-6.el7_9.x86_64 14/177 Running scriptlet: glibc-2.17-317.el7.x86_64 15/177 Installing : glibc-2.17-317.el7.x86_64 15/177 Running scriptlet: glibc-2.17-317.el7.x86_64 15/177 Installing : nspr-4.25.0-2.el7_9.x86_64 16/177 Running scriptlet: nspr-4.25.0-2.el7_9.x86_64 16/177 Installing : nss-util-3.53.1-1.el7_9.x86_64 17/177 Running scriptlet: nss-util-3.53.1-1.el7_9.x86_64 17/177 Installing : libstdc++-4.8.5-44.el7.x86_64 18/177 Running scriptlet: libstdc++-4.8.5-44.el7.x86_64 18/177 Installing : ncurses-libs-5.9-14.20130511.el7_4.x86_64 19/177 Running scriptlet: ncurses-libs-5.9-14.20130511.el7_4.x86_64 19/177 Installing : bash-4.2.46-34.el7.x86_64 20/177 Running scriptlet: bash-4.2.46-34.el7.x86_64 20/177 Installing : libsepol-2.5-10.el7.x86_64 21/177 Running scriptlet: libsepol-2.5-10.el7.x86_64 21/177 Installing : pcre-8.32-17.el7.x86_64 22/177 Running scriptlet: pcre-8.32-17.el7.x86_64 22/177 Installing : libselinux-2.5-15.el7.x86_64 23/177 Running scriptlet: libselinux-2.5-15.el7.x86_64 23/177 Installing : zlib-1.2.7-18.el7.x86_64 24/177 Running scriptlet: zlib-1.2.7-18.el7.x86_64 24/177 Installing : info-5.1-5.el7.x86_64 25/177 Running scriptlet: info-5.1-5.el7.x86_64 25/177 Installing : bzip2-libs-1.0.6-13.el7.x86_64 26/177 Running scriptlet: bzip2-libs-1.0.6-13.el7.x86_64 26/177 Installing : xz-libs-5.2.2-1.el7.x86_64 27/177 Running scriptlet: xz-libs-5.2.2-1.el7.x86_64 27/177 Installing : elfutils-libelf-0.176-5.el7.x86_64 28/177 Running scriptlet: elfutils-libelf-0.176-5.el7.x86_64 28/177 Installing : libdb-5.3.21-25.el7.x86_64 29/177 Running scriptlet: libdb-5.3.21-25.el7.x86_64 29/177 Installing : sed-4.2.2-7.el7.x86_64 30/177 Running scriptlet: sed-4.2.2-7.el7.x86_64 30/177 Installing : gmp-1:6.0.0-15.el7.x86_64 31/177 Running scriptlet: gmp-1:6.0.0-15.el7.x86_64 31/177 Installing : libattr-2.4.46-13.el7.x86_64 32/177 Running scriptlet: libattr-2.4.46-13.el7.x86_64 32/177 Installing : libacl-2.2.51-15.el7.x86_64 33/177 Running scriptlet: libacl-2.2.51-15.el7.x86_64 33/177 Installing : libcap-2.22-11.el7.x86_64 34/177 Running scriptlet: libcap-2.22-11.el7.x86_64 34/177 Installing : popt-1.13-16.el7.x86_64 35/177 Running scriptlet: popt-1.13-16.el7.x86_64 35/177 Installing : readline-6.2-11.el7.x86_64 36/177 Running scriptlet: readline-6.2-11.el7.x86_64 36/177 Installing : libgpg-error-1.12-3.el7.x86_64 37/177 Running scriptlet: libgpg-error-1.12-3.el7.x86_64 37/177 Installing : libgcrypt-1.5.3-14.el7.x86_64 38/177 Running scriptlet: libgcrypt-1.5.3-14.el7.x86_64 38/177 Installing : lua-5.1.4-15.el7.x86_64 39/177 Installing : chkconfig-1.7.6-1.el7.x86_64 40/177 Installing : mpfr-3.1.1-4.el7.x86_64 41/177 Running scriptlet: mpfr-3.1.1-4.el7.x86_64 41/177 Installing : grep-2.20-3.el7.x86_64 42/177 Running scriptlet: grep-2.20-3.el7.x86_64 42/177 Installing : libcom_err-1.42.9-19.el7.x86_64 43/177 Running scriptlet: libcom_err-1.42.9-19.el7.x86_64 43/177 Installing : libffi-3.0.13-19.el7.x86_64 44/177 Running scriptlet: libffi-3.0.13-19.el7.x86_64 44/177 Installing : libuuid-2.23.2-65.el7.x86_64 45/177 Running scriptlet: libuuid-2.23.2-65.el7.x86_64 45/177 Installing : libmpc-1.0.1-3.el7.x86_64 46/177 Running scriptlet: libmpc-1.0.1-3.el7.x86_64 46/177 Installing : xz-5.2.2-1.el7.x86_64 47/177 Installing : cpio-2.11-28.el7.x86_64 48/177 Running scriptlet: cpio-2.11-28.el7.x86_64 48/177 Installing : diffutils-3.3-5.el7.x86_64 49/177 Running scriptlet: diffutils-3.3-5.el7.x86_64 49/177 Installing : findutils-1:4.5.11-6.el7.x86_64 50/177 Running scriptlet: findutils-1:4.5.11-6.el7.x86_64 50/177 Installing : gawk-4.0.2-4.el7_3.1.x86_64 51/177 Running scriptlet: gawk-4.0.2-4.el7_3.1.x86_64 51/177 Installing : file-libs-5.11-37.el7.x86_64 52/177 Running scriptlet: file-libs-5.11-37.el7.x86_64 52/177 Installing : expat-2.1.0-12.el7.x86_64 53/177 Running scriptlet: expat-2.1.0-12.el7.x86_64 53/177 Installing : libcap-ng-0.7.5-4.el7.x86_64 54/177 Running scriptlet: libcap-ng-0.7.5-4.el7.x86_64 54/177 Installing : audit-libs-2.8.5-4.el7.x86_64 55/177 Running scriptlet: audit-libs-2.8.5-4.el7.x86_64 55/177 Installing : p11-kit-0.23.5-3.el7.x86_64 56/177 Running scriptlet: p11-kit-0.23.5-3.el7.x86_64 56/177 Installing : sqlite-3.7.17-8.el7_7.1.x86_64 57/177 Running scriptlet: sqlite-3.7.17-8.el7_7.1.x86_64 57/177 Installing : nss-softokn-3.53.1-6.el7_9.x86_64 58/177 Running scriptlet: nss-softokn-3.53.1-6.el7_9.x86_64 58/177 Installing : tar-2:1.26-35.el7.x86_64 59/177 Running scriptlet: tar-2:1.26-35.el7.x86_64 59/177 Installing : gdbm-1.10-8.el7.x86_64 60/177 Running scriptlet: gdbm-1.10-8.el7.x86_64 60/177 Installing : lz4-1.8.3-1.el7.x86_64 61/177 Running scriptlet: lz4-1.8.3-1.el7.x86_64 61/177 Installing : file-5.11-37.el7.x86_64 62/177 Installing : cpp-4.8.5-44.el7.x86_64 63/177 Running scriptlet: cpp-4.8.5-44.el7.x86_64 63/177 Running scriptlet: pinentry-0.8.1-17.el7.x86_64 64/177 Installing : pinentry-0.8.1-17.el7.x86_64 64/177 Running scriptlet: pinentry-0.8.1-17.el7.x86_64 64/177 Installing : libassuan-2.1.0-3.el7.x86_64 65/177 Running scriptlet: libassuan-2.1.0-3.el7.x86_64 65/177 Installing : acl-2.2.51-15.el7.x86_64 66/177 Installing : patch-2.7.1-12.el7_7.x86_64 67/177 Installing : groff-base-1.22.2-8.el7.x86_64 68/177 Installing : perl-HTTP-Tiny-0.033-3.el7.noarch 69/177 Installing : perl-parent-1:0.225-244.el7.noarch 70/177 Installing : perl-podlators-2.5.1-3.el7.noarch 71/177 Installing : perl-Pod-Perldoc-3.20-4.el7.noarch 72/177 Installing : perl-Pod-Escapes-1:1.04-297.el7.noarch 73/177 Installing : perl-Text-ParseWords-3.29-4.el7.noarch 74/177 Installing : perl-Encode-2.51-7.el7.x86_64 75/177 Installing : perl-Pod-Usage-1.63-3.el7.noarch 76/177 Installing : perl-Carp-1.26-244.el7.noarch 77/177 Installing : perl-Exporter-5.68-3.el7.noarch 78/177 Installing : perl-Filter-1.49-3.el7.x86_64 79/177 Installing : perl-File-Path-2.09-2.el7.noarch 80/177 Installing : perl-PathTools-3.40-5.el7.x86_64 81/177 Installing : perl-Scalar-List-Utils-1.27-248.el7.x86_64 82/177 Installing : perl-Socket-2.010-5.el7.x86_64 83/177 Installing : perl-Storable-2.45-3.el7.x86_64 84/177 Installing : perl-Time-HiRes-4:1.9725-3.el7.x86_64 85/177 Installing : perl-File-Temp-0.23.01-3.el7.noarch 86/177 Installing : perl-Time-Local-1.2300-2.el7.noarch 87/177 Installing : perl-constant-1.27-2.el7.noarch 88/177 Installing : perl-libs-4:5.16.3-297.el7.x86_64 89/177 Running scriptlet: perl-libs-4:5.16.3-297.el7.x86_64 89/177 Installing : perl-macros-4:5.16.3-297.el7.x86_64 90/177 Installing : perl-threads-1.87-4.el7.x86_64 91/177 Installing : perl-threads-shared-1.43-6.el7.x86_64 92/177 Installing : perl-Pod-Simple-1:3.28-4.el7.noarch 93/177 Installing : perl-Getopt-Long-2.40-3.el7.noarch 94/177 Installing : perl-4:5.16.3-297.el7.x86_64 95/177 Installing : perl-Thread-Queue-3.02-2.el7.noarch 96/177 Installing : libdb-utils-5.3.21-25.el7.x86_64 97/177 Installing : dwz-0.11-3.el7.x86_64 98/177 Installing : kmod-libs-20-28.el7.x86_64 99/177 Running scriptlet: kmod-libs-20-28.el7.x86_64 99/177 Installing : libxml2-2.9.1-6.el7.5.x86_64 100/177 Running scriptlet: libxml2-2.9.1-6.el7.5.x86_64 100/177 Installing : bzip2-1.0.6-13.el7.x86_64 101/177 Installing : unzip-6.0-21.el7.x86_64 102/177 Installing : zip-3.0-11.el7.x86_64 103/177 Installing : libgomp-4.8.5-44.el7.x86_64 104/177 Running scriptlet: libgomp-4.8.5-44.el7.x86_64 104/177 Installing : libidn-1.28-4.el7.x86_64 105/177 Running scriptlet: libidn-1.28-4.el7.x86_64 105/177 Running scriptlet: glibc-headers-2.17-317.el7.x86_64 106/177 Installing : glibc-headers-2.17-317.el7.x86_64 106/177 Installing : glibc-devel-2.17-317.el7.x86_64 107/177 Running scriptlet: glibc-devel-2.17-317.el7.x86_64 107/177 Installing : ncurses-5.9-14.20130511.el7_4.x86_64 108/177 Installing : libstdc++-devel-4.8.5-44.el7.x86_64 109/177 Installing : hardlink-1:1.0-19.el7.x86_64 110/177 Installing : json-c-0.11-4.el7_0.x86_64 111/177 Running scriptlet: json-c-0.11-4.el7_0.x86_64 111/177 Installing : keyutils-libs-1.5.8-3.el7.x86_64 112/177 Running scriptlet: keyutils-libs-1.5.8-3.el7.x86_64 112/177 Installing : libsmartcols-2.23.2-65.el7.x86_64 113/177 Running scriptlet: libsmartcols-2.23.2-65.el7.x86_64 113/177 Installing : libtasn1-4.10-1.el7.x86_64 114/177 Running scriptlet: libtasn1-4.10-1.el7.x86_64 114/177 Installing : p11-kit-trust-0.23.5-3.el7.x86_64 115/177 Running scriptlet: p11-kit-trust-0.23.5-3.el7.x86_64 115/177 Running scriptlet: ca-certificates-2020.2.41-70.0.el7_8.noarch 116/177 Installing : ca-certificates-2020.2.41-70.0.el7_8.noarch 116/177 Running scriptlet: ca-certificates-2020.2.41-70.0.el7_8.noarch 116/177 Installing : libverto-0.2.5-4.el7.x86_64 117/177 Running scriptlet: libverto-0.2.5-4.el7.x86_64 117/177 Installing : krb5-libs-1.15.1-50.el7.x86_64 118/177 Running scriptlet: krb5-libs-1.15.1-50.el7.x86_64 118/177 Installing : openssl-libs-1:1.0.2k-21.el7_9.x86_64 119/177 Running scriptlet: openssl-libs-1:1.0.2k-21.el7_9.x86_64 119/177 Running scriptlet: coreutils-8.22-24.el7_9.2.x86_64 120/177 Installing : coreutils-8.22-24.el7_9.2.x86_64 120/177 Running scriptlet: coreutils-8.22-24.el7_9.2.x86_64 120/177 Installing : gzip-1.5-10.el7.x86_64 121/177 Running scriptlet: gzip-1.5-10.el7.x86_64 121/177 Installing : libblkid-2.23.2-65.el7.x86_64 122/177 Running scriptlet: libblkid-2.23.2-65.el7.x86_64 122/177 Installing : libmount-2.23.2-65.el7.x86_64 123/177 Running scriptlet: libmount-2.23.2-65.el7.x86_64 123/177 Installing : glib2-2.56.1-8.el7.x86_64 124/177 Running scriptlet: glib2-2.56.1-8.el7.x86_64 124/177 Installing : shared-mime-info-1.8-5.el7.x86_64 125/177 Running scriptlet: shared-mime-info-1.8-5.el7.x86_64 125/177 Installing : cracklib-2.9.0-11.el7.x86_64 126/177 Running scriptlet: cracklib-2.9.0-11.el7.x86_64 126/177 Installing : binutils-2.27-44.base.el7.x86_64 127/177 Running scriptlet: binutils-2.27-44.base.el7.x86_64 127/177 Installing : cracklib-dicts-2.9.0-11.el7.x86_64 128/177 Installing : pkgconfig-1:0.27.1-4.el7.x86_64 129/177 Installing : libpwquality-1.2.3-5.el7.x86_64 130/177 Running scriptlet: libpwquality-1.2.3-5.el7.x86_64 130/177 Installing : pam-1.1.8-23.el7.x86_64 131/177 Running scriptlet: pam-1.1.8-23.el7.x86_64 131/177 Installing : gcc-4.8.5-44.el7.x86_64 132/177 Running scriptlet: gcc-4.8.5-44.el7.x86_64 132/177 Installing : nss-pem-1.0.3-7.el7.x86_64 133/177 Installing : nss-3.53.1-3.el7_9.x86_64 134/177 Running scriptlet: nss-3.53.1-3.el7_9.x86_64 134/177 Installing : nss-sysinit-3.53.1-3.el7_9.x86_64 135/177 Installing : nss-tools-3.53.1-3.el7_9.x86_64 136/177 Installing : python-libs-2.7.5-90.el7.x86_64 137/177 Running scriptlet: python-libs-2.7.5-90.el7.x86_64 137/177 Running scriptlet: gdb-7.6.1-120.el7.x86_64 138/177 Installing : gdb-7.6.1-120.el7.x86_64 138/177 Installing : libssh2-1.8.0-4.el7.x86_64 139/177 Running scriptlet: libssh2-1.8.0-4.el7.x86_64 139/177 Installing : cyrus-sasl-lib-2.1.26-23.el7.x86_64 140/177 Running scriptlet: cyrus-sasl-lib-2.1.26-23.el7.x86_64 140/177 Installing : libcurl-7.29.0-59.el7_9.1.x86_64 141/177 Running scriptlet: libcurl-7.29.0-59.el7_9.1.x86_64 141/177 Installing : curl-7.29.0-59.el7_9.1.x86_64 142/177 Installing : rpm-libs-4.11.3-45.el7.x86_64 143/177 Running scriptlet: rpm-libs-4.11.3-45.el7.x86_64 143/177 Installing : rpm-4.11.3-45.el7.x86_64 144/177 Installing : openldap-2.4.44-22.el7.x86_64 145/177 Running scriptlet: openldap-2.4.44-22.el7.x86_64 145/177 Installing : redhat-rpm-config-9.1.0-88.el7.centos.noarch 146/177 Installing : lua-srpm-macros-1-2.el7.noarch 147/177 Installing : libuser-0.60-9.el7.x86_64 148/177 Running scriptlet: libuser-0.60-9.el7.x86_64 148/177 Installing : pth-2.0.7-23.el7.x86_64 149/177 Running scriptlet: pth-2.0.7-23.el7.x86_64 149/177 Installing : gnupg2-2.0.22-5.el7_5.x86_64 150/177 Running scriptlet: gnupg2-2.0.22-5.el7_5.x86_64 150/177 Installing : rpm-build-libs-4.11.3-45.el7.x86_64 151/177 Running scriptlet: rpm-build-libs-4.11.3-45.el7.x86_64 151/177 Installing : qrencode-libs-3.4.1-3.el7.x86_64 152/177 Running scriptlet: qrencode-libs-3.4.1-3.el7.x86_64 152/177 Installing : ustr-1.0.4-16.el7.x86_64 153/177 Running scriptlet: ustr-1.0.4-16.el7.x86_64 153/177 Installing : libsemanage-2.5-14.el7.x86_64 154/177 Running scriptlet: libsemanage-2.5-14.el7.x86_64 154/177 Installing : shadow-utils-2:4.6-5.el7.x86_64 155/177 Running scriptlet: libutempter-1.1.6-4.el7.x86_64 156/177 Installing : libutempter-1.1.6-4.el7.x86_64 156/177 Running scriptlet: libutempter-1.1.6-4.el7.x86_64 156/177 Installing : procps-ng-3.3.10-28.el7.x86_64 157/177 Running scriptlet: procps-ng-3.3.10-28.el7.x86_64 157/177 Installing : util-linux-2.23.2-65.el7.x86_64 158/177 Running scriptlet: util-linux-2.23.2-65.el7.x86_64 158/177 Installing : kpartx-0.4.9-134.el7_9.x86_64 159/177 Installing : device-mapper-7:1.02.170-6.el7_9.3.x86_64 160/177 Running scriptlet: device-mapper-7:1.02.170-6.el7_9.3.x86_64 160/177 Installing : dracut-033-572.el7.x86_64 161/177 Installing : kmod-20-28.el7.x86_64 162/177 Installing : device-mapper-libs-7:1.02.170-6.el7_9.3.x86_64 163/177 Running scriptlet: device-mapper-libs-7:1.02.170-6.el7_9.3.x86_64 163/177 Installing : cryptsetup-libs-2.0.3-6.el7.x86_64 164/177 Running scriptlet: cryptsetup-libs-2.0.3-6.el7.x86_64 164/177 Installing : elfutils-libs-0.176-5.el7.x86_64 165/177 Running scriptlet: elfutils-libs-0.176-5.el7.x86_64 165/177 Installing : systemd-libs-219-78.el7_9.2.x86_64 166/177 Running scriptlet: systemd-libs-219-78.el7_9.2.x86_64 166/177 Installing : dbus-libs-1:1.10.24-15.el7.x86_64 167/177 Running scriptlet: dbus-libs-1:1.10.24-15.el7.x86_64 167/177 Running scriptlet: systemd-219-78.el7_9.2.x86_64 168/177 Installing : systemd-219-78.el7_9.2.x86_64 168/177 Running scriptlet: systemd-219-78.el7_9.2.x86_64 168/177 Running in chroot, ignoring request. Running scriptlet: dbus-1:1.10.24-15.el7.x86_64 169/177 Installing : dbus-1:1.10.24-15.el7.x86_64 169/177 Installing : elfutils-default-yama-scope-0.176-5.el7.noarch 170/177 Running scriptlet: elfutils-default-yama-scope-0.176-5.el7.noarch 170/177 Installing : elfutils-0.176-5.el7.x86_64 171/177 Installing : rpm-build-4.11.3-45.el7.x86_64 172/177 Installing : epel-rpm-macros-7-29.noarch 173/177 Installing : gcc-c++-4.8.5-44.el7.x86_64 174/177 Installing : make-1:3.82-24.el7.x86_64 175/177 Running scriptlet: make-1:3.82-24.el7.x86_64 175/177 Installing : which-2.20-7.el7.x86_64 176/177 Running scriptlet: which-2.20-7.el7.x86_64 176/177 Installing : epel-release-7-13.noarch 177/177 Running scriptlet: filesystem-3.2-25.el7.x86_64 177/177 Running scriptlet: p11-kit-trust-0.23.5-3.el7.x86_64 177/177 Running scriptlet: shared-mime-info-1.8-5.el7.x86_64 177/177 Running scriptlet: rpm-4.11.3-45.el7.x86_64 177/177 Running scriptlet: systemd-219-78.el7_9.2.x86_64 177/177 Verifying : acl-2.2.51-15.el7.x86_64 1/177 Verifying : audit-libs-2.8.5-4.el7.x86_64 2/177 Verifying : basesystem-10.0-7.el7.centos.noarch 3/177 Verifying : bash-4.2.46-34.el7.x86_64 4/177 Verifying : binutils-2.27-44.base.el7.x86_64 5/177 Verifying : bzip2-1.0.6-13.el7.x86_64 6/177 Verifying : bzip2-libs-1.0.6-13.el7.x86_64 7/177 Verifying : ca-certificates-2020.2.41-70.0.el7_8.noarch 8/177 Verifying : chkconfig-1.7.6-1.el7.x86_64 9/177 Verifying : cpio-2.11-28.el7.x86_64 10/177 Verifying : cpp-4.8.5-44.el7.x86_64 11/177 Verifying : cracklib-2.9.0-11.el7.x86_64 12/177 Verifying : cracklib-dicts-2.9.0-11.el7.x86_64 13/177 Verifying : cryptsetup-libs-2.0.3-6.el7.x86_64 14/177 Verifying : cyrus-sasl-lib-2.1.26-23.el7.x86_64 15/177 Verifying : dbus-1:1.10.24-15.el7.x86_64 16/177 Verifying : dbus-libs-1:1.10.24-15.el7.x86_64 17/177 Verifying : diffutils-3.3-5.el7.x86_64 18/177 Verifying : dracut-033-572.el7.x86_64 19/177 Verifying : dwz-0.11-3.el7.x86_64 20/177 Verifying : elfutils-0.176-5.el7.x86_64 21/177 Verifying : elfutils-default-yama-scope-0.176-5.el7.noarch 22/177 Verifying : elfutils-libelf-0.176-5.el7.x86_64 23/177 Verifying : elfutils-libs-0.176-5.el7.x86_64 24/177 Verifying : expat-2.1.0-12.el7.x86_64 25/177 Verifying : file-5.11-37.el7.x86_64 26/177 Verifying : file-libs-5.11-37.el7.x86_64 27/177 Verifying : filesystem-3.2-25.el7.x86_64 28/177 Verifying : findutils-1:4.5.11-6.el7.x86_64 29/177 Verifying : gawk-4.0.2-4.el7_3.1.x86_64 30/177 Verifying : gcc-4.8.5-44.el7.x86_64 31/177 Verifying : gcc-c++-4.8.5-44.el7.x86_64 32/177 Verifying : gdb-7.6.1-120.el7.x86_64 33/177 Verifying : gdbm-1.10-8.el7.x86_64 34/177 Verifying : glibc-2.17-317.el7.x86_64 35/177 Verifying : glibc-common-2.17-317.el7.x86_64 36/177 Verifying : glibc-devel-2.17-317.el7.x86_64 37/177 Verifying : glibc-headers-2.17-317.el7.x86_64 38/177 Verifying : gmp-1:6.0.0-15.el7.x86_64 39/177 Verifying : gnupg2-2.0.22-5.el7_5.x86_64 40/177 Verifying : grep-2.20-3.el7.x86_64 41/177 Verifying : groff-base-1.22.2-8.el7.x86_64 42/177 Verifying : gzip-1.5-10.el7.x86_64 43/177 Verifying : hardlink-1:1.0-19.el7.x86_64 44/177 Verifying : info-5.1-5.el7.x86_64 45/177 Verifying : json-c-0.11-4.el7_0.x86_64 46/177 Verifying : keyutils-libs-1.5.8-3.el7.x86_64 47/177 Verifying : kmod-20-28.el7.x86_64 48/177 Verifying : kmod-libs-20-28.el7.x86_64 49/177 Verifying : krb5-libs-1.15.1-50.el7.x86_64 50/177 Verifying : libacl-2.2.51-15.el7.x86_64 51/177 Verifying : libassuan-2.1.0-3.el7.x86_64 52/177 Verifying : libattr-2.4.46-13.el7.x86_64 53/177 Verifying : libblkid-2.23.2-65.el7.x86_64 54/177 Verifying : libcap-2.22-11.el7.x86_64 55/177 Verifying : libcap-ng-0.7.5-4.el7.x86_64 56/177 Verifying : libcom_err-1.42.9-19.el7.x86_64 57/177 Verifying : libdb-5.3.21-25.el7.x86_64 58/177 Verifying : libdb-utils-5.3.21-25.el7.x86_64 59/177 Verifying : libffi-3.0.13-19.el7.x86_64 60/177 Verifying : libgcc-4.8.5-44.el7.x86_64 61/177 Verifying : libgcrypt-1.5.3-14.el7.x86_64 62/177 Verifying : libgomp-4.8.5-44.el7.x86_64 63/177 Verifying : libgpg-error-1.12-3.el7.x86_64 64/177 Verifying : libidn-1.28-4.el7.x86_64 65/177 Verifying : libmount-2.23.2-65.el7.x86_64 66/177 Verifying : libmpc-1.0.1-3.el7.x86_64 67/177 Verifying : libpwquality-1.2.3-5.el7.x86_64 68/177 Verifying : libselinux-2.5-15.el7.x86_64 69/177 Verifying : libsemanage-2.5-14.el7.x86_64 70/177 Verifying : libsepol-2.5-10.el7.x86_64 71/177 Verifying : libsmartcols-2.23.2-65.el7.x86_64 72/177 Verifying : libssh2-1.8.0-4.el7.x86_64 73/177 Verifying : libstdc++-4.8.5-44.el7.x86_64 74/177 Verifying : libstdc++-devel-4.8.5-44.el7.x86_64 75/177 Verifying : libtasn1-4.10-1.el7.x86_64 76/177 Verifying : libuser-0.60-9.el7.x86_64 77/177 Verifying : libutempter-1.1.6-4.el7.x86_64 78/177 Verifying : libuuid-2.23.2-65.el7.x86_64 79/177 Verifying : libverto-0.2.5-4.el7.x86_64 80/177 Verifying : libxml2-2.9.1-6.el7.5.x86_64 81/177 Verifying : lua-5.1.4-15.el7.x86_64 82/177 Verifying : lz4-1.8.3-1.el7.x86_64 83/177 Verifying : make-1:3.82-24.el7.x86_64 84/177 Verifying : mpfr-3.1.1-4.el7.x86_64 85/177 Verifying : ncurses-5.9-14.20130511.el7_4.x86_64 86/177 Verifying : ncurses-base-5.9-14.20130511.el7_4.noarch 87/177 Verifying : ncurses-libs-5.9-14.20130511.el7_4.x86_64 88/177 Verifying : nss-pem-1.0.3-7.el7.x86_64 89/177 Verifying : openldap-2.4.44-22.el7.x86_64 90/177 Verifying : p11-kit-0.23.5-3.el7.x86_64 91/177 Verifying : p11-kit-trust-0.23.5-3.el7.x86_64 92/177 Verifying : pam-1.1.8-23.el7.x86_64 93/177 Verifying : patch-2.7.1-12.el7_7.x86_64 94/177 Verifying : pcre-8.32-17.el7.x86_64 95/177 Verifying : perl-4:5.16.3-297.el7.x86_64 96/177 Verifying : perl-Carp-1.26-244.el7.noarch 97/177 Verifying : perl-Encode-2.51-7.el7.x86_64 98/177 Verifying : perl-Exporter-5.68-3.el7.noarch 99/177 Verifying : perl-File-Path-2.09-2.el7.noarch 100/177 Verifying : perl-File-Temp-0.23.01-3.el7.noarch 101/177 Verifying : perl-Filter-1.49-3.el7.x86_64 102/177 Verifying : perl-Getopt-Long-2.40-3.el7.noarch 103/177 Verifying : perl-HTTP-Tiny-0.033-3.el7.noarch 104/177 Verifying : perl-PathTools-3.40-5.el7.x86_64 105/177 Verifying : perl-Pod-Escapes-1:1.04-297.el7.noarch 106/177 Verifying : perl-Pod-Perldoc-3.20-4.el7.noarch 107/177 Verifying : perl-Pod-Simple-1:3.28-4.el7.noarch 108/177 Verifying : perl-Pod-Usage-1.63-3.el7.noarch 109/177 Verifying : perl-Scalar-List-Utils-1.27-248.el7.x86_64 110/177 Verifying : perl-Socket-2.010-5.el7.x86_64 111/177 Verifying : perl-Storable-2.45-3.el7.x86_64 112/177 Verifying : perl-Text-ParseWords-3.29-4.el7.noarch 113/177 Verifying : perl-Thread-Queue-3.02-2.el7.noarch 114/177 Verifying : perl-Time-HiRes-4:1.9725-3.el7.x86_64 115/177 Verifying : perl-Time-Local-1.2300-2.el7.noarch 116/177 Verifying : perl-constant-1.27-2.el7.noarch 117/177 Verifying : perl-libs-4:5.16.3-297.el7.x86_64 118/177 Verifying : perl-macros-4:5.16.3-297.el7.x86_64 119/177 Verifying : perl-parent-1:0.225-244.el7.noarch 120/177 Verifying : perl-podlators-2.5.1-3.el7.noarch 121/177 Verifying : perl-srpm-macros-1-8.el7.noarch 122/177 Verifying : perl-threads-1.87-4.el7.x86_64 123/177 Verifying : perl-threads-shared-1.43-6.el7.x86_64 124/177 Verifying : pinentry-0.8.1-17.el7.x86_64 125/177 Verifying : pkgconfig-1:0.27.1-4.el7.x86_64 126/177 Verifying : popt-1.13-16.el7.x86_64 127/177 Verifying : procps-ng-3.3.10-28.el7.x86_64 128/177 Verifying : pth-2.0.7-23.el7.x86_64 129/177 Verifying : python-rpm-macros-3-34.el7.noarch 130/177 Verifying : python-srpm-macros-3-34.el7.noarch 131/177 Verifying : python2-rpm-macros-3-34.el7.noarch 132/177 Verifying : qrencode-libs-3.4.1-3.el7.x86_64 133/177 Verifying : readline-6.2-11.el7.x86_64 134/177 Verifying : redhat-rpm-config-9.1.0-88.el7.centos.noarch 135/177 Verifying : rpm-4.11.3-45.el7.x86_64 136/177 Verifying : rpm-build-4.11.3-45.el7.x86_64 137/177 Verifying : rpm-build-libs-4.11.3-45.el7.x86_64 138/177 Verifying : rpm-libs-4.11.3-45.el7.x86_64 139/177 Verifying : sed-4.2.2-7.el7.x86_64 140/177 Verifying : setup-2.8.71-11.el7.noarch 141/177 Verifying : shadow-utils-2:4.6-5.el7.x86_64 142/177 Verifying : shared-mime-info-1.8-5.el7.x86_64 143/177 Verifying : sqlite-3.7.17-8.el7_7.1.x86_64 144/177 Verifying : tar-2:1.26-35.el7.x86_64 145/177 Verifying : unzip-6.0-21.el7.x86_64 146/177 Verifying : ustr-1.0.4-16.el7.x86_64 147/177 Verifying : util-linux-2.23.2-65.el7.x86_64 148/177 Verifying : which-2.20-7.el7.x86_64 149/177 Verifying : xz-5.2.2-1.el7.x86_64 150/177 Verifying : xz-libs-5.2.2-1.el7.x86_64 151/177 Verifying : zip-3.0-11.el7.x86_64 152/177 Verifying : zlib-1.2.7-18.el7.x86_64 153/177 Verifying : centos-release-7-9.2009.1.el7.centos.x86_64 154/177 Verifying : coreutils-8.22-24.el7_9.2.x86_64 155/177 Verifying : curl-7.29.0-59.el7_9.1.x86_64 156/177 Verifying : device-mapper-7:1.02.170-6.el7_9.3.x86_64 157/177 Verifying : device-mapper-libs-7:1.02.170-6.el7_9.3.x86_64 158/177 Verifying : glib2-2.56.1-8.el7.x86_64 159/177 Verifying : kernel-headers-3.10.0-1160.11.1.el7.x86_64 160/177 Verifying : kpartx-0.4.9-134.el7_9.x86_64 161/177 Verifying : libcurl-7.29.0-59.el7_9.1.x86_64 162/177 Verifying : nspr-4.25.0-2.el7_9.x86_64 163/177 Verifying : nss-3.53.1-3.el7_9.x86_64 164/177 Verifying : nss-softokn-3.53.1-6.el7_9.x86_64 165/177 Verifying : nss-softokn-freebl-3.53.1-6.el7_9.x86_64 166/177 Verifying : nss-sysinit-3.53.1-3.el7_9.x86_64 167/177 Verifying : nss-tools-3.53.1-3.el7_9.x86_64 168/177 Verifying : nss-util-3.53.1-1.el7_9.x86_64 169/177 Verifying : openssl-libs-1:1.0.2k-21.el7_9.x86_64 170/177 Verifying : python-libs-2.7.5-90.el7.x86_64 171/177 Verifying : systemd-219-78.el7_9.2.x86_64 172/177 Verifying : systemd-libs-219-78.el7_9.2.x86_64 173/177 Verifying : tzdata-2021a-1.el7.noarch 174/177 Verifying : epel-release-7-13.noarch 175/177 Verifying : epel-rpm-macros-7-29.noarch 176/177 Verifying : lua-srpm-macros-1-2.el7.noarch 177/177 Installed: acl-2.2.51-15.el7.x86_64 audit-libs-2.8.5-4.el7.x86_64 basesystem-10.0-7.el7.centos.noarch bash-4.2.46-34.el7.x86_64 binutils-2.27-44.base.el7.x86_64 bzip2-1.0.6-13.el7.x86_64 bzip2-libs-1.0.6-13.el7.x86_64 ca-certificates-2020.2.41-70.0.el7_8.noarch centos-release-7-9.2009.1.el7.centos.x86_64 chkconfig-1.7.6-1.el7.x86_64 coreutils-8.22-24.el7_9.2.x86_64 cpio-2.11-28.el7.x86_64 cpp-4.8.5-44.el7.x86_64 cracklib-2.9.0-11.el7.x86_64 cracklib-dicts-2.9.0-11.el7.x86_64 cryptsetup-libs-2.0.3-6.el7.x86_64 curl-7.29.0-59.el7_9.1.x86_64 cyrus-sasl-lib-2.1.26-23.el7.x86_64 dbus-1:1.10.24-15.el7.x86_64 dbus-libs-1:1.10.24-15.el7.x86_64 device-mapper-7:1.02.170-6.el7_9.3.x86_64 device-mapper-libs-7:1.02.170-6.el7_9.3.x86_64 diffutils-3.3-5.el7.x86_64 dracut-033-572.el7.x86_64 dwz-0.11-3.el7.x86_64 elfutils-0.176-5.el7.x86_64 elfutils-default-yama-scope-0.176-5.el7.noarch elfutils-libelf-0.176-5.el7.x86_64 elfutils-libs-0.176-5.el7.x86_64 epel-release-7-13.noarch epel-rpm-macros-7-29.noarch expat-2.1.0-12.el7.x86_64 file-5.11-37.el7.x86_64 file-libs-5.11-37.el7.x86_64 filesystem-3.2-25.el7.x86_64 findutils-1:4.5.11-6.el7.x86_64 gawk-4.0.2-4.el7_3.1.x86_64 gcc-4.8.5-44.el7.x86_64 gcc-c++-4.8.5-44.el7.x86_64 gdb-7.6.1-120.el7.x86_64 gdbm-1.10-8.el7.x86_64 glib2-2.56.1-8.el7.x86_64 glibc-2.17-317.el7.x86_64 glibc-common-2.17-317.el7.x86_64 glibc-devel-2.17-317.el7.x86_64 glibc-headers-2.17-317.el7.x86_64 gmp-1:6.0.0-15.el7.x86_64 gnupg2-2.0.22-5.el7_5.x86_64 grep-2.20-3.el7.x86_64 groff-base-1.22.2-8.el7.x86_64 gzip-1.5-10.el7.x86_64 hardlink-1:1.0-19.el7.x86_64 info-5.1-5.el7.x86_64 json-c-0.11-4.el7_0.x86_64 kernel-headers-3.10.0-1160.11.1.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 kmod-20-28.el7.x86_64 kmod-libs-20-28.el7.x86_64 kpartx-0.4.9-134.el7_9.x86_64 krb5-libs-1.15.1-50.el7.x86_64 libacl-2.2.51-15.el7.x86_64 libassuan-2.1.0-3.el7.x86_64 libattr-2.4.46-13.el7.x86_64 libblkid-2.23.2-65.el7.x86_64 libcap-2.22-11.el7.x86_64 libcap-ng-0.7.5-4.el7.x86_64 libcom_err-1.42.9-19.el7.x86_64 libcurl-7.29.0-59.el7_9.1.x86_64 libdb-5.3.21-25.el7.x86_64 libdb-utils-5.3.21-25.el7.x86_64 libffi-3.0.13-19.el7.x86_64 libgcc-4.8.5-44.el7.x86_64 libgcrypt-1.5.3-14.el7.x86_64 libgomp-4.8.5-44.el7.x86_64 libgpg-error-1.12-3.el7.x86_64 libidn-1.28-4.el7.x86_64 libmount-2.23.2-65.el7.x86_64 libmpc-1.0.1-3.el7.x86_64 libpwquality-1.2.3-5.el7.x86_64 libselinux-2.5-15.el7.x86_64 libsemanage-2.5-14.el7.x86_64 libsepol-2.5-10.el7.x86_64 libsmartcols-2.23.2-65.el7.x86_64 libssh2-1.8.0-4.el7.x86_64 libstdc++-4.8.5-44.el7.x86_64 libstdc++-devel-4.8.5-44.el7.x86_64 libtasn1-4.10-1.el7.x86_64 libuser-0.60-9.el7.x86_64 libutempter-1.1.6-4.el7.x86_64 libuuid-2.23.2-65.el7.x86_64 libverto-0.2.5-4.el7.x86_64 libxml2-2.9.1-6.el7.5.x86_64 lua-5.1.4-15.el7.x86_64 lua-srpm-macros-1-2.el7.noarch lz4-1.8.3-1.el7.x86_64 make-1:3.82-24.el7.x86_64 mpfr-3.1.1-4.el7.x86_64 ncurses-5.9-14.20130511.el7_4.x86_64 ncurses-base-5.9-14.20130511.el7_4.noarch ncurses-libs-5.9-14.20130511.el7_4.x86_64 nspr-4.25.0-2.el7_9.x86_64 nss-3.53.1-3.el7_9.x86_64 nss-pem-1.0.3-7.el7.x86_64 nss-softokn-3.53.1-6.el7_9.x86_64 nss-softokn-freebl-3.53.1-6.el7_9.x86_64 nss-sysinit-3.53.1-3.el7_9.x86_64 nss-tools-3.53.1-3.el7_9.x86_64 nss-util-3.53.1-1.el7_9.x86_64 openldap-2.4.44-22.el7.x86_64 openssl-libs-1:1.0.2k-21.el7_9.x86_64 p11-kit-0.23.5-3.el7.x86_64 p11-kit-trust-0.23.5-3.el7.x86_64 pam-1.1.8-23.el7.x86_64 patch-2.7.1-12.el7_7.x86_64 pcre-8.32-17.el7.x86_64 perl-4:5.16.3-297.el7.x86_64 perl-Carp-1.26-244.el7.noarch perl-Encode-2.51-7.el7.x86_64 perl-Exporter-5.68-3.el7.noarch perl-File-Path-2.09-2.el7.noarch perl-File-Temp-0.23.01-3.el7.noarch perl-Filter-1.49-3.el7.x86_64 perl-Getopt-Long-2.40-3.el7.noarch perl-HTTP-Tiny-0.033-3.el7.noarch perl-PathTools-3.40-5.el7.x86_64 perl-Pod-Escapes-1:1.04-297.el7.noarch perl-Pod-Perldoc-3.20-4.el7.noarch perl-Pod-Simple-1:3.28-4.el7.noarch perl-Pod-Usage-1.63-3.el7.noarch perl-Scalar-List-Utils-1.27-248.el7.x86_64 perl-Socket-2.010-5.el7.x86_64 perl-Storable-2.45-3.el7.x86_64 perl-Text-ParseWords-3.29-4.el7.noarch perl-Thread-Queue-3.02-2.el7.noarch perl-Time-HiRes-4:1.9725-3.el7.x86_64 perl-Time-Local-1.2300-2.el7.noarch perl-constant-1.27-2.el7.noarch perl-libs-4:5.16.3-297.el7.x86_64 perl-macros-4:5.16.3-297.el7.x86_64 perl-parent-1:0.225-244.el7.noarch perl-podlators-2.5.1-3.el7.noarch perl-srpm-macros-1-8.el7.noarch perl-threads-1.87-4.el7.x86_64 perl-threads-shared-1.43-6.el7.x86_64 pinentry-0.8.1-17.el7.x86_64 pkgconfig-1:0.27.1-4.el7.x86_64 popt-1.13-16.el7.x86_64 procps-ng-3.3.10-28.el7.x86_64 pth-2.0.7-23.el7.x86_64 python-libs-2.7.5-90.el7.x86_64 python-rpm-macros-3-34.el7.noarch python-srpm-macros-3-34.el7.noarch python2-rpm-macros-3-34.el7.noarch qrencode-libs-3.4.1-3.el7.x86_64 readline-6.2-11.el7.x86_64 redhat-rpm-config-9.1.0-88.el7.centos.noarch rpm-4.11.3-45.el7.x86_64 rpm-build-4.11.3-45.el7.x86_64 rpm-build-libs-4.11.3-45.el7.x86_64 rpm-libs-4.11.3-45.el7.x86_64 sed-4.2.2-7.el7.x86_64 setup-2.8.71-11.el7.noarch shadow-utils-2:4.6-5.el7.x86_64 shared-mime-info-1.8-5.el7.x86_64 sqlite-3.7.17-8.el7_7.1.x86_64 systemd-219-78.el7_9.2.x86_64 systemd-libs-219-78.el7_9.2.x86_64 tar-2:1.26-35.el7.x86_64 tzdata-2021a-1.el7.noarch unzip-6.0-21.el7.x86_64 ustr-1.0.4-16.el7.x86_64 util-linux-2.23.2-65.el7.x86_64 which-2.20-7.el7.x86_64 xz-5.2.2-1.el7.x86_64 xz-libs-5.2.2-1.el7.x86_64 zip-3.0-11.el7.x86_64 zlib-1.2.7-18.el7.x86_64 Complete! Finish: dnf install Start: creating root cache Finish: creating root cache Finish: chroot init INFO: Installed packages: INFO: dwz-0.11-3.el7.x86_64 libgcrypt-1.5.3-14.el7.x86_64 cracklib-dicts-2.9.0-11.el7.x86_64 perl-Time-Local-1.2300-2.el7.noarch glibc-2.17-317.el7.x86_64 ncurses-5.9-14.20130511.el7_4.x86_64 krb5-libs-1.15.1-50.el7.x86_64 basesystem-10.0-7.el7.centos.noarch systemd-219-78.el7_9.2.x86_64 perl-Scalar-List-Utils-1.27-248.el7.x86_64 glib2-2.56.1-8.el7.x86_64 pth-2.0.7-23.el7.x86_64 nss-softokn-3.53.1-6.el7_9.x86_64 libmpc-1.0.1-3.el7.x86_64 expat-2.1.0-12.el7.x86_64 perl-Encode-2.51-7.el7.x86_64 libidn-1.28-4.el7.x86_64 pkgconfig-0.27.1-4.el7.x86_64 libssh2-1.8.0-4.el7.x86_64 ncurses-base-5.9-14.20130511.el7_4.noarch glibc-devel-2.17-317.el7.x86_64 libcurl-7.29.0-59.el7_9.1.x86_64 perl-srpm-macros-1-8.el7.noarch chkconfig-1.7.6-1.el7.x86_64 sqlite-3.7.17-8.el7_7.1.x86_64 redhat-rpm-config-9.1.0-88.el7.centos.noarch acl-2.2.51-15.el7.x86_64 openldap-2.4.44-22.el7.x86_64 python-libs-2.7.5-90.el7.x86_64 libsepol-2.5-10.el7.x86_64 groff-base-1.22.2-8.el7.x86_64 cracklib-2.9.0-11.el7.x86_64 libgomp-4.8.5-44.el7.x86_64 audit-libs-2.8.5-4.el7.x86_64 rpm-4.11.3-45.el7.x86_64 lua-5.1.4-15.el7.x86_64 gpg-pubkey-352c64e5-52ae6884 libcap-ng-0.7.5-4.el7.x86_64 gawk-4.0.2-4.el7_3.1.x86_64 device-mapper-1.02.170-6.el7_9.3.x86_64 popt-1.13-16.el7.x86_64 libgpg-error-1.12-3.el7.x86_64 libuuid-2.23.2-65.el7.x86_64 perl-Pod-Escapes-1.04-297.el7.noarch glibc-headers-2.17-317.el7.x86_64 nspr-4.25.0-2.el7_9.x86_64 perl-Exporter-5.68-3.el7.noarch perl-Text-ParseWords-3.29-4.el7.noarch binutils-2.27-44.base.el7.x86_64 tzdata-2021a-1.el7.noarch libacl-2.2.51-15.el7.x86_64 grep-2.20-3.el7.x86_64 qrencode-libs-3.4.1-3.el7.x86_64 setup-2.8.71-11.el7.noarch gmp-6.0.0-15.el7.x86_64 filesystem-3.2-25.el7.x86_64 lz4-1.8.3-1.el7.x86_64 coreutils-8.22-24.el7_9.2.x86_64 elfutils-0.176-5.el7.x86_64 cyrus-sasl-lib-2.1.26-23.el7.x86_64 perl-Storable-2.45-3.el7.x86_64 sed-4.2.2-7.el7.x86_64 libffi-3.0.13-19.el7.x86_64 perl-threads-shared-1.43-6.el7.x86_64 dracut-033-572.el7.x86_64 cryptsetup-libs-2.0.3-6.el7.x86_64 perl-File-Path-2.09-2.el7.noarch libsmartcols-2.23.2-65.el7.x86_64 json-c-0.11-4.el7_0.x86_64 procps-ng-3.3.10-28.el7.x86_64 ca-certificates-2020.2.41-70.0.el7_8.noarch libverto-0.2.5-4.el7.x86_64 nss-sysinit-3.53.1-3.el7_9.x86_64 perl-Filter-1.49-3.el7.x86_64 perl-Getopt-Long-2.40-3.el7.noarch ncurses-libs-5.9-14.20130511.el7_4.x86_64 curl-7.29.0-59.el7_9.1.x86_64 libsemanage-2.5-14.el7.x86_64 shared-mime-info-1.8-5.el7.x86_64 shadow-utils-4.6-5.el7.x86_64 libstdc++-4.8.5-44.el7.x86_64 elfutils-libelf-0.176-5.el7.x86_64 nss-util-3.53.1-1.el7_9.x86_64 p11-kit-0.23.5-3.el7.x86_64 findutils-4.5.11-6.el7.x86_64 file-5.11-37.el7.x86_64 bzip2-libs-1.0.6-13.el7.x86_64 libutempter-1.1.6-4.el7.x86_64 libcap-2.22-11.el7.x86_64 bzip2-1.0.6-13.el7.x86_64 libdb-5.3.21-25.el7.x86_64 perl-Pod-Perldoc-3.20-4.el7.noarch epel-rpm-macros-7-29.noarch python-rpm-macros-3-34.el7.noarch perl-podlators-2.5.1-3.el7.noarch nss-pem-1.0.3-7.el7.x86_64 gnupg2-2.0.22-5.el7_5.x86_64 epel-release-7-13.noarch perl-Time-HiRes-1.9725-3.el7.x86_64 util-linux-2.23.2-65.el7.x86_64 bash-4.2.46-34.el7.x86_64 nss-3.53.1-3.el7_9.x86_64 perl-HTTP-Tiny-0.033-3.el7.noarch libtasn1-4.10-1.el7.x86_64 rpm-build-4.11.3-45.el7.x86_64 libgcc-4.8.5-44.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 dbus-1.10.24-15.el7.x86_64 perl-Pod-Usage-1.63-3.el7.noarch nss-tools-3.53.1-3.el7_9.x86_64 perl-PathTools-3.40-5.el7.x86_64 diffutils-3.3-5.el7.x86_64 openssl-libs-1.0.2k-21.el7_9.x86_64 python-srpm-macros-3-34.el7.noarch gcc-4.8.5-44.el7.x86_64 rpm-libs-4.11.3-45.el7.x86_64 libattr-2.4.46-13.el7.x86_64 libassuan-2.1.0-3.el7.x86_64 unzip-6.0-21.el7.x86_64 perl-Pod-Simple-3.28-4.el7.noarch zip-3.0-11.el7.x86_64 python2-rpm-macros-3-34.el7.noarch mpfr-3.1.1-4.el7.x86_64 kpartx-0.4.9-134.el7_9.x86_64 centos-release-7-9.2009.1.el7.centos.x86_64 gpg-pubkey-f4a80eb5-53a7ff4b p11-kit-trust-0.23.5-3.el7.x86_64 libmount-2.23.2-65.el7.x86_64 kmod-20-28.el7.x86_64 pinentry-0.8.1-17.el7.x86_64 hardlink-1.0-19.el7.x86_64 elfutils-libs-0.176-5.el7.x86_64 perl-macros-5.16.3-297.el7.x86_64 perl-Thread-Queue-3.02-2.el7.noarch patch-2.7.1-12.el7_7.x86_64 ustr-1.0.4-16.el7.x86_64 libuser-0.60-9.el7.x86_64 kernel-headers-3.10.0-1160.11.1.el7.x86_64 nss-softokn-freebl-3.53.1-6.el7_9.x86_64 make-3.82-24.el7.x86_64 cpp-4.8.5-44.el7.x86_64 kmod-libs-20-28.el7.x86_64 rpm-build-libs-4.11.3-45.el7.x86_64 elfutils-default-yama-scope-0.176-5.el7.noarch file-libs-5.11-37.el7.x86_64 dbus-libs-1.10.24-15.el7.x86_64 perl-Carp-1.26-244.el7.noarch pcre-8.32-17.el7.x86_64 gzip-1.5-10.el7.x86_64 cpio-2.11-28.el7.x86_64 perl-File-Temp-0.23.01-3.el7.noarch gdb-7.6.1-120.el7.x86_64 lua-srpm-macros-1-2.el7.noarch zlib-1.2.7-18.el7.x86_64 libcom_err-1.42.9-19.el7.x86_64 device-mapper-libs-1.02.170-6.el7_9.3.x86_64 xz-libs-5.2.2-1.el7.x86_64 glibc-common-2.17-317.el7.x86_64 gcc-c++-4.8.5-44.el7.x86_64 libxml2-2.9.1-6.el7.5.x86_64 perl-libs-5.16.3-297.el7.x86_64 xz-5.2.2-1.el7.x86_64 tar-1.26-35.el7.x86_64 libblkid-2.23.2-65.el7.x86_64 which-2.20-7.el7.x86_64 libdb-utils-5.3.21-25.el7.x86_64 gdbm-1.10-8.el7.x86_64 perl-parent-0.225-244.el7.noarch libstdc++-devel-4.8.5-44.el7.x86_64 libpwquality-1.2.3-5.el7.x86_64 info-5.1-5.el7.x86_64 perl-threads-1.87-4.el7.x86_64 libselinux-2.5-15.el7.x86_64 perl-5.16.3-297.el7.x86_64 perl-constant-1.27-2.el7.noarch readline-6.2-11.el7.x86_64 pam-1.1.8-23.el7.x86_64 perl-Socket-2.010-5.el7.x86_64 systemd-libs-219-78.el7_9.2.x86_64 Start: buildsrpm Start: rpmbuild -bs Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/TheP8I-2.0.1-1.el7.src.rpm Finish: rpmbuild -bs INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan INFO: /var/lib/mock/epel-7-x86_64-1611774954.410978/root/var/log/dnf.rpm.log /var/lib/mock/epel-7-x86_64-1611774954.410978/root/var/log/dnf.librepo.log /var/lib/mock/epel-7-x86_64-1611774954.410978/root/var/log/dnf.log Finish: buildsrpm INFO: Done(/tmp/copr-rpmbuild-x41l30bo/obtain-sources/TheP8I/TheP8I.spec) Config(child) 1 minutes 17 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 (timeout=18000): unbuffer mock --rebuild /var/lib/copr-rpmbuild/results/TheP8I-2.0.1-1.el7.src.rpm --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1611775033.207788 -r /var/lib/copr-rpmbuild/results/configs/child.cfg INFO: mock.py version 2.9 starting (python version = 3.9.1, NVR = mock-2.9-1.fc33)... WARNING: Not using '/usr/bin/yum', it is symlink to '/usr/bin/dnf-3' INFO: Using 'dnf' instead of 'yum' 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/results/TheP8I-2.0.1-1.el7.src.rpm) Config(epel-7-x86_64) Start: clean chroot Finish: clean chroot Start: chroot init INFO: mounting tmpfs at /var/lib/mock/epel-7-x86_64-1611775033.207788/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 Mock Version: 2.9 INFO: Mock Version: 2.9 Start: dnf update No matches found for the following disable plugin patterns: local, spacewalk Copr repository 109 kB/s | 3.0 kB 00:00 Copr repository 17 MB/s | 1.2 MB 00:00 Additional repo http_mirror_centos_org_centos_7 24 kB/s | 3.0 kB 00:00 CentOS-7 - Base 12 kB/s | 3.6 kB 00:00 CentOS-7 - Updates 41 kB/s | 2.9 kB 00:00 CentOS-7 - Extras 42 kB/s | 2.9 kB 00:00 CentOS-7 - SCLo sclo 190 kB/s | 3.0 kB 00:00 CentOS-7 - SCLo rh 45 kB/s | 3.0 kB 00:00 Extra Packages for Enterprise Linux 7 - x86_64 52 kB/s | 4.7 kB 00:00 Dependencies resolved. Nothing to do. Complete! Finish: dnf update Finish: chroot init Start: build phase for TheP8I-2.0.1-1.el7.src.rpm Start: build setup for TheP8I-2.0.1-1.el7.src.rpm Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/TheP8I-2.0.1-1.el7.src.rpm No matches found for the following disable plugin patterns: local, spacewalk Copr repository 155 kB/s | 3.6 kB 00:00 Copr repository 23 MB/s | 1.2 MB 00:00 Additional repo http_mirror_centos_org_centos_7 176 kB/s | 3.0 kB 00:00 CentOS-7 - Base 52 kB/s | 3.6 kB 00:00 CentOS-7 - Updates 43 kB/s | 2.9 kB 00:00 CentOS-7 - Extras 43 kB/s | 2.9 kB 00:00 CentOS-7 - SCLo sclo 186 kB/s | 3.0 kB 00:00 CentOS-7 - SCLo rh 44 kB/s | 3.0 kB 00:00 Extra Packages for Enterprise Linux 7 - x86_64 25 kB/s | 4.7 kB 00:00 Dependencies resolved. ================================================================================================ Package Arch Version Repository Size ================================================================================================ Installing: ThePEG  x86_64 2.1.5-7.el7 copr_base 2.6 M ThePEG-devel  x86_64 2.1.5-7.el7 copr_base 408 k autoconf  noarch 2.69-11.el7 base 701 k automake  noarch 1.13.4-3.el7 base 679 k devtoolset-8-gcc  x86_64 8.3.1-3.2.el7 centos-sclo-rh 30 M devtoolset-8-gcc-c++  x86_64 8.3.1-3.2.el7 centos-sclo-rh 12 M gsl  x86_64 1.15-13.el7 base 884 k gsl-devel  x86_64 1.15-13.el7 base 446 k lhapdf  x86_64 6.3.0-1.el7 epel 339 k lhapdf-devel  x86_64 6.3.0-1.el7 epel 39 k libtool  x86_64 2.4.2-22.el7_3 base 588 k pythia8  x86_64 8.2.44-2.el7 epel 1.9 M pythia8-devel  x86_64 8.2.44-2.el7 epel 995 k scl-utils  x86_64 20130529-19.el7 base 24 k Installing dependencies: HepMC3  x86_64 3.2.3-1.el7 epel 229 k HepMC3-devel  x86_64 3.2.3-1.el7 epel 59 k HepMC3-rootIO  x86_64 3.2.3-1.el7 epel 47 k HepMC3-rootIO-devel  x86_64 3.2.3-1.el7 epel 8.4 k HepMC3-search  x86_64 3.2.3-1.el7 epel 38 k HepMC3-search-devel  x86_64 3.2.3-1.el7 epel 14 k MG5_aMC  x86_64 2.7.2-1.el7 copr_base 13 M Rivet  x86_64 3.0.2-6.el7 copr_base 68 M Rivet-devel  x86_64 3.0.2-6.el7 copr_base 9.0 M YODA  x86_64 1.7.7-3.el7 copr_base 4.1 M YODA-devel  x86_64 1.7.7-3.el7 copr_base 66 k atlas  x86_64 3.10.1-12.el7 base 4.5 M audit-libs-python  x86_64 2.8.5-4.el7 base 76 k cairo  x86_64 1.15.12-4.el7 base 741 k checkpolicy  x86_64 2.5-8.el7 base 295 k dejavu-fonts-common  noarch 2.33-6.el7 base 64 k dejavu-sans-fonts  noarch 2.33-6.el7 base 1.4 M devtoolset-8-binutils  x86_64 2.30-55.el7.2 centos-sclo-rh 5.5 M devtoolset-8-libstdc++-devel  x86_64 8.3.1-3.2.el7 centos-sclo-rh 2.7 M devtoolset-8-runtime  x86_64 8.1-1.el7 centos-sclo-rh 20 k fastjet  x86_64 3.3.4-2.el7 copr_base 483 k fastjet-devel  x86_64 3.3.4-2.el7 copr_base 164 k fjcontrib  x86_64 1.045-1.el7 copr_base 789 k fontconfig  x86_64 2.13.0-4.3.el7 base 254 k fontpackages-filesystem  noarch 1.44-8.el7 base 9.9 k freetype  x86_64 2.8-14.el7_9.1 updates 380 k fribidi  x86_64 1.0.2-1.el7_7.1 base 79 k gdk-pixbuf2  x86_64 2.36.12-3.el7 base 570 k giflib  x86_64 4.1.6-9.el7 base 40 k gnu-free-fonts-common  noarch 20120503-18.el7 copr_base 130 k gnu-free-mono-fonts  noarch 20120503-18.el7 copr_base 694 k gnu-free-sans-fonts  noarch 20120503-18.el7 copr_base 1.3 M gnu-free-serif-fonts  noarch 20120503-18.el7 copr_base 2.6 M google-droid-sans-fonts  noarch 20120715-12.el7 epel 2.5 M graphite2  x86_64 1.3.10-1.el7_3 base 115 k harfbuzz  x86_64 1.7.5-2.el7 base 267 k hwdata  x86_64 0.252-9.7.el7 base 2.5 M jasper-libs  x86_64 1.900.1-33.el7 base 150 k jbigkit-libs  x86_64 2.0-11.el7 base 46 k libAfterImage  x86_64 1.20-21.el7 epel 233 k libICE  x86_64 1.0.9-9.el7 base 66 k libSM  x86_64 1.2.2-2.el7 base 39 k libX11  x86_64 1.6.7-3.el7_9 updates 607 k libX11-common  noarch 1.6.7-3.el7_9 updates 164 k libXau  x86_64 1.0.8-2.1.el7 base 29 k libXcursor  x86_64 1.1.15-1.el7 base 30 k libXdamage  x86_64 1.1.4-4.1.el7 base 20 k libXext  x86_64 1.3.3-3.el7 base 39 k libXfixes  x86_64 5.0.3-1.el7 base 18 k libXft  x86_64 2.3.2-2.el7 base 58 k libXi  x86_64 1.7.9-1.el7 base 40 k libXinerama  x86_64 1.1.3-2.1.el7 base 14 k libXmu  x86_64 1.1.2-2.el7 base 71 k libXpm  x86_64 3.5.12-1.el7 base 55 k libXrandr  x86_64 1.5.1-2.el7 base 27 k libXrender  x86_64 0.9.10-1.el7 base 26 k libXt  x86_64 1.1.5-3.el7 base 173 k libXxf86misc  x86_64 1.0.3-7.1.el7 base 19 k libXxf86vm  x86_64 1.1.4-1.el7 base 18 k libcgroup  x86_64 0.41-21.el7 base 66 k libcroco  x86_64 0.6.12-6.el7_9 updates 105 k libdrm  x86_64 2.4.97-2.el7 base 151 k libfontenc  x86_64 1.1.3-3.el7 base 31 k libgfortran  x86_64 4.8.5-44.el7 base 301 k libglvnd  x86_64 1:1.0.1-0.8.git5baa1e5.el7 base 89 k libglvnd-egl  x86_64 1:1.0.1-0.8.git5baa1e5.el7 base 44 k libglvnd-glx  x86_64 1:1.0.1-0.8.git5baa1e5.el7 base 125 k libjpeg-turbo  x86_64 1.2.90-8.el7 base 135 k libpciaccess  x86_64 0.14-1.el7 base 26 k libpng  x86_64 2:1.5.13-8.el7 base 213 k libquadmath  x86_64 4.8.5-44.el7 base 190 k librsvg2  x86_64 2.40.20-1.el7 base 132 k libselinux-python  x86_64 2.5-15.el7 base 236 k libselinux-utils  x86_64 2.5-15.el7 base 151 k libsemanage-python  x86_64 2.5-14.el7 base 113 k libthai  x86_64 0.1.14-9.el7 base 187 k libtiff  x86_64 4.0.3-35.el7 base 172 k libtirpc  x86_64 0.2.4-0.16.el7 base 89 k libwayland-client  x86_64 1.15.0-1.el7 base 33 k libwayland-server  x86_64 1.15.0-1.el7 base 39 k libxcb  x86_64 1.13-1.el7 base 214 k libxshmfence  x86_64 1.2-1.el7 base 7.2 k libzstd  x86_64 1.4.7-1.el7 epel 325 k m4  x86_64 1.4.16-10.el7 base 256 k mesa-libEGL  x86_64 18.3.4-12.el7_9 updates 110 k mesa-libGL  x86_64 18.3.4-12.el7_9 updates 166 k mesa-libgbm  x86_64 18.3.4-12.el7_9 updates 39 k mesa-libglapi  x86_64 18.3.4-12.el7_9 updates 46 k pango  x86_64 1.42.4-4.el7_7 base 280 k perl-Compress-Raw-Bzip2  x86_64 2.061-3.el7 base 32 k perl-Compress-Raw-Zlib  x86_64 1:2.061-4.el7 base 57 k perl-Data-Dumper  x86_64 2.145-3.el7 base 47 k perl-IO-Compress  noarch 2.061-2.el7 base 260 k perl-Test-Harness  noarch 3.28-3.el7 base 302 k pixman  x86_64 0.34.0-1.el7 base 248 k policycoreutils  x86_64 2.5-34.el7 base 917 k policycoreutils-python  x86_64 2.5-34.el7 base 457 k pythia8-data  noarch 8.2.44-2.el7 epel 8.6 M python  x86_64 2.7.5-90.el7 updates 96 k python-IPy  noarch 0.75-6.el7 base 32 k python-YODA  x86_64 1.7.7-3.el7 copr_base 2.2 M python3  x86_64 3.6.8-18.el7 updates 70 k python3-libs  x86_64 3.6.8-18.el7 updates 6.9 M python3-pip  noarch 9.0.3-8.el7 base 1.6 M python3-setuptools  noarch 39.2.0-10.el7 base 629 k root-cling  x86_64 6.22.06-1.el7 epel 15 M root-core  x86_64 6.22.06-1.el7 epel 41 M root-fonts  noarch 6.22.06-1.el7 epel 479 k root-graf  x86_64 6.22.06-1.el7 epel 417 k root-graf-asimage  x86_64 6.22.06-1.el7 epel 133 k root-graf-gpad  x86_64 6.22.06-1.el7 epel 256 k root-graf-postscript  x86_64 6.22.06-1.el7 epel 154 k root-graf-x11  x86_64 6.22.06-1.el7 epel 123 k root-graf3d  x86_64 6.22.06-1.el7 epel 222 k root-gui  x86_64 6.22.06-1.el7 epel 1.0 M root-gui-ged  x86_64 6.22.06-1.el7 epel 332 k root-hist  x86_64 6.22.06-1.el7 epel 1.1 M root-hist-painter  x86_64 6.22.06-1.el7 epel 232 k root-icons  noarch 6.22.06-1.el7 epel 543 k root-io  x86_64 6.22.06-1.el7 epel 813 k root-mathcore  x86_64 6.22.06-1.el7 epel 1.1 M root-mathmore  x86_64 6.22.06-1.el7 epel 243 k root-matrix  x86_64 6.22.06-1.el7 epel 409 k root-minuit  x86_64 6.22.06-1.el7 epel 194 k root-multiproc  x86_64 6.22.06-1.el7 epel 66 k root-net  x86_64 6.22.06-1.el7 epel 269 k root-physics  x86_64 6.22.06-1.el7 epel 143 k root-tree  x86_64 6.22.06-1.el7 epel 478 k root-tree-dataframe  x86_64 6.22.06-1.el7 epel 292 k root-tree-player  x86_64 6.22.06-1.el7 epel 449 k root-vecops  x86_64 6.22.06-1.el7 epel 191 k setools-libs  x86_64 3.3.8-4.el7 base 620 k tcsh  x86_64 6.18.01-17.el7_9.1 updates 339 k urw-base35-d050000l-fonts  noarch 20170801-10.el7 base 75 k urw-base35-fonts-common  noarch 20170801-10.el7 base 19 k urw-base35-standard-symbols-ps-fonts  noarch 20170801-10.el7 base 40 k urw-base35-z003-fonts  noarch 20170801-10.el7 base 275 k xorg-x11-font-utils  x86_64 1:7.5-21.el7 base 104 k xorg-x11-fonts-ISO8859-1-75dpi  noarch 7.5-9.el7 base 933 k xorg-x11-server-utils  x86_64 7.7-20.el7 base 178 k xxhash-libs  x86_64 0.8.0-1.el7 epel 26 k Transaction Summary ================================================================================================ Install 155 Packages Total download size: 271 M Installed size: 1.1 G Downloading Packages: (1/155): MG5_aMC-2.7.2-1.el7.x86_64.rpm 20 MB/s | 13 MB 00:00 (2/155): ThePEG-2.1.5-7.el7.x86_64.rpm 23 MB/s | 2.6 MB 00:00 (3/155): Rivet-devel-3.0.2-6.el7.x86_64.rpm 11 MB/s | 9.0 MB 00:00 (4/155): ThePEG-devel-2.1.5-7.el7.x86_64.rpm 10 MB/s | 408 kB 00:00 (5/155): YODA-devel-1.7.7-3.el7.x86_64.rpm 6.4 MB/s | 66 kB 00:00 (6/155): fastjet-3.3.4-2.el7.x86_64.rpm 22 MB/s | 483 kB 00:00 (7/155): fastjet-devel-3.3.4-2.el7.x86_64.rpm 814 kB/s | 164 kB 00:00 (8/155): YODA-1.7.7-3.el7.x86_64.rpm 11 MB/s | 4.1 MB 00:00 (9/155): fjcontrib-1.045-1.el7.x86_64.rpm 5.4 MB/s | 789 kB 00:00 (10/155): gnu-free-fonts-common-20120503-18.el7 4.9 MB/s | 130 kB 00:00 (11/155): gnu-free-sans-fonts-20120503-18.el7.n 26 MB/s | 1.3 MB 00:00 (12/155): gnu-free-serif-fonts-20120503-18.el7. 28 MB/s | 2.6 MB 00:00 (13/155): python-YODA-1.7.7-3.el7.x86_64.rpm 21 MB/s | 2.2 MB 00:00 (14/155): atlas-3.10.1-12.el7.x86_64.rpm 92 MB/s | 4.5 MB 00:00 (15/155): gnu-free-mono-fonts-20120503-18.el7.n 2.1 MB/s | 694 kB 00:00 (16/155): audit-libs-python-2.8.5-4.el7.x86_64. 16 MB/s | 76 kB 00:00 (17/155): automake-1.13.4-3.el7.noarch.rpm 81 MB/s | 679 kB 00:00 (18/155): autoconf-2.69-11.el7.noarch.rpm 34 MB/s | 701 kB 00:00 (19/155): cairo-1.15.12-4.el7.x86_64.rpm 50 MB/s | 741 kB 00:00 (20/155): dejavu-fonts-common-2.33-6.el7.noarch 16 MB/s | 64 kB 00:00 (21/155): checkpolicy-2.5-8.el7.x86_64.rpm 28 MB/s | 295 kB 00:00 (22/155): fontconfig-2.13.0-4.3.el7.x86_64.rpm 38 MB/s | 254 kB 00:00 (23/155): fontpackages-filesystem-1.44-8.el7.no 5.6 MB/s | 9.9 kB 00:00 (24/155): fribidi-1.0.2-1.el7_7.1.x86_64.rpm 24 MB/s | 79 kB 00:00 (25/155): dejavu-sans-fonts-2.33-6.el7.noarch.r 65 MB/s | 1.4 MB 00:00 (26/155): giflib-4.1.6-9.el7.x86_64.rpm 25 MB/s | 40 kB 00:00 (27/155): graphite2-1.3.10-1.el7_3.x86_64.rpm 46 MB/s | 115 kB 00:00 (28/155): gdk-pixbuf2-2.36.12-3.el7.x86_64.rpm 34 MB/s | 570 kB 00:00 (29/155): gsl-devel-1.15-13.el7.x86_64.rpm 46 MB/s | 446 kB 00:00 (30/155): gsl-1.15-13.el7.x86_64.rpm 50 MB/s | 884 kB 00:00 (31/155): harfbuzz-1.7.5-2.el7.x86_64.rpm 39 MB/s | 267 kB 00:00 (32/155): jasper-libs-1.900.1-33.el7.x86_64.rpm 40 MB/s | 150 kB 00:00 (33/155): jbigkit-libs-2.0-11.el7.x86_64.rpm 14 MB/s | 46 kB 00:00 (34/155): libICE-1.0.9-9.el7.x86_64.rpm 19 MB/s | 66 kB 00:00 (35/155): libSM-1.2.2-2.el7.x86_64.rpm 23 MB/s | 39 kB 00:00 (36/155): libXau-1.0.8-2.1.el7.x86_64.rpm 20 MB/s | 29 kB 00:00 (37/155): libXcursor-1.1.15-1.el7.x86_64.rpm 20 MB/s | 30 kB 00:00 (38/155): libXdamage-1.1.4-4.1.el7.x86_64.rpm 14 MB/s | 20 kB 00:00 (39/155): libXext-1.3.3-3.el7.x86_64.rpm 25 MB/s | 39 kB 00:00 (40/155): libXfixes-5.0.3-1.el7.x86_64.rpm 12 MB/s | 18 kB 00:00 (41/155): hwdata-0.252-9.7.el7.x86_64.rpm 61 MB/s | 2.5 MB 00:00 (42/155): libXft-2.3.2-2.el7.x86_64.rpm 4.2 MB/s | 58 kB 00:00 (43/155): libXi-1.7.9-1.el7.x86_64.rpm 24 MB/s | 40 kB 00:00 (44/155): libXinerama-1.1.3-2.1.el7.x86_64.rpm 8.0 MB/s | 14 kB 00:00 (45/155): libXmu-1.1.2-2.el7.x86_64.rpm 33 MB/s | 71 kB 00:00 (46/155): libXpm-3.5.12-1.el7.x86_64.rpm 21 MB/s | 55 kB 00:00 (47/155): libXrandr-1.5.1-2.el7.x86_64.rpm 16 MB/s | 27 kB 00:00 (48/155): libXrender-0.9.10-1.el7.x86_64.rpm 15 MB/s | 26 kB 00:00 (49/155): libXt-1.1.5-3.el7.x86_64.rpm 52 MB/s | 173 kB 00:00 (50/155): libXxf86misc-1.0.3-7.1.el7.x86_64.rpm 8.2 MB/s | 19 kB 00:00 (51/155): libXxf86vm-1.1.4-1.el7.x86_64.rpm 7.8 MB/s | 18 kB 00:00 (52/155): libcgroup-0.41-21.el7.x86_64.rpm 19 MB/s | 66 kB 00:00 (53/155): libdrm-2.4.97-2.el7.x86_64.rpm 38 MB/s | 151 kB 00:00 (54/155): libfontenc-1.1.3-3.el7.x86_64.rpm 11 MB/s | 31 kB 00:00 (55/155): libglvnd-1.0.1-0.8.git5baa1e5.el7.x86 35 MB/s | 89 kB 00:00 (56/155): libgfortran-4.8.5-44.el7.x86_64.rpm 54 MB/s | 301 kB 00:00 (57/155): libglvnd-egl-1.0.1-0.8.git5baa1e5.el7 13 MB/s | 44 kB 00:00 (58/155): libglvnd-glx-1.0.1-0.8.git5baa1e5.el7 45 MB/s | 125 kB 00:00 (59/155): libjpeg-turbo-1.2.90-8.el7.x86_64.rpm 37 MB/s | 135 kB 00:00 (60/155): libpciaccess-0.14-1.el7.x86_64.rpm 11 MB/s | 26 kB 00:00 (61/155): libquadmath-4.8.5-44.el7.x86_64.rpm 30 MB/s | 190 kB 00:00 (62/155): libpng-1.5.13-8.el7.x86_64.rpm 18 MB/s | 213 kB 00:00 (63/155): librsvg2-2.40.20-1.el7.x86_64.rpm 20 MB/s | 132 kB 00:00 (64/155): libselinux-utils-2.5-15.el7.x86_64.rp 31 MB/s | 151 kB 00:00 (65/155): libselinux-python-2.5-15.el7.x86_64.r 19 MB/s | 236 kB 00:00 (66/155): libsemanage-python-2.5-14.el7.x86_64. 23 MB/s | 113 kB 00:00 (67/155): libthai-0.1.14-9.el7.x86_64.rpm 50 MB/s | 187 kB 00:00 (68/155): libtiff-4.0.3-35.el7.x86_64.rpm 28 MB/s | 172 kB 00:00 (69/155): libtirpc-0.2.4-0.16.el7.x86_64.rpm 15 MB/s | 89 kB 00:00 (70/155): libwayland-client-1.15.0-1.el7.x86_64 14 MB/s | 33 kB 00:00 (71/155): libwayland-server-1.15.0-1.el7.x86_64 25 MB/s | 39 kB 00:00 (72/155): libxcb-1.13-1.el7.x86_64.rpm 55 MB/s | 214 kB 00:00 (73/155): libxshmfence-1.2-1.el7.x86_64.rpm 5.0 MB/s | 7.2 kB 00:00 (74/155): libtool-2.4.2-22.el7_3.x86_64.rpm 33 MB/s | 588 kB 00:00 (75/155): m4-1.4.16-10.el7.x86_64.rpm 28 MB/s | 256 kB 00:00 (76/155): pango-1.42.4-4.el7_7.x86_64.rpm 35 MB/s | 280 kB 00:00 (77/155): perl-Compress-Raw-Bzip2-2.061-3.el7.x 11 MB/s | 32 kB 00:00 (78/155): perl-Compress-Raw-Zlib-2.061-4.el7.x8 21 MB/s | 57 kB 00:00 (79/155): perl-Data-Dumper-2.145-3.el7.x86_64.r 16 MB/s | 47 kB 00:00 (80/155): perl-Test-Harness-3.28-3.el7.noarch.r 57 MB/s | 302 kB 00:00 (81/155): perl-IO-Compress-2.061-2.el7.noarch.r 28 MB/s | 260 kB 00:00 (82/155): pixman-0.34.0-1.el7.x86_64.rpm 48 MB/s | 248 kB 00:00 (83/155): policycoreutils-python-2.5-34.el7.x86 61 MB/s | 457 kB 00:00 (84/155): policycoreutils-2.5-34.el7.x86_64.rpm 53 MB/s | 917 kB 00:00 (85/155): python-IPy-0.75-6.el7.noarch.rpm 5.3 MB/s | 32 kB 00:00 (86/155): python3-pip-9.0.3-8.el7.noarch.rpm 84 MB/s | 1.6 MB 00:00 (87/155): scl-utils-20130529-19.el7.x86_64.rpm 15 MB/s | 24 kB 00:00 (88/155): python3-setuptools-39.2.0-10.el7.noar 17 MB/s | 629 kB 00:00 (89/155): setools-libs-3.3.8-4.el7.x86_64.rpm 31 MB/s | 620 kB 00:00 (90/155): urw-base35-d050000l-fonts-20170801-10 15 MB/s | 75 kB 00:00 (91/155): urw-base35-fonts-common-20170801-10.e 5.8 MB/s | 19 kB 00:00 (92/155): urw-base35-standard-symbols-ps-fonts- 13 MB/s | 40 kB 00:00 (93/155): urw-base35-z003-fonts-20170801-10.el7 49 MB/s | 275 kB 00:00 (94/155): xorg-x11-font-utils-7.5-21.el7.x86_64 20 MB/s | 104 kB 00:00 (95/155): xorg-x11-server-utils-7.7-20.el7.x86_ 31 MB/s | 178 kB 00:00 (96/155): xorg-x11-fonts-ISO8859-1-75dpi-7.5-9. 59 MB/s | 933 kB 00:00 (97/155): freetype-2.8-14.el7_9.1.x86_64.rpm 29 MB/s | 380 kB 00:00 (98/155): libX11-common-1.6.7-3.el7_9.noarch.rp 49 MB/s | 164 kB 00:00 (99/155): libcroco-0.6.12-6.el7_9.x86_64.rpm 37 MB/s | 105 kB 00:00 (100/155): libX11-1.6.7-3.el7_9.x86_64.rpm 42 MB/s | 607 kB 00:00 (101/155): mesa-libEGL-18.3.4-12.el7_9.x86_64.r 17 MB/s | 110 kB 00:00 (102/155): mesa-libGL-18.3.4-12.el7_9.x86_64.rp 34 MB/s | 166 kB 00:00 (103/155): mesa-libgbm-18.3.4-12.el7_9.x86_64.r 11 MB/s | 39 kB 00:00 (104/155): mesa-libglapi-18.3.4-12.el7_9.x86_64 20 MB/s | 46 kB 00:00 (105/155): python-2.7.5-90.el7.x86_64.rpm 28 MB/s | 96 kB 00:00 (106/155): python3-3.6.8-18.el7.x86_64.rpm 14 MB/s | 70 kB 00:00 (107/155): tcsh-6.18.01-17.el7_9.1.x86_64.rpm 51 MB/s | 339 kB 00:00 (108/155): devtoolset-8-binutils-2.30-55.el7.2. 41 MB/s | 5.5 MB 00:00 (109/155): python3-libs-3.6.8-18.el7.x86_64.rpm 38 MB/s | 6.9 MB 00:00 (110/155): devtoolset-8-gcc-c++-8.3.1-3.2.el7.x 48 MB/s | 12 MB 00:00 (111/155): devtoolset-8-libstdc++-devel-8.3.1-3 48 MB/s | 2.7 MB 00:00 (112/155): devtoolset-8-runtime-8.1-1.el7.x86_6 7.3 MB/s | 20 kB 00:00 (113/155): devtoolset-8-gcc-8.3.1-3.2.el7.x86_6 59 MB/s | 30 MB 00:00 (114/155): HepMC3-3.2.3-1.el7.x86_64.rpm 962 kB/s | 229 kB 00:00 (115/155): HepMC3-devel-3.2.3-1.el7.x86_64.rpm 674 kB/s | 59 kB 00:00 (116/155): HepMC3-rootIO-3.2.3-1.el7.x86_64.rpm 1.9 MB/s | 47 kB 00:00 (117/155): HepMC3-rootIO-devel-3.2.3-1.el7.x86_ 537 kB/s | 8.4 kB 00:00 (118/155): HepMC3-search-3.2.3-1.el7.x86_64.rpm 1.9 MB/s | 38 kB 00:00 (119/155): HepMC3-search-devel-3.2.3-1.el7.x86_ 782 kB/s | 14 kB 00:00 (120/155): Rivet-3.0.2-6.el7.x86_64.rpm 24 MB/s | 68 MB 00:02 (121/155): google-droid-sans-fonts-20120715-12. 7.5 MB/s | 2.5 MB 00:00 (122/155): lhapdf-6.3.0-1.el7.x86_64.rpm 1.0 MB/s | 339 kB 00:00 (123/155): libAfterImage-1.20-21.el7.x86_64.rpm 7.2 MB/s | 233 kB 00:00 (124/155): lhapdf-devel-6.3.0-1.el7.x86_64.rpm 429 kB/s | 39 kB 00:00 (125/155): libzstd-1.4.7-1.el7.x86_64.rpm 6.7 MB/s | 325 kB 00:00 (126/155): pythia8-8.2.44-2.el7.x86_64.rpm 33 MB/s | 1.9 MB 00:00 (127/155): pythia8-devel-8.2.44-2.el7.x86_64.rp 7.2 MB/s | 995 kB 00:00 (128/155): root-cling-6.22.06-1.el7.x86_64.rpm 45 MB/s | 15 MB 00:00 (129/155): pythia8-data-8.2.44-2.el7.noarch.rpm 21 MB/s | 8.6 MB 00:00 (130/155): root-fonts-6.22.06-1.el7.noarch.rpm 11 MB/s | 479 kB 00:00 (131/155): root-graf-asimage-6.22.06-1.el7.x86_ 6.5 MB/s | 133 kB 00:00 (132/155): root-graf-6.22.06-1.el7.x86_64.rpm 10 MB/s | 417 kB 00:00 (133/155): root-graf-gpad-6.22.06-1.el7.x86_64. 12 MB/s | 256 kB 00:00 (134/155): root-graf-postscript-6.22.06-1.el7.x 7.2 MB/s | 154 kB 00:00 (135/155): root-graf-x11-6.22.06-1.el7.x86_64.r 6.4 MB/s | 123 kB 00:00 (136/155): root-graf3d-6.22.06-1.el7.x86_64.rpm 12 MB/s | 222 kB 00:00 (137/155): root-gui-6.22.06-1.el7.x86_64.rpm 29 MB/s | 1.0 MB 00:00 (138/155): root-gui-ged-6.22.06-1.el7.x86_64.rp 10 MB/s | 332 kB 00:00 (139/155): root-hist-6.22.06-1.el7.x86_64.rpm 30 MB/s | 1.1 MB 00:00 (140/155): root-hist-painter-6.22.06-1.el7.x86_ 7.4 MB/s | 232 kB 00:00 (141/155): root-icons-6.22.06-1.el7.noarch.rpm 22 MB/s | 543 kB 00:00 (142/155): root-io-6.22.06-1.el7.x86_64.rpm 24 MB/s | 813 kB 00:00 (143/155): root-mathcore-6.22.06-1.el7.x86_64.r 25 MB/s | 1.1 MB 00:00 (144/155): root-mathmore-6.22.06-1.el7.x86_64.r 6.9 MB/s | 243 kB 00:00 (145/155): root-matrix-6.22.06-1.el7.x86_64.rpm 11 MB/s | 409 kB 00:00 (146/155): root-minuit-6.22.06-1.el7.x86_64.rpm 5.4 MB/s | 194 kB 00:00 (147/155): root-multiproc-6.22.06-1.el7.x86_64. 3.3 MB/s | 66 kB 00:00 (148/155): root-net-6.22.06-1.el7.x86_64.rpm 8.9 MB/s | 269 kB 00:00 (149/155): root-physics-6.22.06-1.el7.x86_64.rp 8.5 MB/s | 143 kB 00:00 (150/155): root-tree-dataframe-6.22.06-1.el7.x8 10 MB/s | 292 kB 00:00 (151/155): root-tree-6.22.06-1.el7.x86_64.rpm 12 MB/s | 478 kB 00:00 (152/155): root-vecops-6.22.06-1.el7.x86_64.rpm 8.5 MB/s | 191 kB 00:00 (153/155): root-tree-player-6.22.06-1.el7.x86_6 11 MB/s | 449 kB 00:00 (154/155): xxhash-libs-0.8.0-1.el7.x86_64.rpm 1.0 MB/s | 26 kB 00:00 (155/155): root-core-6.22.06-1.el7.x86_64.rpm 39 MB/s | 41 MB 00:01 -------------------------------------------------------------------------------- Total 60 MB/s | 271 MB 00:04 warning: /var/lib/mock/epel-7-x86_64-1611775033.207788/root/var/cache/dnf/centos-sclo-rh-7d964f0c0d64bc8e/packages/devtoolset-8-binutils-2.30-55.el7.2.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID f2ee9d55: NOKEY CentOS-7 - SCLo rh 1.0 MB/s | 1.0 kB 00:00 Importing GPG key 0xF2EE9D55: Userid : "CentOS SoftwareCollections SIG (https://wiki.centos.org/SpecialInterestGroup/SCLo) " Fingerprint: C4DB D535 B1FB BA14 F8BA 64A8 4EB8 4E71 F2EE 9D55 From : /usr/share/distribution-gpg-keys/centos/RPM-GPG-KEY-CentOS-SIG-SCLo Key imported successfully Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : python-2.7.5-90.el7.x86_64 1/155 Installing : HepMC3-3.2.3-1.el7.x86_64 2/155 Running scriptlet: HepMC3-3.2.3-1.el7.x86_64 2/155 Installing : libpng-2:1.5.13-8.el7.x86_64 3/155 Running scriptlet: libpng-2:1.5.13-8.el7.x86_64 3/155 Installing : freetype-2.8-14.el7_9.1.x86_64 4/155 Running scriptlet: freetype-2.8-14.el7_9.1.x86_64 4/155 Installing : fontpackages-filesystem-1.44-8.el7.noarch 5/155 Installing : libjpeg-turbo-1.2.90-8.el7.x86_64 6/155 Running scriptlet: libjpeg-turbo-1.2.90-8.el7.x86_64 6/155 Installing : libICE-1.0.9-9.el7.x86_64 7/155 Running scriptlet: libICE-1.0.9-9.el7.x86_64 7/155 Installing : fastjet-3.3.4-2.el7.x86_64 8/155 Installing : gnu-free-fonts-common-20120503-18.el7.noarch 9/155 Installing : urw-base35-fonts-common-20170801-10.el7.noarch 10/155 Installing : HepMC3-devel-3.2.3-1.el7.x86_64 11/155 Installing : HepMC3-search-3.2.3-1.el7.x86_64 12/155 Running scriptlet: HepMC3-search-3.2.3-1.el7.x86_64 12/155 Installing : mesa-libglapi-18.3.4-12.el7_9.x86_64 13/155 Running scriptlet: mesa-libglapi-18.3.4-12.el7_9.x86_64 13/155 Installing : libquadmath-4.8.5-44.el7.x86_64 14/155 Running scriptlet: libquadmath-4.8.5-44.el7.x86_64 14/155 Installing : libgfortran-4.8.5-44.el7.x86_64 15/155 Running scriptlet: libgfortran-4.8.5-44.el7.x86_64 15/155 Installing : YODA-1.7.7-3.el7.x86_64 16/155 Installing : fastjet-devel-3.3.4-2.el7.x86_64 17/155 Installing : fjcontrib-1.045-1.el7.x86_64 18/155 Running scriptlet: fjcontrib-1.045-1.el7.x86_64 18/155 Installing : libSM-1.2.2-2.el7.x86_64 19/155 Running scriptlet: libSM-1.2.2-2.el7.x86_64 19/155 Installing : lhapdf-6.3.0-1.el7.x86_64 20/155 Running scriptlet: lhapdf-6.3.0-1.el7.x86_64 20/155 Installing : libxshmfence-1.2-1.el7.x86_64 21/155 Running scriptlet: libxshmfence-1.2-1.el7.x86_64 21/155 Installing : libwayland-server-1.15.0-1.el7.x86_64 22/155 Running scriptlet: libwayland-server-1.15.0-1.el7.x86_64 22/155 Installing : libglvnd-1:1.0.1-0.8.git5baa1e5.el7.x86_64 23/155 Running scriptlet: libglvnd-1:1.0.1-0.8.git5baa1e5.el7.x86_64 23/155 Installing : python-YODA-1.7.7-3.el7.x86_64 24/155 Installing : atlas-3.10.1-12.el7.x86_64 25/155 Running scriptlet: atlas-3.10.1-12.el7.x86_64 25/155 Installing : gsl-1.15-13.el7.x86_64 26/155 Running scriptlet: gsl-1.15-13.el7.x86_64 26/155 Installing : Rivet-3.0.2-6.el7.x86_64 27/155 Installing : HepMC3-search-devel-3.2.3-1.el7.x86_64 28/155 Installing : gnu-free-mono-fonts-20120503-18.el7.noarch 29/155 Running scriptlet: gnu-free-mono-fonts-20120503-18.el7.noarch 29/155 Installing : gnu-free-sans-fonts-20120503-18.el7.noarch 30/155 Running scriptlet: gnu-free-sans-fonts-20120503-18.el7.noarch 30/155 Installing : gnu-free-serif-fonts-20120503-18.el7.noarch 31/155 Running scriptlet: gnu-free-serif-fonts-20120503-18.el7.noarch 31/155 Installing : jasper-libs-1.900.1-33.el7.x86_64 32/155 Running scriptlet: jasper-libs-1.900.1-33.el7.x86_64 32/155 Installing : dejavu-fonts-common-2.33-6.el7.noarch 33/155 Installing : dejavu-sans-fonts-2.33-6.el7.noarch 34/155 Running scriptlet: dejavu-sans-fonts-2.33-6.el7.noarch 34/155 Installing : fontconfig-2.13.0-4.3.el7.x86_64 35/155 Running scriptlet: fontconfig-2.13.0-4.3.el7.x86_64 35/155 Installing : google-droid-sans-fonts-20120715-12.el7.noarch 36/155 Running scriptlet: google-droid-sans-fonts-20120715-12.el7.noarch 36/155 Installing : audit-libs-python-2.8.5-4.el7.x86_64 37/155 Installing : libselinux-python-2.5-15.el7.x86_64 38/155 Installing : libsemanage-python-2.5-14.el7.x86_64 39/155 Installing : python-IPy-0.75-6.el7.noarch 40/155 Installing : xxhash-libs-0.8.0-1.el7.x86_64 41/155 Running scriptlet: xxhash-libs-0.8.0-1.el7.x86_64 41/155 Installing : pythia8-data-8.2.44-2.el7.noarch 42/155 Installing : pythia8-8.2.44-2.el7.x86_64 43/155 Running scriptlet: pythia8-8.2.44-2.el7.x86_64 43/155 Installing : libzstd-1.4.7-1.el7.x86_64 44/155 Running scriptlet: libzstd-1.4.7-1.el7.x86_64 44/155 Installing : tcsh-6.18.01-17.el7_9.1.x86_64 45/155 Running scriptlet: tcsh-6.18.01-17.el7_9.1.x86_64 45/155 Installing : libcroco-0.6.12-6.el7_9.x86_64 46/155 Running scriptlet: libcroco-0.6.12-6.el7_9.x86_64 46/155 Installing : libX11-common-1.6.7-3.el7_9.noarch 47/155 Installing : setools-libs-3.3.8-4.el7.x86_64 48/155 Running scriptlet: setools-libs-3.3.8-4.el7.x86_64 48/155 Installing : scl-utils-20130529-19.el7.x86_64 49/155 Installing : pixman-0.34.0-1.el7.x86_64 50/155 Running scriptlet: pixman-0.34.0-1.el7.x86_64 50/155 Installing : perl-Test-Harness-3.28-3.el7.noarch 51/155 Installing : perl-Data-Dumper-2.145-3.el7.x86_64 52/155 Installing : perl-Compress-Raw-Zlib-1:2.061-4.el7.x86_64 53/155 Installing : perl-Compress-Raw-Bzip2-2.061-3.el7.x86_64 54/155 Installing : perl-IO-Compress-2.061-2.el7.noarch 55/155 Installing : MG5_aMC-2.7.2-1.el7.x86_64 56/155 Installing : m4-1.4.16-10.el7.x86_64 57/155 Running scriptlet: m4-1.4.16-10.el7.x86_64 57/155 Installing : autoconf-2.69-11.el7.noarch 58/155 Running scriptlet: autoconf-2.69-11.el7.noarch 58/155 Installing : automake-1.13.4-3.el7.noarch 59/155 Running scriptlet: automake-1.13.4-3.el7.noarch 59/155 Installing : gsl-devel-1.15-13.el7.x86_64 60/155 Running scriptlet: gsl-devel-1.15-13.el7.x86_64 60/155 Installing : libwayland-client-1.15.0-1.el7.x86_64 61/155 Running scriptlet: libwayland-client-1.15.0-1.el7.x86_64 61/155 Installing : libtirpc-0.2.4-0.16.el7.x86_64 62/155 Running scriptlet: libtirpc-0.2.4-0.16.el7.x86_64 62/155 Installing : python3-pip-9.0.3-8.el7.noarch 63/155 Installing : python3-setuptools-39.2.0-10.el7.noarch 64/155 Installing : python3-3.6.8-18.el7.x86_64 65/155 Installing : python3-libs-3.6.8-18.el7.x86_64 66/155 Installing : libthai-0.1.14-9.el7.x86_64 67/155 Running scriptlet: libthai-0.1.14-9.el7.x86_64 67/155 Installing : libselinux-utils-2.5-15.el7.x86_64 68/155 Installing : policycoreutils-2.5-34.el7.x86_64 69/155 Installing : libfontenc-1.1.3-3.el7.x86_64 70/155 Running scriptlet: libfontenc-1.1.3-3.el7.x86_64 70/155 Installing : xorg-x11-font-utils-1:7.5-21.el7.x86_64 71/155 Installing : xorg-x11-fonts-ISO8859-1-75dpi-7.5-9.el7.noarch 72/155 Running scriptlet: xorg-x11-fonts-ISO8859-1-75dpi-7.5-9.el7.noarch 72/155 Running scriptlet: libcgroup-0.41-21.el7.x86_64 73/155 Installing : libcgroup-0.41-21.el7.x86_64 73/155 Running scriptlet: libcgroup-0.41-21.el7.x86_64 73/155 Installing : libXau-1.0.8-2.1.el7.x86_64 74/155 Running scriptlet: libXau-1.0.8-2.1.el7.x86_64 74/155 Installing : libxcb-1.13-1.el7.x86_64 75/155 Running scriptlet: libxcb-1.13-1.el7.x86_64 75/155 Installing : libX11-1.6.7-3.el7_9.x86_64 76/155 Running scriptlet: libX11-1.6.7-3.el7_9.x86_64 76/155 Installing : libXext-1.3.3-3.el7.x86_64 77/155 Running scriptlet: libXext-1.3.3-3.el7.x86_64 77/155 Installing : libXrender-0.9.10-1.el7.x86_64 78/155 Running scriptlet: libXrender-0.9.10-1.el7.x86_64 78/155 Installing : libXfixes-5.0.3-1.el7.x86_64 79/155 Running scriptlet: libXfixes-5.0.3-1.el7.x86_64 79/155 Installing : libXft-2.3.2-2.el7.x86_64 80/155 Running scriptlet: libXft-2.3.2-2.el7.x86_64 80/155 Installing : libXxf86vm-1.1.4-1.el7.x86_64 81/155 Running scriptlet: libXxf86vm-1.1.4-1.el7.x86_64 81/155 Installing : libXt-1.1.5-3.el7.x86_64 82/155 Running scriptlet: libXt-1.1.5-3.el7.x86_64 82/155 Installing : libXmu-1.1.2-2.el7.x86_64 83/155 Running scriptlet: libXmu-1.1.2-2.el7.x86_64 83/155 Installing : libXcursor-1.1.15-1.el7.x86_64 84/155 Running scriptlet: libXcursor-1.1.15-1.el7.x86_64 84/155 Installing : libXdamage-1.1.4-4.1.el7.x86_64 85/155 Running scriptlet: libXdamage-1.1.4-4.1.el7.x86_64 85/155 Installing : libXrandr-1.5.1-2.el7.x86_64 86/155 Running scriptlet: libXrandr-1.5.1-2.el7.x86_64 86/155 Installing : libXi-1.7.9-1.el7.x86_64 87/155 Running scriptlet: libXi-1.7.9-1.el7.x86_64 87/155 Installing : libXinerama-1.1.3-2.1.el7.x86_64 88/155 Running scriptlet: libXinerama-1.1.3-2.1.el7.x86_64 88/155 Installing : libXxf86misc-1.0.3-7.1.el7.x86_64 89/155 Running scriptlet: libXxf86misc-1.0.3-7.1.el7.x86_64 89/155 Installing : xorg-x11-server-utils-7.7-20.el7.x86_64 90/155 Installing : urw-base35-d050000l-fonts-20170801-10.el7.noarch 91/155 Running scriptlet: urw-base35-d050000l-fonts-20170801-10.el7.noarch 91/155 Installing : urw-base35-standard-symbols-ps-fonts-20170801-10 92/155 Running scriptlet: urw-base35-standard-symbols-ps-fonts-20170801-10 92/155 Installing : urw-base35-z003-fonts-20170801-10.el7.noarch 93/155 Running scriptlet: urw-base35-z003-fonts-20170801-10.el7.noarch 93/155 Installing : giflib-4.1.6-9.el7.x86_64 94/155 Running scriptlet: giflib-4.1.6-9.el7.x86_64 94/155 Installing : libXpm-3.5.12-1.el7.x86_64 95/155 Running scriptlet: libXpm-3.5.12-1.el7.x86_64 95/155 Installing : jbigkit-libs-2.0-11.el7.x86_64 96/155 Running scriptlet: jbigkit-libs-2.0-11.el7.x86_64 96/155 Installing : libtiff-4.0.3-35.el7.x86_64 97/155 Running scriptlet: libtiff-4.0.3-35.el7.x86_64 97/155 Installing : gdk-pixbuf2-2.36.12-3.el7.x86_64 98/155 Running scriptlet: gdk-pixbuf2-2.36.12-3.el7.x86_64 98/155 Installing : hwdata-0.252-9.7.el7.x86_64 99/155 Running scriptlet: hwdata-0.252-9.7.el7.x86_64 99/155 Installing : libpciaccess-0.14-1.el7.x86_64 100/155 Running scriptlet: libpciaccess-0.14-1.el7.x86_64 100/155 Installing : libdrm-2.4.97-2.el7.x86_64 101/155 Running scriptlet: libdrm-2.4.97-2.el7.x86_64 101/155 Installing : libglvnd-glx-1:1.0.1-0.8.git5baa1e5.el7.x86_64 102/155 Running scriptlet: libglvnd-glx-1:1.0.1-0.8.git5baa1e5.el7.x86_64 102/155 Installing : mesa-libGL-18.3.4-12.el7_9.x86_64 103/155 Running scriptlet: mesa-libGL-18.3.4-12.el7_9.x86_64 103/155 Installing : mesa-libgbm-18.3.4-12.el7_9.x86_64 104/155 Running scriptlet: mesa-libgbm-18.3.4-12.el7_9.x86_64 104/155 Installing : libglvnd-egl-1:1.0.1-0.8.git5baa1e5.el7.x86_64 105/155 Running scriptlet: libglvnd-egl-1:1.0.1-0.8.git5baa1e5.el7.x86_64 105/155 Installing : mesa-libEGL-18.3.4-12.el7_9.x86_64 106/155 Running scriptlet: mesa-libEGL-18.3.4-12.el7_9.x86_64 106/155 Installing : cairo-1.15.12-4.el7.x86_64 107/155 Running scriptlet: cairo-1.15.12-4.el7.x86_64 107/155 Installing : graphite2-1.3.10-1.el7_3.x86_64 108/155 Running scriptlet: graphite2-1.3.10-1.el7_3.x86_64 108/155 Installing : harfbuzz-1.7.5-2.el7.x86_64 109/155 Running scriptlet: harfbuzz-1.7.5-2.el7.x86_64 109/155 Installing : fribidi-1.0.2-1.el7_7.1.x86_64 110/155 Running scriptlet: fribidi-1.0.2-1.el7_7.1.x86_64 110/155 Installing : pango-1.42.4-4.el7_7.x86_64 111/155 Running scriptlet: pango-1.42.4-4.el7_7.x86_64 111/155 Installing : librsvg2-2.40.20-1.el7.x86_64 112/155 Running scriptlet: librsvg2-2.40.20-1.el7.x86_64 112/155 Installing : libAfterImage-1.20-21.el7.x86_64 113/155 Running scriptlet: libAfterImage-1.20-21.el7.x86_64 113/155 Installing : root-fonts-6.22.06-1.el7.noarch 114/155 Installing : root-icons-6.22.06-1.el7.noarch 115/155 Installing : root-cling-6.22.06-1.el7.x86_64 116/155 Running scriptlet: root-cling-6.22.06-1.el7.x86_64 116/155 Installing : root-io-6.22.06-1.el7.x86_64 117/155 Running scriptlet: root-io-6.22.06-1.el7.x86_64 117/155 Installing : root-mathmore-6.22.06-1.el7.x86_64 118/155 Running scriptlet: root-mathmore-6.22.06-1.el7.x86_64 118/155 Installing : root-graf-postscript-6.22.06-1.el7.x86_64 119/155 Running scriptlet: root-graf-postscript-6.22.06-1.el7.x86_64 119/155 Installing : root-graf-x11-6.22.06-1.el7.x86_64 120/155 Running scriptlet: root-graf-x11-6.22.06-1.el7.x86_64 120/155 Installing : root-graf-6.22.06-1.el7.x86_64 121/155 Running scriptlet: root-graf-6.22.06-1.el7.x86_64 121/155 Installing : root-graf-gpad-6.22.06-1.el7.x86_64 122/155 Running scriptlet: root-graf-gpad-6.22.06-1.el7.x86_64 122/155 Installing : root-graf3d-6.22.06-1.el7.x86_64 123/155 Running scriptlet: root-graf3d-6.22.06-1.el7.x86_64 123/155 Installing : root-hist-6.22.06-1.el7.x86_64 124/155 Running scriptlet: root-hist-6.22.06-1.el7.x86_64 124/155 Installing : root-hist-painter-6.22.06-1.el7.x86_64 125/155 Running scriptlet: root-hist-painter-6.22.06-1.el7.x86_64 125/155 Installing : root-matrix-6.22.06-1.el7.x86_64 126/155 Running scriptlet: root-matrix-6.22.06-1.el7.x86_64 126/155 Installing : root-mathcore-6.22.06-1.el7.x86_64 127/155 Running scriptlet: root-mathcore-6.22.06-1.el7.x86_64 127/155 Installing : root-minuit-6.22.06-1.el7.x86_64 128/155 Running scriptlet: root-minuit-6.22.06-1.el7.x86_64 128/155 Installing : root-multiproc-6.22.06-1.el7.x86_64 129/155 Running scriptlet: root-multiproc-6.22.06-1.el7.x86_64 129/155 Installing : root-net-6.22.06-1.el7.x86_64 130/155 Running scriptlet: root-net-6.22.06-1.el7.x86_64 130/155 Installing : root-physics-6.22.06-1.el7.x86_64 131/155 Running scriptlet: root-physics-6.22.06-1.el7.x86_64 131/155 Installing : root-tree-6.22.06-1.el7.x86_64 132/155 Running scriptlet: root-tree-6.22.06-1.el7.x86_64 132/155 Installing : root-graf-asimage-6.22.06-1.el7.x86_64 133/155 Running scriptlet: root-graf-asimage-6.22.06-1.el7.x86_64 133/155 Installing : root-gui-6.22.06-1.el7.x86_64 134/155 Running scriptlet: root-gui-6.22.06-1.el7.x86_64 134/155 Installing : root-gui-ged-6.22.06-1.el7.x86_64 135/155 Running scriptlet: root-gui-ged-6.22.06-1.el7.x86_64 135/155 Installing : root-tree-dataframe-6.22.06-1.el7.x86_64 136/155 Running scriptlet: root-tree-dataframe-6.22.06-1.el7.x86_64 136/155 Installing : root-tree-player-6.22.06-1.el7.x86_64 137/155 Running scriptlet: root-tree-player-6.22.06-1.el7.x86_64 137/155 Installing : root-vecops-6.22.06-1.el7.x86_64 138/155 Running scriptlet: root-vecops-6.22.06-1.el7.x86_64 138/155 Installing : root-core-6.22.06-1.el7.x86_64 139/155 Running scriptlet: root-core-6.22.06-1.el7.x86_64 139/155 Installing : HepMC3-rootIO-3.2.3-1.el7.x86_64 140/155 Running scriptlet: HepMC3-rootIO-3.2.3-1.el7.x86_64 140/155 Installing : HepMC3-rootIO-devel-3.2.3-1.el7.x86_64 141/155 Installing : checkpolicy-2.5-8.el7.x86_64 142/155 Installing : policycoreutils-python-2.5-34.el7.x86_64 143/155 Installing : devtoolset-8-runtime-8.1-1.el7.x86_64 144/155 Running scriptlet: devtoolset-8-runtime-8.1-1.el7.x86_64 144/155 ValueError: SELinux policy is not managed or store cannot be accessed. Installing : devtoolset-8-binutils-2.30-55.el7.2.x86_64 145/155 Running scriptlet: devtoolset-8-binutils-2.30-55.el7.2.x86_64 145/155 Installing : devtoolset-8-libstdc++-devel-8.3.1-3.2.el7.x86_6 146/155 Installing : YODA-devel-1.7.7-3.el7.x86_64 147/155 Installing : Rivet-devel-3.0.2-6.el7.x86_64 148/155 Installing : ThePEG-2.1.5-7.el7.x86_64 149/155 Installing : ThePEG-devel-2.1.5-7.el7.x86_64 150/155 Installing : libtool-2.4.2-22.el7_3.x86_64 151/155 Running scriptlet: libtool-2.4.2-22.el7_3.x86_64 151/155 Installing : pythia8-devel-8.2.44-2.el7.x86_64 152/155 Installing : lhapdf-devel-6.3.0-1.el7.x86_64 153/155 Installing : devtoolset-8-gcc-8.3.1-3.2.el7.x86_64 154/155 Installing : devtoolset-8-gcc-c++-8.3.1-3.2.el7.x86_64 155/155 Running scriptlet: urw-base35-d050000l-fonts-20170801-10.el7.noarch 155/155 Running scriptlet: urw-base35-standard-symbols-ps-fonts-20170801-10 155/155 Running scriptlet: urw-base35-z003-fonts-20170801-10.el7.noarch 155/155 Verifying : MG5_aMC-2.7.2-1.el7.x86_64 1/155 Verifying : Rivet-3.0.2-6.el7.x86_64 2/155 Verifying : Rivet-devel-3.0.2-6.el7.x86_64 3/155 Verifying : ThePEG-2.1.5-7.el7.x86_64 4/155 Verifying : ThePEG-devel-2.1.5-7.el7.x86_64 5/155 Verifying : YODA-1.7.7-3.el7.x86_64 6/155 Verifying : YODA-devel-1.7.7-3.el7.x86_64 7/155 Verifying : fastjet-3.3.4-2.el7.x86_64 8/155 Verifying : fastjet-devel-3.3.4-2.el7.x86_64 9/155 Verifying : fjcontrib-1.045-1.el7.x86_64 10/155 Verifying : gnu-free-fonts-common-20120503-18.el7.noarch 11/155 Verifying : gnu-free-mono-fonts-20120503-18.el7.noarch 12/155 Verifying : gnu-free-sans-fonts-20120503-18.el7.noarch 13/155 Verifying : gnu-free-serif-fonts-20120503-18.el7.noarch 14/155 Verifying : python-YODA-1.7.7-3.el7.x86_64 15/155 Verifying : atlas-3.10.1-12.el7.x86_64 16/155 Verifying : audit-libs-python-2.8.5-4.el7.x86_64 17/155 Verifying : autoconf-2.69-11.el7.noarch 18/155 Verifying : automake-1.13.4-3.el7.noarch 19/155 Verifying : cairo-1.15.12-4.el7.x86_64 20/155 Verifying : checkpolicy-2.5-8.el7.x86_64 21/155 Verifying : dejavu-fonts-common-2.33-6.el7.noarch 22/155 Verifying : dejavu-sans-fonts-2.33-6.el7.noarch 23/155 Verifying : fontconfig-2.13.0-4.3.el7.x86_64 24/155 Verifying : fontpackages-filesystem-1.44-8.el7.noarch 25/155 Verifying : fribidi-1.0.2-1.el7_7.1.x86_64 26/155 Verifying : gdk-pixbuf2-2.36.12-3.el7.x86_64 27/155 Verifying : giflib-4.1.6-9.el7.x86_64 28/155 Verifying : graphite2-1.3.10-1.el7_3.x86_64 29/155 Verifying : gsl-1.15-13.el7.x86_64 30/155 Verifying : gsl-devel-1.15-13.el7.x86_64 31/155 Verifying : harfbuzz-1.7.5-2.el7.x86_64 32/155 Verifying : hwdata-0.252-9.7.el7.x86_64 33/155 Verifying : jasper-libs-1.900.1-33.el7.x86_64 34/155 Verifying : jbigkit-libs-2.0-11.el7.x86_64 35/155 Verifying : libICE-1.0.9-9.el7.x86_64 36/155 Verifying : libSM-1.2.2-2.el7.x86_64 37/155 Verifying : libXau-1.0.8-2.1.el7.x86_64 38/155 Verifying : libXcursor-1.1.15-1.el7.x86_64 39/155 Verifying : libXdamage-1.1.4-4.1.el7.x86_64 40/155 Verifying : libXext-1.3.3-3.el7.x86_64 41/155 Verifying : libXfixes-5.0.3-1.el7.x86_64 42/155 Verifying : libXft-2.3.2-2.el7.x86_64 43/155 Verifying : libXi-1.7.9-1.el7.x86_64 44/155 Verifying : libXinerama-1.1.3-2.1.el7.x86_64 45/155 Verifying : libXmu-1.1.2-2.el7.x86_64 46/155 Verifying : libXpm-3.5.12-1.el7.x86_64 47/155 Verifying : libXrandr-1.5.1-2.el7.x86_64 48/155 Verifying : libXrender-0.9.10-1.el7.x86_64 49/155 Verifying : libXt-1.1.5-3.el7.x86_64 50/155 Verifying : libXxf86misc-1.0.3-7.1.el7.x86_64 51/155 Verifying : libXxf86vm-1.1.4-1.el7.x86_64 52/155 Verifying : libcgroup-0.41-21.el7.x86_64 53/155 Verifying : libdrm-2.4.97-2.el7.x86_64 54/155 Verifying : libfontenc-1.1.3-3.el7.x86_64 55/155 Verifying : libgfortran-4.8.5-44.el7.x86_64 56/155 Verifying : libglvnd-1:1.0.1-0.8.git5baa1e5.el7.x86_64 57/155 Verifying : libglvnd-egl-1:1.0.1-0.8.git5baa1e5.el7.x86_64 58/155 Verifying : libglvnd-glx-1:1.0.1-0.8.git5baa1e5.el7.x86_64 59/155 Verifying : libjpeg-turbo-1.2.90-8.el7.x86_64 60/155 Verifying : libpciaccess-0.14-1.el7.x86_64 61/155 Verifying : libpng-2:1.5.13-8.el7.x86_64 62/155 Verifying : libquadmath-4.8.5-44.el7.x86_64 63/155 Verifying : librsvg2-2.40.20-1.el7.x86_64 64/155 Verifying : libselinux-python-2.5-15.el7.x86_64 65/155 Verifying : libselinux-utils-2.5-15.el7.x86_64 66/155 Verifying : libsemanage-python-2.5-14.el7.x86_64 67/155 Verifying : libthai-0.1.14-9.el7.x86_64 68/155 Verifying : libtiff-4.0.3-35.el7.x86_64 69/155 Verifying : libtirpc-0.2.4-0.16.el7.x86_64 70/155 Verifying : libtool-2.4.2-22.el7_3.x86_64 71/155 Verifying : libwayland-client-1.15.0-1.el7.x86_64 72/155 Verifying : libwayland-server-1.15.0-1.el7.x86_64 73/155 Verifying : libxcb-1.13-1.el7.x86_64 74/155 Verifying : libxshmfence-1.2-1.el7.x86_64 75/155 Verifying : m4-1.4.16-10.el7.x86_64 76/155 Verifying : pango-1.42.4-4.el7_7.x86_64 77/155 Verifying : perl-Compress-Raw-Bzip2-2.061-3.el7.x86_64 78/155 Verifying : perl-Compress-Raw-Zlib-1:2.061-4.el7.x86_64 79/155 Verifying : perl-Data-Dumper-2.145-3.el7.x86_64 80/155 Verifying : perl-IO-Compress-2.061-2.el7.noarch 81/155 Verifying : perl-Test-Harness-3.28-3.el7.noarch 82/155 Verifying : pixman-0.34.0-1.el7.x86_64 83/155 Verifying : policycoreutils-2.5-34.el7.x86_64 84/155 Verifying : policycoreutils-python-2.5-34.el7.x86_64 85/155 Verifying : python-IPy-0.75-6.el7.noarch 86/155 Verifying : python3-pip-9.0.3-8.el7.noarch 87/155 Verifying : python3-setuptools-39.2.0-10.el7.noarch 88/155 Verifying : scl-utils-20130529-19.el7.x86_64 89/155 Verifying : setools-libs-3.3.8-4.el7.x86_64 90/155 Verifying : urw-base35-d050000l-fonts-20170801-10.el7.noarch 91/155 Verifying : urw-base35-fonts-common-20170801-10.el7.noarch 92/155 Verifying : urw-base35-standard-symbols-ps-fonts-20170801-10 93/155 Verifying : urw-base35-z003-fonts-20170801-10.el7.noarch 94/155 Verifying : xorg-x11-font-utils-1:7.5-21.el7.x86_64 95/155 Verifying : xorg-x11-fonts-ISO8859-1-75dpi-7.5-9.el7.noarch 96/155 Verifying : xorg-x11-server-utils-7.7-20.el7.x86_64 97/155 Verifying : freetype-2.8-14.el7_9.1.x86_64 98/155 Verifying : libX11-1.6.7-3.el7_9.x86_64 99/155 Verifying : libX11-common-1.6.7-3.el7_9.noarch 100/155 Verifying : libcroco-0.6.12-6.el7_9.x86_64 101/155 Verifying : mesa-libEGL-18.3.4-12.el7_9.x86_64 102/155 Verifying : mesa-libGL-18.3.4-12.el7_9.x86_64 103/155 Verifying : mesa-libgbm-18.3.4-12.el7_9.x86_64 104/155 Verifying : mesa-libglapi-18.3.4-12.el7_9.x86_64 105/155 Verifying : python-2.7.5-90.el7.x86_64 106/155 Verifying : python3-3.6.8-18.el7.x86_64 107/155 Verifying : python3-libs-3.6.8-18.el7.x86_64 108/155 Verifying : tcsh-6.18.01-17.el7_9.1.x86_64 109/155 Verifying : devtoolset-8-binutils-2.30-55.el7.2.x86_64 110/155 Verifying : devtoolset-8-gcc-8.3.1-3.2.el7.x86_64 111/155 Verifying : devtoolset-8-gcc-c++-8.3.1-3.2.el7.x86_64 112/155 Verifying : devtoolset-8-libstdc++-devel-8.3.1-3.2.el7.x86_6 113/155 Verifying : devtoolset-8-runtime-8.1-1.el7.x86_64 114/155 Verifying : HepMC3-3.2.3-1.el7.x86_64 115/155 Verifying : HepMC3-devel-3.2.3-1.el7.x86_64 116/155 Verifying : HepMC3-rootIO-3.2.3-1.el7.x86_64 117/155 Verifying : HepMC3-rootIO-devel-3.2.3-1.el7.x86_64 118/155 Verifying : HepMC3-search-3.2.3-1.el7.x86_64 119/155 Verifying : HepMC3-search-devel-3.2.3-1.el7.x86_64 120/155 Verifying : google-droid-sans-fonts-20120715-12.el7.noarch 121/155 Verifying : lhapdf-6.3.0-1.el7.x86_64 122/155 Verifying : lhapdf-devel-6.3.0-1.el7.x86_64 123/155 Verifying : libAfterImage-1.20-21.el7.x86_64 124/155 Verifying : libzstd-1.4.7-1.el7.x86_64 125/155 Verifying : pythia8-8.2.44-2.el7.x86_64 126/155 Verifying : pythia8-data-8.2.44-2.el7.noarch 127/155 Verifying : pythia8-devel-8.2.44-2.el7.x86_64 128/155 Verifying : root-cling-6.22.06-1.el7.x86_64 129/155 Verifying : root-core-6.22.06-1.el7.x86_64 130/155 Verifying : root-fonts-6.22.06-1.el7.noarch 131/155 Verifying : root-graf-6.22.06-1.el7.x86_64 132/155 Verifying : root-graf-asimage-6.22.06-1.el7.x86_64 133/155 Verifying : root-graf-gpad-6.22.06-1.el7.x86_64 134/155 Verifying : root-graf-postscript-6.22.06-1.el7.x86_64 135/155 Verifying : root-graf-x11-6.22.06-1.el7.x86_64 136/155 Verifying : root-graf3d-6.22.06-1.el7.x86_64 137/155 Verifying : root-gui-6.22.06-1.el7.x86_64 138/155 Verifying : root-gui-ged-6.22.06-1.el7.x86_64 139/155 Verifying : root-hist-6.22.06-1.el7.x86_64 140/155 Verifying : root-hist-painter-6.22.06-1.el7.x86_64 141/155 Verifying : root-icons-6.22.06-1.el7.noarch 142/155 Verifying : root-io-6.22.06-1.el7.x86_64 143/155 Verifying : root-mathcore-6.22.06-1.el7.x86_64 144/155 Verifying : root-mathmore-6.22.06-1.el7.x86_64 145/155 Verifying : root-matrix-6.22.06-1.el7.x86_64 146/155 Verifying : root-minuit-6.22.06-1.el7.x86_64 147/155 Verifying : root-multiproc-6.22.06-1.el7.x86_64 148/155 Verifying : root-net-6.22.06-1.el7.x86_64 149/155 Verifying : root-physics-6.22.06-1.el7.x86_64 150/155 Verifying : root-tree-6.22.06-1.el7.x86_64 151/155 Verifying : root-tree-dataframe-6.22.06-1.el7.x86_64 152/155 Verifying : root-tree-player-6.22.06-1.el7.x86_64 153/155 Verifying : root-vecops-6.22.06-1.el7.x86_64 154/155 Verifying : xxhash-libs-0.8.0-1.el7.x86_64 155/155 Installed: HepMC3-3.2.3-1.el7.x86_64 HepMC3-devel-3.2.3-1.el7.x86_64 HepMC3-rootIO-3.2.3-1.el7.x86_64 HepMC3-rootIO-devel-3.2.3-1.el7.x86_64 HepMC3-search-3.2.3-1.el7.x86_64 HepMC3-search-devel-3.2.3-1.el7.x86_64 MG5_aMC-2.7.2-1.el7.x86_64 Rivet-3.0.2-6.el7.x86_64 Rivet-devel-3.0.2-6.el7.x86_64 ThePEG-2.1.5-7.el7.x86_64 ThePEG-devel-2.1.5-7.el7.x86_64 YODA-1.7.7-3.el7.x86_64 YODA-devel-1.7.7-3.el7.x86_64 atlas-3.10.1-12.el7.x86_64 audit-libs-python-2.8.5-4.el7.x86_64 autoconf-2.69-11.el7.noarch automake-1.13.4-3.el7.noarch cairo-1.15.12-4.el7.x86_64 checkpolicy-2.5-8.el7.x86_64 dejavu-fonts-common-2.33-6.el7.noarch dejavu-sans-fonts-2.33-6.el7.noarch devtoolset-8-binutils-2.30-55.el7.2.x86_64 devtoolset-8-gcc-8.3.1-3.2.el7.x86_64 devtoolset-8-gcc-c++-8.3.1-3.2.el7.x86_64 devtoolset-8-libstdc++-devel-8.3.1-3.2.el7.x86_64 devtoolset-8-runtime-8.1-1.el7.x86_64 fastjet-3.3.4-2.el7.x86_64 fastjet-devel-3.3.4-2.el7.x86_64 fjcontrib-1.045-1.el7.x86_64 fontconfig-2.13.0-4.3.el7.x86_64 fontpackages-filesystem-1.44-8.el7.noarch freetype-2.8-14.el7_9.1.x86_64 fribidi-1.0.2-1.el7_7.1.x86_64 gdk-pixbuf2-2.36.12-3.el7.x86_64 giflib-4.1.6-9.el7.x86_64 gnu-free-fonts-common-20120503-18.el7.noarch gnu-free-mono-fonts-20120503-18.el7.noarch gnu-free-sans-fonts-20120503-18.el7.noarch gnu-free-serif-fonts-20120503-18.el7.noarch google-droid-sans-fonts-20120715-12.el7.noarch graphite2-1.3.10-1.el7_3.x86_64 gsl-1.15-13.el7.x86_64 gsl-devel-1.15-13.el7.x86_64 harfbuzz-1.7.5-2.el7.x86_64 hwdata-0.252-9.7.el7.x86_64 jasper-libs-1.900.1-33.el7.x86_64 jbigkit-libs-2.0-11.el7.x86_64 lhapdf-6.3.0-1.el7.x86_64 lhapdf-devel-6.3.0-1.el7.x86_64 libAfterImage-1.20-21.el7.x86_64 libICE-1.0.9-9.el7.x86_64 libSM-1.2.2-2.el7.x86_64 libX11-1.6.7-3.el7_9.x86_64 libX11-common-1.6.7-3.el7_9.noarch libXau-1.0.8-2.1.el7.x86_64 libXcursor-1.1.15-1.el7.x86_64 libXdamage-1.1.4-4.1.el7.x86_64 libXext-1.3.3-3.el7.x86_64 libXfixes-5.0.3-1.el7.x86_64 libXft-2.3.2-2.el7.x86_64 libXi-1.7.9-1.el7.x86_64 libXinerama-1.1.3-2.1.el7.x86_64 libXmu-1.1.2-2.el7.x86_64 libXpm-3.5.12-1.el7.x86_64 libXrandr-1.5.1-2.el7.x86_64 libXrender-0.9.10-1.el7.x86_64 libXt-1.1.5-3.el7.x86_64 libXxf86misc-1.0.3-7.1.el7.x86_64 libXxf86vm-1.1.4-1.el7.x86_64 libcgroup-0.41-21.el7.x86_64 libcroco-0.6.12-6.el7_9.x86_64 libdrm-2.4.97-2.el7.x86_64 libfontenc-1.1.3-3.el7.x86_64 libgfortran-4.8.5-44.el7.x86_64 libglvnd-1:1.0.1-0.8.git5baa1e5.el7.x86_64 libglvnd-egl-1:1.0.1-0.8.git5baa1e5.el7.x86_64 libglvnd-glx-1:1.0.1-0.8.git5baa1e5.el7.x86_64 libjpeg-turbo-1.2.90-8.el7.x86_64 libpciaccess-0.14-1.el7.x86_64 libpng-2:1.5.13-8.el7.x86_64 libquadmath-4.8.5-44.el7.x86_64 librsvg2-2.40.20-1.el7.x86_64 libselinux-python-2.5-15.el7.x86_64 libselinux-utils-2.5-15.el7.x86_64 libsemanage-python-2.5-14.el7.x86_64 libthai-0.1.14-9.el7.x86_64 libtiff-4.0.3-35.el7.x86_64 libtirpc-0.2.4-0.16.el7.x86_64 libtool-2.4.2-22.el7_3.x86_64 libwayland-client-1.15.0-1.el7.x86_64 libwayland-server-1.15.0-1.el7.x86_64 libxcb-1.13-1.el7.x86_64 libxshmfence-1.2-1.el7.x86_64 libzstd-1.4.7-1.el7.x86_64 m4-1.4.16-10.el7.x86_64 mesa-libEGL-18.3.4-12.el7_9.x86_64 mesa-libGL-18.3.4-12.el7_9.x86_64 mesa-libgbm-18.3.4-12.el7_9.x86_64 mesa-libglapi-18.3.4-12.el7_9.x86_64 pango-1.42.4-4.el7_7.x86_64 perl-Compress-Raw-Bzip2-2.061-3.el7.x86_64 perl-Compress-Raw-Zlib-1:2.061-4.el7.x86_64 perl-Data-Dumper-2.145-3.el7.x86_64 perl-IO-Compress-2.061-2.el7.noarch perl-Test-Harness-3.28-3.el7.noarch pixman-0.34.0-1.el7.x86_64 policycoreutils-2.5-34.el7.x86_64 policycoreutils-python-2.5-34.el7.x86_64 pythia8-8.2.44-2.el7.x86_64 pythia8-data-8.2.44-2.el7.noarch pythia8-devel-8.2.44-2.el7.x86_64 python-2.7.5-90.el7.x86_64 python-IPy-0.75-6.el7.noarch python-YODA-1.7.7-3.el7.x86_64 python3-3.6.8-18.el7.x86_64 python3-libs-3.6.8-18.el7.x86_64 python3-pip-9.0.3-8.el7.noarch python3-setuptools-39.2.0-10.el7.noarch root-cling-6.22.06-1.el7.x86_64 root-core-6.22.06-1.el7.x86_64 root-fonts-6.22.06-1.el7.noarch root-graf-6.22.06-1.el7.x86_64 root-graf-asimage-6.22.06-1.el7.x86_64 root-graf-gpad-6.22.06-1.el7.x86_64 root-graf-postscript-6.22.06-1.el7.x86_64 root-graf-x11-6.22.06-1.el7.x86_64 root-graf3d-6.22.06-1.el7.x86_64 root-gui-6.22.06-1.el7.x86_64 root-gui-ged-6.22.06-1.el7.x86_64 root-hist-6.22.06-1.el7.x86_64 root-hist-painter-6.22.06-1.el7.x86_64 root-icons-6.22.06-1.el7.noarch root-io-6.22.06-1.el7.x86_64 root-mathcore-6.22.06-1.el7.x86_64 root-mathmore-6.22.06-1.el7.x86_64 root-matrix-6.22.06-1.el7.x86_64 root-minuit-6.22.06-1.el7.x86_64 root-multiproc-6.22.06-1.el7.x86_64 root-net-6.22.06-1.el7.x86_64 root-physics-6.22.06-1.el7.x86_64 root-tree-6.22.06-1.el7.x86_64 root-tree-dataframe-6.22.06-1.el7.x86_64 root-tree-player-6.22.06-1.el7.x86_64 root-vecops-6.22.06-1.el7.x86_64 scl-utils-20130529-19.el7.x86_64 setools-libs-3.3.8-4.el7.x86_64 tcsh-6.18.01-17.el7_9.1.x86_64 urw-base35-d050000l-fonts-20170801-10.el7.noarch urw-base35-fonts-common-20170801-10.el7.noarch urw-base35-standard-symbols-ps-fonts-20170801-10.el7.noarch urw-base35-z003-fonts-20170801-10.el7.noarch xorg-x11-font-utils-1:7.5-21.el7.x86_64 xorg-x11-fonts-ISO8859-1-75dpi-7.5-9.el7.noarch xorg-x11-server-utils-7.7-20.el7.x86_64 xxhash-libs-0.8.0-1.el7.x86_64 Complete! Finish: build setup for TheP8I-2.0.1-1.el7.src.rpm Start: rpmbuild TheP8I-2.0.1-1.el7.src.rpm Building target platforms: x86_64 Building for target x86_64 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.yVn4n6 + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf TheP8I-2.0.0 + /usr/bin/gzip -dc /builddir/build/SOURCES/TheP8I-2.0.0.tar.gz + /usr/bin/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd TheP8I-2.0.0 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.hWGqQ0 + umask 022 + cd /builddir/build/BUILD + cd TheP8I-2.0.0 + cat + scl enable devtoolset-8 -- checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether make supports nested variables... (cached) yes checking for style of include used by make... GNU checking for g++... g++ checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... none checking for ar... ar checking the archiver (ar) interface... ar checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... (cached) yes checking dependency style of g++... (cached) none checking whether g++ supports C++11 features with -std=c++11... yes checking whether make sets $(MAKE)... (cached) yes checking whether ln -s works... yes checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking how to print strings... printf checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... none checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by gcc... /opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld checking if the linker (/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /opt/rh/devtoolset-8/root/usr/bin/nm -B checking the name lister (/opt/rh/devtoolset-8/root/usr/bin/nm -B) interface... BSD nm checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop checking for /opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /opt/rh/devtoolset-8/root/usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for shl_load... no checking for shl_load in -ldld... no checking for dlopen... no checking for dlopen in -ldl... yes checking whether a program can dlopen itself... yes checking whether a statically linked program can dlopen itself... yes checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking how to run the C++ preprocessor... g++ -std=c++11 -E checking for ld used by g++ -std=c++11... /opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld -m elf_x86_64 checking if the linker (/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ -std=c++11 linker (/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld -m elf_x86_64) supports shared libraries... yes checking for g++ -std=c++11 option to produce PIC... -fPIC -DPIC checking if g++ -std=c++11 PIC flag -fPIC -DPIC works... yes checking if g++ -std=c++11 static flag -static works... no checking if g++ -std=c++11 supports -c -o file.o... yes checking if g++ -std=c++11 supports -c -o file.o... (cached) yes checking whether the g++ -std=c++11 linker (/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking if THEPEGPATH is set... no (found /usr) checking if the installed ThePEG works... yes checking for gsl location... in system libraries checking for sqrt in -lm... yes checking for cblas_srot in -lgslcblas... yes checking for gsl_ran_poisson in -lgsl... yes checking for /usr/share/Pythia8/xmldoc/Index.xml... yes checking if Pythia8 library and headers are present and working... /usr checking for perl... /usr/bin/perl checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating test/Makefile config.status: creating doc/Makefile config.status: creating doc/refman.conf config.status: creating Makefile config.status: creating bin/fixinterfaces.pl config.status: creating bin/P8Particles.pl config.status: creating bin/interfaces.pl config.status: executing depfiles commands config.status: executing libtool commands bin/interfaces.pl --var include/TheP8I/Hadronization/StringFragmentation StringFragmentation StringZ StringPT StringFlav FragmentationSystems MiniStringFragmentation HadronLevel bin/interfaces.pl --init include/TheP8I/Hadronization/StringFragmentation StringFragmentation StringZ StringPT StringFlav FragmentationSystems MiniStringFragmentation HadronLevel bin/interfaces.pl --input include/TheP8I/Hadronization/StringFragmentation StringFragmentation StringZ StringPT StringFlav FragmentationSystems MiniStringFragmentation HadronLevel bin/interfaces.pl --output include/TheP8I/Hadronization/StringFragmentation StringFragmentation StringZ StringPT StringFlav FragmentationSystems MiniStringFragmentation HadronLevel bin/interfaces.pl --interfaces include/TheP8I/Hadronization/StringFragmentation StringFragmentation StringZ StringPT StringFlav FragmentationSystems MiniStringFragmentation HadronLevel bin/interfaces.pl --var include/TheP8I/BE/BoseEinsteinHandler BoseEinstein bin/interfaces.pl --init include/TheP8I/BE/BoseEinsteinHandler BoseEinstein bin/interfaces.pl --input include/TheP8I/BE/BoseEinsteinHandler BoseEinstein bin/interfaces.pl --output include/TheP8I/BE/BoseEinsteinHandler BoseEinstein bin/interfaces.pl --interfaces include/TheP8I/BE/BoseEinsteinHandler BoseEinstein make all-recursive make[1]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0' Making all in . make[2]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0' CXX libTheP8IBE_la-BoseEinsteinHandler.lo CXXLD libTheP8IBE.la CXX libTheP8IConfig_la-RndmEngine.lo CXX libTheP8IConfig_la-Pythia8Interface.lo CXXLD libTheP8IConfig.la CXX libTheP8IString_la-StringFragmentation.lo CXX libTheP8IString_la-StringPipe.lo CXX libTheP8IString_la-OverlapPythiaHandler.lo CXX libTheP8IString_la-ParameterHandler.lo CXX libTheP8IString_la-RandomAverageHandler.lo CXX libTheP8IString_la-RandomHandler.lo CXX libTheP8IString_la-Ropewalk.lo CXXLD libTheP8IString.la CXX libTheP8IStrategy_la-TheP8IStrategy.lo CXXLD libTheP8IStrategy.la CCLD libTheP8I.la bin/P8Particles.pl /usr/share/Pythia8/xmldoc/ParticleData.xml > share/TheP8IParticles.in mkdir -p lib; cd lib;\ for sofile in ../.libs/*.so* ../.libs/*.dylib* ../.libs/*.la; \ do if test -f $sofile; then ln -s -f $sofile .; fi; done; cd lib;\ for sofile in .libs/*.so* .libs/*.dylib*; \ do if test -f $sofile; then ln -s -f $sofile .; fi; done echo "stamp" > done-all-links /usr/bin/setupThePEG -Llib -L/usr/lib64/ThePEG --exitonerror --init -r /usr/lib64/ThePEG/ThePEGDefaults.rpo -o lib/TheP8IDefaults.rpo share/TheP8IDefaults.in Using duplicate PDGName d for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName s for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName s for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_e for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_e for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_ebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_ebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName gamma for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName gamma for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z'0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z'0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName A0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName A0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Rbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Rbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_ue for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_ue for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_uebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_uebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_L0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_L0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName f_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName f_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_S0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_S0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Kbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Kbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Dbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Dbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Upsilon for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Upsilon for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambdabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambdabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omegabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omegabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_30 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_30 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_40 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_40 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~Gravitino for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~Gravitino for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi'_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi'_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName V8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName V8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_1_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_1_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_11_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_11_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_12_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_12_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_21_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_21_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_22_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_22_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_e0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_e0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_ebar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_ebar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Re for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Re for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rmu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rmu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rtau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rtau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z_R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z_R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_diff0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_diff0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi_diff for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi_diff for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffr0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffr0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffrbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffrbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffrbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffrbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. make[2]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0' Making all in test make[2]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0/test' CXX TestJunctions_la-TestJunctions.lo CXXLD TestJunctions.la libtool: link: warning: `-version-info/-version-number' is ignored for convenience libraries make[2]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0/test' Making all in doc make[2]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0/doc' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0/doc' make[1]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0' + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.rcFyJQ + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 ++ dirname /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 + cd TheP8I-2.0.0 + /usr/bin/make install DESTDIR=/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 /usr/bin/make install-recursive make[1]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0' Making install in . make[2]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0' /usr/bin/setupThePEG -Llib -L/usr/lib64/ThePEG --exitonerror --init -r /usr/lib64/ThePEG/ThePEGDefaults.rpo -o lib/TheP8IDefaults.rpo share/TheP8IDefaults.in Using duplicate PDGName d for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName s for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName s for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_e for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_e for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_ebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_ebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName gamma for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName gamma for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z'0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z'0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName A0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName A0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Rbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Rbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_ue for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_ue for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_uebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_uebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_L0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_L0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName f_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName f_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_S0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_S0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Kbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Kbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Dbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Dbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Upsilon for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Upsilon for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambdabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambdabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omegabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omegabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_30 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_30 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_40 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_40 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~Gravitino for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~Gravitino for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi'_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi'_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName V8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName V8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_1_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_1_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_11_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_11_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_12_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_12_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_21_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_21_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_22_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_22_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_e0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_e0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_ebar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_ebar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Re for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Re for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rmu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rmu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rtau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rtau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z_R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z_R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_diff0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_diff0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi_diff for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi_diff for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffr0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffr0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffrbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffrbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffrbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffrbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. make[3]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0' /usr/bin/mkdir -p '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG' /bin/sh ./libtool --mode=install /usr/bin/install -c libTheP8I.la '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG' libtool: install: /usr/bin/install -c .libs/libTheP8I.so.0.0.0 /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG/libTheP8I.so.0.0.0 libtool: install: (cd /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG && { ln -s -f libTheP8I.so.0.0.0 libTheP8I.so.0 || { rm -f libTheP8I.so.0 && ln -s libTheP8I.so.0.0.0 libTheP8I.so.0; }; }) libtool: install: (cd /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG && { ln -s -f libTheP8I.so.0.0.0 libTheP8I.so || { rm -f libTheP8I.so && ln -s libTheP8I.so.0.0.0 libTheP8I.so; }; }) libtool: install: /usr/bin/install -c .libs/libTheP8I.lai /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG/libTheP8I.la libtool: install: warning: remember to run `libtool --finish /usr/lib64/ThePEG' /usr/bin/mkdir -p '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I' /usr/bin/install -c -m 644 share/TheP8IDefaults.in share/TheP8IRemove.in share/OverlapStringFragmenter.in '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I' /usr/bin/mkdir -p '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I' /usr/bin/install -c -m 644 share/TheP8IParticles.in '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I' make[3]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0' make[2]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0' Making install in test make[2]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0/test' make[3]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0/test' make[3]: Nothing to be done for `install-exec-am'. /usr/bin/mkdir -p '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I' /usr/bin/install -c -m 644 SimpleLEP.in SimpleLHC.in HerwigLEP.in HerwigLEPTheP8I.in HerwigDIS.in HerwigDISTheP8I.in HerwigLHC.in HerwigLHCTheP8I.in TestJunctions.in '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I' make[3]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0/test' make[2]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0/test' Making install in doc make[2]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0/doc' make[3]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0/doc' make[3]: Nothing to be done for `install-exec-am'. if test -d refman-html; then /usr/bin/mkdir -p /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I/doc;\ find refman-html -follow -name '*.*' \ -exec /bin/sh /builddir/build/BUILD/TheP8I-2.0.0/install-sh -c -m 644 \{\} /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I/doc/\{\} \;; \ /bin/sh /builddir/build/BUILD/TheP8I-2.0.0/install-sh -c -m 644 TheP8I-refman.tag /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I/doc/TheP8I-refman.tag; fi if test -d refman-latex -a -f refman-latex/refman.pdf; then \ /bin/sh /builddir/build/BUILD/TheP8I-2.0.0/install-sh -c -m 644 refman-latex/refman.pdf /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I/doc/refman.pdf; fi make[3]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0/doc' make[2]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0/doc' make[1]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0' + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/TheP8I-2.0.0 extracting debug info from /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG/libTheP8I.so.0.0.0 dwz: Too few files for multifile optimization /usr/lib/rpm/sepdebugcrcfix: Updated 1 CRC32s, 0 CRC32s did match. symlinked /usr/lib/debug/usr/lib64/ThePEG/libTheP8I.so.0.0.0.debug to /usr/lib/debug/usr/lib64/ThePEG/libTheP8I.so.debug symlinked /usr/lib/debug/usr/lib64/ThePEG/libTheP8I.so.0.0.0.debug to /usr/lib/debug/usr/lib64/ThePEG/libTheP8I.so.0.debug 502 blocks + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Processing files: TheP8I-2.0.1-1.el7.x86_64 Provides: TheP8I = 2.0.1-1.el7 TheP8I(x86-64) = 2.0.1-1.el7 libTheP8I.so.0()(64bit) libtool(/usr/lib64/ThePEG/libTheP8I.la) Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: libTheP8I.so.0()(64bit) libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libgcc_s.so.1()(64bit) libgcc_s.so.1(GCC_3.0)(64bit) libpythia8-8.2.44.so()(64bit) rtld(GNU_HASH) Processing files: TheP8I-debuginfo-2.0.1-1.el7.x86_64 Provides: TheP8I-debuginfo = 2.0.1-1.el7 TheP8I-debuginfo(x86-64) = 2.0.1-1.el7 Requires(rpmlib): rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 Wrote: /builddir/build/RPMS/TheP8I-2.0.1-1.el7.x86_64.rpm Wrote: /builddir/build/RPMS/TheP8I-debuginfo-2.0.1-1.el7.x86_64.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.R4htYU + umask 022 + cd /builddir/build/BUILD + cd TheP8I-2.0.0 + /usr/bin/rm -rf /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 + exit 0 Finish: rpmbuild TheP8I-2.0.1-1.el7.src.rpm Finish: build phase for TheP8I-2.0.1-1.el7.src.rpm INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan INFO: /var/lib/mock/epel-7-x86_64-1611775033.207788/root/var/log/dnf.rpm.log /var/lib/mock/epel-7-x86_64-1611775033.207788/root/var/log/dnf.librepo.log /var/lib/mock/epel-7-x86_64-1611775033.207788/root/var/log/dnf.log INFO: Done(/var/lib/copr-rpmbuild/results/TheP8I-2.0.1-1.el7.src.rpm) Config(child) 2 minutes 17 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