gigabot3457

On my original issue, I ended up editing the ebuild for util-linux and changing the r2 to r1 on the shadow requirement for su. Recreated the manifest and I have gone on mostly fine. 70 packages to go in rebuilding world, but I think we can close this issue, for me, at least. Thanks for the help and advice.

Thanks, that got me back on the road again.

Fresh install seems to be the same: Sync successful and kits in alignment! :) livecd / # emerge -s e2fs [ Results for search key : e2fs ] Searching... * app-xemacs/efs Latest version available: 1.37 Latest version installed: [ Not Installed ] Size of files: 369 KiB Homepage: http://xemacs.org/ Description: Treat files on remote systems the same as local files License: GPL-2+ * sys-fs/e2fsprogs Latest version installed: 1.46.5 Homepage: http://e2fsprogs.sourceforge.net/ Description: Standard EXT2/EXT3/EXT4 filesystem utilities License: GPL-2 BSD * sys-libs/e2fsprogs-libs Latest version installed: 1.46.5 Homepage: http://e2fsprogs.sourceforge.net/ Description: e2fsprogs libraries (common error and subsystem) License: GPL-2 [ Applications found : 3 ] livecd / # emerge -1 sys-fs/e2fsprogs Calculating dependencies... done! emerge: there are no ebuilds to satisfy "sys-fs/e2fsprogs". livecd / # emerge -1 sys-fs/e2fsprogs Calculating dependencies... done! emerge: there are no ebuilds to satisfy "sys-fs/e2fsprogs". livecd / # I tried twice, just because I am still not entirely positive I am just not making a typo.

