Backwards incompatible change: PowerDNS (2.9.x to 3.1.x)

[Stephen John Smoogen]

On 28 November 2012 08:03, Gary T. Giesen <giesen at snickers.org> wrote:
> Fancy record support (ie URL) records are also no longer supported in
> 3.x. Some people's businesses depend on these features, and if they
> inadvertently upgrade it will cause downtime for zones using those
> records. Now they've been forced to exclude pdns in their yum configs
> so they can run a yum update without breaking their systems...
>
> This completely defeats the purpose of having an enterprise OS with a
> stable set of packages...

I would really like to point out a couple of things that goes with ANY
3rd party repository and people who use them should remember EVERY
time they do a yum update:

0) Third party repositories are volunteer organizations which will set
guidelines on how updates and packages will occur. Enforcement of
those guidelines can only be proactive by community members being
active.
1) Being proactive means helping to maintain packages that you use and
testing packages before they get pushed to updates.
2) Problems not caught by this method will still happen but can be
mitigated by people helping packagers and other users.

This is not just an EPEL thing. RPMforge, ATrpms, Dag, CentOS Extras
etc all run into the same issue. If you feel this is too expensive,
then you can find services elsewhere at a cost more meeting your
needs.


-- 
Stephen J Smoogen.
"Don't derail a useful feature for the 99% because you're not in it."
Linus Torvalds
"Years ago my mother used to say to me,... Elwood, you must be oh
so smart or oh so pleasant. Well, for years I was smart. I
recommend pleasant. You may quote me."  —James Stewart as Elwood P. Dowd