can't start moc in Ubuntu 14.10

[Tong Sun]

The moc fails to start in Ubuntu 14.10:

$ moc
moc: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/moc': No such file or directory

DistroRelease: Ubuntu 14.10
NonfreeKernelModules: nvidia
Package: moc 1:2.5.0~beta2-1build2
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
SourcePackage: moc
Tags: utopic
Uname: Linux 3.16.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)

[Elimar Riesebieter (riesebie)]

* Tong Sun <email address hidden> [2015-01-17 15:59 -0000]:

> Public bug reported:
>
> The moc fails to start in Ubuntu 14.10:
>
> $ moc
> moc: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/moc': No such file or directory

According to /usr/share/doc/moc/README.Debian you have to run:

$ mocp

Elimar
--
 Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)

[Tong Sun (suntong001)]

Ahh... Thanks!

[Jeffrey Stern (jas-61803)]

i would like to vote to re-open this bug (or to start a new one), on the basis of UI/UX. Many Linux newbies do not know that /usr/share/doc/moc/README even exists. Yes, they will discover it later, but that page is "remote" to the experience (on the command-line itself). Even if you goes to that page, the heads-up is easy to miss because the warning about the alternative executable name is not prominently displayed at the top, but instead is buried a page down.

I'd like to suggest/request that for the easiest/friendliest end-user experience (especially newbies to Linux):

1) the moc executable be re-instated as "moc", not "mocp", so that it matches the package-name (which is most often standard for Debian package naming)

OR (less desireable):

2) the package be renamed to "mocp" to match the executable name

OR (at least...)

3) that the error message be changed or amended so that it redirects the user to 'mocp' instead of giving a useless / unfriendly error message.

Thank you.
-JS

[Elimar Riesebieter (riesebie)]

1) Not possible as the binary moc is part of libqt4-dev-bin.

2) moc is given as many users all over the world appreciate that package and it is well known. Ah, and there won't be a patched patched Debian package, though.

3) There is no error message caused by moc package. What I can do is to implement a hint while package installation. This has to wait until next upload.

Elimar
Debian's moc maintainer

[Tong Sun (suntong001)]

Giving that `moc` is producing errors like this:

> $ moc
> moc: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/moc': No such file or directory

is there anyone that actually use it?

I meant, can we use alternative or something that make moc works like mocp? Saving you from explaining each time...

[Elimar Riesebieter (riesebie)]

* Tong Sun <email address hidden> [2015-11-03 20:47 -0000]:

> Giving that `moc` is producing errors like this:
>
> > $ moc
> > moc: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/moc': No such file or directory
>
> is there anyone that actually use it?
>
As told before:
$ apt-file search /usr/lib/x86_64-linux-gnu/qt4/bin/moc
libqt4-dev-bin: /usr/lib/x86_64-linux-gnu/qt4/bin/moc

> I meant, can we use alternative or something that make moc works like
> mocp? Saving you from explaining each time...

So it is not moc's fault.

Elimar
--
 >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
              --posting from alex in debian-user--

[Tong Sun (suntong001)]

On Tue, Nov 3, 2015 at 4:28 PM, Elimar Riesebieter <email address hidden>
wrote:

> So it is not moc's fault.
>

Yep, definitely understood. But it shouldn't prevent moc to mitigate it
either. I mean,

If we install moc as a symlink to mocp under /usr/bin, that would sure have
fixed the problem right?

[Elimar Riesebieter (riesebie)]

* Tong Sun <email address hidden> [2015-11-03 21:54 -0000]:

> On Tue, Nov 3, 2015 at 4:28 PM, Elimar Riesebieter <email address hidden>
> wrote:
>
> > So it is not moc's fault.
> >
>
> Yep, definitely understood. But it shouldn't prevent moc to mitigate it
> either. I mean,
>
> If we install moc as a symlink to mocp under /usr/bin, that would sure have
> fixed the problem right?

No way! One who uses /usr/lib/x86_64-linux-gnu/qt4/bin/moc from
libqt4-dev-bin will be confused.

Elimar
--
 Learned men are the cisterns of knowledge,
  not the fountainheads ;-)

[Peter Flynn (frisket)]

I just installed it in Mint 19 and it still fails to execute, with the error:
moc: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/moc': No such file or directory

Can it please be made to work?

[Elimar Riesebieter (riesebie)]

* Peter Flynn <email address hidden> [2019-03-31 14:10 -0000]:

> I just installed it in Mint 19 and it still fails to execute, with the error:
> moc: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/moc': No such file or directory
>
> Can it please be made to work?

To run moc you must type

$ mocp

See /usr/share/doc/moc/README.Debian

Elimar
--
  From The Collaborative International Dictionary of English v.0.48 [gcide]:
  .
  arsehole \arse"hole`\ ([aum]rs"h[=o]l`), n.
         1. execretory opening at the end of the alimentary canal.