Red Hat Bugzilla – Bug 1266805
Review Request: springframework-social - Connect your applications with SaaS providers such as Facebook and Twitter
Last modified: 2015-11-21 21:24:08 EST
Spec URL: https://gil.fedorapeople.org/springframework-social.spec
SRPM URL: https://gil.fedorapeople.org/springframework-social-1.0.3-1.fc22.src.rpm
The Spring Social project allows you to integrate the
APIs exposed by Software-as-a-Service (SaaS) providers
such as Facebook and Twitter into your applications.
It consists of a service provider 'connect' framework,
sign-in support, and strongly-typed Java API bindings
Fedora Account System Username: gil
- rpmlint checks return nothing.
- package meets naming guidelines
- package meets packaging guidelines
- license (ASL 2.0) OK, text in %license, matches source
- spec file legible, in am. english
- source matches upstream (b219ac0fee6a3c35e8812d8ad5b13f1b700e0cf167414f54cf250fb29dc9d058)
- package compiles on f23 (noarch)
- no missing BR
- no unnecessary BR
- no locales
- not relocatable
- owns all directories that it creates
- no duplicate files
- permissions ok
- macro use consistent
- code, not content
- javadoc ok
- nothing in %doc affects runtime
- no need for .desktop file
As always, a very good package gil. Nice work.
Request for new package:
Package request has been approved: https://admin.fedoraproject.org/pkgdb/package/springframework-social
springframework-social-1.0.3-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-f3f521a103
springframework-social-1.0.3-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update springframework-social'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-f3f521a103
springframework-social-1.0.3-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.