Mailinglist Archive: opensuse-buildservice (162 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] openSUSE:Tools dropped 11.3 repo already?
- From: Archie Cobbs <archie.cobbs@xxxxxxxxx>
- Date: Tue, 24 Jan 2012 08:13:16 -0600
- Message-id: <CANSoFxsQXFpQ8+1_8V96+bg0zhtnFYPE1WEJnGKXAjjujgP6Fw@mail.gmail.com>
OK forget zypper and openSUSE:Tools for the moment...
What I'm simply trying to say is: just because 11.3 is itself EOL, that
doesn't mean OBS projects should start dropping the 11.3 repo right away.
Do others not agree?
-Archie
On Tue, Jan 24, 2012 at 3:27 AM, Adrian Schröter <adrian@xxxxxxx> wrote:
--
Archie L. Cobbs
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx
What I'm simply trying to say is: just because 11.3 is itself EOL, that
doesn't mean OBS projects should start dropping the 11.3 repo right away.
Do others not agree?
-Archie
On Tue, Jan 24, 2012 at 3:27 AM, Adrian Schröter <adrian@xxxxxxx> wrote:
Am Montag, 23. Januar 2012, 20:18:49 schrieb Archie Cobbs:
I noticed that openSUSE:Tools has dropped its 11.3 repo already.
I understand 11.3 is EOL'd, but it seems like Tools repo should be special,
as it contains zypper -- the tool that lets you upgrade.
No, it was never part of that repo.
I understand that EOL means no longer "community supported" - that's fine..--
but it seems to me that "community supported" is a completely different
concept than "exists as a repo in a project".
After all, openSUSE:Tools has RHEL 4 and all these other non-SUSE repos...
are those distributions "community supported" by the openSUSE project??
So I don't understand the rush to remove the repo.
Needless to say, I still have stable 11.3 systems around that I'm not ready
to upgrade just yet...
Thanks,
-Archie
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian@xxxxxxx
--
Archie L. Cobbs
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx
| < Previous | Next > |