Description
Guillaume Ayoub
2010-06-05 00:52:44 UTC
Created attachment 234161 [details]
radicale-0.2.ebuild
Created attachment 234669 [details]
radicale-0.2-r1 ebuild, fixing the Python version needed for SSL
Created attachment 235513 [details]
radicale-0.3 ebuild
Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Thanks, On behalf of the Gentoo Sunrise Team, Markos. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq Created attachment 237447 [details]
radicale-0.3-r1 ebuild, with reviews from #gentoo-dev-help
Created attachment 237567 [details]
radicale-0.3-r3 ebuild, with reviews from #gentoo-sunrise
The package should provide a default configuration file as mentioned at the homepage and also an init-script :) Created attachment 241337 [details]
radicale-0.3.ebuild
Here is a new radicale ebuild.
Changes:
+ removes the "-r3" part: Not in tree yet ... so no need to care about revs.
+ installs init.d file: now able to start/stop service
+ installs default config: config file now taken care of by portage
Created attachment 241339 [details, diff]
radicale-0.3-foreground.patch
Patch needed by the last ebuild. It adds "--foreground" option needed by the init script.
Created attachment 241341 [details]
init script
Created attachment 241343 [details]
default config file
Radicale 0.4 has been released, with a default config file included in the package and the --foreground option. Created attachment 242277 [details]
radicale-0.4.ebuild
Here is the ebuild for the 0.4 version. :)
Committed to sunrise. After being reviewed by the developers this should be moved into the available overlay. Created attachment 268407 [details]
radicale-0.5.ebuild
Bump to version 0.5
Also added "ssl" as useflag and removed the pkg_postinst message. When the ssl-useflag is set, I also enforce the python-version to be 2.6.6 at least to avoid hitting the SSL-bug in previous python-versions.
The config file misses a logging section, from the website which I can see that should exist. But then those docs also refer you to http://docs.python.org/library/logging.config.html to configure a logging file. Well, a sample config should be there at least for some tweaking... (In reply to comment #16) > The config file misses a logging section, from the website which I can see that > should exist. But then those docs also refer you to > http://docs.python.org/library/logging.config.html to configure a logging file. > Well, a sample config should be there at least for some tweaking... There's no logging in the 0.5 version of Radicale, it has been added in the current git master (there's a (too?) small note about it on the documentation). http://radicale.org/user_documentation#id19 The default configuration file included in the 0.5 package is OK. Can we get a 0.6 ebuild. I think we need more than just a version bump since there are new features like wsgi etc...I am looking forward to give wsgi feature a try behind apache... I have a working radicale w/ wsgi setup behind a lighttpd. I need to see, if/what I needed to configure in radicale. I'll try to bump the package this evening. There are several small things that need to be fixed before I'll present an ebuild here. So lets wait for radicale-0.6.1 :) (In reply to comment #20) > There are several small things that need to be fixed before I'll present an > ebuild here. So lets wait for radicale-0.6.1 :) So are we good to go? (In reply to comment #21) > (In reply to comment #20) > > There are several small things that need to be fixed before I'll present an > > ebuild here. So lets wait for radicale-0.6.1 :) > > So are we good to go? Some executable and configuration files have been added in the 0.6.1 archive, I think that everything is ready for an ebuild! I hate to bug people like that but it has been a while since the radicale release and it would be great to have this ebuild tested. (In reply to comment #23) > I hate to bug people like that but it has been a while since the radicale > release and it would be great to have this ebuild tested. I have pushed an updated ebuild here: https://github.com/Kozea/Overlay/tree/master/app-office/radicale The WSGI script if installed if the "apache" use flag is set, and the FCGI script is installed if the "lighttpd" use flag is set. I don't know whether I should add lighttpd and apache as dependences when the flags are set. If everything works for you, I can update the sunrise overlay (and even add myself as the ebuild maintainer, if needed). You should probably rename "lighttpd" to "fastcgi", as this is a global useflag. But honestly, I would just install them without a useflag (see for example the discussion about the bash-completion flag on the gentoo-dev ML). And these two file should go to /usr/share/${PN} I think. Directly placing anything is under /var/www is a bad thing imho as you don't know how the server is structured there and putting stuff there might do bad things. Also /usr/share/${PN} is where the other webapps install there stuff to. Oh btw: My (old) version of the ebuild can be found here: [1] Besides the changes I already pointed out in the previous post, it adds flup as a dependency in the fastcgi case (is this correct?) I'll see that I get stuff merged and committed this evening. Sorry for the delay. [1] http://git.necoro.eu/overlay.git/tree/app-office/radicale/radicale-0.6.ebuild Thanks a lot for your tips and for your ebuild, I've updated my ebuild to reflect your changes. Things look much better now! Created attachment 289485 [details]
radicale-0.6.2.ebuild
I've committed the attached ebuild to sunrise.
I did the following changes over Guillaume's version:
* move stuff from DEPEND to RDEPEND where it belongs (my error to put in into DEPEND in the first place)
* remove ${ROOT} from insinto
* sort IUSE :)
* remove the README.rst prior to installing (else we have the README twice in the system, which is pointless)
* minor aesthetic/repoman-enforced updates
Created attachment 294989 [details, diff]
making the system a litttle bit more gentoo-itive.
I had an exception while compiling with python-3.1* so as a work-around adding >>RESTRICT_PYTHON_ABIS="3.*"<< omit the following problem: Traceback (most recent call last): File "setup.py", line 93, in <module> "Topic :: Office/Business :: Groupware"]) File "/usr/lib64/python3.1/distutils/core.py", line 149, in setup dist.run_commands() File "/usr/lib64/python3.1/distutils/dist.py", line 919, in run_commands self.run_command(cmd) File "/usr/lib64/python3.1/distutils/dist.py", line 938, in run_command cmd_obj.run() File "/usr/lib64/python3.1/distutils/command/install.py", line 592, in run self.run_command(cmd_name) File "/usr/lib64/python3.1/distutils/cmd.py", line 315, in run_command self.distribution.run_command(command) File "/usr/lib64/python3.1/distutils/dist.py", line 938, in run_command cmd_obj.run() File "/usr/lib64/python3.1/distutils/command/install_egg_info.py", line 44, in run self.distribution.metadata.write_pkg_file(f) File "/usr/lib64/python3.1/distutils/dist.py", line 1040, in write_pkg_file file.write('Description: %s\n' % long_desc) UnicodeEncodeError: 'ascii' codec can't encode character '\xa0' in position 455: ordinal not in range(128) !!! ERROR in app-office/radicale-0.6.2::sunrise: !!! In python_execute_function at line 3620 !!! Installation failed with CPython 3.1 in distutils_installation() function !!! Call stack: !!! * python_execute_function (/var/tmp/paludis/app-office-radicale-0.6.2/temp/loadsaveenv:3620) !!! * distutils_src_install (/var/tmp/paludis/app-office-radicale-0.6.2/temp/loadsaveenv:1472) !!! * src_install (/var/tmp/paludis/app-office-radicale-0.6.2/temp/loadsaveenv:5237) !!! * ebuild_f_install (/usr/libexec/paludis/0/src_install.bash:48) !!! * ebuild_main (/usr/libexec/paludis/ebuild.bash:646) !!! * main (/usr/libexec/paludis/ebuild.bash:672) diefunc: making ebuild PID 13813 exit with error die trap: exiting with error. I removed the non-ASCII character of the docstring in the git branch upstream, that should fix this bug. I just installed the sunrise overlay and tried to emerge radicale and got the same error: File "/usr/lib/python3.1/distutils/dist.py", line 1040, in write_pkg_file file.write('Description: %s\n' % long_desc) UnicodeEncodeError: 'ascii' codec can't encode character '\xa0' in position 455: ordinal not in range(128) Has the fix referenced in Comment 31 made it into what gets exposed in sunrise? (In reply to comment #32) > I just installed the sunrise overlay and tried to emerge radicale and got the > same error: > > File "/usr/lib/python3.1/distutils/dist.py", line 1040, in write_pkg_file > file.write('Description: %s\n' % long_desc) > UnicodeEncodeError: 'ascii' codec can't encode character '\xa0' in position > 455: ordinal not in range(128) > > Has the fix referenced in Comment 31 made it into what gets exposed in > sunrise? No, the "fix" is not in 0.6.2, but in 0.6.4 (just released!). The bug is indeed in Python, not fixed in Python 3.1, but fixed in Python 3.2 (and is not present in Python 2.x). http://bugs.python.org/issue6011 Renaming the ebuild from 0.6.2 to 0.6.4 works. Bump to 0.6.4 in sunrise -- also applied Micha's patch. Created attachment 301223 [details]
ebuild for carddav branch of radicale (git with CardDAV support)
There's git branch of radicale with CardDAV support. So far I've tested this branch with Evolution and CardDAV/CalDAV-sync(android). It's mostly based on the latest ebuild from sunrise with a few changes:
- switched from single log file to a log directory (see below why)
- added logrotate flag
- added logrotate script
Created attachment 301225 [details]
logrotate script for the live ebuild
Created attachment 323266 [details] radicale-0.7.1.ebuild Bump to newest version of radicale: 0.7.1 This ebuild also improves the log handling. Two notes: - I did not include the logrotate-script - I did not add the "pam"-dependency: The requested package is not in portage -- and it is so old, that I don't feel like adding it. Especially in the light of http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-1502 (this affects another pam binding, but still). Created attachment 323268 [details]
init-script for 0.7.1
Updated init script
Created attachment 358704 [details]
radicale-0.8.ebuild
New ebuild for radicale-0.8
Please note, that this ebuild marks radicale as being Python2 only, as flup is not py3 ready yet and python-ldap does not support py3.3.
Created attachment 358706 [details, diff]
radicale-0.8-config.patch
Instead of the sed-orgy in the old ebuild, this one uses a patch (mainly because there are now more changes...).
For me, the init-script isn't working properly. I am able to start radicale as root, but when started through the scipt, it crashes. myserver ~ # /etc/init.d/radicale start * Starting radicale ... [ ok ] myserver ~ # /etc/init.d/radicale status * status: crashed no logentries however. Created attachment 371168 [details, diff]
Patch for ebuild to add missing dependency
Hi,
I've tried to use radicale with postgres and it was missing dev-python/psycopg. I've added it as dependency to the ebuild in my local overlay. I think it's not perfect because I need now the sql and the postgres USE flag. Perhaps someone have a better idea how to solve this.
Cheers,
Kim
I am going to update the ebuild to 0.10 this week. Changes, I'd like to introduce: - python-pam is now in portage -> add 'pam' flag and the dependency - remove the 'fastcgi' flag and print out a message instead. Reason: flup is just one possibility to add fcgi support. Just point the user in the right direction. It's still his responsibility to set up the server. - add 'http' flag (better name?) and add dependency on dev-python/requests @kim: I don't think, adding db-specific flags is a good idea. Such things are handled by sqlalchemy (which, unfortunately, has changed from useflags to 'please install yourself' behavior) I still can't mark the package as supporting py3, due to some dependencies. The only possibility here would be to go the sqlalchemy way and print a 'if you want this, install that' wall of text. Did you actually update to 0.10, is the ebuild stuck in a review process? Created attachment 417808 [details]
New ebuild for Radicale 1.0.1
Attached here is an ebuild for Radicale 1.0.1, the latest release. Changes from the 0.8 files in Sunrise are, of course, the version bump, a respin and slight simplification of the configuration file patch (which I will attach momentarily), and a change from doins to python_doscript for radicale.{wsgi,fcgi}, which both makes the files executable (necessary for spawn-fcgi to launch them) and also repoints them through python-exec and fixes their shebangs so they don’t explode if your system Python is Python 3.
Created attachment 417810 [details, diff]
The new configuration file patch for version 1.0.1
I've reworked ebuilds from Sunrise and this bug and included Radicale into the tree. Closing bug. |