The package of jabberd2 is not current in Fedora 13. The available package is jabberd-2.2.8-5.fc12.x86_64, upstream already provides 2.2.10 since the beginning of June, see http://codex.xiaoka.com/wiki/jabberd2:start I can support you as Co-Maintainer if you like.
(In reply to comment #0) > The package of jabberd2 is not current in Fedora 13. The available package is > jabberd-2.2.8-5.fc12.x86_64, upstream already provides 2.2.10 since the > beginning of June, see http://codex.xiaoka.com/wiki/jabberd2:start > > I can support you as Co-Maintainer if you like. I'd be happy to pass maintainership of jabberd to you... what's your FAS name?
You will find me as "dmaphy" in FAS. :)
(In reply to comment #2) > You will find me as "dmaphydmaphy" in FAS. :) I just realized I had already passed maintainership of jabberd to adrian a while ago: https://admin.fedoraproject.org/pkgdb/acls/name/jabberd While we're waiting for Adrian to respond, why don't you go ahead and request ACLs on the package?
(In reply to comment #3) > (In reply to comment #2) > > You will find me as "dmaphydmaphy" in FAS. :) > > I just realized I had already passed maintainership of jabberd to adrian a > while ago: and I thought you took it over from me ;-) > While we're waiting for Adrian to respond, why don't you go ahead and request > ACLs on the package? I approved your requests and I am happy yor are interested in jabberd2. The problem with jabberd2 is that upgrades are not always 100% compatible with the previous version. Until now there were never any real problems... Just wanted to let you know.
Okay, good to know. I'll have a deeper look at the package today. :)
Just for completeness: I already have a new package lying around locally, I'll try to get this online within the coming week. :)
*** Bug 621949 has been marked as a duplicate of this bug. ***
For those interested I already have an update now: http://dmaphy.fedorapeople.org/jabberd2/ Be careful with upgrading and backup your configuration files, even if they're not be overwritten. You most likely will find either *.rpmsave or *.rpmnew files in /etc/jabberd/ and have to have a look at the changes yourself. I'm sorry for the delay in providing this update, just began a new job in July and there is much to do... I guess you know that. ;) I think I will provide this update for Rawhide first and will push it to F14 and F13, if I get positive feedback concerning the update in Rawhide.
jabberd-2.2.11-2.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/jabberd-2.2.11-2.fc13
jabberd-2.2.11-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/jabberd-2.2.11-2.fc14
I'd appreciate any tests and feedback to the update system. :)
I have not tested it yet, but seeing as you seem to have changed the default storage backend from berkley db to sqlite I would expect problems during the upgrade. I would not recommend changing the default backend during a release (in this case Fedora 13, probably also Fedora 14). I would change it in development and with the next new Fedora release I would release a new jabberd version with a new storage backend.
jabberd-2.2.11-2.fc14 has been pushed to the Fedora 14 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 'yum --enablerepo=updates-testing update jabberd'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/jabberd-2.2.11-2.fc14
Well, since configuration files and existing data isn't overridden, I don't see a danger that anything might crash. Do you think it's too confusing for users when they set up a new jabber configuration? Sooner or later they would have to face this change I guess. I must admit, I maybe was a bit too tired last night and forgot to explicitly write a hint about the change to the new default database, even if it was my plan before. :s If you think it is worth to revoke the update request, please let me know.
(In reply to comment #14) > If you think it is worth to revoke the update request, please let me know. I just wanted to mention it to make sure it has not been overlooked. It does not sound like it needs to be revoked.
Just noted bodhi provides possibility to edit updates. Thus I added the following paragraph to the update notes: ----- Note this update changes the default backend from BDB to SQLite. Thus if you're setting up a new Jabber service with this package, have an eye on this. You're also recommended to diff and review your configuration files manually. ----- Hope this prevents unnecessary confusion. :)
jabberd-2.2.11-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
jabberd-2.2.11-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.