Re: [gentoo-user] Weirdness when emerging ffmpeg
I am coming across this more often lately - last was curl with openssl or nss - anoying! Try removing ffmpeg and then re-emerging it. It will usually complain about some other package with use flag problems so remove that too [rinse and repeat as neccessary] until eventually it works and puts back the chain of packages you have just removed ... BillK On Sun, 2012-10-07 at 00:58 -0400, Walter Dnes wrote: Situation: I have ffmpeg on my netbook, emerged without the sdl USE flag. I've run into a scenario where I want it emerged with sdl. The usual response is to to add the sdl USE flag (either in make.conf or in package.use) and simply emerge ffmpeg again. But... == [aa1][root][~] emerge ffmpeg Calculating dependencies... done! [ebuild R] media-video/ffmpeg-0.10.3 USE=sdl* !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: media-video/ffmpeg:0 (media-video/ffmpeg-0.10.3::gentoo, ebuild scheduled for merge) pulled in by (no parents that aren't satisfied by other packages in this slot) (media-video/ffmpeg-0.10.3::gentoo, installed) pulled in by =media-video/ffmpeg-0.10.2[X=,encode=,jpeg2k=,mp3=,sdl=,theora=,threads=,truetype=,vaapi=,vdpau=,x264=] required by (virtual/ffmpeg-0.10.2-r1::gentoo, installed) !!! Enabling --newuse and --update might solve this conflict. !!! If not, it might help emerge to give a more specific suggestion. What is it whining about?!?! I want to overwrite it, not pull in a second version side-by-side. I tried the suggestion, but no luck... [aa1][root][~] emerge --newuse ffmpeg Calculating dependencies... done! Auto-cleaning packages... No outdated packages were found on your system. [aa1][root][~] emerge --newuse --update ffmpeg Calculating dependencies... done! Auto-cleaning packages... No outdated packages were found on your system. [aa1][root][~] emerge --update ffmpeg Calculating dependencies... done! Auto-cleaning packages... No outdated packages were found on your system. [aa1][root][~] I said screw it (or words to that effectG), unmerged ffmpeg, and re-emerged it. The emerge is running as I type.
Re: [gentoo-user] Kernel options and udisk
On Sat, 06 Oct 2012 17:19:57 -0500 Dale rdalek1...@gmail.com wrote: Alan McKinnon wrote: I've promised myself for years since my apprentice days that I would one day built a valve amp from a kit. There's something about the warm glow from the tubes on a winter night that is appealing :-) I'd better hurry up and get on with it, I read that decent quality valves are becoming scarce and are generally only available from (what used to be) the USSR. Found a few sites for ya: http://tctubes.com/about-us.aspx http://electrontubestore.com/index.php?main_page=contact_us http://www.tubesandmore.com/customer_service/about_us I found that by typing 6gh8a in google. That's a old tube that I used to have to replace pretty regular. I think it was used in the audio section and would usually work fine when cold but get a bit weird when it gets good and hot. They got replaced a LOT back then. Anyway, two are in the USA but one is in Canada. Cool finds, thanks! Maybe I should go-ahead and build an amp and be done with it. No more mucking about putting it off :-) Maybe you got more time than you think. ;-) I do think the old tubes have better sound tho. I can't explain it but they just sound different. You're not imagining things. Valves do sound better and you can measure it and see why. Valves and transistors both distort sound to some degree as all electronic systems will. The difference is in how the distortion happens. Semiconductors are prone to even-harmonic distortion, so if you have a 100Hz sine wave, it will produce distortion at 100hz, 400Hz, 1600Hz and so on. Valves produce odd-harmonic distortion, at 200Hz, 800Hz and so on. If you are now thinking Fourier and wondering if transistors try to make square waves, you are bang on the money because that is exactly what is happening. To the human ear, a square wave sounds like gross horrendous distortion, even at very small percentages. At it's worst, this is clipping and happens because a transistor will happily pass current until the voltage drop over it hits the supply voltage and it clips. Bingo, one square(ish) wave and horrible sound. Valves deal with this in a more analog fashion, as the voltage drop nears the supply voltage it passes less and less current, rounding the waveform and never actually clipping it. Which sounds far more pleasant to the human ear. Modern circuitry tries to avoid the transistor problem using soft clipping and other tricks - basically trying to make the transistor behave in the same way a valve oes. This does make a huge difference, but you can never completely eliminate the device's inherent characteristics, it is what it is and this leopard doesn't change it's spots. I think that is why some places still have tubes. Some people just like them more. I think they make great heaters. lol Dale :-) :-) -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] Locking dependant installs
Hi, Suppose the following setup: I want to emerge application F, which depends on library A,B,C,D and E, which unfortunately are not used by any other program and are really heavy to compile in terms of compile time. Unfortunately the last step -- the compilation of A -- fails, which I recognize unfortunately but naturally at the moment all other dependencies are installed. Is there a legal and clean way to lock those already installed dependencies and save them from being wiped out by the tidy and clean up commands normally used after a general update of gentoo? Thank you very much for any help in advance! Best regards, mcc
[gentoo-user] Can't emerge libreoffice-3.5.6.2
Hi, Gentoo! When I try to emerge libreoffice-3.5.6.2, I get the following failure: # --- Oh dear - something failed during the build - sorry ! For more help with debugging build errors, please see the section in: http://wiki.documentfoundation.org/Development internal build errors: ERROR: error 65280 occurred while making /var/tmp/portage/app-office/libreoffice-3.5.6.2/work/libreoffice-core-3.5.6.2/sal/qa/sal it seems that the error is inside 'sal', please re-run build inside this module to isolate the error and/or test your fix: --- /bin/sh cd /var/tmp/portage/app-office/libreoffice-3.5.6.2/work/libreoffice-core-3.5.6.2 source ./Env.Host.sh cd sal rm -Rf /var/tmp/portage/app-office/libreoffice-3.5.6.2/work/libreoffice-core-3.5.6.2/sal/unxlngx6.pro # optional module 'clean' build when the problem is isolated and fixed exit and re-run 'make' from the top-level make[1]: *** [build] Error 1 make[1]: Leaving directory `/var/tmp/portage/app-office/libreoffice-3.5.6.2/work/libreoffice-core-3.5.6.2' make: *** [source-env-and-recurse] Error 2 * ERROR: app-office/libreoffice-3.5.6.2 failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 85: Called src_compile * environment, line 8968: Called die * The specific snippet of code: * make build || die * * If you need support, post the output of `emerge --info * '=app-office/libreoffice-3.5.6.2'`, * the complete build log and the output of `emerge -pqv * '=app-office/libreoffice-3.5.6.2'`. !!! When you file a bug report, please include the following information: GENTOO_VM= CLASSPATH= JAVA_HOME= JAVACFLAGS= COMPILER= # . There is a bug report on this, allegedly, bug #393413, but this has been open since last December. Has anybody else encountered this, and is there a known workaround? TIA! -- Alan Mackenzie (Nuremberg, Germany).
Re: [gentoo-user] Locking dependant installs
On Sun, 7 Oct 2012 17:20:05 +0200, meino.cra...@gmx.de wrote: I want to emerge application F, which depends on library A,B,C,D and E, which unfortunately are not used by any other program and are really heavy to compile in terms of compile time. Unfortunately the last step -- the compilation of A -- fails, which I recognize unfortunately but naturally at the moment all other dependencies are installed. Is there a legal and clean way to lock those already installed dependencies and save them from being wiped out by the tidy and clean up commands normally used after a general update of gentoo? I can think of three options: 1) Create a set (if using portage 2.2). Add each of the packages to /etc/portage/sets/depsforF then emerge -n @depsforF. 2) quickpkg B C D E - then it doesn't matter if they are unmerged them as you can quickly re-emerge them with the -k option. 3) Don't run emerge --depclean until you have resolved this issue. -- Neil Bothwick How is it that we put man on the moon before we figured out it would be a good idea to put wheels on luggage?
Re: [gentoo-user] Locking dependant installs
Neil Bothwick n...@digimed.co.uk [12-10-07 17:36]: On Sun, 7 Oct 2012 17:20:05 +0200, meino.cra...@gmx.de wrote: I want to emerge application F, which depends on library A,B,C,D and E, which unfortunately are not used by any other program and are really heavy to compile in terms of compile time. Unfortunately the last step -- the compilation of A -- fails, which I recognize unfortunately but naturally at the moment all other dependencies are installed. Is there a legal and clean way to lock those already installed dependencies and save them from being wiped out by the tidy and clean up commands normally used after a general update of gentoo? I can think of three options: 1) Create a set (if using portage 2.2). Add each of the packages to /etc/portage/sets/depsforF then emerge -n @depsforF. 2) quickpkg B C D E - then it doesn't matter if they are unmerged them as you can quickly re-emerge them with the -k option. 3) Don't run emerge --depclean until you have resolved this issue. -- Neil Bothwick How is it that we put man on the moon before we figured out it would be a good idea to put wheels on luggage? Hi Neil, thank you for your help! :) Best regards, mcc
Re: [gentoo-user] Locking dependant installs
On Sun, 7 Oct 2012 17:20:05 +0200 meino.cra...@gmx.de wrote: Hi, Suppose the following setup: I want to emerge application F, which depends on library A,B,C,D and E, which unfortunately are not used by any other program and are really heavy to compile in terms of compile time. Unfortunately the last step -- the compilation of A -- fails, which I recognize unfortunately but naturally at the moment all other dependencies are installed. Is there a legal and clean way to lock those already installed dependencies and save them from being wiped out by the tidy and clean up commands normally used after a general update of gentoo? Put them in your world file. or with portage-2.2 you could maintain your own set of stuff you want to keep and emerge that set. This is effectively the same thing as putting things in world but you might find it to be cleaner and easier to maintain (a cluttered world is very untidy and prone to being cleaned) Thank you very much for any help in advance! Best regards, mcc -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Locking dependant installs
Am Sun, 7 Oct 2012 16:33:08 +0100 schrieb Neil Bothwick n...@digimed.co.uk: [...] 1) Create a set (if using portage 2.2). Add each of the packages to /etc/portage/sets/depsforF then emerge -n @depsforF. Just a quick note: current stable portage also supports user defined sets. I use them extensively :) . -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup signature.asc Description: PGP signature
Re: [gentoo-user] Brother MFC 7320
On Fri, 5 Oct 2012 18:15:52 -0700 Chris Stankevitz chrisstankev...@gmail.com wrote: Thank you for sharing. How did you figure out what the solution was? Cups give at end the msg after compile. Regards Silio
