Mailinglist Archive: opensuse-gnome (69 mails)

[Magnus Boman <captain.magnus@xxxxxxxxx>]

Thu, 2009-03-19 at 18:07 +0100, Vincent Untz wrote:
> Hi all,

Hello!

<- SNIP -> 
> osc gnome news
> ==============
>
> While waiting for GNOME 2.26.0 to build (locally in my jhbuild, and in
> the build service for packages), I worked a bit on osc gnome to bring
> two new things:
>
>  + the first one is self-explanatory:
>    osc gnome todo --project GNOME:STABLE:2.24
>    Yes. We can use osc gnome with GNOME:STABLE!
>    For now, the todo command will only list packages that are part of
>    the official GNOME release. If we want to update other packages,
>    it's possible with some small work.
>
>  + the second one is that osc gnome is now completely independent from
>    oS:F and G:F: those projects are not used anywhere anymore in the
>    code (except for the default values, which people can easily
change).
>    This means the plugin is getting more and more ready to conquer the
>    world ;-)

This is great news. I was a bit concerned about the amount of work OBS
had to do before finally building 2.26 for us, but seeing this, it was
actually a good thing :-)

> It's all in the git repo right now, and if it works fine after a few
> days, I'll update the osc-plugins-gnome package in openSUSE:Tools.
>
> Note that I need to change a bit the way reservations work so that
they
> are per-project. Right now, if you reserve gnome-panel in G:F, it will
> also mark it as reserved in G:S:2.24, which is obviously wrong. I'll
fix
> this before next week (I might have time for it tonight)
>
> GNOME:STABLE
> ============
>
> With osc gnome working with GNOME:STABLE, it's now possible to easily
> update everything that needs to be updated in GNOME:STABLE.
>
> There are some questions to discuss (the meeting sounds like a good
time
> for that):
>
>  + creation of G:S:2.26: when? And when it's created, should we move
G:F
>    to 2.27?

G:S:2.26 already exists. Once we update the last couple of packages in
G:F, I will copy everything over to G:S:2.26.
Once the copy is complete, I think we should start updating G:F straight
away. We should, however, not forward those changes to oS:F for a week,
so that people who follows Factory have a chance to update.

>  + what kind of package updates go in. I think it doesn't make sense
to
>    do work on cleaning the packaging (this is something that should be
>    done in G:F) unless it fixes a bug. So I propose to only package
new
>    upstream versions, or add patches to fix bugs.

Agreed. It makes no sense to continue to clean up packages in G:S at
all. We should only update when official GNOME tarballs comes through,
and if there are any specific request from the public to add a patch (or
fix something trivial)

>  + handling of security issues: if there's a security update for 11.1,
>    we need to make sure the relevant patch also appears in G:S. How
can
>    we do this?

Good question! ATM, Marcus Meissner (sorry, not sure how to spell his
name) notifies people in Contrib if security updates are needed. Perhaps
we can have a talk to him to notify us as well? Other possibilities is
to monitor 11.1:Updates via a script and if packages are updated there,
we need to have a look. Other ideas are welcome.

Cheers,
Magnus


-- 
To unsubscribe, e-mail: opensuse-gnome+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-gnome+help@xxxxxxxxxxxx