-
Posts
34 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Everything posted by engineer
-
I did an emerge --depclean, then an emerge --backtrack=500 @world >>> Installing (1 of 2) dev-libs/libxml2-2.9.8-r1::core-kit >>> Emerging (2 of 2) dev-util/itstool-2.0.6-r1::core-kit * itstool-2.0.6.tar.bz2 BLAKE2B SHA512 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking itstool-2.0.6.tar.bz2 to /var/tmp/portage/dev-util/itstool-2.0.6-r1/work >>> Source unpacked in /var/tmp/portage/dev-util/itstool-2.0.6-r1/work >>> Preparing source in /var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6 ... * Fixing shebang in /var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6/setup.py. * Fixing shebang in /var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6/setup.py.in. * Fixing shebang in /var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6/itstool. >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6 ... ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-silent-rules --docdir=/usr/share/doc/itstool-2.0.6-r1 --htmldir=/usr/share/doc/itstool-2.0.6-r1/html --libdir=/usr/lib64 checking for a BSD-compatible install... /usr/lib/portage/python3.6/ebuild-helpers/xattr/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether /usr/bin/python3.6 version is >= 2.6... yes checking for /usr/bin/python3.6 version... 3.6 checking for /usr/bin/python3.6 platform... linux checking for /usr/bin/python3.6 script directory... ${prefix}/lib64/python3.6/site-packages checking for /usr/bin/python3.6 extension module directory... ${exec_prefix}/lib64/python3.6/site-packages checking for python module libxml2... found checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating itstool config.status: creating itstool.1 config.status: creating its/Makefile config.status: creating setup.py >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6 ... make -j5 Making all in its make[1]: Entering directory '/var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6/its' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6/its' make[1]: Entering directory '/var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6' >>> Source compiled. >>> Test phase [not enabled]: dev-util/itstool-2.0.6-r1 >>> Install itstool-2.0.6-r1 into /var/tmp/portage/dev-util/itstool-2.0.6-r1/image category dev-util make -j5 DESTDIR=/var/tmp/portage/dev-util/itstool-2.0.6-r1/image install Making install in its make[1]: Entering directory '/var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6/its' make[2]: Entering directory '/var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6/its' make[2]: Nothing to be done for 'install-exec-am'. /bin/mkdir -p '/var/tmp/portage/dev-util/itstool-2.0.6-r1/image/usr/share/itstool/its' /usr/lib/portage/python3.6/ebuild-helpers/xattr/install -c -m 644 docbook.its docbook5.its its.its mallard.its ttml.its xhtml.its '/var/tmp/portage/dev-util/itstool-2.0.6-r1/image/usr/share/itstool/its' make[2]: Leaving directory '/var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6/its' make[1]: Leaving directory '/var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6/its' make[1]: Entering directory '/var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6' make[2]: Entering directory '/var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6' /bin/mkdir -p '/var/tmp/portage/dev-util/itstool-2.0.6-r1/image/usr/bin' /bin/mkdir -p '/var/tmp/portage/dev-util/itstool-2.0.6-r1/image/usr/share/man/man1' /usr/lib/portage/python3.6/ebuild-helpers/xattr/install -c itstool '/var/tmp/portage/dev-util/itstool-2.0.6-r1/image/usr/bin' /usr/lib/portage/python3.6/ebuild-helpers/xattr/install -c -m 644 itstool.1 '/var/tmp/portage/dev-util/itstool-2.0.6-r1/image/usr/share/man/man1' make[2]: Leaving directory '/var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6' make[1]: Leaving directory '/var/tmp/portage/dev-util/itstool-2.0.6-r1/work/itstool-2.0.6' >>> Completed installing itstool-2.0.6-r1 into /var/tmp/portage/dev-util/itstool-2.0.6-r1/image * Final size of build directory: 680 KiB * Final size of installed tree: 252 KiB ecompressdir: bzip2 -9 /usr/share/doc ecompressdir: bzip2 -9 /usr/share/man >>> Installing (2 of 2) dev-util/itstool-2.0.6-r1::core-kit >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. * After world updates, it is important to remove obsolete packages with * emerge --depclean. Refer to `man emerge` for more information. [/usr/src/linux]-> emerge --depclean * Always study the list of packages to be cleaned for any obvious * mistakes. Packages that are part of the world set will always * be kept. They can be manually added to this set with * `emerge --noreplace <atom>`. Packages that are listed in * package.provided (see portage(5)) will be removed by * depclean, even if they are part of the world set. * * As a safety measure, depclean will not remove any packages * unless *all* required dependencies have been resolved. As a * consequence of this, it often becomes necessary to run * `emerge --update --newuse --deep @world` prior to depclean. Calculating dependencies... done! >>> Calculating removal order... sys-kernel/debian-sources-lts selected: 4.9.161_p1 protected: none omitted: 4.9.168_p1 All selected packages: =sys-kernel/debian-sources-lts-4.9.161_p1 >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging (1 of 1) sys-kernel/debian-sources-lts-4.9.161_p1... * * To avoid automounting and auto(un)installing with /boot, * just export the DONT_MOUNT_BOOT variable. * * * Your boot partition was detected as being mounted as /boot. * Files will be installed there for debian-sources-lts to function correctly. * Packages installed: 1728 Packages in world: 68 Packages in system: 81 Required packages: 1728 Number removed: 1 * Messages for package sys-kernel/debian-sources-lts-4.9.161_p1: * * To avoid automounting and auto(un)installing with /boot, * just export the DONT_MOUNT_BOOT variable. * * GNU info directory index is up-to-date. [/usr/src/linux]-> emerge @world Calculating dependencies... done! WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: dev-libs/libxml2:2 (dev-libs/libxml2-2.9.9-r1:2/2::core-kit, ebuild scheduled for merge) conflicts with dev-libs/libxml2[python,python_targets_python2_7(-),python_targets_python3_4(-),python_targets_python3_5(-),python_targets_python3_6(-),-python_single_target_jython2_7(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),python_single_target_python3_6(+)] required by (dev-util/itstool-2.0.6-r1:0/0::core-kit, installed) >>> Auto-cleaning packages... >>> No outdated packages were found on your system.
-
[/etc/portage]-> emerge --rage-clean dev-util/itstool dev-libs/libxml2 dev-util/itstool selected: 2.0.6-r1 protected: none omitted: none dev-libs/libxml2 selected: 2.9.8-r1 protected: none omitted: none All selected packages: =dev-libs/libxml2-2.9.8-r1 =dev-util/itstool-2.0.6-r1 >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. >>> Unmerging (1 of 2) dev-util/itstool-2.0.6-r1... >>> Unmerging (2 of 2) dev-libs/libxml2-2.9.8-r1... >>> needed sym /usr/lib64/libxml2.so.2 >>> needed obj /usr/lib64/libxml2.so.2.9.8 * GNU info directory index is up-to-date. !!! existing preserved libs: >>> package: dev-libs/libxml2-2.9.8-r1 * - /usr/lib64/libxml2.so.2 * - /usr/lib64/libxml2.so.2.9.8 * used by /usr/bin/bijiben (app-misc/bijiben-3.30.3) * used by /usr/bin/brasero (app-cdr/brasero-3.12.2-r1) * used by /usr/bin/csslint-0.6 (dev-libs/libcroco-0.6.12-r1) * used by 139 other files Use emerge @preserved-rebuild to rebuild packages using these libraries
-
OK, got SSH working. Here's the output of emerge @world: WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: dev-libs/libxml2:2 (dev-libs/libxml2-2.9.9-r1:2/2::core-kit, ebuild scheduled for merge) conflicts with dev-libs/libxml2[python,python_targets_python2_7(-),python_targets_python3_4(-),python_targets_python3_5(-),python_targets_python3_6(-),-python_single_target_jython2_7(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),python_single_target_python3_6(+)] required by (dev-util/itstool-2.0.6-r1:0/0::core-kit, installed)
-
Without my kernel working properly, I'm having trouble getting the output. Might take a picture of the screen. But, what I did to try to get a kernel is to run a 'make clean' and 'make', then I was going to just genkernel and avoid the emerge. But - I get the old: mpihelp_add_1 multiple definitions problem. Didn't this go away about a decade ago? It has something to do with 'extern' vs 'static'. Why is this still happening?!?
-
One or more updates skipped due to dependency conflict: dev-libs/libxml2-2.9.9-r1 conflicts with dev-util/itstool-2.0.6-r1 This was on 'emerge @system' Anyone know the steps to resolve? Tried --backtrack=500 and even removing both. Also tried --emptytree
-
Where is gfxmode set when you do ego boot update?
engineer replied to engineer's topic in Dev Central
That did the trick! Thank you. -
Where is gfxmode set when you do ego boot update It keeps going to 640x480. Also when I build grub myself, the grub-mkconfig outputs a vastly different file than ego does. How can I fix this?
-
Install has more options and is designed for packages to use. Mkdir just makes a simple directory; it's like "install-lite".
-
I was getting "failed to connect to lvmetad", so I tried the (theoretically inert) fix of taking "noauto" away from my boot line in /etc/fstab. The error is gone. So I put the "noauto" back in, and it is still "fixed". Is there some one-time function that needs to read /boot when a new kernel is built?
-
Try emerge --autounmask-write x11-base/xorg-x11
-
Ah. "Things I could have been told YESTERDAY!" I didn't see the other one - was it there on the 18th? If I redo this install and gnupg fails I'm going to be pretty mad... have you done a simple core to desktop update on a core i5?
-
So I got the 11-20 stage3 for Haswell, removed /lib43,/usr/lib32, and /usr/src/lib32, removed lib32 from env.d and generated a new ld.so.conf. I had to emerge sys-kernel/{debian-sources-lts, genkernel, linux-firmware}, sys-firmware/intel-micocode, sys-apps/iucode_tool, and grub. This gave me a working Core, so (after a backup) I ran 'epro flavor desktop'. I was required to emerge dev-python/{pygments, pyyaml} [could this be included in desktop flavor?], and eselect fontconfig to add 60-liberation.conf (for some reason). Now the 'genkernel all' is failing on gnupg. I tried emerging app-crypt/gnupg but it didn't fix the error. The final error is 'Failed to compile the "" target'. The actual errors seem to revolve around statically linked apps requiring runtime libraries, which is why I went through the preamble above about having removed all the lib32s prior to first compile. I don't know how to resolve library issues here. Please help.
-
OK I fixed this. So I got into the grub editor and changed the name of the kernels manually to get it to boot. Then I did an ego boot update which failed. I then remembered the emerge grub part and did that. When I looked up it was like the matrix on my screen as a billion lines of code went by. Why doesn't make change the text color to shades of green when i use the --matrix option??!!? I used etc-update to merge /etc/default/grub changes. Now "ego boot update" worked, tho with warning I must digest. Things I notice: the search line has updated disk ID, and it found the old kernels which boot-update never did. Oh - and KDE doesn't start. /etc/conf.d/xdm has DISPLAYMANAGER="sddm" but there's plenty of --depclean stuff yet to be done. So thanks for the help, guys, I can boot again!! _Eng
-
My problems are these: I can't boot because grub lists an invalid efi file, and choosing it gives an error. So I boot a LiveCD and chroot in. When I run 'ego boot update' I get an "ERROR: couldn't find grub-probe" Emerge grub says "fails to validate /dev - may be a broken '/dev/fd'". I don't know how to fix this.
-
I don't know how to update the grub tho. The kernels in boot are all LTS 4.9.130, but grub.cfg says genkernel 4.14.12. I don't remember modifying grub.cfg so I wonder if there is a tool I need to run?
