Jump to content
funtoo forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by jhan

  1. I would say that your are looking for the functionality of versionator.eclass or eapi7-ver.eclass. versionator.eclass can be found at https://code.funtoo.org/bitbucket/projects/AUTO/repos/gentoo-staging/browse/eclass/versionator.eclass eapi7-ver.eclass at https://code.funtoo.org/bitbucket/projects/AUTO/repos/gentoo-staging/browse/eclass/eapi7-ver.eclass
  2. I would say, looking at the code in the ebuild: REQUIRED_USE="?? ( elogind systemd )" CDEPEND=" >=dev-libs/glib-2.44:2 sys-auth/polkit elogind? ( >=sys-auth/elogind-229.4 ) introspection? ( >=dev-libs/gobject-introspection-0.9.12:= ) systemd? ( >=sys-apps/systemd-186:0= ) !systemd? ( !elogind? ( sys-auth/consolekit ) ) that it is more like that: - Either none or one of the required use USE flags need to be enabled but not both: https://devmanual.gentoo.org/ebuild-writing/variables/index.html#required_use - If USE flag systemd is set sys-apps/systemd is required - If USE flag elogind is set sys-auth/elogind is required - If systemd USE flag is not set and elogind USE flag is not set then sys-auth/consolekit is required So the question here is, why is the systemd USE flag triggered in the first place because the packages depending on accountservice sicota@farout /data/incoming $ equery d -a sys-apps/accountsservice * These packages depend on sys-apps/accountsservice: gnome-base/gdm-3.32.0 (>=sys-apps/accountsservice-0.6.12) gnome-base/gnome-control-center-3.32.2 (>=sys-apps/accountsservice-0.6.39) gnome-base/gnome-shell-3.32.2-r4 (>=sys-apps/accountsservice-0.6.14[introspection]) gnome-extra/cinnamon-desktop-3.6.2 (sys-apps/accountsservice) kde-plasma/user-manager-5.15.5 (sys-apps/accountsservice) kde-plasma/user-manager-5.16.1 (sys-apps/accountsservice) mate-base/mate-control-center-1.22.1 (accountsservice ? sys-apps/accountsservice) mate-extra/mate-polkit-1.22.0 (accountsservice ? sys-apps/accountsservice) mate-extra/mate-polkit-1.22.0-r1 (accountsservice ? sys-apps/accountsservice) x11-misc/lightdm-1.26.0-r1 (gnome ? sys-apps/accountsservice) x11-misc/lightdm-1.28.0 (gnome ? sys-apps/accountsservice) x11-misc/lightdm-1.30.0 (gnome ? sys-apps/accountsservice) x11-misc/mugshot-0.4.1 (sys-apps/accountsservice) sicota@farout /data/incoming $ do not require systemd to be set. And looking at the output of an emerge -pv kde-meta on my system the accountsservice line looks like: [ebuild N ] sys-apps/accountsservice-0.6.54-r1::gnome-kit USE="-doc -elogind -introspection (-selinux) (-systemd)" 91 KiB with systemd USE flag masked and elogind USE flag turned off. The mask for systemd is the default setting for the epro flavor "core" and also the mix-in no-systemd. To find out why the systemd USE flag is set we would need the output of: - epro - emerge -pv kde-meta
  3. That is interesting, as I see that field only in English, no matter which language I choose from the language menu.
  4. That can depend on many factors. Did you set PYTHON_SINGLE_TARGET or PYTHON_TARGETS somewhere? There are also some programs that still don't have the USE flag for python3_7 or just don't support it yet. But if your 'emerge -pv --depclean =dev-lang/python-3.6* ' output does not show more packages, that should not be the case.
  5. As plasma also has the wayland USE flag, I said it might be good to try to build the system without this USE flag first. To not have a "mixed state", where one part supports wayland and one not. As far as I know, wayland is not yet ready for "general use", there are too many things that don't work yet or still need the use of XWayland, depending on the desktop environment you want to use. Gnome seems to be working fine, KDE plasma e.g still has some problems (https://community.kde.org/Plasma/Wayland_Showstoppers) and no idea about the others. At the moment I wouldn't use it as my normal desktop, unless I have tested all applications under it first, probably on another computer. And if you say that Xorg+KDE seems to get stuck, how far does it get? How are you starting it? Any messages in the Xorg protocol or dmesg?
  6. The radeon driver is correct. The name of the driver is just radeon but it supports many different versions of similar cards: https://www.x.org/releases/current/doc/man/man4/radeon.4.xhtml
  7. If you can only start wayland but don't want or need it. You could etiher remove the wayland mix-in (which you inherited) or use the '-wayland' USE flag. That should at least give you you the possibility to to start plasma normally.
  8. That might be a good idea, as the VIDEO_CARDS setting in make.conf seems to have priority over the mix-ins setting. I tested that locally by adding the gfxcard-radeon mix-in but the USE flags for xorg-drivers and mesa only changed after I removed the VIDEO_CARDS line from make.conf. A 'emerge -pv mesa xorg-drivers' would probably enough to see if a rebuild would change anything.
  9. If you have set gfxcard-radeon as a mix-in, gallium-r600 is already set as VIDEO_CARDS: farout $ more /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/mix-ins/gfxcard-radeon/make.defaults # reference: # https://www.x.org/wiki/RadeonFeature/ # https://wiki.gentoo.org/wiki/Radeon # profile covers: r600 <= chipset <= N.Islands # GFX Core 4 and 5 VIDEO_CARDS="radeon r600 gallium-r600" USE="glamor vdpau vaapi" But so is radeon, which makes your mesa warning above look a bit suspicious but I see no profile setting that would disable it. Are you sure your local /etc/portage/ files don't accidentally contain anything that would disable it? And my guess for the r600g would be that that is the gallium-r600.
  10. Hi @upc0d3 Not sure if xorg-x11 is the opengl provider for your card but could be. @cardinal might be able to tell more. To get more output from glxgears you can use LIBGL_DEBUG=verbose glxgears You can also use glxinfo|grep DRI to see information about DRI usage. That should also be visible in the Xorg log file: cat /var/log/Xorg.0.log|grep DRI In that regard it would also be interesting to see what USE flags are used for mesa and xorg-drivers and what driver xorg is using. It might also help to have a look at the gentoo wiki page to see if there is something that might help.
  11. What does 'eselect opengl list' show?
  12. You could download the patch from https://code.funtoo.org/bitbucket/projects/AUTO/repos/core-kit/browse/sys-devel/gcc/files/svn-patches?at=refs%2Fheads%2F1.4-release
  13. The first question is where the cryptsetup USE flag for genkernel comes from. Installing debian-sources-lts with the binary USE flag does not require it, only the luks USE flag does. But as it says "installed" for genkernel, what is the output of 'emerge -pv genkernel'? If it wants to install it with the cryptsetup USE flag, try 'USE="-cryptsetup emerge -pv genkernel'. Another question would be if you want to have genkernel using the cryptsetup USE flag. If not, you should find out where it is coming from. If yes, using the mix-in encrypted-root works fine.
  14. If you created a funtoo account the login should be the same on all funtoo sites (as far as I know). The text "Not a member? To request an account, please contact your Jira administrators." on bugs.funtoo.org is misleading and should probably be changed. In the "Introduction" section directly below, the way to get access is described.
  15. If this is funtoo 1.4 then I wonder where the 32bit files come from. As you can see in the output all broken files are are looking for a 32bit version of the nvidia driver, which does not exist in funtoo 1.4. That is why you are always asked to install nvidia-drivers again.
  16. Try 'revdep-rebuild -pvi', that should give you more info.
  17. I did not mean the output of 'emerge --info'. I meant the output of the emerge that complained about json-c needing the static USE flag.
  18. json-c does not need the static-libs USE flag unless you have set static-libs for the package cryptsetup. Or use the mix-in encrypted-root. If that is not the case for you, please check the emerge output. There should be more information about which package requires the USE flag to be set for json-c
  19. I think your view of the portage tree is different from mine. The mentioned freecad is not in the official portage tree, which is probably the reason why it is not in funtoo. To my knowledge it was removed from the portage some time ago because of the problems associated with it. But it still exists in several overlays, provided by different users. Layman still exists and, as far as I know, still works. Haven't used it though. I prefer to put the ebuilds I need in my personal overlay and maintain them there. Others use git to pull the ebuilds/overlays they need into their system and use that. There are several ways to get all the packages you need into your system. You are free to choose. While I don't know how to remove games-kit with funtoo tools (ego, portage,...) and I don't know why you want to do that, you could probably use git to ignore that repository (as kits are just repositories). And adding new kits is the same as adding a local overlay. Have a look at the link I posted above. You can add as many repositories (kits) to your system as you like. The name my-overlay used on that page is just an example. You can call your overlays like you want: lefsha-kit, freecad-kit, lefsha-freecad,...
  20. If you are asking how to incorporate local overlays into funtoo you can find information at: https://www.funtoo.org/Creating_Your_Own_Overlay And you can also always submit pull request for ebuilds missing in funtoo via bugs.funtoo.org
  21. Like @cardinal said, the directory in which the ebuild lies needs to have the same name as the program, the ebuild is for, e.g.: - www-client/firefox-66.0.4.ebuild => directory www.client/firefox - x11-base/xorg-server-1.20.5.ebuild => directory x11-base/xorg-server or in your case net-fs/s3fs-1.83.ebuild => directory net-fs/s3fs
  22. I haven't seen any circular dependencies with mesa yet as you haven't shown the log with it. So it is hard to say where the problem is or if there is one. With a complex package like mesa there is always the chance of a bug. If you think you have found one feel free to open a bug at bugs.funtoo.org to get it looked at and fixed.
  23. Where in your overlay structure did you put the files?
  24. Hmm, which funtoo version are you talking about? 1.3 or 1.4? Which version of mesa? What is the exact error message? In funtoo 1.4 the mentioned include files are installed by media-libs/mesa-gl-headers and not by mesa. In funtoo 1.3 those files are installed without problems with mesa-18.2.8
  • Create New...