Oleg Vinichenko
-
Posts
619 -
Joined
-
Last visited
-
Days Won
53
Content Type
Profiles
Forums
Blogs
Posts posted by Oleg Vinichenko
-
-
With latest addition of nvidia-drivers, many of hardware might not be recognized due to upstream support deprecation
With attempt of merging the driver on hardware that is not supported you will get the warning of following type:
* ***** WARNING ***** * * You are currently installing a version of nvidia-drivers that is * known not to work with a video card you have installed on your * system. If this is intentional, please ignore this. If it is not * please perform the following steps: * * Add the following mask entry to /etc/portage/package.mask by * echo ">=x11-drivers/nvidia-drivers-391.0.0" >> /etc/portage/package.mask * * Failure to perform the steps above could result in a non-working * X setup. * * For more information please read: * http://www.nvidia.com/object/IO_32667.html
Please, pay attention to the message and your hardware listed in in:
-
-
this USE need set in the mix-in.
-
this is reported already
-
New kit, lllvm-kit now added. It consist of small numbers of ebuilds that are directly related to the sys-devel/llvm. The rationale behind this is that ebuilds for llvm had no update for very long time and are problematic to maintain due to those ebuilds were spread all over different kits. Now they are from one kit. This kit is enabled by default and involves following update steps:
ego sync emerge -C llvm:0 clang:0 emerge -1 llvm mesa emerge -auDN @world emerge @preserved-rebuild
- AdiosKid and Tassie_Tux
-
2
-
yes. this is already reported
acpilight appears better alternative to xbacklight
-
it doesn't break anything
python-3.6 need selected
eselect python list
should be set to python-3.6
emerge -auND @world need ran after setting python-3.6 kit
some additional steps might be required to complete update.
-
they are not unstable. Why are they?
I suggest moving to python-3.6
-
5.12 branch released now
-
provide full emerge output, please.
-
this needs reflected in wiki guides. Or, maybe fixed in ebuilds.
-
kde-kit 5.12 branch now available for quick testing. This will bring regression fixes found recently and will sort bunch of other KDE bugs reported.
It is currently in BETA state but will be default quickly. To help testing, please follow this steps:
Edit /etc/ego.conf and add at bottom of the file
kde-kit = 5.12-prime
Save file and run ego sync. This will sync the meta-repo with new ebuilds for testing.
Kind regards, Oleg.
-
you, perhaps, used a specifically optimized stage3 for the chroot? if cpu's are different, using generic_64 stage would be best choice.
-
that's correct. This is as user controlled files for any weird stuff :)
portage has the ability to add entries into those files too but i never used this feature.
-
/etc/portage/package.unmask, /etc/portage/package.mask /etc/portage/package.keywords
those are.
-
this particular problem should be fixed with update.
most of management such as masks, unmasks, keywords should be just about the same as in Gentoo.
-
this is known problem, which is caused by a coincidental issues caused by datacenter downtimes, where Funtoo infrastructure runs. It will be sorted asap.
-
no, this doesn`t require rebuild at all.
The very major version updastes, such 5 to 6 or 6 to 7 do require such rebuilds.
-
it is an approximate space used during compilation of kernel ins a temporary build environment, typically /var/tmp/portage. not the kernels (package size) installed. it is slightly lesser than 20gb in reality, so that number is set to be 100% sure the build environment has the space.
-
stage3 is a basic Funtoo linux image that is built from sources of software packages list, which is necessary minimal set of software which will allow your to run Funtoo linux on top of linux kernel. This list is carefully crafted and forms a special set, called @system
to rebuild all of relevant packages from sources on your machine, use
emerge -e @system
-
LABEL is actually not that boot-update directly using, it is kernel command line argument that is passed to kernel.
If you using prebuilt kernel from older installation, it's initramfs is not using --disklabel. It was fixed, but to get the fix, you need to do emerge debian-sources.
-
the correct way would be
USE=X emerge x11-libs/gtk+
-
config-extract is not shipped with gentoo-sources. it is a specific tool that included and works with debian-sources only
-
it is mentioned in install guide
Migration to meta-repo, many blocked packages?
in Portage Help
Posted
the proto blocks should be resolved.