https://bugzilla.redhat.com/show_bug.cgi?id=1264546 --- Comment #43 from Michael Schwendt <bugs.michael@xxxxxxx> --- Hard to tell, as entry->size could be anything and isn't checked within that function. Can you enhance the build, so that the output is more verbose and shows the detailed invocations of gcc and ld? That would be the only way to tell how exactly the files are compiled/linked. Who knows under which circumstances results like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751812 turn up with GCC 5? > Version: %{soletta_major}.%{soletta_minor}.%{soletta_build}.%{soletta_tag} Hard to follow why it's done like that. As it ends up with soletta-0.0.1.beta10-1.fc22.src.rpm that doesn't follow the Package Versioning Guidelines: https://fedoraproject.org/wiki/Packaging:Guidelines#Version_and_Release https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Package_Versioning Those would move the "beta10" out of %version and into a less-significant position in %release. That can be important for all cases where RPM version comparison is not compatible with upstream's release versioning scheme. -- 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