Mailinglist Archive: opensuse-buildservice (162 mails)

< Previous Next >
Re: [opensuse-buildservice] openSUSE:Tools dropped 11.3 repo already?
On 1/26/2012 1:15 PM, Archie Cobbs wrote:
On Thu, Jan 26, 2012 at 12:04 PM, Claudio Freire<klaussfreire@xxxxxxxxx> wrote:
On Thu, Jan 26, 2012 at 2:47 PM, Archie Cobbs<archie.cobbs@xxxxxxxxx> wrote:
We have a bunch of mission critical machines running openSUSE 11.3.
Why? Because one of the attractive features of openSUSE is that it is
very stable and runs great for a long time.

But now all of these machines are essentially unsupportable (and
unreproducible), until we force them through an upgrade process that
creates risk.

Just add the DISCONTINUED repo to your home, and all is fine.

So that solves the problem for my home repository, but what about the
10-15 other repos that our machines depend on? For example,
Apache2:Modules, server:monitoring, etc., etc.

So that doesn't seem like a very scalable solution.


Archie L. Cobbs

I agree 100%. I made the mistake of using Server:Monitoring and some others and now I don't do that any more. Anything I really need maintained for myself, I copy to my own home project, which means living without a lot of things I would like to have newer because I can't maintain that much all by myself.

Your comment about the existence of evergreen speaking for itself I also agree completely with.

We who chose suse a few years ago because it had qualities that said "we will be able to count on this for a long time" have now all gotten burned. Suse is changing way too much from month to month, but we're all invested in it now, servers already installed and deployed and 24/7 customers running their entire business on them, many with special EDI setups with other parties requiring non-trivial firewall coordination with customers-of-customers and vendors-of-customers IT people, If an IP changes, it no longer matches the external peoples firewalls and all the EDI transactions break... Uncountable business damage with orders not received or processed, etc, so it's rather non-trivial to upgrade or migrate these customers to other boxes just because the os version went eol a few months later. In place upgrades are out because as difficult as a migration to another newer box is, at least it can be reverted instantly with 100% confidence and safety. Not so with an in-place upgrade.

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups