Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

cardinal

Members
  • Posts

    490
  • Joined

  • Last visited

  • Days Won

    59

Posts posted by cardinal

  1.  

    The name [windowmaker-local] in this file:

    /etc/portage/repos.conf/windowmaker

    is different than the name windomaker-local in the profiles/repo_name and metadata/layout.conf in /home/overlays/windowmaker-local

    The reference name must be identical in all configuration files for the specific overlay.

  2. This issue is closed which would indicate it's resolved.

    [FL-11225] app-emulation/virtualbox-guest-additions-7.0.8 fails to emerge

    [FL-11225] is a sub-task of a larger still unresolved issue that is in Ready to Fix status.

    [FL-10669] virtualbox autogen has hit version 7.0 and the templates need maintenance.

     

     

  3. The issue is python3.9, the bug report has the details:

    FL-10643 [next]: equery has problems getting the use flags from ebuilds

    A workaround would be to install dev-lang/python-3.7.16,then use eselect python list, and eselect python set the [  ] by  python3.7 so it becomes [1]

    rj@funtoo-next ~ $ ego query v python
     dev-lang/python| slot|            repo
    ----------------+-----+----------------
         * 2.7.18-r1|     | python-kit/next
    ----------------+-----+----------------
            * 3.7.16|   /m| python-kit/next
    ----------------+-----+----------------
              3.8.16|     | python-kit/next
            * 3.9.16|     | python-kit/next
             3.10.11|     | python-kit/next
    rj@funtoo-next ~ $ eselect python list
    Available Python interpreters, in order of preference:
      [1]   python3.7
      [2]   python3.9
      [3]   python2.7 (fallback)

     

  4. Windowmaker will build on 1.4-release by temporarily switching the desktop-kit to 1.3-release branch.

    This method only works if 1.3-release branch still exists on desktop-kit from an in-place 1.3 to 1.4 release upgrade. 

    # cd /var/git/meta-repo/kits/desktop-kit/
    # git checkout 1.3-release

    Follow directions in output for dubious owner error:

    funtoo /var/git/meta-repo/kits/desktop-kit # git checkout 1.3-release
    fatal: detected dubious ownership in repository at '/var/git/meta-repo/kits/desktop-kit'
    To add an exception for this directory, call:
    
    	git config --global --add safe.directory /var/git/meta-repo/kits/desktop-kit
    funtoo /var/git/meta-repo/kits/desktop-kit # git config --global --add safe.directory /var/git/meta-repo/kits/desktop-kit
    funtoo /var/git/meta-repo/kits/desktop-kit # git checkout 1.3-release
    Switched to branch '1.3-release'

    Verify Windowmaker is available and emerge:

    funtoo /var/git/meta-repo/kits/desktop-kit # ego query v windowmaker
     x11-wm/windowmaker| slot|                    repo
    -------------------+-----+------------------------
                 0.95.7|    0| desktop-kit/1.4-release
              0.95.8-r1|     | desktop-kit/1.4-release
                   9999|     | desktop-kit/1.4-release
    
    funtoo /var/git/meta-repo/kits/desktop-kit # emerge -av windowmaker
    Calculating dependencies... done!
    [ebuild  N     ] x11-wm/windowmaker-0.95.8-r1::desktop-kit  USE="gif jpeg nls png tiff webp xinerama xpm -imagemagick -modelock -xrandr" 3,410 KiB
    
    Total: 1 package (1 new), Size of downloads: 3,410 KiB
    
    Would you like to merge these packages? [Yes/No] 

    After emerge completes:

    funtoo /var/git/meta-repo/kits/desktop-kit # git checkout 1.4-release 
    Switched to branch '1.4-release'

    If modified or un-tracked files prevent the checkout to 1.4-release the easiest solution is to delete desktop-kit.

    Running ego sync will download a clean replacement that only includes the 1.4-release branch.

    Attempting to emerge windowmaker on Next release would begin with importing x11-wm/windowmaker from 1.3-release desktop-kit into a local overlay

  5. * The specific snippet of code:
     *       cp -n "${FILESDIR}"/${PN}-2.20.0-tests-data/*.xml "${S}"/tests/data/ || die;

    In this case locate the ebuild, open in editor and insert a # in front of the offending snippet of code.

    Locate:

    rj@funtoo-next ~ $ ego query v at-spi2-atk
     app-accessibility/at-spi2-atk| slot|                      repo
    ------------------------------+-----+--------------------------
                          * 2.34.2|    2| gnome-kit/next-3.36-prime
    rj@funtoo-next ~ $ cd /var/git/meta-repo/kits/gnome-kit/app-accessibility/at-spi2-atk/
    

    Edit:

    rj@funtoo-next /var/git/meta-repo/kits/gnome-kit/app-accessibility/at-spi2-atk $ sudo nano at-spi2-atk-2.34.2.ebuild 
    src_prepare() {
            # Upstream forgot to put this in tarball, upstream #770615
       ---->#cp -n "${FILESDIR}"/${PN}-2.20.0-tests-data/*.xml "${S}"/tests/data/ || die
    
            gnome2_src_prepare
    }

    Merge:

    rj@funtoo-next /var/git/meta-repo/kits/gnome-kit/app-accessibility/at-spi2-atk $ sudo ebuild at-spi2-atk-2.34.2.ebuild merge

    Bug report:

    [gnome-kit] app-accessibility/at-spi2-atk-2.34.2 fails pkg_prepare

  6. Note wiki/talk:

    https://www.funtoo.org/Talk:Install/Profiles

    Bugs.funtoo.org Improvement:

    Running nouveau requires deleting etc/modprobe.d/nouveau-blacklist.conf

    If you choose to go with proprietary driver mixin profile gfxcard-nvidia-legacy should support your GT-420 

    https://code.funtoo.org/bitbucket/projects/AUTO/repos/core-gl-kit/browse/profiles/funtoo/mix-ins/gfxcard-nvidia-legacy/package.mask

    https://www.nvidia.com/Download/driverResults.aspx/196213/en-us/

    You would have to manually blacklist nouveau again to try out nvidia-390

  7. The core2 march profile is the next available stage3 that is a generation down from nehalem that excludes SSE4.1, SSE4.2, and POPCNT.

    core2

    Intel Core 2 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, CX16, SAHF and FXSR instruction set support.

    Reference: https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html

    Verify MMX, SSE, SSE2, SSE3, SSSE3, CX16, SAHF and FXSR would be enabled by gcc if you were using native (gcc autodetection of options supported by CPU).

    gcc -c -Q -march=native --help=target | grep enabled

    Reference: https://wiki.gentoo.org/wiki/GCC_optimization

    If all are not enabled default to generic_64 

×
×
  • Create New...