Rajko M. wrote:
On Sunday 02 September 2007 08:37, jdd wrote:
the point is an update of the data is necessary only when Yast install
don't find on the server the package it looks for.
YaST doesn't browse server to see what is there, or ask for
and when it can't find it than update local dat
On Sunday 02 September 2007 08:37, jdd wrote:
> the point is an update of the data is necessary only when Yast install
> don't find on the server the package it looks for.
YaST doesn't browse server to see what is there, or ask for
and when it can't find it than update local database. If there
Andreas Jaeger wrote:
Can't a system be designed to at least give
the user the illusion that it is going faster?
the point is an update of the data is necessary only when Yast install
don't find on the server the package it looks for.
you could then add the "refresh" option on the error me
On Sunday 02 September 2007 11:14:41 am John Layt wrote:
> Not sure if this is your problem, but in Yast in Software Repositories, you
> can turn off Auto Update for the repositories, this is what forces zypper
> to re-download the full repo listing from the server everytime you so much
> as breath
On Sunday 02 September 2007 04:14, John Layt wrote:
> I've used every other major package management system out there, and I
> don't recall any of them being so slow, not even urpmi.
> patience as it is under heavy development, but it had better improve by the
> RC's.
Better no rush.
One of
"Robert Lewis" <[EMAIL PROTECTED]> writes:
> Why is it necessary to build a new database of
> patches every time I choose another YaST
> s/w function?
>
> The delays waiting to update or pick a new
> package are quite a time hit.
>
> Even if these processes just completed and
> I leave YaST an re-
On Saturday 01 September 2007, Robert Lewis wrote:
> Why is it necessary to build a new database of
> patches every time I choose another YaST
> s/w function?
>
> The delays waiting to update or pick a new
> package are quite a time hit.
>
> Even if these processes just completed and
> I leave YaST
On Sunday 02 September 2007, Robert Lewis wrote:
> This window is not movable and obscures other ICONS.
If you single click on the window (well popup really) it goes away but it
carries on working in the background. Double click the system tray icon to
show the status again.
> When it finishes
On Saturday 01 September 2007 18:27, Robert Lewis wrote:
...
> When it finishes the Blue icon has a big question mark
> that says: "Unable to check whether upgrades are available".
> Is this expected behavior for the beta?
>
> Also, if I click on: "Online Update" in YaST I get back:
> "No Active Up
On 9/1/07, Rajko M. <[EMAIL PROTECTED]> wrote:
> On Saturday 01 September 2007 17:46, Robert Lewis wrote:
> ...
> > Is it normal with 10.3 Beta 2 for the little blue ICON in the bottom right
> > to always say: " Unable to check whether updates are available" ?
>
> I'm not sure is there any bug, but
On 9/1/07, Robert Lewis <[EMAIL PROTECTED]> wrote:
> On 9/1/07, Rajko M. <[EMAIL PROTECTED]> wrote:
> > On Saturday 01 September 2007 14:58, Robert Lewis wrote:
> > > Why is it necessary to build a new database of
> > > patches every time I choose another YaST
> > > s/w function?
> > >
> > > The de
On Saturday 01 September 2007 17:46, Robert Lewis wrote:
...
> Is it normal with 10.3 Beta 2 for the little blue ICON in the bottom right
> to always say: " Unable to check whether updates are available" ?
I'm not sure is there any bug, but it means that it can't access the update
repository. Try
On 9/1/07, Rajko M. <[EMAIL PROTECTED]> wrote:
> On Saturday 01 September 2007 14:58, Robert Lewis wrote:
> > Why is it necessary to build a new database of
> > patches every time I choose another YaST
> > s/w function?
> >
> > The delays waiting to update or pick a new
> > package are quite a time
On Saturday 01 September 2007 14:58, Robert Lewis wrote:
> Why is it necessary to build a new database of
> patches every time I choose another YaST
> s/w function?
>
> The delays waiting to update or pick a new
> package are quite a time hit.
>
> Even if these processes just completed and
> I leav
Why is it necessary to build a new database of
patches every time I choose another YaST
s/w function?
The delays waiting to update or pick a new
package are quite a time hit.
Even if these processes just completed and
I leave YaST an re-enter I have to wait again
a very long time before I can cho
15 matches
Mail list logo
