From: Martin Jansa <martin.jansa@gmail.com>
To: Michael Halstead <mhalstead@linuxfoundation.org>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: Before you ping some older patches
Date: Thu, 23 Feb 2017 02:53:17 +0100 [thread overview]
Message-ID: <20170223015317.GJ3283@jama> (raw)
In-Reply-To: <CA+chaQe23zrLkeJ81iyWxx__=S2PDjGtTSGqm8x5KZOtMd5D_w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3790 bytes --]
On Thu, Feb 23, 2017 at 12:48:22AM +0100, Martin Jansa wrote:
> Hi Michael,
>
> thanks for quick fix.
>
> The hook now shows error about sendmail I wasn't seeing before:
>
> OE @ ~/meta-openembedded $ git push origin master-next
> Counting objects: 78, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (25/25), done.
> Writing objects: 100% (78/78), 7.35 KiB | 0 bytes/s, done.
> Total 78 (delta 56), reused 66 (delta 49)
> remote: No sendmail executable found. Try setting
> multimailhook.sendmailCommand.
> To git.openembedded.org:meta-openembedded
> eb7979113..0d27137f0 master-next -> master-next
Now it found some sendmail...
OE @ ~/meta-openembedded $ git push origin master-next
Counting objects: 85, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (71/71), done.
Writing objects: 100% (85/85), 18.90 KiB | 0 bytes/s, done.
Total 85 (delta 47), reused 0 (delta 0)
remote: Sending notification emails to: openembedded-commits@lists.openembedded.org.
remote:
remote: Exception 'CommandError' raised. Please report this as a bug to
remote: https://github.com/git-multimail/git-multimail/issues
remote: with the information below:
remote:
remote: git-multimail version 1.2.0
remote: Python version 2.7.12 (default, Nov 19 2016, 06:48:10)
remote: [GCC 5.4.0 20160609]
remote: Traceback (most recent call last):
remote: File "/home/git/bin/git_multimail.py", line 3729, in main
remote: run_as_post_receive_hook(environment, mailer)
remote: File "/home/git/bin/git_multimail.py", line 3386, in run_as_post_receive_hook
remote: push.send_emails(mailer, body_filter=environment.filter_body)
remote: File "/home/git/bin/git_multimail.py", line 3332, in send_emails
remote: change.recipients,
remote: File "/home/git/bin/git_multimail.py", line 1883, in send
remote: raise CommandError(self.command, retcode)
remote: CommandError: Command "/usr/sbin/sendmail -oi -t" failed with retcode 1
To git.openembedded.org:meta-openembedded
0d27137f0..57115ebc1 master-next -> master-next
> On Thu, Feb 23, 2017 at 12:06 AM, Michael Halstead <
> mhalstead@linuxfoundation.org> wrote:
>
> > The hooks are repaired and need testing. (Bad git/config settings.) Please
> > feel free to resubmit patches. Let me know if they do not appear in
> > patchwork.
> > I'm trying to see if I can automatically resend the missed patches and
> > mark them superseded if needed. I'll update post here if it works.
> >
> >
> >
> > On 02/22/2017 01:32 PM, Martin Jansa wrote:
> >
> > 1) Make sure they aren't already in master (or master-next), currently
> > there is only one change in master-next:
> > eb7979113 netcat-openbsd: fix implicit dependency on pkg-config
> >
> > 2) Make sure there weren't some negative feedback comments on our change
> >
> > 3) Make sure the change made it to patchwork, currently there is only
> > one "open" change:https://patchwork.openembedded.org/patch/137499/
> >
> > Be aware that the changes are usually daily marked as archived, when
> > they are sorted to corresponding bundles and included in master-next
> > branch for testing, as described here:http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork
> >
> > I'm writing this, because currently many changes are missing on patchwork,
> > because of some unknown issue with it, see:http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html
> > once this issue is resolved, please re-send missing changes.
> >
> > Regards,
> >
> >
> >
> >
> > --
> > Michael Halstead
> > Linux Foundation / SysAdmin
> >
> >
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2017-02-23 1:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 21:32 Before you ping some older patches Martin Jansa
2017-02-22 23:06 ` Michael Halstead
2017-02-22 23:48 ` Martin Jansa
2017-02-23 0:08 ` Michael Halstead
2017-02-23 0:20 ` Derek Straka
2017-02-23 1:53 ` Martin Jansa [this message]
2017-02-23 1:58 ` Michael Halstead
2017-02-23 2:31 ` Michael Halstead
-- strict thread matches above, loose matches on Subject: below --
2017-02-22 22:26 MacDonald, Joe
2017-02-22 22:51 ` Martin Jansa
2017-02-22 23:09 MacDonald, Joe
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=20170223015317.GJ3283@jama \
--to=martin.jansa@gmail.com \
--cc=mhalstead@linuxfoundation.org \
--cc=openembedded-devel@lists.openembedded.org \
/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