Suse 11.1 repo-update

Since some days I get the message that the repository repo-update seems to be outdated from my updateapplet.
Is there another mirror in place now ?
Thanks

It would be useful to know:

  • which repo you are using currently (complete path)

11.2 reached end of life about a month ago, see
http://en.opensuse.org/Lifetime

you should look to moving to a supported version, or maybe you want to
participate in the Project Evergreen, see
http://en.opensuse.org/openSUSE:Evergreen


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11

@Denver: you wanted to say 11.1 I am sure.
Right, that is why it would be interesting to know what repos he is referring to.
/update and /oss /noss where (AFAIK) shifted to packman, but I checked, they are available as well in Index of /pub/opensuse/update/11.1 and so on and so forth. So that is why I was wondering what repos he referred to. Maybe he has a problem because he is using the automated mirror that…probably does not work any more after end of support.

On 2011-02-13 21:36, tobiasw2 wrote:
>
> Since some days I get the message that the repository repo-update seems
> to be outdated from my updateapplet.

There is no longer 11.1.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Some of the 11.1 libraries don’t seem to be supported but many are still there and are updated.

Nvidia appears to have dropped support for its 11.1 repository.

On 02/14/2011 01:06 AM, stakanov wrote:
>
> @Denver: you wanted to say 11.1 I am sure.

correct…2 was a typo.


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11

So I have to update, thanks for advice.

Lifetime is a bit short, isn’t it ?

Update costs me at least 2 hours, only if everything works

Or you just wait for 11.4 to come out and take advantage of the maximum duration of support (should come out the beginning of March). In the meanwhile the repository Evergreen could come handy.

Or look at the Tumbleweed project?
http://en.opensuse.org/Tumbleweed


Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.32.27-0.2-default
up 3 days 13:55, 2 users, load average: 0.23, 0.11, 0.09
GPU GeForce 8600 GTS Silent - Driver Version: 260.19.36

On 02/14/2011 06:06 PM, tobiasw2 wrote:
>
> Lifetime is a bit short, isn’t it ?

yep!

personally, i think it is so short for two reasons:

first, the linux project is on a FAST track, and even with an 8 month
release cycle, openSUSE seldom shipping the ‘latest versions’

and second, short lives could be one part of a plan to move openSUSE
users to the profitable (for Novell) Enterprise product, which is
supported for years…like five or eight…


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11

On 2011-02-14 19:30, DenverD wrote:

> personally, i think it is so short for two reasons:

Money.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

I never understood why upgrading every 18 months would be such a drawback… especially since it obviously is easily possible to do a “hot” upgrade (meaning upgrading the entire system within the running one) since 11.2 or 11.3. Don’t get me wrong, I would prefer a longer lifecycle as well (and generally welcome both the Tumbleweed and the Evergreen project), but after all it’s not that much of a big deal for me. I wait for the new version, let it get bugfixed for a couple of weeks, then it usually is stable enough to substitute the running system.

On 2011-02-15 00:06, gropiuskalle wrote:
>
> I never understood why upgrading every 18 months would be such a
> drawback…

The drawback is the lifecycle.

> I would prefer a longer
> lifecycle as well (and generally welcome both the Tumbleweed and the
> Evergreen project), but after all it’s not that much of a big deal for
> me. I wait for the new version, let it get bugfixed for a couple of
> weeks, then it usually is stable enough to substitute the running
> system.

It is not much of a deal if you only have one or two computers. It is a big
deal if you have a small shop to upgrade, about every year.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Decided to use Evergreen. Works ok.

But now kupdate, which I switched to zypper, claims

kupdateapplet(9572) Logics::slotPluginNeedsConfiguration: ? plugin needs configuration: no update repos

despite evergreen has bee added with
zypper ar -t YUM Index of /repositories/openSUSE:/Evergreen:/11.1/standard repoupdate

any ideas,
Thanks

Could you post output from


zypper repos --sort-by-priority 
### or 
zypper repos --sort-by-priority --details

Also what are your settings for kupdateapplet?

zypper repos --sort-by-priority

| Alias | Name | Enabled | Refresh | Priority

—±-------------------±----------------------±--------±--------±--------
2 | Evergreen | Evergreen | Yes | Yes | 20
1 | Downloads | Downloads | Yes | Yes | 99
3 | Mozilla | Mozilla | No | Yes | 99
4 | Packman Repository | Packman Repository | Yes | Yes | 99
5 | nvidia | nvidia | No | Yes | 99
6 | openSUSE 11.1-0 | openSUSE 11.1-0 | No | No | 99
11 | repoupdate | repoupdate | Yes | Yes | 99
7 | repo-debug | openSUSE-11.1-Debug | No | Yes | 100
8 | repo-non-oss | openSUSE-11.1-Non-Oss | Yes | Yes | 100
9 | repo-oss | openSUSE-11.1-Oss | Yes | Yes | 100
10 | repo-source | openSUSE-11.1-Source | No | Yes | 100

Also what are your settings for kupdateapplet?

  • ZYpp Plugin as Backend
  • none of the options is selected


[quote="tobiasw2,post:17,topic:61985"]
zypper repos --sort-by-priority 

#  | Alias              | Name                  | Enabled | Refresh | Priority
---+--------------------+-----------------------+---------+---------+---------
2  | Evergreen          | Evergreen             | Yes     | Yes     |   20
1  | Downloads          | Downloads             | Yes     | Yes     |   99
3  | Mozilla            | Mozilla               | No      | Yes     |   99
4  | Packman Repository | Packman Repository    | Yes     | Yes     |   99
5  | nvidia             | nvidia                | No      | Yes     |   99
6  | openSUSE 11.1-0    | openSUSE 11.1-0       | No      | No      |   99
11 | repoupdate         | repoupdate            | Yes     | Yes     |   99
7  | repo-debug         | openSUSE-11.1-Debug   | No      | Yes     |  100
8  | repo-non-oss       | openSUSE-11.1-Non-Oss | Yes     | Yes     |  100
9  | repo-oss           | openSUSE-11.1-Oss     | Yes     | Yes     |  100
10 | repo-source        | openSUSE-11.1-Source  | No      | Yes     |  100

[/quote]

Not a problem refreshing the repos, I get those messages. I update my systems 2x a week using crontab instead of the applet.

You may want to pay attention to the priority of your repos. Evergreen is first while others enabled are left to FIFO. That might be the reason for the errors.

Suggest 95 for :
repoupdate <– openSUSE-11.1-update?
openSUSE-11.1-Non-Oss
openSUSE-11.1-Oss

96: Or 94: depending on your preference
Packman Repository

IMHO, it would be better for users if OpenSuse would end support for a release after the latest release. For instance, support for OpenSuSe 11.1 ends 2 weeks after the release of 11.4. Users would have an upgrade choice, 11.3 or 11.4. When ending in between releases there’s only 11.3.

On 02/20/2011 05:36 PM, tararpharazon wrote:
>
> When ending in between releases there’s only 11.3.

what is 11.2, chopped liver?


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11