| Summary: | Emesene Package is outdated in the latest fedora | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jeremy Newton <alexjnewt> |
| Component: | emesene | Assignee: | Itamar Reis Peixoto <itamar> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | itamar, metherid, michael.monreal+bugs, rosset.filipe |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | emesene-2.11.11-1.fc16 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-03-15 02:23:56 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 769124 | ||
| Attachments: | |||
|
Description
Jeremy Newton
2011-05-10 16:55:32 UTC
"yes, we know emesene 2.11.4 is a little rough around the edges, but we needed to make a release to reach a wider audience, get more feedback and hopefully more developers (help us!)" That makes it more suitable for Rawhide I think. A binary rpm isn't that useful for review. A spec file patch would be. Can you provide one? Well the advantage of emesene 2 is it fixes a lot of protocol/connection bugs from emesene 1. As well, emesene 1 uses a very outdated msn protocol, thus this version is a much more compatible/better choice. The developers themselves are discouraging the use of the old emesene because of these issues (along with tendency to "breaking accounts"). Most of emesene's glitches spring from papyon. Having a papyon >= 0.5.5, which to my knowledge is provided in Fedora 15, seems to fix much of these issues. Emesene is "rough around the edges" but it is not a beta release; it's stable enough for day to day use. These "rough edges" refer to the lack of polish, similar to the lack of polish on gnome-shell. He wasn't referring to any unstable behaviour. I personally use this on a day to day basis, and I find it is the best implementation for the MSN protocol for linux. Also, unfortunately I seem to have lost the the spec file. I'll have to remake it. I'll attach it when I finish. Created attachment 498190 [details]
the Spec file for the emesene RPM
I had to remake the Spec file because I seemed to have mistakenly deleted it. There may be an error in it but I'm pretty sure it's fine and as close to how I made it originally as I can remember.
Thanks. I had to rewrite the spec to match Fedora guidelines http://fpaste.org/WYjQ/ I still need to fix locale files handling and inform upstream about the license updates required. rpmlint emesene-2.11.4-1.fc15.noarch.rpm emesene.noarch: E: incorrect-fsf-address /usr/lib/python2.7/site-packages/emesene/gui/gtkui/enchant_dicts.py emesene.noarch: E: incorrect-fsf-address /usr/lib/python2.7/site-packages/emesene/e3/papylib/Session.py emesene.noarch: E: incorrect-fsf-address /usr/lib/python2.7/site-packages/emesene/e3/papylib/PapyEvents.py emesene.noarch: E: incorrect-fsf-address /usr/lib/python2.7/site-packages/emesene/e3/papylib/PapyConvert.py emesene.noarch: E: incorrect-fsf-address /usr/lib/python2.7/site-packages/emesene/e3/papylib/Worker.py emesene.noarch: E: incorrect-fsf-address /usr/lib/python2.7/site-packages/emesene/e3/papylib/__init__.py emesene.noarch: E: incorrect-fsf-address /usr/lib/python2.7/site-packages/emesene/e3/papylib/PapyConference.py emesene.noarch: E: incorrect-fsf-address /usr/lib/python2.7/site-packages/emesene/e3/common/NetworkManagerHelper.py emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/ar/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/ast/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/az/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/bg/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/bn/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/bs/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/ca/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/cs/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/da/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/de/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/dv/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/el/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/en_AU/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/en_CA/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/en_GB/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/eo/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/es/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/et/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/eu/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/fi/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/fil/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/fo/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/fr/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/ga/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/gl/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/gv/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/he/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/hr/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/hu/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/id/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/is/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/it/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/ja/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/kab/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/kn/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/ko/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/ku/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/la/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/lv/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/mk/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/ms/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/nan/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/nb/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/nds/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/nl/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/nn/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/oc/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/pl/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/pt/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/pt_BR/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/ro/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/ru/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/sk/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/sl/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/sq/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/sr/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/sv/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/ta/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/th/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/tr/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/uk/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/vec/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/zh_CN/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/zh_HK/LC_MESSAGES/emesene.mo emesene.noarch: W: file-not-in-%lang /usr/lib/python2.7/site-packages/emesene/po/zh_TW/LC_MESSAGES/emesene.mo thanks for your help There's a new bug fix release for emesene (v2.11.5): http://blog.emesene.org/2011/05/emesene-2115.html "we fixed more than 100 user-reported issues" the source can be found at this link: https://github.com/emesene/emesene/tarball/v2.11.5 as well, line 26 on your rewrite would need to be changed to: %setup -q -n emesene-emesene-a724977 I believe emesene is trying for a monthly release, mostly for bug fixing. The version naming strategy is 2.YY.M, where YY is the year and M is the month it's released. Emesene 1 has started showing some error window on every connect and only works very unstable. Maybe version 2.x will help. Emesene 2 has fixed a lot of issues that were in emesene 1, including an issue where logging-in would break the user's account. Emesene 2 is a complete rewrite, along with the use of papyon rather than the depreciated libraries emesene 1 used. The emesene dev's have really been busy and 2.11.7 was released not too long ago, and looks like 2.11.8 maybe coming out within a few weeks (they typically do end of month cycles). Most of the bugs have been fixed it seems (in the hundreds) with only a hand full left. You can read the release info here: http://blog.emesene.org/2011/07/emesene-2117.html And grab the source here: https://github.com/emesene/emesene/tarball/v2.11.7 Also, the plugins are now separate from the core packages, and can be found here: https://github.com/emesene/emesene-supported-plugins If someone wants to package these plugins, there's already a package made in the AUR for arch linux; the PKGBUILD could be converted or used as a model to make a spec: http://aur.archlinux.org/packages.php?ID=51363 please post a diff against current spec file and I will commit. Created attachment 519396 [details]
Proposed SPEC file for emesene 2.11.7
I decided to just re-uploaded a new spec, based off Rahul's modified one.
Haven't tested it, but should be good; I only left out a name in the latest change log. I'm not sure if my name should be there or the uploader; furthermore, it may need tweaking, but I don't have an opportunity to test and fiddle with it.
How about pushing emesene2 to the fc16 testing repo? I recently upgraded all my systems to fc16 branch and emesene1 is nearly unusable... Emesene 2.11.9 came out a month ago: http://blog.emesene.org/2011/09/emesene-2119-is-out.html Source (redirect): https://github.com/emesene/emesene/tarball/v2.11.9 All the recessions and bugs caused by the moves from version 1 to 2 have been fixed, it's far more stable and much more up to date with the protocol than emesene 1.6.3, unfortunately this still hasn't been adopted into the fedora Repos :( Emesene 1 is now obsolete and very unusable due to a change in the MSN protocol, this was fixed in 2.11.11. Release notes and source download here: http://blog.emesene.org/2011/11/emesene-21111.html Emesene 1 is now pretty much useless and Emesene 2 is very stable these days. I realize there must be some issue(s) with updating emesene to the latest, is there anything I can do personally to help? Created attachment 548432 [details]
SPEC for emesene version 2.11.11
I uploaded the SPEC for the latest version (2.11.11). Is this being ignored? I realize this has still locale issues, but I'm fully willing to help. Just I'm unfamiliar with the file-not-in-%lang warning and RPM -I file-not-in-%lang doesn't show anything. Searching for the answer seems to give me nothing as well. %find_lang foo %files -f foo.lang please update spec file and I will commit it today. The issue is that the locale is located under /usr/lib/python2.7/site-packages/emesene/po/ not /usr/share/locale, which is where find_lang looks if I'm not mistaken. How should I handle this? emesene-2.11.11-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/emesene-2.11.11-1.fc15 emesene-2.11.11-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/emesene-2.11.11-1.fc16 I'll assume it's alright then we still need to fix the lang issue and remove papyon blunded with emesene. I will remove the papyon now. FWIW I think emesene ships a modified copy of papyon (In reply to comment #5) I need something like used in the old version of emesene to fix the lang issue with rpmlint. cd po for dir in *;do echo "%lang($dir) %{_datadir}/%{name}/po/$dir" >> $RPM_BUILD_DIR/%{name}-%{version}/%{name}.lang done (In reply to comment #22) > FWIW I think emesene ships a modified copy of papyon fedora rules forbidden the shipping blunded libs why emesene doesnt have sent the changes to upstream ? If I understand it correctly they say the papyon is too in development or far too conservative. As well their version of papyon is optimized or patched to work better with emesene or something like that. Unfortunately an exception for this package will have to be made or I can ask a emesene dev for a patch to truncate/remove it. Package emesene-2.11.11-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing emesene-2.11.11-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-17297/emesene-2.11.11-1.fc15 then log in and leave karma (feedback). emesene-2.11.11-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. emesene-2.11.11-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |