On 02/03/2013 10:23 PM, Greg KH wrote:
On Sun, Feb 03, 2013 at 12:51:41PM +0200, Angelos
On 02/03/2013 10:49 AM, Greg KH wrote:
So Tumbleweed is, I think, almost 2 years old now.
Thank you for your excellent
work on this
It seems to be
working fairly well, or at least well enough for my daily use, and I
haven't heard any complaints about it in a long time which means that
either no one is using it, or it's working for others :)
I am using it for 1+
year now and it is working great. I am
upgrading once a month.
The only 2 issues I have:
1. some dev projects have not yet created tumbleweed repositories on
OBS (I have taken care of that for things that I maintain)
shouldn't be needed, unless you have packages that depend
on stuff like KDE or GNOME.
ok thanks for clearing this up. I thought the safe way was to have a
tumbleweed repository, but I see your point.
updates from openSUSE-current-oss-updates are incompatible
with current package versions. Perhaps there should be a
Tumbleweed-oss-updates repository to port those updates.
I have never heard of
this, nor have ever seen this happen before, do
you have an specific examples of packages with this problem?
I have just upgraded my system from Tumbleweed.
After that I run "zypper patch" and I get the following conflicts:
patch:openSUSE-2012-813-1.noarch conflicts with libpackagekit-qt2-2.i586
patch:openSUSE-2012-658-1.noarch conflicts with libpackagekit-glib2-14.i586
After I solve this conflict by installing the updates, I get more
I assume those updates should be applied and then I have to upgrade the
system once more?
There should not be a need for the updates repo to have a tumbleweed
repo, if I've done everything properly.
So, I was
thinking about maybe, when 12.3 changing Tumbleweed from being
an "add-on" repo on top of the 12.3 repos, to being a "full" distro
snapshot. That would resolve the build number problems we have had, but
the dependancy rebuild issue would increase.
This is a great idea. Is there a plan
on how to sync during a stable
The whole repo would get created from scratch and start over with
new stable update, much like it happens today.
rebuild problem can be manually handled, much like FACTORY currently
is, but odds are, I would lean toward the conservative side, having more
rebuilds than are probably necessary just to ensure that systems work
well. That means that libreoffice would be updated on a weekly basis
for users, which might get annoying over time :)
Is it really necessary to update
libre-office so often? Perhaps
packages that cause big file downloads should be kept to once per 2
weeks or more. Thoughts?
It's not a "need", the Libreoffice
packages aren't getting updated, they
are just getting rebuilt due to all of the dependancy issues in the
distro (touch almost anything, and it will end up rebuilding.) It's
just the most visable example of the dependancy logic we have.
Remote Sensing Laboratory
National Technical University of Athens
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org