Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mikhail Vanyulin <mvanyulin@dev.rtsoft.ru>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] patch for bug #12814
Date: Tue, 13 Nov 2018 16:44:30 +0300	[thread overview]
Message-ID: <1231b8ff-b174-9eab-a79a-ecca39e9a613@dev.rtsoft.ru> (raw)
In-Reply-To: <57ede211-3422-e8ef-8f1c-8bfd320f28f0@dev.rtsoft.ru>

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

Resending email as "This mailinglist requires people to subscribe before 
posting. "

Best regards, / С уважением,
Mikhail       / Михаил

On 11/13/2018 04:38 PM, Mikhail Vanyulin wrote:
> Should be ok now.
>
> Best regards, / С уважением,
> Mikhail       / Михаил
>
> On 11/12/2018 01:29 PM, Burton, Ross wrote:
>> Please rewrite the commit message to follow the guidelines in
>> https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#New_Development. 
>>
>> The bug  reference is correct but should be at the end before your
>> SOB.  Something like:
>>
>> python: fix contents of python-xmlrpc package
>>
>> Add missing files etc etc.
>>
>> [ YOCTO #1234 ]
>>
>> Signed-off-by: Foo Bar <foo@bar>
>>
>> Also the patch needs rebasing onto master, the manifest was
>> reformatted since your patch was created.
>>
>> Thanks,
>> Ross
>> On Mon, 12 Nov 2018 at 06:59, Mikhail Vanyulin 
>> <mvanyulin@dev.rtsoft.ru> wrote:
>>> Adds a missing file to python-xmlrpc package.
>>>
>>> -- 
>>> Best regards, / С уважением,
>>> Mikhail       / Михаил
>>>
>>>
>


[-- Attachment #2: 0001-python-fix-contents-of-python-xmlrpc-package.patch --]
[-- Type: text/x-patch, Size: 1164 bytes --]

From 2b840184cb4dd99913baa96ef6040c08605e71cc Mon Sep 17 00:00:00 2001
From: mvanyulin <mvanyulin@dev.rtsoft.ru>
Date: Tue, 13 Nov 2018 17:27:16 +0400
Subject: [PATCH] python: fix contents of python-xmlrpc package

Add a missed xmlrpclib.py to python-xmlrpc package.

[ YOCTO #12814 ] -- https://bugzilla.yoctoproject.org/show_bug.cgi?id=12814

Signed-off-by: Mikhail Vanyulin <mvanyulin@dev.rtsoft.ru>
---
 meta/recipes-devtools/python/python/python2-manifest.json | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python/python2-manifest.json b/meta/recipes-devtools/python/python/python2-manifest.json
index 260fa6f..95e639c 100644
--- a/meta/recipes-devtools/python/python/python2-manifest.json
+++ b/meta/recipes-devtools/python/python/python2-manifest.json
@@ -1031,7 +1031,8 @@
         ], 
         "files": [
             "${libdir}/python2.7/DocXMLRPCServer.py", 
-            "${libdir}/python2.7/SimpleXMLRPCServer.py"
+            "${libdir}/python2.7/SimpleXMLRPCServer.py", 
+            "${libdir}/python2.7/xmlrpclib.py"
         ]
     }, 
     "zlib": {
-- 
1.9.1


      parent reply	other threads:[~2018-11-13 13:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f9d3e588-e159-f31c-1698-1903ebb4b0a5@dev.rtsoft.ru>
     [not found] ` <be39ebc7-47fe-07df-a419-b5725e43f7ac@dev.rtsoft.ru>
2018-11-12 10:29   ` [PATCH] patch for bug #12814 Burton, Ross
     [not found]     ` <57ede211-3422-e8ef-8f1c-8bfd320f28f0@dev.rtsoft.ru>
2018-11-13 13:44       ` Mikhail Vanyulin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1231b8ff-b174-9eab-a79a-ecca39e9a613@dev.rtsoft.ru \
    --to=mvanyulin@dev.rtsoft.ru \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox