palica
-
Posts
294 -
Joined
-
Last visited
-
Days Won
11
Content Type
Profiles
Forums
Blogs
Posts posted by palica
-
-
On 10/14/2017 at 9:11 PM, valerievonck said:
PYTHON_TARGET nor PYTHON_SINGLE_TARGET
are now set through python-kit, you shouldn't have to set this manually, if you have packages that require this, please report it in bug-tracker.
-
-
are you installing funtoo or gentoo? paste the error message of compile failure. what stage3 are you using?
-
So this is how nextcloud is doing it. Allowing individual stats is a good idea. Opt-in is ok, but since the data is anonymous and not containing any secrets I would feel the same as haxmeister and would report from all of my machines.
-
let's discuss what metric should we track?
-
COMPUTER related
-
cpu
- cpuflags
- mem
- swap
-
cpu
- kernel
-
epro
- arch
- subarch
- flavor
- mix-ins
-
ego kit
- enabled non-default kits
-
emerge --info
- portage version
- ego version
- python version
- gcc version
- glibc
- useflags (somehow removing the flags coming from flavor and mix-ins)
- world and sets entries
-
COMPUTER related
-
check the /etc/portage/make.conf.example and all the ELOG stuff for logging output.
-
Mixing NetworkManager and manual wpa_supplicant will not work. Pick only one approach.
- NetworkManager: set it up in the applet or using CLI
- wpa_supplicant & dhcpcd: disable NetworkManager and enable wpa_supplicant and dhcpcd services and set your credential in /etc/wpa_supplicant/wpa_supplicant.conf using the wpa_pass utility
-
Hi all,
I wanted to open a discussion about collecting some anonymous usage data about funtoo kits and maybe some more metrics from your computers. What are your thoughts about it?
This is what for example Nextcloud is using and collecting:
QuoteWe take your privacy seriously. The data is anonymized and you can enable/disable it at any time, by default it is always disabled. Below you can also adjust what kind of data is sent and always see the last report sent to us. When the server receives a new report of your instance, all entries from previous reports are removed. If you disable one of the settings below, you can send a new report, which will delete the data that is currently stored on the server.
Actual data sent:
{ "id": "oc9f8tble2uv", "items": [ [ "server", "version", "12.0.3.3" ], [ "php", "version", "7.1.10" ], [ "php", "memory_limit", 536870912 ], [ "php", "max_execution_time", 0 ], [ "php", "upload_max_filesize", 10737418240 ], [ "database", "type", "pgsql" ], [ "database", "version", "PostgreSQL 9.6.4 64-bit" ], [ "database", "size", 82090520 ], [ "apps", "audioplayer", "disabled" ], ...
You get the idea.
We can discuss what types of metrics could make sense to collect.
Let me know what you thing about it.
-
This is now fixed in ego-2.3.3-r1 so no need to use 9999.
-
paste emerge -pv x11-apps/xdm
-
paste your rc-status -a to see what scripts are autostarting after reboot.
paste your ps aux
-
still having trouble or solved?
-
ego-2.3.3 adds this functionality
try with:
ego config set kits xorg-kit 1.19-prime
-
emerge --resume
-
Are you using funtoo and switching from 5.4.0 to 6.4.0? If yes then you need to:
gcc-config 2 . /etc/profile emerge -e @system --exclude gcc revdep-rebuild -L 'libstdc++.so.6' -- --exclude gcc
-
python 3.6 needed for ego query
-
-
Fair point, but don't know how to automate stuff such as printing - how would you tell the script the print succeeded? And do you really want to print everyday a test page? Just an example.
Sorry I can't help. Maybe someone else has an idea how to test general user interaction with the system.
Stuff gets tested by users running kits. If a bug is there it gets reported and gets squashed the best thing to do is tell your friends to use funtoo so the userbase grows and more people run software and report bugs.
I haven't had problems with:
- usb drives not being recognized by the system
- monitors being plugged in
- loggin in
Funtoo makes it easy with debian-kernel (most of the stuff just works - hardware), curated kits where stuff is not upgraded just because there is a new version of something ...
If you think of something, please let me know.
take care
-
I haven't done anything to my systems and eix just works. It is something with your system that is miss-configured and you have to find it. I was just trying to help to narrow down the causes.
what is in /var/git/meta-repos/repos.conf/default ?
-
4 hours ago, walterw said:
With all of the tools such as docker and virtualbox, I can easily launch a VM, but what I would like to do is to simulate all of the typical activity I perform on my machine and replay that against the VM to see what works and doesn't work.
Is this possible using off-the-shelf software? For example, I would like to plug in a USB thumbdrive, join a wifi network, have certain displays connected, etc.
Well sorry then, but none of your text does say "image" or "iso-imager" or anything similar. I thought your are talking about funtoo and funtoo as such can be installed of a live rescue cd, but using stages. Stages as such can be tested using LXD and simple scripts. What are you trying to solve?
Network traffic = installing packages inside the stage would generate traffic
hardware stuff is not easy to simulate would be my guess
But I still don't understand why? Do you have bad experience? Is this stuff not working? (logging as a user, plugging a monitor)
-
USE flag - you are right not the cause of your problems with eix
Iinstructions - yes you are right it says copy in one and link in other. my fault
copy all the kits from /var/git/meta-repo/repos.conf/ to /etc/portage/repos.conf/ (prepend them with ego-)
add stuff from default to ego-core-kit
add your chopin.conf to /etc/portage/repos.conf/
rm /usr/share/portage/config/repos.conf
-
I would say something like
- https://github.com/ohwgiles/laminar
- LXD
- and a bash script with all the stuff you want to test
-
you want probably
L10N="${LINGUAS}" in your make.conf
for the useflags I would suggest to remove them from make.conf and use profiles instead
for example
gif jpeg png tiff flac ogg vorbis mp3
are all in audio and media mix-ins which are part of workstation flavor which is part of desktop flavor
so selecting desktop flavor has you covered with most of them
-
so I would recommend you to do it this way:
/etc/portage/repos.conf/ will contain:
-
copy all the kits and prepend them with ego-
- so you will have ego-core-kit linking to /var/git/meta-repo/repos.conf/core-kit and so on for other kits
- don't copy default
- put stuff from default into core-kit
- put your chopin.conf in here too
This is going to be the new layout coming with ego-2.3.2
Paste your chopin.conf
eix-sync works without problems no need to write custom scripts
-
copy all the kits and prepend them with ego-
Move to more "unstable"?
in Dev Central
Posted
good way is to list what ebuilds you are missing or would like to be version bumped. For now you can write it here, for the future there is bugs.funtoo.org where you can request for a new/update ebuild.
I like to be bleeding edge myself, but as you grow older you will like stuff to just work and that is where funtoo is heading. Yes, it is not there yet. If you are considering yourself a developer or someone who can write and test ebuilds join #funtoo-dev on freenode irc.