Jump to content
funtoo forums

palica

Funtoo Linux Developer
  • Content Count

    291
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by palica

  1. most of the stuff gets announced https://forums.funtoo.org/forum/5-news-and-announcements/ available are always only the branches that are part of the release. 1.3-release is now release as beta quality. so test it out and report any bugs that you encounter. some of the branches get named after the release some are named after the version of the software they are incorporating like kde-5.12 gnome-3.26 perl-5.26 python-3.7 ... and others just have many different software and are simply named 1.3-release. there is no other description visible using currently available funtoo tools. stability can be found here: https://github.com/funtoo/kit-fixups/blob/master/modules/fixups/foundations.py#L5-L12 class KitStabilityRating(Enum): PRIME = 0 # Kit is enterprise-quality NEAR_PRIME = 1 # Kit is approaching enterprise-quality BETA = 2 # Kit is in beta ALPHA = 3 # Kit is in alpha DEV = 4 # Kit is newly created and in active development CURRENT = 10 # Kit follows Gentoo currrent DEPRECATED = 11 # Kit is deprecated/retired switching to kde-kit from 1.3-release while still on 1.2-release will fail when doing ego sync, but can be done manually (although not recommended and definitely not supported). You could manually switch to kde-kit from 1.3-release by checking out the appropriate sha hash of the commit as listed here: https://github.com/funtoo/meta-repo/blob/1.3-release/metadata/kit-sha1.json but this has to be done after every ego sync.
  2. thank you for your positive and friendly answers. I explained to you that 1.3-release branches will show up once you switch to 1.3-release, 5.12-prime is there from 1.2-release and master branch is a remnant of 1.0-release (at that time called 1.0-prime) here are the definitions that are used for kit generation, maybe that will answer your question https://github.com/funtoo/kit-fixups/blob/master/modules/fixups/foundations.py there is not a simple way of switching to a different branch of a kit (1.3-release for kde-kit) without actually switching the whole release = all kits to the 1.3-release. from the user perspective you should edit /etc/ego.conf and add in [global] section release = 1.2 (1.3) and perform ego sync ego will then switch the kit branches for you. There is a reason you cannot see all branches of a kit on a single release as these are untested and will probably not work. if there are multiple branches supported they are listed in ego kit list output and they can be switched using /etc/ego.conf with a value for example xorg-kit=1.20-release inside [kits] section. if you want to go your own way (switching a single kit to a different branch that is not supported for a given release) - you will probably not receive any official help from funtoo. (and definitely not from me 🙂 )
  3. so you looked at github and explored git locally - no sign of ego kit list here. You wonder if there is a way to do it with ego or any funtoo specific command -> ego kit list 1.3-release will show once you switch to 1.3-release in ego.conf [global] release = 1.3 the stability tag: current - tracking gentoo prime - somehow seen as good for production anything else - alpha, beta, dev => not good for production if you are not a developer
  4. ~ ❯❯❯ ego kit list kit is active? branch stability core-kit active 1.2-prime prime core-hw-kit active master current security-kit active 1.2-prime prime xorg-kit 1.17-prime prime active 1.19-prime prime 1.20-release dev gnome-kit active 3.20-prime prime 3.26-prime prime kde-kit active 5.12-prime prime media-kit active 1.2-prime prime perl-kit active 5.24-prime prime python-modules-kit active master current python-kit active 3.6-prime prime php-kit active master current java-kit active 1.2-prime prime ruby-kit active 1.2-prime prime haskell-kit active 1.2-prime prime ml-lang-kit active 1.2-prime prime lisp-scheme-kit active 1.2-prime prime lang-kit active 1.2-prime prime llvm-kit active 1.2-prime prime master dev dev-kit active 1.2-prime prime xfce-kit active 4.12-prime prime desktop-kit active 1.2-prime prime editors-kit active master current net-kit active master current text-kit active master current science-kit active master current games-kit active master current nokit active master current NOTE: This information comes from /etc/ego.conf and meta-repo metadata. After making changes to ego.conf, be sure to run ego sync in so that the individual kit repositories on disk are synchronized with the kit branches shown above.
  5. palica

    Build livecd

    https://github.com/matijaskala/metro-1 https://slontoo.sourceforge.io/
  6. palica

    cannot build openssl--1.1.0h on arm64

    open a bug report on bugs.funtoo.org
  7. palica

    cannot set profile

    no problem, glad we sorted it out.
  8. palica

    Trying to upgrade from funtoo 1.0

    there is no stable anymore try ./ego profile build current and try to resume from there
  9. palica

    Trying to upgrade from funtoo 1.0

    well actually he is using live master of ego can you from cloned ego folder do "ego profile "
  10. palica

    email notifications

    https://forums.funtoo.org/notifications/options/
  11. palica

    Virtualbox issues fresh Funtoo install

    try to find a log file inside VM dir somewhere, without it it is reading from a crystal ball.
  12. good plan. let us know what you find out.
  13. palica

    Virtualbox issues fresh Funtoo install

    running as what user? are you in the "virtualbox" group if not root?
  14. palica

    Virtualbox issues fresh Funtoo install

    lsmod | grep vbox
  15. it is not that much about software becoming incompatible with older release, it is more of any patches and fixes that didn't make it into 4.9-lts branch that you probably used, at the time of creation of the system, some BTRFS features that were in 4.14 branch and are not in 4.9. so creating a loop device btrfs system with 4 disks and creating a raid10 with 4.14 and then turning on all the flags like compress and such on the fs and putting some dummy data on there, and afterwards downgrading the kernel and mounting the filesystem and comparing for example the checksums of the dummy data or performing a scrub could give you information about if this downgrade is safe for your server, but also don't take this for granted and have backups!!! couple of ideas how to test without 4 harddrives can be found here: https://www.funtoo.org/BTRFS_Fun
  16. palica

    cannot set profile

    all the setup commands are run as root. there is no "own profile" there is only "system profile". changing profile requires being root or using sudo.
  17. https://btrfs.wiki.kernel.org/index.php/Changelog#By_feature don't know how much debian backports btrfs fixes (or new features) changelog here: https://salsa.debian.org/kernel-team/linux/blob/046a5da6eb748c59f7402d5aae84ab7543dbb396/debian/changelog?expanded=true&viewer=simple downgrade could be problematic if you use ZSTD as your compression for example, but not limited to this probably. IMHO - test the downgrade on a separate pc or disk. (and never touch a running system) at least for those running btrfs this kernel switch should be done with extreme caution.
  18. palica

    cannot set profile

    so I don't know why you can update on one as normal user - but that should not be the normal behaviour. I think that setting profile is a admin's (root) job and should be limited to root or sudoers. there has to be a difference other then one being mac and the other amd, what stage did you use for both of them, how did you extract them. I am just guessing here as I don't know what could cause this behaviour, but what I am trying to say, try to go back in your setup procedure and give any differences between the two machines. Also I don't think that you should be allowed to change system's profile as a normal user. So actually I find the mac performance strange. I have never encountered this as I always setup the core OS as root. How did you emerge packages, also as denis user?
  19. palica

    cannot set profile

    paste /etc/sudoers from both
  20. palica

    cannot set profile

    paste "groups denis" from both pc
  21. palica

    the second login need password

    paste your .ssh/config and please read
  22. palica

    cannot set profile

    then you have to adjust permissions on /etc/portage/make.profile/parent
  23. lxd import Description: Import existing containers This command is mostly used for disaster recovery. It lets you attempt to recreate all database entries for containers that LXD no longer knows about. To do so, you must first mount your container storage at the expected path inside the storage-pools directory. Once that's in place, `lxd import` can be called for each individual container. Usage: lxd import <container name> [flags] Flags: -f, --force Force the import (override existing data or partial restore) Global Flags: -d, --debug Show all debug messages -h, --help Print help --logfile Path to the log file --trace Log tracing targets -v, --verbose Show all information messages --version Print version number
  24. We’d love to help you. To improve your chances of getting an answer, here are some tips: Search, and research ...and keep track of what you find. Even if you don't find a useful answer elsewhere on the site, including links to related questions that haven't helped can help others in understanding how your question is different from the rest. Write a title that summarizes the specific problem The title is the first thing potential answerers will see, and if your title isn't interesting, they won't read the rest. So make it count: Pretend you're talking to a busy colleague and have to sum up your entire question in one sentence: what details can you include that will help someone identify and solve your problem? Include any error messages, key APIs, or unusual circumstances that make your question different from similar questions already on the site. Spelling, grammar and punctuation are important! Remember, this is the first part of your question others will see - you want to make a good impression. If you're not comfortable writing in English, ask a friend to proof-read it for you. If you're having trouble summarizing the problem, write the title last - sometimes writing the rest of the question first can make it easier to describe the problem. Examples: Bad: Is there command to do what it needs? Good: How can I apply changes proposed by emerge? Bad: Problem update system Good: Why does the compile of dev-libs/boost-1.63.0 fail with x86_64-pc-linux-gnu-g++: internal compiler error: Killed (program cc1plus)? Introduce the problem before you post any code In the body of your question, start by expanding on the summary you put in the title. Explain how you encountered the problem you're trying to solve, and any difficulties that have prevented you from solving it yourself. The first paragraph in your question is the second thing most readers will see, so make it as engaging and informative as possible. Help others reproduce the problem Not all questions benefit from including code. Here are some guidelines: Include just enough code to allow others to reproduce the problem. For portage errors include all the relevant info and output. Include all relevant tags Try to include a tag for the language, library, and specific API your question relates to. If you start typing in the tags field, the system will suggest tags that match what you've typed - be sure and read the descriptions given for them to make sure they're relevant to the question you're asking! See also: What are tags, and how should I use them? Proof-read before posting! Now that you're ready to ask your question, take a deep breath and read through it from start to finish. Pretend you're seeing it for the first time: does it make sense? Try reproducing the problem yourself, in a fresh environment and make sure you can do so using only the information included in your question. Add any details you missed and read through it again. Now is a good time to make sure that your title still describes the problem! Post the question and respond to feedback After you post, leave the question open in your browser for a bit, and see if anyone comments. If you missed an obvious piece of information, be ready to respond by editing your question to include it. If someone posts an answer, be ready to try it out and provide feedback! Look for help asking for help In spite of all your efforts, you may find your questions poorly-received. Don't despair! Learning to ask a good question is a worthy pursuit, and not one you'll master overnight. Here are some additional resources that you may find useful: Writing the perfect question How do I ask and answer homework questions? How to debug small programs Meta discussions on asking questions How to ask questions the smart way — long but good advice.
  25. palica

    'x11-base/xcb-proto-1.13'

    just for reference: https://bugs.funtoo.org/browse/FL-5623
×