Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next v2 3/3] package/python-mwclient: bump version to 0.8.6
Date: Fri, 24 Nov 2017 21:32:08 +0100	[thread overview]
Message-ID: <20171124213208.0e784d54@windsurf.lan> (raw)
In-Reply-To: <CAGm1_ku9aHQYXjEX1zP9O85weDgYjHG9jvmqk+8J1H7bB61nhA@mail.gmail.com>

Hello,

On Fri, 24 Nov 2017 20:12:15 +0100, Yegor Yefremov wrote:

> > Apparently this update is causing a new build failure:
> > http://autobuild.buildroot.net/results/79e/79ef04d2e8c91231028e23f4bb35df685efa55ca/build-end.log.
> >
> > Could you have a look?
> >
> > Thanks a lot!  
> 
> I've opened an issue [1]
> 
> [1] https://github.com/mwclient/mwclient/issues/179

Thanks. However, Bernd has submitted a patch that apparently fixes this
problem: https://patchwork.ozlabs.org/patch/841159/. It looks sane to
me, but I'm not a Python packaging expert. Could you have a look?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-11-24 20:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-12 10:45 [Buildroot] [PATCH/next v2 1/3] package/python-oauthlib: new package Bernd Kuhls
2017-11-12 10:45 ` [Buildroot] [PATCH/next v2 2/3] package/python-requests-oauthlib: " Bernd Kuhls
2017-11-12 22:18   ` Yegor Yefremov
2017-11-12 10:45 ` [Buildroot] [PATCH/next v2 3/3] package/python-mwclient: bump version to 0.8.6 Bernd Kuhls
2017-11-12 22:20   ` Yegor Yefremov
2017-11-24 14:28   ` Thomas Petazzoni
2017-11-24 19:12     ` Yegor Yefremov
2017-11-24 20:32       ` Thomas Petazzoni [this message]
2017-11-12 22:18 ` [Buildroot] [PATCH/next v2 1/3] package/python-oauthlib: new package Yegor Yefremov
2017-11-23 21:54 ` Thomas Petazzoni

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=20171124213208.0e784d54@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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