xindy: command not found...
Failed to search for file: repo_add_solv() has failed.
This should offer to install the texlive-xindy package.
--
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to us
On Sat, 18 Apr 2020 at 23:45, Hiisi wrote:
> On Sat, Apr 18, 2020 at 12:44 PM Samuel Sieb wrote:
> >
>
> > Are you sure that's a binary? That looks more like a script of some
> > sort. What does "file wnprun/bin/witnotp" say?
>
> You are right. It's a script actually:
> workspace/tmp/jake/wnpr
I would guess its trying to return the fikesystem mount point for the supplied
pathname - try:
Stat -c %m
> On 19 Apr 2020, at 03:45, Hiisi wrote:
>
> On Sat, Apr 18, 2020 at 12:44 PM Samuel Sieb wrote:
>>
>
>> Are you sure that's a binary? That looks more like a script of some
>> sort.
On 4/18/20 7:44 PM, Hiisi wrote:
You are right. It's a script actually:
workspace/tmp/jake/wnprun/bin/witnotp: Bourne-Again shell script,
ASCII text executable
The line that causes the error is:
wnp_dir=`netfsname $wnp_dir`
Maybe I will play with it trying to substitute that outdated bash
comman
On Sat, Apr 18, 2020 at 12:44 PM Samuel Sieb wrote:
>
> Are you sure that's a binary? That looks more like a script of some
> sort. What does "file wnprun/bin/witnotp" say?
You are right. It's a script actually:
workspace/tmp/jake/wnprun/bin/witnotp: Bourne-Again shell script,
ASCII text execu
On 4/18/20 6:51 AM, Hiisi wrote:
On Sat, Apr 18, 2020 at 3:33 AM Samuel Sieb wrote:
Is that the name of the binary that you are trying to run?
No. The software is called WitNop. The error occurs when I run the
compiled binary file:
wnprun/bin/witnotp: line 200: netfsname: command not found
On Sat, Apr 18, 2020 at 3:33 AM Samuel Sieb wrote:
>
>
> Is that the name of the binary that you are trying to run?
No. The software is called WitNop. The error occurs when I run the
compiled binary file:
wnprun/bin/witnotp: line 200: netfsname: command not found
sorry, cant execu
On 4/17/20 5:54 PM, Hiisi wrote:
Hello, list.
After compiling some ancient Fortran project I'm unable to run the
resulting binary. It halts with the following message:
netfsname: command not found
Is that the name of the binary that you are trying t
Hello, list.
After compiling some ancient Fortran project I'm unable to run the
resulting binary. It halts with the following message:
netfsname: command not found
Searching with dnf I wasn't able to get any matches. I understand it
must be some old commands, but maybe grey-headed
On 5/15/19 10:02 AM, francis.montag...@inria.fr wrote:
Me too, and particularly since I discovered the M-/ (or Alt-/,
complete-filename) key to force a simple filename completion when the
full (too fancy) completion with TAB is not what you want.
Thank you very much for this tip! I used this y
On 15/05/2019 06:33, Tom Horsley wrote:
Try removing PackageKit-command-not-found if you don't want that
"feature".
On my list to remove even before I first boot a newly
installed fedora (from a chroot into the fedora partition).
bash-completion and environment-modules are t
Hi
On Wed, 15 May 2019 11:45:51 +0100 Patrick O'Callaghan wrote:
> On Tue, 2019-05-14 at 18:33 -0400, Tom Horsley wrote:
>> On my list to remove even before I first boot a newly
>> installed fedora (from a chroot into the fedora partition).
>> bash-completion and environment-modules are two other
On Tue, 2019-05-14 at 18:33 -0400, Tom Horsley wrote:
> On Tue, 14 May 2019 18:11:45 -0400
> DJ Delorie wrote:
>
> > Try removing PackageKit-command-not-found if you don't want that
> > "feature".
>
> On my list to remove even before I first boot a ne
On Tue, 14 May 2019, Samuel Sieb wrote:
> On 5/14/19 3:00 PM, Robert P. J. Day wrote:
> >i'm finally annoyed enough about this to just ask ... on a regular
> > basis, i mistype a command and (predictably) get:
> >
> >bash: xxx: command not found...
>
On Tue, 14 May 2019 18:11:45 -0400
DJ Delorie wrote:
> Try removing PackageKit-command-not-found if you don't want that
> "feature".
On my list to remove even before I first boot a newly
installed fedora (from a chroot into the fedora partition).
bash-completion and enviro
On 5/14/19 3:00 PM, Robert P. J. Day wrote:
i'm finally annoyed enough about this to just ask ... on a regular
basis, i mistype a command and (predictably) get:
bash: xxx: command not found...
but, quite often, rather than getting a bash prompt back immediately,
there is a lo
"Robert P. J. Day" writes:
> what in the name of mutt is bash doing all that time? if there's no
> such command, why the long pause in giving me a new prompt?
It's probably trying to give you a clue on how to install the right
package to get that command.
Try remov
pause after bash "command not found"?
>
> i'm finally annoyed enough about this to just ask ... on a regular
>basis, i mistype a command and (predictably) get:
>
> bash: xxx: command not found...
>
>but, quite often
==
i'm finally annoyed enough about this to just ask ... on a regular
basis, i mistype a command and (predictably) get:
bash: xxx: command not found...
but, quite often, rather than getting a bash prompt back immediately,
there is a lng pause, as i wait, and wait, and wait for
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 met
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 PackageKi
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_
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 is
isconnected machines. IIRC, fetching recent metadata
> > (e.g., by using yum to find a file-level dependency) restores pk-c-n-f's
> > operation.
>
> This is by design. I lost count of the number of bugs opened against
> PackageKit-command-not-found where yum would happily go and
find a file-level dependency) restores pk-c-n-f's
> operation.
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 return to the bash prompt,
even when yum is told to w
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
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 fo
;>> 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 cl
: command not found...
and that's all. The system does not propose to install telnet client
package.
Is this normal ?
Thanks
Eric
Install
PackageKit-command-not-found
PackageKit-command-not-found-0.6.14-2.fc15.x86_64 already installed but
does not seem to work.
Hi Eric,
after uninsta
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
>>
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 c
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
package.
Is this normal ?
Thanks
On 07/04/2010 11:58 AM, Tim wrote:
> Jurek Bajor:
>
>>> Bash is a too important application to be subjected to that kind of
>>> "experimentation" !
>>>
> Geoffrey Leach:
>
>> Agreed!
>>
> Hmm, imagine the fun and games of running a script with a lot of typing
> errors! :-\
>
>
Jurek Bajor:
>> Bash is a too important application to be subjected to that kind of
>> "experimentation" !
Geoffrey Leach:
> Agreed!
Hmm, imagine the fun and games of running a script with a lot of typing
errors! :-\
--
[...@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send privat
On 03/07/10 22:04, Geoffrey Leach wrote:
--snip--
>> I think somebody went over the hills ...
>> Bash is a too important application to be subjected to that kind of
>> "experimentation" !
>>
>> Jurek
>
> Agreed!
I think it's cool, has helped me install missing packages at times,
have also seen goo
On 07/03/2010 10:19:18 AM, Jurek Bajor wrote:
> Hi,
> this is the current state of the matter:
>
> [...@localhost ~]$ clera
> bash: /usr/libexec/pk-command-not-found: No such file or directory
> [r...@localhost jb]# yum install PackageKit-command-not-found
> ...
> [r
Hi,
this is the current state of the matter:
[...@localhost ~]$ clera
bash: /usr/libexec/pk-command-not-found: No such file or directory
[r...@localhost jb]# yum install PackageKit-command-not-found
...
[r...@localhost jb]# clera<-- note
the root mode
bash: cl
thanks.
On 07/02/2010 09:23:20 PM, Ralf Corsepius wrote:
> On 07/03/2010 01:53 AM, Geoffrey Leach wrote:
> > As in:
> > ge...@mtranch[30]->clera
> > Command not found. Similar command is: 'clear'
> >
> > Which would explain the annoying pause after I
On 07/03/2010 01:53 AM, Geoffrey Leach wrote:
> As in:
> ge...@mtranch[30]->clera
> Command not found. Similar command is: 'clear'
>
> Which would explain the annoying pause after I mis-type something.
> bash-4.1.7-1.fc13.i686
>
> Anyone know how to suppress
On Fri, 2010-07-02 at 18:44 -0700, Geoffrey Leach wrote:
> On 07/02/2010 05:19:07 PM, JD wrote:
> > On 07/02/2010 05:05 PM, Craig White wrote:
> > > On Fri, 2010-07-02 at 16:53 -0700, Geoffrey Leach wrote:
> > >> As in:
> > >> ge...@mtranch[30]->clera
On 07/02/2010 05:19:07 PM, JD wrote:
> On 07/02/2010 05:05 PM, Craig White wrote:
> > On Fri, 2010-07-02 at 16:53 -0700, Geoffrey Leach wrote:
> >> As in:
> >> ge...@mtranch[30]->clera
> >> Command not found. Similar command is: 'clear'
> &g
On 07/02/2010 05:05 PM, Craig White wrote:
> On Fri, 2010-07-02 at 16:53 -0700, Geoffrey Leach wrote:
>> As in:
>> ge...@mtranch[30]->clera
>> Command not found. Similar command is: 'clear'
>>
>> Which would explain the annoying pause after I
On Fri, 2010-07-02 at 16:53 -0700, Geoffrey Leach wrote:
> As in:
> ge...@mtranch[30]->clera
> Command not found. Similar command is: 'clear'
>
> Which would explain the annoying pause after I mis-type something.
> bash-4.1.7-1.fc13.i686
>
> Anyone know how
lso quash it system wide via:
yum erase PackageKit-command-not-found
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
As in:
ge...@mtranch[30]->clera
Command not found. Similar command is: 'clear'
Which would explain the annoying pause after I mis-type something.
bash-4.1.7-1.fc13.i686
Anyone know how to suppress this nonsense?
thanks.
--
users mailing list
users@lists.fedoraproject.org
To u
46 matches
Mail list logo
