On Mon, Oct 15, 2012 at 1:59 AM, Gordan Bobic <[email protected]> wrote: > On 10/14/2012 11:05 PM, Marc Curry wrote: >> >> I was excited to see this project, but I'm wondering if anyone is >> still maintaining the distro? The mailing list seems a little quiet >> (the last post is March 2012), and when I use yum for any package >> maintenance, it seems the repo hasn't been updated since June 2012: >> >> Not using downloaded repomd.xml because it is older than what we have: >> Current : Sun Jun 3 03:42:34 2012 >> Downloaded: Sat Mar 24 17:18:33 2012 > > > The distro is certainly not abandoned, if that's what you are asking. It's > just that both myself and the other maintainer have been rather busy in the > past couple of months with these things called "day jobs", which is why we > haven't yet rebuilt the latest upstream updates.
I completely understand. Its very good to hear that redsleeve is alive and well! I'd like to preface all the below feedback with a *huge* thanks for making this distro available!! Its exactly what I was looking for (replacing an aging web/mail server with a raspberry pi). > Putting together a set of > scripts that fetch the latest upstream updates and rebuild the new ones > daily is on my todo list. That would be ideal. The easier and more automated it is, the better. Let us (the users) know if/how we can help, besides just submitting bug reports to the list. > >> The primary advantage of this distro, for me, is familiarity (I use >> distros in this family all the time), but if it only gets updated once >> in a blue moon...it won't be useful to begin a project using it for a >> home server. > > > The upstream distro only gets updated relatively infrequently - that's kind > of the whole point; the goal posts don't keep changing. I agree if you mean the infrequent 6.x mileposts, but there are fairly frequent bug/security updates released that make the upstream distro "enterprise quality", as well. If its running in a protected/isolated environment, that's one thing. Using it, as in my case, as a server connected to the Internet, is another. > > If there are any packages you would like to see updated sooner rather than > later (e.g. specific bugs you are tripping over or potential security > concerns), do tell - I'll see what I can do to get them updated to the > latest upstream versions ASAP. The first one that crossed my mind: labeled as a "critical security update", xulrunner (used by Firefox) was very recently released. I understand this is not really a concern for typical server function. There were also about 6 "moderate" and about 4 "important" security updates in the last month or so, not counting bug fixes. I'm less concerned about minor bug fixes. Ideally there is a script that automates the update, but in lieu of that, maybe the way to go is to establish a severity level threshold at which updates are released, to fix the potentially nasty stuff? Best regards, -Marc > > Gordan > _______________________________________________ > users mailing list > [email protected] > http://lists.redsleeve.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
