Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 15/15] python3: update to 3.8.0
Date: Sat, 30 Nov 2019 01:25:14 +0200	[thread overview]
Message-ID: <20191129232514.GA19686@localhost> (raw)
In-Reply-To: <ce46910c-b481-f7a8-9f41-b8a4a745644f@intel.com>

On Fri, Nov 29, 2019 at 10:55:23PM +0000, Ross Burton wrote:
> On 29/11/2019 22:54, Ross Burton wrote:
> > Not sure what is going on but with this when btrfs-tools is rebuild:
> > 
> > packages/corei7-64-poky-linux/btrfs-tools/btrfs-tools: FILELIST:
> > directory renamed
> > /usr/lib/python3.7/site-packages/btrfsutil-1.1.1-py3.7.egg-info ->
> > /usr/lib/python3.8/site-packages/btrfsutil-1.1.1-py3.8.egg-info, removed "/usr/lib/python3.7/site-packages/btrfsutil.cpython-37m-x86_64-linux-gnu.so",
> > added
> > "/usr/lib/python3.8/site-packages/btrfsutil.cpython-38-x86_64-linux-gnu.so"
> > 
> > Basically, all the 3.7 references are now 3.8.  That's fine.
> > 
> > packages/corei7-64-poky-linux/btrfs-tools/btrfs-tools: RDEPENDS: removed
> > "libpython3 (['>= 3.7.5'])"
> > 
> > Python 3.7 is removed but no Python 3.8 added. Weird!
> 
> Same happened to gpgme:
> 
> packages/corei7-64-poky-linux/gpgme/python3-gpg: RDEPENDS: removed
> "libpython3 (['>= 3.7.5'])"

That's expected, C extensions are no longer linked with libpython by default.


> Ross

cu
Adrian


  parent reply	other threads:[~2019-11-29 23:25 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 13:11 [PATCH 01/15] rpm: upgrade to 4.15.1 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 02/15] libdnf: upgrade 0.28.1 -> 0.38.1 Alexander Kanavin
2019-12-02 14:55   ` Ross Burton
2019-12-02 15:10     ` Adrian Bunk
2019-12-02 15:24       ` Alexander Kanavin
2019-12-02 21:37         ` Adrian Bunk
2019-12-02 22:44         ` Khem Raj
2019-12-02 22:55           ` Adrian Bunk
2019-12-02 23:25             ` Khem Raj
2019-11-29 13:11 ` [PATCH 03/15] dnf: upgrade 4.2.2 -> 4.2.16 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 04/15] gettext-minimal-native: update to 0.20.1 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 05/15] gettext: " Alexander Kanavin
2019-11-29 13:11 ` [PATCH 06/15] lrzsz: fix issues with newer versions of gettext Alexander Kanavin
2019-11-29 13:11 ` [PATCH 07/15] p11-kit: convert to meson Alexander Kanavin
2019-11-29 22:56   ` Ross Burton
2019-12-02 12:00     ` Alexander Kanavin
2019-11-29 13:11 ` [PATCH 08/15] psmisc: revert to default autopoint exclusion Alexander Kanavin
2019-11-29 13:11 ` [PATCH 09/15] sed: upgrade to 4.7 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 10/15] bind: update 9.11.5-P4 -> 9.11.13 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 11/15] flex: update to 2.6.4 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 12/15] gettext: fix failing ptests Alexander Kanavin
2019-11-29 13:11 ` [PATCH 13/15] libffi: update to 3.3 final Alexander Kanavin
2019-12-02 16:19   ` Ross Burton
2019-12-02 16:21     ` Ross Burton
2019-12-02 16:24       ` Alexander Kanavin
2019-12-02 16:31       ` Adrian Bunk
2019-11-29 13:11 ` [PATCH 14/15] libcomps: update to 0.1.12 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 15/15] python3: update to 3.8.0 Alexander Kanavin
2019-11-29 22:54   ` Ross Burton
2019-11-29 22:55     ` Ross Burton
2019-11-29 22:56       ` Ross Burton
2019-12-02 11:43         ` Alexander Kanavin
2019-11-29 23:25       ` Adrian Bunk [this message]
2019-12-02 11:13         ` Ross Burton
2019-12-03  8:56   ` Ross Burton
2019-11-29 13:32 ` ✗ patchtest: failure for "rpm: upgrade to 4.15.1..." and 14 more Patchwork
2019-11-29 20:52 ` [PATCH 01/15] rpm: upgrade to 4.15.1 Ross Burton
2019-11-29 21:28   ` Alexander Kanavin
2019-11-29 22:08     ` Ross Burton
2019-12-03 23:05     ` Ross Burton
2019-12-03 23:52       ` Ross Burton
2019-12-04 10:17         ` Alexander Kanavin

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=20191129232514.GA19686@localhost \
    --to=bunk@stusta.de \
    --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