Hey everyone,
Scott (sreeves) and I have been looking at re-organizing some of the GNOME-related content in the openSUSE wiki. We're hoping to have a concrete proposal ready for Thursday. Until then, please go read the draft proposal. We'd love as much feedback as possible.
http://en.opensuse.org/GNOME/Wiki_Layout
Feel free to comment back to this mailing list or the Wiki_Layout's "discussion" page.
Thanks,
-Boyd
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Hallo.
I would like to propose two new repositories:
multimedia:codec for libraries and similar infrastructure for multimedia
formats.
Examples of packages:
libogg, libvorbis, libdvdnav, libdvdread, libsidplay, wavpack,...
multimedia:gstreamer010 or GNOME:GSTREAMER010 or so (exact case and name
is not sure):
Move gstreamer packages from GNOME:*STABLE here. This project will be
build against multimedia:codec repository to have the latest codecs.
--
Best Regards / S pozdravem,
Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz
Lihovarská 1060/12 tel: +420 284 028 966
190 00 Praha 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
JP Rosevear wrote:
> On Thu, 2007-09-20 at 14:10 +0200, Stanislav Brabec wrote:
> > Hallo.
> >
> > I would like to propose two new repositories:
> >
> > multimedia:codec for libraries and similar infrastructure for multimedia
> > formats.
> > Examples of packages:
> > libogg, libvorbis, libdvdnav, libdvdread, libsidplay, wavpack,...
> >
> > multimedia:gstreamer010 or GNOME:GSTREAMER010 or so (exact case and name
> > is not sure):
> > Move gstreamer packages from GNOME:*STABLE here. This project will be
> > build against multimedia:codec repository to have the latest codecs.
>
> I don't see a particular reason to fragment repositories, our goal
> should be fewer, larger repositories that are available to regular end
> users at large to reduce confusion (ala metaverse).
I see:
Packages like wavpack, avifile, libexif, nvtv, (but also e. g.
pilot-link, libgadu, meanwhile, gphoto) have no relation with GNOME. But
we have them in GNOME:* to be able to compile multimedia packages and
gstreamer for older distros.
Having a repository, where all codecs can be in the latest version would
be a better solution.
Having one package in more repositories is sub-optimal as well.
--
Best Regards / S pozdravem,
Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz
Lihovarská 1060/12 tel: +420 284 028 966
190 00 Praha 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
When I use 'cairo_text_path', I found that it cost too much time at the first running, even more than 3 seconds.
My version is 1.0.2 in sled10-sp1.
I don't know what can I do to make it faster.
Can anyone give me some suggestions?
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
I just performed a Beta2 install from the Gnome CD and ended up with a
mess of an install. I allowed the option in the install to pre-connect
to the online repository and I think that's what caused the problem.
The Factory online repository is a moving target and there were a number
of packages that required different versions of libraries etc.
All of that explanation so I could propose this....
Can we get online repositories that are snapshots of the Beta releases?
I was so excited to have an install that was on a single install and
would pull packages from online only to find it was almost useless. I
understand that once we release this may not happen, but we can't even
test it right now because we the default online repository is factory.
One other thing I've noticed, when I am installed and connected to the
online repository, the time taken to load up the "Software Management"
tool in Yast is completely unacceptable. I don't know exactly what is
going on there, but I see messages about a cache being cleared out, lots
of xml files coming down, rebuilding RPM lists, etc. I'll file a bug
about what I'm seeing but I though I would discuss it here first.
-Calvin
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
I use sled sp1 and gnome. I am trying to upgrade my install of
libgnomecanvas 2.12 to 2.14 using the opensuse gnome:stable repo.
Everytime i install 2.14 version, it messes-up gmd so i can not login.
Has anyone gone to 2.14 from 2.12 successfully? If so, please share
exactly what you had to do.
Chris
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Chris Arnold wrote:
> James Ogley wrote:
>
>>> Wrong, notice the link:
>>> http://download.opensuse.org/repositories/GNOME:/STABLE/_*SUSE_Linux_10.1*_…
>>>
>>>
>> Yes, which is different to SLED which is what you said you were using.
>>
>>
> SLED is based on Suse 10 and 10.1; i have used other packages that are
> 10.1 rpm's and they work fine. I got tired of some saying 10 and others
> saying 10 and 10.1 so i called novell and used some of my support; they
> too say it is based on 10 and 10.1. So this package should work. If this
> isn't the package then where is the SLED rpm of libgnomecanvas 2.14?
>
>
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Dear lovers of reduced entomology,
There has been a bunch of discussion about the bug status of GNOME in
openSUSE. Some people say it is buggier than the cockroach nest which I
found two days ago in my cupboard. It's not that bad, but close.
Anyway --- we want to build a list of the bugs which annoy the most
people, so that we can fix those first. Rodrigo Moya and myself have
been talking of how to do this.
There are several ways to do this:
- By counting the "votes" in Bugzilla. If you look very closely in bug
pages (or use the high technology available in Edit/Find), you'll see a
"Vote for this bug" field. This hasn't been used very much in bugs for
openSUSE 10.3, while there is some interesting info in 10.2 (e.g. the
most-voted bug of all in 10.2 is
https://bugzilla.novell.com/show_bug.cgi?id=222490 - Nautilus uses 100%
CPU; we have a patch, which I'll take care of putting into a package for
10.2 soon).
- By looking at the bugs with the highest number of duplicates. No idea
about this yet.
- By looking at bugs with the largest CC list. I don't know if people
really take the trouble of looking for bugs before (re)filing them, so
this may not give out meaningful info.
- Bug severities / priorities, of course.
[An interesting bit of literature is
http://www.joelonsoftware.com/articles/fog0000000014.html for those
interested.]
So, here is a
CALL FOR HELP
* Please vote for bugs in Bugzilla. Vote for bugs that happen to *you*,
not for bugs which you don't get but which you think may be important.
* Please make sure that you are in the CC list for relevant bugs which
have already been filed (or just file the bug again; the elves will take
care of marking it as a duplicate).
Rodrigo and myself will probably publish a list of "hot bugs" soon.
Thanks!
Federico
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Hello all,
This is the plan for integration of the GNOME 2.20 release into
factory/10.3.
As you know, the GNOME-2.20 release date is Wednesday, September 19.
These updates will clearly not make RC1 but they will make it in for RC2
and/or the final build of 10.3.
The upstream GNOME tarballs, however, are due on Monday, September 17.
Which means the GNOME packaging team at Novell will be starting to
submit the updates to factory next Monday, and will declare it finished
on Wednesday.
Keep in mind that GNOME-2.20 has been in hard code freeze since
September 10 with only a few code changes approved by the release team
since then. These updates will largely be no-ops (just a version bump)
and translation or doc updates.
This is the plan:
We have the package list here:
http://spreadsheets0.google.com/ccc?key=pXWjzV1g7sCqH0NY9PgddOg&hl=en_GB
It is a public doc, editable by the SUSE team.
sbrabec will start early in Prague, followed by mw, mauropm and myself
in the US. We will update spreadsheet to indicate that a package is
being worked on, and then mark it as updated once submitted to our
internal build system. We may even solicit some help from other well
known packaging superstars such as jpr, coolo, etc.
We will be taking the tarballs from upstream as they are submitted by
the maintainers to the FTP tree; grabbing them from here, as that's
where they show up the quickest:
http://ftp.acc.umu.se/pub/gnome/sources/
Internal administrivia:
When you build packages place them in $HOME/Export/yyyy/mmdd/arch so
others building packages can pull them into the $BUILD_ROOT with
--prefer-rpms
We're all looking forward to a great 10.3!
Cheers.
-los paqueteros (mw,mauropm, gekker)
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
It would be great if some could tag any gnome related packages in the
build service with the 'gnome' tag so they can be found more easily via
the tag cloud (for instance G:S, G:U and G:C have none or almost no
packages tagged, although the repo itself is).
-JP
--
JP Rosevear <jpr(a)novell.com>
Novell, Inc.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org