| View previous topic :: View next topic |
| Author |
Message |
sicr0
Apprentice
Joined: 23 Mar 2022
Posts: 180
|
 Posted: Tue Sep 06, 2022 2:21 pm Post subject: gnome-base/librsvg won't update |
 |
|
Hi, for some reason gnome-base/librsvg won't update.
The build log is a bit weird, not like the usual ones: https://gist.github.com/ignamartinoli/c4707c9d8385c31ed3fe67e443fb4896
It says that the package got installed, but when I do emerge -auD @world, I get prompted again, asking to update it.
Does anybody know why does this happens? Or what is making it fail? |
|
| Back to top |
|
 |
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 31085
Location: here
|
| Posted: Tue Sep 06, 2022 2:26 pm Post subject: |
|
|
Try to disable ccache.
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
logrusx
Veteran
Joined: 22 Feb 2018
Posts: 1889
|
| Posted: Tue Sep 06, 2022 2:34 pm Post subject: Re: gnome-base/librsvg won't update |
|
|
| fedeliallalinea wrote: | | Try to disable ccache. |
Since when does ccache support rust? And what does it have to do with portage asking to update again?
| sicr0 wrote: | Hi, for some reason gnome-base/librsvg won't update.
The build log is a bit weird, not like the usual ones: https://gist.github.com/ignamartinoli/c4707c9d8385c31ed3fe67e443fb4896
It says that the package got installed, but when I do emerge -auD @world, I get prompted again, asking to update it.
Does anybody know why does this happens? Or what is making it fail? |
please provide the output of emerge -pvuD @world |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22088
|
| Posted: Tue Sep 06, 2022 4:03 pm Post subject: |
|
|
| The build log says that cargo is trying to access the user's home directory. This is wrong, and it should not do that. My guess is that this is the same problem I tried to get sicr0 to deal with last time: environment variables in the root environment that point to the user's home directory. |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1786
|
| Posted: Tue Sep 06, 2022 4:39 pm Post subject: |
|
|
| Hu wrote: | | The build log says that cargo is trying to access the user's home directory. This is wrong, and it should not do that. My guess is that this is the same problem I tried to get sicr0 to deal with last time: environment variables in the root environment that point to the user's home directory. |
In short, running sudo emerge causes random issues like this.
Best to become root with either 'sudo -i' or 'su -' first to get a clean, root login shell. Then, issue emerge and other maintenance commands as needed |
|
| Back to top |
|
|
sicr0
Apprentice
Joined: 23 Mar 2022
Posts: 180
|
| Posted: Tue Sep 06, 2022 7:58 pm Post subject: |
|
|
I tried it with a root shell but it didn't work.
After removing this environment variables it worked
| Code: | export CARGO_HOME="$XDG_DATA_HOME/cargo"
export RUSTUP_HOME="$XDG_DATA_HOME/rustup"
|
Should I report this upstream? |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 1767
|
| Posted: Sat Oct 01, 2022 7:16 am Post subject: |
|
|
I've posted an update on the Rust issue after OP pointed me to this thread, see https://bugs.gentoo.org/873802#c6.
TL;DR: The reason the env unsetting stuff we have fails for librsvg is complicated but it should be sorted soon (in at least one of two ways). It'll be fixed when bug 753764 is closed. |
|
| Back to top |
|
|
tld
Veteran
Joined: 09 Dec 2003
Posts: 1829
|
| Posted: Sun Oct 02, 2022 3:58 pm Post subject: |
|
|
| grknight wrote: | In short, running sudo emerge causes random issues like this.
Best to become root with either 'sudo -i' or 'su -' first to get a clean, root login shell. |
I got burned by this many years ago. I was going nuts trying to figure out why the build of busybox was failing. The issue was that my non-root user had a variable $s set to a directory I currently reference, and I was becoming root using just "su" as apposed to "su -", and that variable was breaking something in a build script. To do most anything as root, it's always best to have the full root ENV for sure.
Tom |
|
| Back to top |
|
|
|
Portage & Programming
