Mailinglist Archive: opensuse-factory (379 mails)

[Marcus Meissner <meissner@xxxxxxx>]

On Fri, Apr 01, 2011 at 05:47:38PM -0400, Greg Freemyer wrote:
> On Fri, Apr 1, 2011 at 4:49 PM, Greg KH <gregkh@xxxxxxx> wrote:
> > On Fri, Apr 01, 2011 at 12:22:16PM -0400, Greg Freemyer wrote:
> > > All,
> > >
> > > Is there a simple way security updates can be tested to install
> > > cleanly on a Tumbleweed system?
> > >
> > > Can we make that part of the process somehow?
> >
> > No, that's not up to the security or maintance people, that's up to the
> > tumbleweed developers.
> >
> > > == details
> > >
> > > I just tried to do a YOU, but I get a conflict that a typical user
> > > should not have to face just because they're using Tumbleweed:
> >
> > What's a "YOU"?
>
> Yast Online Update
>
> It's the normal security update process that all users should use.
>
> ie. Hopefully everybody is pulling / installing security updates.
>
> I typically pull security updates by typing "you" at the command-line
> when I get the urge.

It was a bugfix update though.

> I don't think the typical opensuse user knows virtualbox has to be
> compiled for a specific kernel.
>
> And I assume the goal is for the "typical tumbleweed user" to be
> similar to the typical opensuse user.
>
> Also, normally when there is a package conflict and one of the choices
> will break a package (or more), then the choices the user gets to
> select from explicitly say that.  In this case, the choices don't make
> that clear.

I still think that you need to have a certain level of knowledge
to try Tumbleweed though, and this includes resolving of such minor conflicts.

Ciao, Marcus
-- 
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx