Hi, I want to switch to the stable branch

[elover]

I've been using the ~amd64 branch since I started Gentoo many years ago, I didn't try the amd64 version until the beginning of the year. I was several months with stable branch and zero problems.

Now I want to move from ~amd64 to amd64, what do you recommend me to do, recompile GCC, Glibc, Ncurses and make emerge --ask --verbose --emptytree --with-bdeps=y @world

And another small question, I have in the make.conf set to protect configurations with CONFIG_PROTECT="/etc/conf.d/consolefont /etc/locale.gen /etc/conf.d/keymaps /etc/eixrc/00-eixrc" but it seems that it doesn't work, I don't know why

[xgivolari]

To absolutely make sure the toolchain works, I would start with this: linux-headers -> glibc -> binutils -> gcc -> libtool, and maybe even glibc -> binutils -> gcc -> libtool again. (note that different versions of binutils and gcc require you to manually select them using eselect, something I tend to forget ) Furthermore, a rebuild like this will probably trigger the ol' freetype-harfbuzz circular dependency again, so it might be prudent to temporarily disable USE="harfbuzz" on freetype.

[elover]

Hello, thanks for your reply
Glibc can't be downgraded, I'll use the one I have and then I'll tell you if I had any problem

[NeddySeagoon]

elover,

Change your ACCEPT_KEYWORDS and see what emerge wants to downgrade.
Look at the list carefully.
If glibc is there, mask it at the installed version. Downgrading glibc can break lots of things, so portage won't let you.

The usual advice is not to downgrade ... let stable catch you up.

[lekto]

I did it already three times (~amd64 => amd64) this way:
1. Make sure you have fully updated system, no packages that can't be updated because of conflicts etc.
2. Change your ACCEPT_KEYWORDS.
3. Try to update your system, but do not let it do it, instead put all currently installed packages (with currently installed version) that need to be downgraded into package.accept_keywords (on my last machine that was about 300 packages)
4. Now when you try to update system there should be nothing to update/downgrade.
5. Update your system as usual.
When you do it this way you will be emerging few packages at time, which is easier to debug than after rebuilding half of the system.

Now when updating system make sure it doesn't want downgrade anything important like glibc (broken system) or firefox (broken profile). If it wants just bump version in package.accept_keywords to the nearest version.
When I want to clean package.accept_keywords I run this command to show me what I can remove (change package.accept_keyword/amd64 to whatever you used):

Code: Select all

emerge -pO $(cat /etc/portage/package.accept_keywords/amd64) | grep -v "\[ebuild   R   \~\]"

It shows you what can be removed from the file.
Also there are packages that don't have stable versions so won't be updated this way (like openmw and its dependencies), instead run eclean-dist (from gentoolkit) to see what do you have installed that is not in tree any more.

There is one disadvantage: it take time to get rid off all ~amd64 packages, but system is working solid during this.

[forrestfunk81]

I would also update the system, freeze the currently installed versions in accept_keywords and then wait for stable to catch up.

Code: Select all

qlist -Iev | sed -e 's/^/=/' > /etc/portage/package.accept_keywords/freezed-versions-2022-08-05

This is not a fine elaborated command. It includes all installed packages and versions (not only arch).

[asturm]

I would also update the system, freeze the currently installed versions in accept_keywords and then wait for stable to catch up.

That is exactly the right thing to do.

[sabayonino]

Code: Select all

qlist -Iev | sed -e 's/^/=/' > /etc/portage/package.accept_keywords/freezed-versions-2022-08-05

Code: Select all

# emerge -p $(eix --installed-unstable --only-names)

It's better thing

"eix" must be installed

[forrestfunk81]

Code: Select all

qlist -Iev | sed -e 's/^/=/' > /etc/portage/package.accept_keywords/freezed-versions-2022-08-05

Code: Select all

# emerge -p $(eix --installed-unstable --only-names)

It's better thing

"eix" must be installed

Ok then:

Code: Select all

qlist -Iev $(eix --installed-unstable --only-names) | sed -e 's/^/=/' > /etc/portage/package.accept_keywords/unstable-packages

[sabayonino]

If you need to rebuild amd64 keywords packages (stable) , you don't need to set the package version.
Portage will downgrade to the latest stable version available in the tree

Code: Select all

