Jump to content
funtoo forums

savasten

Members
  • Content Count

    11
  • Joined

  • Last visited

  • Days Won

    1

savasten last won the day on April 6

savasten had the most liked content!

About savasten

  • Rank
    Member

Online

  • freenode
    savasten

Personal

  • Location
    Edgerton, KS, USA

Recent Profile Visitors

439 profile views
  1. Thanks to someone on the IRC I found the fix. It was suggested that I try changing my default shell back from zsh to bash and that fixed the issue. Now I just need to fix zsh. Thank you Command to change the default change the user default shell: chsh
  2. Yeah I did that. I may have hijacked this thread incorrectly. This error occurred after upgrading to 1.3 maintenance release 1.
  3. root filesytem total 112 drwxr-xr-x 20 root root 4096 May 30 11:16 . drwxr-xr-x 20 root root 4096 May 30 11:16 .. drwxr-xr-x 2 root root 4096 May 30 15:15 bin drwxr-xr-x 5 root root 4096 Dec 31 1969 boot drwxr-xr-x 19 root root 3500 Jun 4 22:08 dev drwxr-xr-x 102 root root 4096 Jun 4 22:08 etc drwxr-xr-x 3 root root 4096 May 30 08:56 home lrwxrwxrwx 1 root root 5 May 30 11:16 lib -> lib64 drwxr-xr-x 16 root root 12288 May 30 15:13 lib64 drwx------ 2 root root 16384 Dec 21 2016 lost+found drwxr-xr-x 6 root root 4096 May 30 08:56 mnt drwxr-xr-x 7 root root 4096 May 30 08:56 opt dr-xr-xr-x 130 root root 0 Jun 4 22:08 proc drwx------ 20 root root 4096 Jun 4 10:28 root drwxr-xr-x 23 root root 660 Jun 4 22:08 run drwxr-xr-x 2 root root 12288 May 30 15:13 sbin drwxr-xr-x 2 root root 4096 May 30 08:56 srv dr-xr-xr-x 13 root root 0 Jun 4 22:08 sys drwxrwxrwt 5 root root 20480 Jun 4 22:08 tmp -rwxr-xr-x 1 root root 168 Mar 25 2018 uns.sh drwxr-xr-x 13 root root 4096 May 30 08:56 usr drwxr-xr-x 15 root root 4096 May 30 17:03 var Home Directory total 12 drwxr-xr-x 3 root root 4096 May 30 08:56 . drwxr-xr-x 20 root root 4096 May 30 11:16 .. -rw-r--r-- 1 root root 0 May 30 08:56 .keep_sys-apps_baselayout-0 drwxr-xr-x 54 savasten savasten 4096 Jun 4 22:10 savasten
  4. Did either of you find a way to recover from this issue. I can boot to sddm and when I attempt to login the sessions freezes. Switch over to tty2 I can log in but PATH is not set properly. Also ROOTPATH returns blank. env-update does not seem to change anything, seems as the config file (is not being read) Questions: What should the default user PATH variables: /bin:/usr/bin:/usr/local/bin ......... Default ROOTPATH: ? Do you have any tips on troubleshooting this type of issue? Thank You Keith
  5. I believe that Funtoo has switched to a more stable release cycle (Not exactly, more like a break less stuff cycle). @drobbins has also released some great videos on his youtube channel for submitting put requests to have the community start helping with the updates.
  6. Looks like they are looking for help with the documentation. The new builds are located https://build.funtoo.org/1.3-release-std/
  7. This is telling you that you have an auto generated package.use file in that directory. Look in /etc/portage for a possible updated config file or files .cfg0000_package.use (note you may have a lot depending on how long it has been giving you that error). From a root or super user command prompt run: cd /etc/portage/ and then ls -al as then are hidden files. (filenames starting with a . are hidden) dispatch-conf is a tool designed to help update config files.
  8. Sorry for the questions? sshd running by default - did you file a bug report? Have you all checked out the youtube videos on contributing? Lets fix these things. We are Funtoo, @drobbins, @Oleg Vinichenko and other regulars are the directors. If it is broken fix it.
  9. All fixed had some issues with a few other bugs that have now been fixed. so all is good running 1.2. At least until i break it again. :)
  10. I understand but I got myself in a messy situation. I am having trouble staying at 1.2 due to running perl 5.28 and the changes that happened. I was running 5.28 then updated to 1.2 then the perl kit 5.28-release was depreciated. Kit system changes.
  11. !!! All ebuilds that could satisfy "gcc" have been masked. !!! One of the following masked packages is required to complete your request: - sys-devel/gcc-7.3.0::core-kit (masked by: corruption) - sys-devel/gcc-7.2.0::core-kit (masked by: corruption) - sys-devel/gcc-6.4.0::core-kit (masked by: corruption) - sys-devel/gcc-6.3.0::core-kit (masked by: corruption) - sys-devel/gcc-5.4.0-r1::core-kit (masked by: corruption) - sys-devel/gcc-5.4.0::core-kit (masked by: corruption) - sys-devel/gcc-5.3.0-r2::core-kit (masked by: corruption) - sys-devel/gcc-5.3.0-r1::core-kit (masked by: corruption) - sys-devel/gcc-4.9.4-r1::core-kit (masked by: corruption) - sys-devel/gcc-4.9.4::core-kit (masked by: corruption) - sys-devel/gcc-4.8.5-r1::core-kit (masked by: corruption) I have got my system in a very sorry state. Trying to run on 1.3. If i try and emerge gcc I get the previous errors not sure where to start. Updated portage, replaced the /var/git/meta-repo Any pointers would be great. Thank you
  12. Boot-update has been added into ego so you need to remove boot-update. I don't know all the details yet but they are coming out in time. Little more info here.
  13. I created a /etc/portage/package.accept_keywords file: # ego =app-admin/ego-2.6.0 ** I tried to emerge and hit a hard block that I need to work through. [ebuild U *] app-admin/ego-2.6.0::core-kit [2.4.2::core-kit] USE="-zsh-completion" PYTHON_SINGLE_TARGET="python3_6 -python3_4 -python3_5 -python3_7" PYTHON_TARGETS="python3_6 -python3_4 -python3_5 -python3_7" 158 KiB [blocks B ] sys-boot/boot-update ("sys-boot/boot-update" is blocking app-admin/ego-2.6.0) Total: 1 package (1 upgrade), Size of downloads: 158 KiB Conflict: 1 block (1 unsatisfied) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. (sys-boot/boot-update-1.9.0:0/0::core-kit, installed) pulled in by sys-boot/boot-update required by @selected (app-admin/ego-2.6.0:0/0::core-kit, ebuild scheduled for merge) pulled in by app-admin/ego required by @system ego >=app-admin/ego-1.1.3-r3 required by (sys-apps/portage-2.3.47:0/0::core-kit, installed)
  14. You need to add ego to ACCEPT_KEYWORDS in your /etc/portage/make.conf or create a /etc/portage/package.accept.keywords file. https://wiki.gentoo.org/wiki/ACCEPT_KEYWORDS I am still trying to figure out the correct syntax by referring to the prior link and the info from the post below.
  15. This may be a silly question but what is the purpose of this tool? Thank you Keith
×
×
  • Create New...