Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

drobbins

Funtoo Linux BDFL
  • Posts

    513
  • Joined

  • Last visited

  • Days Won

    282

Posts posted by drobbins

  1. If you want to install 1.3, use a more recent stage3 -- like 2018-12-12 for Haswell has been available since about 12-12 (look in "1.3-release-std"). If your stage3 has 32-bit libs, it is too old. You should have done a full-stop at that point and grabbed a newer one.

    Also follow instructions here: https://www.funtoo.org/Upgrade_Instructions/1.3-release

    Uh -- edit. If you are using a NEW 1.3 stage3 as I suggested, you shouldn't need any upgrade steps. Just follow our install docs! ?

  2. Show me the output of "epro show" -- do you have the gnome mix-in enabled? We masked newer versions of enchant because I believe they break some builds. But it may only be active when you have the gnome mix-in enabled which I am guessing you do not. Maybe we should expand the mask to be global for all users.

  3. Be sure to look at the 1.3 upgrade guide. We have some sed tweaks to do on the /var/db/pkg package database to get rid of abi_86_32/64 USE deps. Basically these USE deps can be removed as they are deprecated in Funtoo. Also you encountered an issue with xorg-proto. In the 1.3-upgrade docs, we tell you to manually unmerge xorg-server, which should resolve this ? So like I said, you sort of need to combine the 1.2 and 1.3 upgrade steps. ?

  4. One of the things I am pushing for is for Portage to grab any installed conflicting packages and add them to the package set automatically, before backtracking at all. This is likely going to resolve the majority of conflicts automatically. The upstream gentoo bug for this feature is https://bugs.gentoo.org/559354 <-- and I am thinking of something like an --expand option that will auto-add installed packages that conflict to the set of packages to be rebuilt, so users don't have to. If you think this would be a good idea, you may want to comment on the upstream bug and this may result in it being prioritized.

  5. Cool. This is the big reason we are working on having official upgrade docs. The upgrade process for Gentoo is left as "an exercise for the reader" and has gotten too complicated. As we have official versioned releases and attempt to write upgrade docs, we'll get better and better at it and gradually streamline the process. We've also started engaging with upstream Gentoo portage developers to look at ways that emerge can be improved to not throw so many conflicts.

  6. I recommend using the 1.3-upgrade docs but sort of combine them with the 1.2-upgrade docs for best results. When having conflicts, try --ignore-world to see if that resolves them. You can also add any "(installed)" packages in the conflict listing to the end of the emerge command-line which will force them to rebuild and often resolves the conflict.

  7. On 12/6/2018 at 3:43 PM, mauricev said:

    First, I can't report anything on bugs.funtoo.org because the login is rejecting me. 

    If login is rejecting you, you will need to use authy to upgrade your account -- go to https://auth.funtoo.org/login and go through that. It should prompt you to upgrade your account. If you are not willing or able to use SMS to validate your account, you can find us on IRC and get us to manually validate your account. Oleg (angry_vincent), biberao and me will be able to help you there (other guys will have the ability to do this tomorrow)...

  8. Hi All,

    Within 12 hours, I plan to move 1.3-release to BETA status.

    Along with this comes the very important change on 64-bit platforms -- I am removing multilib and making "pure64" compatibility the default. This means that 1.3-release builds with the x86-64bit arch will be 64-bit only.

    This is done for a variety of reasons, most important of which is that the world has had a 64-bit PC instruction set for approximately 15 years. It is time to drop 32-bit support. For those who still need 32-bit support, it will be available via a Funtoo 32-bit chroot setup.

    The story behind multilib is rather complex and interesting, and might be the focus of a future blog post, but for now, you will just have to trust me -- multilib support in Gentoo is a pain in the butt. It takes a lot of effort to work with and slows us down. Our efforts are best spent in other places, and chroot should work for the vast majority of users who truly are running a critical 32-bit application (other options are 32-bit containers, etc.)

    EDIT: Upgrade Instructions Here: https://www.funtoo.org/Upgrade_Instructions/1.3-release

    Best,

    Daniel

×
×
  • Create New...