Bug 9712 - buildhistory-diff depends on python3-git, which is not in Debian Stable
Summary: buildhistory-diff depends on python3-git, which is not in Debian Stable
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.2 M1
Assignee: Ed Bartosh
QA Contact:
URL:
Whiteboard: 8 June 2016: IN PROGRESS REVIEW
Depends on:
Blocks:
 
Reported: 2016-06-06 13:36 UTC by Jussi Kukkonen
Modified: 2017-12-06 16:55 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: Done (doc changes complete)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jussi Kukkonen 2016-06-06 13:36:52 UTC
buildhistory-diff fails on Debian Stable because python3-git is not available.

python3-git is in jessie-backports but that's not enabled by default. So if we consider this as just a documentation bug, we would have to document how to enable backports on Debian...
Comment 1 Ed Bartosh 2016-06-07 12:41:27 UTC
This also true for OpenSUSE 13.2 and 42.1
It's even worse on OpenSUSE as it doesn't have even python-git in default installation.

There are plenty of choices how to deal with this:
- find and install python3-git as Jussi suggested
- install GitPython with pip3: pip3 install GitPython --user
- run script with python 2 explicitly: python ../scripts/buildhistory-diff
- refer to python 2 in script's shebang: #!/usr/bin/env python

Changing documentation looks better than going back to python 2 from my point of view.
Comment 2 Scott Rifenbark 2016-06-07 17:34:09 UTC
This section (http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#examining-build-history-information) talks about running buildhistory-diff.  Outside of a mention in the migration section, which probably does not apply, that is the only area where buildhistory-diff is specifically shown. 

Would a "NOTE" be sufficient here?  

One thing I thought was going to happen with post 2.1 is that Python 3 would be part of the release.  If so, wouldn't this issue go away for future releases of YP?

Scott
Comment 3 Ed Bartosh 2016-06-08 09:16:18 UTC
I think NOTE should be enough.

Would something like this be ok?

Buildhistory-diff requries GitPython package. Please, install it with pip3:
pip3 install GitPython --user

Or install python3-git package using distro package manager(apt-get, dnf or zipper)
Comment 4 Ed Bartosh 2016-06-08 11:05:02 UTC
> One thing I thought was going to happen with post 2.1 is that Python 3 would be part of the release.  If so, wouldn't this issue go away for future releases of YP?

No it wouldn't as it was caused by the move to Python 3.
Comment 5 Scott Rifenbark 2016-06-08 15:52:36 UTC
Hi, 

Check out the new note at http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#examining-build-history-information and let me know if this is okay. 

Thanks, 
Scott
Comment 6 Scott Rifenbark 2016-06-08 15:53:31 UTC
Oops... I just realized I am not the owner of this bug.  I did change the state Ed.  Sorry.

Scott
Comment 7 Ed Bartosh 2016-06-09 07:15:01 UTC
Thank you for updating the documentation! The change looks good to me. There is just one small typo in there: "Alternatively, you can install python3-3" should be "Alternatively, you can install python3-git"

Jussi, are you ok with the change?
Comment 8 Jussi Kukkonen 2016-06-09 07:23:09 UTC
(In reply to comment #7)
> Jussi, are you ok with the change?

Sure.
Comment 9 Leonardo Sandoval Gonzalez 2016-06-09 14:39:04 UTC
a similar issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=9690
Comment 10 Scott Rifenbark 2016-06-09 16:25:37 UTC
Ed, 

Don't know how I managed that typo :)

Fixed it - see http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#examining-build-history-information

Thanks, 
Scott
Comment 11 Scott Rifenbark 2016-06-10 17:23:19 UTC
Thanks... I am putting the doc flag to Done.  It was set at "No" but it did involve the docs. 

Scott
Comment 12 Ed Bartosh 2016-06-13 07:43:21 UTC
Thank you!