Ticket #1999 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

python-etk-git patches patched upstream

Reported by: ptitjes Owned by: julian_chu
Priority: normal Milestone:
Component: Distro Version:
Severity: normal Keywords:
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:
Reproducible: always


Patches for the python-etk-git package already have been patched upstream. This makes its build fail.


python-etk_git.bb.patch (617 bytes) - added by ptitjes 11 years ago.
A patch for the python-etk-git.bb file

Change History

Changed 11 years ago by ptitjes

A patch for the python-etk-git.bb file

comment:1 Changed 11 years ago by Niko!

A doubt... should be a git package avoided (if no version/date locked), in a "stable" branch?

comment:2 Changed 11 years ago by zecke

  • Status changed from new to closed
  • Resolution set to fixed

Sorry that it took so long. It would have helped if you specify the git branch you are building. The issue was that I cherry-picked a etk upgrade but the package was not rebuilt (as the srcrev was not part of the PV). So only people building from scratch suffered this issue with org.openmoko.asu.stable. This has been resolved now and the PV was fixed and the patches were dropped.

In org.openmoko.asu.stable every single SCM based recipe should be pinned to a fixed revision. It should be possible to parse/reparse and build without network connection. If you think/know that is not the case I would be interested in that information.

comment:3 Changed 11 years ago by ptitjes


Sorry I did forgot to tell the git branch I was building. I'm a newbie with om, oe and git. Also this was my first bug report for om. I'll try to give better informations next time.

I'll tell if I see floating versions...

Thanks for the fix.

Note: See TracTickets for help on using tickets.