Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#26998 - [gnome-packagekit] doesn't build
Attached to Project:
Community Packages
Opened by Andrea Scarpino (BaSh) - Friday, 18 November 2011, 10:12 GMT
Last edited by Jonathan Conder (PirateJonno) - Thursday, 16 February 2012, 01:28 GMT
Opened by Andrea Scarpino (BaSh) - Friday, 18 November 2011, 10:12 GMT
Last edited by Jonathan Conder (PirateJonno) - Thursday, 16 February 2012, 01:28 GMT
|
DetailsDescription:
Making all in packagekit /bin/sh: python: command not found make[3]: *** [genums.py] Error 127 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Additional info: * gnome-packagekit 3.2.1-1 Steps to reproduce: Try to build it. |
This task depends upon
Closed by Jonathan Conder (PirateJonno)
Thursday, 16 February 2012, 01:28 GMT
Reason for closing: Fixed
Thursday, 16 February 2012, 01:28 GMT
Reason for closing: Fixed
Comment by Jonathan Conder (PirateJonno) -
Friday, 18 November 2011, 15:08 GMT
Looks like I missed this because my chroots have python installed. I think I'll just make packagekit and gnome-packagekit depend on python 3. Once I've had some sleep that is
Comment by Jonathan Conder (PirateJonno) -
Sunday, 20 November 2011, 11:14 GMT
I'll have to wait until pacman 4 (thus packagekit 0.6.19-2) comes out, otherwise I risk messing up the pkgrels for people using [testing]. However I could probably do gnome-packagekit individually if anyone needs this urgently.
Comment by Andrea Scarpino (BaSh) -
Sunday, 20 November 2011, 11:15 GMT
This is a build issue, then I guess you can fix this in repos/community-i686 and community-x86_64, without bumping pkgrel.
Comment by Jonathan Conder (PirateJonno) -
Sunday, 20 November 2011, 11:40 GMT
Ok, good point. I take it this is done via svn directly rather than using communitypkg and db-update?
Comment by Andrea Scarpino (BaSh) -
Sunday, 20 November 2011, 11:41 GMT
Yes, you can use svn directly.