I made a couple steps forward and then hit a complaint about sys-fs/e2fsprogs blocking. Thinking I could get around it by removing e2fsprogs and just installing the new version, I removed the package. But upon trying to reinstall/update it, I have found that sys-fs/e2fsprogs no longer exist in the tree and I cannot install anything because the package is uninstallable. More I am just wonder if anyone else can confirm this. Tomorrow I will fire up a VM and install Funtoo on it, see if I hit a similar issue. Starting to wonder if this install is just cursed. Sorry for the numerous messages. emerge sys-fs/e2fsprogs /usr/lib/python3.9/site-packages/portage/package/ebuild/_config/KeywordsManager.py:140: UserWarning: /etc/portage/package.keywords is deprecated, use /etc/portage/package.accept_keywords instead warnings.warn(_("%s is deprecated, use %s instead") % Calculating dependencies... done! emerge: there are no ebuilds to satisfy "sys-fs/e2fsprogs". emerge: searching for similar names... emerge: Maybe you meant any of these: sys-fs/xfsprogs, sys-fs/reiserfsprogs, sys-fs/btrfs-progs?

[ebuild U ] sys-devel/binutils-2.36.1_p3-r1:2.36::core-kit [2.36.1_p3:2.36::core-kit] USE="gold nls plugins -64-bit-bfd -cet -default-gold -doc -multitarget -static-libs -test -vanilla" 0 KiB [ebuild U ] sys-libs/binutils-libs-2.36.1_p3-r1::core-kit [2.36.1_p3::core-kit] 0 KiB [blocks b ] <sys-libs/binutils-libs-2.36.1_p3-r1 ("<sys-libs/binutils-libs-2.36.1_p3-r1" is blocking sys-devel/binutils-2.36.1_p3-r1) Well I got to this point and I am cross-eyed. I do not feel good about trying to unmerge binutils. Maybe the exclude will help here. I will look at it later. Thanks again.

Exclude is probably what I was trying to remember and could not. The downside to not having too many issues is these things leave my realm of recollection. Just got back up after having my mobo die for reasons shortly after my last response and still trying to get a drive change to work as I want. Just did an ego sync and will work through the blocking packages in emerge -auDN @world. Things are in a lot better shape and the Next update is overall going much better than 1.4 did for me. Honestly, I shot myself in the foot when binutils did not fully install and thought I would just extract the latest tarball, completely forgetting that /etc was mounted, not backed up recently and rather complex. I think my old mobo just died from the 1,000 reboots as I sorted all of that out. I appreciate the help and it does help a lot, because I really was not sure how to go about getting around it. End up just building trees of packages until they hit a stopping point. Meson seems to be them breaking old functionality to match their documented functionality and a bunch of Gnome packages not changing to match the documented function, yet. Possibly they're unmaintained now. Sometimes I just have to switch between Python version and rebuild to get something to work. Anyway, now that I am 98% working, I will just mess around some more this weekend on it. Thanks again.

Starting with a default make.conf, but I will see if I can figure out what is trying to pull the newer than possible release. Head scratching. I am working, just didn't finish the world update automatically. Now that I am functional, I will post config/logs, if I continue to have issues. Thanks.

I am updating a system that has gone about 6 months since last update. At some point binutils got hosed and I overwrote things with the stage3 tar file, to get out of that. I am almost back up, but util-linux is an issue and it is blocked by a version of a package that does not exist in my repo. The title says it, I have sys-apps/util-linux-2.38.1 installed and sys-apps/shadow 4.7-r1 installed. Portage is telling me that without shadow 4.7-r2, it cannot go on. I just did an ego sync and I do not have a shadow newer than what is already installed. I suspect there is a way out of this, but I am not finding it. I also cannot compile spidermonkey >v68 and have some issues with harfbuzz and the later version of Meson, but those are other issues that I will post separately if they persist. Any thoughts would be appreciated. Thanks

patch -p1 failed with /var/tmp/portage/kde-misc/kio-locate-0.6.0/files/kio-locate-0.6.0-gcc-4.7.patch ls /var/tmp/portage/kde-misc/kio-locate-0.6.0/files/ kio-locate-0.5.3-gcc-4.7.patch kio-locate-0.5.3-kf5port.patch I tried renaming the patch file, just in case it was that simple, and it goes further and then fails. So not that simple. Any thoughts, thanks in advance.

Thanks for your response. That probably would bypass the issue. Is 1.3 stable? I upgraded my processor to a 2nd Gen Ryzen and my existing kernel blew up, caused the machine to reboot rather early in the boot. I started to go down the path of 1.3 over my existing install, most likely unnecessarily, and was having a lot of issues, so I dropped back to 1.2. Of course I am not sure if it was because the recommended rescue CD had a kernel from 2016, but it was late at night, I saw signs of multilib issues, possibly from libraries laying around from the prior install, and I was just looking to get up and going. So I instead downloaded the latest Gentoo minimal install CD and Funtoo 1.2 and have progressed, with some small hiccups, until Mesa. I will make a snapshot of what I have and try 1.3. See if it progresses further. Everything else is working now, just no X, though I have not tried it. My goal had been to get back up and going quickly, as I had not expected to have issues. Thanks again, I will try and report back.

I ended up switching to 1.3. Had several new issues, mainly due to old libraries that were still lying around, but got around all of those and this one did not reappear, so I am marking this solved. My apologies if this has been discussed or I am being obtuse. I am trying to install Mesa 17.2.8, but it fails because I have LLVM 6 installed. It tries to use flags.setUnsafeAlgebra, which is replaced with flags.setFast in LLVM6, based on my reading. There is a patch to resolve this issue, by checking for LLVM 6 and using the proper flag, in that case. I applied it manually and managed to compile and install Mesa manually. I feel at one time I could tell Portage, etc, that I provided my own package for something, but I am not sure if that is the best path forward here. Certainly I can take the time to learn how to add patches to my own version of the ebuild, but I am not sure it is knowledge that I am going to use again or anytime soon. At least I hope this is not something I will have to do a lot. I am on Release 1.2, though if the easier fix is to get a newer mesa by going to 1.3, I am game. Time is scarce, so I was hoping to avoid a lot of issues. Can I get a newer version of Mesa on 1.2? I saw someone that grabbed a Gentoo ebuild and I can go that route, I would like an updated Mesa. Am I wrongly assuming the amount of work for rolling my own ebuild, with patch? Link to discussion on patch: https://lists.freedesktop.org/archives/mesa-dev/2017-November/175944.html I am not at the machine and overlooked giving my non-root account sudo access, so I am limited in what logs or info I can supply right now, but later today I will update this with whatever is requested, if that will help answer my question. Thanks in advance.