Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

cardinal

Members
  • Posts

    490
  • Joined

  • Last visited

  • Days Won

    59

Posts posted by cardinal

  1. User must update meta-repo with:

    ego sync
    

    Then I was able to remove python targets from /etc/portage/make.conf

    If you use the manual method of updating meta-repo portage is unaware of PYTHON_TARGETS and
    PYTHON_SINGLE_TARGET, then you get error like this for installed packages:

    The following REQUIRED_USE flag constraints are unsatisfied:
     exactly-one-of ( python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) 
    
  2. There is an issue with the latest sync that removed PYTHON_TARGETS and PYTHON_SINGLE_TARGET from core-kit/profiles/funtoo/1.0/linux-gnu/make.defaults.

    Bug report: https://bugs.funtoo.org/browse/FL-4119
     
    The problem is caused by this change:
    https://github.com/funtoo/core-kit/commit/573056d2ef402eaf352e3b71f1a3be4641d21857#diff-dbc31f1e797004b709d3acad7d8288a4

    @@ -12,10 +12,6 @@ USE_EXPAND="CPU_FLAGS_X86 OSS_CARDS APACHE2_MODULES APACHE2_MPMS FOO2ZJS_DEVICES
     # Nginx variables
     USE_EXPAND="${USE_EXPAND} NGINX_MODULES_EXTERNAL NGINX_MODULES_HTTP NGINX_MODULES_MAIL"
     
    -# This value should be kept in synchronization with _PYTHON_GLOBALLY_NONDEFAULT_ABIS variable set in python.eclass by funtoo/scripts/merge.py.
    -PYTHON_TARGETS="python2_7 python3_4"
    -PYTHON_SINGLE_TARGET="python3_4"
    -
     # This setting should be kept in sync with a >=dev-lang/php-5.x mask,
     # so that PHP_TARGETS always refers to the latest unmasked x.y version
     # of PHP.
    

    My temporary solution was to add the removed variables to /etc/portage/make.conf :

    PYTHON_TARGETS="python2_7 python3_4"
    PYTHON_SINGLE_TARGET="python3_4"
    
  3. Verify microcode is loaded after using "Early microcode" method:

    rj@funtoo ~ $ dmesg | grep microcode
    [    0.000000] microcode: CPU0 microcode updated early to revision 0xa4, date = 2010-10-02
    [    0.009999] microcode: CPU1 microcode updated early to revision 0xa4, date = 2010-10-02
    [    0.740346] microcode: CPU0 sig=0x6fd, pf=0x1, revision=0xa4
    [    0.740472] microcode: CPU1 sig=0x6fd, pf=0x1, revision=0xa4
    [    0.740640] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
    
    

    https://wiki.gentoo.org/wiki/Intel_microcode :

    The microcode-ctl utility has been deprecated as of version 1.28-r1(Gentoo unstable)[1] and no longer contains the init script. It also does not work on certain CPUs such as Intel Haswells, you should switch to the "Early microcode" method explained directly below. If however you wish to continue using microcode-ctl please skip to the "Microcode-ctl" section near the bottom of this page.

  4. (0) 1.0.2k^d {M}(~)1.1.0e(0/1.1)^d

    Curly brackets { } around the Mask  =>  {M}
    The version was originally masked in $PORTDIR/profiles/package.mask, but this was locally changed in /etc/portage/package.unmask.
    Eix indicates you have manually unmasked openssl-1.1.0e in /etc/portage/package.unmask

    Remove that configuration.

     

    Reference: eix manpage

  5. Compiling puts an extended heavy load on CPU generating heat which laptops are not designed for.

    There is the potential for thermal overload causing the laptop to shutdown.

    Reduce -j setting, cpu throttling reduce load but increase build time, and cool pad may be necessary to workaround overheating.

    You would want a minimal install with a lightweight desktop environment like lxde.

    Vivaldi install is sourced from binary deb and virtualbox-bin version is binary so no compiling is necessary for them.

  6. The conversion to meta-repo from ports-2012 downgrades xorg-server from 1.19.1_p20170228 to 1.17.4-r1
    You manually removed xorg-server-1.19.1_p20170228 which was being replaced with xorg-server-1.17.4-r1

    Due to the file collision you haven't finished installing x11-base/xorg-server-1.17.4-r1
     
    I had the same file collision error that prevented xorg-server from updating.

    # mv /usr/share/X11/xorg.conf.d/10-evdev.conf /usr/share/X11/xorg.conf.d/10-evdev.conf~
    

    No file collision after rename, install of xorg-server-1.17.4-r1 should succeed.
    Before starting Xorg check for /usr/share/X11/xorg.conf.d/10-evdev.conf
    If you start xorg-server without 10-evdev.conf the mouse won't move the cursor.
    On my system it didn't exist, I rename 10-evdev.conf~ back to 10-evdev.conf

    # mv /usr/share/X11/xorg.conf.d/10-evdev.conf~ /usr/share/X11/xorg.conf.d/10-evdev.conf
    

    After the update is finished:
    funtoo rj # eix -I xorg-server
    x11-base/xorg-server [1]
    Available versions: 1.17.4(0/1.17.4) 1.17.4-r1(0/1.17.4) {dmx doc glamor ipv6 kdrive libressl minimal nptl selinux static-libs +suid systemd tslib +udev unwind wayland xephyr xnest xorg xvfb}
    Installed versions: 1.17.4-r1(0/1.17.4)(07:05:44 PM 07/27/2017)(glamor ipv6 nptl suid udev xorg -dmx -doc -kdrive -libressl -minimal -selinux -static-libs -systemd -tslib -unwind -wayland -xephyr -xnest -xvfb)
    Homepage: http://xorg.freedesktop.org/
    Description: X.Org X servers

    [1] "xorg-kit" /var/git/meta-repo/kits/xorg-kit

     

    funtoo rj # equery list -po x11-base/xorg-server
     * Searching for xorg-server in x11-base ...
    [--O] [  ] x11-base/xorg-server-1.17.4:0/1.17.4
    [i-O] [  ] x11-base/xorg-server-1.17.4-r1:0/1.17.4
     

  7. Your system should not be trying to emerge dev-libs/openssl-1.1.0e

     

    dev-libs/openssl-1.1.0e is masked by portage:

     

    /var/git/meta-repo/kits/core-kit/profiles/package.mask/00-gentoo

     

    # Lars Wendler <polynomial-c@gentoo.org> (26 Aug 2016)
    # Masked while being tested and reverse deps aren't fully compatible
    =dev-libs/openssl-1.1*

     

     On  my systems Installed versions: openssl-1.0.2k, Available versions: [M](~)1.1.10e [M] indicates masked.

    funtoo rj # eix -I openssl
    dev-libs/openssl
         Available versions:  
         (0.9.8) 0.9.8z_p8^d
         (0)    (~)1.0.2g-r1(0/1.0.2g)^d[1] 1.0.2k^d [M](~)1.1.0e(0/1.1)^d
           {+asm bindist gmp kerberos rfc3779 sctp sslv2 +sslv3 static-libs test (+)tls-heartbeat vanilla zlib ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32" CPU_FLAGS_X86="sse2"}
         Installed versions:  1.0.2k^d[?](12:49:14 PM 01/30/2017)(asm sslv3 tls-heartbeat zlib -bindist -gmp -kerberos -rfc3779 -sctp -sslv2 -static-libs -test -vanilla ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32" CPU_FLAGS_X86="sse2")
         Homepage:            http://www.openssl.org/
         Description:         full-strength general purpose cryptography library (including SSL and TLS)
     

  8. Emerge xorg-server and xorg-drivers:

    # emerge -av =x11-base/xorg-server-1.17.4-r1 =x11-base/xorg-drivers-1.17
    

    If you get any file collision errors preventing install temporarily rename the file.
    I had an error with 10-evdev.conf on both my systems.
    Temporarily remove libcryptui to resolve gnupg slot conflict.

    # emerge -Ca libcryptui
    
    # emerge world -uDNav --verbose-conflicts --backtrack=30
    

    After completion of building all other packages reinstall libcryptui.

  9. On my updated i686 meta-repo current system "emerge --info" shows 

    PYTHON_SINGLE_TARGET="python3_4" 

    PYTHON_TARGETS="python2_7 python3_4"

    rrdtool was the only package that wouldn't resolve on my system because PYTHON_SINGLE_TARGET="python2_7 python3_4 -python3_5" and it's only allowed exactly-one-of python2_7 or python3_4 not both.

     

    If this works:

    PYTHON_SINGLE_TARGET="python3_4" emerge -pv rrdtool
    

    then use this configuration

    echo "net-analyzer/rrdtool PYTHON_SINGLE_TARGET: -* python3_4" >> /etc/portage/package.use/rrdtool
    

    If this works:

    PYTHON_SINGLE_TARGET="python2_7" emerge -pv asciidoc
    

    then use this configuration

    echo "app-text/asciidoc PYTHON_SINGLE_TARGET: -* python2_7" >> /etc/portage/package.use/asciidoc
    

    If this works:

    PYTHON_SINGLE_TARGET="python3_4" emerge -pv lensfun
    

    then use this configuration

    echo "media-libs/lensfun PYTHON_SINGLE_TARGET: -* python3_4" >> /etc/portage/package.use/lensfun
    
  10. How to change the xorg-kit from 1.17-prime to master?
     

    # cd /var/git/meta-repo/kits/xorg-kit
    # git branch
    * (HEAD detached at 52fa72a)
      1.17-prime
    # git checkout 1.17-prime
    Switched to branch '1.17-prime'
    Your branch is up-to-date with 'origin/1.17-prime'.
    # git branch 
    * 1.17-prime
    # git checkout master
    Branch master set up to track remote branch master from origin.
    Switched to a new branch 'master'
    # git branch
      1.17-prime
    * master
    

    git branch lists the tracked branch's with * in front of the current branch.
    git checkout <branch name> changes the current branch to <branch name>
    Switch back to 1.17-prime:

    # git checkout 1.17-prime
    Switched to branch '1.17-prime'
    Your branch is up-to-date with 'origin/1.17-prime'.
    # git branch
    * 1.17-prime
      master
    
  11. biber-2.5 will not work with dev-lang/perl-5.22.2 due to dependency on
    Unicode::Collate' => '1.14' and 'Unicode::Normalize' => '1.25'
    virtual/perl-Unicode-Collate-1.140.0-r2 and virtual/perl-Unicode-Normalize-1.250.0-r2 require dev-lang/perl-5.24.0-r2
     

    funtoo rj # equery g virtual/perl-Unicode-Collate-1.140.0-r2
    * Searching for perl-Unicode-Collate1.140.0-r2 in virtual ...
    
    * dependency graph for virtual/perl-Unicode-Collate-1.140.0-r2
    `-- virtual/perl-Unicode-Collate-1.140.0-r2 ~x86
    `-- dev-lang/perl-5.24.0-r2 (=dev-lang/perl-5.24*) ~x86
    `-- perl-core/Unicode-Collate-1.140.0 (~perl-core/Unicode-Collate-1.140.0) [~x86 keyword]
    [ virtual/perl-Unicode-Collate-1.140.0-r2 stats: packages (3), max depth (1) ]
    
    
    funtoo rj # equery g virtual/perl-Unicode-Normalize-1.250.0-r2
    * Searching for perl-Unicode-Normalize1.250.0-r2 in virtual ...
    
    * dependency graph for virtual/perl-Unicode-Normalize-1.250.0-r2
    `-- virtual/perl-Unicode-Normalize-1.250.0-r2 ~x86
    `-- dev-lang/perl-5.24.0-r2 (=dev-lang/perl-5.24*) ~x86
    `-- perl-core/Unicode-Normalize-1.250.0 (~perl-core/Unicode-Normalize-1.250.0) [~x86 keyword]
    [ virtual/perl-Unicode-Normalize-1.250.0-r2 stats: packages (3), max depth (1) ]
    

     

  12. According to these comments substantial work is required before the kde shard could be updated.

    Create a task report at bugs.funtoo.org for more information if needed.

     

     

     

    # IMPORTANT ----

    #

    # You are not allowed to update a shard without following our SQA Plan. Currently, that involves doing a detailed analysis of the quality

    # of the EXISTING (active) shard, then identifying issues that need to be addressed, and then defining how a shard bump will FIX or IMPROVE

    # these issues. And you MUST have your analysis reviewed and approved by the BDFL, and just blindly bumping a shard is probably NOT the

    # best solution

     

    # kde: d33259410e3eb1b0330698520796cb927ac596e7 (Updated 25 Feb 2017)

  13. Couldn't find include 'Gsf-1.gir' (search path: '[u'/usr/share/gdm/gir-1.0', u'/var/lib/menu-xdg/gir-1.0', u'/usr/local/share
    /usr/share/gobject-introspection-1.0/Makefile.introspection:155: recipe for target 'Abi-3.0.gir' failed
    

    Reinstall libgsf and gobject-introspection:

    emerge -1av libgsf gobject-introspection
    
    

    Try building abiword-3.0.1

    emerge -av =app-office/abiword-3.0.1
    

    If you need more help use wgetpaste to upload the build.log and post the link.

    abiword-3.0.1.log for my install on x86

    abiword-3.0.1.log for my install on ~amd64

×
×
  • Create New...