Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by dkg

  1. FYI, the Funtoo Container FAQ still states that meta-repo is shared.
  2. I can't figure out why I don't get emails from Jira when someone updates a ticket that I've created or watched. Poked all around the Jira settings and account. Is it just me?
  3. First, if you haven't, I suggest reading up a little on passive vs. active PFC, waveform, etc. Second, my (older) CyberPower CP1500PFCLCD works a treat with apcupsd. From what I've seen, at least some newer CyberPower models work, as well, though I don't think there is an exhaustive list anywhere. It looks as though the LE850G uses USB for communication, so I think chances are good it will work.
  4. I've been having a problem lately where Dropbox has been repeatedly creating filling up ~/Dropbox/.dropbox.cache/tmp_dirs with what looks like identical folders until the disk is (near) full. I've since revoked all user permissions to that folder do prevent this behavior. Is anyone else experiencing this?
  5. Umm. Okay. I suppose this all makes sense to people with deep insight into Funtoo, but it's awful confusing to this user. Python 3.6 is in the tree, but it's not part of Funtoo 1.4. Software which I find critical is in the tree, but does not have a Python 3.7 target (only 3.5 and 3.6). So I keep Python 3.6 and therefore I'm deviating from Funtoo 1.4, I guess. I did not know that what I did was not supported. Seems the correct thing to do was to remove 3.6, and break that critical software. It needed to be fixed for 3.7, but I had no idea about this when I started the upgrade. I'm not
  6. And there you have it. 🙂 https://bugs.funtoo.org/browse/FL-6963 Honestly, I feel this discussion has gotten a little off track, though. It was supposed to be about my concern with the upgrade instructions. I guess the answer is, "Don't blindly follow the steps." Good advice, that. I only pointed out the s3ql problem because pycrypto vs. pycryptodome came up. A workaround is there if anybody needs it.
  7. Sure, it makes sense, but it is a problem that I am experiencing in both. I am happy to open a Funtoo bug, too, if that is the proper etiquette in my situation.
  8. I am both a Gentoo user and a Funtoo user. Would you like me to open a bug on both trackers?
  9. See the bug I filed at gentoo yesterday 🙂 https://bugs.gentoo.org/707878
  10. True. But until that work is done, advising people to execute 'emerge -C =dev-lang/python-3.6*' without checking if they are using it seems silly.
  11. Did you get s3ql v3.3 working? Could you share your ebuild?
  12. I'm confused by the way that the 1.4 upgrade instructions state, unconditionally, "Remove python-3.6 as it will no longer be used." There are at least a couple of ebuilds in the tree that do not have a Python 3.7 target, e.g., net-fs/s3ql and dev-python/pycrypto. What am I missing?
  13. I appreciate the post, but I'd like to ask a question. It seems to me that with the chroot method, there is going to be no integration or interaction between the "host" and the chroot "guest". That is, I can't start an application in the chroot by clicking on a Plasma icon, or using 'Open With' in Dolphin. Or the other direction, having a command in a Windows app open a folder in Dolphin or Konsole, or a URL in Firefox. Have you found ways to make things like this work with your method? Thanks.
  14. dkg

    agetty log spam

    Perfect, thank you.
  15. I'm getting spam in my logs in my container from agetty like this: Jul 21 00:19:58 dkg agetty[5782]: /dev/tty1: cannot open as standard input: No such file or directory Jul 21 00:19:58 dkg agetty[5784]: /dev/tty3: cannot open as standard input: No such file or directory Jul 21 00:19:58 dkg agetty[5786]: /dev/tty5: cannot open as standard input: No such file or directory
  16. Believe me, I appreciate that multilib is a hack, and I've had plenty of issues with it over the years. And I can accept that my use case is uncommon. It's also a use case that is not addressed well by chroot or containers, unfortunately. Hope my feedback was useful, anyway. By the way, I cannot figure out why the forums do not send me an email when someone replies to a post or thread I'm following. Don't know if it's just me or what.
  17. I'm aware that and X server is going to magically appear in the chroot, but I was hoping xhost would make it unnecessary, though I was pretty sure going in that it would not. No, I did not, as I had no need to run 64-bit Windows apps. The point is, I could not copy the wine *prefixes* over. This, I did not anticipate. Not disaster, but definitely a pain. Gentoo still uses openrc by default. Meanwhile, I'm still limping along with Funtoo 1.2 on that system.
  18. Well, since a few weeks have passed with no suggestions for my difficulties, nor news of a solution in the near term, I guess I'm faced with "downgrading" this system to Gentoo. As much as I love Funtoo's extra features (enough that I've been a financial supporter of Funtoo for years), it just isn't providing the things I need for this system. Hope to bring it back to Funtoo one day.
  19. Since adding the 'X' use flag to wine-vanilla/wine-staging (not currently mentioned in guide), I can actually launch a program now. However, I could not use a copy of the existing wine prefix, as it complained that it "is not a 64-bit installation, it cannot be used with a 32-bit wineserver." I'd have to rebuild the prefix from scratch, not knowing all the tweaks I made to get it where it is. With work, I could probably copy the things needed to bring it into shape. But, it doesn't have access to any of the files from either my home folder nor NFS mounts. I'd have to bind remount a number
  20. No success so far. Following the wiki instructions, when I run winecfg at the end, I get the following. I did run the 'xhost' command. 0009:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0009:err:winediag:nodrv_CreateWindow The graphics driver is missing. Check your build!
  21. In the meantime, can anybody share experience with running apps, particularly apps in wine, using a chroot as described in the wiki? It's not clear to me how to transparently launch applications in the chroot from a desktop (Plasma launcher/widgets). Or whether file type associations can work.
  22. Yes, I don't know why I left "stage3" out of the post. I was not aware that they could run different versions of funtoo. If I find time, I will give it a try this weekend. Thanks.
  23. I have a few important apps that I run in wine (not Steam or games). Before I go all in with the 1.3 upgrade, I wanted to try creating a 32-bit chroot in 1.2 to make sure I could get wine and apps working. The problem is, I don't see any 32-bit tarballs available for 1.2 - only 64-bit. How else might one go about this?
  24. The system upgrade is now complete. Thanks for the help, @palica.
  25. I think the Upgrade Instructions may be missing steps regarding the python upgrade. It says to run these commands: # emerge -u1 =dev-lang/python-3.6* # emerge -C =dev-lang/python-3.4* Both systems that I've upgraded to 1.2, I got this message when trying to remove python-3.4: [root@wolfie 73% etc]# emerge -C =dev-lang/python-3.4* * This action can remove important packages! In order to be safer, use * `emerge -pv --depclean <atom>` to check for reverse dependencies before * removing packages. >>> These are the packages that would be unmerged: * Not unmerging pac
  • Create New...