Great job, Gentoo apache team! Very professional move!
This is the last time I will EVER run gentoo on a machine that I depend on as a server.



I love how people are trying to justify this move by saying "oh read the mailing list" or the newletter, or my favorite "its a community distro." Its not a question of notification, its a question having .xx upgrade that requires a bunch of manual configuration just to be operational. Its completely insane!loki99 wrote:You two guys should rather read the GWN or the gentoo dev mailing list (where it has been discussed for a couple of months!)
What else should they do? Send you a personal email?
It has nothing to do with .xx upgrade or x. upgrade! Apache was changed so it would be compliant with the upstream apache release. This way anyone who is an apache admin on any other distro can use apache on Gentoo and not have to relearn how to use it the Gentoo way.asv wrote: Its not a question of notification, its a question having .xx upgrade that requires a bunch of manual configuration just to be operational. Its completely insane!

Do you have to manually edit apache configuration files after the upgrade in order for apache to run? Yes!Monkeh wrote: Plus, it doesn't take hours to fix, nor does it require 'manual configuration just to be operational'. .

It didn't cause me a lot of downtime and again its not a question of being warned, its a question of expectations for a routine software update. I guess I just have elevated expectations from years of running debian and redhat. Do you honestly think Redhat would do a point release apache upgrade for RHEL4 that broke every exisiting configuration?Monkeh wrote: The fact is, you were warned, you didn't have to update, and you didn't check to see exactly what the update did before installing it. If it caused you a lot of downtime, it's your own fault.

Well the best way to handle that would to keep the existing confuration scheme until a major apache update such as 2.x instead of 2.x.x.loki99 wrote:I'm still waiting for an answer.loki99 wrote: But if you have a better idea how to handle something like that, I bet the devs (and me too!) would love to hear about it.
if you're doing updates on a server which you depend on, you just have to check what the updates do!asv wrote:This is the last time I will EVER run gentoo on a machine that I depend on as a server.

Whatever problems may have been introduced, it is only the administrator's fault for not testing before making changes to a live system. I'm not even talking about reading mailing lists, etc.asv wrote:Who was the genius who decided to change all the apache2 config files with the latest update? Now my finely tuned apache configuration is broken and its going to take me hours to fix it.
Great job, Gentoo apache team! Very professional move!
This is the last time I will EVER run gentoo on a machine that I depend on as a server.
Ignore hard and soft masks, and you don't have to worry about that "crap." Then its just a matter of more testing before the masked packages are made stable. (Which you can pretend didn't previously exist in a masked state.)j79zlr wrote:no silly hard masked, soft masked crap. Tested, stable, committed.
It would be nice to have a RSS-feed announcing important changes!pjp wrote: Though regarding informing the Gentoo community, I'd like to see something dedicated to announcing "major changes." I don't want to read the GWN every week for the .001% of useful information I might need. Mailing lists aren't appropriate, as there are way too many, unless there was a means of identifying "important" traffic.
What one person considers a "major update" is relative to what one does with their system. I have a laptop and a server running gentoo.. they use very different sets of packages. What would be ideal is a system for notifications based on what is installed on your system. I am sure many people would gladly sign up to a service in which portage notified a server about which packages they were interested in recieving major announcements about.pjp wrote:Though regarding informing the Gentoo community, I'd like to see something dedicated to announcing "major changes."
Or a girl wearing almost nothing jumping out of a cake whispering it into your ear...Simba wrote:an sms would be great..

You could have at least linked to the upgrade instructions at the end of the ebuild. If you know what to do it is of course no big deal BUT only if you know it. Sure geeks know what to do or those who read the mailing list or those who administer a http server with 10 vhosts but that's not the usual case. No really it was very annoying.loki99 wrote:But if you have a better idea how to handle something like that, I bet the devs (and me too!) would love to hear about it.