<div dir="ltr"><div>Hi, </div><div><br></div><div><div class="gmail_extra">On 11 January 2016 at 06:21, <span dir="ltr"><<a href="mailto:auh@auh.yoctoproject.org" target="_blank">auh@auh.yoctoproject.org</a>></span> wrote:<br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hello,<br><br>You are receiving this email because you are the maintainer<br>of *gpgme* recipe and this is to let you know that the automatic attempt<br>to upgrade the recipe to *1.6.0* has Succeeded.<br></blockquote><div><br></div><div><br></div></div></div></div>First, thanks for the effort Anibal, the upgrade helper is looking very useful: I'm certainly going to use it.<br><div class="gmail_extra"><br></div><div class="gmail_extra">Couple of small issues:</div><div class="gmail_extra">* The license diffs do not seem correct: they look like like diffs between an empty file and the new license file version (see the parent gpgme post for example)</div><div class="gmail_extra">* Is the decision to use "buildhistory-diff -a" intentional? I'm not 100% sure what exactly "-a" option brings with it but I've usually avoided it on upgrades because the path changes in  -dbg package are so verbose as to hide everything else...</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks,</div><div class="gmail_extra"> Jussi</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
*LICENSE CHANGED* please review the gpgme.h.in.diff file and update the LICENSE<br>
variable in the recipe if is needed.<br>
<br>
The recipe has been successfully compiled for machines qemux86, qemux86-64, qemuarm, qemumips, qemuppc.<br>
<br>
Next steps:<br>
  - apply the patch: git am 0001-gpgme-upgrade-to-1.6.0.patch<br>
  - check that required upstream patches have not been commented from the recipe,<br>
   if upstream patches were commented the reason is specified in the commit message.<br>
  - compile an image that contains the package<br>
  - perform some basic sanity tests<br>
  - amend the patch and sign it off: git commit -s --reset-author --amend<br>
  - send it to the list<br>
<br>
Attached are the patch, license diff (if change) and bitbake log.<br>
Any problem please contact Anibal Limon <<a href="mailto:anibal.limon@intel.com" target="_blank">anibal.limon@intel.com</a>>.<br>
<br>
Regards,<br>
The Upgrade Helper</blockquote></div><br></div></div>