https://bugzilla.redhat.com/show_bug.cgi?id=1826439 Alaa Hleihel (Mellanox) <ahleihel(a)redhat.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ahleihel(a)redhat.com, | |honli(a)redhat.com, | |mschmidt(a)redhat.com Doc Type|--- |If docs needed, set a value -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #2 from igor.ivanov.va(a)gmail.com --- Thank you for review. Spec is updated. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 Petr Pisar <ppisar(a)redhat.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ppisar(a)redhat.com Flags| |fedora-review? -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #5 from igor.ivanov.va(a)gmail.com --- Thank you for review libvma.spec has been updated accordingly. There are a couple of notes: 1. After applying changes to meet https://fedoraproject.org/wiki/Changes/Removing_ldconfig_scriptlets requirements rpmlint reports error: libvma.x86_64: E: postin-without-ldconfig /usr/lib64/libvma.so.9.0.2 This package contains a library and its %post scriptlet doesn't call ldconfig. libvma.x86_64: E: postun-without-ldconfig /usr/lib64/libvma.so.9.0.2 This package contains a library and its %postun doesn't call ldconfig. I am using rpmlint version 1.10 on fc30 2. I would like to avoid putting man page for executable 'vma_stats' at the moment unless it must be done. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #7 from Honggang LI <honli(a)redhat.com&gt; --- $ cat -n libvma.spec ..... 4 %{!?make_build: %global make_build %{__make} %{?_smp_mflags} %{?mflags} V=1} It was my bad. I should told you to delete line 4. 5 %{!?_pkgdocdir: %global _pkgdocdir %{_docdir}/%{name}-%{version}} Why you think line 5 is necessary? Can we just delete it too? 40 This package includes headers for building programs with libvma's interface 41 directly, as opposed to loading it dynamically with LD_PRELOAD. Line 40 and 41 are in the base sub-package libvma's %description section. The base sub-package dose not include any header. It seems line 40 and 41 belongs to sub-package libvma-devel's %description section. Is it right? 52 Summary: Libvma utilities 57 analyzing Libvma statistic. Please replace "Libvma" with "libvma" for line 52 and 57. 68 %configure --docdir=%{_pkgdocdir} \ ^^^^^^^^^^^^^^^^^^^^^^ "--docdir=%{_pkgdocdir}" is unnecessary. Should be removed? 85 %{?ldconfig} 92 %{?ldconfig} Why you need line 85 and 92? 105 %license COPYING Should append "LICENSE" in line 105. $ tar -tf libvma-9.0.2.tar.gz | grep -i license libvma-9.0.2/LICENSE Thanks -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #9 from Honggang LI <honli(a)redhat.com&gt; --- 1 Package Review 2 ============== 3 4 Legend: 5 [x] = Pass, [!] = Fail, [-] = Not applicable, [?] = Not evaluated 6 [ ] = Manual review needed 7 8 9 Issues: 10 ======= 11 - Development (unversioned) .so files in -devel subpackage, if present. 12 Note: Unversioned so-files directly in %_libdir. 13 See: https://docs.fedoraproject.org/en-US/packaging- 14 guidelines/#_devel_packages That's OK, as the libvma-9.0.2-1.fc33.x86_64.rpm/usr/lib64/libvma.so file is used as PRE_LOAD. So, it should be included in the main sub-package. 15 - Package does not use a name that already exists. 16 Note: A package with this name already exists. Please check 17 https://src.fedoraproject.org/rpms/libvma 18 See: https://docs.fedoraproject.org/en-US/packaging- 19 guidelines/Naming/#_conflicting_package_names It's OK, as we are import libvma again for fedora. See https://bugzilla.redhat.com/show_bug.cgi?id=1826439#c3 . 20 21 22 ===== MUST items ===== 23 24 C/C++: 25 [ ]: Package does not contain kernel modules. PASS 26 [ ]: Package contains no static executables. PASS 27 [x]: If your application is a C or C++ application you must list a 28 BuildRequires against gcc, gcc-c++ or clang. 29 [x]: Header files in -devel subpackage, if present. 30 [x]: ldconfig not called in %post and %postun for Fedora 28 and later. 31 [x]: Package does not contain any libtool archives (.la) 32 [x]: Rpath absent or only used for internal libs. 33 34 Generic: 35 [ ]: Package is licensed with an open-source compatible license and meets 36 other legal requirements as defined in the legal section of Packaging 37 Guidelines. PASS 38 [ ]: License field in the package spec file matches the actual license. 39 Note: Checking patched sources after %prep for licenses. Licenses 40 found: "Unknown or generated", "BSD (unspecified) GPL (v2)", "BSD 41 3-clause "New" or "Revised" License", "GPL (v3 or later)", "BSD 42 2-clause "Simplified" License GPL (v2)", "Expat License". 113 files 43 have unknown license. Detailed output of licensecheck in 44 /home/honli/fedora/libvma/1826439-libvma/licensecheck.txt PASS 45 [ ]: License file installed when any subpackage combination is installed. PASS. 46 [ ]: If the package is under multiple licenses, the licensing breakdown 47 must be documented in the spec. PASS 48 [ ]: Package requires other packages for directories it uses. PASS 49 Note: No known owner of /usr/share/doc/libvma, /usr/include/mellanox Please fix this. /usr/share/doc/libvma should be owned by sub-package "libvma". /usr/include/mellanox should be owned by sub-package "libvma-devel". 50 [ ]: Package must own all directories that it creates. 51 Note: Directories without known owners: /etc/security/limits.d, 52 /etc/security, /usr/include/mellanox, /usr/share/doc/libvma PASS. The first two directories are co-owned. The last two are duplicated of line 49. 53 [ ]: %build honors applicable compiler flags or justifies otherwise. PASS 54 [ ]: Package contains no bundled libraries without FPC exception. PASS 55 [ ]: Changelog in prescribed format. PASS 56 [ ]: Sources contain only permissible code or content. PASS 57 [ ]: Package contains desktop file if it is a GUI application. PASS. Not GUI application. 58 [ ]: Development files must be in a -devel package PASS 59 [ ]: Package uses nothing in %doc for runtime. PASS 60 [ ]: Package consistently uses macros (instead of hard-coded directory 61 names). Except the doc dir. Others looks good. 62 [ ]: Package is named according to the Package Naming Guidelines. PASS 63 [ ]: Package does not generate any conflict. PASS 64 [ ]: Package obeys FHS, except libexecdir and /usr/target. PASS 65 [ ]: If the package is a rename of another package, proper Obsoletes and 66 Provides are present. PASS 67 [ ]: Requires correct, justified where necessary. PASS 68 [ ]: Spec file is legible and written in American English. PASS 69 [ ]: Package contains systemd file(s) if in need. PASS. Yes, it does. 70 [ ]: Useful -debuginfo package or justification otherwise. PASS 71 [ ]: Package is not known to require an ExcludeArch tag. PASS, see inline comments in spec file. 72 [ ]: Large documentation must go in a -doc subpackage. Large could be size 73 (~1MB) or number of files. 74 Note: Documentation size is 184320 bytes in 3 files. PASS 75 [ ]: Package complies to the Packaging Guidelines PASS 76 [x]: Package successfully compiles and builds into binary rpms on at least 77 one supported primary architecture. 78 [x]: Package installs properly. 79 [x]: Rpmlint is run on all rpms the build produces. 80 Note: There are rpmlint messages (see attachment). 81 [x]: If (and only if) the source package includes the text of the 82 license(s) in its own file, then that file, containing the text of the 83 license(s) for the package is included in %license. 84 [x]: Package does not own files or directories owned by other packages. 85 [x]: Package uses either %{buildroot} or $RPM_BUILD_ROOT 86 [x]: Package does not run rm -rf %{buildroot} (or $RPM_BUILD_ROOT) at the 87 beginning of %install. 88 [x]: %config files are marked noreplace or the reason is justified. 89 [x]: Macros in Summary, %description expandable at SRPM build time. 90 [x]: Dist tag is present. 91 [x]: Package does not contain duplicates in %files. 92 [x]: Permissions on files are set properly. 93 [x]: Package must not depend on deprecated() packages. 94 [x]: Package use %makeinstall only when make install DESTDIR=... doesn't 95 work. 96 [x]: Package is named using only allowed ASCII characters. 97 [x]: No %config files under /usr. 98 [x]: Package is not relocatable. 99 [x]: Sources used to build the package match the upstream source, as 100 provided in the spec URL. 101 [x]: Spec file name must match the spec package %{name}, in the format 102 %{name}.spec. 103 [x]: systemd_post is invoked in %post, systemd_preun in %preun, and 104 systemd_postun in %postun for Systemd service files. 105 Note: Systemd service file(s) in libvma 106 [x]: File names are valid UTF-8. 107 [x]: Packages must not store files under /srv, /opt or /usr/local 108 109 ===== SHOULD items ===== 110 111 Generic: 112 [ ]: If the source package does not include license text(s) as a separate 113 file from upstream, the packager SHOULD query upstream to include it. PASS 114 [ ]: Final provides and requires are sane (see attachments). PASS 115 [ ]: Package functions as described. PASS. See https://bugzilla.redhat.com/show_bug.cgi?id=1826439#c8 116 [ ]: Latest version is packaged. PASS 117 [ ]: Package does not include license text files separate from upstream. PASS 118 [ ]: Sources are verified with gpgverify first in %prep if upstream 119 publishes signatures. 120 Note: gpgverify is not used. PASS. NO GPG. 121 [ ]: Description and summary sections in the package spec file contains 122 translations for supported Non-English languages, if available. PASS 123 [ ]: %check is present and all tests pass. PASS 124 [ ]: Packages should try to preserve timestamps of original installed 125 files. PASS 126 [x]: Reviewer should test that the package builds in mock. 127 [x]: Buildroot is not present 128 [x]: Package has no %clean section with rm -rf %{buildroot} (or 129 $RPM_BUILD_ROOT) 130 [x]: No file requires outside of /etc, /bin, /sbin, /usr/bin, /usr/sbin. 131 [x]: Fully versioned dependency in subpackages if applicable. 132 [x]: Packager, Vendor, PreReq, Copyright tags should not be in spec file 133 [x]: Sources can be downloaded from URI in Source: tag 134 [x]: SourceX is a working URL. 135 [x]: Package should compile and build into binary rpms on all supported 136 architectures. 137 [x]: Spec use %global instead of %define unless justified. 138 139 ===== EXTRA items ===== 140 141 Generic: 142 [!]: Package should not use obsolete m4 macros 143 Note: Some obsoleted macros found, see the attachment. 144 See: https://fedorahosted.org/FedoraReview/wiki/AutoTools Please fix this. 145 [x]: Rpmlint is run on debuginfo package(s). 146 Note: No rpmlint messages. 147 [x]: Rpmlint is run on all installed packages. 148 Note: There are rpmlint messages (see attachment). 149 [x]: Large data in /usr/share should live in a noarch subpackage if package 150 is arched. 151 [x]: Spec file according to URL is the same as in SRPM. 152 153 154 Rpmlint 155 ------- 156 Checking: libvma-9.0.2-1.fc33.x86_64.rpm 157 libvma-devel-9.0.2-1.fc33.x86_64.rpm 158 libvma-utils-9.0.2-1.fc33.x86_64.rpm 159 libvma-debuginfo-9.0.2-1.fc33.x86_64.rpm 160 libvma-debugsource-9.0.2-1.fc33.x86_64.rpm 161 libvma-9.0.2-1.fc33.src.rpm 162 libvma.x86_64: W: shared-lib-calls-exit /usr/lib64/libvma.so.9.0.2 exit(a)GLIBC_2.2.5 163 libvma.x86_64: W: devel-file-in-non-devel-package /usr/lib64/libvma.so 164 libvma.x86_64: E: postin-without-ldconfig /usr/lib64/libvma.so.9.0.2 165 libvma.x86_64: E: postun-without-ldconfig /usr/lib64/libvma.so.9.0.2 line 164 and 165 are false positive. 166 libvma.x86_64: W: no-manual-page-for-binary vma 167 libvma.x86_64: W: no-manual-page-for-binary vmad should be fixed. 168 libvma-devel.x86_64: W: no-documentation 169 libvma-utils.x86_64: W: spelling-error %description -l en_US vma -> ma, via, v ma 170 libvma-utils.x86_64: W: no-documentation 171 libvma-utils.x86_64: W: no-manual-page-for-binary vma_stats should be fixed. 172 6 packages and 0 specfiles checked; 2 errors, 8 warnings. 173 174 175 176 177 Rpmlint (debuginfo) 178 ------------------- 179 Checking: libvma-debuginfo-9.0.2-1.fc33.x86_64.rpm 180 1 packages and 0 specfiles checked; 0 errors, 0 warnings. 181 182 183 184 185 186 Rpmlint (installed packages) 187 ---------------------------- 188 libvma-debugsource.x86_64: W: invalid-url URL: https://github.com/Mellanox/libvma <urlopen error [Errno -2] Name or service not known> 189 libvma.x86_64: W: invalid-url URL: https://github.com/Mellanox/libvma <urlopen error [Errno -2] Name or service not known> 190 libvma.x86_64: W: unused-direct-shlib-dependency /usr/lib64/libvma.so.9.0.2 /lib64/librt.so.1 191 libvma.x86_64: W: unused-direct-shlib-dependency /usr/lib64/libvma.so.9.0.2 /lib64/libm.so.6 192 libvma.x86_64: W: shared-lib-calls-exit /usr/lib64/libvma.so.9.0.2 exit(a)GLIBC_2.2.5 193 libvma.x86_64: W: devel-file-in-non-devel-package /usr/lib64/libvma.so 194 libvma.x86_64: E: postin-without-ldconfig /usr/lib64/libvma.so.9.0.2 195 libvma.x86_64: E: postun-without-ldconfig /usr/lib64/libvma.so.9.0.2 196 libvma.x86_64: W: no-manual-page-for-binary vma 197 libvma.x86_64: W: no-manual-page-for-binary vmad 198 libvma-debuginfo.x86_64: W: invalid-url URL: https://github.com/Mellanox/libvma <urlopen error [Errno -2] Name or service not known> 199 libvma-utils.x86_64: W: spelling-error %description -l en_US vma -> ma, via, v ma 200 libvma-utils.x86_64: W: invalid-url URL: https://github.com/Mellanox/libvma <urlopen error [Errno -2] Name or service not known> 201 libvma-utils.x86_64: W: no-documentation 202 libvma-utils.x86_64: W: no-manual-page-for-binary vma_stats 203 libvma-devel.x86_64: W: invalid-url URL: https://github.com/Mellanox/libvma <urlopen error [Errno -2] Name or service not known> 204 libvma-devel.x86_64: W: no-documentation 205 5 packages and 0 specfiles checked; 2 errors, 15 warnings. duplicated error report. 206 207 208 209 Unversioned so-files 210 -------------------- 211 libvma: /usr/lib64/libvma.so 212 213 Source checksums 214 ---------------- 215 https://github.com/Mellanox/libvma/archive/9.0.2/libvma-9.0.2.tar.gz : 216 CHECKSUM(SHA256) this package : 1f273c309f553bd479da229a39b93d53fcf3fdda9b8eae2df973f6b8d02aa164 217 CHECKSUM(SHA256) upstream package : 1f273c309f553bd479da229a39b93d53fcf3fdda9b8eae2df973f6b8d02aa164 218 219 220 Requires 221 -------- 222 libvma (rpmlib, GLIBC filtered): 223 /bin/sh 224 /usr/bin/bash 225 config(libvma) 226 ld-linux-x86-64.so.2()(64bit) 227 libc.so.6()(64bit) 228 libdl.so.2()(64bit) 229 libgcc_s.so.1()(64bit) 230 libgcc_s.so.1(GCC_3.0)(64bit) 231 libibverbs.so.1()(64bit) 232 libibverbs.so.1(IBVERBS_1.0)(64bit) 233 libibverbs.so.1(IBVERBS_1.1)(64bit) 234 libibverbs.so.1(IBVERBS_1.8)(64bit) 235 libm.so.6()(64bit) 236 libmlx5.so.1()(64bit) 237 libmlx5.so.1(MLX5_1.2)(64bit) 238 libmlx5.so.1(MLX5_1.4)(64bit) 239 libnl-3.so.200()(64bit) 240 libnl-3.so.200(libnl_3)(64bit) 241 libnl-route-3.so.200()(64bit) 242 libnl-route-3.so.200(libnl_3)(64bit) 243 libpthread.so.0()(64bit) 244 librdmacm.so.1()(64bit) 245 librdmacm.so.1(RDMACM_1.0)(64bit) 246 librt.so.1()(64bit) 247 libstdc++.so.6()(64bit) 248 libstdc++.so.6(CXXABI_1.3)(64bit) 249 libstdc++.so.6(CXXABI_1.3.8)(64bit) 250 libstdc++.so.6(CXXABI_1.3.9)(64bit) 251 libvma.so.9()(64bit) 252 rtld(GNU_HASH) 253 254 libvma-devel (rpmlib, GLIBC filtered): 255 libvma(x86-64) 256 257 libvma-utils (rpmlib, GLIBC filtered): 258 libc.so.6()(64bit) 259 libgcc_s.so.1()(64bit) 260 libgcc_s.so.1(GCC_3.0)(64bit) 261 libpthread.so.0()(64bit) 262 libstdc++.so.6()(64bit) 263 libstdc++.so.6(CXXABI_1.3)(64bit) 264 libstdc++.so.6(CXXABI_1.3.9)(64bit) 265 libvma(x86-64) 266 rtld(GNU_HASH) 267 268 libvma-debuginfo (rpmlib, GLIBC filtered): 269 270 libvma-debugsource (rpmlib, GLIBC filtered): 271 272 273 274 Provides 275 -------- 276 libvma: 277 config(libvma) 278 libvma 279 libvma(x86-64) 280 libvma.so.9()(64bit) 281 282 libvma-devel: 283 libvma-devel 284 libvma-devel(x86-64) 285 286 libvma-utils: 287 libvma-utils 288 libvma-utils(x86-64) 289 290 libvma-debuginfo: 291 debuginfo(build-id) 292 libvma-debuginfo 293 libvma-debuginfo(x86-64) 294 295 libvma-debugsource: 296 libvma-debugsource 297 libvma-debugsource(x86-64) 298 299 300 301 AutoTools: Obsoleted m4s found 302 ------------------------------ 303 AC_PROG_LIBTOOL found in: libvma-9.0.2/configure.ac:107 Please fix this. 304 305 306 Generated by fedora-review 0.7.5 (5fa5b7e) last change: 2020-02-16 307 Command line :/usr/bin/fedora-review -b 1826439 308 Buildroot used: fedora-rawhide-x86_64 309 Active plugins: Generic, C/C++, Shell-api 310 Disabled plugins: fonts, SugarActivity, Haskell, Ocaml, PHP, Perl, Java, R, Python, Ruby 311 Disabled flags: EPEL6, EPEL7, DISTTAG, BATCH, EXARCH Thanks -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #11 from Honggang LI <honli(a)redhat.com&gt; --- (In reply to igor.ivanov.va from comment #10) I checked libvma git repo. I did not found this patch. The patch should be applied in upstream before apply it for fedora. Please see https://docs.fedoraproject.org/en-US/packaging-guidelines/#_patch_guidelines . -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #13 from Honggang LI <honli(a)redhat.com&gt; --- (In reply to igor.ivanov.va from comment #10) The updated spec file looks good to me. I will set the fedora-review+ flag, after the patch get into upstream. Thanks -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 Honggang LI <honli(a)redhat.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(igor.ivanov.va@gm | |ail.com) --- Comment #15 from Honggang LI <honli(a)redhat.com&gt; --- Please tell me your FSA account. I searched 'igor.ivanov.va' in https://src.fedoraproject.org/users , but did not get a match. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 igor.ivanov.va(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(igor.ivanov.va@gm | |ail.com) | --- Comment #16 from igor.ivanov.va(a)gmail.com --- May FCA : iivanov -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #18 from igor.ivanov.va(a)gmail.com --- Michal, Honggang what is next step for getting one into fc33? Thanks, Igor -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #20 from igor.ivanov.va(a)gmail.com --- Added https://pagure.io/releng/issue/9509 Thanks, Igor -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #22 from igor.ivanov.va(a)gmail.com --- Hi Michal, I have updated libvma.spec to meet most of your requirements and added additional patch as https://raw.githubusercontent.com/igor-ivanov/libvma/pr/fedora-package/fe... For others please look at my comments inline. Thanks, Igor (In reply to Michal Schmidt from comment #21) Done Done It is used during configure to set VMA_SVN_REVISION. Corrected but following rules as https://docs.fedoraproject.org/en-US/packaging-guidelines/#_why_the_makei... permit original usage. livma has own extra api with vma_extra.h header file and admits direct linkage. This option is used to provide flexibility in final binary libvma version. For example: this option can be used to enable tso support (--enable-tso) that increases throughput but not ready to be included by default. I removed it but it is used in pair with configure_options to differentiate packages for the customers on our side. There is such recommendation at https://docs.mellanox.com/display/VMAv902/VMA+Installation+Options that forces to https://github.com/Mellanox/libvma/wiki/VMA-over-RHEL-7.x-with-inbox-driv... Done Done It does support of some systems easier for us. SIGTERM is generated by kill utility by default. So it is used to restart vmad in this case too. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #24 from Honggang LI <honli(a)redhat.com&gt; --- (In reply to Michal Schmidt from comment #23) In real HPC production environment, we are always to lifted the resource for all users. For example, see "13.5.3. Relaxing memlock restrictions for users" https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/... -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #26 from Honggang LI <honli(a)redhat.com&gt; --- (In reply to Michal Schmidt from comment #25) No, but we setup it with kickstart scripts for our internal cluster. [root@rdma-dev-01 ~]$ cat /etc/security/limits.d/rdma.conf # configuration for rdma performance tuning * soft memlock unlimited * hard memlock unlimited * soft stack unlimited * hard stack unlimited * soft core unlimited * hard core unlimited # rdma tuning end -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #28 from igor.ivanov.va(a)gmail.com --- Thank you for review Package was updated. Changes include: 1. 30-libvma-limits.conf was removed (let administrator configure system basing on internal requirements for user, groups etc. libvma has run-time check as https://github.com/igor-ivanov/libvma/blob/master/src/vma/main.cpp#L423) 2. vma.service started using vmad directly. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #30 from Michal Schmidt <mschmidt(a)redhat.com&gt; --- Igor, I can see no more blocking issues. Thanks! I have added you to the "packager" Fedora group. You can reopen https://pagure.io/releng/issue/9509 now. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 alexv(a)mellanox.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexv(a)mellanox.com --- Comment #32 from alexv(a)mellanox.com --- Hi, We've reopened the ticket to Unretire libvma: https://pagure.io/releng/issue/9509. Thanks, Alex -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 igor.ivanov.va(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(igor.ivanov.va@gm | |ail.com) | --- Comment #34 from igor.ivanov.va(a)gmail.com --- Hi Honggang, Could you advise how to create remote f31, f32 branches for libvma. I can not do it useing `git push origin f32` Thanks, Igor -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #36 from igor.ivanov.va(a)gmail.com --- I submitted request to unblock f31 as https://pagure.io/releng/issue/9681 -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 Honggang LI <honli(a)redhat.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Fixed In Version| |libvma-9.0.2-1.fc34,libvma- | |9.0.2-1.fc33 Resolution|--- |RAWHIDE Last Closed| |2020-08-14 03:31:30 --- Comment #38 from Honggang LI <honli(a)redhat.com&gt; --- libvma-9.0.2-1.fc33 and libvma-9.0.2-1.fc34 had been built. Close it. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

