Jump to content
funtoo forums

All Activity

This stream auto-updates     

  1. Past hour
  2. I am trying to activate my mariadb database. After installting mariadb: [ebuild R ] dev-db/mariadb-10.4.6:0/18::core-server-kit USE="server -backup -bindist -client-libs -cracklib -debug -extraengine -galera -innodb-lz4 -innodb-lzo -innodb-snappy -jdbc -jemalloc -kerberos -latin1 -libressl -mroonga -numa -odbc -oqgraph -pam -perl -profiling -rocksdb (-selinux) -sphinx -sst-mariabackup -sst-rsync -static -systemd -systemtap -tcmalloc -test -tokudb -xml -yassl" 0 KiB [ebuild R ] virtual/mysql-5.6-r12:0/18::core-server-kit USE="server -embedded -static" 0 KiB After the installtion I wrote: emerge --config =dev-db/mariadb-10.4.6 and i got: Configuring pkg... * Trying to get password for mysql 'root' user from 'mysql' section ... /var/tmp/portage/dev-db/mariadb-10.4.6/temp/environment: line 4365: usr/libexec/mariadb/my_print_defaults: No such file or directory * Trying to get password for mysql 'root' user from 'client' section ... /var/tmp/portage/dev-db/mariadb-10.4.6/temp/environment: line 4365: usr/libexec/mariadb/my_print_defaults: No such file or directory /var/tmp/portage/dev-db/mariadb-10.4.6/temp/environment: line 4365: usr/libexec/mariadb/my_print_defaults: No such file or directory /var/tmp/portage/dev-db/mariadb-10.4.6/temp/environment: line 4365: usr/libexec/mariadb/my_print_defaults: No such file or directory /var/tmp/portage/dev-db/mariadb-10.4.6/temp/environment: line 4365: usr/libexec/mariadb/my_print_defaults: No such file or directory * Please provide a password for the mysql 'root'@'localhost' user now * or through the /root/.my.cnf file. * Avoid ["'\_%] characters in the password * Not entering a password defaults to UNIX authentication > * Retype the password > * Creating the mysql database and setting proper permissions on it ... * Command: usr/bin/mysql_install_db --basedir=/usr --loose-skip-grant-tables --loose-skip-host-cache --loose-skip-name-resolve --loose-skip-networking --loose-skip-slave-start --loose-skip-ssl --loose-skip-log-bin --loose-skip-relay-log --loose-skip-slow-query-log --loose-skip-external-locking --loose-skip-log-slave-updates --datadir=//var/lib/mysql --tmpdir=/ * ERROR: dev-db/mariadb-10.4.6::core-server-kit failed (config phase): * Failed to initialize mysqld. Please review /var/log/mysql/mysqld.err AND /var/tmp/portage/dev-db/mariadb-10.4.6/temp/mysql_install_db.log * * Call stack: * ebuild.sh, line 93: Called pkg_config * environment, line 4492: Called die * The specific snippet of code: * die "Failed to initialize mysqld. Please review ${EPREFIX}/var/log/mysql/mysqld.err AND ${TMPDIR}/mysql_install_db.log"; * * If you need support, post the output of `emerge --info '=dev-db/mariadb-10.4.6::core-server-kit'`, * the complete build log and the output of `emerge -pqv '=dev-db/mariadb-10.4.6::core-server-kit'`. !!! When you file a bug report, please include the following information: GENTOO_VM= CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm" JAVACFLAGS="" COMPILER="" and of course, the output of emerge --info =mariadb-10.4.6 * The complete build log is located at '/var/tmp/portage/dev-db/mariadb-10.4.6/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-db/mariadb-10.4.6/temp/environment'. * Working directory: '/var/tmp/portage/dev-db/mariadb-10.4.6/temp' * S: '/var/tmp/portage/dev-db/mariadb-10.4.6/work/mariadb-10.4.6' The output of file /var/tmp/portage/dev-db/mariadb-10.4.6/temp/mysql_install_db.log: sh: usr/bin/mysql_install_db: No such file or directory On my computer I have the file mysql_install_db at a different directory: /usr/share/mariadb/scripts/mysql_install_db Any idea how to solve this problem?
  3. Last week
  4. Earlier
  5. nrc

    1.4 stages

    Any special upgrade considerations for installs launched from the AWS AMI?
  6. Also note -- kde5-plasma *should* also merge cleanly. While I don't personally use this desktop environment, I have started testing plasma builds. Please report any issues you encounter.
  7. Hey everyone, Just wanted to let you know that as of last night, I am happily running GNOME 3.32 with no issues (I did need to fix librsvg to get SVG's to display properly, but after that, it's working great.) I successfully upgraded my dev workstation from 1.3 to 1.4. If you want to upgrade from 1.3, or install a fresh 1.4 using one of our 1.4 stages (now available for Intel only), things should work well. One thing to note, on both the beta 1.4 stages and a 1.3 upgrade, you will need to manually run "eselect python set --python3 python3.7" to set python3.7 to be the default python interpreter instead of 3.6. Our stages will be fixed to have this set already but this is not done yet. I will also include a copy of my post from another place on the forums about upgrading from 1.3: So, upgrade is pretty easy this time around.I will have instructions soon. But you can basically use "standard" upgrade steps. I recommend emerge -1 glibc gcc first, then emerge -auDN @world should generally work. Report any bugs related to upgrade like failed builds because often this can be fixed by tweaking dependencies. Overall the upgrade is MUCH easier than 1.2 -> 1.3. One trick is to remember to "eselect python set --python3 python3.7" after python-3.7 is emerged to make it default. Also, mesa right now is very picky about USE flags related to video card. For example, if you don't have a card that supports vulkan, you cannot have vulkan in USE. Same with xa and other things that were more "permissible" before. As of yesterday, I am now happily running gnome 3.32 and it is working perfectly. I would still call things "in beta" but the remaining issues (there is a "reboot doesn't work" issue currently active, due to a missing /run/initctl -> /dev/initctl symlink) should be worked out with minor package updates.
  8. So, upgrade is pretty easy this time around.I will have instructions soon. But you can basically use "standard" upgrade steps. I recommend emerge -1 glibc gcc first, then emerge -auDN @world should generally work. Report any bugs related to upgrade like failed builds because often this can be fixed by tweaking dependencies. Overall the upgrade is MUCH easier than 1.2 -> 1.3. One trick is to remember to "eselect python set --python3 python3.7" after python-3.7 is emerged to make it default. Also, mesa right now is very picky about USE flags related to video card. For example, if you don't have a card that supports vulkan, you cannot have vulkan in USE. Same with xa and other things that were more "permissible" before. As of yesterday, I am now happily running gnome 3.32 and it is working perfectly. I would still call things "in beta" but the remaining issues (there is a "reboot doesn't work" issue currently active, due to a missing /run/initctl -> /dev/initctl symlink) should be worked out with minor package updates.
  9. Ohh, that's nice. ^^
  10. I'm not using overlay to gcc, that is already available on 1.4.
  11. Which overlay do you use to emerge gcc 9.1?
  12. I always prefer make a new installation from stage3 and recompile all with the new gcc 9.1. I didn't upgrade from 1.3 yet.
  13. will need zero install for upgrade of 1.3 to 1.4???
  14. That worked great! Thanks for the detailed instructions, they worked first time, flawlessly. This has inspired me to try an --empty-tree which may take a couple of days on my Core i5 with 1800+ packages. I'm sure something will break and I'll be back. ;)
  15. I found the cause of surf crash. Actually I built xorg-server with the minimal flag set and after disabling this flag and rebuilt xorg-server again I could open pages that were causing crashes.
  16. The openssl patches for building those programs are in the next release branch of their respective kits. To build the programs now you have to temporarily add them to local patches. Click link, File/Save page as: telepathy-gabble-0.18.4-openssl-1.1.patch telepathy-salut-0.8.1-openssl-1.1.patch # mkdir -p /etc/portage/patches/net-voip/telepathy-{gabble,salut} # cp telepathy-gabble-0.18.4-openssl-1.1.patch /etc/portage/patches/net-voip/telepathy-gabble/ # cp telepathy-salut-0.8.1-openssl-1.1.patch /etc/portage/patches/net-voip/telepathy-salut/ # emerge -av telepathy-connection-managers
  17. Latest problem is net-voip/telepathy-gabble-0.18.4 and net-voip/telepathy-salute-0.8.1-r1 which are pulled in by net-in/telepathy-connection-managers-2-r2 I suspect openssl 1.1+ is messing them up, or some Apple defines that are messing up the structures. Anyone else running into this?
  18. Been doing automated tests all day today, adding fixes as I find things, and also added a fix so kde-plasma-5 should merge fine now.
  19. More fixes added for a bunch of build issues I detected overnight. Ibus, gnome-settings-daemon and mutter compilation without wayland enabled, and others. Will continue doing build tests over here to try to find any issues I can.
  20. Pulse-socket permissions explained in this closed upstream issue report: [Security] socket access granted to users outside auth-group
  21. I'm sandboxing some applications and I want to have a sound. I did what's written here: https://wiki.gentoo.org/wiki/Simple_sandbox#Configure_Firefox_to_output_sound_to_larry.27s_PulseAudio_daemon echo -e ".include /etc/pulse/default.pa\nload-module module-native-protocol-unix auth-anonymous=1 socket=/tmp/pulse-socket" > ~larry/.config/pulse/default.pa but I dont like that /tmp/pulse-socket has 777 (rwxrwxrwx) permissions. I found this link: https://gist.github.com/Earnestly/4acc782087c0a9d9db58 created pulseaudio user, added other users to that group and changed `auth-anonymous=1` to `auth-group=pulseaudio` but still I have 777 (rwxrwxrwx) permissions on /tmp/pulse-socket How can I change the permissions to e.g. 770? Is it even a good idea to "sandbox" webrowser or media player like that? (https://bugs.funtoo.org/browse/FL-6453)
  22. I found a last-minute bug related to xorg-server building with some new tweaks to mesa and libglvnd. I have applied some fixes and as of right now the tree is being regenerated. When you have the fixes, 'glvnd' global USE will be enabled with workstation or desktop profile. And you may need to re-emerge mesa-19.1 if xorg-server doesn't build. Since it's a beta, I won't always make things perfectly smooth -- that is the goal for the release 😉
  23. Everyone, 1.4-release is now in BETA -- GNOME 3.32 should now build and be ready to test. Please file bug reports for any bugs you encounter. Best, Daniel
  24. Thanks for the unhappy news, sure beats beating my head against the wall for hours or days.
  25. You can't upgrade to xorg-server-1.20.1-r1 and use nvidia-drivers-304.137 Trying to force it is a waste of time. Gentoo has removed nvidia-drivers-304.137.ebuild from their portage due to this. The easiest solution is to try nouveau although I'm reading reports that indicate nouveau doesn't work well with geforce 6150 If you can accept no 3d-acceleration the nv driver is another alternative. Otherwise to keep nvidia-drivers-304.137 you will have to mask >xorg-server-1.19.5 and every package from updating that is listed here: (x11-base/xorg-server-1.20.1-r1:0/1.20.1::xorg-kit, installed) pulled in by
  26. So I have done some more digging, I pulled out my mask so that I could get @world to finish up at the very least. I then removed the nvidia-drivers and here is where I sit when I try to install them now. emerge -av nvidia-drivers These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N #] x11-drivers/nvidia-drivers-410.93:0/410::core-hw-kit USE="X driver kms tools uvm -acpi -compat -gtk3 (-multilib) -static-libs -wayland" 0 KiB Total: 1 package (1 new), Size of downloads: 0 KiB The following mask changes are necessary to proceed: (see "package.unmask" in the portage(5) man page for more details) # required by nvidia-drivers (argument) # /etc/portage/package.mask: # http://www.nvidia.com/object/IO_32667.html nuttin over 304 =x11-drivers/nvidia-drivers-410.93 NOTE: The --autounmask-keep-masks option will prevent emerge from creating package.unmask or ** keyword changes. emerge --verbose-conflicts -av =x11-drivers/nvidia-drivers-304.137 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild UD ] x11-base/xorg-server-1.19.5-r2:0/1.19.5::xorg-kit [1.20.1-r1:0/1.20.1::xorg-kit] USE="glamor ipv6 udev xorg -debug -dmx -doc -kdrive -libressl -minimal (-selinux) -static-libs -suid% (-systemd) -tslib% -unwind -wayland -xcsecurity -xephyr -xnest -xvfb" 0 KiB [ebuild N ] x11-drivers/nvidia-drivers-304.137:0/304::core-hw-kit USE="X tools -acpi (-multilib) -pax_kernel -static-libs" 0 KiB Total: 2 packages (1 downgrade, 1 new), Size of downloads: 0 KiB !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: x11-base/xorg-server:0 (x11-base/xorg-server-1.19.5-r2:0/1.19.5::xorg-kit, ebuild scheduled for merge) pulled in by <x11-base/xorg-server-1.19.99:= required by (x11-drivers/nvidia-drivers-304.137:0/304::core-hw-kit, ebuild scheduled for merge) ^ ^^^^^^^ ^ (x11-base/xorg-server-1.20.1-r1:0/1.20.1::xorg-kit, installed) pulled in by =x11-base/xorg-server-1.20* required by (net-misc/tigervnc-1.9.0-r1:0/0::net-kit, installed) ^ ^^^^^ x11-base/xorg-server:0/1.20.1= required by (x11-drivers/xf86-video-vesa-2.4.0:0/0::xorg-kit, installed) ^^^^^^^^^^ x11-base/xorg-server:0/1.20.1= required by (x11-drivers/xf86-input-mouse-1.9.3:0/0::xorg-kit, installed) ^^^^^^^^^^ x11-base/xorg-server:0/1.20.1= required by (x11-drivers/xf86-input-evdev-2.10.6:0/0::xorg-kit, installed) ^^^^^^^^^^ x11-base/xorg-server:0/1.20.1= required by (x11-drivers/xf86-input-libinput-0.28.0-r1:0/0::xorg-kit, installed) ^^^^^^^^^^ x11-base/xorg-server:0/1.20.1= required by (x11-drivers/xf86-input-keyboard-1.9.0:0/0::xorg-kit, installed) Here are the relevant parts in the ebuild, I think just fixing the rdepend stuff in it will do what I need, but I imagine that this may need to be fixed upstream, to keep things working for others. COMMON=" app-eselect/eselect-opencl kernel_linux? ( >=sys-libs/glibc-2.6.1 ) tools? ( dev-libs/atk[${MULTILIB_USEDEP}] dev-libs/glib:2[${MULTILIB_USEDEP}] x11-libs/gdk-pixbuf[${MULTILIB_USEDEP}] x11-libs/gtk+:2[${MULTILIB_USEDEP}] x11-libs/libX11[${MULTILIB_USEDEP}] x11-libs/libXext[${MULTILIB_USEDEP}] x11-libs/pango[X,${MULTILIB_USEDEP}] x11-libs/pangox-compat[${MULTILIB_USEDEP}] ) X? ( >=app-eselect/eselect-opengl-1.0.9 ) " DEPEND="${COMMON} kernel_linux? ( virtual/linux-sources virtual/pkgconfig )" RDEPEND="${COMMON} acpi? ( sys-power/acpid ) tools? ( !media-video/nvidia-settings ) X? ( <x11-base/xorg-server-1.19.99:= >=x11-libs/libX11-1.6.2[${MULTILIB_USEDEP}] >=x11-libs/libXext-1.3.2[${MULTILIB_USEDEP}] sys-libs/zlib[${MULTILIB_USEDEP}] x11-libs/libXvMC[${MULTILIB_USEDEP}] ) " PDEPEND="X? ( >=x11-libs/libvdpau-0.3-r1[${MULTILIB_USEDEP}] )"
  27. Some Java components as JLabel, JButton and many others is not showing up on the JFrame. If I set a text to a button, it doesn't appear in the screen. I suspected that this issue is because the default font used by Java is not installed so I tried to change the font used in the components but once again it didn't show up anything. I checked if it was due to bad code or something like this but was not the case, also I used codes from the internet and none worked. I really don't have another idea of how to solve this and I'm worried because I need to practice Java UI due to I'm studying an OOP subject in the college. If someone help me I'd really appreciate.
  28. 1.4-release stages, currently in ALPHA, are available for download for all Intel 32-bit and 64-bit CPUs including generic_64: https://www.funtoo.org/Generic_64 Please give them a try. Right now, the core system is pretty solid but GNOME 3.32 doesn't merge yet, and we are expecting a major update to the GL subsystem prior to release. So things may be a bit bumpy in the desktop arena for now but for console-based stuff, the 1.4 builds should be pretty solid. Best, Daniel
  1. Load more activity
×
×
  • Create New...