TL;DR → I need somebody to help me with Cherokee, and I intend to stop
maintaining it (i.e. orphan it) after Wheezy is released.
I have been maintaining Cherokee for quite a long time — I packaged
the initial version sitting together with the upstream author while at
a conference in Bolivia, back in 2004, and did the first upload to
Debian in 2006.
The package description is:
Cherokee is a very fast, flexible and easy to configure Web Server.
It supports the widespread technologies nowadays: FastCGI, SCGI, PHP,
CGI, TLS and SSL encrypted connections, Virtual hosts, Authentication,
on the fly encoding, Apache compatible log files, HTTP Load Balancing,
Data Base Balancing, SSI, Reverse HTTP Proxy and much more.
.
Cherokee also provides an easy to use configuration interface that
allows one to configure the server from top to bottom without having to
edit a text configuration file.
After being a very quiet package for some time, it entered a phase of
quick development, and saw eight major versions (and 82 upstream
versions in total) over five years. Right now, it seems development
speed has slowed down again.
Cherokee is not a very complex package; although it generates 16
binary packages, its build and installation logic are quite
straightforward. The package is quite a typical DH-based one.
Interaction with the upstream developers is a gift, it's one of the
swiftest packages I've seen — They are most responsive, and most
interested in having it packaged for Debian. There is an important
difference in our postures, however — A common one: They are
interested in supporting the latest versions, but not as much in
giving support to older releases. I have been requested several times
to push the latest release to backports.debian.org, but have failed to
do so.
Having the upstream project leader (Álvaro López) listed as a
co-maintainer, and having Leonel Núñez as an active co-maintainer as
well, why do I request an adopter for the cherokee package instead of
leaving it just for them? Because of the work focus. I cannot provide
proper support for older releases, as I am not quite literate in C and
the (very few) patches I have submitted to them end up being worse
than the bug I'm treating, and their main focus is basically providing
newer versions and prompting the users to upgrade. Leonel's work has
been quite useful, but as I have repeatedly told him, it is often
limited to a "make it compile and ship it" stance — Again, due to a
different focus.
I expect to hand this package over to a DD or DM, so no explicit
sponsoring is needed. Álvaro is since recently a Canonical employee —
Of course, I don't know much about his position there, but if you are
also related to Ubuntu, you might find extra points in interacting
with a co-worker.
Cherokee currently has an open security bug, but before it, since
three versions ago (1.2.100) has given several FTBFS in several
platforms (during the build tests — The binary itself builds
correctly, but might be performing in a buggy way). I have been unable
to follow up in a responsible way to the bugs.
IN SHORT, MY REQUEST:
--------------------
I am sending now this "Request For Adoption" bug. I intend to keep
maintaining Cherokee the best way I can (which as can be seen is not
too good) until the next Debian Stable release, and if no new
maintainer steps up by then, will flag it as Orphaned.
Thank you very much,
I've never maintained a Debian package before, but I'm certainly willing to learn if for no other reason than to ensure this project continues for as an active package. What's the first step?
M. David Peterson dijo [Fri, Nov 11, 2011 at 05:30:09PM -0800]: Hi, The package is kept in a public git repository, tracked at: http://git.debian.org/?s=collab-maint%2Fcherokee To be honest, I'd love to take your proposal, but that's more or less where we are now - We need somebody familiar with maintaining packages for Debian (and not just building packages, that's where we stand now). This package is not too complex, but is clearly more than what I'd suggest you to start with. Anyway, if you are interested in maintaining packages in Debian, start with the New Maintainers' Guide: http://www.debian.org/doc/manuals/maint-guide/ Also, be sure to get familiar with the Debian policy: http://www.debian.org/doc/debian-policy/ Greetings,
Hello: I am a Cherokee Fan and a Cherokee User. I keep the Ubuntu PPA package updated with the lattest Cherokee version https://launchpad.net/~cherokee-webserver/+archive/ppa and when there is a need to patch something in /debian a patch is made. I'd like to take the package or help a DD or DM to keep it updated and to send or apply upstream patches for the Debian Releases For sometime I've been working with Gunnar to keep the last cherokee version updated for Debian Unstable. I can keep Cherokee with the lattest version for Debian Unstable, and keep it updated for the Testing and Stable versions. I've added, edited, redoed some patches for this package. A little background: For sometime when CLAMAV was in Ubuntu Universe ( community maintained), Working with Scott Kittermain ( MOTU ) we keept Clamav updated with security patches for the current Ubuntu versions, making patches from upstream updated versions. We made the MIR document and applied to move clamav from Universe ( community maintained) to Main ( officialy maintained) https://wiki.ubuntu.com/MainInclusionReportClamav Every clamav release, we searched the CVEs and sent the patches to launchpad for revision and where applied for a new Ubuntu Security release. Once Clamav went into MAIN I stoped keeping track for clamav CVE's So I only need to keep up with the debian policy Saludos and I hope I can help with this.
Hello: I am a Cherokee Fan and a Cherokee User. I keep the Ubuntu PPA package updated with the lattest Cherokee version https://launchpad.net/~cherokee-webserver/+archive/ppa and when there is a need to patch something in /debian a patch is made. I'd like to take the package or help a DD or DM to keep it updated and to send or apply upstream patches for the Debian Releases For sometime I've been working with Gunnar to keep the last cherokee version updated for Debian Unstable. I can keep Cherokee with the lattest version for Debian Unstable, and keep it updated for the Testing and Stable versions. I've added, edited, redoed some patches for this package. A little background: For sometime when CLAMAV was in Ubuntu Universe ( community maintained), Working with Scott Kittermain ( MOTU ) we keept Clamav updated with security patches for the current Ubuntu versions, making patches from upstream updated versions. We made the MIR document and applied to move clamav from Universe ( community maintained) to Main ( officialy maintained) https://wiki.ubuntu.com/MainInclusionReportClamav Every clamav release, we searched the CVEs and sent the patches to launchpad for revision and where applied for a new Ubuntu Security release. Once Clamav went into MAIN I stoped keeping track for clamav CVE's So I only need to keep up with the debian policy Saludos and I hope I can help with this.
I can adopt this package. I'm listed as an uploader but I'm not a debian developer or maintainder What's the procedure to adopt this package ??
retitle 648256 RFP: cherokee -- Very fast, flexible and easy to configure web server noowner 648256 tag 648256 - pending thanks Hi, A long time ago, you expressed interest in packaging cherokee. Unfortunately, it seems that it did not happen. In Debian, we try not to keep ITP bugs open for a too long time, as it might cause other prospective maintainers to refrain from packaging the software. This is an automatic email to change the status of cherokee back from ITP (Intent to Package) to RFP (Request for Package), because this bug hasn't seen any activity during the last 14 months. If you are still interested in packaging cherokee, please send a mail to <control@bugs.debian.org> with: retitle 648256 ITP: cherokee -- Very fast, flexible and easy to configure web server owner 648256 ! thanks It is also a good idea to document your progress on this ITP from time to time, by mailing <648256@bugs.debian.org>. If you need guidance on how to package this software, please reply to this email, and/or contact the debian-mentors@lists.debian.org mailing list. Thank you for your interest in Debian,
El 2013-08-16 10:58, Lucas Nussbaum escribió: Hello: I was waiting for debian to be released so I can push the new cherokee package to sid. I need an sponsor/mentor for that. I had the package ready some months ago, let me check the package status and see if we can upload the lattest version. Thank you Leonel--- Leonel Nunez http://enelserver.com/leonel
Ping
hello : El 2013-11-30 13:03, Ken Sharp escribió: I've already cleaned my schedule I'll start working on this bug next week For what I've seen the root directory on the package has changed since the prior version that is what is holding me down Can you help me in case I need help--- Leonel Nunez
Hi, I have recently been in touch with upstream (Stefan de Konink) and have been assisting with a few bugs in Cherokee. I'd be interested in helping with the packaging since I will need to maintain updated Cherokee packages for myself for a Wheezy server anyway. Are you interested in co-maintaining the package in Sid? D.
El 2014-01-02 04:11, Daniel Silverstone escribió: Yes all help is welcome I'm already working on the package but it's taking me longer than I expected but I'm moving on Gracias y Saludos--- Leonel Nunez http://enelserver.com/leonel
I went with what was there from before and just removed the patch which didn't apply from the quilt. That worked just fine for me. Obviously it's not ideal since it won't be necessarily up-to-date policy-wise, but it was good. Gunnar was maintaining it on git.debian.org using git-buildpackage's infra. Since then, upstream has moved to git themselves (on github) so we should probably just migrate to that git history and add the debian/ dir in. Let me know if you want me to do any of this. D.
Yes we are working on git.debian.org, I still have access to git.debian.org sometime in the past upstream kept a /debian dir on the package but was removed. I don't know if upstream wants to add the /debian dir but if you have acces to git.debian we can work there or if you prefer work with upstream I don't mind as long we can push the package to sid This is the cherokee package status The current version on git.debian.org and the ubuntu ppa version is the 1.2.102 version. the 1.2.103 version changed the package root directory from cherokee to webserver-1.2.103 so .. No files are found when we try to build the package I'm working on fixing that so we can push the package to SID--- Leonel Nunez http://enelserver.com/leonel
Hello: Last months all got very busy here and unfortunately haven't find time finish this new package version even with the great help from other people who steped up to help. So we need to find a new maintainer, I'd like to thank Daniel Silverstone and unit193@gmail.com for the great job they have done. Sorry to abandon this package, but I know there are better people for the this task Again Sorry for this .--- Leonel Nunez http://enelserver.com/leonel
retitle 648256 RFP: cherokee -- Very fast, flexible and easy to noowner 648256 tag 648256 - pending thanks Hi, A long time ago, you expressed interest in packaging cherokee. Unfortunately, it seems that it did not happen. In Debian, we try not to keep ITP bugs open for a too long time, as it might cause other prospective maintainers to refrain from packaging the software. This is an automatic email to change the status of cherokee from ITP (Intent to Package) to RFP (Request for Package), because this bug hasn't seen any activity during the last 12 months. If you are still interested in packaging cherokee, please send a mail to <control@bugs.debian.org> with: retitle 648256 ITP: cherokee -- Very fast, flexible and easy to owner 648256 ! thanks It is also a good idea to document your progress on this ITP from time to time, by mailing <648256@bugs.debian.org>. If you need guidance on how to package this software, please reply to this email, and/or contact the debian-mentors@lists.debian.org mailing list. Thank you for your interest in Debian,
This package was already available in Debian but got removed again due to lack of interest. Anyway, this RFP is longer needed and can be closed. Thorsten