[gentoo-user] How to list NOT installed packages which depend on certain package?
Hi, how can I list all packages INCLUDING those, which are not installed on my system, which depend on a certain package (in my case: dev-libs/boosy) ? I tried emerge d dev-libs/boost but nothing was found... Thank you very much in advance for any help! best regards, mcc
Re: [gentoo-user] How to list NOT installed packages which depend on certain package?
Am 13.01.2013 15:47, schrieb meino.cra...@gmx.de: Hi, how can I list all packages INCLUDING those, which are not installed on my system, which depend on a certain package (in my case: dev-libs/boosy) ? I tried emerge d dev-libs/boost but nothing was found... Thank you very much in advance for any help! best regards, mcc Try `eix --depend dev-libs/boost`. The results might not match your particular USE flags or other factors. Read `man eix` for details. Also, that are only direct dependencies. Regards, Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] How to list NOT installed packages which depend on certain package?
On Sunday 13 Jan 2013 15:47:11 meino.cra...@gmx.de wrote: Hi, how can I list all packages INCLUDING those, which are not installed on my system, which depend on a certain package (in my case: dev-libs/boosy) ? I tried emerge d dev-libs/boost but nothing was found... Thank you very much in advance for any help! best regards, mcc In addition to what Florian mentioned theres also equery depends -a boost albeit a bit slower. -- - Yohan Pereira The difference between a Miracle and a Fact is exactly the difference between a mermaid and a seal. -- Mark Twain
[gentoo-user] What does # mean in emerge output?
# emerge --oneshot --ask wxGTK These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R #] x11-libs/wxGTK-2.9.4.1 Hello, In the above emerge instance, a # symbol appears in the emerge output. What does this mean? man emerge seems to skip this when describing these OUTPUTS. Thank you, Chris
Re: [gentoo-user] What does # mean in emerge output?
Chris Stankevitz wrote: In the above emerge instance, a # symbol appears in the emerge output. What does this mean? man emerge seems to skip this when describing these OUTPUTS. My man emerge says: Symbol Mask Type -- # package.mask * missing keyword ~ unstable keyword NOTE: The unstable keyword symbol (~) will not be shown in cases in which the corresponding unstable keywords have been accepted globally via ACCEPT_KEYWORDS. So your package seems to be masked by an entry in /etc/portage/package.mask. -Matt
Re: [gentoo-user] What does # mean in emerge output?
On Sun, Jan 13, 2013 at 10:17 AM, Matthias Hanft m...@hanft.de wrote: So your package seems to be masked by an entry in /etc/portage/package.mask. Matt, Thank you. I read that very section but missed the definition of # somehow. FYI in this case the package is masked by the devs and unmasked by me in /etc/portage/package.unmask. Chris
[gentoo-user] Re: Ekopath compiler failing to build - something about glibc development files
On 01/12/2013 10:53 PM, Andrew Lowe wrote: Hi all, I've got the ekopath compiler installed on my machine and Portage wants to update it, but fails. Before I go to the trouble of filling out a full bug report, does anyone have any ideas as to the problem? I think it is in the 5th line, Configuration failed... Install ekopath-4.0.12.1_pre20121102 into /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image/ category dev-lang Problem running post-install step. Installation may not complete correctly Configuration failed. Make sure you have glibc developement files installed. Additional information: In file included from /usr/include/endian.h:61, from /usr/include/pthread.h:23, from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/rw/_mutex-pthread.h:52, from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/rw/_mutex.h:71, from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/rw/_strref.h:41, from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/string:44, from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/loc/_locale.h:37, from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/rw/_iosbase.h:37, from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/streambuf:40, from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/ostream:45, from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/istream:44, from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/iostream:34, from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/test.cpp:3: /usr/include/bits/byteswap.h: In function 'unsigned int __bswap_32(unsigned int)': /usr/include/bits/byteswap.h:46: error: '__builtin_bswap32' was not declared in this scope /usr/include/bits/byteswap.h: In function 'long long unsigned int __bswap_64(long long unsigned int)': /usr/include/bits/byteswap.h:110: error: '__builtin_bswap64' was not declared in this scope * From all of the above, I think the important part is that I need to install some glibc developement files. A google search doesn't point me in the direction of what these might be. According to eix glibc, I have debug turned OFF - is this the problem? Or is this for debugging glibc and not my code? I think if I can work out the development files stuff, the bswap64 problem will fix itself. That's obviously a bug in the ebuild because you should never need to install dependencies on your own -- that's a big part of what the ebuild is supposed to do. Because gentoo compiles most packages from source, all of the development files are included with the main package (including glibc) unlike most linux distros that do package them separately because many linux users are not going to compile anything. It's true that the gentoo glibc package might have omitted some of the headers by mistake, but I don't think so in this case because I just wrote, compiled, and ran a C program that includes byteswap.h and got no errors. The bottom line is that the ekopath package is broken -- for reasons I don't know, but the package maintainer should ;)
Re: [gentoo-user] Re: Gigabyte wont boot
If all else fails, maybe it is dead. Yeah no beep equals cpu | ram | mb Check if pin 1 on the cpu is in the right place and cpu power cables right and no bent pins. The cpu and ram are compatible with the mb. Hoover the ram slot and reseat If your second mb works you could try the cpu and ram seperately in the working mb to eliminate the problems/problems bearing in mind they could damage the working mb. -- ___ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) ___
[gentoo-user] OT: blanking disk of linux appliance
shred and dd available, but not srm etc I want to remove the user account info before the device is returned, but dont want to cripple the device. Filesystem is ext3 with default mount options, which implies its mounted with the default data=ordered, and according to the docs In both the data=ordered (default) and data=writeback modes, shred works as usual Would these steps be effective? - set root pw back to installation default - manually create copies of passwd and shadow (named passwd2 shadow2, NOT by copying files then deleting extra lines) containing only the default installation entries - shred /etc/passwd /etc/shadow - mv passwd2 and shadow2 to passwd and shadow - dd if=/dev/zero of=/blah (to blank all spare blocks on fs, dd will bail out once full. Will it miss info from non-fully allocated blocks?) - rm /blah
Re: [gentoo-user] Re: Gigabyte wont boot
On 01/14/13 04:49, Kevin Chadwick wrote: If all else fails, maybe it is dead. Yeah no beep equals cpu | ram | mb Check if pin 1 on the cpu is in the right place and cpu power cables right and no bent pins. The cpu and ram are compatible with the mb. Hoover the ram slot and reseat If your second mb works you could try the cpu and ram seperately in the working mb to eliminate the problems/problems bearing in mind they could damage the working mb. Did you check 2 power cables? And does your power supply work correctly?
