On 6 June 2011 03:57, Rahul Sundaram wrote:
> It really isn't. It is just a workaround that produces inconsistent
> behaviour for reasons that are not clear or documented. The right fix
> would be to find out why yum doesn't work off the cache when told to and
> solve that problem but this worka
On 06/02/2011 05:19 PM, Chris Tyler wrote:
> On Thu, 2011-06-02 at 12:39 +0100, Richard Hughes wrote:
>>
>> This is by design. I lost count of the number of bugs opened against
>> PackageKit-command-not-found where yum would happily go and download
>> the latest metadata and take 3 minutes to ret
On Thu, 2011-06-02 at 16:09 +0200, Eric Tanguy wrote:
> Le 02/06/2011 15:30, Eric Tanguy a écrit :
> > Le 02/06/2011 13:12, Michael Schwendt a écrit :
> >> On Thu, 02 Jun 2011 11:43:19 +0200, ET wrote:
> >>
> >>> I tried uninstall and reinstall PackageKit-command-not-found with the
> >>> same resul
Le 02/06/2011 15:30, Eric Tanguy a écrit :
> Le 02/06/2011 13:12, Michael Schwendt a écrit :
>> On Thu, 02 Jun 2011 11:43:19 +0200, ET wrote:
>>
>>> I tried uninstall and reinstall PackageKit-command-not-found with the
>>> same result.
>>> Maybe a x86_64 problem ?
>> No. Don't just reinstall a pack
Le 02/06/2011 13:12, Michael Schwendt a écrit :
> On Thu, 02 Jun 2011 11:43:19 +0200, ET wrote:
>
>> I tried uninstall and reinstall PackageKit-command-not-found with the
>> same result.
>> Maybe a x86_64 problem ?
> No. Don't just reinstall a package if it isn't broken.
> Try to examine the proble
On Thu, 2011-06-02 at 12:39 +0100, Richard Hughes wrote:
> On 2 June 2011 12:35, Chris Tyler wrote:
> > - If pk-c-n-f times out on fetching file list metadata, it seems to
> > silently stop trying to suggest packages. I've seen this on slow
> > connections and disconnected machines. IIRC, fetching
On 2 June 2011 12:35, Chris Tyler wrote:
> - If pk-c-n-f times out on fetching file list metadata, it seems to
> silently stop trying to suggest packages. I've seen this on slow
> connections and disconnected machines. IIRC, fetching recent metadata
> (e.g., by using yum to find a file-level depen
On Thu, 2011-06-02 at 11:43 +0200, Eric Tanguy wrote:
> I tried uninstall and reinstall PackageKit-command-not-found with the
> same result.
> Maybe a x86_64 problem ?
> Eric
>
Two observations:
- If Packagekit-command-not-found is active, the error message seems to
change from:
bash: thun
On Thu, 02 Jun 2011 11:43:19 +0200, ET wrote:
> I tried uninstall and reinstall PackageKit-command-not-found with the
> same result.
> Maybe a x86_64 problem ?
No. Don't just reinstall a package if it isn't broken.
Try to examine the problem a bit. Everything's there for
you to look at.
$ rpm -
Le 02/06/2011 11:36, Joachim Backes a écrit :
> On 06/02/2011 11:30 AM, Eric Tanguy wrote:
>> Le 02/06/2011 11:25, Joachim Backes a écrit :
>>> On 06/02/2011 11:19 AM, Eric Tanguy wrote:
In fedora14 in cli if i try an unknown command the system tried to
find
the package containing t
On 06/02/2011 11:30 AM, Eric Tanguy wrote:
Le 02/06/2011 11:25, Joachim Backes a écrit :
On 06/02/2011 11:19 AM, Eric Tanguy wrote:
In fedora14 in cli if i try an unknown command the system tried to find
the package containing this command.
This seems to not work in f15.
# telnet
bash: telnet:
Le 02/06/2011 11:25, Joachim Backes a écrit :
> On 06/02/2011 11:19 AM, Eric Tanguy wrote:
>> In fedora14 in cli if i try an unknown command the system tried to find
>> the package containing this command.
>> This seems to not work in f15.
>> # telnet
>> bash: telnet: command not found...
>>
>> and
On 06/02/2011 11:19 AM, Eric Tanguy wrote:
In fedora14 in cli if i try an unknown command the system tried to find
the package containing this command.
This seems to not work in f15.
# telnet
bash: telnet: command not found...
and that's all. The system does not propose to install telnet client
13 matches
Mail list logo
