https://bugzilla.redhat.com/show_bug.cgi?id=1215344 Elder Marco <eldermarco@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eldermarco@xxxxxxxxx --- Comment #2 from Elder Marco <eldermarco@xxxxxxxxx> --- Hello Pavel, thank you! [!]: Package must own all directories that it creates. Note: Directories without known owners: /usr/share/plowshare, /usr/share/plowshare/modules Those directories belongs to plowshare package. Maybe, the package (and plowshare) must own the directory /usr/share/plowshare/modules. (?) [!]: Each %files section contains %defattr if rpm < 4.4 Note: %defattr present but not needed I want to submit the package to EPEL. I think the section is needed in this case. [!]: Each %files section contains %defattr if rpm < 4.4 Note: %defattr present but not needed [!]: Package does not run rm -rf %{buildroot} (or $RPM_BUILD_ROOT) at the beginning of %install. Note: rm -rf %{buildroot} present but not required [!]: Buildroot is not present Note: Buildroot: present but not needed [!]: Package has no %clean section with rm -rf %{buildroot} (or $RPM_BUILD_ROOT) Note: %clean present but not required I want to submit the package to EPEL. I think the section is needed in this case. [!]: Latest version is packaged. Latest commit 098d61824beb108d146cfa5b73eb8d9b05400fe3 and I do not see any tags or releases. There are no tags or releases. Main issue: Offsite (https://github.com/mcrapet/plowshare-modules-legacy) said it "Plowshare legacy & unmaintained modules". So, it useless for packaging. Do you plan maintain that repository if author do not willing do that? It is stop issue. As we discuss in mail list apparently you should choose different method of packaging that. No, I don't. The core package depends on the modules, since it will not work without them. Thus, maintaining a base package without modules does not make any sense, in my opinion. This is the repository which users can install locally through plowmod. Thank you! -- 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 _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review