eix --installed-unstable --only-names
app-backup/dar

[I] app-backup/dar
     Available versions:  2.7.5^t{tbz2} (~)2.7.6^t{tbz2} {argon2 curl dar32 dar64 doc gcrypt gpg lz4 lzo nls rsync threads xattr}
     Installed versions:  2.7.6^t{tbz2}(21:58:51 05/07/2022)(curl dar64 gcrypt lz4 lzo nls rsync threads xattr -argon2 -dar32 -doc -gpg)
     Homepage:            http://dar.linux.free.fr/
     Description:         A full featured backup tool, aimed for disks

DAR-2.7.5 is the latest stable version available

if you have set ACCEPT_KEYWORDS="amd64" , portage gonna be to downgrade from 2.7.6 (~amd64) to 2.7.5 (amd64)

Code: Select all

emerge app-backup/dar --ask

If you want to keep some ~amd64 packages , you can set _accept_keywords file per package

[Zucca]

I would also update the system, freeze the currently installed versions in accept_keywords and then wait for stable to catch up.

That is exactly the right thing to do.

This is exactly how I did it (some years ago) and it worked without any problems.

[Clad in Sky]

2 years forward I'm trying to do the same.
The list qlist -Iev $(eix --installed-unstable --only-names) outputs seems rather short, though. Am I missing something?

[Zucca]

2 years forward I'm trying to do the same.
The list qlist -Iev $(eix --installed-unstable --only-names) outputs seems rather short, though. Am I missing something?

The following mentioned earlier here should just work:

I would also update the system, freeze the currently installed versions in accept_keywords and then wait for stable to catch up.

Code: Select all

qlist -Iev | sed -e 's/^/=/' > /etc/portage/package.accept_keywords/freezed-versions-2022-08-05

This is not a fine elaborated command. It includes all installed packages and versions (not only arch).

I don't see any flaws in that at least.

[Clad in Sky]

2 years forward I'm trying to do the same.
The list qlist -Iev $(eix --installed-unstable --only-names) outputs seems rather short, though. Am I missing something?

The following mentioned earlier here should just work:

I would also update the system, freeze the currently installed versions in accept_keywords and then wait for stable to catch up.

Code: Select all

qlist -Iev | sed -e 's/^/=/' > /etc/portage/package.accept_keywords/freezed-versions-2022-08-05

This is not a fine elaborated command. It includes all installed packages and versions (not only arch).

I don't see any flaws in that at least.

Well, that command gave me a list that seems more complete.

[Zucca]

Well, that command gave me a list that seems more complete.

Its only flaw is that it also lists installed stable packages. However that should cause no harm.

[Clad in Sky]

Doing "eix-update" before might be a good idea. In my case, the last time I used eix was so long ago that the database was missing a lot of packages.

[Clad in Sky]

I found another issue.

I have musescore-4.4.2 in the unstable-packages list.
For some reason when I do an update now, portage wants to downgrade musescore to 3.6.2-r1 (latest stable).
Could this be because 4.4.2 isn't in the repository anymore (latest available version there is 4.4.3 at the moment)? How could I freeze musescore-4.4.2 then?

[Hu]

When told to update packages, Portage will always seek to install the best available version, even if this is a downgrade. Since 4.4.2 is gone, and 4.4.3 is not stable, and you are now only allowing stable packages, Portage cannot pick 4.4.3, and cannot stay on the removed 4.4.2, so it seeks to go down. You could mask versions lower than 4.4.2, but this may cause other errors. You could update to 4.4.3 and try to pin there. Perhaps 4.4.3 will go stable rather than being removed in preference to an even newer unstable version. You could avoid updating this package name until a 4.x version is marked as stable.

[Clad in Sky]

When told to update packages, Portage will always seek to install the best available version, even if this is a downgrade. Since 4.4.2 is gone, and 4.4.3 is not stable, and you are now only allowing stable packages, Portage cannot pick 4.4.3, and cannot stay on the removed 4.4.2, so it seeks to go down. You could mask versions lower than 4.4.2, but this may cause other errors. You could update to 4.4.3 and try to pin there. Perhaps 4.4.3 will go stable rather than being removed in preference to an even newer unstable version. You could avoid updating this package name until a 4.x version is marked as stable.

Thanks.