Hello people,
I'd like to delete all package from GNOME:UNSTABLE to avoid people using
old, stale, broken stuff. G:U, as explained [1] is only going to be used
once Factory is frozen prior to the next openSUSE release.
If you have any packages in there that you need, can you please copy
them somewhere else. I plan on removing all packages in a weeks time.
Also, as a side note, GNOME:Factory:Next have now been removed and
people should be using GNOME:Factory instead.
Thanks,
Magnus
[1] http://en.opensuse.org/GNOME/Repositories
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Hey there,
Some relevant information for people using G:F.
If you're seeing some weird stuff about gconf in the next few days, ping
me.
Vincent
----- Forwarded message from Vincent Untz <vuntz(a)opensuse.org> -----
Date: Thu, 26 Feb 2009 23:24:54 +0100
From: Vincent Untz <vuntz(a)opensuse.org>
To: opensuse-factory(a)opensuse.org, Michael Meeks <michael.meeks(a)novell.com>
Subject: Re: [opensuse-factory] gconftool-2 makes factory update slow
Mail-Followup-To: opensuse-factory(a)opensuse.org,
Michael Meeks <michael.meeks(a)novell.com>
Hi,
Le jeudi 26 février 2009, à 02:35 +0100, Vincent Untz a écrit :
> Le lundi 23 février 2009, à 22:01 +0100, Markus Koßmann a écrit :
> > Just updating factory I noticed that many gnome applications need a lot of
> > time for running several instances of /usr/bin/gconftool-2 with --makefile-
> > install-rule or --makefile-uninstall-rule arguments. in their install script.
> > Compiz installation comsumed over 5 minutes for doing that
> > Is this expected ?
>
> This is certainly not expected. I think it's because of this change in
> gconf2:
>
> Use "merged" for schema-install-source, for better performance.
After some discussion with Michael, and thanks to his input, I made some
changes to the gconf2 package which should solve the issue in most
cases:
+ we call gconftool-2 --makefile-install-rule only once per package
using gconf now, instead of multiple times. This should improve
things significantly for some packages.
(we still have to call gconftool-2 --makefile-uninstall-rule too)
+ if the schema file hasn't changed between the old and the new
package, we just skip this test. And since schema files don't change
that often, this is a huge win.
I just put the updated gconf2 package in GNOME:Factory, so it'd be great
to have people test GNOME:Factory to make sure it doesn't break anything.
I'm a bit hesitant to directly push it to openSUSE:Factory since it can
break stuff badly if I made a small mistake ;-) But we'll push it at
some point.
Note that to really experience the improvement, you'll need to update to
GNOME packages compiled with this new gconf. And then, on the following
updates, it will be much faster.
(the first update is still somewhat slow because the package you
currently have has the old %preun script which is not optimal)
Vincent
--
Les gens heureux ne sont pas pressés.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
----- End forwarded message -----
--
Les gens heureux ne sont pas pressés.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
> +Mon Feb 23 13:57:01 CET 2009 - vuntz(a)novell.com
> +
> +- Revert the use of %{libproxy_shnum}: there are places where the
> + macro cannot be used (%files, eg), and we want don't want to mix
> + libproxy0 and libproxy%{libproxy_shnum} -- too likely to forget
> + to update one of the two instances.
What do you mean it can't be used in the %files section? I have been packaging this lib for more than half a year with this and apparently everything
goes well? I even use this technique very often in
%files
%{_libdir}/%{name}.so.%{shnum}
as it allows to 'detect' immediately that the version is wrong, based on a wrong file blob.
Under what specific case does it not work in %files ?
Dominique
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
The openSUSE-GNOME Team is proud to announce its Hack Day Series for the
next two months. These events are designed to get the community
involved in the various processes that make everything hum so
wonderfully.
These events will be held bi-weekly on Thursdays, coinciding with our
regular weekly team meetings. They are all day events with a scheduled
coordinator monitoring the channel throughout the day. All hack days
will occur in the #opensuse-gnome channel on the Freenode Network. We
welcome everyone to join us. And don't be intimidated if you don't
think you know how to do certain tasks. There will be experts around to
guide you.
Below is our schedule: (Please note that topics of each hack day may
change as we get closer. For updated information, subscribe to
news.opensuse.org's calendar.)
26-February-2009
Wiki Hack Day
Cleaning up all -GNOME related pages on the openSUSE Wiki site. This
includes updating old pages, removing or adding pages, rearranging, etc.
I will be chairing this day.
12-March-2009
Spec File Day
Cleaning up our packages and ensuring consistency of our packages across
the board.
26-March-2009
GNOME:Stable Day
Upgrade all packages in GNOME:Stable repository to the latest stable
2.24 version.
09-April-2009
(To be determined)
23-April-2009
Patch from Upstream Day
By this date, GNOME 2.26.1 should be released and we'll update packages
in GNOME:Factory/Backports.
Looking forward to seeing you all there!
--
Bryen Yunashko
openSUSE Board Member
openSUSE-GNOME Team Member
GNOME-A11y Team Member
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Good afternoon,
I was just busy updating comix to the latest version in G:C and ran into an issue (works up to openSUSE 11.1, so I submitted the package, even though
it does not work on Factory for the moment).
the problem in short: comix BuildRequires: python-gtk and python-gtk apparently Requires python < 2.6, which is not available.
Is this a known problem? In a regular factory build we have python-gtk and apparently it does not require python < 2.6..
Looking forward for some fixes there :)
Dominique
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
On Sun, 2009-02-15 at 18:55 -0600, Bryen wrote:
> On Mon, 2009-02-16 at 10:41 +1100, Magnus Boman wrote:
> > Hello,
> >
> > I just had a look at our wiki page [1] and lots of stuff was really
> > outdated. We had "Report a bug" pointing to 10.3 etc. I think we really
> > need to have virtual teams that take responsible for the different
> > parts, such as wiki, packaging, testing, bug reporting etc.
> >
> > We currently do have a page for Team [2] and Directory [3]
> >
> > On the Directory [3] page, we list the following topics;
> >
> > * Accessibility
> > * Bug Tracking
> > * Packaging
> > * Meetings
> > * Helping Hands
> > * GNOME Repositories
> >
> > I think we need a wiki specific topic as well, and would like each and
> > everyone of you to add yourself to the topics of interest and where you
> > can help. We should then try to go through these topics once a month
> > (either during the normal meeting or as a separate meeting) to make sure
> > that we keep this up to date.
> > As I see it, people adding themselfs to the wiki topic would have a huge
> > task on their hand, checking pages to make sure they are current. It's
> > also a great way to contribute if you don't have coding skills etc.
> >
> > Opinions?
> >
> > Cheers,
> > Magnus
> >
> > [1] http://en.opensuse.org/GNOME
> > [2] http://en.opensuse.org/GNOME/Team
> > [3] http://en.opensuse.org/GNOME/Directory
> >
>
> Well, besides spelling "themselfs" when it should be "themselves", I
> think its a great idea. But reality is, it's always a challenge.
> Dividing up the work is a good approach if we all agree that we'll each
> consistently update our tasked pages.
>
> Bigger challenge still is to clean up the wiki overall. Reorganize
> pages as needed, remove pages as needed, etc.
>
> Perhaps we need to have a Wiki Hack Day soon to do this.
> --
> Bryen Yunashko
> openSUSE Board Member
>
I wouldn't know anything about this wiki cleanup...
Maybe yet another wiki meeting is in order and we can identify what
exactly needs polishing?
--
Christopher M. Hobbs, chobbs(a)siloamsprings.com
Network Administrator, City of Siloam Springs
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
It's time for our next openSUSE-GNOME Meeting in the IRC Channel
#opensuse-gnome on the Freenode network. This will be held at 22:00 UTC
on Thursday, February 18.
In this meeting, we will discuss Magnus's email discussing wiki cleanup
and possibly organizing a Wiki Hack Day. We'll also discuss other hack
fests as appropriate and needed, including bug squashing, etc.
We look forward to see you there!
--
Bryen Yunashko
openSUSE Board Member
GNOME-A11y Team Member
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Hi,
i was wondering where i could find specificly the icon theme used for the
latest openSUSE GNOME release?!
Is it Gilouche icon theme or Industrial, its called, im not sure?!.
is it part of the gnome-icon-theme or does the opensuse have a separate icon
package for that?
Preferably if a svn/cvs repository..
im not using opensuse as a distribution you see, but i like the artwork :)
best regards
/Nicklas / smurfd
ps please CC me if you reply
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Hello,
I just had a look at our wiki page [1] and lots of stuff was really
outdated. We had "Report a bug" pointing to 10.3 etc. I think we really
need to have virtual teams that take responsible for the different
parts, such as wiki, packaging, testing, bug reporting etc.
We currently do have a page for Team [2] and Directory [3]
On the Directory [3] page, we list the following topics;
* Accessibility
* Bug Tracking
* Packaging
* Meetings
* Helping Hands
* GNOME Repositories
I think we need a wiki specific topic as well, and would like each and
everyone of you to add yourself to the topics of interest and where you
can help. We should then try to go through these topics once a month
(either during the normal meeting or as a separate meeting) to make sure
that we keep this up to date.
As I see it, people adding themselfs to the wiki topic would have a huge
task on their hand, checking pages to make sure they are current. It's
also a great way to contribute if you don't have coding skills etc.
Opinions?
Cheers,
Magnus
[1] http://en.opensuse.org/GNOME
[2] http://en.opensuse.org/GNOME/Team
[3] http://en.opensuse.org/GNOME/Directory
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org