Hi,
after some reorganizations of GNOME: namespace, I noticed, that some
GNOME:Apps does not build since some time:
- no gimp
- no inkscape
xsane publishing is blocked by above.
Before, I fetched the current gnome stuff from Factory, but after the reorg,
zypper dup wants to downgrade all those packages, because of the build
failures in question.
It would be very nice, if somebody would give this repo some love and
complete the transition.
Thanks,
Pete
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Hey,
So in case you don't want to work on factory stuff or you don't like
cleaning BuildRequires/Requires, there's something else you can do!
We're planning to release GNOME 2.28.2 as a maintenance update for 11.2
(see the previous thread on this topic). While 2.28.2 is not out yet, we
can still start updating quite a few package from 2.28.1 in
GNOME:STABLE:2.28.
You can get a first list with:
osc collab --project GNOME:STABLE:2.28 todo
(install the osc-plugin-collab from openSUSE:Tools if you don't have it
already)
Most of those updates should be easy to handle. It is really important
to make sure to list the changes from upstream (which are usually listed
in the NEWS file), so that we can review the changes and decide this new
version is suitable for the maintenance update. You can just look at how
previous .changes entries are formatted to get an idea on how to do it.
Oh, and if you don't know osc collab, this line will do most of the
magic for you:
osc collab --project GNOME:STABLE:2.28 update $package
(where $package can be gnome-keyring, for example)
People in #opensuse-gnome will be glad to get you started, I'm sure :-)
Thanks,
Vincent
--
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
Hi,
Andreas has started working on cleaning up some packages so that they
don't uselessly BuildRequires or Requires a deprecated library. We don't
have a good list of such libraries, but on the top of my head, I can
list: libgnome, libgnomeui, gnome-vfs, libgnomeprint, libgnomeprintui,
libglade, hal, PolicyKit 0.8, libbonobo, libbonoboui. I'm using upstream
module names here, so beware: package names might be a bit different ;-)
(Note that hal is being replaced with the "DeviceKit effort" -- which is
slowly being renamed to the "udev effort"...)
To make a long story short: we need help to do all this work. You'll
find a few different cases:
+ a package uselessly BuildRequires, say, libgnome-devel, but doesn't
need it. You can simply remove the BuildRequires.
+ a package can be compile with both a deprecated API (gnome-vfs) and
the new API (gio, part of glib). In this case, often, we just don't
need to keep the gnome-vfs dependency.
+ sometimes, there are cases where we might want to keep this. I think
an example could be gstreamer-0_10-plugins-base, where it might make
sense to keep the gnome-vfs plugin. In such a case, we should
probably split the packge so that the gnome-vfs plugin is in a
specific subpackage, that won't get installed by default.
Note that having a package compile even after you removed a
BuildRequires doesn't mean you did the right thing. For example, a
package might BuildRequires both libgnomeui-devel and libbonoboui-devel.
If you remove libgnomeui-devel, it will still compile because
libbonoboui-devel brings libgnomeui-devel in. The right thing to do
anyway is to make sure the package doesn't need libgnomeui-devel (you
can usually check this by looking at the configure.in or configure.ac
file of the tarball).
Also, sometimes, removing the build dependency will remove a feature. If
it's an important feature, we prefer to keep the build dependency.
And if you're feeling brave, you can even write patches for the packages
(and send them upstream!) to get rid of those dependencies!
Below you can find a first list of packages that still depend on
gnome-vfs or libgnomeui, compiled by Andreas (thanks Andreas!). This is
a good place to start.
If you have any question, just join #opensuse-gnome on irc :-)
Vincent
----- Forwarded message from Andreas Jaeger -----
Date: Thu, 10 Dec 2009 16:14:30 +0100
From: Andreas Jaeger
To: Vincent Untz
Subject: gnome-vfs2-devel and libgnomeui-devel requires
Hi Vincent,
here's what grep showed me for factory. I just fixed twitux and will tackle
libgweather now,
Andreas
gnome-vfs2-devel - BuildRequires
================================
abiword
banshee-1
dice
gnome-vfsmm
gobby04
gstreamer-0_10-plugins-base
inkscape
libgnome
raw-thumbnailer
gnome-vfs2-devel - Requires
===========================
abiword
banshee-1
evolution-data-server
gnome-vfsmm
libgda3
libgda
libgnome
libgnomeui
libgweather
planner
libgnomeui-devel - BuildRequires
================================
balsa
conglomerate
dasher
dia
eiciel
f-spot
gDesklets
ghex
glabels
glade3
gnome-commander
gnome-docker
gnome-main-menu
gnome-netspeed-applet
gnome-panel
gnome-presence-applet
gnome-spell2
gnucash
grip
gtetrinet
gthumb
gtkam
gtktalog
gurlchecker
gwget
libgail-gnome
libgnomeuimm
memprof
nautilus-cd-burner
planner
pybliographer
python-gnome
twitux
xchat-gnome
compiz
eclipse
eID-belgium
etherape
gjiten
graphviz
gtkpod
gwc
icewm
ifolder3
jack-rack
mdbtools
MozillaFirefox
MozillaSunbird
MozillaThunderbird
mozilla-xulrunner191
multisync-gui
novell-ifolder-client-plugins
padevchooser
pythoncad
python-gnome-extras
scim
seamonkey
stardict
thinclient-greeter
thinclient-settings
thinclient-users
tsclient
uim
libgnomeui-devel - Requires
===========================
evolution
gedit
gnome-panel
gnome-pilot
gnucash
gok
gtkhtml2
libgnomeuimm
--
Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org}
Twitter: jaegerandi | Identica: jaegerandi
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
----- 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
Hi,
(please follow-up on opensuse-gnome, unless you have a cross-desktop
point)
People have been working on a new accessibility stack based on dbus for
the past few months, and even though we had preliminary packages in
11.2, it was not really ready for real-world testing. We're reaching
this point today. I opened a feature [1] to track this.
The goal of doing this change now is to test this new stack, and help us
decide if we want to use it in 11.3, or not. This should also help
upstream find and fix bugs in the new stack.
But for this to really work, we need help from people.
How can I help?
===============
If you know accessibility, you can certainly help. You'll need factory
(or a development version of 11.3), and you'll need to make sure the new
stack is installed. And then, just try some accessibility features to
see what works, what doesn't work, etc.
If you don't know accessibility, just join the GNOME accessibility
effort: people will help you start. They have a good wiki page [2] that
is the first place you should look.
How can I have the new stack?
=============================
Make sure at-spi2-core is installed. If you have gtk2, you should
automatically get at-spi2-atk too. That's all. You're done.
How can I switch to the old stack?
==================================
Both stacks are parallel-installable. To use the old stack, you simply
need the at-spi package, and you should set the
/desktop/gnome/interface/at-spi-corba gconf key to true.
While the two stacks are parallel-installable, I'm unsure that using the
old one when the new one is installed works (it should, but there might
be bugs). If this is the case, you can remove the old stack. But please
file a bug too.
Why a new stack?
================
The rewrite of the stack was triggered by technical reasons (moving away
from corba to dbus). So the goal is not to propose new features, or to
remove anything. But there'll probably be regressions.
This rewrite should also help KDE share the same infrastructure; I think
this is still something being worked on, though (someone else might be
better informed).
What changes?
=============
For people not using accessibility, nothing should change.
For people using accessibility:
- you should be able to use orca and accerciser in the very same way
- I believe the magnifier and the on-screen keyboard will not work fine
(gnome-mag and gok). I'm actually not sure we can make them work with
the new stack, so maybe we'll have to switch back because of this
- accessibility of bonobo objects (that's mainly panel applets at this
point) will likely be broken.
Vincent
[1] https://features.opensuse.org/308451
[2] http://live.gnome.org/Accessibility
--
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
openSUSE 11.1, Compiz 0.8.4-167, GNOME 2.28.0 (?)
Once upon a time I could adjust a windows transparency my having my
mouse over that window and while holding down the Super key scrolling
the wheel up and down. That stopped working sometime during 11.1. Now
I've gone looking for how to enable that and can't seem to find any
relevant configuration dialog. I'd assume it is in "CompizConfig
Setting Manager" but I can't find it [that thing has so many layers it
gives me the KDE creeps! :)]
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Hi all,
As some of you probably saw, the KDE team is going to release a version
upgrade of KDE as a maintenance update:
http://lists.opensuse.org/opensuse-announce/2009-12/msg00002.html
Magnus noticed the discussion when it was still on the maintenance
mailing list, and we started considering the option of doing the same
for GNOME. A good candidate would be GNOME 2.28.2, which is due next
week.
It would certainly fix many bugs that are reported in bugzilla as of
today. Of course, doing this will take some time (we need to update the
packages, and then test all that), so it wouldn't happen before at least
a few weeks.
How do people feel about this?
Vincent
--
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
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Since I tried 11.2 M6, up to current GM, the gnome screensaver does not set my display to sleep.
In Screensaver preferences, I have set "regard the computer as iddle after 12 minutes", and in power
management preferences, I have "put display to sleep after 5 minutes".
It doesn't work.
Where do I look? Is it a known bug? A configuration issue somewhere?
- --
Cheers / Saludos,
Carlos E. R.
(from 11.2-ex-factory "Emerald" GM)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkr+uVsACgkQU92UU+smfQVEHgCcDWFHxb2tm7UpYXluayixyl2V
dQUAnRIFzxgunD29PZPPiUEPkbTj9zZY
=TSC5
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org