[gentoo-user] config file '/etc/mtab' needs updating
After update I get: * IMPORTANT: config file '/etc/mtab' needs updating. What is this, don't remember seeing it before. cfg-update -u doesn't give me an option to view it.
Re: [gentoo-user] X not starting after kernel upgrade
On Mon, 2023-04-10 at 15:53 -0600, the...@sys-concept.com wrote: > Is: make oldconfig same as: make olddefconfig ? No. olddefconfig accepts the default answer for each new configuration item, non-interactively. oldconfig is interactive. I can't really give you guidance with your original problem though.
Re: [gentoo-user] emerge -U or emerge -N
On Mon, 2023-04-10 at 22:10 -0600, the...@sys-concept.com wrote: > On 4/10/23 18:53, Dale wrote: > > > I've asked ChatGPT for explanation and here is what I got: > > Here are the differences between emerge -U and emerge -N: > > emerge -U: This option upgrades the specified package(s) to the > latest available version. It will first download the new version, > then build and install it. If a dependency of the package being > upgraded also needs to be upgraded, it will also be upgraded. > > emerge -N: This option installs the specified package(s) without > upgrading any dependencies. It will only download and install the > package(s) if they are not already installed. If any dependencies of > the package(s) are not already installed, the command will fail. > > In other words, emerge -U upgrades packages and their dependencies, > while emerge -N only installs packages without upgrading any > dependencies. > This is a good example of why ChatGPT cannot be trusted. When ChatGPT doesn't know the answer to something, rather than saying it doesn't know the answer, it just makes it up. The difference between -U and -N as explained by ChatGPT is wrong; in fact, it has nothing to do with dependencies. To have a truthful answer, let's not ask ChatGPT and instead look at `man 5 emerge`: --newuse, -N Tells emerge to include installed packages where USE flags have changed since compilation. This option also implies the --selective option. USE flag changes include: A USE flag was added to a package. A USE flag was removed from a package. A USE flag was turned on for a package. A USE flag was turned off for a package. --changed-use, -U Tells emerge to include installed packages where USE flags have changed since installation. This option also implies the --selective option. Unlike --newuse, the --changed-use option does not trigger reinstallation when flags that the user has not enabled are added orremoved. In a nutshell, `--newuse` or `-N` rebuilds packages when USE flags have changed, regardless of whether the changed USE flags affect the outcome Where as `--changed-use` or `-U` rebuilds packages when the USE flags have changed, AND the changed USE flags affect the outcome. For example, suppose you are on an openRC system, and a package introduces a new `systemd` USE flag; With `-N`: this package will be rebuilt with `-systemd` With `-U`: this package will not be rebuilt -- Julien signature.asc Description: This is a digitally signed message part
Re: [gentoo-user] emerge -U or emerge -N
On 4/10/23 18:53, Dale wrote: the...@sys-concept.com wrote: Is it better to us emerge -U or emerge -N I've always done -N but it didn't go very smoothly it seems to me -U might be better option but it takes longer. Right now I'm doing -U and it is compiling 549-packages. . I always do both except I use the lower case 'u'. I started using Gentoo back in 2003. Over the years, I added/changed options to emerge until I got a good sane system that works as expected and is stable. My command is emerge -auDN world and it has worked for years. One difference, I update once a week and on occasion two weeks if I have something going on and need to wait. I'd think tho, if one goes a long time between updates, my way would result in a longer compile time but also a system that is more stable or clean. Everyone has their own way. If what a person does is working, by all means do it that way. I picked my way because of problems I ran into. The solutions to those problems resulted in the command I use. If one waits a long time between updates, more packages will have updated and result in more updates regardless of the options. In that case, any USE changes would apply to those packages anyway. If one updates often, as I do, then the way I do it may have benefits and result in a more stable system, even tho it requires more packages to compile. Hope that helps. Dale :-) :-) I've asked ChatGPT for explanation and here is what I got: Here are the differences between emerge -U and emerge -N: emerge -U: This option upgrades the specified package(s) to the latest available version. It will first download the new version, then build and install it. If a dependency of the package being upgraded also needs to be upgraded, it will also be upgraded. emerge -N: This option installs the specified package(s) without upgrading any dependencies. It will only download and install the package(s) if they are not already installed. If any dependencies of the package(s) are not already installed, the command will fail. In other words, emerge -U upgrades packages and their dependencies, while emerge -N only installs packages without upgrading any dependencies.
Re: [gentoo-user] Re: emerge -U or emerge -N
Grant Edwards wrote: > On 2023-04-11, Dale wrote: >> the...@sys-concept.com wrote: >>> Is it better to us emerge -U or emerge -N >> I always do both except I use the lower case 'u'. I started using >> Gentoo back in 2003. Over the years, I added/changed options to emerge >> until I got a good sane system that works as expected and is stable. My >> command is emerge -auDN world and it has worked for years. > Once upon a time, a little over 20 years ago, I did some studying, and > I searched mailing lists postings for recommendations, and I settled > on > > emerge -auvND > > I've been using that ever since on a handful of machines. I'd have to > spend a few minutes reading the man page to remember the significance > of a couple of the flags, but I note that differs only in verbosity > from Dale's usage. > > -- > Grant I need to add something. I always forget the default options I have in make.conf. This is the options I put in there. EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=500 --keep-going -v --quiet-build=y -1 --unordered-display --jobs=6 --load-average 8" I added with-bdeps ages ago to correct some issues. After I had to use it a few times to fix issues, I added it to the default. I used to have backtrack set to 100. After a while 100 just didn't allow it to go deep enough. I tried higher settings until I reached 500. I don't recall ever having to increase it manually since. The -1 keeps my world file clean. If I want to add something to the world file, I use the --select y option to bypass it. The others are pretty obvious and are more of a personal preference or based on my CPU etc. I might add, it is rare that emerge can't find a path to do updates. Other than known bugs, it's also rare that I have problems with things not working with software, unless it is me doing something wrong of course. :/ Hope this helps, someone at least. Dale :-) :-)
[gentoo-user] Re: emerge -U or emerge -N
On 2023-04-11, Dale wrote: > the...@sys-concept.com wrote: >> Is it better to us emerge -U or emerge -N > > I always do both except I use the lower case 'u'. I started using > Gentoo back in 2003. Over the years, I added/changed options to emerge > until I got a good sane system that works as expected and is stable. My > command is emerge -auDN world and it has worked for years. Once upon a time, a little over 20 years ago, I did some studying, and I searched mailing lists postings for recommendations, and I settled on emerge -auvND I've been using that ever since on a handful of machines. I'd have to spend a few minutes reading the man page to remember the significance of a couple of the flags, but I note that differs only in verbosity from Dale's usage. -- Grant
Re: [gentoo-user] emerge -U or emerge -N
the...@sys-concept.com wrote: > Is it better to us emerge -U or emerge -N > > I've always done -N but it didn't go very smoothly it seems to me -U > might be better option but it takes longer. > Right now I'm doing -U and it is compiling 549-packages. > > . > I always do both except I use the lower case 'u'. I started using Gentoo back in 2003. Over the years, I added/changed options to emerge until I got a good sane system that works as expected and is stable. My command is emerge -auDN world and it has worked for years. One difference, I update once a week and on occasion two weeks if I have something going on and need to wait. I'd think tho, if one goes a long time between updates, my way would result in a longer compile time but also a system that is more stable or clean. Everyone has their own way. If what a person does is working, by all means do it that way. I picked my way because of problems I ran into. The solutions to those problems resulted in the command I use. If one waits a long time between updates, more packages will have updated and result in more updates regardless of the options. In that case, any USE changes would apply to those packages anyway. If one updates often, as I do, then the way I do it may have benefits and result in a more stable system, even tho it requires more packages to compile. Hope that helps. Dale :-) :-)
Re: [gentoo-user] X not starting after kernel upgrade
On 4/10/23 17:29, Jack wrote: On 2023.04.10 18:22, the...@sys-concept.com wrote: On 4/10/23 15:53, the...@sys-concept.com wrote: After upgrading to newest kernel the X will not start. Is: make oldconfig same as: make olddefconfig ? Xorg.0.log showing; [ 673.829] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so [ 673.829] (II) Module nouveau: vendor="X.Org Foundation" [ 673.829] compiled for 1.21.1.8, module version = 1.0.17 [ 673.829] Module class: X.Org Video Driver [ 673.829] ABI class: X.Org Video Driver, version 25.2 [ 673.829] (II) LoadModule: "nv" [ 673.829] (WW) Warning, couldn't open module nv [ 673.829] (EE) Failed to load module "nv" (module does not exist, 0) [ 673.829] (II) LoadModule: "modesetting" [ 673.829] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 673.830] (II) Module modesetting: vendor="X.Org Foundation" [ 673.830] compiled for 1.21.1.8, module version = 1.21.1 [ 673.830] Module class: X.Org Video Driver [ 673.830] ABI class: X.Org Video Driver, version 25.2 [ 673.830] (II) LoadModule: "fbdev" [ 673.830] (WW) Warning, couldn't open module fbdev [ 673.830] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 673.830] (II) LoadModule: "vesa" [ 673.830] (WW) Warning, couldn't open module vesa [ 673.830] (EE) Failed to load module "vesa" (module does not exist, 0) [ 673.830] (II) NOUVEAU driver [ 673.830] (II) NOUVEAU driver for NVIDIA chipset families : [ 673.830] RIVA TNT (NV04) [ 673.830] RIVA TNT2 (NV05) [ 673.830] GeForce 256 (NV10) [ 673.830] GeForce 2 (NV11, NV15) [ 673.830] GeForce 4MX (NV17, NV18) [ 673.830] GeForce 3 (NV20) [ 673.830] GeForce 4Ti (NV25, NV28) [ 673.830] GeForce FX (NV3x) [ 673.830] GeForce 6 (NV4x) [ 673.830] GeForce 7 (G7x) [ 673.830] GeForce 8 (G8x) [ 673.830] GeForce 9 (G9x) [ 673.830] GeForce GTX 2xx/3xx (GT2xx) [ 673.830] GeForce GTX 4xx/5xx (GFxxx) [ 673.830] GeForce GTX 6xx/7xx (GKxxx) [ 673.830] GeForce GTX 9xx (GMxxx) [ 673.830] GeForce GTX 10xx (GPxxx) [ 673.830] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 673.831] (EE) [drm] Failed to open DRM device for pci::01:00.0: -19 [ 673.831] (EE) open /dev/dri/card0: No such file or directory [ 673.831] (WW) Falling back to old probe method for modesetting [ 673.831] (EE) open /dev/dri/card0: No such file or directory [ 673.831] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 673.831] (EE) Screen 0 deleted because of no matching config section. [ 673.831] (II) UnloadModule: "modesetting" [ 673.831] (EE) Device(s) detected, but none match those in the config file. [ 673.831] (EE) Fatal server error: [ 673.831] (EE) no screens found(EE) This is an old system and is using: GeForce GTS 450 Does the newest kernel: linux-6.1.19-gentoo supports my old GeForce GTS 450 card? grep KMS .config CONFIG_DRM_KMS_HELPER=y CONFIG_DRM=y I don't recall anything about the kernel that has to match the video card - it's the video driver for X, but if you're using Nouveau, I wouldn't expect a problem. I know the current nVidia driver is often not ready for the latest kernel, but I don't think that's your problem. Have you recompiled xv86-video-nouveau after installing the new kernel? Are there any relevant errors in dmesg? I think the problem is with latest kernel linux-6.1.19-gentoo I'm using Nvidia dirver; x11-drivers/nvidia-drivers-390.157 and after compiling the driver on this kernel I was getting a message notice: WARN: setup Detected potential configuration issues with used kernel: CONFIG_FB_SIMPLE: is set, recommended to disable and switch to FB_EFI or FB_VESA as it currently may be broken with >=kernel-5.18.13 + NVIDIA: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341 (feel free to ignore this if it works for you) I downgraded the kerenl to: linux-5.15.102-gentoo and X is booting OK. message after recompiling Nvida driver: WARN: postinst Be warned/reminded that the 390.xx branch reached end-of-life and NVIDIA is no longer fixing issues (including security). Free to keep using (for now) but it is recommended to either switch to nouveau or replace hardware. Will be kept in-tree while possible, but expect it to be removed likely in early 2027 or earlier if major issues arise.
Re: [gentoo-user] X not starting after kernel upgrade
On 2023.04.10 18:22, the...@sys-concept.com wrote: On 4/10/23 15:53, the...@sys-concept.com wrote: After upgrading to newest kernel the X will not start. Is: make oldconfig same as: make olddefconfig ? Xorg.0.log showing; [ 673.829] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so [ 673.829] (II) Module nouveau: vendor="X.Org Foundation" [ 673.829] compiled for 1.21.1.8, module version = 1.0.17 [ 673.829] Module class: X.Org Video Driver [ 673.829] ABI class: X.Org Video Driver, version 25.2 [ 673.829] (II) LoadModule: "nv" [ 673.829] (WW) Warning, couldn't open module nv [ 673.829] (EE) Failed to load module "nv" (module does not exist, 0) [ 673.829] (II) LoadModule: "modesetting" [ 673.829] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 673.830] (II) Module modesetting: vendor="X.Org Foundation" [ 673.830] compiled for 1.21.1.8, module version = 1.21.1 [ 673.830] Module class: X.Org Video Driver [ 673.830] ABI class: X.Org Video Driver, version 25.2 [ 673.830] (II) LoadModule: "fbdev" [ 673.830] (WW) Warning, couldn't open module fbdev [ 673.830] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 673.830] (II) LoadModule: "vesa" [ 673.830] (WW) Warning, couldn't open module vesa [ 673.830] (EE) Failed to load module "vesa" (module does not exist, 0) [ 673.830] (II) NOUVEAU driver [ 673.830] (II) NOUVEAU driver for NVIDIA chipset families : [ 673.830] RIVA TNT (NV04) [ 673.830] RIVA TNT2 (NV05) [ 673.830] GeForce 256 (NV10) [ 673.830] GeForce 2 (NV11, NV15) [ 673.830] GeForce 4MX (NV17, NV18) [ 673.830] GeForce 3 (NV20) [ 673.830] GeForce 4Ti (NV25, NV28) [ 673.830] GeForce FX (NV3x) [ 673.830] GeForce 6 (NV4x) [ 673.830] GeForce 7 (G7x) [ 673.830] GeForce 8 (G8x) [ 673.830] GeForce 9 (G9x) [ 673.830] GeForce GTX 2xx/3xx (GT2xx) [ 673.830] GeForce GTX 4xx/5xx (GFxxx) [ 673.830] GeForce GTX 6xx/7xx (GKxxx) [ 673.830] GeForce GTX 9xx (GMxxx) [ 673.830] GeForce GTX 10xx (GPxxx) [ 673.830] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 673.831] (EE) [drm] Failed to open DRM device for pci::01:00.0: -19 [ 673.831] (EE) open /dev/dri/card0: No such file or directory [ 673.831] (WW) Falling back to old probe method for modesetting [ 673.831] (EE) open /dev/dri/card0: No such file or directory [ 673.831] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 673.831] (EE) Screen 0 deleted because of no matching config section. [ 673.831] (II) UnloadModule: "modesetting" [ 673.831] (EE) Device(s) detected, but none match those in the config file. [ 673.831] (EE) Fatal server error: [ 673.831] (EE) no screens found(EE) This is an old system and is using: GeForce GTS 450 Does the newest kernel: linux-6.1.19-gentoo supports my old GeForce GTS 450 card? grep KMS .config CONFIG_DRM_KMS_HELPER=y CONFIG_DRM=y I don't recall anything about the kernel that has to match the video card - it's the video driver for X, but if you're using Nouveau, I wouldn't expect a problem. I know the current nVidia driver is often not ready for the latest kernel, but I don't think that's your problem. Have you recompiled xv86-video-nouveau after installing the new kernel? Are there any relevant errors in dmesg?
Re: [gentoo-user] X not starting after kernel upgrade
On 4/10/23 15:53, the...@sys-concept.com wrote: After upgrading to newest kernel the X will not start. Is: make oldconfig same as: make olddefconfig ? Xorg.0.log showing; [ 673.829] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so [ 673.829] (II) Module nouveau: vendor="X.Org Foundation" [ 673.829] compiled for 1.21.1.8, module version = 1.0.17 [ 673.829] Module class: X.Org Video Driver [ 673.829] ABI class: X.Org Video Driver, version 25.2 [ 673.829] (II) LoadModule: "nv" [ 673.829] (WW) Warning, couldn't open module nv [ 673.829] (EE) Failed to load module "nv" (module does not exist, 0) [ 673.829] (II) LoadModule: "modesetting" [ 673.829] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 673.830] (II) Module modesetting: vendor="X.Org Foundation" [ 673.830] compiled for 1.21.1.8, module version = 1.21.1 [ 673.830] Module class: X.Org Video Driver [ 673.830] ABI class: X.Org Video Driver, version 25.2 [ 673.830] (II) LoadModule: "fbdev" [ 673.830] (WW) Warning, couldn't open module fbdev [ 673.830] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 673.830] (II) LoadModule: "vesa" [ 673.830] (WW) Warning, couldn't open module vesa [ 673.830] (EE) Failed to load module "vesa" (module does not exist, 0) [ 673.830] (II) NOUVEAU driver [ 673.830] (II) NOUVEAU driver for NVIDIA chipset families : [ 673.830] RIVA TNT (NV04) [ 673.830] RIVA TNT2 (NV05) [ 673.830] GeForce 256 (NV10) [ 673.830] GeForce 2 (NV11, NV15) [ 673.830] GeForce 4MX (NV17, NV18) [ 673.830] GeForce 3 (NV20) [ 673.830] GeForce 4Ti (NV25, NV28) [ 673.830] GeForce FX (NV3x) [ 673.830] GeForce 6 (NV4x) [ 673.830] GeForce 7 (G7x) [ 673.830] GeForce 8 (G8x) [ 673.830] GeForce 9 (G9x) [ 673.830] GeForce GTX 2xx/3xx (GT2xx) [ 673.830] GeForce GTX 4xx/5xx (GFxxx) [ 673.830] GeForce GTX 6xx/7xx (GKxxx) [ 673.830] GeForce GTX 9xx (GMxxx) [ 673.830] GeForce GTX 10xx (GPxxx) [ 673.830] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 673.831] (EE) [drm] Failed to open DRM device for pci::01:00.0: -19 [ 673.831] (EE) open /dev/dri/card0: No such file or directory [ 673.831] (WW) Falling back to old probe method for modesetting [ 673.831] (EE) open /dev/dri/card0: No such file or directory [ 673.831] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 673.831] (EE) Screen 0 deleted because of no matching config section. [ 673.831] (II) UnloadModule: "modesetting" [ 673.831] (EE) Device(s) detected, but none match those in the config file. [ 673.831] (EE) Fatal server error: [ 673.831] (EE) no screens found(EE) This is an old system and is using: GeForce GTS 450 Does the newest kernel: linux-6.1.19-gentoo supports my old GeForce GTS 450 card? grep KMS .config CONFIG_DRM_KMS_HELPER=y CONFIG_DRM=y
[gentoo-user] X not starting after kernel upgrade
After upgrading to newest kernel the X will not start. Is: make oldconfig same as: make olddefconfig ? Xorg.0.log showing; [ 673.829] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so [ 673.829] (II) Module nouveau: vendor="X.Org Foundation" [ 673.829]compiled for 1.21.1.8, module version = 1.0.17 [ 673.829]Module class: X.Org Video Driver [ 673.829]ABI class: X.Org Video Driver, version 25.2 [ 673.829] (II) LoadModule: "nv" [ 673.829] (WW) Warning, couldn't open module nv [ 673.829] (EE) Failed to load module "nv" (module does not exist, 0) [ 673.829] (II) LoadModule: "modesetting" [ 673.829] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 673.830] (II) Module modesetting: vendor="X.Org Foundation" [ 673.830]compiled for 1.21.1.8, module version = 1.21.1 [ 673.830]Module class: X.Org Video Driver [ 673.830]ABI class: X.Org Video Driver, version 25.2 [ 673.830] (II) LoadModule: "fbdev" [ 673.830] (WW) Warning, couldn't open module fbdev [ 673.830] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 673.830] (II) LoadModule: "vesa" [ 673.830] (WW) Warning, couldn't open module vesa [ 673.830] (EE) Failed to load module "vesa" (module does not exist, 0) [ 673.830] (II) NOUVEAU driver [ 673.830] (II) NOUVEAU driver for NVIDIA chipset families : [ 673.830]RIVA TNT(NV04) [ 673.830]RIVA TNT2 (NV05) [ 673.830]GeForce 256 (NV10) [ 673.830]GeForce 2 (NV11, NV15) [ 673.830]GeForce 4MX (NV17, NV18) [ 673.830]GeForce 3 (NV20) [ 673.830]GeForce 4Ti (NV25, NV28) [ 673.830]GeForce FX (NV3x) [ 673.830]GeForce 6 (NV4x) [ 673.830]GeForce 7 (G7x) [ 673.830]GeForce 8 (G8x) [ 673.830]GeForce 9 (G9x) [ 673.830]GeForce GTX 2xx/3xx (GT2xx) [ 673.830]GeForce GTX 4xx/5xx (GFxxx) [ 673.830]GeForce GTX 6xx/7xx (GKxxx) [ 673.830]GeForce GTX 9xx (GMxxx) [ 673.830]GeForce GTX 10xx(GPxxx) [ 673.830] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 673.831] (EE) [drm] Failed to open DRM device for pci::01:00.0: -19 [ 673.831] (EE) open /dev/dri/card0: No such file or directory [ 673.831] (WW) Falling back to old probe method for modesetting [ 673.831] (EE) open /dev/dri/card0: No such file or directory [ 673.831] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 673.831] (EE) Screen 0 deleted because of no matching config section. [ 673.831] (II) UnloadModule: "modesetting" [ 673.831] (EE) Device(s) detected, but none match those in the config file. [ 673.831] (EE) Fatal server error: [ 673.831] (EE) no screens found(EE) This is an old system and is using: GeForce GTS 450 -- Thelma
[gentoo-user] Somebody deserves a medal...
Some hero fixed Ruby, all good atm. Chromium still absolutely b0rk3d. All tabs spew crash dumps to disk at extremely high frequency, no functionality. "Error 11" not exactly same as signal 11, but very similar. Seamonkey works fine for e-mail and non-multimedia pages; any multimedia -> segfault. -- Beware of Zombies. =O #EggCrisis #BlackWinter White is the new Kulak. Powers are not rights.
Re: [gentoo-user] emerge -U or emerge -N
On 4/10/23 11:11, hitachi303 wrote: Am 10.04.23 um 18:44 schrieb the...@sys-concept.com: Is it better to us emerge -U or emerge -N I've always done -N but it didn't go very smoothly it seems to me -U might be better option but it takes longer. Right now I'm doing -U and it is compiling 549-packages. Just out of curiosity: Is that your update process for world or in which context do you use it? If this is your update process, with which other options do you combine it? 549-packages is quit a lot. emerege -uDUavq @world Haven't done done any updates since Dec. I think that is why. -U came up with 549-packages -N came up with 592-packages
Re: [gentoo-user] emerge -U or emerge -N
Am 10.04.23 um 18:44 schrieb the...@sys-concept.com: Is it better to us emerge -U or emerge -N I've always done -N but it didn't go very smoothly it seems to me -U might be better option but it takes longer. Right now I'm doing -U and it is compiling 549-packages. Just out of curiosity: Is that your update process for world or in which context do you use it? If this is your update process, with which other options do you combine it? 549-packages is quit a lot.
Re: [gentoo-user] emerge -U or emerge -N
On Mon, 2023-04-10 at 10:44 -0600, the...@sys-concept.com wrote: > Is it better to us emerge -U or emerge -N > > I've always done -N but it didn't go very smoothly it seems to me -U might be > better option but it takes longer. > Right now I'm doing -U and it is compiling 549-packages. > Since I learned the difference, I've always only done -U (--changed- use) unless I need to change the value of some new flags. The lynchpin is this: "Unlike --newuse, the --changed-use option does not trigger reinstallation when flags that the user has not en‐abled are added or removed." As far as "better"? Use the option that fits your need or desire. If you don't care to rebuild a package when a new use flag is added, you need not use --newuse.
[gentoo-user] emerge -U or emerge -N
Is it better to us emerge -U or emerge -N I've always done -N but it didn't go very smoothly it seems to me -U might be better option but it takes longer. Right now I'm doing -U and it is compiling 549-packages.
[gentoo-user] Re: Zoom calls make firefox/librewolf crash
On 23/04/10 02:38AM, Efe İzbudak wrote: > Hi everyone, > > So since this weekend whenever I try to join a zoom call, my firefox > crashes and so does my librewolf. I've tried using both > firefox-bin-102.9.0 and firefox-bin-111.0.1 and also > librewolf-bin-110.0_p2. > > This doesn't happen when I disable webgl. > > I'm using dwl-0.4 and I'm on stable. > > Does anyone have any ideas on how to solve this? > For the sake of completeness, if anyone has this issue, downgrade wayland to 1.21-0-r1 to solve it. -- All the best, Efe The funny quote of this email is trivial and left as an exercise. signature.asc Description: PGP signature
Re: [gentoo-user] net-libs/webkit-gtk-2.38.5 and net-libs/webkit-gtk-2.38.5-r500
On Sun, 9 Apr 2023 at 22:37, wrote: > > My system pulled IN two versions of webkit-gtk (slot 4 and 5) > net-libs/webkit-gtk-2.38.5 > net-libs/webkit-gtk-2.38.5-r500 > > Running: > equery d =net-libs/webkit-gtk-2.38.5-r500 > * These packages depend on net-libs/webkit-gtk-2.38.5-r500: > app-office/gnucash-4.8 (net-libs/webkit-gtk:4/37) > net-libs/libproxy-0.4.18 (webkit ? net-libs/webkit-gtk:4) > > equery d =net-libs/webkit-gtk-2.38.5 > * These packages depend on net-libs/webkit-gtk-2.38.5: > app-office/gnucash-4.8 (net-libs/webkit-gtk:4/37) > net-libs/libproxy-0.4.18 (webkit ? net-libs/webkit-gtk:4) > > Which package is pulling IN slotted version? It definitely seems like gnucash and libproxy are pulling in the slot 4 version? You might have other packages that don't depend on any particular slot, and portage will then pull in the latest version, which on a stable system is the slot 5 package. This could maybe be considered a bug. On my system, I have one package depending on a slot 4.1 package, and one with no slot requirement, so I have both a slot 4.1 package and a slot 6 package installed. It's annoying, true. Regards, Arve
Re: [gentoo-user] net-libs/webkit-gtk-2.38.5 and net-libs/webkit-gtk-2.38.5-r500
On Sun, 9 Apr 2023 14:37:26 -0600, the...@sys-concept.com wrote: > My system pulled IN two versions of webkit-gtk (slot 4 and 5) > net-libs/webkit-gtk-2.38.5 > net-libs/webkit-gtk-2.38.5-r500 > > Running: > equery d =net-libs/webkit-gtk-2.38.5-r500 > * These packages depend on net-libs/webkit-gtk-2.38.5-r500: > app-office/gnucash-4.8 (net-libs/webkit-gtk:4/37) > net-libs/libproxy-0.4.18 (webkit ? net-libs/webkit-gtk:4) > > equery d =net-libs/webkit-gtk-2.38.5 > * These packages depend on net-libs/webkit-gtk-2.38.5: > app-office/gnucash-4.8 (net-libs/webkit-gtk:4/37) > net-libs/libproxy-0.4.18 (webkit ? net-libs/webkit-gtk:4) > > Which package is pulling IN slotted version? Use emerge instead of equery, it gives better, if slower, results: emerge -cpv webkit-gtk:4 emerge -cpv webkit-gtk:5 -- Neil Bothwick Q. Why do women have orgasms? A: It gives them one extra reason to moan.
[gentoo-user] Zoom calls make firefox/librewolf crash
Hi everyone, So since this weekend whenever I try to join a zoom call, my firefox crashes and so does my librewolf. I've tried using both firefox-bin-102.9.0 and firefox-bin-111.0.1 and also librewolf-bin-110.0_p2. This doesn't happen when I disable webgl. I'm using dwl-0.4 and I'm on stable. Does anyone have any ideas on how to solve this? -- All the best, Efe The funny quote of this email is trivial and left as an exercise. signature.asc Description: PGP signature
