https://bugzilla.redhat.com/show_bug.cgi?id=988667 Gergely Polonkai <gergely@xxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment|0 |1 #1143720 is| | obsolete| | --- Comment #28 from Gergely Polonkai <gergely@xxxxxxxxxxx> --- Created attachment 1146971 --> https://bugzilla.redhat.com/attachment.cgi?id=1146971&action=edit .spec file for valadoc 0.30 I have fixed what you suggested, and also added vala-devel as a build dependency. This is required to generate 0.30.x/libdriver.so This brings up the question in me (again): what to do with this? For every available Vala version (all even numbers from 0.20 to 0.30), if libvala-{version} present, the corresponding libdriver.so will be generated; so if a user has a (maybe manually) installed version of Vala-0.20, then a new file will be created during the build, which won’t be handled anywhere in the .spec, hence, RPM will fail. This, of course, won’t happen in Mock/Koji. I have uploaded the new SPEC and SRPM to the old URLs. -- You are receiving this mail because: You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/package-review@xxxxxxxxxxxxxxxxxxxxxxx