Hide Forgot
Fedora Account System Username: stieg Spec URL: http://triplehelix.org/~stieg/specs/scudcloud.spec SRPM URL: http://triplehelix.org/~stieg/srpms/scudcloud-1.0.84-1.fc23.src.rpm Koji Build: https://koji.fedoraproject.org/koji/taskinfo?taskID=11527165 Description: scudcloud uses the QT library with Webkit to render the web version of Slack, and enhances it by integrating the QWebkit-Native bridge to improve desktop integration. This is my first package submission, and according to https://fedoraproject.org/wiki/Join_the_package_collection_maintainers I will need a sponsor. Also I'm not entirely sure about best practices for the icon installation that I did. This spec file was originally adapted from a OpenSuSE repo, and they did that there. I would imagine its not quite correct, but wasn't able to find any literature on the topic. Pointers welcome.
stieg's scratch build of scudcloud-1.0.84-1.fc23.src.rpm for f23 completed http://koji.fedoraproject.org/koji/taskinfo?taskID=11527721
This would be useful for my work so I'm happy to do the review. Note I'm not a sponsor but following FESCO ticket 1499[1] I can carry out the review and once approved you can file a ticket at the sponsorship trac instance[2] indicating you need a sponsor for a package that has completed review. My initial pre-fedora-review comments: * Remove all that commented blurb at the top of the spec * Group is not required and shouldn't be used in current fedora specs * Use %autosetup macro rather than separate %setup then %patch macros * You are referencing %srcname which is not defined I'll add the more complete formal review within the next few days to add to the initial comments. [1] https://fedorahosted.org/fesco/ticket/1499 [2] https://fedorahosted.org/packager-sponsors/
> This would be useful for my work so I'm happy to do the review. Hooray... finally a reviewer! Thanks for the time. > Note I'm not a sponsor but following FESCO ticket 1499[1] I can carry out the review and once approved you can file a ticket at the sponsorship trac instance[2] indicating you need a sponsor for a package that has completed review. Not ideal but its something. I'll take it. > My initial pre-fedora-review comments: > > * Remove all that commented blurb at the top of the spec > * Group is not required and shouldn't be used in current fedora specs > * Use %autosetup macro rather than separate %setup then %patch macros > * You are referencing %srcname which is not defined > > I'll add the more complete formal review within the next few days to add to the initial comments. Got it. I'll apply this feedback as well as upgrade to the latest package and submit another build to koji. I'll post back here when its ready.
I'm unassigning this for now then until you get the latest build ready for review. If there's no sponsor still then I can pick it back up for review. By unassigning this will appear on the "needs tobe sponsored" dashboard again. You may want to post on the fedora-devel mailing list introducing yourself and the package when you're ready so that you are more visible to the various sponsors too.
Good idea James. I have a pull out at https://github.com/raelgc/scudcloud/pull/329. Once that makes it in then I can re-do the rpm spec so it compliant.
Re-opening this ticket as the scudcloud project merged my changes and I have adapted the spec file to work with it as well as applied the feedback from above. Here is the new spec and SRPM. Spec: http://katsu.triplehelix.org/~stieg/specs/python3-scudcloud.spec SRPM: http://katsu.triplehelix.org/~stieg/srpms/python3-scudcloud-1.5.0-1.fc23.src.rpm Koji Build in progress: http://koji.fedoraproject.org/koji/taskinfo?taskID=12733212
*** Bug 1346015 has been marked as a duplicate of this bug. ***
Andrew, don't you mind if I will close this as duplicate of 1346015? It has proper requirements, modernized spec, proper name and some other stuff.
@Igor, Go ahead. I got no traction from the Fedora community on this so perhaps someone who works for RedHat can finally get this into the main repos.
*** This bug has been marked as a duplicate of bug 1346015 ***