Jump to content

Search the Community

Showing results for tags 'meta-repo'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Funtoo Discussion Forums
    • News and Announcements
    • General Discussion
    • Dev Central
    • Funtoo Hosting
    • Funtoo Infrastructure
  • Help Central
    • General Help
    • Installation Help
    • Portage Help
    • Desktop Help
    • Server Help
  • Funtoo Services

Blogs

  • drobbins' Blog
  • It's a Bear's life
  • haxmeister's Blog
  • psychopatch's Blog
  • 666threesixes666's Blog
  • decision theory
  • Chris Kurlinski's Blog
  • Sandro's Blog
  • danielv's Blog
  • Not So Stupid Admin Tricks
  • maldoror's Blog
  • andreawilson's Blog
  • Simple Step-by-Step Server Setup
  • saraedward's Blog
  • eusanpe
  • Linux Container Club - LXD/LXC's Blog
  • Funtoo Perl Hackers's Perl on Funtoo

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


freenode


github


web


First Name


Last Name


Location


Interests

Found 4 results

  1. I did not update my system for a long time and also missed the announcement for the meta-repo thing. I decided to update, read a lot of links from the forums etc. and ended up screwing up my build system. (for example this post ) # epro === Enabled Profiles: === arch: base build: (not set) subarch: (not set) flavor: (not set) mix-ins: (not set) === Python kit: === branch: 3.4-prime # emerge -vpuD --newuse @world !!! /etc/portage/make.profile is not a symlink and will probably prevent most merges. !!! It should point into a profile within
  2. Hi, I'm trying to update to meta-repo after discovering emerge --sync doesn't work anymore. I'm following the instructions at: https://github.com/funtoo/meta-repo and when I get to git submodule init it fails with fatal: No url found for submodule path 'repos.conf/kits/core-hw-kit' in .gitmodules I found something in a bug tracker response saying that it wasn't using submodules anymore, so I decided to push forward and see if it would work and got to USE="python_targets_${my_pyver/./_} python_single_target_${my_pyver/./_}" emerge -1 --nodeps ego which, along with any
  3. After following instructions to migrate to meta-repo here: https://github.com/funtoo/meta-repo I did this command: emerge -auDN @world --with-bdeps=y --verbose-conflicts --backtrack=50 This brought up many conflicts and blocked package problems. I solved the conflicts packages by removing, manually upgrading. I am still stuck with the blocked packages as following. What do I do to get my system up to date? I have tried unmerge all blocking packages (i.e. x11-proto/*) and emerge x11-base/xorg-proto-2018.4. After that I re-ran the command above. I still get the same errors. T
  4. Can /usr/portage be deleted now that /var/git/meta-repo stores all the ebuild info?
×
×
  • Create New...