Bug 349363 – kde-base/system-config-printer-kde-4.5.4 fails on installing

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Igor Petrov 2010-12-22 12:58:27 UTC]

When trying to install process crashing with reason "make: *** No rule to make target `install'.  Stop."

Reproducible: Always

Steps to Reproduce:
1. emerge kde-base/system-config-printer-kde-4.5.4
2.
3.

Actual Results:  
Installing crashes because of wrong makefile.

Expected Results:  
Obviously package should just be built and installed. :}

[Comment 1 Igor Petrov 2010-12-22 13:00:43 UTC]

Created attachment 257756 [details]
build log

Here is a log.

[Comment 2 Rafał Mużyło 2010-12-22 15:43:35 UTC]

Traceback (most recent call last):
  File "/usr/share/apps/cmake/modules/FindPyKDE4.py", line 8, in <module>
    import PyKDE4.pykdeconfig
ImportError: No module named PyKDE4.pykdeconfig

First guess - incorrect python update, run python updater.
Second guess - incorrect pyqt4 upgrade, remerge packages, that depend on it (as per ebuild message).

[Comment 3 Igor Petrov 2010-12-22 17:48:51 UTC]

> First guess - incorrect python update, run python updater.
> Second guess - incorrect pyqt4 upgrade, remerge packages, that depend on it (as
> per ebuild message).
> 

I've got one more question. Two days ago I had problems with portage and I found there were no python prifile chosen. I've got 2.6 and 3.1 installed. I set 3.1. Maybe I should set 2.6 version?

[Comment 4 Igor Petrov 2010-12-22 18:13:00 UTC]

(In reply to comment #3)
> > First guess - incorrect python update, run python updater.
> > Second guess - incorrect pyqt4 upgrade, remerge packages, that depend on it (as
> > per ebuild message).
> > 
> 
> I've got one more question. Two days ago I had problems with portage and I
> found there were no python prifile chosen. I've got 2.6 and 3.1 installed. I
> set 3.1. Maybe I should set 2.6 version?
> 

Nope. The problem is in Makefile. There's no target for 'install'. You may check it yourself.

[Comment 5 Rafał Mużyło 2010-12-22 19:35:25 UTC]

The first guess was for a case of upgrading python 2.6 to 2.7
and not running python-updater afterwards. Seems it's not the case.

The second is most likely valid - there's an important message in postint of dev-python/sip ebuild and it seems you've failed to follow it.

[Comment 6 Igor Petrov 2010-12-22 21:31:31 UTC]

(In reply to comment #5)
> The first guess was for a case of upgrading python 2.6 to 2.7
> and not running python-updater afterwards. Seems it's not the case.
> 
> The second is most likely valid - there's an important message in postint of
> dev-python/sip ebuild and it seems you've failed to follow it.
> 

I've seen message of dev-python/sip and reemerged everything as it was said there. And I believe in this case version of active python profile doesnt't really matter. Do you know what actually are you talking about? Why can't you understand that _there_is_no_target_'install'_ in Makefile. Do you know what makefile is?

[Comment 7 Igor Petrov 2010-12-22 22:57:40 UTC]

Well... I'm sorry. I was a little been nervous. You were right. The reason is in python profile. I changed it to 2.7 and used python-updater. 

Thank you. Solved.

[Comment 8 Igor Petrov 2010-12-22 22:58:17 UTC]

And I still don't understand why... 

[Comment 9 Rafał Mużyło 2010-12-23 01:59:55 UTC]

Till you ran python-updater all the old packages were installed only for python 2.6.

[Comment 10 andry 2010-12-29 19:00:42 UTC]

(In reply to comment #0)
> When trying to install process crashing with reason "make: *** No rule to make
> target `install'.  Stop."
>
 
This helped me:
emerge pycups system-config-printer-common