Jump to content
funtoo forums

walterw

Members
  • Content Count

    30
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by walterw

  1. Resetting the UPS fixed it - is there anyway to do that in the future without resetting the UPS? Walter
  2. I have a CyberPower, CP1500 AVR, UPS that I had at one point working with funtoo; however, I noticed recently that communications have broken down and I can no longer even start upsdrvctl. /etc/nut/nut.conf MODE=standalone /etc/nut/ups.conf [CyberPowerUPS] driver = usbhid-ups port = auto vendorid = 0764 productid = 0501 product = CST135XLU serial = CR7HQ2008167 vendor = CPS # @see: https://raspberrypi.stackexchange.com/questions/66611/nut-cyberpower-data-stale pollinterval = 15 /etc/nut/upsd.conf (completely empty) /etc/nut/upsd.users [nut] password=SOMETHING upsmon master /etc/nut/upsmon.conf MONITOR CyberPowerUPS@localhost 1 nut SOMETHING master I have disconnected the USB cable and reconnected; however, I have yet to try resetting the UPS ... Walter
  3. I am just curious - what is the manual effort that Daniel and team perform? It seems there is some testing around that, can that by automated is what I'm getting at? Why can't there be rolling releases? I'm not complaining about the release process, but am trying to understand when the infra team prepares 1.3 or 1.4, what are they doing? Why must they do it by hand? I understand that Funtoo packages is a collection of software all developed at a different pace and that ebuilds have to be maintained to keep up with those packages. I'm looking for, how can we improve infrastructure to make this process better, more robust, etc.
  4. So, if I understand correctly, testing is based on the end user manually follows above steps and reporting any issues? Can any tasks be automated?
  5. I am wondering what is involved for testing releases such as the upcoming 1.4 release? Is it manual by the user base, automated, etc.? How can we help out? Thanks, Walter
  6. Hi all, I built squid 4.6 with both ssl and ssl-crtd enabled: net-proxy/squid qos tproxy ssl ssl-crtd htcp wccp wccpv2 caps And, after it is done building, I expect ssl_crtd to live in /usr/libexec or somewhere down there, but after doing: find / -type f | grep ssl | grep crtd I see nothing. Even with: find / -type f | grep crtd I too see nothing. I don't see any build errors I checked the squid documentation and everything I found still references ssl-crtd and /usr/libexec ... ssl_crtd. I see the answer: /usr/libexec/squid/security_file_certgen That is the default value, it apparently has moved and some of the documentation hasn't caught up. I'm leaving this here in case anyone else runs into the same problem. Walter
  7. Great, it looks like it got to the compile phase now! Thanks!
  8. When trying to install xorg-server, I get an error with GL: configure: error: Package requirements (glproto >= 1.4.17 mesa-gl >= 9.2.0) were not met: Package 'mesa-gl', required by 'virtual:world', not found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables GL_CFLAGS and GL_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. !!! Please attach the following file when seeking support: !!! /var/tmp/portage/x11-base/xorg-server-1.20.1-r1/work/xorg-server-1.20.1_build/config.log * ERROR: x11-base/xorg-server-1.20.1-r1::xorg-kit failed (configure phase): * econf failed * * Call stack: * ebuild.sh, line 92: Called src_configure * environment, line 3591: Called xorg-2_src_configure * environment, line 4644: Called autotools-utils_src_configure * environment, line 979: Called econf '--docdir=/usr/share/doc/xorg-server-1.20.1-r1' '--enable-shared' '--disable-static' '--disable-selective-werror' '--enable-ipv6' '--disable-debug' '--disable-dmx' '--disable-glamor' '--disable-kdrive' '--disable-libunwind' '--disable-xwayland' '--enable-record' '--enable-xfree86-utils' '--enable-dri' '--enable-dri2' '--enable-glx' '--disable-xcsecurity' '--disable-xephyr' '--disable-xnest' '--enable-xorg' '--enable-xvfb' '--enable-config-udev' '--without-doxygen' '--without-xmlto' '--without-systemd-daemon' '--disable-systemd-logind' '--disable-suid-wrapper' '--enable-install-setuid' '--enable-libdrm' '--sysconfdir=/etc/X11' '--localstatedir=/var' '--with-fontrootdir=/usr/share/fonts' '--with-xkb-output=/var/lib/xkb' '--disable-config-hal' '--disable-linux-acpi' '--without-dtrace' '--without-fop' '--with-os-vendor=Gentoo' '--with-sha1=libcrypto' * phase-helpers.sh, line 718: Called __helpers_die 'econf failed' * isolated-functions.sh, line 121: Called die * The specific snippet of code: * die "$@" * * If you need support, post the output of `emerge --info '=x11-base/xorg-server-1.20.1-r1::xorg-kit'`, * the complete build log and the output of `emerge -pqv '=x11-base/xorg-server-1.20.1-r1::xorg-kit'`. * The complete build log is located at '/var/tmp/portage/x11-base/xorg-server-1.20.1-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-base/xorg-server-1.20.1-r1/temp/environment'. * Working directory: '/var/tmp/portage/x11-base/xorg-server-1.20.1-r1/work/xorg-server-1.20.1_build' * S: '/var/tmp/portage/x11-base/xorg-server-1.20.1-r1/work/xorg-server-1.20.1' >>> Failed to emerge x11-base/xorg-server-1.20.1-r1, Log file: >>> '/var/tmp/portage/x11-base/xorg-server-1.20.1-r1/temp/build.log' * Messages for package x11-base/xorg-server-1.20.1-r1: I commented out glamor support to see if that might have an effect: /etc/portage/package.use/x11 media-libs/mesa bindist -gallium -d3d9 -llvm #x11-base/xorg-server glamor x11-base/xorg-server -glamor x11-drivers/xf86-video-ati -glamor I thought I came across an article about 1.4-release and how it changes the GL implementation. If I am remembering or interpreting correctly, I don't believe this will work easily until 1.4-release. Is that accurate, or is there a quick-fix to get up and running? Thanks, Walter
  9. I also have pycharm installed and yes, it is 2018.2.4. Not the latest and greatest. If you look in git: find /var/git/meta-repo/kits/dev-kit/dev-util/pycharm-community -type f | grep \\.ebuild$ You will only see 2018.2.1 and 2018.2.4. Then, if you go to github.com or checkout the other branches, you will see 1.4-release has the latest version. I don't fully understand the methodology behind the releases and what testing takes place before the latest and greatest ebuilds get included into funtoo kits, but they don't track gentoo 1:1. If you are feeling lucky or have patience, you can configure /etc/ego.conf to use a specific branch, ie. 1.4-release to get the latest. Just be aware that, that has cascading effects ... Walter
  10. If I am using the 1.4 generic 64-bit stage 3 tarball, that will already be referencing the 1.4 branches, correct? Will most things build under 1.4 without changing my use flags and other settings?
  11. Thanks - I checked the gentoo wiki and will post back results after I rebuild the kernel. Walter
  12. Hi gingerbread, I set that, rebuilt my kernel, modules, and installed it, but I still have no touchpad. I did have to manually modprobe hid-alps as it wasn't loaded by default; however, manually loading it had no impact. I am wondering if perhaps it would work if there were a corresponding x11 config file somewhere telling it to use it? But I am also not sure that matters because my /proc/bus/input/devices doesn't show any touchpad devices. I believe it works in Ubuntu, so I will have to keep comparing what the kernel supports versus what I have built in my kernel ... Thanks, Walter
  13. Hi gingerbread, Thanks for your reply, I do not have that set and will try that now. Walter
  14. Hi digifuzzy, Good call - I think you are most certainly right, I checked and I do not have x11-drivers/xf86-input-synaptics installed, nor the use flags with synaptics (which probably pulls that in). I'm building now and will report back :). Thanks, Walter
  15. Hi all, I am having difficulty getting the touchpad working on my laptop - if I boot up to Ubuntu, it works fine. I played around with removing modules to semi isolate which modules I need and have deduced that I need at least: i2c_hid hid_multitouch When I remove those on Ubuntu, the touchpad stops working. However, merely having those built and available on my funtoo installation is insufficient. I also tried copying the xorg.conf.d/*.conf files for anything resembling input devices and that also did not work (after restarting X11). I will play around more with other kernel modules. I am trying to dig through lspci to see if I'm missing something but it isn't entirely clear to me, perhaps this might be what I need support: Communication Controller: Intel Corporation Point-LP CSME HECI #1 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) Thanks, Walter
  16. Hi, I am starting with a base release 1.3 64-bit image and getting this message throughout my build process: Unavailable repository 'gentoo' referenced by masters entry in '/var/git/met a-repo/kits/rust-kit/metadata/layout.conf' It appears whenever I am calling equery l <package-atom>, I am getting this error. Any ideas what might be causing this? Thanks, Walter
  17. Hi all, I built a java-based application that can build Gentoo / Funtoo / Ubuntu (and other Debian-based) systems from within any Linux distribution that has Java installed. The source code is here: https://github.com/walterjwhite/linux-builder And, I have a corresponding "system" to build an image: https://github.com/walterjwhite/funtoo-linux Caveats: 1. I will be updating the code on github as all of the dependencies for the linux-builder project are about a year old. There is no documentation, this needs to be written for anyone to use. 2. My own systems are much more complicated than the sample system there. This is meant to showcase what you CAN do. Furthermore, there is also no documentation as to what patches are available, this needs written. a. a "system" contains patches b. a "patch" contains all the changes necessary for that single patch unit. This could be copying files, creating a user, group, adding a service to a runlevel, installing packages, etc. Patches that are inter-related are linked through "dependencies". This ensures the base patch is installed first so if those files or libraries, etc. are needed, they will be installed prior to installing this patch. It is meant to be as generic as possible so if you want to prepare a configuration for Gentoo and want to translate that to Ubuntu, you can with ease (provided you know the package names and configuration directory). c. a "phase" can be setup, build, update, finalize and provides hooks at various stages of the build process. Say for instance, you need to download a file before you attempt to unpack and install it, you would create a download item in the setup phase. I've been using this system for about 3 years now and my goals are / were to: 1. make it easier to get started with Gentoo / Funtoo 2. allow users to switch across distributions whilst having the same applications, configuration, etc. partially supported, each distribution tends to put files in different places and has different package names thus requiring the packages listed in add-packages to be updated as well as the configuration files to be in the right place 3. share this utility with other linux users (Gentoo, Funtoo, etc.) and see what others' interests were and how this might help them to accomplish those goals 4. allow users to backup their systems easily and restore them to a pristine state 5. provide a means to capture all the patches applied to a system provided in an earlier release, and not currently implemented (relied on python and latex to generate PDF files describing the system) Thanks for your feedback, Walter
  18. Hi cardinal, My distfiles are downloaded to /var/cache/portage/distfiles as best as I can tell and it is installing genkernel-next-68. I overwrote my logs, so I don't have the original message, but here is my /etc/make.conf (it is automatically generated, so I apologize for all the lines, they're organized by patches): http_proxy="http://localhost:8118" CHOST="x86_64-pc-linux-gnu" CFLAGS="-march=x86-64 -O2 -pipe" CXXFLAGS="-march=x86-64 -O2 -pipe" CPU_FLAGS_X86="mmx mmxext sse sse2" MAKEOPTS="-j5" USE="" VIDEO_CARDS="" SANE_BACKENDS="" LINGUAS="" # kernel USE="${USE} symlink -fortran -openmp acpi" # funtoo-network USE="${USE} -networkmanager" # compression USE="${USE} zlib minizip" # lvm USE="${USE} lvm device-mapper" # permissions USE="${USE} pam caps filecaps" # cups USE="${USE} cups" # ext4 USE="${USE} ext4" # luks USE="${USE} cryptsetup" # zsh USE="${USE} zsh-completion" # english LINGUAS="${LINGUAS} en" # compression USE="${USE} lz4" I could remove the symlink and uninstall the kernel and try to reproduce it? Also, for genkernel, I do have a custom init + scripts, so that could be a potential concern, but I also grepped there and do not see anything that'd point to /usr/share/genkernel/src. The error message was for genkernel-next only and it was after building the kernel and modules. I think it was during the initramfs phase. EDIT: I am building a different system that uses ZFS and as such requires an earlier kernel, interestingly enough, that kernel built just fine along with the initramfs (no error messages about files not being in /usr/share/genkernel/src, and that directory does not exist). The one that built is: 4.14.80 and the one that wasn't was 4.19.1. Now, before I upgraded to 1.3-release, the last time I built the other system, it was actually using the 4.20 kernel, so the portage trees must have been different. Furthermore, the last time I built this system, it was actually using the 4.14.90 kernel. I'll have to investigate in more detail, maybe that will shed some light onto what is really going on.
  19. I am trying to build / install funtoo from a stage 3 tarball using the latest 1.3-release and hitting a snag with kernel compilation. All other packages (from what I can tell) are being properly fetched to /var/cache/portage/distfiles and installed. During the kernel compilation (specifically, when generating the initramfs), I'm getting an error: Could not find source tarball /usr/share/genkernel/src/open-iscsi-2.0-872.tar.gz. Please refetch. This is occurring for any files that are required for the init such as busybox and open-iscsi (which oddly enough should not be in my init), I manually copied a file there to see that it'd resolve it and it did just resolve that single one, but I don't want to do it piece meal. Now, the files are in distfiles (/var/cache/portage/distfiles) and I am thinking I can symlink /usr/share/genkernel/src/ to distfiles, but is that required or is there something else broken that is causing this? I did check the install guide and don't see anything alluding to that. I also grepped /etc for any such configuration also to no avail. EDIT: symlinking /usr/share/genkernel/src to /var/cache/portage/distfiles worked and I was able to install gentoo sources. Thanks, Walter
  20. Will funtoo be tracking upstream automatically or will there still be human intervention (even for current)? Also, along the same lines, I noticed that sometimes I have packages I cannot install because my kits don't have that package version available. Is there a utility that exists to perform that dependency check with the kit to ensure accuracy? I am on master so I would expect that to be manually revised / curated whereas 1.3 release would be automatic?
  21. Thanks - I tried that many times. I also started over with a new stage3. My systems with zfs in them all have this problem, the systems without do not. I have no idea why yet.
  22. Thanks - the bug report is closed, what are the next steps for this?
  23. I am attempting to update my systems and for whatever reason, when running: emerge --newuse -uD world -vp mips-sources is complaining of eapi7-ver: EAPI=5 not supported. I don't have mips-sources installed and I'm on an x86/64 system. Calculating dependencies / * ERROR: sys-kernel/mips-sources-4.13.16::nokit failed (depend phase): * eapi7-ver: EAPI=5 not supported * * Call stack: * ebuild.sh, line 603: Called source '/var/git/meta-repo/kits/nokit/sys-kernel/mips-sources/mips-sources-4.13.16.ebuild' * mips-sources-4.13.16.ebuild, line 27: Called inherit 'eapi7-ver' 'eutils' 'kernel-2' * ebuild.sh, line 294: Called __qa_source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' - * ebuild.sh, line 79: Called source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * eapi7-ver.eclass, line 62: Called die * The specific snippet of code: * die "${ECLASS}: EAPI=${EAPI:-0} not supported";; * * If you need support, post the output of `emerge --info '=sys-kernel/mips-sources-4.13.16::nokit'`, * the complete build log and the output of `emerge -pqv '=sys-kernel/mips-sources-4.13.16::nokit'`. * Working directory: '/usr/lib64/python2.7/site-packages' * S: '/var/tmp/portage/sys-kernel/mips-sources-4.13.16/work/linux--20171007' | * ERROR: sys-kernel/mips-sources-4.9.75::nokit failed (depend phase): * eapi7-ver: EAPI=5 not supported * * Call stack: * ebuild.sh, line 603: Called source '/var/git/meta-repo/kits/nokit/sys-kernel/mips-sources/mips-sources-4.9.75.ebuild' * mips-sources-4.9.75.ebuild, line 27: Called inherit 'eapi7-ver' 'eutils' 'kernel-2' * ebuild.sh, line 294: Called __qa_source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * ebuild.sh, line 79: Called source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * eapi7-ver.eclass, line 62: Called die * The specific snippet of code: * die "${ECLASS}: EAPI=${EAPI:-0} not supported";; * * If you need support, post the output of `emerge --info '=sys-kernel/mips-sources-4.9.75::nokit'`, * the complete build log and the output of `emerge -pqv '=sys-kernel/mips-sources-4.9.75::nokit'`. - * Working directory: '/usr/lib64/python2.7/site-packages' * S: '/var/tmp/portage/sys-kernel/mips-sources-4.9.75/work/linux--20161216' \ * ERROR: sys-kernel/mips-sources-4.4.110::nokit failed (depend phase): * eapi7-ver: EAPI=5 not supported * * Call stack: * ebuild.sh, line 603: Called source '/var/git/meta-repo/kits/nokit/sys-kernel/mips-sources/mips-sources-4.4.110.ebuild' * mips-sources-4.4.110.ebuild, line 27: Called inherit 'eapi7-ver' 'eutils' 'kernel-2' * ebuild.sh, line 294: Called __qa_source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * ebuild.sh, line 79: Called source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * eapi7-ver.eclass, line 62: Called die * The specific snippet of code: * die "${ECLASS}: EAPI=${EAPI:-0} not supported";; * * If you need support, post the output of `emerge --info '=sys-kernel/mips-sources-4.4.110::nokit'`, * the complete build log and the output of `emerge -pqv '=sys-kernel/mips-sources-4.4.110::nokit'`. * Working directory: '/usr/lib64/python2.7/site-packages' * S: '/var/tmp/portage/sys-kernel/mips-sources-4.4.110/work/linux--20160123' ... done! Total: 0 packages, Size of downloads: 0 KiB WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: dev-python/urllib3:0 dev-python/urllib3-1.23:0/0::python-modules-kit, ebuild scheduled for merge conflicts with <dev-python/urllib3-1.23[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by dev-python/elasticsearch-py-6.3.0:0/0::python-modules-kit, installed Now, the interesting thing is, I only get this error when updating systems with ZFS, but those ebuilds don't appear to have changed recently. I'm running the default kits, but I also tried updating to 1.2 where possible, but that didn't seem to make any difference.
×
×
  • Create New...