https://bugzilla.redhat.com/show_bug.cgi?id=1826439 --- Comment #40 from Honggang LI <honli(a)redhat.com&gt; --- Please use bodhi to create update for libvma. I confirmed it works for me. fabtests (f32)]$ bodhi updates new --type bugfix --notes "Update fabtests to latest upstream release v1.11.0" --user honli fabtests-1.11.0-1.fc32 ================================================================================ fabtests-1.11.0-1.fc32 ================================================================================ Update ID: FEDORA-2020-2b79a2faad Content Type: rpm Release: Fedora 32 Status: pending Type: bugfix Severity: unspecified Karma: 0 Autokarma: False [-3, 3] CI Status: no tests are required Request: testing Notes: Update fabtests to latest upstream release v1.11.0 Submitter: honli Submitted: 2020-08-17 09:15:32 Comments: bodhi - 2020-08-17 09:15:32 (karma 0) This update has been submitted for testing by honli. bodhi - 2020-08-17 09:15:32 (karma 0) This update's test gating status has been changed to 'ignored'. bodhi - 2020-08-17 09:15:32 (karma 0) This update's test gating status has been changed to 'waiting'. https://bodhi.fedoraproject.org/updates/FEDORA-2020-2b79a2faad Caveats: The number of stable days required was set to the mandatory release value of 7 days -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component