無語録むごろく

ムゴロク

Subscribe to RSS feed

Emerging iBus

* To use ibus, you should:
* 1. Get input engines from sunrise overlay.
* Run "emerge -s ibus-" in your favorite terminal
* for a list of packages we already have.
*
* 2. Setup ibus:
*
* $ ibus-setup
*
* 3. Set the following in your user startup scripts
* such as .xinitrc, .xsession or .xprofile:
*
* export XMODIFIERS="@im=ibus"
* export GTK_IM_MODULE="ibus"
* export QT_IM_MODULE="xim"
* ibus-daemon -d -x

Failed to emerge www-client/chromium-9999

>>> Failed to emerge www-client/chromium-9999, Log file:

>>> '/var/tmp/portage/www-client/chromium-9999/temp/build.log'

* Messages for package www-client/chromium-9999:

* Installing/updating to version 6.0.446.0_p50559
* Failed Patch: chromium-optional-cups-r1.patch !
* ( /usr/portage/www-client/chromium/files/chromium-optional-cups-r1.patch )
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/www-client/chromium-9999/temp/chromium-optional-cups-r1.patch.out
* ERROR: www-client/chromium-9999 failed:
* Failed Patch: chromium-optional-cups-r1.patch!
*
* Call stack:
* ebuild.sh, line 54: Called src_prepare
* environment, line 2886: Called epatch '/usr/portage/www-client/chromium/files/chromium-optional-cups-r1.patch'
* environment, line 1366: Called die
* The specific snippet of code:
* die "Failed Patch: ${patchname}!";
*
* If you need support, post the output of 'emerge --info =www-client/chromium-9999',
* the complete build log and the output of 'emerge -pqv =www-client/chromium-9999'.
* The complete build log is located at '/var/tmp/portage/www-client/chromium-9999/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-client/chromium-9999/temp/environment'.
* S: '/var/tmp/portage/www-client/chromium-9999/work/chromium-9999'

備忘

Mencoder 壓 x264 放在PSP 上播 第一試

mencoder input.wmv -srate 24000 -af volume=10 -of lavf -lavfopts format=psp -oac faac -ovc x264 -x264encopts bitrate=500 -vf scale=480:272,harddup -ofps 24000/1001 -o 1.mp4

失敗......

Messages for package games-simulation/openttd-0.7.1:

* Messages for package games-simulation/openttd-0.7.1:

* Remember, in order to play games, you have to
* be in the 'games' group.
* Just run 'gpasswd -a <USER> games', then have <USER> re-login.
*
* In order to play, you must copy the following 6 files from
* a version of TTD to /usr/share/games/openttd/data/.
*
* From the WINDOWS version you need:
* sample.cat trg1r.grf trgcr.grf trghr.grf trgir.grf trgtr.grf
* OR from the DOS version you need:
* SAMPLE.CAT TRG1.GRF TRGC.GRF TRGH.GRF TRGI.GRF TRGT.GRF
*
* File names are case sensitive so make sure they are
* correct for whichever version you have.
*
* You have emerged with 'aplaymidi' for playing MIDI.
* You have to set the environment variable ALSA_OUTPUT_PORTS.
* Available ports can be listed by using 'aplaymidi -l'.

package sys-apps/lm_sensors-2.10.7

* Messages for package sys-apps/lm_sensors-2.10.7:

*
* Please run `/usr/sbin/sensors-detect' in order to setup
* /etc/conf.d/lm_sensors.
*
* /etc/conf.d/lm_sensors is vital to the init-script.
* Please make sure you also add lm_sensors to the desired
* runlevel. Otherwise your I2C modules won't get loaded
* on the next startup.
*
* You will also need to run the above command if you're upgrading from
* <=lm_sensors-2.9.0, as the needed entries in /etc/conf.d/lm_sensors has
* changed.
*
* Be warned, the probing of hardware in your system performed by
* sensors-detect could freeze your system. Also make sure you read
* the documentation before running lm_sensors on IBM ThinkPads.
*
* Please refer to the lm_sensors documentation for more information.
* (http://www.lm-sensors.org/wiki/Documentation)
*

Emerge messages as of 12 July 2009

* Updating /etc/vmware/locations
* Use
* emerge vmware-server --config
* to configure your installation of VMware Server 2.
* In order to run VMware Server 2, you have to
* be in the 'vmware' group.
* VMWare Server also has issues when running on a JFS filesystem. For more
* information see http://bugs.gentoo.org/show_bug.cgi?id=122500#c94

* Messages for package app-emulation/vmware-vix-1.6.2.156745-r1:

* In order to run VMware VIX API, you have to
* be in the 'vmware' group.

* Messages for package www-servers/apache-2.2.11-r2:

*
* Selected default MPM: prefork
*
* Please note that you need SysV IPC support in your kernel.
* Make sure CONFIG_SYSVIPC=y is set.
*
* The default webroot has not been installed into
* /var/www/localhost because the directory already exists
* and we do not want to overwrite any files you have put there.
*
* If you would like to install the latest webroot, please run
* emerge --config =apache-2.2.11-r2
*

* Messages for package app-emulation/vmware-server-2.0.1.156745-r2:

* Fallback PaX marking -m
* Use
* emerge vmware-server --config
* to configure your installation of VMware Server 2.
* In order to run VMware Server 2, you have to
* be in the 'vmware' group.
* VMWare Server also has issues when running on a JFS filesystem. For more
* information see http://bugs.gentoo.org/show_bug.cgi?id=122500#c94
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

* Regenerating GNU info directory index...
* Processed 182 info files.

dzen

>>> /usr/bin/gdbar
>>> /usr/bin/gcpubar
>>> /usr/bin/dzen2
>>> /usr/bin/dbar
>>> /usr/bin/textwidth

Emerge Bitlbee messages

* Messages for package net-im/bitlbee-1.2.3-r1:

* Note: Support for all IM protocols are controlled by use flags.
* Make sure you've enabled the flags you want.
*
* The utils included in bitlbee (other than bitlbeed) are now
* located in /usr/share/bitlbee
*
* NOTE: The IRSSI script is no longer provided by BitlBee.

Messages for package sys-apps/openrc-0.4.2

* Messages for package sys-apps/openrc-0.4.2:

* /etc/conf.d/rc is no longer used for configuration.
* Please migrate your settings to /etc/rc.conf as applicable
* and delete /etc/conf.d/rc
* /etc/modules.autoload.d is no longer used. Please convert
* your files to /etc/conf.d/modules and delete the directory.
* You should now update all files in /etc, using etc-update
* or equivalent before restarting any services or this host.
*
* Please read the migration guide available at:
* http://www.gentoo.org/doc/en/openrc-migration.xml
February 2012
S M T W T F S
January 2012March 2012
1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29