pyblake2 removal if gemato&portage@python3_6 [Solved]

[CaptainBlood]

Here, after new install&USE flags minimizing tweaks

Code: Select all

equery u portage gemato pyblake2
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for sys-apps/portage-2.3.40-r1:
 U I
 - - build                    : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for creating build images and the first half of bootstrapping [make stage1]
 - - doc                      : Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally
 - - epydoc                   : Build html API documentation with epydoc.
 - - gentoo-dev               : Enable features required for Gentoo ebuild development.
 - + ipc                      : Use inter-process communication between portage and running ebuilds. 
 + + native-extensions        : Compiles native "C" extensions (speedups, instead of using python backup code). Currently includes libc-locales. This should only be
                                temporarily disabled for some bootstrapping operations. Cross-compilation is not supported. 
 - - python_targets_python2_7 : Build with Python 2.7
 - - python_targets_python3_4 : Build with Python 3.4
 - - python_targets_python3_5 : Build with Python 3.5
 + + python_targets_python3_6 : Build with Python 3.6
 + + rsync-verify             : Enable full-tree cryptographic verification of Gentoo repository rsync checkouts using app-portage/gemato. 
 - - xattr                    : Preserve extended attributes (filesystem-stored metadata) when installing files. Usually only required for hardened systems. 

 * Found these USE flags for app-portage/gemato-13.0-r1:
 U I
 + + blake2                   : Install dependencies needed for BLAKE2 hash functions
 - - bzip2                    : Use the bzlib compression library
 - - gpg                      : Install dependencies needed for OpenPGP signature verification support
 - - lzma                     : Support for LZMA (de)compression algorithm
 - - python_targets_python2_7 : Build with Python 2.7
 - - python_targets_python3_4 : Build with Python 3.4
 - - python_targets_python3_5 : Build with Python 3.5
 + + python_targets_python3_6 : Build with Python 3.6
 - - sha3                     : Install dependencies needed for SHA3 hash functions
 - - test                     : Workaround to pull in packages needed to run with FEATURES=test. Portage-2.1.2 handles this internally, so don't set it in
                                make.conf/package.use anymore
 - - tools                    : Install additional utilities (benchmarks, hash testing tools, fast Manifest generators) to /usr/share/gemato.

 * Found these USE flags for dev-python/pyblake2-1.1.2:
 U I
 - - python_targets_python2_7 : Build with Python 2.7
 - - python_targets_python3_4 : Build with Python 3.4
 - - python_targets_python3_5 : Build with Python 3.5
 + + python_targets_python3_6 : Build with Python 3.6


emerge -p -c
Calculating dependencies... done!
>>> Calculating removal order...

>>> These are the packages that would be unmerged:

 dev-python/pyblake2
    selected: 1.1.2 
   protected: none 
     omitted: none 

All selected packages: =dev-python/pyblake2-1.1.2

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

Packages installed:   174
Packages in world:    8
Packages in system:   43
Required packages:    173
Number to remove:     1

Although I don't know anything about pyblake2 ( something to do with rsync verification, I suppose ) I don't understand why emerge allows to remove it. Futhermore showing the lack of constraints on *python3_6

Code: Select all

 * These packages depend on pyblake2:
app-portage/gemato-13.0-r1 (python_targets_pypy ? dev-python/pyblake2[python_targets_pypy(-)?,-python_single_target_pypy(-),python_targets_python2_7(-)?,-python_single_target_python2_7(-),python_targets_python3_4(-)?,-python_single_target_python3_4(-),python_targets_python3_5(-)?,-python_single_target_python3_5(-)])
                           (python_targets_python2_7 ? dev-python/pyblake2[python_targets_pypy(-)?,-python_single_target_pypy(-),python_targets_python2_7(-)?,-python_single_target_python2_7(-),python_targets_python3_4(-)?,-python_single_target_python3_4(-),python_targets_python3_5(-)?,-python_single_target_python3_5(-)])
                           (python_targets_python3_4 ? dev-python/pyblake2[python_targets_pypy(-)?,-python_single_target_pypy(-),python_targets_python2_7(-)?,-python_single_target_python2_7(-),python_targets_python3_4(-)?,-python_single_target_python3_4(-),python_targets_python3_5(-)?,-python_single_target_python3_5(-)])
                           (python_targets_python3_5 ? dev-python/pyblake2[python_targets_pypy(-)?,-python_single_target_pypy(-),python_targets_python2_7(-)?,-python_single_target_python2_7(-),python_targets_python3_4(-)?,-python_single_target_python3_4(-),python_targets_python3_5(-)?,-python_single_target_python3_5(-)])
sys-apps/portage-2.3.40-r1 (python_targets_pypy ? dev-python/pyblake2[python_targets_pypy(-)?,-python_single_target_pypy(-),python_targets_python2_7(-)?,-python_single_target_python2_7(-),python_targets_python3_4(-)?,-python_single_target_python3_4(-),python_targets_python3_5(-)?,-python_single_target_python3_5(-)])
                           (python_targets_python2_7 ? dev-python/pyblake2[python_targets_pypy(-)?,-python_single_target_pypy(-),python_targets_python2_7(-)?,-python_single_target_python2_7(-),python_targets_python3_4(-)?,-python_single_target_python3_4(-),python_targets_python3_5(-)?,-python_single_target_python3_5(-)])
                           (python_targets_python3_4 ? dev-python/pyblake2[python_targets_pypy(-)?,-python_single_target_pypy(-),python_targets_python2_7(-)?,-python_single_target_python2_7(-),python_targets_python3_4(-)?,-python_single_target_python3_4(-),python_targets_python3_5(-)?,-python_single_target_python3_5(-)])

should explain the removal. But then how would the feature be performed?
Thks 4 ur attention.

[bobbymcgee]

ebuilds are hashed with blake2 in the tree. blake2 hashing was added directly to python in 3.6. So if portage is only built with python3.6 target, you probably don't need pyblake anymore.

[CaptainBlood]

fine!
Thks 4 ur attention, interest & support