Jump to content
funtoo forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


walterw last won the day on April 30

walterw had the most liked content!

About walterw

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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?
  3. 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
  4. 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
  5. Great, it looks like it got to the compile phase now! Thanks!
  6. 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
  7. 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
  8. 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?
  9. Thanks - I checked the gentoo wiki and will post back results after I rebuild the kernel. Walter
  10. 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
  11. Hi gingerbread, Thanks for your reply, I do not have that set and will try that now. Walter
  12. 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
  13. 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
  14. 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
  • Create New...