https://bugzilla.redhat.com/show_bug.cgi?id=1215762 --- Comment #32 from gil cattaneo <puntogil@xxxxxxxxx> --- (In reply to Raphael Groner from comment #31) > (In reply to gil cattaneo from comment #29) > > ISSUES: > > > > [?]: Package contains no bundled libraries without FPC exception. > > py4j-9a8ab938b4024af8f0455edb54f80fdb5195968b/py4j-java/src/py4j/Base64.java > > This file is obviously taken from MiGBase64 that's licensed with BSD and can > be found as the original project separately at sourceforge, see also inside > the source file header with an included BSD statement. There are some forks > also at GitHub. But I fail to find any Fedora package. Not sure if we have > to care. Maybe use base64coder or java-base64 as a replacement? > http://migbase64.cvs.sourceforge.net/viewvc/migbase64/migbase64/src/util/ > Base64.java?view=markup > http://sourceforge.net/projects/migbase64/ i not sure if py4j work adding migbase64 symlink in %{_datadir}/py4j/ you can try to request an FPC exception for use Base64.java documenting if there were no changes compared to the original file e.g. https://fedorahosted.org/fpc/ticket/516 > > [!]: Uses parallel make %{?_smp_mflags} macro. > > What to do here exactly? Should I patch the setup.py internal logic that > builds the CPython stuff? should be added in the phase of the build of the documentation pushd %{name}-web make %{?_smp_mflags} html ... ... > > Diff spec file in url and in SRPM (see above) > > Not clear to me what that means? please, increase the Release number when make changes in the spec file -- 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