There is a well-discused bug on bugzilla:
https://bugzilla.novell.com/show_bug.cgi?id=216097 about
opensuse-updater.
I posted some idea of resolving this, which I find quite fine. You can
find this in comment #57:
https://bugzilla.novell.com/show_bug.cgi?id=216097#c57
Could some developer focus o
Den Monday 02 July 2007 22:12:01 skrev Rafał Miłecki:
> Could some
> developer focus on this bug before publishing 10.3? It wouldn't be nice to
> remove ZMD and don't give any alternative wayof watching repositories for
> updates of _any_ kind (not these securityones only).
I think Duncan stated t
-On 02/07/07, Rafał Miłecki <[EMAIL PROTECTED]> wrote:
There is a well-discused bug on bugzilla:
https://bugzilla.novell.com/show_bug.cgi?id=216097 about
opensuse-updater.
I posted some idea of resolving this, which I find quite fine. You can
find this in comment #57:
https://bugzilla.novell.com
Hi Benji,
On Monday 02 July 2007 15:51, Benji Weber wrote:
> It may be we need 3 policies:
>
> - Updates only (as default now)
This is important for every user, and leaves system stable.
> - Updates and version upgrades from same vendor as installed package
> (e.g. if you install xine from pack
* Benji Weber <[EMAIL PROTECTED]> [Jul 02. 2007 22:51]:
>
> There are also other things to be decided, like how to resolve package
> vendor "bouncing" where the user has e.g. guru & kde-backports
> repositories subscribed and the updater first updates to one then the
> other version of amarok, gai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Tuesday 2007-07-03 at 09:06 +0200, Klaus Kaempf wrote:
...
> There might be even another approach - updating by repository.
Why not "find out what is updatable and show a list where I can choose
from? Ie, a selection to choose aside from "secu
* Carlos E. R. <[EMAIL PROTECTED]> [Jul 03. 2007 11:32]:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> The Tuesday 2007-07-03 at 09:06 +0200, Klaus Kaempf wrote:
>
> ...
>
> > There might be even another approach - updating by repository.
>
> Why not "find out what is updatable and s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Tuesday 2007-07-03 at 13:48 +0200, Klaus Kaempf wrote:
> > > There might be even another approach - updating by repository.
> >
> > Why not "find out what is updatable and show a list where I can choose
> > from? Ie, a selection to choose aside
Klaus Kaempf escribió:
> * Carlos E. R. <[EMAIL PROTECTED]> [Jul 03. 2007 11:32]:
>>> There might be even another approach - updating by repository.
>> Why not "find out what is updatable and show a list where I can choose
>> from? Ie, a selection to choose aside from "security patches only / all"
On Wednesday 04 July 2007 02:43:02 wrote Carlos E. R.:
> The Tuesday 2007-07-03 at 13:48 +0200, Klaus Kaempf wrote:
> > > > There might be even another approach - updating by repository.
> > >
> > > Why not "find out what is updatable and show a list where I can choose
> > > from? Ie, a selection t
* Adrian Schröter <[EMAIL PROTECTED]> [Jul 04. 2007 09:37]:
> On Wednesday 04 July 2007 02:43:02 wrote Carlos E. R.:
> >
> > Ahhh... oops, right. Mmm... Then, show what is updatable for each repo,
> > perhaps show a list by repo?
>
> I would like to avoid user confusing by showing a large numbers
* Gabriel <[EMAIL PROTECTED]> [Jul 04. 2007 02:51]:
> Klaus Kaempf escribió:
> > * Carlos E. R. <[EMAIL PROTECTED]> [Jul 03. 2007 11:32]:
> >>> There might be even another approach - updating by repository.
> >> Why not "find out what is updatable and show a list where I can choose
> >> from? Ie,
Klaus Kaempf escribió:
> * Gabriel <[EMAIL PROTECTED]> [Jul 04. 2007 02:51]:
>> Klaus Kaempf escribió:
>>> * Carlos E. R. <[EMAIL PROTECTED]> [Jul 03. 2007 11:32]:
> There might be even another approach - updating by repository.
Why not "find out what is updatable and show a list where I c
On 04/07/07, Gabriel <[EMAIL PROTECTED]> wrote:
It seems that smart is capable of manage it.
You can have a look at the source to see what is doing.
Smart handles this quite badly, it just blindly upgrades to newer
versioned packages regardless of the vendor/repository.
_
Benjamin Weber
--
Benji Weber escribió:
> Smart handles this quite badly, it just blindly upgrades to newer
> versioned packages regardless of the vendor/repository.
>
Yup, smart is no model of good behaviuor in this case...and better not
to talk about the mess it produces in 64 bit systems..;-)
signature.asc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benji Weber schreef:
> On 04/07/07, Gabriel <[EMAIL PROTECTED]> wrote:
>> It seems that smart is capable of manage it.
>> You can have a look at the source to see what is doing.
>
> Smart handles this quite badly, it just blindly upgrades to newer
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Wednesday 2007-07-04 at 10:45 +0200, Klaus Kaempf wrote:
> * Adrian Schröter <[EMAIL PROTECTED]> [Jul 04. 2007 09:37]:
> > On Wednesday 04 July 2007 02:43:02 wrote Carlos E. R.:
> > >
> > > Ahhh... oops, right. Mmm... Then, show what is updatable
2007/7/4, Carlos E. R. <[EMAIL PROTECTED]>:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Wednesday 2007-07-04 at 10:45 +0200, Klaus Kaempf wrote:
> * Adrian Schröter <[EMAIL PROTECTED]> [Jul 04. 2007 09:37]:
> > On Wednesday 04 July 2007 02:43:02 wrote Carlos E. R.:
> > >
> > > Ahhh... oo
On Wednesday 04 July 2007 13:23, Rafał Miłecki wrote:
> 2007/7/4, Carlos E. R. <[EMAIL PROTECTED]>:
> > Anyway, I suppose that if the user has activated a dozen repos, he must
> > be prepared for some confussion, but he surely must be interested in
> > knowing what is new from all, sorted some
Have one question: there is for ex. freetype in my system installed as
RPM. Does YaST know where from is this RPM installed
(DVD/update/packman/etc.)?
--
Rafał Miłecki
* Rafał Miłecki <[EMAIL PROTECTED]> [Jul 05. 2007 13:13]:
> Have one question: there is for ex. freetype in my system installed as
> RPM. Does YaST know where from is this RPM installed
> (DVD/update/packman/etc.)?
No, not in openSUSE 10.2
We are working on a solution, though.
Klaus
On Wednesday 04 July 2007 20:23:20 Rafał Miłecki wrote:
> Method of managing updates is hard to create but is also hightly
> needed. Lack of updaing applications from 3rd party repositories may
> be really dangerous.
Don't mix upgrading with updating. Guru and packman just upgrade the packages.
T
2007/7/5, Duncan Mac-Vicar Prett <[EMAIL PROTECTED]>:
On Wednesday 04 July 2007 20:23:20 Rafał Miłecki wrote:
> Method of managing updates is hard to create but is also hightly
> needed. Lack of updaing applications from 3rd party repositories may
> be really dangerous.
Don't mix upgrading with
23 matches
Mail list logo
