Package Details: mozilla-firefox-sync-server-hg 549.ba4bf783018f-1

Git Clone URL: (read-only)
Package Base: mozilla-firefox-sync-server-hg
Description: Mozilla Sync Server for built-in Firefox Sync - 1.1 version for Firefox <29
Upstream URL:
Licenses: GPL
Conflicts: mozilla-firefox-sync-server-git
Submitter: sergej
Maintainer: None
Last Packager: Siosm
Votes: 16
Popularity: 0.000000
First Submitted: 2011-11-28 10:38
Last Updated: 2015-06-09 10:34

Dependencies (2)

Required by (0)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

eigengrau commented on 2013-09-28 17:06

Still getting the deprecation warning, weirdly.. although you obviously added "--paste" to the .service. I also made sure to issue systemctl daemon-reload.

eigengrau commented on 2013-09-28 17:00

Still getting that deprecation warning, weirdly..

Siosm commented on 2013-09-25 22:50

@untitaker: I've fixed the warning brought by the latest gunicorn update. Could you be more specific about the problem regarding file permissions? Thanks

untitaker commented on 2013-09-25 21:19

The server gives me a warning that bin/gunicorn_paster development.ini is deprecated, bin/gunicorn --paste development.ini should be used.

Also, the file permissions don't work out of the box, the ffsync user needs write access for the python egg cache.

Siosm commented on 2013-08-25 20:45

@eigengrau: You're right, I completely forgot to update the default configuration as I had already made such a change in mine and didn't check. Updated with your suggestions. Thanks.

In my case, this log file is completely empty as ffsync logging is done by systemd redirecting stdin/err output to journald. To be thorough we should add a logrotate rule, but it doesn't seem to be a pressing matter here. I'm wondering if the file is even used.

Moreover, I'm using gunicorn and not the default in the systemd service file, which requires the following line in development.ini:
use = egg:gunicorn#main

Maybe I should use the default here too.

eigengrau commented on 2013-08-25 13:30

Just out of curiosity: Did you update the development.ini to use /var/log/ffsync? I had to update mine and was surprised because it didn't give me a .pacnew file. So I presume the /var/log path which you create in post_install isn't really used?

Also, the post_install doesn't seem to be called upon upgrades, i.e. if you really want to use /var/log by adapting the default development.ini, there should be a post_upgrade which makes sure the log path exists, I guess.

Also cheers for maintaining this!

Siosm commented on 2013-08-24 04:17

Updated with waddles' suggestions. Thanks.

Anonymous comment on 2013-08-13 04:55

Needs an install script to add the ffsync user:
# useradd -r -g http -d /opt/mozilla-firefox-sync-server ffsync

Probably should also move the error log to /var/log/ffsync/ and install script should handle creating/chowning that too.

Siosm commented on 2013-08-06 16:09

The latest update introduces an issue that has to be taken care of manually. Due to a potential bug in pacman (reported here:, you will probably get file conflicts when upgrading. I had to remove and reinstall the package to bypass this. Don't forget to backup your config (see backup in PKGBUILD) before doing so, just in case (it destroyed mine, I don't know why).

rumpelsepp commented on 2013-06-18 11:56

@siosm: I think this package is unmaintained. Would you adopt it? :-)