>>> Has Greg-KH advised Tw users to change priorities? If so, have you a
>>> reference link for that?
> On the contrary, he has told not to, several times.
> I’m sorry, no reference here to that either right now.
Funny, first hit in Google search “priorities greg k-h”
On 01/19/2013 10:08 AM, Vahis wrote:
> Then why do you say it’s “untested”?
it is untested (by Greg) in Tumbleweed.
perhaps i’m wrong (i was once before:) but i think this is the way it goes:
developers hack out new versions of code (not just bug fixes, but NEW
stuff) and submits it to factory where it is tested and tested in the
factory environment…after some time and
occasionally/periodically/weekly (i do NOT know the schedule, but i
guess its when Greg’s real job and other commitments allow, or when the
mood moves him), Greg installs the some factory tested NEW code in his
Tumbleweed and if smiling he moves it into the Tumbleweed base…
at the same time other developers/hackers across the earth are
improving/fixing bugs in the current openSUSE version…as they do,
they are made available as security patch, major bug updates or selected
new releases (like the monthly mozilla) which can be install either by
YaST Online Update or zypper patch…
and, there are other updates (that appear in YaST with blue fonts next
to the installed version (in black font))…which can be installed via
YaST Software Management (select version and click the new version) or
“zypper up”…those updates have not been tested in and approved for
the Tumbleweed environment (and won’t be unless they get into factory
first)…however, if a system has the priorities of all repos the same,
and “zypper dup” is run one might easily introduce the untested in
Tumbleweed ‘current’ code into their Tumbleweed–happy testing!!
On 01/19/2013 12:46 PM, consused wrote:
> Greg-KH has posted that it is normal with plain
> zypper dup to have package sources change between tumbleweed and current
> or standard openSUSE update repos. He supports that approach, so one
> must assume that he practices that approach on his own systems.
well…hmmmmm…perhaps you are correct…i have not seen his post
saying that…i did read more than one of his posts where he explained
that the path to Tumbleweed had to go through factory testing…before
he would put it in…
hmmmmmm…and now i see Greg’s own words on priorities (in recent post
to this thread)…sure looks like i missed more of his posts than i
read (or remembered reading)…
i am (was) far wrong in my understanding of Tumbleweed.
any mod who wishes to is welcomed to remove all the incorrect info i’ve
put into this thread…with my apologies…
but, who can answer the original question: how can two machines running
TW turn up with different versions of some code, and the question in the
and let me add: why do folks have to read in so many different places
(wiki, forums, lists and probably IRC and personal blogs) to learn all
the nuances of the one true way?